Compiling the Packet Driver


The Packet Driver is platform dependent, therefore it MUST be compiled on the platform where you intend to use it.


Compiling on Windows NT 4.0

Software requirements:

If your system satisfies the requirements, follow these steps:

  1. From the Window NT Start menu, select the folder Programs and then Windows NT DDK. From here select the voice Checked Build Environment if you want to build a debug version, or Free Build Environment if you want to build a release version.
  2. A DOS shell will be opened. Move to the directory whit the driver's source code and type the command

    compile

    This command will generate the driver (packet.sys). The debug version of the files will be generated in the directory \i386\checked. The release version in \i386\free.
  3. To compile the sources of packet.dll, load the project contained in the directory packetNT\dll\project in the Visual C++ 6.0 IDE. Build the project to obtain the packet.dll and packet.lib files. The debug version of these files will be generated in the directory packetNT\dll\project\debug, the release version in packetNT\dll\project\release.

Windows 95/98 platform

To compile the driver there are the following software requirements:

If your system satisfies the requirements, follow these steps:

  1. Open a dos shell
  2. Go in the VisualC++ BIN directory (for example C:\DEVSTUDIO\VC\BIN) and execute the command

    Vcvars32
  3. Go in the SDK directory (for example C:\MSSDK) and execute the command

    Setenv sdk_path

    where sdk_path is the directory of SDK (for example Setenv C:\MSSDK)
  4. Go in the DDK directory (for example C:\DDK) and execute the command

    Ddkenv 32 net
  5. Move to the directory whit the driver's source code and type the command

    nmake rtl

    to obtain a release version, or

    nmake

    to obtain a debug version.
    The release version of packet.vxd will be placed in the retail directory, the debug version in the debug directory.

Warning: we often encountered problems compiling the driver for Windows 95. In particular on some systems the NMAKE utility was not able to launch ADRC2VXD (the driver is generated without the copyright informations), and on other systems the debug version was not compiled correctly. We don't know the cause of these problems.