Re: Packaging Script

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

"MikeD" <nobody@xxxxxxxxxxx> wrote in message
news:OnVAcLzMJHA.5428@xxxxxxxxxxxxxxxxxxxxxxx

"Lenny Abbey" <labbeyATmindspring.com> wrote in message
news:9cKdna1auezUK2HVnZ2dnUVZ_oHinZ2d@xxxxxxxxxxxxxxx
Where can I find the packageing scripts for the Package & Deployment
Wizard?

I need to peek in order to solve a problem.



I too am not sure what you mean by "packaging script". If indeed you mean
what mayanana said, good enough. But, if you mean you want to modify the
actual Setup program, that is located in "\VB98\Wizards\PDWizard\Setup1".
I
suggest you back up everything in that folder before making changes to
anything. If you do make changes, when you recompile the Setup1.exe file,
you have two options for how you want to include your new Setup1.exe. You
can either copy it to "\VB98\Wizards\PDWizard" OR you can copy it to the
Support folder (after having run PDW) and recreate the package by running
the batch file as mayayana described. The difference is that if you copy
it
to "\VB98\Wizards\PDWizard", ALL packages you create will use your
modified
Setup1exe. If you copy it to the Support folder, ONLY that package will
have your modified Setup1.exe.

Note that you cannot modify the Setup.exe bootstrap program. MS did not
include the source code for that (it's written in C or C++, not sure
which).
All it basically does, however, is install the VB6 runtime and launches
Setup1.exe (well, it creates the uninstall log file too). Everything
having
to do with installing your application is done by Setup1.exe and you can
customize that to your heart's content.

--
Mike


My problem is that the packager is no longer creating a "Documentation"
subdir for my project. I haven't changed anything, and this problem surfaced
after 42 compilations of the exe file. I could work up a new script, but the
Doc file (html) contains many small illustrations, and I don't want to have
to hunt them all down again.

Lenny


.