Yes, use EMCO MSI PACKAGE BUILDER.
I have used this app and it is great. Just start monitoring the install, enter the S/N -- generate the MSI. It all gets packaged into a MSI. Let me know what you think of it. You can download the free evulation program and have full use of it

Yes, use EMCO MSI PACKAGE BUILDER.
I have used this app and it is great. Just start monitoring the install, enter the S/N -- generate the MSI. It all gets packaged into a MSI. Let me know what you think of it. You can download the free evulation program and have full use of itThe OP doesn't *need* an MSI: the package is already in that format....

FH, use ProcMon as you launch. It will show what's missing (probably a registry entry).

ORIGINAL: VBScab
The OP doesn't *need* an MSI: the package is already in that format....

FH, use ProcMon as you launch. It will show what's missing (probably a registry entry).



You really love procmon, don't you? [;)]

May be useful but before going to that extreme I'd see if there's a serial number property in the package.

Also, ensure that you have the proper type of license. I've seen this type of behavior before when attempting to repackage something somebody gave me, which turned out to be a single user version. As soon as I realized that, I stopped work on the project and told them it could not be done that way and to get a multi-user version. It doesn't make sense to package or customize a single user version - not only would you have problems with the package, even if you get it to work it would violate your license agreement if you distribute it to more than one user.

You really love procmon, don't you? [;)]As I've said before, I really don't know how anybody does this job without it.