About a month ago I started getting errors when I started Logic 0 (I think about .50, but cannot check); this is also about the time I started using an instant backup program to copies files to an archive. The problems could be related, or might not; I do not know.

I am running Windows XP SP 02 with SP3. My logic.exe file is 1240kB dated 1/2/2013 10:12 AM.

At present, when I double click on the Logic icon, nothing happens. If I go to Prgram Files\Logic, right click Logic.exe, then I get an error: c:\program files\logic.exe c:\Docume~1\.............\Locals~1\Temp\VFP$2398_0292BEED.tmp FFFFFFFF - 5 - 1256, followed by another nearly identical error wih the file name ...BEEE.tmp with the same trailing characters. Then I get an error that may get close to the real problem, "Visual FoxPro cannot start. Cannot create program workspace temp files.

I changed the file permissions on the temp space to allow writes (supposed to be that way anyway). When I ran again I got similar errors.

The config.fpw includes progwok=TMP, editwork=TMP, and sortwork=TMP. I have not tried changing TMP to TEMP in this file.

Sure would like to get Logic working again and tackle a couple of radio interface issues. I really like the software, especially the flexibility.

I also notice that I have a VFP8err.log file, and can send that if it helps figure out this problem.

Update on the failure to start Logic problem. I changed nothing on my system. Before I started Logic, I STOPPEd by instant backup program. (It has a timer, so will restart after some time.) I was able to successfully start Logic, download QSLs from LoTW, and update QSL status. This leads me to believe the instant backup program is the root cause of my trouble. I will work on replacing the backup program with something smarter that does NOT interfere with my other software and computer operations.

I appreciate the quick answers and suggestions. I checked the items you suggested and found them as they should be, which leads me to a stronger conclusion the instant backup program is the cause of the problem.

I did not reload the software (still an option) because I temporarily misfiled the CD. It will turn up and be refiled in the correct findable location.