*******************************************************************************
*                    Build Instructions: NT HLC Drivers                       *
*                                                                             *
*                               Date: 9/24/98                                 *
*******************************************************************************

******************
** Requirements **
******************

Required Software:
- Visual C++ 5.0
- Platform SDK (January 1998)
- NT 4.0 DDK
- Visual SourceSafe 5.0

Optional Software
- CVS for Windows NT (used only if updating firmware headers and binaries from CVS)

Machine Setup Requirements:
- VSS (SourceSafe) executables must be in the "path"
- If updating firmware, then CVS binaries must be in the "path"
- If updating firmware, then firmware binaries must be accessible (\\phoenix\html)
- VSS database must be accessible (\\fs1\eng\vss)
- ExportMakefile macro must be installed in VC++ (see instructions below)


Installing ExportMakefile macro:
-------------------------------
1.  Copy the expmake.dsm file to %MsDevDir%\Macros.
2.  Start MSVC.
3.  In the Tools menu, select Customize and go to the "Add-ins and Macro Files"
    tab.
4.  Load the expmak.dsm macro file by selecting the checkbox next to its name 
    and then click Close.
5.  Test it:
    - In the Tools menu, select Macro
	 - In the Macro File field, select expmake
	 - In the Macro Name field, select ExpMakeTest
	 - Press the Run button
	 - MSVC should exit

Updating HLC firmware header files and binaries:
------------------------------------------------
Firmware header files are stored in CVS at \\fs1\eng\cvs\Dense.  Firmware binaries are
built daily and stored at \\phoenix\html\fep.  You must specify the exact path to the 
firmware binaries as well as the date/time of headers to "get" from CVS.  This is done by 
running update.cmd.  In some temp directory, type:

	ss get -I- $/WanLinks/Latest/Firmware/Dense  // This "gets" the update.cmd file
	update <firmware_binaries_path> <date_time>  // This "checks in" new firmware files

A few sample update commandlines:

	// Get binaries at fep.19980820-0525\bin, get headers from CVS at 5:24am on 8/13/98
	update \\phoenix\html\fep\fep.19980820-0525\bin -D "8/13/1998 5:24am"

	// Get binaries at fep.19980820-0525\bin, get headers from CVS by tag "Foo"
	update \\phoenix\html\fep\fep.19980820-0525\bin -r Foo


*****************************
** Building the Driver Set **
*****************************

The entire driver set is built from DDK Build Environment windows.  To build a debug
version, build in the "Checked Build Environment".  For a release version, build in 
the "Free Build Environment".

Process:
--------

1.  Edit the readme.txt file, adding release notes as appropriate.  It's stored in VSS
at $/WanLinks/Latest/Docs/readme.txt.  BE SURE TO CHECK IT BACK IN BEFORE CONTINUING.

2.  [OPTIONAL].  Update HLC firmware header files and binaries.  See above.

3.  "Get" the root files from SourceSafe.  Only need to get the root files, located in
$/WanLinks/Latest.  All other files are pulled automatically by makerelease.  In a 
build window, type:

        ss get $/WanLinks/Latest -I-

4.  Run the MakeRelease command file.  This builds everything and puts the output 
files in the .\bin\checked or .\bin\free directory.  MakeRelease can tag the files in
VSS for this build using an optional commandline parameter.  To build with no tag, 
type:

        makerelease

To build with a tag, type:

        makerelease "My Tag Identifying this Build"

5.  Build the distribution release disk images by running the MakeDisks command file.
This copies files from the .\bin\* directories into a .\Disks subdirectory.
