PDA

View Full Version : Using Setup.exe to install Windows Installer engine 2.0...



NewsArchive
12-07-2001, 01:00 AM
I may just be missing the big boat on this one but I thought that during
your Release build, if you have within the Windows Installer Service dialog
of the Release Wizard set to "Create Installation Launcher (Setup.exe)" and
checked "Have Setup.exe install WinNT MSI engine" (don't need Win9x MSI
engine, also have the "Delay..." check box checked and "Supress..." check
box checked) that the Setup.exe would install the Windows Installer engine.
We are using the Windows Installer engine 2.0. I have the proper entries in
the Registry (MSIVersion 2.0.2600.0) and the Setup.ini also has the correct
entries <see below>. The Microsoft setup for the WI 2.0 engine, instmsiw.exe
(version 12.0.2600.0), is located along with the source files, Setup.exe,
Setup.ini, WIInstall20.msi, Data1.cab, 0x0409.ini. The Windows 2000 machine
has by default the Windows installer engine, msiexec.exe version
1.20.1827.0. When running my setup, I get the Windows Installer "This
installation package cannot be installed by the Windows Installer service.
You must install a Windows service pack that contains a newer version of the
Windows Installer service." (This is Error 1613 within the Windows Installer
Platform SDK or MSI Help.) Installing Service Pack 2 for Win2K does not
help. I can simply run the instmsiw.exe setup which will in turn install WI
2.0 and of course require a re-boot but I thought InstallShield's Setup.exe
would do this instead. Am I missing something here?

I am using InstallShield Developer 7.01.

Thanks for any help.
William F. Snodgrass
GeoGraphix

Setup.ini text:
[Info]
Name=INTL
Version=1.00.000
DiskSpace=8000 ;DiskSpace requirement in KB

[Startup]
CmdLine=
SuppressWrongOS=Y
ScriptDriven=0
ScriptVer=4.0.0.110
Product=WIInstall20
PackageName=WIInstall20.msi
MsiVersion=2.0.2600.0
EnableLangDlg=N
DoMaintenance=Y
SuppressReboot=Y

[SupportOS]
Win95=1
Win98=1
WinME=1
WinNT4=1
Win2K=1

[Win95]
MajorVer=4
MinorVer=0
BuildNo=950
PlatformId=1

[Win98]
MajorVer=4
MinorVer=10
BuildNo=1998
PlatformId=1

[WinME]
MajorVer=4
MinorVer=90
BuildNo=3000
PlatformId=1

[WinNT4]
MajorVer=4
MinorVer=0
BuildNo=1381
PlatformId=2
ServicePack=1536

[Win2K]
MajorVer=5
MinorVer=0
BuildNo=2195
PlatformId=2
[Languages]
count=1
default=409
key0=409
[WIInstall20.msi]
Type=0
Location=WIInstall20.msi
[Setup.bmp]
Type=1
[instmsiw.exe]
Type=0
Location=instmsiw.exe
CertKey=MSIEng.isc

NewsArchive
12-07-2001, 01:00 AM
I may be missing the boat too, but I think you've got an install that
requires engine 2.0, and you can't get it on the system without a reboot no
matter what boxes you check. The point of the options is that if you don't
have anything that explicitly requires 2.0 *and* your installation requires
a reboot, set your schema to (say) 110 (which will get it installed without
requiring the new engine) and then your reboot will replace the engine with
the 2.0 version as well as complete your installation.

"William F. Snodgrass" <bsnodgrass@geographix.com> wrote in message
news:3c1114cb$1@news.installshield.com...
> I may just be missing the big boat on this one but I thought that during
> your Release build, if you have within the Windows Installer Service
dialog
> of the Release Wizard set to "Create Installation Launcher (Setup.exe)"
and
> checked "Have Setup.exe install WinNT MSI engine" (don't need Win9x MSI
> engine, also have the "Delay..." check box checked and "Supress..." check
> box checked) that the Setup.exe would install the Windows Installer
engine.
> We are using the Windows Installer engine 2.0. I have the proper entries
in
> the Registry (MSIVersion 2.0.2600.0) and the Setup.ini also has the
correct
> entries <see below>. The Microsoft setup for the WI 2.0 engine,
instmsiw.exe
> (version 12.0.2600.0), is located along with the source files, Setup.exe,
> Setup.ini, WIInstall20.msi, Data1.cab, 0x0409.ini. The Windows 2000
machine
> has by default the Windows installer engine, msiexec.exe version
> 1.20.1827.0. When running my setup, I get the Windows Installer "This
> installation package cannot be installed by the Windows Installer service.
> You must install a Windows service pack that contains a newer version of
the
> Windows Installer service." (This is Error 1613 within the Windows
Installer
> Platform SDK or MSI Help.) Installing Service Pack 2 for Win2K does not
> help. I can simply run the instmsiw.exe setup which will in turn install
WI
> 2.0 and of course require a re-boot but I thought InstallShield's
Setup.exe
> would do this instead. Am I missing something here?
>
> I am using InstallShield Developer 7.01.
>
> Thanks for any help.
> William F. Snodgrass
> GeoGraphix
>
> Setup.ini text:
> [Info]
> Name=INTL
> Version=1.00.000
> DiskSpace=8000 ;DiskSpace requirement in KB
>
> [Startup]
> CmdLine=
> SuppressWrongOS=Y
> ScriptDriven=0
> ScriptVer=4.0.0.110
> Product=WIInstall20
> PackageName=WIInstall20.msi
> MsiVersion=2.0.2600.0
> EnableLangDlg=N
> DoMaintenance=Y
> SuppressReboot=Y
>
> [SupportOS]
> Win95=1
> Win98=1
> WinME=1
> WinNT4=1
> Win2K=1
>
> [Win95]
> MajorVer=4
> MinorVer=0
> BuildNo=950
> PlatformId=1
>
> [Win98]
> MajorVer=4
> MinorVer=10
> BuildNo=1998
> PlatformId=1
>
> [WinME]
> MajorVer=4
> MinorVer=90
> BuildNo=3000
> PlatformId=1
>
> [WinNT4]
> MajorVer=4
> MinorVer=0
> BuildNo=1381
> PlatformId=2
> ServicePack=1536
>
> [Win2K]
> MajorVer=5
> MinorVer=0
> BuildNo=2195
> PlatformId=2
> [Languages]
> count=1
> default=409
> key0=409
> [WIInstall20.msi]
> Type=0
> Location=WIInstall20.msi
> [Setup.bmp]
> Type=1
> [instmsiw.exe]
> Type=0
> Location=instmsiw.exe
> CertKey=MSIEng.isc
>
>

