Import a setup?

[Jch]

Ok, I'm not a programmer, but thats why I'm interested in setup factory. I read a review that indicated it was powerful yet easy enough for idiots like me.

Question: My company had an application and a setup.exe written - without serial number protection. My boss does not want the author to have the serial numbers to unlock the app. Now we want to simply add serial number protection. Can we create use the existing setup? Import it into Setup Factory?
Any enlightenment Appreciated....

[Ted]

While it is *possible* to simply add your existing setup.exe to your Setup Factory 5.0 project, have it installed to a temp folder and then executed, it would be much better to start over using Setup Factory's IDE.

You simply add the files you want to distribute, set their destinations and you're ready to go. The manual steps you through this in the tutorial.

The serial number feature is quite popular in Setup Factory 5.0. If you have any questions about using it, let me know.

Ted

[Jch]

Thanks Ted.
You are right Setup Factory is sure easy to use!
I have created a setup from the authors Setup.lst file which he advised me listed all the application files.
I could use a piece of advice: Do I include all the files listed in the setup.lst or all the files in the .cab? The .cab contains a few more files.

Here's what was listed:
[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=Connectup.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.pdw
Cabs=1

[Bootstrap Files]
File1=@VB6STKIT.DLL,$(WinSysPathSysFile),,,6/18/98 12:00:00 AM,102912,6.0.81.69
File2=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRe gister),,5/31/98 12:00:00 AM,22288,4.71.1460.1
File3=@STDOLE2.TLB,$(WinSysPathSysFile),$(TLBRegis ter),,3/8/99 11:15:44 AM,17920,2.40.4275.1
File4=@ASYCFILT.DLL,$(WinSysPathSysFile),,,3/8/99 11:50:56 AM,147728,2.40.4275.1
File5=@OLEPRO32.DLL,$(WinSysPathSysFile),$(DLLSelf Register),,3/8/99 11:50:56 AM,164112,5.0.4275.1
File6=@OLEAUT32.DLL,$(WinSysPathSysFile),$(DLLSelf Register),,3/8/99 11:50:54 AM,598288,2.40.4275.1
File7=@MSVBVM60.DLL,$(WinSysPathSysFile),$(DLLSelf Register),,5/10/99 12:00:00 AM,1384448,6.0.84.95

[IconGroups]
Group0=Fairway
PrivateGroup0=False
Parent0=$(Programs)

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

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

[Setup1 Files]
File1=@MDAC_TYP.EXE,$(AppPath),,,6/26/98 12:00:00 AM,8124720,4.71.1015.0
File2=@MSMASK32.OCX,$(WinSysPath),$(DLLSelfRegiste r),$(Shared),5/7/99 12:00:00 AM,166408,6.0.84.18
File3=@COMDLG32.OCX,$(WinSysPath),$(DLLSelfRegiste r),$(Shared),5/7/99 12:00:00 AM,140288,6.0.84.18
File4=@MSCOMCT2.OCX,$(WinSysPath),$(DLLSelfRegiste r),$(Shared),5/7/99 12:00:00 AM,645616,6.0.84.18
File5=@MSCOMCTL.OCX,$(WinSysPath),$(DLLSelfRegiste r),$(Shared),5/13/99 12:00:00 AM,1064456,6.0.84.98
File6=@MSSTDFMT.DLL,$(WinSysPath),$(DLLSelfRegiste r),$(Shared),3/26/99 12:00:00 AM,118784,6.0.84.50
File7=@MSBIND.DLL,$(WinSysPath),$(DLLSelfRegister) ,$(Shared),6/18/98 12:00:00 AM,77824,6.0.81.69
File8=@MSDERUN.DLL,$(CommonFiles)\designer,$(DLLSe lfRegister),$(Shared),3/26/99 12:00:00 AM,136704,6.0.84.50
File9=@RDOCURS.DLL,$(WinSysPath),,$(Shared),3/26/99 12:00:00 AM,151552,6.0.84.50
File10=@MSRDO20.DLL,$(WinSysPath),$(DLLSelfRegiste r),$(Shared),3/26/99 12:00:00 AM,397312,6.0.84.50
File11=@MSCDRUN.DLL,$(CommonFiles)\Designer,$(DLLS elfRegister),$(Shared),6/18/98 12:00:00 AM,49152,6.0.81.69
File12=@MSDBRPTR.DLL,$(WinSysPath),$(DLLSelfRegist er),$(Shared),6/18/98 12:00:00 AM,299008,6.0.81.69
File13=@DAO360.DLL,$(WinSysPath),$(DLLSelfRegister ),$(Shared),12/7/99 1:00:00 PM,557328,3.60.2927.12
File14=@WININET.DLL,$(WinSysPath),,$(Shared),3/18/99 12:00:00 AM,459024,5.0.2314.1003
File15=@Connectup.exe,$(AppPath),,,3/21/00 12:21:30 AM,602112,1.0.0.1

; The following lines may be deleted in order to obtain extra
; space for customizing this file on a full installation diskette.
;
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

[Ted]

Depending on your situation, it is best to use Setup Factory 5.0's "Runtime Wizard" to add your support files. Of course, if you already have a list that you know is correct then go ahead and work with that. It's better to know what you need to install rather than just install something because it was found in a .cab file. You don't really want to be installing system files that aren't required or something like that.