Found this on a forum which may help -

We've seen this reported on a dual-processor system. The solution seems to be to
add CALL SLEEPQQ(500) at the beginning of the program - this allows enough time
for INITIALIZEFONTS to complete.

---------------------------------------------

If that doesn't work download a copy of process monitor and run that prior to running the program and then have a look at the results as it may shine some light on exactly whats going wrong.

The other option would be to build the machines using windows 7 and then run a virtual copy of windows 95.