Getting "FoxproW caused an illegal instruction in module<unknown> 040

[rjm13]

I'm trying to run a Foxpro 2.6 application on a new server, Win 2003 Small Business Server, and getting the following message:

Getting "FoxproW caused an illegal instruction in module<unknown> 040F:BB58|||| Foxprow will close"

I've tried resetting the memlimit in config.fpw and Virtual Memory to increase memory. There are very few other applications running on the server (Access 2000, Symantec Anti-virus) and most workstations are able to run the software okay. The workstations are running Win 2000. Workstations that had WinME OS but were upgraded to Win 2000 are getting the same message as above.

The setup for the application loads the runtime files, foxprow.esl and foxtools.fll, to the local path to run.

What needs tweaking on the workstations and the server? Any suggestions are greatly appreciated. I've learned a lot from the other postings but could not pinpoint the help for this problem.
Thanks.

 

[rgbean]

When do you get this error? On startup? During the program? Are you running the patched FPW2.6a version for "High Speed CPUs"?

Rick

 

[rjm13]

The program starts with a login screen. When trying to login the problem happens. I'm using the lastest foxw2600.esl (dated 11/09/98) if that's what you mean by patch.

 

[rgbean]

See thread182-471045 for one discussion. The date on your ESL file is really meanless - the last official update to FPW 2.6 was in August of 1994! However many programs - including the High Speed CPU fix may change the external date.

Were the ME machines simply upgraded to 2000, or were these new (faster?) machines? What SP level of 2000 are they running?

There are a number of reasons to get "illegal instructions", but almost none of them are really FPW's fault - it was only tested on Win 3.x! However I've got FPW 2.6s applications that still run fine on XP Pro SP2.

Have you configured your virus checkers to NOT scan .DBF, .CDX and .FPT files?

Rick

 

[DSummZZZ]

As a side note per the reference to Thread182-471045, I put DZPATCH on my web site, feel free to download it. Just follow the link by my signature and scroll down until you find it on that page.

Illegal operation errors can also occur as a result of bad index files. Since you said it happens at login time, I'm guessing you do some sort of a lookup at that time. It could be that when you copied the files to the new server, Fox got confused with different blocks on the disk.
Try recreating the indexes from scratch on all of your tables.


-Dave Summers-

Even more Fox stuff at:

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

 

[rjm13]

Rick,
Two machines were simply upgraded from ME to 2000. A third newer faster machine is Win 2000. All are SP-4.

The virus check was configured for "All" files and a test with .dbf etc. NOT selected was attempted and the app still didn't run.

Dave,
Thanks for the link and advice. The app gets re-indexed on a fairly regular basis. Is this the same as re-creating indexes? Again, the app opens and works fine on 3 other machines. It does not open on the 3 mentioned above AND the server, even though all point to the server install.

 

[rgbean]

Reindexing isn't the same as recreating the indexes. Sometimes, when an index is corrupted, the header is also corrupted, and since that's where the index expressions are kept, it may not be really indexing the file as it was originally defined.

ALWAYS, recreate the indexes! You can keep the index creation information in code, or keep it in a (readonly) table that's part of your .EXE.

Rick