In regards to saving projects and such, I ran into some more MPLAB 3.09
GPFs.  As I was working with incremental versions of programs, I ran into
the following problems:

1.  While I could assemble the incremental programs, I could not use them as
Simulator Source.  The first program in the Project was continually used.
(I confirmed this by looking at the Program Memory.

2.  When I tried to use the Programmer (PICStart Plus), with an incremental
program, the only program loaded in was the first one in the Project (I
confirmed this by the checksum to be burned into IDLOCS).

This is when things began to get weird.  Somehow, the programmer was given
the device type of "16C54" (I was using a 16C84).

3.  Coming out of the Programmer caused a General Protection Fault in this
case and each and everytime I did it, until I changed the device type to a
16C84.

4.  After this, I started getting GPFs when I tried to load in the project
that had the source file code.  Looking at the files, the .pjt looked okay,
but the .cfg was 0 bytes long.

To fix the GPFs, I deleted the errant .pjt and .cfg (and the watch file
".wat") and created a new project for the first program and then a new
project for each subsequent program.  After working this way, no more problems.

Myke
>In article <31BBEEE0.9BF@ipserv.ffo.fgan.de>, Wolfram Liebchen
><liebchen@IPSERV.FFO.FGAN.DE> writes
>>Hi fellow PICers:
>>
>>I have a strange problem with MPLAB 3.09:
>>When I "save project", then all child windows get closed. That was
>>not true with version 2.99 .
>>Must that be?
>
>Fortunately re-opening the project brings them all back where they were.
>God knows why they get closed in the first place.
>
>On a similar note - any way of persuading MPLAB to use long Win95
>filenames ?
>
>Karel
>--
>++++++++khladky@khdesign.demon.co.uk++Manchester M14 6BF England++++++++
>
>
Myke

"We're Starfleet officers, weird is part of the job."

Capt. Catherine Janeway