Fox Pro 2.6a and windows xp printer error

[twinstop]

I upgraded my operating system to Windows XP and am now having problems with the Foxpro 2.6a program printing. When I try to print from Foxpro 2.6a using Vision Point 7 I get the following error:

FOXPROW.EXE caused a General Protection Fault in the module FOXPROW.EXE at 0001:222D. Choose close. FOXPRO will close.

We are on a network with the FOXPRO loaded on the server. All other computers (running windows 98) are working fine.
I have a local HP 1200 laser printer on LPT1 and a local Okidata printer on LPT2. Printers worked fine previously and now in all other applications.

 

[TomKane]

What happens if you try to print from another DOS application? Does it still go wrong if you did something like "DIR > LPT1" or "DIR > LPT2"?

Woud you be able to save your report to disk and use TYPE "filename" > LPT1 does that work?

 

[rgbean]

TwinStop,
Often, these kind of print errors are due to the printer driver - specifically it's not properly resetting the Floating Point Processor. For some background see -

http://support.microsoft.com/default.aspx?scid=KB;en-us;q253356

- "PRB: "API Call Caused an Exception" Error Message with Third-Party Print Drivers". Unfortunately the fix provided is a bit more complicated to implement in FPW. The best way to "fix" it, is to change printer drivers - sometimes a newer or older version will work, or a different model that supports your printer's model.

Rick

 

[tondi]

Twinstop,

If your reports are hard coded, '???' commands will cause your error on WinXP but not on Win98. When I removed the
'???' I stopped getting the error. BTW ... are you able to redirect printing to your OKI printer (LPT2)? If so, how?
That has been a challenge for me which I have not been able to resolve. Everything goes to default printer no matter what I try.

Tony

 

[dbMark]

Tondi,

With dBase 5 I print to a local printer as LPT1 and a remote printer as LPT2, and FoxPro should be similar. I am able to do this after I run "NET USE LPT2 \\otheruser\printer /yes", then I use the command "SET PRINTER TO LPT2". To revert back to the local printer on LPT1 I then "SET PRINTER TO". (Remember, you are still linked to the remote printer, although inactive, until you run "NET USE LPT2 /delete /yes".)

Oh yes, I'm using Win9x and its NET USE command set is slightly different from the one on Win2000/XP. One difference with 2K/XP is that you cannot "NET USE LPT2 ..." to a different location until you delete the current link. Old Win9x was so forgiving...