> Olin - your directions for installing PICDEV were extremely clear and very
> easy to follow.  Thanks for making it so easy!  Guess what I get to play
> with this weekend!

Thanks, it's really not hard as long as you are willing to *read* the
directions.  Unfortunately too many people don't.

Let me know how you make out with the stuff.

> I also installed the project files as well: HAL, HOS, Chess and Wave but
> I'm not sure that my assumptions were valid.  The install packages had the
> same directory structure as the main dev package so I assumed that they
all
> installed in the same directories.  In the case of duplicate file names, I
> kept the files with the most recent date.  It looks as if only one of
those
> has changed: the PICDEV package contained a larger version of
> "file.msg".  Since it was also the most recent file date, I just kept it.

That was the right thing to do.  Click on the "CLICK HERE for directions on
how to install a software release" link at the top of the page you
downloaded the software from.  It explains how to install multiple releases
and demystifies the directory structure.  Multiple releases must be
installed in oldest to newest order.  Note that dates are given for all
software releases, partly for that purpose.

> However, I'm not convinced that I made the right choice.  Should I have
> created separate child sub-directories off of SOURCE for each project?  In
> other words, should I have created a directory called
> 'c:\embedinc\source\hal' for the HAL source files?  Right now, all the
> source code files are in a directory called 'c:\embedinc\source\pics'.

Embed Inc software all lives in one tree.  Each release contains whatever
subset of that tree it needs.  You can name the whole embedinc directory
whatever you want and place it wherever you want, but don't rename or move
around anything inside that tree.  A bunch of generic projects live in the
PICS source directory, including the HAL and HOS projects.  The PICS
directory is sortof my generic PIC play area.  It contains stuff I'm usually
willing to give out.  Real projects live in other diretories that aren't on
any of the releases or course.

The BUILD_HAL_EXPIC and BUILD_HOS_EXPIC scripts, for example, assume that
these projects are in the PICS directory.  Again, see
http://www.embedinc.com/swdload.htm.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

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