Had some annoying problems pop up at client sites with modems dropping
out during comms.
I found one bug in our xmodem handing in that we were not sending back
NAK's on comm errors which partly solves the problem (the app recovers
after an error) but the errors are still being logged far too often
(every 20-30 seconds during calls).
The component we are using (TMSComm - this is D1), is reporting 'windows
errors' which from the Delphi/MS help are described as:
"Set when a line-status error occurs. Line-status errors are
CE_FRAME, CE_OVERRUN, and CE_RXPARITY. "
Weird thing is that the errors occur everytime on a Win95 laptop we have
here (and the clients Win95 machines) but not the Win98 machines that we
have tried (with the same modem init strings, port settings etc).
I am still doing some experimentation but I am starting to suspect that
something was broken in the comm driver for Win95 (version 8-24-1996)
and fixed in the Win98's comm driver (dated 4-10-1998). Somewhat
annoying is that IE5 or something updates the driver again - on my
machine the driver is dated 5-11-1998.
Anyone else notice anything weird with windows Comm drivers or am I just
being paranoid?
Grant Black
Software Developer
SmartMove (NZ) Ltd
Phone: +64 9 361-0219 extn 719
Fax : +64 9 361-0211
Email: [EMAIL PROTECTED]
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
