1. An x86 processor
   
2. Any 32-bit development environment supporting C, Visual Basic or Delphi.
   

1. An x86 processor.
   
2. Any 32-bit development environment supporting C, VB or Delphi.
   
3. Windows NT: Service Pack 3 or higher (Service Pack 6 is recommended).
   

1. Insert the WinDriver CD into your CD-ROM drive.
   (When installing WinDriver by downloading it from Jungo's web site instead of using the WinDriver CD, double click the downloaded WinDriver file (WDxxx.EXE) in your download directory, and go to step 3).
   
2. Wait a few seconds until the installation program starts automatically. If for some reason it does not start automatically, double-click the file Wdxxx.EXE (where xxx is the version number) and click the Install WinDriver button.
   
3. Read the license agreement carefully, and click Yes if you accept its terms.
   
4. Choose the destination location in which to install WinDriver.
5. In the Setup Type screen, choose one of the following:
   
   
   • Typical - to install all WinDriver modules. (Generic WinDriver toolkit + specific chipset APIs).
   • Compact - to install only the generic WinDriver toolkit.
   • Custom - to choose which modules of WinDriver to install; You may choose which APIs will be installed.
     
6. After the installer completes copying all the required files, chose whether to view the quick-start guides.
   
7. You will be prompted to reboot your computer.

In order to register your copy of WinDriver with the license you have received from Jungo, please follow the steps bellow:

1. Activate DriverWizard GUI (Start | Programs | WinDriver | DriverWizard).
   
2. Select the Register WinDriver option from the File menu and insert the license string you received from Jungo there. Click Activate License button.
   
3. To activate source code you have developed during the evaluation period, please refer to WD_license function refence.

Go back

Back to top

• An x86 Windows CE target platform
  
• Windows NT/2000/XP/Server 2003 host development platform
  
• Microsoft eMbedded Visual C++ with a corresponding target SDK or
  
  Microsoft Platform Builder with corresponding BSP (Board Support Package) for the target platform
  

• Building new CE-based platforms.
  
  This will usually be the case if you are an OEM who ports the Windows CE operating system to his custom hardware using Microsoft Platform Builder (for example, if you are developing a device like a Pocket PC or a Handheld PC).
• Developing applications for Windows CE-based computers.
  
  This will usually be the case if you are an ISV (independent software vendor) who develops applications, using Microsoft eMbedded Visual Tools, targeted to run on CE platforms created by the OEMs.

Installing WinDriver CE when Building New CE-based Platforms:

NOTE:
We recommend that you read Microsoft's documentation and understand the Windows CE and device driver integration procedure before you perform the installation.

1. Run Microsoft Platform Builder and open your platform.
   
2. Select Open Build Release Directory from the Build menu.
   
3. Copy the WinDriver CE kernel file \WinDriver\redist\TARGET_CPU\windrvr6.dll to the %_FLATRELEASEDIR% subdirectory on your development platform (should be the current directory in the new command window).
   
4. Append the contents of the file \WinDriver\samples\wince_install\PROJECT_WD.REG to the file PROJECT.REG in the %_FLATRELEASEDIR% subdirectory.
   
5. Append the contents of the file \WinDriver\samples\wince_install\PROJECT_WD.BIB to the file PROJECT.BIB in the %_FLATRELEASEDIR% subdirectory.
   
   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). This would be the case if you were transferring 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 need not carry out this step until you build a permanent kernel.
   
6. Select Make Image from the Build menu and name the new image NK.BIN.
   
7. 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.
   
8. Restart your target CE platform. The WinDriver CE kernel will automatically load.
   
9. Compile and run the sample programs to make sure that WinDriver CE is loaded and is functioning correctly. (See Section  3.4 of the Users's Guide, which describes how to check your installation.)

1. Insert the WinDriver CD into your Windows host CD drive.
   
2. Exit from the auto installation.
   
3. Double click the Cd_setup.exe file found in the \Wince directory on the CD. This will copy all needed WinDriver files to your host development platform.
   
4. Copy the WinDriver CE kernel file
   \WinDriver\redist\TARGET_CPU\windrvr6.dll
   to the \WINDOWS subdirectory of your target CE computer.
   
5. Use the Windows CE Remote Registry Editor tool (ceregedt.exe) or the Pocket Registry Editor (pregedt.exe) on your target CE computer to modify your registry so that the WinDriver CE kernel is loaded appropriately. The file \WinDriver\samples\wince_install\PROJECT_WD.REG contains the appropriate changes to be made.
   
6. 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).
   
