The WinDriver and KernelDriver 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\KernelDriver 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 WinDriver's\KernelDriver's utilities).
- On Linux, Solaris, VxWorks and Windows CE -
The evaluation version has a 60-minutes development session limit
(this time was shorter in previous versions of WinDriver\KernelDriver).
In order to continue using WinDriver\KernelDriver after a 60-minutes
session, you will need to do the following:
- For VxWorks - The whole system must be restarted (i.e., reboot) after a 60 minutes session.
- On Linux and Solaris - The driver has to be reloaded - i.e. perform unload and then reload:
On Linux:
/sbin/rmmod windrvr6
/sbin/modprobe windrvr6
On Solaris:
/usr/sbin/rem_drv windrvr6
/usr/sbin/add_drv windrvr6
Before removing the windrvr6 (/windrvr) module, make sure that there are no open handles to this module.
- 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 Installation Instructions for Windows CE).
The limitations of the evaluation version are also outlined in the WinDriver User's Manual.
Back to Top
|