Don't want to "install" the .exe or a shortcuts/icons

I used the PDW years ago to create this

Code:

---

[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=AMC.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1

[Bootstrap Files]
[email protected],$(WinSysPathSysFile),,,6/18/98 12:00:00 AM,102912,6.0.81.69
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98 12:00:00 AM,22288,4.71.1460.1
[email protected],$(WinSysPathSysFile),$(TLBRegister),,8/4/04 4:00:00 AM,17920,3.50.5014.0
[email protected],$(WinSysPathSysFile),,,8/4/04 4:00:00 AM,65024,5.1.2600.2180
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,8/4/04 4:00:00 AM,83456,5.1.2600.2180
[email protected],$(WinSysPathSysFile),$(DLLSelfRegister),,8/4/04 4:00:00 AM,553472,5.1.2600.2180

[IconGroups]
Group0=AMC
PrivateGroup0=True
Parent0=$(Programs)

[AMC]
Icon1="AMC.exe"
Title1=AMC
StartIn1=$(AppPath)

[Setup]
Title=AMC
DefaultDir=$(ProgramFiles)\AMC
AppExe=AMC.exe
AppToUninstall=AMC.exe

[Setup1 Files]
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/24/98 12:00:00 AM,244024,6.0.81.69
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),6/26/98 12:00:00 AM,644400,6.0.81.77
[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),7/14/04 6:27:12 PM,1081616,6.1.97.82

---

We are about to use it at a new customer sight...

We don't want it to create an entry in the PROGRAM FILES - or actually install the AMC.exe program.

Just the dll's - that's it.

The wizard didn't seem to allow that - and I'm not sure how to "hand edit" this.

Also - how to you make sure the references are the newest and best for deployment?

OK.... I'll bite.... why not install the EXE? You're trying to build a patch install aren't you?

I haven't used PDW in some time.... but I'd guess that the IconGroups, AMC, and Setup sections could be taken out... leave the boottstrap and the SetupFiles section. But that's just a guess.

-tg

I tried removing one of those "sections" and the thing blew up - I'll try all three.

The .EXE runs off a share that the users get to under some common "universal drive" that they all have access to. That just happens to be the way we set this up 7 years ago.

Actually - this customer will have several shortcuts - each with the .exe paired with a different .ini to open a different DB (and thus a different application for the user).

Instead of just editing the ini, you may want to try modifying the setup project in ..

?:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Setup1

Make a backup copy of the project and the exe in use. Change the code to perform the install as you need, recompile and run. :)