7. Compile and run the sample programs (see Section 3.4 of the User's Guide, which describes how to check your installation) to make sure that WinDriver CE is loaded and is functioning correctly.

Go back

Back to top

• Linux 2.0.31 or higher (can be embedded Linux or Linux 2.4x)
  
• An x86 processor.
  
• Any 32-bit development environment supporting C (such as GCC).
  

In Linux, kernel modules must be compiled with the same header files that the kernel itself was compiled with. Since WinDriver installs the kernel module windrvr6.o, 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 linux kernel source code

• If you have yet to install Linux, please choose Custom installation when performing the installation and then choose to install the source code.
  
• If Linux is already installed on the machine, you must check to see if 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, you can either reinstall Linux with the source code, as described above, or you can install the source code by following these steps:
  
  1. Login as super user.
     
  2. Type:
     /$ rpm -i /<source location>/ <Linux distributor>/RPMS/kernel-source-<version number>
     (For example: to install the source code from the Linux installation CD-ROM, for RedHat 7.1, type:
     /$ rpm -i /mnt/cdrom/RedHat/RPMS/
     kernel-source-2.4.2.-2.i386rpm)

     TIP!
     If you do not have an RPM with the source code, you may download it from: http://rpmfind.net/linux/RPM/.

• 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. Type:
     /$ make xconfig
  2. Save the configuration by choosing Save and Exit.
  3. Type:
     /$ make dep.

1. Insert the WinDriver CD into your Linux machine CD drive or copy the downloaded file to your preferred directory.
   
2. Change directory to your preferred installation directory (your home directory, for example):
   /$ cd ~
   
3. Extract the file WDxxxLN.tgz (where xxx is the version number):
   ~$ tar xvzf /<file location>/WDxxxLN.tgz
   For example:
   
   • From a CD:
     ~$ tar xvzf /mnt/cdrom/LINUX/WDxxxLN.tgz
     
   • From a downloaded file:
     ~$ tar xvzf /home/username/WDxxxLN.tgz
   
   
4. Change directory to WinDriver (this directory gets created by tar):
   ~$ cd WinDriver/

   NOTE:
   From version 5.x and above this directory gets created by tar, but in versions preceding 5.x the WinDriver directory does not get created by the extraction. Therefore, when working with versions preceding 5.x (version 4.33, for example) first create a directory (e.g., WinDriver) before proceeding with the installation.
   (/$ mkdir ~/WinDriver)

5. Install WinDriver:
   1. ~/WinDriver$ make
   2. Become super user:
      ~/WinDriver$ su
   3. Install the driver:
      ~/WinDriver# make install
6. Create a symbolic link so that you can easily launch the DriverWizard GUI
   ~/WinDriver$ ln -s ~/WinDriver/wizard/wdwizard/ usr/bin/wdwizard
   
7. Change the read and execute permissions on the file wdwizard so that ordinary users can access this program.
   
8. 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.
   
9. You can now start using WinDriver to access your hardware and generate your driver code!

In order to register your copy of WinDriver with the license you received from Jungo, follow the steps below:

1. Activate the DriverWizard GUI:
   ~/WinDriver/wizard$ ./wdwizard
2. Select the Register WinDriver option from the File menu and insert the license string you received from Jungo.
3. Click the Activate License button.
4. To register source code you developed during the evaluation period, please refer to WD_License function reference in Appendix A.

Restricting Hardware Access on Linux

CAUTION:
Since /dev/windrvr6 gives direct hardware access to user programs, it may compromise kernel stability on multi-user Linux systems. Please restrict access to the 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 executable (wdwizard).

Go back

Back to top

• Solaris 8.0/9.0
• 64-bit kernel on SPARC platform
• Any development environment supporting C (such as GCC)
• WinDriver 5.22 is still provided for Solaris 2.6/7.0 32-bit kernel on Intel x86 platform.
  
  NOTE:
  If you have chosen a development environment other than GCC, make sure libgcc is installed on your computer. You may download it from http://www.sunfreeware.com/.
  Set the LD_LIBRARY_PATH to the location of your libgcc, a probable location would be:
  LD_LIBRARY_PATH= /usr/local/lib:/usr/local/lib/sparcv9
  

Installation of WinDriver should be performed by the system administrator logged in as root, or with root privileges, since the WinDriver installation process includes installation of the kernel module windrvr6.

1. Insert your CD into your Solaris machine CD drive or copy the downloaded file to your preferred directory.
   
2. Change directory to preferred installation directory (your home directory, for example):
   /$ cd ~
   
3. Copy the file WDxxxSLS.tgz to the current directory (here `xxx' stands for the version number-500, for example):
   ~$ cp /home/username /WDxxxSLS.tgz /
   
4. Extract the file:
   ~$ gunzip -c WDxxxSLS.tgz | tar xvf -
   
5. Change directory to WinDriver.
   
6. Install WinDriver:
   

   The installation requires you to determine on which PCI card you will be working, by defining the device's Vendor ID and Device ID (hexadecimal values). There are two different ways to do this and install the driver:

   • Modify the installation file before performing the installation and then install WinDriver:
     1. Open the file install_windrvr for editing, and change the default Vendor ID and default Device ID to your PCI card's identification values.
     2. Install WinDriver:
        ~/WinDriver# ./install_windrvr
     
     
   • Use the Command Line to change your device's identification values and install the driver in one step, by typing:
     ~/WinDriver# VENDOR_ID=XXXX DEVICE_ID=XXXX ./install_windrvr

   The following three steps are optional:

7. Create a symbolic link so that you can easily launch the DriverWizard GUI:
   ~/WinDriver# ln -s ~/WinDriver/wizard/wdwizard /usr/bin/wdwizard
   
8. Change the read and execute permissions on the file wdwizard so that ordinary users can access this program.
   
9. 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.
   
10. You can now start using WinDriver to access your hardware and generate your driver code! The following steps are for registered users only:

In order to register your copy of WinDriver with the license you have received from Jungo, please follow the steps below:

1. Activate the DriverWizard GUI:
   ~/WinDriver/wizard$ ./wdwizard
   
2. Select the Register WinDriver option from the File menu and insert the license string you received from Jungo.
   
3. Click the Activate License button.
   
4. To register source code you developed during the evaluation period, please refer to WD_License function reference in Appendix A.

Restricting Hardware Access on Solaris

CAUTION:
Since /dev/windrvr6 gives direct hardware access to user programs, it may compromise kernel stability on multi-user Solaris 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 executable (wdwizard).

Go back

Back to top

The following describes the installation of DriverBuilder for VxWorks. DriverBuilder development environment works with Tornado 2 for Windows only (on x86 platform). Drivers generated using version 5.x and above of DriverBuilder will run on Intel x86 BSPs (pc486, pcPentium and pcPentiumPro), PPC 821/860 with MBX821/860 and PPC 750 (IBM PPC 604) with MCP750. For an up-to-date list see:
db-vxworks.htm#platforms.

Installation:

1. Download DriverBuilder for VxWorks.
   
2. Change drive to the preferred root drive for DriverBuilder. For example:
   \> c:\
   
3. Unpack the file you downloaded:
   \> unzip -d DBXXXVX.zip c:\ (Here `xxx' stands for the version number, e.g., 500.)
   NOTE:
   

   The extraction creates a directory called DriverBuilder and then places all of the DriverBuilder installation files in it. If working with a version prior to 5.00, you will have to create a directory for DriverBuilder manually, and then perform the extraction. For example:
   \> c:\cd_vxworks and unpack the file to it:
   \> unzip -d DBxxxVX.zip c:\db_vxworks

NOTE:
In WinDriver, samples for VxWorks have the .out extension, e.g., pci_diag.out. To invoke these programs, use Windsh to load them, and execute the routine xxx_main. For example:

wddebug.out : wddebug_main pci_diag.out : pci_diag_main

TIP!
DriverBuilder is based on Jungo's WinDriver product line. You can save time by downloading the Windows version of WinDriver and using its graphical development environment for fast hardware validation and automatic code generation. If you choose to do so, follow these steps:

1. Download and install DriverBuilder for VxWorks.
   
2. Download and install WinDriver for Windows. Don't skip this part.
   
3. Create a shortcut on your desktop to DriverWizard (C:\WinDriver\wizard\wdwizard.exe) so that you can easily launch and develop your driver using the GUI DriverWizard.