FoxPro 2.6a will not start on Windows XP

[PatrickvO]

I have read many of the Tek-Tips on this matter, but none helped me, thus I'm starting this new thread.

I'm testing all our application to see if we could convert to XP. My test machine, a 1.5 GHz Systemax, is similar to other existing Win 98 machines on which the following works fine, after we applied the patch26.exe (divide by zero).

Day 1 AM:
My FoxPro 2.6 development (both Win and Dos) ran with no problems or need of adjustments. Then I went on to test some applications (SBT, Ultipro, and in house written stuff).
Most apps use the foxw2600.esl from a shared folder, and after adapting the PATH, I was able to run several apps.
Day 1 PM:
I can't recall doing any major changes, but later in the afternoon, none of my Win FoxPro 2.6 apps or FoxPro 2.6 development worked anymore.
When launching the foxprow.exe or any app using the foxw2600.esl, I'll briefly see the fox splash screen and then nothing.
All the DOS stuff still works fine.

Any suggetsions why the Win FoxPro stopped working, or how can slow dow the startup/ending process to see if any messages appeared ?

Thanks,

Patrick

 

[rgbean]

Have you checked the XP event log to see if any system / security / application errors were logged? While I occassionally experience "hangs" on FPD apps/development, under XP, I've seen no problems with FPW 2.6a. I'm running a dual processor 2 gHz Xeon workstation running XP Pro since last October.

Rick

 

[PatrickvO]

I have verified all 3 event logs, and it seems that no event point out a reason on why I only see the Fox splash screen.

We have a 2nd XP OS machine (1.2 GHz and 1 GB), and using that one, I can execute the foxprow.exe and apps. using the foxw2600.esl. I'll see with the other technician where our difference lay.

Any more suggestions are always welcome,

Patrick

 

[rgbean]

Patrick,
You may want to check your CONFIG.FPW for a MEMLIMIT line. I use:
MEMLIMIT = 60, 2048, 16384

I believe FPW can't really use more than 16MB and since it may try to grab all it can find without this limitation, it may be "choking" on too much memory.

Rick

 

[awaresoft]

Patrick,

Perhaps your Path is pointing to a non-patched version of Foxw2600.esl?

I would search my hard drive for all *.esl files and make sure that all your *.esl files have been patched.

Goodluck!
Malcolm

 

[GemWarner]

Check your 'compatibility' option for your applications under the shortcut's properties, for some reason turning it on causes fox to stop running on my machine, not sure why.

Please reply if this helps.

Gem