> Howard wrote:
>
> > Interestingly, look at the mcp file in Explorer, it's zero Kb. Refresh
> > once, and it's still zero kB. Refresh again, and lo - it's 1 Kb. Not
> > all the time, mind you, but most of the time.
>
Dennis wrote:
> Yes, the .mcp file generated by mplab has several stages during savings. At
> the very first stage, when a new mcp file is created it look like this:
> (67kb)
> [HEADER]
> magic_cookie={66E99B07-E706-4689-9E80-9B2582898A13}
> fil
>
> After saving the project without close the workspace, it looks like this:
> (517kb)
> magic_cookie={66E99B07-E706-4689-9E80-9B2582898A13}
> file_version=0.9
> [PATH_INFO]
> dir_src=
> dir_out=
> dir_tmp=
> dir_sin=
> dir_inc=
> dir_lib=
> dir_lkr=
> [CAT_FILTERS]
> filter_src=*.asm
> filter_inc=*.h;*.inc
> filter_obj=*.o
> filter_lib=*.lib
> filter_lkr=*.lkr
> [FILE_INFO]
> file_000=96-72.asm
> [SUITE_INFO]
> suite_guid={6B3DAA78-59C1-46DD-B6AA-DBDAE4E06484}
> suite_state=
> [TOOL_SETTINGS]
> TS{DD2213A8-6310-47B1-8376-9430CDFC013F}=
> TS{BFD27FBA-4A02-4C0E-A5E5-B812F3E7707C}=/o"$(TARGETBASE).cof"
>
> In order to rescue a "project" we have to distinguish between Workspace
> file and Project file.
> The project file seems to have the cookie and files paths.
> A possible solution may be:
> 1.- delete the .mcp file
> 2.- open the workspace disregarding the missing file
> 3.- generate another project by clicking Project/new and adding the .asm
> .cod etc files again.
>
> With this method you don't have to re-create, stimulus, debugging
> stopwatch, watch windows, selected device, programmer, debugger tool,
> ufffff, practically all your debugging work.
>
> Regards,
> Dennis.
>

Umm... I don't quite agree with that.
Firstly, yes, the *.mcp file saves as you say, however, on my machine it
never gets above 1kB long.
The *mcw file does though - it is 29Kb on my present project.
Secondly, it's not a short simple matter to setup the project again, I
find that ALL the settings have to be gone through.
Thirdly, why are we doing this?  Why doesn't it work?
I apologise that I don't have the know-how to figure it out, to fix it,
or even to find out what's wrong.  I suspect (note suspect - I really
don't know!) MicroChip is just not saving files as per every other darn
program on the planet.
Surely, if I command  "Save" it should do just that.  And why does the
cookie problem seem to be cropping up so many times, but MicroChip say
they cannot duplicate it.
That's fine, I suppose - bit hard to fix something which they cannot
see, but I assure them the problem is there!
Howard.

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.