4.2 WinDriver Installation Process

4.2 WinDriver Installation Process
	Chapter 4. Installing WinDriver

The WinDriver CD contains all versions of WinDriver for the supported operating systems. The CD's root directory contains the Windows 7 / Vista / Server 2008 / Server 2003 / XP / 2000 version. The installation of this version will begin automatically when you insert the CD into the CD drive on your Windows development machine. The other versions of WinDriver are located in <OS> sub-directories (for example: Linux; Wince).

4.2.1 Windows WinDriver Installation Instructions


	Driver installation on Windows requires administrator privileges.

Insert the WinDriver CD into your CD-ROM drive, or double-click the downloaded installation file – WD1020.EXE – and follow the installation instructions.


	When using the installation CD, wait a few seconds for the installation to begin automatically. If this does not happen, double-click the file WD1020.EXE in the CD, and click the Install WinDriver button.

At the end of the installation, you may be prompted to reboot your computer.

The WinDriver installation defines a WD_BASEDIR environment variable, which is set to point to the location of your WinDriver directory, as selected during the installation. This variable is used during the DriverWizard [5] code generation – it determines the default directory for saving your generated code and is used in the include paths of the generated project/make files.
If the installation fails with an ERROR_FILE_NOT_FOUND error, inspect the Windows registry to see if the RunOnce key exists in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion. This registry key is required by Windows Plug-and-Play in order to properly install drivers using INF files. If the RunOnce key is missing, create it; then try installing the INF file again.

The following steps are for registered users only:

To register your copy of WinDriver with the license you received from Jungo, follow these steps:

Start DriverWizard: Start | Programs | WinDriver | DriverWizard.
Select the Register WinDriver option from the File menu, and insert the license string you received from Jungo.
Click the Activate License button.
To register source code that you developed during the evaluation period, refer to the documentation of WDU_Init() [B.4.1].

4.2.2 Windows CE WinDriver Installation Instructions

4.2.2.1 Installing WinDriver CE when Building New CE-Based Platforms

The following instructions apply to platform developers who build Windows CE kernel images using Windows CE Platform Builder or using MSDEV 2005/2008 with the Windows CE 6.0 plugin. The instructions use the notation 'Windows CE IDE' to refer to either of these platforms.
We recommend that you read Microsoft's documentation and understand the Windows CE and device driver integration procedure before you perform the installation.

Modify the project registry file to add an entry for your target device:
- If you select to use the WinDriver component (refer to step 2), modify WinDriver\samples\wince_install\<TARGET_CPU>\WinDriver.reg (e.g., WinDriver\samples\wince_install\ARMV4I\WinDriver.reg).
- Otherwise, modify WinDriver\samples\wince_install\project_wd.reg.
You can simplify the driver integration into your Windows CE platform by following the procedure described in this step before the Sysgen platform compilation stage.
Note:
- The procedure described in this step is relevant only for developers who use Windows CE 4.x-5.x with Platform Builder.
  Developers who use Windows CE 6.x with MSDEV 2005/2008 should skip to the next step (refer to step 3).
- This procedure provides a convenient method for integrating WinDriver into your Windows CE platform. If you select not to use this method, you will need to perform the manual integration steps described in step 4 below, after the Sysgen stage.
- The procedure described in this step also adds the WinDriver kernel module (windrvr6.dll) to your OS image. This is a necessary step if you want the WinDriver CE kernel file (windrvr6.dll) to be a permanent part of the Windows CE image (NK.BIN), which is the case if you select to transfer the file to your target platform using a floppy disk. However, if you prefer to have the file windrvr6.dll loaded on demand via the CESH/PPSH services, you need to perform the manual integration method described in step 4 instead of performing the procedure described in the present step.
1. Run the Windows CE IDE and open your platform.
2. From the File menu select Manage Catalog Items.... and then click the Import... button and select the WinDriver.cec file from the relevant WinDriver\samples\wince_install\<TARGET_CPU> directory (e.g., WinDriver\samples\wince_install\ARMV4I). This will add a WinDriver component to the Platform Builder Catalog.
3. In the Catalog view, right-click the mouse on the WinDriver Component node in the Third Party tree and select Add to OS design.
Compile your Windows CE platform (Sysgen stage).
If you did not perform the procedure described in step 2 above, perform the following steps after the Sysgen stage in order to manually integrate the driver into your platform. Note: If you followed the procedure described in step 2, skip this step and go directly to step 5.
1. Run the Windows CE IDE and open your platform.
2. Select Open Release Directory from the Build menu.
3. Copy the WinDriver CE kernel file – WinDriver\redist\<TARGET_CPU\windrvr6.dll – to the %_FLATRELEASEDIR% sub-directory on the target development platform (should be the current directory in the new command window).
4. Append the contents of the project_wd.reg file in the WinDriver\samples\wince_install directory to the project.reg file in the %_FLATRELEASEDIR% sub-directory.
5. Append the contents of the project_wd.bib file in the WinDriver\samples\wince_install directory to the project.bib file in the %_FLATRELEASEDIR% sub-directory.
  This step is only necessary if you want the WinDriver CE kernel file (windrvr6.dll) to be a permanent part of the Windows CE image (NK.BIN), which is the case if you select to transfer the file to your target platform using a floppy disk. If you prefer to have the file windrvr6.dll loaded on demand via the CESH/PPSH services, you do not need to carry out this step until you build a permanent kernel.
