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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Watcom Win386 Read Error

Status
Not open for further replies.

MDoom

Programmer
Aug 31, 2001
52
US
This error message: "Watcom Win386 Read Error" occurs frequently when trying to open a foxpro 2.6 application on a Windows 98 machine. This error message displays on its own in a alert box and the user is unable to open the application. It happens about half the time on these windows 98 machines. It doesn't occur at all running the same application on Windows 2000 or Windows XP machines.
Any suggestions or help would be greatly appreciated.
 
Since this is likely a memory problem, start by reading - "PRB: Insufficient Memory or Not Enough Memory for Application".

Make sure you have the memory manager settings right, and also check your CONFIG.FP(W) file for a MEMLIMIT line.

Note: Watcom was the C compiler used to create the FoxPro .EXE and .ESL files. Even Microsoft used it when they first "merged" with Fox Software!

Rick
 
Unsure how to access the memory manager settings or what they should be. Can you describe?
Thanks
 
Well it's dependent on which version of FPD you are running - Extended or Regular, with or without EMS. (It may also be a bit different if you are running 2.6 or 2.6a.)Another factor is how you start it up - .LNK, .PIF and whether you run it directly or start it up in a .BAT file.

Sorry, it's not a simple answer - remember Win9x is based on DOS, where NT/W2K and XP aren't and they do things a bit differently.

Did you check out the MEMLIMIT setting? I usually use:
MEMLIMIT = 60, 2048, 16384

Rick
 
I'm running 2.6a, and I believe it is extended, but I don't know if it is with or without EMS. The application is an .exe and was created in the foxpro development 2.6a. I tried different memlimit settings with no change.
The only other option I was thinking is to upgrade the windows 98 to windows 2000. This problem hasn't occured on any of the windows 2000 machines.
Anything else you can suggest...thanks again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top