Re: [ql-users] sernet
On 23 Sep 2003 at 13:28, Derek Stewart wrote: Sernet works on all SMSQ/E systems and also non-SMSQ/E systems with SIMSER. On a QL with Superhermes, you will have to use SER1 or SER2. The superhermes SER3 failed to connect on my serial network. I think is is a limitation of the SER3 device driver. And if it did work it would only be 57600 baud Q60 to QPC2 is no problem connects first time with a standard null modem cable from Maplins Electronics or any good electronics shop. Connection speed is 115200 baud. Derek Same here. Same between Q60 Atari, QPC Atari. Wolfgang
Re: [ql-users] sernet
[EMAIL PROTECTED] schrieb: On 23 Sep 2003 at 13:28, Derek Stewart wrote: Sernet works on all SMSQ/E systems and also non-SMSQ/E systems with SIMSER. On a QL with Superhermes, you will have to use SER1 or SER2. The superhermes SER3 failed to connect on my serial network. I think is is a limitation of the SER3 device driver. And if it did work it would only be 57600 baud Q60 to QPC2 is no problem connects first time with a standard null modem cable from Maplins Electronics or any good electronics shop. Connection speed is 115200 baud. Derek Same here. Same between Q60 Atari, QPC Atari. Wolfgang I had it working between ATARI and QPC without any trouble, and Q40 and ATARI too. As I had a 4-ser card in the Q40 (of which only 2 worked properly due to interrupt problems) I had to fiddle a bit to see which of the two worked without problems, and used the one without interrupts for the mouse. I also managed 115k data rates between all machines, and they worked fine. I guess it is a cable problem in most cases - you can easily try connecting the two machines with your nul modem cable and start QTPI on both systems. If you see on the other machine what you typed on one system and vv, then the cable is correct. It was not working here in most cases where problems were reported to me, so blaming SERNET for that is a bit unfair. If you then have a working connection, and you were able to transfer data at higher rates using ZMODEM (for example) both ways, then SERNET was working too. Regards Jochen
Re: [ql-users] sernet
On Wed, 24 Sep 2003 at 14:23:45, Jochen Merz wrote: (ref: [EMAIL PROTECTED]) I guess it is a cable problem in most cases - you can easily try connecting the two machines with your nul modem cable and start QTPI on both systems. If you see on the other machine what you typed on one system and vv, then the cable is correct. Not necessarily. That checks RX/TX only. The link will usually work with incorrect handshake if data rate is slow. It is vital on links to 'real' QLs that handshake is correctly connected. You _might_ get away with it on fast hardware with good serial chips - like 16550 (PN from memory). Often one finds RTS is not connected at all! -- QBBS (QL fido BBS 2:252/67) +44(0)1442-828255 tony@surname.co.uk http://www.firshman.co.uk Voice: +44(0)1442-828254 Fax: +44(0)1442-828255 TF Services, 29 Longfield Road, TRING, Herts, HP23 4DG
Re: [ql-users] Bugs
On 9 Aug 2003, at 20:39, P Witte wrote: Ive recently discovered the following bugs in Smsq/e recently was a long time ago. - I'm slowly working up my backlog. PRINT PRT_USE$ crashes Smsq/e since at least version 2.98 on QPC2 (and QPC2 itself). Yes, confirmed, I'll have a bugfix soon. (Monday). PARTYP, PARUSE, PARNAM$, and PARSTR$ dont work on Smsq/e 3.00 and 3.01. Ok on 2.93 and 2.98 I'll have a look, I haven't had time to confirm/deny. Can anyone confirm? (Save your work first!) see above Is there somewhere to report bugs in Smsq/e? Preferably it should be somewhere where they can also be looked up by others who are experiencing problems or who are out looking for something to fix.. in view of the underwhelming response to that, I presume that you'd better report bugs to me and/or the list. I'll try to pick up all bugs reported. Wolfgang - www.scp-paulet-lenerz.com
Re: [ql-users] Bugs
In a message dated 24/09/03 19:33:23 GMT Daylight Time, [EMAIL PROTECTED] writes: in view of the underwhelming response to that, I presume that you'd better report bugs to me and/or the list. I'll try to pick up all bugs reported. One of the biggest problems with SMSQ/e (especially on the Aurora version) has always been that if FORMAT flp1_ works on a DD disk, try it after FLP_DENSITY 'D' - always gives an error !! Wonder why?? -- Rich Mellor RWAP Services 35 Chantry Croft, Kinsley, Pontefract, West Yorkshire, WF9 5JH TEL: 01977 610509 Visit our website at: URL:http://www.rwapservices.co.uk Stuck with ordinary dial up internet connection ?? Read our review of internet accelerators and broadband at: URL:http://hometown.aol.co.uk/RWAPSoftware/reviews.html
