If I understand your question correctly, you are indicating that an attempt to install your application's prerequisites causes Explorer to appear. If that is the case, it would be useful to diagnose what the InstallShield wizard is doing at that time. For setup prerequisites, the easiest way to see this is a debug log created with setup.
Exe /debuglog . For feature prerequisites, you need to specify the property ISDEBUGLOG to the full path for the debug log it should use (this can be the same or a different path as the other one). So for both you can specify something like setup.
Exe /debuglog /v"ISDEBUGLOG=\"C:\debuglog. Txt\"" .
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.