NewsArchive
12-11-2001, 01:00 AM
Thanks for answering Phil but I still don't "get" it. Everything I've read
within the newsgroups, Help documentation and Install seems to suggest that
the Setup should in fact install the WI 2.0 engine, run my setup, then
re-boot. I note that none of the IS people who frequent this newsgroup have
responded which means either I'm doing something 'dumb' or this is a bug.
Unfortunately IS Support has not had an answer either.
Bill

"Phil Wilson" <phil.wilson@unisys.com> wrote in message
news:3c113331$1@news.installshield.com...
> I may be missing the boat too, but I think you've got an install that
> requires engine 2.0, and you can't get it on the system without a reboot
no
> matter what boxes you check. The point of the options is that if you don't
> have anything that explicitly requires 2.0 *and* your installation
requires
> a reboot, set your schema to (say) 110 (which will get it installed
without
> requiring the new engine) and then your reboot will replace the engine
with
> the 2.0 version as well as complete your installation.
>
> "William F. Snodgrass" <bsnodgrass@geographix.com> wrote in message
> news:3c1114cb$1@news.installshield.com...
> > I may just be missing the big boat on this one but I thought that during
> > your Release build, if you have within the Windows Installer Service
> dialog
> > of the Release Wizard set to "Create Installation Launcher (Setup.exe)"
> and
> > checked "Have Setup.exe install WinNT MSI engine" (don't need Win9x MSI
> > engine, also have the "Delay..." check box checked and "Supress..."
check
> > box checked) that the Setup.exe would install the Windows Installer
> engine.
> > We are using the Windows Installer engine 2.0. I have the proper entries
> in
> > the Registry (MSIVersion 2.0.2600.0) and the Setup.ini also has the
> correct
> > entries <see below>. The Microsoft setup for the WI 2.0 engine,
> instmsiw.exe
> > (version 12.0.2600.0), is located along with the source files,
Setup.exe,
> > Setup.ini, WIInstall20.msi, Data1.cab, 0x0409.ini. The Windows 2000
> machine
> > has by default the Windows installer engine, msiexec.exe version
> > 1.20.1827.0. When running my setup, I get the Windows Installer "This
> > installation package cannot be installed by the Windows Installer
service.
> > You must install a Windows service pack that contains a newer version of
> the
> > Windows Installer service." (This is Error 1613 within the Windows
> Installer
> > Platform SDK or MSI Help.) Installing Service Pack 2 for Win2K does not
> > help. I can simply run the instmsiw.exe setup which will in turn install
> WI
> > 2.0 and of course require a re-boot but I thought InstallShield's
> Setup.exe
> > would do this instead. Am I missing something here?
> >
> > I am using InstallShield Developer 7.01.
> >
> > Thanks for any help.
> > William F. Snodgrass
> > GeoGraphix
> >
> > Setup.ini text:
> > [Info]
> > Name=INTL
> > Version=1.00.000
> > DiskSpace=8000 ;DiskSpace requirement in KB
> >
> > [Startup]
> > CmdLine=
> > SuppressWrongOS=Y
> > ScriptDriven=0
> > ScriptVer=4.0.0.110
> > Product=WIInstall20
> > PackageName=WIInstall20.msi
> > MsiVersion=2.0.2600.0
> > EnableLangDlg=N
> > DoMaintenance=Y
> > SuppressReboot=Y
> >
> > [SupportOS]
> > Win95=1
> > Win98=1
> > WinME=1
> > WinNT4=1
> > Win2K=1
> >
> > [Win95]
> > MajorVer=4
> > MinorVer=0
> > BuildNo=950
> > PlatformId=1
> >
> > [Win98]
> > MajorVer=4
> > MinorVer=10
> > BuildNo=1998
> > PlatformId=1
> >
> > [WinME]
> > MajorVer=4
> > MinorVer=90
> > BuildNo=3000
> > PlatformId=1
> >
> > [WinNT4]
> > MajorVer=4
> > MinorVer=0
> > BuildNo=1381
> > PlatformId=2
> > ServicePack=1536
> >
> > [Win2K]
> > MajorVer=5
> > MinorVer=0
> > BuildNo=2195
> > PlatformId=2
> > [Languages]
> > count=1
> > default=409
> > key0=409
> > [WIInstall20.msi]
> > Type=0
> > Location=WIInstall20.msi
> > [Setup.bmp]
> > Type=1
> > [instmsiw.exe]
> > Type=0
> > Location=instmsiw.exe
> > CertKey=MSIEng.isc
> >
> >
>
>