=============================================================================Installation and Getting Started=============================================================================INSTALLATION1) Download and install the Pacific C developer kit.You can find everything at http://www.htsoft.com/products/pacific.htmlFollow the included directions.  Be sure to change your PATH environmentvariable to include the bin directory.The linker input files assume that the Pacific C kit is installed inthe \PACIFIC directory of the current drive. (The drive containingall of your UCOS-II files.)  By default, the kit is installed underC:\PACIFIC.  If your UCOS-II files are on a different drive eithermove C:\PACIFIC to the new drive or edit the TEST.LNK files ineach of the example directories.2) Install the port.I've just included the files from the UCOS-II distribution (V2.70) thathad to be changed, so you'll still need to obtain to get the UCOS-II code.I assume that the software is installed in the original\Micrium directory.  Unzip the port from the root directory of the drive containing the\Micrium directory.3) Install the utilities.The DMAKE, RTSETUP and VIDSET utilities are included in PACCUTIL.ZIParchive in the port DOC directory. If you unzip the archive from thedrive root directory the utilities will be placed in the\Micrium\bin directory.4) Set environment variables.Adjust your PATH environment variable to include the compilier andutility bin directories:SET PATH=\PACIFIC\BIN;\MICRIUM\BIN;%path%The DMAKE program, a make program for DOS is included in the PACCUTIL.ZIParchive and should be now be in the \MICRIUM\BIN directory.The DMAKE configuration file is also in \MICRIUM\BIN.Set the MAKESTARTUP environment variable so that it points to the startup.mkfile. See the dmake man page for details.SET MAKESTARTUP=\MICRIUM\BIN\STARTUP.MKSet the RTDEVOS environment variable to either WIN95 (DOS, Win31, Win95,Win98) or WINNT (WinNT, Win2K, WinXP).I find it most convenient to set these in a batch file.  Seethe RTSETUP.BAT section below.4) Test by building the examples.Change directories to then\Micrium\Software\uCOS-II\Ports\80x86\DOS\L\PACC751\AMR\Ex1directory.  Then run the MAKETEST batch program and  the resultingTEST program.  Repeat for the other examples.==================================================================PROBLEMS++++++++++++++++++++++++++++Blank displayIf, when you run TEST, nothing appears to happen, press ESC andrun VIDSET.  Then run TEST again.  I'm not sure why this fixes theproblem, but it works for me.  If you have the same problem I suggestsetting up a shortcut to automatically run VIDSET anytime you opena CMD window.  You can do this by changing the Target of the shortcut to"CMD /K VIDSET" in the CMD Prompt Properties window.  (Alternatively,run VIDSET as described in the next section.)The vidset source code is included in the port DOC subdirectory.The executable is in the Micrium\BIN subdirectory.  You will need the DJGPP C compiler to compile from source.++++++++++++++++++++++++++++File or directory not foundIf under WinNT, Win2K or WinXP you get "file or directory not found"errors when building the examples.  Check to make sure that theAUTOEXEC.NT batch file is not resetting the PATH environment variable.This file can usually be found in the C:\Windows\System32 directory.If the PATH variable is being set/reset either delete the linewhere this occurs or add \PACIFIC\BIN;\Micrium\BIN to the beginning of thelist of directories.++++++++++++++++++++++++++++The system cannot execute the specified program.If you get the above error message when trying to run a 16-bit program thepath to your current directory contains more than 64 characters.This is documented in the Microsoft Knowledge Base in article 241712.This is only a problem for 16-bit programs.  If you get this messageyou will have to use shorter directory names are a shallower path.++++++++++++++++++++++++++++Out of far memory when compiling os_core.cThe compiler seems to choke when compiling os_core.c in certainsituations.  At first I thought this only happened under Windows98, but it has been reported under Windows XP also.  I am notsure why this happens, but I have found a work around.  Itconsists of breaking the initialization of the OSUnMapTbl[] arrayinto separate definition and initialization steps.  Specificinstructions can be found in the OS_CORE.TXT file in the portDOC directory.==================================================================RTSETUPI use a batch file to automatically set all environment variablesand run VIDSET.  The batch file is RTSETUP.BAT and is included inthe BIN directory.  I have a shortcut on my desktop that runs"CMD /K BIN\RTSETUP".  (The startup directory should be C:\Micrium)When I click on the shortcut, I've automatically got a DOS box setupthe way I need it.  The default value of RTDEVOS is WINNT, you mayneed to change it to WIN95.Here are the details for creating the shortcut (WinXP):1) Right click on the Desktop select New -> Shortcut from the menu.2) Enter cmd for the location of the item (or command for Windows 98   and older systems)3) Give the shortcut any name you want.4) Click on the Finish button.5) Right click on the shortcut and select properties.6) Click on the Shortcut tab.7) Change the Target text box to: CMD /K BIN\RTSETUP.BAT8) Change the Start in text box to: C:\Micrium9) Click on the OK button.==================================================================Writing your own programsTo write your own programs I would suggest copying one of the examplesubdirectory trees.You should then only need to create a new TEST.C file in the SOURCEsubdirectory to create a new program.  You will need to modifythe EXDIR variable setting in the maketest.bat file and the BLDIRsetting in clean.bat.  The MAKETEST batch file in the TEST directoryshould still work fine for your new project.Tony Richardson05/09/03richardson@evansville.edu