Re: I need help with Inno
Well your iss file is deploying your exe and the couple of your own files and making the startup shortcuts etc but it isn't deploying any of the VB bootstrap or runtime files.
I never use the inno wizard.
I don't have a link to hand but on the inno site is a help page that shows how to make an iss file based on your vb setup.lst file.
Re: I need help with Inno
Re: I need help with Inno
Marty,
As far as the files listed in your PDW under bootstrap and setup1 files, you can forget about the bootstrap, and just download and include the VB6SP6 runtime package from Microsoft Downloads (and name it VB6SP6 for simplicity).
The line in INNO to install the VB6SP6 runtimes is just this:
in [files] section:
Source: c:\VB6SP6.exe; DestDir: {tmp}; DestName: VB6SP6.exe; Flags: ignoreversion skipifsourcedoesntexist
in [run] section:
Filename: {tmp}\VB6SP6.exe; Parameters: "/Q"; WorkingDir: {tmp}; Flags: skipifdoesntexist
That will install the VB6 runtimes, if needed on the end user machine.
as far as the "setup files" section goes from the PDW, you already included the ones that were actually yours, like the vbnewkeywords.txt, your exe, etc.. so you only need to then include the various OCX and DLL files. You would include them the same way, but make their target directory the system32 folder (the {sys} environment variable in INNO can be used) and not the program directory (same way PDW would do it). Any one marked DLLSelfRegister should also have a flag for 'regserver' in the files section for those files so INNO knows to call regsvr on them to register them for COM.
See how far that gets you and post back with more questions... its friday... must... go... home
Re: I need help with Inno
Okay the following is an iss file that creates a setup.exe that works but the setup.exe file is large at 1856 KB compared to the 478 KB file created by the P&D Wizard. I assume it's larger because I'm including msvbvm60.dll. What do I do about that?
; Script generated by the Inno Setup Script Wizard.
; SEE THE DOCUMENTATION FOR DETAILS ON CREATING INNO SETUP SCRIPT FILES!
[Setup]
; NOTE: The value of AppId uniquely identifies this application.
; Do not use the same AppId value in installers for other applications.
; (To generate a new GUID, click Tools | Generate GUID inside the IDE.)
AppId={{0D1C056E-4224-472B-A838-87658831B805}
AppName=Private Message Viewer
AppVerName=Private Message Viewer 1.3
AppPublisher=MartinLiss
DefaultDirName={pf}\Private Message Viewer
DefaultGroupName=Private Message Viewer
OutputBaseFilename=setup
Compression=lzma
SolidCompression=yes
ArchitecturesInstallIn64BitMode=x64 ia64
[Languages]
Name: "english"; MessagesFile: "compiler:Default.isl"
[Tasks]
Name: "desktopicon"; Description: "{cm:CreateDesktopIcon}"; GroupDescription: "{cm:AdditionalIcons}"; Flags: unchecked
Name: "quicklaunchicon"; Description: "{cm:CreateQuickLaunchIcon}"; GroupDescription: "{cm:AdditionalIcons}"; Flags: unchecked; OnlyBelowVersion: 0,6.1
[Files]
;System DLLs
Source: "C:\Inno VB System DLLs\stdole2.tlb"; DestDir: "{sys}"; OnlyBelowVersion: 0,6; Flags: restartreplace uninsneveruninstall sharedfile regtypelib
Source: "C:\Inno VB System DLLs\msvbvm60.dll"; DestDir: "{sys}"; OnlyBelowVersion: 0,6; Flags: restartreplace uninsneveruninstall sharedfile regserver
Source: "C:\Inno VB System DLLs\oleaut32.dll"; DestDir: "{sys}"; OnlyBelowVersion: 0,6; Flags: restartreplace uninsneveruninstall sharedfile regserver
Source: "C:\Inno VB System DLLs\olepro32.dll"; DestDir: "{sys}"; OnlyBelowVersion: 0,6; Flags: restartreplace uninsneveruninstall sharedfile regserver
Source: "C:\Inno VB System DLLs\asycfilt.dll"; DestDir: "{sys}"; OnlyBelowVersion: 0,6; Flags: restartreplace uninsneveruninstall sharedfile
Source: "C:\Inno VB System DLLs\comcat.dll"; DestDir: "{sys}"; OnlyBelowVersion: 0,6; Flags: restartreplace uninsneveruninstall sharedfile regserver
;Program files
Source: "C:\Private Message Viewer\Private Message Viewer.exe"; DestDir: "{app}"; Flags: ignoreversion
Source: "C:\Private Message Viewer\Data\vbkeywords.txt"; DestDir: "{app}\Data"; Flags: ignoreversion
Source: "C:\Private Message Viewer\Data\vbnewkeywords.txt"; DestDir: "{app}\Data"; Flags: ignoreversion
;OCXs
Source: "C:\Private Message Viewer\P&D Wizard\Support\SSCTA32.OCX"; DestDir: "{sys}"; Flags: sharedfile regserver
Source: "C:\Private Message Viewer\P&D Wizard\Support\comdlg32.ocx"; DestDir: "{sys}"; Flags: sharedfile regserver
;Source: "C:\Private Message Viewer\P&D Wizard\Support\RICHED32.DLL"; DestDir: "{sys}"
Source: "C:\Private Message Viewer\P&D Wizard\Support\RICHTX32.OCX"; DestDir: "{sys}"; Flags: sharedfile regserver
Source: "C:\Private Message Viewer\P&D Wizard\Support\DBGWPROC.DLL"; DestDir: "{sys}"; Flags: sharedfile regserver
Source: "C:\Private Message Viewer\P&D Wizard\Support\RICHTX32.OCX"; DestDir: "{sys}"; Flags: sharedfile regserver
Source: "C:\Private Message Viewer\P&D Wizard\Support\msxml4.dll"; DestDir: "{sys}"; Flags: sharedfile regserver
Source: "C:\Private Message Viewer\P&D Wizard\Support\msimg32.dll"; DestDir: "{sys}"; Flags: sharedfile
;The following are from the P&D Wizard setup.lst
;[email protected],$(AppPath)\Data,,,3/6/07 8:39:12 AM,2440,0.0.0.0
;[email protected],$(AppPath)\Data,,,2/1/07 8:37:09 AM,989,0.0.0.0
;[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),7/1/96 4:03:00 AM,20992,1.0.0.1
;[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),3/9/04 1:00:00 AM,152848,6.1.97.82
;[email protected],$(WinSysPathSysFile),,,5/7/98 1:00:00 AM,174352,4.0.993.4
;[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),5/14/08 2:32:48 AM,212240,6.1.97.82
;[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),2/3/07 8:28:50 PM,28672,1.0.0.829
;[email protected],$(WinSysPath),$(DLLSelfRegister),$(Shared),7/21/09 1:05:40 AM,1348432,4.20.9876.0
;[email protected],$(WinSysPath),,$(Shared),4/13/08 5:11:59 PM,4608,5.1.2600.5512
;File10=@Private Message Viewer.exe,$(AppPath),,,6/17/10 8:44:54 AM,475136,1.3.0.0
; NOTE: Don't use "Flags: ignoreversion" on any shared system files
[Icons]
Name: "{group}\Private Message Viewer"; Filename: "{app}\Private Message Viewer.exe"
Name: "{group}\{cm:UninstallProgram,Private Message Viewer}"; Filename: "{uninstallexe}"
Name: "{commondesktop}\Private Message Viewer"; Filename: "{app}\Private Message Viewer.exe"; Tasks: desktopicon
Name: "{userappdata}\Microsoft\Internet Explorer\Quick Launch\Private Message Viewer"; Filename: "{app}\Private Message Viewer.exe"; Tasks: quicklaunchicon
[Run]
Filename: "{app}\Private Message Viewer.exe"; Description: "{cm:LaunchProgram,Private Message Viewer}"; Flags: nowait postinstall skipifsilent
Re: I need help with Inno
Not an Innoan, but maybe rip out:
Code:
Source: "C:\Inno VB System DLLs\stdole2.tlb"; DestDir: "{sys}"; OnlyBelowVersion: 0,6; Flags: restartreplace uninsneveruninstall sharedfile regtypelib
Source: "C:\Inno VB System DLLs\msvbvm60.dll"; DestDir: "{sys}"; OnlyBelowVersion: 0,6; Flags: restartreplace uninsneveruninstall sharedfile regserver
Source: "C:\Inno VB System DLLs\oleaut32.dll"; DestDir: "{sys}"; OnlyBelowVersion: 0,6; Flags: restartreplace uninsneveruninstall sharedfile regserver
Source: "C:\Inno VB System DLLs\olepro32.dll"; DestDir: "{sys}"; OnlyBelowVersion: 0,6; Flags: restartreplace uninsneveruninstall sharedfile regserver
Source: "C:\Inno VB System DLLs\asycfilt.dll"; DestDir: "{sys}"; OnlyBelowVersion: 0,6; Flags: restartreplace uninsneveruninstall sharedfile
Source: "C:\Inno VB System DLLs\comcat.dll"; DestDir: "{sys}"; OnlyBelowVersion: 0,6; Flags: restartreplace uninsneveruninstall sharedfile regserver
;Program files
Seriously though, I'd just use VSI 1.1 and create a nice clean MSI for this.
Re: I need help with Inno
VSI (the official replacement for P&DW) is no longer available direct from the Microsoft site, but you can get it (slowly!) from an archive site:
http://web.archive.org/web/200805131.../aa718352.aspx
It may also be available via MSDN subscriber downloads.
Re: I need help with Inno
If you don't have VSI 1.1 yet you probably don't have the VB6 SP6 merge modules then either.
After installing VSI 1.1 you extract the merge modules and copy them over the old ones in:
C:\Program Files\Microsoft Visual Studio\COMMON\Tools\VSInst\BuildRes
Re: I need help with Inno
I had previously downloaded and extracted both setup1.exe and setup2.exe for the VSI but then what do i do? When I run setup.exe it just installs the installer. :confused:
Re: I need help with Inno
The product is named "Visual Studio 6.0 Installer 1.1" which is a sort of crummy name, easily confused with Windows Installer.
Afterward you should end up with a new folder in the Start Menu under Microsoft Visual Studio 6.0: Microsoft Visual Studio Enterprise Tools. Look in there.
Re: I need help with Inno
BTW the VSI documentation says "[VSI] setups can run on any 32-bit Windows desktop platform". I have someone who wants to run on a 64-bit platform which Inno can handle. So let me ask this. What happens if I don't include msvbvm60.dll?
Re: I need help with Inno
Quote:
Originally Posted by
dilettante
The product is named "Visual Studio 6.0 Installer 1.1" which is a sort of crummy name, easily confused with Windows Installer.
Afterward you should end up with a new folder in the Start Menu under Microsoft Visual Studio 6.0: Microsoft Visual Studio Enterprise Tools. Look in there.
Thanks.
Re: I need help with Inno
Quote:
Originally Posted by
MartinLiss
BTW the VSI documentation says "[VSI] setups can run on any 32-bit Windows desktop platform". I have someone who wants to run on a 64-bit platform which Inno can handle. So let me ask this. What happens if I don't include msvbvm60.dll?
LOL, sorry. Can't help myself.
The whole 64-bit thing was just marketing hype to get people to buy a new PC and more RAM. Otherwise as prices fell well-equipped PCs would be going for $100, cutting into profits.
Don't sweat it. Even WMP is still 32-bit software under Vista/Win7 64-bit, as is Visual Studio 2010! VSI 1.1 is just old, not obsolete like some things. ;)
I wish those Inno people wouldn't spread so much FUD. Their setups are deprecated under Viata/Win7 just like the PDW's.
BTW: The VB6 runtimes (and even more) are shipped as part of Windows, even 64-bit. Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008 and Windows 7. Expect a Support Statement update covering Win8 when it ships.
Re: I need help with Inno
Re: I need help with Inno
Quote:
Originally Posted by
dilettante
The whole 64-bit thing was just marketing hype to get people to buy a new PC and more RAM. Otherwise as prices fell well-equipped PCs would be going for $100, cutting into profits.
Maybe for you, but I for one use all 6GB of the ram in my machine, and I wouldn't be able to do that with a 100 dollar x86 machine.
http://www.bit-tech.net/bits/2007/10...just_the_ram/1
