W2K/WXP Printing Issues

[NICKYSUWANDI]

When i print from my program (i am using foxprow 2,6a), error messages occurer:

FOXPROW caused a General Protection Fault in module
FOXW2600.ESL at 0001:222D

i try using printer generic it same too, my other experience with this?

 

[DSummZZZ]

First, follow ALL the advice in this thread:

Help me ! The font in report preview is too small (FPW26 in WinXP)
thread182-843753

If that doesn't fix the problem, try using a smaller screen resolution. Something like 800X600.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[Bandzo]

Remove all the printers from your control panel and install only generic.

If this doesn't work check your RAM memory.

 

[NICKYSUWANDI]

i had try using only gneneric printer but same, this error message appear in every computer if i load the program

 

[JRB-Bldr]

Are you printing via a Report Form or via 'hard coded' @Row,Col SAY's?

If via a Report Form, have you 'hacked' the Report Form's table to eliminate any inherited printer settings?
faq184-581

Good Luck,


JRB-Bldr
VisionQuest Consulting
Business Analyst & CIO Consulting Services
CIOServices@yahoo.com

 

[NICKYSUWANDI]

i pint via hard coded

 

[rgbean]

Nicky,
Checkout thread182-581077 (see my info on Call32) - you may have a "bad" printer driver.

Rick

 

[NICKYSUWANDI]

rgbean this error only occurer in w2k and WXP, in w98/W95 this problem is not occurer. There's a people say this a bug from FPW26,but i don't believe may friends in this forums can help me.

 

[JRB-Bldr]

The only possible "bug from FPW26" concerning newer, faster computers (not really a Win 2K/Win XP issue) might be the Divide By Zero problem.

However, the error message is not generally the "General Protection Fault" error.

And we have assumed that you have already attended to that by patching your code. If you have not done so, make certain that the EXE and ESL files have been patched.

Good Luck,


JRB-Bldr
VisionQuest Consulting
Business Analyst & CIO Consulting Services
CIOServices@yahoo.com

 

[rgbean]

Nicky,
One explanation for it working in one OS and not another, is that the printer drivers are likely NOT the same. Also, unless these are exactly the same hardware on all OSs, the capabilities of the Floating Point processors are likely different. That is why the explicit reseting of the FP processor may "fix" your problem.

Rick

 

[NICKYSUWANDI]

jrbbldr ,my exe or exl has been patch.
rgbean, my program can't on any OS (windows) oly if i print it won't work in W2k,WXP,W2003. I used the same printer driver and try many things, but useless. i try upgrade to VFX but my program does't work, many error because my program to big

 

[JRB-Bldr]

"I used the same printer driver..."

Is it the EXACT SAME print driver on all OS's or is it the OS-specific print driver for the same manufacturer/model printer?

There can very likely be a difference between the two.

Good Luck,


JRB-Bldr
VisionQuest Consulting
Business Analyst & CIO Consulting Services
CIOServices@yahoo.com

 

[NICKYSUWANDI]

yes, i am using Epson LX-300
This my example source code for print
****
EXTERNAL ARRAY _pdparms
Do case
CASE INLIST(mxmode, "print", "reprint")
mset=GETENV("PRINTER")
mdrv10=mset+"10"
mdrv12=mset+"12"
mdrv16=mset+"16"
*SET PRINTER TO
SET RESOURCE ON
SET PDSETUP TO mdrv12
SET PRINTER ON
?? _pdparms [8]
?? _pdparms [9]
Endcase
? 'Print This Source Code'

 

[BigEdNY]

You are probably OK by now, But, I had the same GPF errors when we went from W95 to W2000. My program 'asked' what LPT# to go to, with TO FILE as an option. Using the 'Report....To File' eliminated the error and reports were able to be printed ok.

 

[dbMark]

BigEdNY is probably right. The Windows 95/98/98se/Me family have "real" DOS windows and native support for LPT1, LPT2, etc. Windows NT, 2000, XP, 2003 all work on different principles. I see that your posts on June 6 and 7 confirm that going to the different Windows family is the basic issue. Now it's time for workarounds, but it's no fun.

On Windows NT, 2000, XP, 2003, the DOS window (now renamed Command Prompt) is "emulated", for lack of a better word, and so are LPT and COM ports. Most DOS prorams will work "as advertised" if you adjust them for the DOS-related issues, you know, reminds me of pounding a round peg into a square hole. With some issues, using a DOS window via the older but limited Command.com works better than Cmd.exe. Sorry, FoxPro for Windows was a hybrid, a limited Windows look and feel, but underneath it too was a DOS program.

Perhaps it is time to upgrade to newer Visual FoxPro with all its improvements, but of course the program will need some rewriting. Other posts here have talked about the DOS issues on the newer computers, but printing is the most common surprise. Also other posts on how to run program converters to get VFP to work on older code, perhaps not pretty, but working.

dbMark

 

[NICKYSUWANDI]

THANKS BIGEDNY, i will try using using u idea.
And thanks to for dMark for u advise..