VFP 6.0 (patch 2) Freezes with HP supplied printer drivers running with Windows 98..

Has anybody seen this behavior? In both development mode and compiled my computer will completely freeze up when trying to run my app or misc. parts of it when I am running Windows 98 with the printer driver that came with the printer and not the one that came with Windows 98. I have had at least seven users report this same problem all of whom fit the same pattern.

Here is the pattern so far; the computer will freeze up if:
The user is running Windows 98
The user is using a printer driver that is distributed by HP and not the one that comes with Windows 98
So far this has been reported only from users of HP printer drivers but not all the same printer/printer driver.

My machine is Pentium 133 with 80 Meg of memory and no TSRs running. I do not have that info. for the other users.

The places where the freeze takes place have nothing to do with printers or printing functions. If I take a form that locks up the machine while running in the app and run stand-alone in development mode (DO FORM myform), it will run fine. If I create a menu that has only one "command" pad which has a DO FORM myform, the machine will lockup when the menu pad is clicked.

So far it seems to be a Memory problem . At the beginning of my app two modeless forms are put on the screen. The first one is "text only" and the second basically had only one line of code in the form.activate procedure which was an IIF(SYS(21)... The app was freezing in the middle of the first form opening. If I removed the SYS(21) reference from the second form then the first form would instantiate without problems but the second form would freeze. If I removed both forms from startup then my app would run but would freeze when any other form was called from the menu bar.

If I switch to the HP driver that came with Windows 98 there would be no problems what-so-ever. If I ran my app with the HP driver that came with the printer but running Windows 95 instead of 98 there would be no problems what-so-ever.

In looking into the C:\Windows\AppLog\myapp.lgc file I can see where the last thing that is run before the freeze-up is the printer driver. I can see where the various VFP DLLs are run, then MyApp.exe, then various MyApp system files are opened, then Win.ini is opened, then the HP driver.dll is run, and then that is the end of the log file.

HP insist that the drivers that originally shipped with their printers under Win 95 are still the ones to use and, indeed, I have never had any problems with them except when running VFP 6.0 (patch 2) and some of my users say that they like the HP supplied drivers better and have actually had problems with the Win98 supplied drivers in other programs.

Has anybody heard of this problem or have any recommendations of what might be done to at least predict the problem before a user's machine locks up so that I could popup a warning screen letting the user know what the work-around might be or at least to contact me.

Any Help, Suggestions, or Rumors would be appreciated.

Ed