On Thu, 18 Jan 96 16:16:35 EST Steve Dirickson, in reply to my
 
<<Is there an update for Windows 95 to make COM3 and COM4 functionally
equivalent to COM1 and COM2 serial ports?>>
 
wrote the following:
 
>Could you clarify what this means? As far as I know, COM3/4 work just
>fine; in fact, the machine I'm typing on is talking to CIS even as we
>speak, using a modem configured as COM3 on IRQ 11. There is video
>hardware out there that has a conflict with the standard COM4 I/O address
>of 0x2E8 (ATI, S3, anything claiming 8514/A hardware compatibility), but
>that's a hardware issue, unrelated to the OS.
 
We have an internal modem on COM4 in our Windows 95 Pentium 90 PC. The CIM will
not dial out to the CIS. Under terminal emulation, the pointer freezes when the
screen saver kicks in and we have to go into configuration mode to re-activate
the connection. We are unable to do this work-around for file transfer as it has
the same effect as the screen saver and we are unable to get at the
configuration mode to re-activate the connection.
 
Our PC supplier says MicroSoft acknowledge there are problems associated with
COM3 and COM4. This has been confirmed by MiniSoft whose MS92 terminal emulator
we use along with R1 for Windows from WRQ. We have heard rumours that there is
an update for Windows 95 due for release shortly which fixes the COM3 and COM4
deficiencies along with numerous other glitches in Windows 95.
 
Every PC is a unique "disaster waiting to happen" to quote Birket Foster.
 
Enjoy your use of COM3 while it works for you.
 
Ken Nutsford  <[log in to unmask]>