Select Make Run-Time Image from the Build menu and name the new image NK.BIN.
Download your new kernel to the target platform and initialize it either by selecting Download/Initialize from the Target menu or by using a floppy disk.
Restart your target CE platform. The WinDriver CE kernel will automatically load.
Compile and run the sample programs to make sure that WinDriver CE is loaded and is functioning correctly (see section 4.4.2, which describes how to check your installation).

4.2.2.2 Installing WinDriver CE when Developing Applications for Windows CE Computers


	Unless otherwise specified, 'Windows CE' references in this section include all supported Windows CE platforms, including Windows Mobile.

The following instructions apply to driver developers who do not build the Windows CE kernel, but only download their drivers, built using Microsoft eMbedded Visual C++ (Windows CE 4.x – 5.x) or MSDEV .NET 2005/2008 (Windows Mobile or Windows CE 6.x) to a ready-made Windows CE platform:

Insert the WinDriver CD into your Windows host CD drive.
Exit the automatic installation.
Copy WinDriver's kernel module – windrvr6.dll – from the WinDriver\redist\WINCE\<TARGET_CPU> directory on the Windows host development PC to the Windows directory on your target Windows CE platform.
Add WinDriver to the list of device drivers Windows CE loads on boot:
- Modify the registry according to the entries documented in the file WinDriver\samples\wince_install\project_wd.reg. This can be done using the Windows CE Pocket Registry Editor on the hand-held CE computer or by using the Remote CE Registry Editor Tool supplied with MS eMbedded Visual C++ (Windows CE 4.x – 5.x) / MSDEV .NET 2005/2008 (Windows Mobile or Windows CE 6.x). Note that in order to use the Remote CE Registry Editor tool you will need to have Windows CE Services installed on your Windows host platform.
- On Windows Mobile the operating system's security scheme prevents the loading of unsigned drivers at boot time, therefore the WinDriver kernel module has to be reloaded after boot. To load WinDriver on the target Windows Mobile platform every time the OS is started, copy the WinDriver\redist\Windows_Mobile_5_ARMV4I\wdreg.exe utility to the Windows\StartUp directory on the target PC.
Restart your target CE computer. The WinDriver CE kernel will automatically load. You will have to do a warm reset rather than just suspend/resume (use the reset or power button on your target CE computer).
Compile and run the sample programs to make sure that WinDriver CE is loaded and is functioning correctly (see section 4.4, which describes how to check your installation).

4.2.2.3 Windows CE Installation Note

The WinDriver installation on the host Windows 7 / Vista / Server 2008 / Server 2003 / XP / 2000 PC defines a WD_BASEDIR environment variable, which is set to point to the location of your WinDriver directory, as selected during the installation. This variable is used during the DriverWizard [5] code generation – it determines the default directory for saving your generated code and is used in the include paths of the generated project/make files.

Note that if you install the WinDriver Windows 7 / Vista / Server 2008 / Server 2003 / XP / 2000 toolkit on the same host PC, the installation will override the value of the WD_BASEDIR variable from the Windows CE installation.

4.2.3 Linux WinDriver Installation Instructions

4.2.3.1 Preparing the System for Installation

In Linux, kernel modules must be compiled with the same header files that the kernel itself was compiled with. Since WinDriver installs kernel modules, it must compile with the header files of the Linux kernel during the installation process.

Therefore, before you install WinDriver for Linux, verify that the Linux source code and the file versions.h are installed on your machine:

Install the Linux kernel source code:

If you have yet to install Linux, install it, including the kernel source code, by following the instructions for your Linux distribution.
If Linux is already installed on your machine, check whether the Linux source code was installed. You can do this by looking for 'linux' in the /usr/src directory. If the source code is not installed, either install it, or reinstall Linux with the source code, by following the instructions for your Linux distribution.

