Fixing VSPs That Throw Driver Errors

Various software applications use system drivers. Programs like Daemon tools, or Adobe Acrobat are both examples of applications that depend on drivers to function properly.

You may have run into this problem, caused by drivers: You build the VSA, activate it, and see an error message that probably points out that a necessary driver is missing or not started. This is a problem in almost all software virtualization software.

But cheer up, there is a way to get these messages under control with a few simple steps.

Why?

First of all, why do some applications that depend on drivers work, and others don't?

The answer is simple. System drivers can be divided into two groups: resistant and persistent. The first group is no problem; You build a VSA with these drivers, and then the VSA will work. Activating, de-activating. It is no problem. The second group, where Deamon tools belong, are the problem.

The Fix

1. Package the application.
2. Activate the package.
3. If the error pops up, deactivate the package and open the VSA.
4. Go to the windir\system32\drivers, and copy the *.sys file to the local c:\windir\system32\drivers.
5. Now activate the package.
6. The error message will be gone.

Regards
Erikw