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

FoxPro 2.0 runtime will not open in Win XP Pro

Status
Not open for further replies.

GLSwallow

Technical User
Joined
Nov 14, 2003
Messages
4
Location
US
Have been using a runtime version 2.0 for several years under Win95, Win98, and Win98se, that has worked flawlessly until I upgraded to Win XP Pro. It is a standalone application and is located in the same directories and hard drive as before.

When I attempt to run it via a dos window, I get a black screen with nothing but a blinking cursor on it. I have tried disabling all of the I attempted changing the compatibility modes in the CMD(MSDOS) properties window but nothing I do seems to work. I can exit to the cmd prompt and do other doslike functions but not Foxpro.

Suggestions please!
 
How are you running it and exactly what runtime files are you using? I don't believe you can run using extended (XMS) memory or a standalone using the extended memory option. I can run using both standard memory or expanded (EMS) memory.

Rick
 
I meant to include the exe files in this foxpro directory:
************************************************************
fox .exe 9489 14-Nov-03 16:36:10
(fox.exe has today's date because I changed compatibility
settings trying to get it to work. Otherwise, it has a
1991 date like the other files.)
foxr .exe 8993 11-Jul-91 15:50:22
foxl .exe 8993 11-Jul-91 15:50:30
foxunpak.exe 31185 10-Jul-91 11:45:46
foxldr .exe 160924 08-Jul-91 16:20:02
patch .exe 23009 28-Dec-91 20:12:10
foxprol .exe 480119 15-Nov-91 16:15:48
proapi16.exe 13281 11-Jul-91 22:46:24
foxprolx.exe 1728k 15-Nov-91 16:19:18
wlink8 .exe 127530 13-Jun-91 12:00:00
 
I found the problem: the paths to the two directories were deleted during the upgrade. I suspect these 2 paths were just set by the Foxpro program each time it was executed rather than being permanently set in autoexec.bat. When I entered the information in the environment variables section for WinXP, everything returned to normal. Thanks for causing me to continue to look for the problem. Once I knew the program "should" run, it was just a matter of more research til the problem was found.

thank you! thank you!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top