msiexec errors with photobook installation
msiexec errors with photobook installation
I am unable to install the programme from photobook.com.my on my Ubuntu 7.10 Gutsy with wine 1.0. Can someone help on this?
The wine is set default to WinXP and there is nothing in new override for library.
Below is the output:
$ wine Desktop/MyPhotoBookInstaller.exe
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
The wine is set default to WinXP and there is nothing in new override for library.
Below is the output:
$ wine Desktop/MyPhotoBookInstaller.exe
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
Sounds like this bug: http://bugs.winehq.org/show_bug.cgi?id=9628
This thread has some workarounds: http://forum.winehq.org/viewtopic.php?t=2454
This thread has some workarounds: http://forum.winehq.org/viewtopic.php?t=2454
better try this one :http://www.winehq.org/pipermail/wine-pa ... 62900.html
probably the fix for this bug (?)
probably the fix for this bug (?)
Yes, you'd have to patch wine's source , and then recompile. However, hopefully that patch will make it into wine's source anyway soon. Then you'd just have to download gitwine, and compile, or wait till next release. Btw, i tested the installer (with patch applied), and there seems to be yet another bug, so i'll open a bugreport for it in bugzilla.qwertymn, What am i suppose to do with the attachment.bin?
I am only using binary of the wine for Linux Ubuntu 7.10. It sounded like I am expected to compile the source. Umm...have NOT done that for wine yet.
Compiling patch for this problem
I think there is a chance this patch may fix an install problem I'm having.
But even though I have been using Linux on and off for the last 10 years (when I started, you had to look at the chip on the video card and enter it during the install) I have managed to avoid compiling from source code.
I've looked in the FAQ, Wiki and the "PACKAGING' file in the documentation folder, but I don't see instructions for someone who is trying to compile from source code for the first time.
I know this is second nature to many of you, but not me.
Can some one point me to a source (no pun intended) where I can read up on this - preferably something designed for a first timer?
BTW, I'm running Fedora 9, Kernel 2.6.26.3 and Wine version 1.1.4.
On an earlier post when I first described my problem, which seems similar to this one, someone responded that they were able to install my application using an older version of Wine, I think 0.9.32. I'd prefer not to go backward if I can help it.
But even though I have been using Linux on and off for the last 10 years (when I started, you had to look at the chip on the video card and enter it during the install) I have managed to avoid compiling from source code.
I've looked in the FAQ, Wiki and the "PACKAGING' file in the documentation folder, but I don't see instructions for someone who is trying to compile from source code for the first time.
I know this is second nature to many of you, but not me.
Can some one point me to a source (no pun intended) where I can read up on this - preferably something designed for a first timer?
BTW, I'm running Fedora 9, Kernel 2.6.26.3 and Wine version 1.1.4.
On an earlier post when I first described my problem, which seems similar to this one, someone responded that they were able to install my application using an older version of Wine, I think 0.9.32. I'd prefer not to go backward if I can help it.
Re: Compiling patch for this problem
I've always found the instructions for regression testing to be the clearest step-by-step guide to compiling Wine. It even has a section on how to apply patches. http://wiki.winehq.org/RegressionTestinggooberpat wrote:I think there is a chance this patch may fix an install problem I'm having.
But even though I have been using Linux on and off for the last 10 years (when I started, you had to look at the chip on the video card and enter it during the install) I have managed to avoid compiling from source code.
I've looked in the FAQ, Wiki and the "PACKAGING' file in the documentation folder, but I don't see instructions for someone who is trying to compile from source code for the first time.
I know this is second nature to many of you, but not me.
Can some one point me to a source (no pun intended) where I can read up on this - preferably something designed for a first timer?
BTW, I'm running Fedora 9, Kernel 2.6.26.3 and Wine version 1.1.4.
On an earlier post when I first described my problem, which seems similar to this one, someone responded that they were able to install my application using an older version of Wine, I think 0.9.32. I'd prefer not to go backward if I can help it.
If you have access to a Windows partition, one thing you could try is installing the program in Windows, then copying its directory to Wine. This can work for programs that keep everything they need in their own directory and don't make a lot of registry entries.nicholas wrote:qwertymn and all,
Thank you for ideas. B4 i try wine compile-install, will wait for the Ubuntu 8.10, for now I it looks like the EXE from the photobook.com.my does not work on WINE. Problem is that the app didnt come with much info on requirements to install.