🚀 go-pugleaf

Ok, I wrote a program about 2 years ago that will poll the "busy" pin on 
the parallel port.  It's accepting a TTL pulse and waits for a change in 
status value before doing something.  It was compiled as 16-bit on a 
laptop running Win98.  We got a new laptop and I tried moving the 
executable over and it didn't work (after intalling all the necessary 
16-bit dlls into Win/Sys directory).  Then I tried recompiling and that 
didn't work.  So, I downgraded the new laptop to Win98 and that didn't 
work either.  I am using the interrupt function in vbasm.dll to gain 
access to the port.  It seems to be able to read from the port once and 
then (although the TTL value changes) the value read doesn't change the 
way it used to.  Anyone know why this would not work on a new laptop?  
Also, in the BIOS I noticed that there are the following options for the 
"mode" of parallel port:  output only, bi-directional, EPP, and ECP.  
Anyone know which of these is best for what I'm doing?  Unfortunately, I 
don't have access to the old laptop anymore so I can't look up the BIOS 
settings on that one, but I'm sure they were standard settings (whatever 
those are).  Here's the snippet of code that calls the busy pin:

Global Const IntNum = &H17

'power the device by turning on data lines
InRegs.AX = &H7
InRegs.DX = &H0
Call vbRealModeIntX(IntNum, InRegs, OutRegs)
'Status Request Parameters
InRegs.AX = &H2000
InRegs.DX = &H0
TriggStat = OutRegs.AX

'Read from the port
Call vbRealModeIntX(IntNum, InRegs, OutRegs)
TriggStat = OutRegs.AX
Text1.Text = TriggStat

Maybe my addresses are off for the new machine?  I never really 
understood how those worked (I lifted them from something else I saw and 
they just worked).  Thanks for any and all help.
-Adam