Hi,
I have a biped, an ssc and an old dos PC. I am having to use the old PC as XP SP2 is having issues with not letting me near the com ports…
I have tried various commands but am still having no luck in dos… anyone else using dos out there?
I am trying:
MODE COM1:9600,N,8,1,N>NUL
ECHO #3P1000T1000 > COM1
and I have the jumpers set to 9600 on the ssc32. Still no joy, this gives erro while writing to com1…
This doesn’t have anything to do with the ssc-32 really. I don’t remember there being a way to disable handshaking on serial ports using the MODE command. You more than likely need to tie the handshake lines on the serial port to an active level to fake it out. Try connecting DTR to CTS and RTS to DSR on the serial port connector, if that doesn’t work then tie DTR to both CTS and DSR (leaving RTS unconnected.) Obviously the GND, TXD, and RXD pins still need to go to the SSC-32.
For win95/98 machines, you need to make a null modem type of serial connector like below to make windows think something is connected to the serial port. Connect the tx and ground pins to the ssc-32. Bach files can’t recieve on the rx line, so no need to connect. This is not a problem with XP.
I was using my db9 to db9 from my modem… perhaps this is the route of all evil … or at least my problem 
I’ll check it out.
Thanks.
it is not the cable per-se, just the lack of hand shake signals required by DOS to send data out the serial port. You can make the necessary connections at the db-9 on the SSC-32 however it will undoubtedly void any type of warranty I am sure.
If you have a dos communications program like flashlink, promodem, qmodem, kermit, etc then you can quite likely configure its serial port connection for no handshake and send strings through that.
You may want to try the below line instead of the one you are using.
mode com1:9600,N,8,1 >nulI don’t remember DOS requiring the handshaking.
Why not try a terminal program?
a loopback plug might tell you a lot.
Alan KM6VV