home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.misc
- Subject: Re: MSD under OS/2 (Was Re: Couple of OS/2 problems...)
- Message-ID: <1992Jul31.173029.2095@njitgw.njit.edu>
- Date: 31 Jul 92 17:30:29 GMT
- References: <Bs7szn.KA6@acsu.buffalo.edu>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 20
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <Bs7szn.KA6@acsu.buffalo.edu> tjc@acsu.buffalo.edu (Thomas J. Corsalini) writes:
- > I have noticed that MSD reports a 16550 UART on COM1 under OS/2 but
- >an 8250 under DOS! Has anyone else noticed this? My I/O board has a 16450
- >chip.
-
- Neat! I think I can explain why. Note that this is 100% speculation.
-
- MSD is probably checking for the presence of buffering. Under DOS, if
- the program ignores DOS, and manipulates the UART, and still detects
- buffering, it can assume a 16550. Otherwise, it assumes 8250. Well,
- OS/2 buffers the port no matter how the VDM-based program gets to it,
- so MSD assumes a 16550.
-
-
-
- --
- |) David Charlap "I don't even represent myself
- /|_ dic5340@hertz.njit.edu sometimes so NJIT is right out!.
- ((|,)
- ~|~ Hi! I am a .signature virus, copy me into your .signature file.
-