RE: Recurrent serial port problems

Kraml Willibald Dr. (KRAML@kpmg.co.at)
27 Mar 96 08:16 CET

As everybody seems to have his little problems with the OGo serial
connections, I can add my 2 cents here and tell you about mine:

War story 1: At home I use a notebook with Win95. Everything worked
fine first time; although once I had a weird experience with Win95
telling me that the port would be in use by another process (which wasn't
true); rebooting Win95 cured the problem.

War story 2: At work I use Win 3.11 on a machine hooked up to
the corporate LAN. No way to bring the Omnigo serial connection
to live. I even changed the serial board and tested it with all
kinds of equipment. An RS232 tester showed that signals were clearly
coming out from the Windows machine, but no response from the OGo.
Handshaking lines show the correct signals.
After a lot of experimenting I found the culprit (?): I use a
special serial driver which diverts COM4 to a network modem
(Shiva) - but not COM2 which I try to use for the OGo! Still,
when I disable the netmodem altogether, serial OGo connectivity
works! I might have to blame the Shiva serial driver, but I am just
not yet sure if this is 10 percent true ...

I doubt this will be of much help to all the others experiencing
serial troubles (serious troubles :-), but perhaps collective
evidence will shed some light on it in due course.

Yours,

Willi

W> Same thing happened this past weekend, and it is still out there. This
W> time around my i/o board got totally smoked while I was trying to
W> coerce the OGO to speak. I had the PC apart to switch the cable etc.
W> do I have no idea what the cause was. The OGO seemed no different so I
W> assumed that the i/o board was to blame. I replaced it, but still no
W> go. Laplink, graphics tablet, etc all seem to function fine from the
W> port. The symptoms are identical in that while none of the programs
W> will establish a connection, they behave differently if the baud rate
W> on the OGO is changed. In addition when the connectivity pack gives up
W> trying, the OGO drops out of the connect mode as it should. This makes
W> me skeptical of the cable being the culprit along with the act that I
W> tried to recreate the problem
W> before by jiggling the cable, etc. with no success.
W>

Dr. Willibald Kraml (kraml@kpmg.co.at) ...- -.-- --... ...-- -.. .
KPMG Austria, Koling.19, A-1090 Vienna --- . ...-- .-- -.- .-..
+43(1) 31 3 32 -200 (Voice), -5 (Fax)
E-Mail address at Vienna University: Willibald.Kraml@univie.ac.at