How to build Encryption for the Masses - A Developers Guide

Paul Le Roux
19 June 1999

Table of Contents

Copyright (C) 1998-99 Paul Le Roux. All Rights Reserved.

1. Introduction

Welcome to the source distribution of E4M. This document briefly describes how to build E4M.

Firstly E4M does not use the build tool supplied by Microsoft in the NT DDK.

E4M uses normal makefiles to build everything.

Extract the files from the zip archive, with "use directories" set on. The source zip contains long names so don't use an older pkunzip.

For the rest of this document I will assume you installed it into "C:\e4m", but this can be any directory. If you pick another directory just replace "C:\e4m" in the documentation with whatever you like.

2. What you will need

  1. A compiler, which can be VC4.x, VC5.0, VC6.0 or later
  2. The NT DDK

3. Setup the DDK path

In the device drivers makefile, change the variable DDK to the full path of your ddk directory, normally c:\ddk

3.1. If you plan to debug the driver

If you plan to debug the product you will need:

  1. Two computers and a serial cable (laplink cable)
  2. The Win32 SDK, or WinDbg alone, which can be downloaded from Microsoft
  3. The checked build of Widows NT installed on the second computer

3.2. If you want to modify the help files

  1. SDF http://www.mincom.com/mtr/sdf/resources/index.html
  2. any text editor
  3. any Microsoft help compiler

3.3. If you want to modify the setup program

  1. InstallShield 5.0 professional or the "Free" Edition which comes with Visual C++.
  2. PackageForTheWeb which creates self extracting archives for distribution.

Note: The Debug format changed between VC4.x and VC5.0. To debug using VC5.0 or later you must download a new WinDbg from Microsoft. With an older VC4.x, try the WinDbg from an old Win32 SDK CD.

Enjoy,

Paul Le Roux paulca@rocketmail.com

4. Verifying that you have genuine source code

Follow the instructions given in the E4M help file or in the online documentation for verifying the main program.

5. Building the driver

  1. open up a DOS prompt
  2. change to the C: drive
  3. cd to c:\e4m\ntdriver
  4. run "c:\progra~1\devstudio\vc\bin\vcvars32.bat" or "vcvars32 x86" for VC4.x this sets up the search path's for your compiler
  5. run "nmake" or "nmake RELEASE=1"

You should end up with e4mnt4.sys in the ntdriver directory.

6. Setting up the registry entries for the driver

Don't try this by hand, just install the driver from the binary distribution, then overwrite it with the rebuilt driver.

7. Building volmount, voltest etc

  1. open up a DOS prompt
  2. change to the C: drive
  3. cd to c:\e4m\volmount, volformat etc
  4. run "c:\progra~1\devstudio\vc\bin\vcvars32.bat" or "vcvars32 x86"
  5. run "nmake" or "nmake RELEASE=1"