I'll say you're in for a bit of work!
Your program must be completely re-structured.
VB is Event-driven, and doesn't like top-town and
procedural code at all.
THis, in it self isn't neccessarily a show-stopper, as long as your
QB code is reasonably structured, but the *big* problem here, is
the I/O and direct memory access.
This is a big NO NO in windows in general, and in win2k & XP in
particular. IO belongs to the system. Period.
This means that you need to get hold of, or write a device-driver
for your card. You might be lucky... The card-vendor might have drivers
If not, you have to write them yourself. That is *NOT* a task that can be
done in VB, but is usually the domain of C and or Assembly.