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

VFP3.0 running on windows XP having problem. 3

Status
Not open for further replies.

so180500

IS-IT--Management
Sep 24, 2001
9
SG
I have this problem of using an old VFP 3.0 program (*.exe) install and run in Windows XP. This exe has been running in the Window 95/98. NO problem at all. When i install and run it from XP, there is an error msg that says 'insufficient memory'. Why is that so?. Pls help..... your input will be much appreciated. Thanksss.

p/s: Could it be that XP does not support old VFP program?
 
What else is different about the PC that this app is running on besides the XP OS?

Here's a link from another forum where they are talking about it happening on a 1.8 ghz computer VFP 3 app ->


Wish I had a better answer for you, my only experience with the error you are seeing was back in the Foxprow 2.6 days. Slighthaze = NULL
 
Thanks for that BUT it seems that it still does not work. Most of the solutions are actually meant for NT and 98 but not XP. I will continue to search.. Hopefully i will be able to slove it. Anyway thanks....
 
Hi

you can make it works, if the RAM is 256MB, if it's exceeds 256MB you will get this insufficient message.

reduce the memory in your boot.ini file.

Before Change
==============
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
C:\="Previous Operating System on C:"
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional"
/fastdetect /KERNEL=LOGOOS.EXE



After Change
============

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
C:\="Previous Operating System on C:"
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional"
/fastdetect /KERNEL=LOGOOS.EXE
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional
For VFP" /fastdetect /KERNEL=LOGOOS.EXE /MAXMEM=256
 
Hi saleem123,

Thanks for your msg. I have one stupid question to ask you. I could not find the boot.ini file. Where is that located? I have searched everywhere. Pls let me know. Thanks


 
BOOT.INI is in your main boot directory - usually C:\. It is a Hidden file, so if your Explore isn't optioned to show Hidden / System files, you won't see.

Be VERY careful changing this file - especially if that drive is formated NTFS - you won't be able to boot properly without it. (If the drive is FAT32, at least you could use a Win98 Boot floppy and edit the file - this is NOT an option with NTFS.

Rick
 
Hi rgbean,

Thanks for that. I have done that, check the hidden files and show all files. Still could not find that file. If i am not mistaken, the boot.ini only occurs in dual-mode. Correct me if i am wrong.

I have searched in Win95 and XP. No such file.

Your input will be much appreciated. Thanks.

Pls help.
 
As far as I know, BOOT.INI is used on all NT/2000/XP machines - single or multiple-boot optioned.

Of course if you use a third party boot manager, then it may be handled by some other mechanism.

Win 9x doesn't have a boot.ini file.

Rick
 
Hi

As far as WIn98 you can type at run "msconfig" then go to advance, limit your memory as 256MB.

NT,XP,2000 you can find the boot.ini file. show all hidden files. before changing the boot.ini file, duplicate the boot.ini file.

Cheers
Saleem
 
One think you may want to check: ( because I had a 'memory' problem with VFP Ver 3) See if the VFP you are using is Ver 3.0 or Ver 3.0B. Version 3.0 had a 'memory leakage' problem that was fixed in the Ver 3.0b upgrade. Check this first, in case you are using the original Ver 3.0, and it may save you a lot of time. If you are on Ver 3.0b, then you know it's not related to the 'memory leakage' problem.

Jack McCarrick
 
Hi Jack,Saleem,Rick.

You guys are the best..

Thanks for your reply, What needs to be done to convert this VFP3.0 to VFP3.0b? DO i need to re-compile all the source codes? Patches? I have applied some patches, does not seems to work.

I am quite new to this VFP thing. By the way, i do not have any source codes to this application. Only the EXE.

I have amended the Boot.ini. About half of the fuctions in the program working well and the other half keep giving me error messages such as 'Not enough memory for this operation'

I have choosen 'IGNORE'to continue. Sometimes it works.

At least, i can see part of my application right now after amended the boot.ini to 256k memory.

Your comments are highly appreciated.

Let me know. Thanks....

samson
 
Samson,
While 3.0b fixed a lot of problems in the original VFP release, it was never available as a download, you could only get it by contacting MS, and after you supplied the appropriate registration key information, they'd send you an update CD for S/H costs (~$10).

However, without the source code, you won't be able to recompile the project to create a 3.0b application. In fact the other (better?) possibility of moving to VFP 5/6/7/8 which don't have these memory limits is also not possible without the source files.

Rick



 
rgbean (Programmer) Feb 7, 2003
Samson,
While 3.0b fixed a lot of problems in the original VFP release, it was never available as a download, you could only get it by contacting MS, and after you supplied the appropriate registration key information, they'd send you an update CD for S/H costs (~$10).

However, without the source code, you won't be able to recompile the project to create a 3.0b application. In fact the other (better?) possibility of moving to VFP 5/6/7/8 which don't have these memory limits is also not possible without the source files.

Rick


Rick is absolutely right, Samson! Even if you upgrade to the VFP 6.0 SP5 (skip the 5.0, it's buggy) or 7.0 (also ain't bug-free yet) you would need the source code.
But I happen to know the solution for this problem: ReFox.
Try These guys built de-compiler for all Fox versions from FoxBASE+ and FoxPro 2.x to VFP 6.0 (as for ReFox ver. 8.0 I have in my possession). One thing, though: their sale is final, you can't return it and get your money back.

HTH.

Regards,

Ilya
 
Ilya,
Of course this does assume that Samson has the "rights" to that source code. If the products was bought without these express rights, it might be illegal in many juristrictions! Of course I know you weren't encouraging the use of a product to "pirate" any source code!

Rick
 
Ilya,
Of course this does assume that Samson has the "rights" to that source code. If the products was bought without these express rights, it might be illegal in many juristrictions! Of course I know you weren't encouraging the use of a product to "pirate" any source code!

Rick


Rick, I was actually referencing to the ReFox itself. It's part of the license agreement with Xi-Tech when you buy their product. And that's absolutely rightful requirement, considering the nature of the tool.

To make it short, we bought first FoxFix (database repair tool) - and it worked perfectly, and then we went ahead and bought their ReFox - also excellent tool![thumbsup]

So, Samson may consider having his company buying ReFox, run that old VFP 3.0 program trough it, and then recompile it in VFP 6.0. That was my suggestion, actually.

Regards,

Ilya
 
Thanks guys...

I will surely check out the decompiler. HOpefully it will bring me forward.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top