Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cause a General Protection Fault in Module

Status
Not open for further replies.

Guest_imported

New member
Jan 1, 1970
0
I use in windows 2000 professional and I had been Patch Foxprow.exe and then I run it for Applications , during all task some application run good but some applications fail message &quot;Cause a General Protection Fault in Module <unknown> 0667:A36A...Foxprow will close&quot; and then I click OK then foxprow close , I want to fix it, may all you help me SOS because I need it as soon as.
Thanks a lot all you.
 
Unfortunately, this really isn't enough information to provide much help. What version of FPW are you running? (2.5, 2.5a, 2.5b, 2.6, 2.6a?) Do the runtime versions match the development system? Have you any idea what the code is doing at the point of the fault? Does it always seem to be at the same place? Are you using any API calls or 3rd party .FLLs? What Service Pack are you running on W2K? ('base', SP1, SP2?) Are you running any virus checking software? Is it and the data up to date? Are you running any non-W2K screen saver? What else is running on the system when this happens?

Rick
 
Hi,

In the Foxpro Help there is an specific topic on this matter. There are some pieces of advice there (I would copy it now, but I have it in spanish, sorry!) Look it like &quot;general protection errors&quot; in the index label.

David.
 
David,
That was a good &quot;catch&quot;, it's been a long time since I read that particular Help file entry, and it was interesting to re-read. I'd only add that because this was written assuming you were running under Windows 3.x, some of the specific information doesn't necessarily apply to the 32-bit Windows environment - especially NT / 2000 / XP.

Rick
 
I had this same error using a FoxPro 2.6 for Windows application on Win2000.

I added the line:

memlimit = 100,4096,16384

to the config.fpw file to set the memory usage and this seemed to resolve the problem. Also, check the properties of any shortcuts you are using and make sure you have 'Run in separate memory space' checked.

cheers,

Nathan
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top