There are known problems with HP drivers. The HP Laser Jet 4 Plus driver works as does the Laser Jet 5 for Win98.

>here's the scenario:
>I am running a VFP 6.0 app in Win98 on a Novell network
>
>the user picks one menu choice that involves creating
>a cursor and 2 forms but no reports, then they select
>another option that prints a report. this works ok,
>but then if they try another option thats call another form,
>the system crashes - big ugly blue screen of death, message fatal exception error, etc basically lights out - requires complete reboot!.
>
>the above 3 options in the app are choices from a windows
>style pulldown menu.
>
>option 1:
>
> do form whatever.scx (this calls another form, then both are released)
>
>option 2:
> do form somethingelse
> (this allow the user to create a cursor and print a report
> then release the form)
>option 3:
> do form anotherone
> (crash happens here (right after the load and before the init))
>
>basically, the code is very simple and seems to work fine
>on machines with foxpro installed.
>One other machines I have all the required files in the executable
>directory (or at least I think all the files)
>
>questions:
>what exactly are the required files and DLLs for an exe to run?
>why does this crash happen only if a report is run?
> (otherwise everything works ok)
>
>I know I haven't given all the details of my app code here,
>but there is nothing fancy going on - just forms with just basic
>command buttons with very simple code, SQL statements, simple
>grids, but no fancy activeX controls etc
>
>plenty of RAM on the machines (one had 256Meg!)
>I checked the resource meter - seems ok
>
>Anyone have any ideas?
>help would be greatly appreciated.
>
>-tjm
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>I am running a VFP app (an exe) on a computer on a Novell
>network that has several options for the user from a main
>pulldown menu.
>The first option(lets call it option#1) a form is called, it creates
>a cursor that user
>in turn, is released, and then another form is called