I have a pile of Quickbasic utility/hardware control programs that directly access PC parallel port hardware. I also have several legacy hardware devices that interface via the Parallel port...logic analyzer, prom programmer, battery charger etc.
These have all been rendered obsolete by Windows XP's denial of access to the port hardware. Yes, I can dual boot, but that ain't what I want.
I'm sure this is a good idea for 99.9% of the population who only use their PC for power point presentations and downloading p*rn. But it's a problem for us hardware junkies.
Recoding all the programs in VB with a third party control to access the ports works, but only for the code I wrote. And it will no longer run on the dos laptop. I'd really like to be able to pop out three lines of quickbasic code to run some hardware test.
What's needed is a hack for XP that lets the OS ignore direct reads/writes to the parallel port. If hackers can disable registration codes, they ought to be able to figure out how to make XP ignore direct port accesses. It might be as simple as hacking an older version of Command.com to run as the dos box in XP. I haven't tried setenv yet, but that would be too easy.
Google turns up LOTS of requests for this capability, but so far, no solutions.
Anything helpful available? Thanks, mike