Page 1
Page 2
Page 3
These, too, are operated upon by right-clicking the list
of entries. Again, they may be applied to all processors or one specific example.
Once
all of this has been done, the next step is to create the setups themselves!
Here,
the user may decide which processor setups are to be created. Click on the 'Create
Setup' button and PPCInstall will go to work, creating the necessary .Cab and
.Inf files for the setup. To reduce the size of the setup files, PPCInstall only
puts one processor type in each setup file, naming them accordingly. It seems
highly unlikely that any end-user would really want an inflated setup file that
supported all processor types!
Note that the PPCInstall
setup project file and all setup files created here are placed in a 'PPCSetup'
folder beneath the original project folder i.e. the one where the eVb project
file was located.
Once the work has been done to create
the setup files, a summary of the is displayed:
You'll
note the message about WinZip® SE shown here. One of PPCInstall's neat features
is that, if it finds SE installed on the computer where it is carrying out it's
work, it will create a self-extracting installation file for you! Note that it
still provides the .Cab, .Inf, and Setup.exe file if you prefer to use them.
The
SE file is configured to operate as a true setup operation, like many found on
the 'net.
Note that a PPCInstall help-file
is available for download on the site.
WinZip®
SE is available from http://www.winzip.com.
I
hope that eVb developers will take the opportunity to try the free
30-day evaluation copy of PPCInstall and let me know their conclusions. My
aim is to continue development of this tool - there are several ideas in mind
for it's future (see the web-site). If you have other ideas - let me know!
Jeff
Law
jefflaw@datamasta.co.nz
Next Page