Software Deployment

Could you post the CustomAction table entry for us?
Also; where are you sequencing it?

As ever, a verbose log will show you more detail about the error.

Below is an extract from the verbose log which runs the my app:

Action start 09:14:11: RunHASPDriver.
MSI (c) (E8:64) [09:14:14:878]: Note: 1: 1721 2: RunHASPDriver 3: C:\Program Files\HRH\Gravitas\Program\Remote Update\hinstall.exe 4: -i
MSI (c) (E8:64) [09:14:21:753]: Product: Gravitas -- Error 1721.There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: RunHASPDriver, location: C:\Program Files\HRH\Gravitas\Program\Remote Update\hinstall.exe, command: -i
Action ended 09:14:21: RunHASPDriver. Return value 3.
Info 2896.Executing action RunHASPDriver failed.

The custom action is set to run if the check box on the final screen is selected and the finish button is clicked. The in-script execution is immediate and the return processing is synchronous (check exit code).

I have noticed that the vista UAC shield has disappeared from my setup.exe icon.

All I wanted to do was compress the files to a cabinet so my CD image wouldn't be so big.

Thanks in advance for any solutions

If not already, use the Aladdin Hardlock driver Merge Module found at: ftp://ftp.aladdin.com/pub/aladdin.de/hardlock

This merge module is out of date a new driver has just been released this month.

Also it would be preferred if the user had the option to install the hasp drivers or not at the end of the install.

Any other ideas how to fix this?

Thanks in advance

The in-script execution is immediate
This is the cause the CA fail. On Vista any CA that modifies the "system" needs to be executed in deferred execution due to the UAC "feature".