InstallAware

HI,

We have some credetial provider installed on Windows 7, and as such the DLL's can only be removed after a re-boot and a clean up of the registry. It appears that the installer is not cleaning up these files, despite the comments on the forum that locked files will be cleaned up by MSi if they are locked or in use during the uninstall. Is there a way of setting up an uninstall of files after a re-boot?

The dlls are copied in via the install command, but never removed due to the issue above?

Thanks

Steve

Dear Steve,

What about cleaning your registry, rebooting the computer and then calling Apply Uninstall? Have you tried that?

Hi

How do you that? in the script and keep the installer running after a re-boot?

Regards

Steve

Dear Steve,

Exactly. Please look at the Reboot Computer command and let me know if that solves your problem.

Hi,

Ok have tried this..

Have set the Reboot, to reboot and resume, if reboot requested the install does not restart, what is wrong?

All i am trying to achive is to remove two files after a reboot, after the first apply uninstall, I perform two delete files then issue
the command below, which makes sence to me, but it does not even restart the installer?

NOTE: that I have just updated the product to fix the silent install issue, which I also need working. My patients is waring thin on all these issues I keep encountering, as you keep providing answers that either 1. do not work, or 2 be vague at best.! your Difx solution does not work on network light weight filter protocol drivers, and the install is not removing files that it installed. After upgrading to fix the silent install it damaged one of my own dialogs, which stopped wrapping characters on the check box text, which I have had to resort to changing to a label, which fixes the issue, SIGH! . As a side issue everytime I switch to the welcolm screen it cuts the display in half so you can not see your projects which is another anoyance!

Can you please provide more in depth answers to question, such that we can quickly resolve issues as I do not have the time to keep experimenting with your product. I also feel like I am QA'ing an installer product at times and not producing what is needed.

Comment: End of Installation
Display Dialog: finish, wait for dialog to return (modal)
if Variable SILENT Equals FALSE
if Variable REBOOTCOMPUTER Equals TRUE
if Variable SUCCESS Equals REBOOT
if Variable REMOVE Equals TRUE
Reboot Computer and Resume Setup
else
Reboot Computer
end
end
end
end

Regards

Steve

Steve,

It looks like your setup doesn't resume (or resumes and exits) because the Reboot Computer is the last command that is executed. I meant that you reboot your computer and then manually delete the files from the target dir (to make sure they do get removed).

Note that issues can stem from many different reasons. Some stem from misuse of InstallAware, some from problematic target machines, some from a faulty installation of InstallAware and/or its license, and some from bugs with InstallAware.
When issues are posted, I can't always point to the answer in a second. Due to the aforementioned, we need to research the problem together in order to get to a solution. I am sorry you have had some bad experience with InstallAware lately, I truly hope that everything will be resolved ASAP.

Hi,

As this is a built in piece of functionality;

1. How does the installer, (in the msi script) know that is is being resumed? I can not find any variable that tells me this?

2. I was expecting it to at least go into Maintainance mode? it did not? What sections does the resume go into?

3. Is the sample end script code written correctly? or not? (NOTE I have placed message boxes in appropiate places, so I know its getting to the right place).

4. A simple sample script might help me understand how this is supposed to work?

Steve

Dear Steve,

Attached is a sample project that does what you need.
The installer does not know that it is being resumed - that why you need to set a flag for it, like I did with the file in the example (you could substitute this with a registry value or any other way you could think of).
The installer resumes from the beginning - that's why you need to have that flag so you could process your after reboot resume and exit the installer. Please refer to the example - I hope its helpful!

HI,

Ok we have had a re-think on this one and I have created a DLL which uses MoveFileEx, and removes the locked file on a re-boot, this solves the need to resume the install and just removes the file as needed.

Thanks for sample code, it may come in handy for future installers

Steve

Sure, Steve. My pleasure.