I also put (what I think) is a nice drive validation script together that checks... - TARGETDIR starts with a letter and a colon - drive set in TARGETDIR exists - drive is a local fixed drive - enough free space on the drive set in TARGETDIR - drive set in TARGETDIR is writable Check out the attachm...

I am thinking of avoiding all of the hassles of InstallAware and just going back to writing my own bootstrapper. What a pity, the IA concept has such great potential. FYI, one way to accomplish this is to set the registry key for 'automatic' windows logging (HKLM\\Software\\Policies\\Microsoft\\Win...

II can try overriding InstallAware's call to MsiEnableLog() by using the "Call DLL Function" method. Maybe that will do it. That didn't help. I am thinking of avoiding all of the hassles of InstallAware and just going back to writing my own bootstrapper. What a pity, the IA concept has su...

Does anyone have the list of return codes and their meanings from InstallAware? I am running into some trouble, and I am getting back error 314, which is not a standard windows error. Thanks, Eric Actually, nevermind. I figured out the problem. The symptom was the installation was just simply quitt...

Does anyone have the list of return codes and their meanings from InstallAware?

I am running into some trouble, and I am getting back error 314, which is not a standard windows error.

Thanks,

Eric

One of my users is having problems with the install failing on one particular PC. We have tried various copies of the install.exe but the problem persists. The same install has worked on thousands of other sites. The error log shows errors 1708 and 1709 (unhelpful) but this appears to be where the ...

I know that we can use /L=<logfile>, but that turns logging all the way up. This equates to the msi command line option /l*v. I would like to be able to specify, especially for my "sub" MSIs a different logging command. Is there anyway to do this? I can try overriding InstallAware's call t...