This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C28EFB.EBD4EA10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit >> Since I only run 98SE on my home machines, I have not yet been able to install the package. << Right. The installer won't work on Win 9x as documented. The limitation is actually in the installer, not the executables. >> I now have W2K on my work machine, but the install was not successful. This is probably related to me not having admin rights. << That would do it. The installer needs to set some global environment variables, which requires admin rights for the registry changes. >> I had hoped to try it at work then do a manual install on Win98SE at home. << This can be done but is tricky. I have documented the procedure for how to do this from a regular installation directory. But most of the releases are self-extracting EXE files because these don't give you as much opportunity to screw up something. If you're really clever, you can run the self-extracting EXE to let it build a release directory, then manually install with the special Win9x directions from wherever the self-extractor put the directory. This directory should stick around as long as the installer is still running. Just let it sit at a prompt. I have attached the documentation file that describes how to do a manual install on Win9x. I'll try to update the web page to add this some time when I have some spare time (yeah, right). >> Also, as I review the files that made it in before the install error, I see some (but not much) reference to the 18F family. As I am committed to these for my project, are they supported in this software environment? << Sorry, not yet. >> (This message was encoded as "Plain Text" when it left this machine. I hope it arrives in a similar format on delivery) << No it didn't, which is why I had to add those annoying ">>" and "<<" to mark blocks of your text. Here are the relevant lines from your header. Note the quoted printable encoding: content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0005_01C28EFB.EBD4EA10 Content-Type: text/plain; name="readme_install.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="readme_install.txt" This file describes how to install software from an Embed Inc software release directory. All Embed Inc software release directories contain the files INSTALL.EXE, RELEASE.INST, and README.TXT, in addition to some other files and directories. If you are installing Embed Inc software from a CD, then the release directory is usually at the top level of the CD. For example, if your CD is drive D, then D:\ will usually be the software release directory. If you received the software as a zip file or self-extracting zip file, then the software release directory is wherever you unzipped the file to. The installation requirements are: Hardware: Standard IBM-compatible PC with Intel 386 or later processor, or equivalent. Operating system: Microsoft Windows 95, 98, ME, NT4, 2000, or XP. To install the software on Windows NT4, 2000, or XP: 1) Make sure you are logged into an account with administrator privileges. If the installation fails with errors like "access denied", then you are not logged in with the necessary privileges. 2) Run INSTALL.EXE in the software release directory and follow the directions. 3) Once the installation is complete, the software release directory is no longer needed. If you installed the software from a removable disk, you can now remove it. If you created the release directory by unzipping a file, you can now delete the whole directory including the zipped file. To install the software on Windows 95, 98, or ME: No automated installation procedure exists for these archaic operating systems. The procedure below assumes you have moderate knowledge of using Windows. There is no "installation for dummies" procedure. If you consider yourself a "dummy", then this software isn't for you until you upgrade to one of the systems listed above (you should anyway). To install the software, follow these steps: 1) Copy the EMBEDINC directory to your hard drive. We normally put it at C:\EMBEDINC, but you can put it anywhere and name it anything you want. However, everything inside the EMBEDINC directory must be copied exactly. If you don't understand what it means to "copy a directory", stop now - this software isn't for you. From now on we will refer to the copy of the EMBEDINC directory on your hard drive as the "EMBEDINC directory". You do not need the original software release directory anymore. 2) Set the environment variable EMBEDINC to the path of the EMBEDINC directory. This can be done by adding the line set embedinc=c:\embedinc to your AUTOEXEC.BAT file. Of course the "c:\embedinc" is replaced by wherever you copied the EMBEDINC directory to in step 1. 3) Add the EMBEDINC\COM directory to the command search path. This is best done by adding the line set path=%embedinc%\com;%path% at the bottom of your AUTOEXEC.BAT file. Note that this only works if this line appears after the line from step 2. 4) Reboot the machine. ------=_NextPart_000_0005_01C28EFB.EBD4EA10-- ***************************************************************** Embed Inc, embedded system specialists in Littleton Massachusetts (978) 742-9014, http://www.embedinc.com -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads