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!

foxpro 2.6a app not working after win2k upgrade 2

Status
Not open for further replies.

britexpat

MIS
Jul 27, 2001
1
US
1. Application working
2. Upgraded to Windows 2000 on a test machine (not clean install)
3. Foxpro application won't work on the win 2000 machine:
Displays start up screen but then stops.

Clean install for win2000 not an option.
Are there some .dll files or .vbx files that I need?

Help!
 
Many people have reported problems with a number of DOS and Win3.x applications on "upgraded" Win2000 machines (starting back in the W2K beta days). The only "fix" that works reliably is to reformat the drive and do a clean Win 2000 install followed by an install of all your applications in a "historic" order. i.e. In the order they were probably released / installed on the old machine.

Speculation as to why these "old" applications don't work is usually based around incorrectly converted Registry settings. It also seems to depend on the OS you are upgrading from (NT seems to be "best", and the original Win95 is reported to be the "worst - YMMV.)

Not much help, but it's always good to know that you're not alone.

Rick
 
A couple notes about going to W2K. Make sure you have the app "patched" for the Divide by Zero error. NT won't allow fox or fox apps to run while this error is occurring. After that, the ony file 'required' is the FOXW2600.ESL file. There could be an application specific .DLL or .FLL that the developer used, but you would have to know which one(s) and add them individually. If there are any communications functions happenning in the app where the HOSTS or SERVICES files are referenced (TCP/IP), these will also have to be updated as they reside in a different directory for w2k/nt, as do other files that would normally reside in the WINDOWS and WINDOWS\SYSTEM directories.

I hope I have been somewhat helpful since I didn't go into a terrible amount of detail.

Dave.
 
I was running a database application designed in foxpro2.6
successfully for a month but now I am in trouble.
The program crashes and gives the following error
"Pharlap fatal sys err10025 :Unexpected processor Exception.
I reinstalled Windows2000 Professional but to no avail
I again get same message.Other applications and Operating
system is running fine only this program crashes.What
could be the problem.
 
Hopefully I'm not just asking the obvious, but if it ran "successfully for a month", what changed? Did you install or update any other applications (including virus checkers)? Did you add or delete a "lot" of data to your FP tables?

As stated before, not all DOS programs work well under Win2000 - remember it like NT doesn't actually run DOS, but rather a DOS emulator. Since the Pharlap code was used in memory management, are you running more (or different) applications now than before? Do you fire up this program through a PIF, BAT file or just a "standard" shortcut? What memory settings do you use for it? Have you got any memory settings in your CONFIG.FP file?

Rick

 
A lot of times, a corrupt index file will cause memory errors/GPF's too. Make sure your data is good (no garbage in the fields like invalid data and ascii characters that don't belong) and rebuild your indexes from scratch if you haven't already. By rebuild from scratch I mean delete the index files (.IDX and/or .CDX), and index them again using:

INDEX ON some_key TAG some_tag

Don't just do a REINDEX command on the tables as this does not always recreate the index header properly. A bad key could still be in the index file and will generate a bad index accordingly.

Note: Be sure and note all the keys and tags in you index before deleting them.

Dave S.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top