Installation issues 1

[cmahon]

Hi All

I'm sorry if this topic has been covered before but I'm really stuck at the moment and I can't quite figure out how to create an install program.

I originally used the Package and Deployment wizard as included with VB and after succesfull installs on Win 98 machines I then tried to put it onto a Win XP Machine, however, I received an error message saying that some files were out of date and the PC then rebooted, however the program did not install.

I have tried using the INNO program to create the script but I just can't get my head around what I'm doing wrong.

I have tried searching through the forums for help on the install program but I can't make sense of what is wrong. Thh following is the SETUP.lst file as created by the VB Package and Deployment wizard:

[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=Timesheet_Entry.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),$(DLLSelfRegister),,5/31/98 12:00:00 AM,22288,4.71.1460.1
File3=@STDOLE2.TLB,$(WinSysPathSysFile),$(TLBRegister),,8/29/02 5:00:00 AM,17920,3.50.5014.0
File4=@ASYCFILT.DLL,$(WinSysPathSysFile),,,8/29/02 5:00:00 AM,77824,3.50.5014.0
File5=@OLEPRO32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,8/29/02 5:00:00 AM,106496,5.0.5014.0
File6=@OLEAUT32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,8/29/02 5:00:00 AM,569344,3.50.5016.0
File7=@MSVBVM60.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,8/29/02 5:00:00 AM,1388544,6.0.92.37

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

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

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

[Setup1 Files]
File1=@MSCOMCT2.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/26/98 12:00:00 AM,644400,6.0.81.77
File2=@GRID32.OCX,$(AppPath),,,6/26/98 8:22:22 PM,94744,4.0.29.8
File3=@MSCAL.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),1/5/04 10:24:16 AM,89600,8.0.0.5007
File4=@MSFLXGRD.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/24/98 12:00:00 AM,244024,6.0.81.69
File5=@MSMASK32.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/24/98 12:00:00 AM,166200,6.0.81.69
File6=@msstdfmt.dll,$(WinSysPath),$(DLLSelfRegister),$(Shared),4/5/01 5:43:19 PM,118784,6.0.88.4
File7=@MSADODC.OCX,$(WinSysPath),$(DLLSelfRegister),$(Shared),6/24/98 12:00:00 AM,118064,6.0.81.71
File8=@msado20.tlb,$(WinSysPath),,$(Shared),2/20/03 4:20:58 PM,61440,2.80.1022.0
File9=@Timesheet_Entry.exe,$(AppPath),,,1/15/04 2:13:41 AM,86016,1.0.0.0

and this is what I have so far in INNO.

[Setup]
AppName=Timesheet Entry
AppVerName=Timesheet Entry 1.1
AppPublisher=CM Software
DefaultDirName={pf}\Timesheet Entry
DefaultGroupName=Timesheet Entry
Compression=lzma
SolidCompression=yes

[Tasks]
Name: "desktopicon"; Description: "{cm:CreateDesktopIcon}"; GroupDescription: "{cm:AdditionalIcons}"; Flags: unchecked

[Files]
Source: "C:\OLD\Timesheet_Entry.exe"; DestDir: "{app}"; Flags: ignoreversion
; NOTE: Don't use "Flags: ignoreversion" on any shared system files

[Icons]
Name: "{group}\Timesheet Entry"; Filename: "{app}\Timesheet_Entry.exe"
Name: "{userdesktop}\Timesheet Entry"; Filename: "{app}\Timesheet_Entry.exe"; Tasks: desktopicon

[Run]
Filename: "{app}\Timesheet_Entry.exe"; Description: "{cm:LaunchProgram,Timesheet Entry}"; Flags: nowait postinstall skipifsilent

If anyone can point me in the right direction about where to include the copying and registering of DLL's and ocx's in the INNO file I would appreciate it, or if someone can help me to change the SETUP.lst file so that it will install I would also appreciate it.

The program uses ADO to interface with an ACCESS database, I am using VB6 SP 4.0

Thanks

cmahon

 

[dilettante]

I'm slightly suspicious of File8 after giving this a quick look. It seems to be the version from an installation of MDAC 2.8, and probably "points to" MDAC 2.8 components.

You can't just install an msado20.tlb from a random version of MDAC. The whole MDAC package (tailored for the OS version) needs to be installed if you want to use 2.8 MDAC. XP comes with MDAC 2.7 if I recall correctly.

Microsoft Data Access Components (MDAC) 2.8

I'm not aware of a strategy to slip this into your application setup package. Generally it needs to be run as a separate setup (though your setup can perhaps "kick it off" to run by itself).

If you are referencing msado20.tlb in your VB project in order to get a program that runs generically with any later (2.5+??) MDAC, maybe the answer is to exclude this file from your setup package? Easy enough to try on one XP system, hmm?

Just an idea. If something else occurs to me I'll repost.

 

[AEtherson]

after the reboot you did run the install package again???

because the system needs a reboot after installing the vb runtimes, then you can install your app

 

[dilettante]

If the problem turns out to be MDAC, you might look at:

INFO: VB6 Readme: Part 6 Wizard Issues
or
How To Distribute ADO with the VB5 Application Setup Wizard

Though the latter should be irrelevant to you, using VB6. It still may offer an idea or two worth knowing.

 

[cmahon]

Thanks for your replies, I think it did have something to do with the version of MDAC. I did some research on the Microsoft website and I can basically remove all the components from the Bootstrap files area (except for VB6STKIT.DLL) and run a program called vbrun60.exe which installs the latest versions of all the VB6 run-time libraries. I have then amended the setup1 files area to install the mdac_typ.exe and copy the executable across to the client machine, there is now no reference to msado20.tlb in the setup.lst. I don't have any non-development XP Machines to test this on but I'm hopeful it will work, having tested this on a development machine the program has installed successfully.