Page 1 of 1

File corrupted?

Posted: Mon Jul 23, 2012 5:27 am
by krimles
For the second time my work file seems to have become corrupted and I cannot open it. It's telling me that access was denied.
I am running on Win XP. Both times the hour glass was running and the program locked up. I had to do a CTRL-ALT-DEL to unlock my PC. Is there any way to open the file - I never printed out my work and I fear that all my work is lost. I have looked over the forum but cannot see a way to recover this.

Re: File corrupted?

Posted: Mon Jul 23, 2012 5:45 am
by krimles
UPDATE: my file that I could not access is emcon4.fcf

I was able to recover my work by renaming the emcon4.fcf.001 file (some sort of backup in the same directory??) to emcon4.fcf. First I had to rename the corrupted file to something else. I may have pressed a button by mistake to cause the corruption. Has anyone experienced this type of thing before?

Re: File corrupted?

Posted: Mon Jul 23, 2012 6:30 am
by Spanish_dude
Flowcode automatically makes a backup of your file and names it 'something.fcf.001'.
Never had any problems with Flowcode so far.

Nicolas

Re: File corrupted?

Posted: Tue Jul 24, 2012 11:17 am
by Enamul
Hi,
It happened to me couple of times in V5 (maximum 2/3 times in v4 ) that FC crashes and I have to re-open the FC but it shows error to open which makes me mad :x .

But I have noticed earlier that xx.fcf.001 file in the same directory with the last saved version at least saves most of my valuable work :)
Enamul

Re: File corrupted?

Posted: Thu Jul 26, 2012 4:25 pm
by krimles
I bought a new PC and the corruption seems to have gone away. My old faithful was not up to the job!
When I first connected the PICKit3 to my new PC, it would not communicate with Flowcode even though all the programming parameters were correct.
Someone else on the web offered a good solution to this problem:
Run Microchip MPLAB and connect to the PICKit3 as normal. Close down MPLAB and then run Flowcode. This solves the connection problem. I read this is something to do with how the USB ports enumerate. MPLAB must use a more sophisticated USB program. Anyway it's all working OK now :)