Barry Gershenfeld wrote:

> MCP? MCW? They changed it?

They confused it... :)

MPLAB has settings in (at least) three places (would be good if there were
a complete list somewhere):

- Application settings (common to all projects and workspaces)
These are for example the ICD2 settings (I think), the editor settings, the
recently loaded files lists. 

- Workspace settings (common to all projects loaded into that workspace)
These are for example the chip model and configuration.

- Project settings (only for this one project)
These are the project files and possibly the compiler settings (I don't
build through MPLAB, so I don't really know that much here).

Anyway, whenever you load a project, MPLAB runs within a workspace. It can
be the default (then you never really know what workspace settings you
have, other than that they probably are the ones that were loaded last), or
it can be a specific one that you created by saving it with a specific name
in a specific location. Which is probably the sensible thing to do. Then
you have at least the chip configuration stored in that workspace file, and
you know that it's the right one. 

That's probably why Olin loads workspace files -- that's where the
important stuff like the chip type is stored. Doesn't help you to load a
project file for a 16F666 into the default workspace where you have the
chip set to an 18F888 :)

It's probably helpful to keep in mind that settings get stored in (at
least) these three different places, even if you don't know exactly which
one gets stored where. And as a matter of rule, I think it's best to only
load workspace files. They then load automatically the project files that
are linked to them.

Workspace files are the .mcw files, project files are the .mcp files.

Gerhard

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist