🚀 go-pugleaf

dic5340@hertz.njit.edu (David Charlap) writes:
: In article <1992Jul29.193644.7290@tin.monsanto.com> kncarp@nicsn1.monsanto.com (Kevin N. Carpenter) writes:
: >Anyhow, does anybody have any suggestion as too what might be going on?
: >I've theorized that the OS/2 Math Co-Processor simulation routines might
: >have a subtle bug.  The other possiblity is wrapped up in the IRQ issues.
: >Does anybody know how I can disable the Co-Processor simulation and just
: >let Turbo-C's routines do the work?  Oh, yeah, this program is running
: >in a DOS box.
: 
: I don't like your interrupt configurations, but I don't know if that
: is causing the problems your describe.  You DO realize that all data
: being sent to printer ports gets routed through the spooler, right?
: I don't know if this is causing any problems or not.

I know, I know, I'm pushing it...

: 
: Doesn't TurboC have an option not to use any coprocessor routines?
: With Tubro Pascal I can go to options->compiler options, and set
: Numeric processing to Software, and the program won't use the 8087
: even if its installed.

Well, I changed the program from doing a BIOSPRINT function call to a 
direct OUTB(portnum) call and the problem seems to have gone away.  I 
found it interesting that even though all I'm doing is a direct output
to the port address, OS/2 will still protect that port from other windows.
A rather complete job of resource protection if you ask me...


--
Kevin Carpenter       Internet:  kncarp@nicsn1.monsanto.com
Monsanto Company 
St. Louis, Missouri, U.S.A.
Opinions expressed are those of the author, not the company he works for.