DOS Guy
2009-06-10 00:46:56 UTC
I'm working with a DOS app (written in PowerBasic) where two PC's are
communicating with each other over the com port. I open the ports at
115k-baud. Data is transfered mainly from one system to the other
(although there is some bi-directional coordination).
I get pretty close to the theoretical max transfer rate when both
systems have booted into DOS to run the app.
Now this app talks to some custom hardware in one of the PC's using some
machine code and i/o reads and writes. This app was made XP-compatible
by "wrapping" it in a port-mapper (I forget the name - port-talk I
think). This allows the app to function perfectly when running under
XP.
However, the serial communications aspect of the program functions
extremely poorly. At first I thought that XP was interfering with the
app's ability to talk to the com port via BIOS calls, but then I
realized that PowerBasic probably has it's own com port interface and
interrupt handler.
So, I'm wondering if anyone out there has any experience with a compiled
basic DOS app (powerbasic or otherwise) that performs serial I/O and
running such an app under win-XP.
Or if I'll have to poke more holes in the I/O permission table in order
to give the app full access to the serial ports - and how do I "remove"
XP's influence or control over the ports?
communicating with each other over the com port. I open the ports at
115k-baud. Data is transfered mainly from one system to the other
(although there is some bi-directional coordination).
I get pretty close to the theoretical max transfer rate when both
systems have booted into DOS to run the app.
Now this app talks to some custom hardware in one of the PC's using some
machine code and i/o reads and writes. This app was made XP-compatible
by "wrapping" it in a port-mapper (I forget the name - port-talk I
think). This allows the app to function perfectly when running under
XP.
However, the serial communications aspect of the program functions
extremely poorly. At first I thought that XP was interfering with the
app's ability to talk to the com port via BIOS calls, but then I
realized that PowerBasic probably has it's own com port interface and
interrupt handler.
So, I'm wondering if anyone out there has any experience with a compiled
basic DOS app (powerbasic or otherwise) that performs serial I/O and
running such an app under win-XP.
Or if I'll have to poke more holes in the I/O permission table in order
to give the app full access to the serial ports - and how do I "remove"
XP's influence or control over the ports?