failed autoexecutable msi installer
failed autoexecutable msi installer
Hi all,
I'm trying to install a piece of software that seems to be an
autoexecutable MSI installer (if that's the correct term). When I run it
a small 'Setup' window pops up for about 30 seconds but the content
never gets painted. Then the installer quits and I get the msiexec usage
message.
The installer runs OK on native Windows and the previous version of the
same software (released in Feb 2007) installs OK in Wine. The exe file
can be unpacked but I don't see any msi or setup file in there.
Has anyone come across this before? Any suggestions?
Software available from
http://xsens.com/Static/Documents/UserU ... v3.0.2.exe.
Output from attempted installation:
[carl@carl-macbook:~]% wine '/home/carl/OperaDownloads/MTSDK_v3.0.2/MTSDK_v3.0.2.exe'
preloader: Warning: failed to reserve range 00000000-00010000
preloader: Warning: failed to reserve range 00000000-00010000
preloader: Warning: failed to reserve range 00000000-00010000
preloader: Warning: failed to reserve range 00000000-00010000
preloader: Warning: failed to reserve range 00000000-00010000
preloader: Warning: failed to reserve range 00000000-00010000
Usage:
Install a product:
msiexec {package|productcode} [property]
msiexec /i {package|productcode} [property]
msiexec /a package [property]
Repair an installation:
msiexec /f[p|o|e|d|c|a|u|m|s|v] {package|productcode}
Uninstall a product:
msiexec /x {package|productcode} [property]
Advertise a product:
msiexec /j[u|m] package [/t transform] [/g languageid]
msiexec {u|m} package [/t transform] [/g languageid]
Apply a patch:
msiexec /p patchpackage [property]
msiexec /p patchpackage /a package [property]
Modifiers for above operations:
msiexec /l[*][i|w|e|a|r|u|c|m|o|p|v|][+|!] logfile
msiexec /q{|n|b|r|f|n+|b+|b-}
Register a module:
msiexec /y module
Unregister a module:
msiexec /z module
Display usage and copyright:
msiexec {/h|/?}
NOTE: Product code on commandline unimplemented as of yet
Copyright 2004 Vincent B�ron
Thanks.
--
Carl
I'm trying to install a piece of software that seems to be an
autoexecutable MSI installer (if that's the correct term). When I run it
a small 'Setup' window pops up for about 30 seconds but the content
never gets painted. Then the installer quits and I get the msiexec usage
message.
The installer runs OK on native Windows and the previous version of the
same software (released in Feb 2007) installs OK in Wine. The exe file
can be unpacked but I don't see any msi or setup file in there.
Has anyone come across this before? Any suggestions?
Software available from
http://xsens.com/Static/Documents/UserU ... v3.0.2.exe.
Output from attempted installation:
[carl@carl-macbook:~]% wine '/home/carl/OperaDownloads/MTSDK_v3.0.2/MTSDK_v3.0.2.exe'
preloader: Warning: failed to reserve range 00000000-00010000
preloader: Warning: failed to reserve range 00000000-00010000
preloader: Warning: failed to reserve range 00000000-00010000
preloader: Warning: failed to reserve range 00000000-00010000
preloader: Warning: failed to reserve range 00000000-00010000
preloader: Warning: failed to reserve range 00000000-00010000
Usage:
Install a product:
msiexec {package|productcode} [property]
msiexec /i {package|productcode} [property]
msiexec /a package [property]
Repair an installation:
msiexec /f[p|o|e|d|c|a|u|m|s|v] {package|productcode}
Uninstall a product:
msiexec /x {package|productcode} [property]
Advertise a product:
msiexec /j[u|m] package [/t transform] [/g languageid]
msiexec {u|m} package [/t transform] [/g languageid]
Apply a patch:
msiexec /p patchpackage [property]
msiexec /p patchpackage /a package [property]
Modifiers for above operations:
msiexec /l[*][i|w|e|a|r|u|c|m|o|p|v|][+|!] logfile
msiexec /q{|n|b|r|f|n+|b+|b-}
Register a module:
msiexec /y module
Unregister a module:
msiexec /z module
Display usage and copyright:
msiexec {/h|/?}
NOTE: Product code on commandline unimplemented as of yet
Copyright 2004 Vincent B�ron
Thanks.
--
Carl
Re: failed autoexecutable msi installer
Looks like a long known problem. You might want to extract content of the exe file. And use msiexec directly on the .msi file that's inside that archive.Carl Fischer wrote:Output from attempted installation:
[carl@carl-macbook:~]% wine '/home/carl/OperaDownloads/MTSDK_v3.0.2/MTSDK_v3.0.2.exe'
Usage:
Install a product:
msiexec {package|productcode} [property]
msiexec /i {package|productcode} [property]
failed autoexecutable msi installer
On Mon, May 5, 2008 at 12:08 PM, vitamin <[email protected]> wrote:
http://bugs.winehq.org/show_bug.cgi?id=9628 perhaps?[carl@carl-macbook:~]% wine '/home/carl/OperaDownloads/MTSDK_v3.0.2/MTSDK_v3.0.2.exe'Looks like a long known problem.Usage:
Install a product:
msiexec {package|productcode} [property]
msiexec /i {package|productcode} [property]
Re: failed autoexecutable msi installer
Looks like it, assuming this installer works on windows .Dan Kegel wrote:On Mon, May 5, 2008 at 12:08 PM, vitamin <[email protected]> wrote:http://bugs.winehq.org/show_bug.cgi?id=9628 perhaps?[carl@carl-macbook:~]% wine '/home/carl/OperaDownloads/MTSDK_v3.0.2/MTSDK_v3.0.2.exe'Looks like a long known problem.Usage:
Install a product:
msiexec {package|productcode} [property]
msiexec /i {package|productcode} [property]
failed autoexecutable msi installer
On Mon, 2008-05-05 at 14:08 -0500, vitamin wrote:
there is no .msi file inside, or any other archives that I can see.
--
Carl
Thanks for your reply. I already extracted the contents of the file butCarl Fischer wrote:Looks like a long known problem. You might want to extract content of the exe file. And use msiexec directly on the .msi file that's inside that archive.Output from attempted installation:
[carl@carl-macbook:~]% wine '/home/carl/OperaDownloads/MTSDK_v3.0.2/MTSDK_v3.0.2.exe'
Usage:
Install a product:
msiexec {package|productcode} [property]
msiexec /i {package|productcode} [property]
there is no .msi file inside, or any other archives that I can see.
--
Carl
Re: failed autoexecutable msi installer
There is a msi installer inside that file at offset 249586.Carl Fischer wrote:On Mon, 2008-05-05 at 14:08 -0500, vitamin wrote:Thanks for your reply. I already extracted the contents of the file butCarl Fischer wrote:Looks like a long known problem. You might want to extract content of the exe file. And use msiexec directly on the .msi file that's inside that archive.Output from attempted installation:
[carl@carl-macbook:~]% wine '/home/carl/OperaDownloads/MTSDK_v3.0.2/MTSDK_v3.0.2.exe'
Usage:
Install a product:
msiexec {package|productcode} [property]
msiexec /i {package|productcode} [property]
there is no .msi file inside, or any other archives that I can see.
--
Carl
Hint :
$ dd if=MTSDK_v3.0.2.exe of=MTSDK_v3.0.2.msi bs=512 skip=488
464190+1 records in
464190+1 records out
237665656 bytes (238 MB) copied, 19.703 s, 12.1 MB/s
Sylvain@vincentx64 ~/My Documents
$ file MTSDK_v3.0.2.msi
MTSDK_v3.0.2.msi: Microsoft Installer
failed autoexecutable msi installer
On Tue, 2008-05-06 at 08:38 -0500, Usurp wrote:
'msiexec /i file.msi'.
I wouldn't have found that on my own but I think I can "reverse
engineer" your solution
1) Grep for "Microsoft Installer" in /usr/share/file/magic.
Find \xD0\xCF\x11\xE0\xA1\xB1\x1A\xE1\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x3E\x00\x03\x00\xFE\xFF Microsoft Installer
2) hexedit MTSDK_v3.0.2.exe
Search for D0CF11...
Found at 0x3D000 (249856) just after a load of PADDING bytes.
Block size is 512 so 249856/512 = 488 blocks.
3) Use dd to extract the msi file.
Did you do something like that?
All I did previously was run cabextract but that extracts the contents
of the msi file too instead of just removing the extra header.
Anyway thanks for your help, I've learnt something today.
--
Carl
Thanks a lot. That worked and the msi file seems to install ok withThere is a msi installer inside that file at offset 249586.
Hint :
$ dd if=MTSDK_v3.0.2.exe of=MTSDK_v3.0.2.msi bs=512 skip=488
464190+1 records in
464190+1 records out
237665656 bytes (238 MB) copied, 19.703 s, 12.1 MB/s
'msiexec /i file.msi'.
I wouldn't have found that on my own but I think I can "reverse
engineer" your solution
1) Grep for "Microsoft Installer" in /usr/share/file/magic.
Find \xD0\xCF\x11\xE0\xA1\xB1\x1A\xE1\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x3E\x00\x03\x00\xFE\xFF Microsoft Installer
2) hexedit MTSDK_v3.0.2.exe
Search for D0CF11...
Found at 0x3D000 (249856) just after a load of PADDING bytes.
Block size is 512 so 249856/512 = 488 blocks.
3) Use dd to extract the msi file.
Did you do something like that?
All I did previously was run cabextract but that extracts the contents
of the msi file too instead of just removing the extra header.
Anyway thanks for your help, I've learnt something today.
--
Carl
failed autoexecutable msi installer
On Tue, 2008-05-06 at 15:44 +0100, Carl Fischer wrote:
key I can't get to the next step in the installation despite clicking
Next and hitting Return several times.
[carl@carl-macbook:~]% wine msiexec /i MTSDK_v3.0.2.msi
fixme:advapi:LookupAccountNameW (null) L"carl" (nil) 0x32f7fc (nil) 0x32f800 0x32f7f4 - stub
fixme:advapi:LookupAccountNameW (null) L"carl" 0x12eb00 0x32f7fc 0x1525a0 0x32f800 0x32f7f4 - stub
fixme:msi:msi_unimplemented_action_stub MigrateFeatureStates -> 4 ignored L"Upgrade" table values
fixme:msi:ControlEvent_HandleControlEvent unhandled control event L"ValidateProductID" arg(L"0")
fixme:msi:ControlEvent_HandleControlEvent unhandled control event L"ValidateProductID" arg(L"0")
fixme:msi:ControlEvent_HandleControlEvent unhandled control event L"ValidateProductID" arg(L"0")
fixme:msi:ControlEvent_HandleControlEvent unhandled control event L"ValidateProductID" arg(L"0")
Any more advice?
Thanks.
--
Carl
I spoke too soon. The msi file runs but after I enter the registrationThanks a lot. That worked and the msi file seems to install ok with
'msiexec /i file.msi'.
key I can't get to the next step in the installation despite clicking
Next and hitting Return several times.
[carl@carl-macbook:~]% wine msiexec /i MTSDK_v3.0.2.msi
fixme:advapi:LookupAccountNameW (null) L"carl" (nil) 0x32f7fc (nil) 0x32f800 0x32f7f4 - stub
fixme:advapi:LookupAccountNameW (null) L"carl" 0x12eb00 0x32f7fc 0x1525a0 0x32f800 0x32f7f4 - stub
fixme:msi:msi_unimplemented_action_stub MigrateFeatureStates -> 4 ignored L"Upgrade" table values
fixme:msi:ControlEvent_HandleControlEvent unhandled control event L"ValidateProductID" arg(L"0")
fixme:msi:ControlEvent_HandleControlEvent unhandled control event L"ValidateProductID" arg(L"0")
fixme:msi:ControlEvent_HandleControlEvent unhandled control event L"ValidateProductID" arg(L"0")
fixme:msi:ControlEvent_HandleControlEvent unhandled control event L"ValidateProductID" arg(L"0")
Any more advice?
Thanks.
--
Carl
failed autoexecutable msi installer
On Wed, May 7, 2008 at 3:18 AM, Carl Fischer <[email protected]> wrote:
Time to file a bug at http://bugs.winehq.org, I think.I spoke too soon. The msi file runs but after I enter the registration
key I can't get to the next step in the installation despite clicking
Next and hitting Return several times.
failed autoexecutable msi installer
On Wed, 2008-05-07 at 07:50 -0700, Dan Kegel wrote:
http://bugs.winehq.org/show_bug.cgi?id=13054
--
Carl
Done.On Wed, May 7, 2008 at 3:18 AM, Carl Fischer <[email protected]> wrote:Time to file a bug at http://bugs.winehq.org, I think.I spoke too soon. The msi file runs but after I enter the registration
key I can't get to the next step in the installation despite clicking
Next and hitting Return several times.
http://bugs.winehq.org/show_bug.cgi?id=13054
--
Carl