The WinDriver evaluation versions are full-featured, without any reduced features or degraded performance.

The only differences from the registered version are as follows:

    • Each time WinDriver is activated, an evaluation message will appear. When using the DriverWizard, an evaluation message will also pop-up occasionally.


    • On Windows — The evaluation version has a 30 days time limit.


    • On Windows — The evaluation message will appear every two hours (provided you have used the WinDriver kernel module — i.e., called one of the WinDriver APIs, either directly from your code or through one of the WinDriver utilities).


  • On Linux and Windows CE (and in previous versions also onMac OS X, Solaris, and VxWorks) — The evaluation version has a 60 minutes development session limit (this time was shorter in previous versions of WinDriver). To continue using WinDriver after a 60 minutes session, you need to do the following:
      • On Mac OS X, Linux, and Solaris — The driver has to be reloaded — i.e., perform unload and then reload, as detailed below.
        Before removing the WinDriver kernel module (windrvr6/WinDriver/windrvr — depending on the OS), make sure that there are no open handles to this module.

        On Linux:
        /sbin/modprobe -r windrvr6
        <path to wdreg>/wdreg windrvr6

        Note: The commands must be executed with root privileges.

        On Mac OS X (supported until v10.4.0):
        sudo kextunload \

        sudo <path to wdreg>/wdreg WinDriver

        Note: The commands must be executed with root privileges.

        On Solaris (supported until v9.0.1):
        /usr/sbin/rem_drv windrvr6
        /usr/sbin/add_drv windrvr6

      • On Windows CE — Try performing a warm reset, according to the following instructions: Restart your HPC. The WinDriver CE kernel will automatically be loaded. You will have to do a warm reset, rather than just Suspend/Resume. You should look for a button labeled “RESET” on your HPC. On the HP 3xx/6xx series, this button can be found under the reserve battery cover. If this does not help, you will need to reload the OS Image with WinDriver (as was done for the initial installation of WinDriver — see the WinDriver Windows CE installation instructions).
    • On VxWorks (supported until v5.2.2) — The whole system must be restarted (i.e., reboot) after a 60 minutes session.

The limitations of the evaluation version are also outlined in the WinDriver User’s Manual.