Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Compile problems on new hard drive
Message
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Vista
Miscellaneous
Thread ID:
01311148
Message ID:
01311223
Views:
23
No - the project is entirely .prg files. .fxp file are all generated either during a BUILD EXE or while running interpretively during development.

I have deleted all the fxp's several times. That triggers errors the next time I run.

One odd thing is that when I try to build the executable, it either fails right away or builds successfully. Right now I can't get it to fail at all on the build, but it will occassionaly corrupt the fxp for a .prg I am working on when I go to run it.


>Do you .fxp files in your project that are included or excluded from the project? Are these .prg files or .fxp files?
>
>>I upgraded the hard drive in one of my computers the other day to a Western Digital Caviar SE16 640 GB SATA 3.0Gb/s drive. I am running Vista SP1 and VFP9 SP2. When working with source code on the new hard drive, I am unable to run my applications. It seems that I am having compile problems. The most common error I see is "Cannot compile until the current COMPILE command has completed." VFP will then crash. If I try to run again, I get an error indicating that I have an invalid .fxp file. If I delete the corrupted fxp file, then the problem starts all over again with a different fxp. If I try to build the .exe, it sometimes works and sometimes crashes. If it works then I can delete the executable and go on with development.
>>
>>I go through this scenario everytime I copy a project onto this machine and try to work on it.
>>
>>If I put the code on another hard drive in the machine, everything works fine.
>>
>>I have disabled write caching on the hard drive through the device manager. I have uninstalled VFP9 sp2 and tried with an unpatched version. I have run the Western Digital diagnostics on the drive, and it says everything is fine.
>>
>>Any suggestions? Is this just an incompatible drive? Is it just too fast?
Paul R. Moon
Business Software Solutions
paul@businessoftware.com
Previous
Reply
Map
View

Click here to load this message in the networking platform