home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!jvnc.net!rutgers!spcvxb!benezra_a
- From: benezra_a@spcvxb.spc.edu
- Newsgroups: comp.os.os2.misc
- Subject: sio and vsio.sys problems
- Message-ID: <1992Dec25.101655.4762@spcvxb.spc.edu>
- Date: 25 Dec 92 15:16:55 GMT
- References: <2PJBwB1w165w@tcscs.UUCP> <1992Dec25.105652.21041@actrix.gen.nz>
- Organization: St. Peter's College, US
- Lines: 14
-
- > DEVICE=C:\OS2\COM.SYS (3,3e8,5) (4,2e8,2)
- > DEVICE=C:\OS2\MDOS\VCOM.SYS (3,3e8,5) (4,2e8,2)
- >
- > in your config.sys? OS/2 doesn't recognise COM3 or 4 unless you add these
- > parameters. This is in the FAQ.
- >
- > I believe these parms will also work with the (very good!) SIO.SYS and
- > VSIO.SYS third-party comms drivers - currently at version 0.15, I hear.
- >
- They will indeed work with the sio.sys drivers, but ckermit 5a(188) will not.
- I am now using ckoker16.exe and it works fine but ckoker32.exe bombs out with
- a "message file not found" error. I'm using v 0.11 i believe.
-
- Alan Benezra
-