Install version.h:

The file version.h is created when you first compile the Linux kernel source code. Some distributions provide a compiled kernel without the file version.h. Look under /usr/src/linux/include/linux to see if you have this file. If you do not, please follow these steps:
1. Become super user:
  $ su
2. Change directory to the Linux source directory:
  # cd /usr/src/linux
3. Type:
  # make xconfig
4. Save the configuration by choosing Save and Exit.
5. Type:
  # make dep

To run GUI WinDriver applications (e.g., DriverWizard [5]; Debug Monitor [7.2]) you must also have version 5.0 of the libstdc++ library – libstdc++.so.5. If you do not have this file, install it from the relevant RPM in your Linux distribution (e.g., compat-libstdc++).

Before proceeding with the installation, you must also make sure that you have a linux symbolic link. If you do not, create one by typing
/usr/src$ ln -s <target kernel>/linux
For example, for the Linux 2.4 kernel type
/usr/src$ ln -s linux-2.4/ linux

4.2.3.2 Installation

Insert the WinDriver CD into your Linux machine's CD drive or copy the downloaded file to your preferred directory.
Change directory to your preferred installation directory, for example to your home directory:
$ cd ~
Extract the WinDriver distribution file – WD1020LN.tgz:
$ tar xvzf /<file location>/WD1020LN.tgz
For example:
- From a CD:
  $ tar xvzf /mnt/cdrom/LINUX/WD1020LN.tgz
- From a downloaded file:
  $ tar xvzf /home/username/WD1020LN.tgz
Change directory to your WinDriver redist directory (the tar automatically creates a WinDriver directory):
$ cd <WinDriver directory path>/redist

Install WinDriver:

<WinDriver directory>/redist$

./configure

The configure script creates a makefile based on your specific running kernel. You may run the configure script based on another kernel source you have installed, by adding the flag --with-kernel-source=<path> to the configure script. The <path> is the full path to the kernel source directory, e.g., /usr/src/linux.
If the Linux kernel is version 2.6.26 or higher, configure generates makefiles that use kbuild to compile the kernel modules. You can force the use of kbuild on earlier versions of Linux, by passing the --enable-kbuild flag to configure.

<WinDriver directory>/redist$ make
Become super user:
<WinDriver directory>/redist$ su
Install the driver:
<WinDriver directory>/redist# make install

Create a symbolic link so that you can easily launch the DriverWizard GUI:
$ ln -s <path to WinDriver>/wizard/wdwizard/ usr/bin/wdwizard
Change the read and execute permissions on the file wdwizard so that ordinary users can access this program.
Change the user and group IDs and give read/write permissions to the device file /dev/windrvr6 depending on how you wish to allow users to access hardware through the device. If you are using a Linux 2.6.x kernel that has the udev file system, change the permissions by modifying your /etc/udev/permissions.d/50-udev.permissions file. For example, add the following line to provide read and write permissions:
windrvr6:root:root:0666 Otherwise, use the chmod command, for example:
chmod 666 /dev/windrvr6
Define a new WD_BASEDIR environment variable and set it to point to the location of your WinDriver directory, as selected during the installation. This variable is used in the make and source files of the WinDriver samples and generated DriverWizard [5] code, and is also used to determine the default directory for saving your generated DriverWizard projects. If you do not define this variable you will be instructed to do so when attempting to build the sample/generated code using the WinDriver makefiles.
You can now start using WinDriver to access your hardware and generate your driver code!


	Use the WinDriver/util/wdreg script to load the WinDriver kernel module [10.3].

The following steps are for registered users only:

To register your copy of WinDriver with the license you received from Jungo, follow these steps:

Start DriverWizard:
$ <path to WinDriver>/wizard/wdwizard
Select the Register WinDriver option from the File menu, and insert the license string you received from Jungo.
Click the Activate License button.
To register source code that you developed during the evaluation period, refer to the documentation of WDU_Init() [B.4.1].

4.2.3.3 Restricting Hardware Access on Linux

Since /dev/windrvr6 gives direct hardware access to user programs, it may compromise kernel stability on multi-user Linux systems. Please restrict access to DriverWizard and the device file /dev/windrvr6 to trusted users.

For security reasons the WinDriver installation script does not automatically perform the steps of changing the permissions on /dev/windrvr6 and the DriverWizard application (wdwizard).


Chapter 4. Installing WinDriver		4.3 Upgrading Your Installation