Any hints!??!??!?!?!?
I am running ISWI ver. 2.03.
Thanking You in Anticipation
Thomas Eskesen
Posted 25 April 2001 - 14:20
Any hints!??!??!?!?!?
I am running ISWI ver. 2.03.
Thanking You in Anticipation
Thomas Eskesen
Posted 07 May 2001 - 21:35
Posted 07 May 2001 - 23:40
Posted 08 May 2001 - 07:50
BUT: I found a Hack that did the trick (after a lot of "blod, sweat and tears"):
To Update the msi aftewards use the script (I have not tried this, but found it in a new group!!!)
<vbscript>
Set oMsi = CreateObject("WindowsInstaller.Installer")
Set oDb = oMsi.OpenDatabase("...\MyMsi.msi" , 1 )
Set oView = oDb.OpenView("UPDATE `Control` SET `Attributes`=1 WHERE
`Control`='DlgLine' AND `Attributes`=0")
oView.Execute
oView.Close
oDb.Commit
</vbscript>
To fix the problem:
Export the ism to Isv, then patch it..., then reconvert it to .ISM (backup before as this is a hack).
There is no real way to be sure of the right dialog. Basically, look in the ISV file for the dialogname, then the following lines should be the controls. 1 control should be named 'DlgLine'.
"DlgLine CONTROL Cxxxx 1 0 Line 326 234 0 0 48"
The last 0 should be changed to 1
The Cxxxx may vary.
And it works!!!!
Regards,
Thomas
Posted 15 May 2001 - 18:41
Posted 30 May 2001 - 16:22
I solved it by exporting the "Ready to install" dialog, using that instead of the Blank to create a new one, then I deleted the original components and copied my new components across. After recreating the button actions, I deleted the original dialog and renamed the new one to replace it.
You don't have to use "Ready to install" but its lack of radio buttons helps prevent further problems when deleting the unwanted components.