home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!yale.edu!yale!gumby!destroyer!cs.ubc.ca!unixg.ubc.ca!ochealth
- From: ochealth@unixg.ubc.ca (ochealth)
- Newsgroups: comp.os.os2.apps
- Subject: sio.sys beta 25 com drivers are buggy
- Date: 5 Jan 1993 10:45:19 GMT
- Organization: University of British Columbia, Vancouver, B.C., Canada
- Lines: 26
- Message-ID: <1iborvINNsdq@iskut.ucs.ubc.ca>
- References: <1ialdtINNp7g@iskut.ucs.ubc.ca> <1993Jan5.025319.14377@magnus.acs.ohio-state.edu> <1ibntmINNscr@iskut.ucs.ubc.ca>
- NNTP-Posting-Host: unixg.ubc.ca
-
-
- Beta version 25 of the SIO replacement com drivers are buggy (they cause
- TRAP E - page fault) on my system, usually at boot time, although
- it is kind sort of random. It says exception in driver com3: so
- I'm certain it's their fault. Verson 20 was better I think.
-
- Other things seemed wonky with v25, on a couple of occaisions, the desktop
- froze totally, except for mouse (moved, but nothing else), and a crash
- when I tried to start a seamless winos2 session. My system had been rock
- solid until I added the beta drivers. (this bolsters my theory that the
- OS/2 kernel, basic stuff is EXTREMELY stable, and that 99% of traps,
- hangs, freezes, crashes come from device drivers and low level DLLs.
- Previous oddities went away with standard VGA, and now with the
- generic 32bit SVGA drivers (bless you IBM, although they could be faster).
- The amount of problems those %((*^(*^ Trident drivers caused....)
-
- So far, the worst I've had from the standard com.sys driver is TE/2
- clobbering the serial ports. I guess the driver dies. At least everything
- else continues working, and I can shutdown and reboot properly. I
- hate not being able to reload the com port drivers on the fly. Why
- can't OS/2 just kill the old driver and reload it? Grrr.
- --
- ______________________________________________________________________________
- ochealth@unixg.ubc.ca
-
-
-