I don't knowingly make any registry changes. InstallShield may be making some that I don't know about in doing it's thing.

As for DLL's I have the 3 VFP7 runtime DLL's that I install in Windows\System32, 2 MTDLL's for my ActiveVFP app, and the VFP7 runtime and MS Visual C++ 7 runtime. I also have 1 VFP table, a post-installation EXE, some AVFP prgs and fxps and some misc. HTML, TXT and ASP files.

Thanks,

June

>I believe the windows installer determines this in the installfinalize action. The msi help (from the installshield express help menu) may be more specific. Does your app use any other dlls or make any registry changes during the install/uninstall?
>
>>What are some of the reasons that an un-install of an app installed with InstallShield Express 3.03 (the one that comes with VFP7) will require a computer re-start?
>>
>>I'm testing a new app and am repeatedly installing and un-installing it on my Win SBS 2003 machine. Up until today, it has installed and un-installed nicely, but today it decided it wanted to restart the machine to complete the un-installation.
>>
>>The app is an ActiveVFP web server, and I found that the MTDLL couldn't be deleted as the pool had it locked up. The app is in its own pool, so I stopped it and could then delete the MTDLL.
>>
>>I'm guessing that not being able to delete the MTDLL is one reason that it wants to restart the machine.
>>
>>Are there likely to be any others, such as the VFP runtimes similarly locked? I installed them into Windows\System32 so they could be found, but they were deleted from there.
>>
>>Thanks,
>>June