http://bugs.winehq.org/show_bug.cgi?id=22784
Summary: InstallShield: Fails with ole errors Product: Wine Version: 1.1.44 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ole32 AssignedTo: wine-bugs@winehq.org ReportedBy: vanoudt@gmail.com
Created an attachment (id=28112) --> (http://bugs.winehq.org/attachment.cgi?id=28112) ole debug log
When trying to run the Pradis ( http://appdb.winehq.org/objectManager.php?sClass=version&iId=11417 ) InstallSHield installer, it fails with a whole swag of ole errors, popping up a dialog box saying "1608: Unable to create InstallDriver instance, Return code: -2147467262"
Manually running regsvr32 ole32 removes some of the err: log entries, but with no real effect.
A WINEDEBUG=+ole log is attached.
Running on the latest git (wine-1.1.44-143-g2ba53f4) with wine32
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #1 from Andrew Nguyen arethusa26@gmail.com 2010-05-19 23:56:05 --- wine-1.1.44-143-g2ba53f4 is not the latest Git as of today. In any case, assuming that http://www.zondervan.com/media/software/pradis6_01_0024.exe is the installer you were testing, I can't reproduce a problem with the installer in a clean Wine prefix; it seems to succeed for me.
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #2 from Andrew Nguyen arethusa26@gmail.com 2010-05-19 23:56:41 --- I forgot to mention that I was using wine-1.1.44-322-g5cc00e8.
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #3 from Nicholas van Oudtshoorn vanoudt@gmail.com 2010-05-20 00:23:20 --- Oops - seems there was a problem in my Wow64 build script (only the wine64 bits were being updated!)
Yes, that's the installer I was talking about. However, with a fresh wineprefix running wine-1.1.44-322-g5cc00e8, the installer still fails for me. (still with ole errors). The attached log (no WINEDEBUG options set) shows what it's complaining about.
The difference here is that the Installshield error reads "1628: Failed to complete installation"
http://bugs.winehq.org/show_bug.cgi?id=22784
Nicholas van Oudtshoorn vanoudt@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #28112|0 |1 is obsolete| |
--- Comment #4 from Nicholas van Oudtshoorn vanoudt@gmail.com 2010-05-20 00:24:26 --- Created an attachment (id=28114) --> (http://bugs.winehq.org/attachment.cgi?id=28114) standard debug output of the installer
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #5 from Nicholas van Oudtshoorn vanoudt@gmail.com 2010-05-20 00:31:27 --- Created an attachment (id=28115) --> (http://bugs.winehq.org/attachment.cgi?id=28115) alternative standard debug output of the installer
Strangeness here. Seems to intermittently alternate between this new stderr output and the previous attachment(28114: standard debug output of the installer). The previous log shows wine throwing a "wine: invalid address" error, but this new log shows it throwing some ole errors.
http://bugs.winehq.org/show_bug.cgi?id=22784
Nicholas van Oudtshoorn vanoudt@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #28115|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=22784
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|InstallShield: Fails with |Pradis installer fails with |ole errors |ole errors
http://bugs.winehq.org/show_bug.cgi?id=22784
Nicholas van Oudtshoorn vanoudt@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|ole32 |windowscodecs
--- Comment #6 from Nicholas van Oudtshoorn vanoudt@gmail.com 2010-05-20 08:26:52 --- Have done some more detailed testing here. Turns out things only go pear-shaped when running a WoW64 wine install.
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2010-05-20 08:53:18 --- (In reply to comment #6)
Have done some more detailed testing here. Turns out things only go pear-shaped when running a WoW64 wine install.
So the app works just fine with standard 32-bit Wine? Is there any reason that you have changed the component?
http://bugs.winehq.org/show_bug.cgi?id=22784
Nicholas van Oudtshoorn vanoudt@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|windowscodecs |ole32
--- Comment #8 from Nicholas van Oudtshoorn vanoudt@gmail.com 2010-05-20 19:18:50 --- yep, the app works perfectly fine with standard 32-bit wine.
About the component... oops! I didn't mean to do that. Setting it back to what it was.
http://bugs.winehq.org/show_bug.cgi?id=22784
Nicholas van Oudtshoorn vanoudt@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|x86 |x86-64
--- Comment #9 from Nicholas van Oudtshoorn vanoudt@gmail.com 2010-05-20 21:02:57 --- Changing Platform to x86-64 - this only occurs on a WoW64 build
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #10 from Nicholas van Oudtshoorn vanoudt@gmail.com 2010-05-20 21:04:59 --- (In reply to comment #8)
yep, the app works perfectly fine with standard 32-bit wine.
About the component... oops! I didn't mean to do that. Setting it back to what it was.
tested on a 64bit vista machine, and it installs fine.
http://bugs.winehq.org/show_bug.cgi?id=22784
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |win64
http://bugs.winehq.org/show_bug.cgi?id=22784
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |minor
--- Comment #11 from Dmitry Timoshkov dmitry@codeweavers.com 2010-05-21 02:10:57 --- There is no an official win64 supporting Wine release, and an obvious solution is to use standard 32-bit Wine -> minor (if not invalid).
http://bugs.winehq.org/show_bug.cgi?id=22784
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|win64 |
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #12 from Dmitry Timoshkov dmitry@codeweavers.com 2010-05-21 02:14:36 --- Regarding win64 keyword removal: this is not a 64-bit application.
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #13 from Nicholas van Oudtshoorn vanoudt@gmail.com 2010-05-21 02:43:25 --- (In reply to comment #11)
There is no an official win64 supporting Wine release, and an obvious solution is to use standard 32-bit Wine -> minor (if not invalid).
True, but I was under the impression that (one of)the big new feature of 1.2 would be a working WoW64 release. If that is the case, would this not be a regression? [I've been running the WoW64 install from git for quite some time now with no problems. (An old install of this app in a wine32 prefix runs perfectly fine using the latest git builds...)]
I don't want to clutter up everybody's time if this is an inappropriate bug...
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #14 from Dmitry Timoshkov dmitry@codeweavers.com 2010-05-21 02:48:58 --- (In reply to comment #13)
I don't want to clutter up everybody's time if this is an inappropriate bug...
This is an appropriate bug, but there are things that needs to to addressed: 1. how did you build and configured Wine? 2. how the Wine prefix have been created? 3. how do you install the application?
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #15 from Nicholas van Oudtshoorn vanoudt@gmail.com 2010-05-21 02:59:29 --- (In reply to comment #14)
(In reply to comment #13)
I don't want to clutter up everybody's time if this is an inappropriate bug...
This is an appropriate bug, but there are things that needs to to addressed:
- how did you build and configured Wine?
- how the Wine prefix have been created?
- how do you install the application?
1. I run the following script to build and configure wine. (Is it right - there's no clear instructions on this in the Wiki)
#!/bin/bash mkdir -p ./wine{32,64} cd wine64 ../wine-git/configure --enable-win64 make depend && make cd ../wine32 ../wine-git/configure --with-wine64=../wine64 make depend && make sudo make install cd ../wine64 sudo make install cd ..
2. Running off an uncreated WINEPREFIX ( export WINEPREFIX=~/.wine-pradis-test ) where the directory ~/.wine-pradis-test doesn't exist
3. I unzipped the installer into its own directory ["mkdir -p ~/PI && cd ~/PI && unzip ~/Downloads/pradis6_01_0024.exe"](I hate those winzipped installers!) and then run the file as normally: "wine ~/PI/PradisInstaller.exe"
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #16 from Nicholas van Oudtshoorn vanoudt@gmail.com 2010-05-21 03:01:34 --- (In reply to comment #15)
(In reply to comment #14)
(In reply to comment #13)
I don't want to clutter up everybody's time if this is an inappropriate bug...
This is an appropriate bug, but there are things that needs to to addressed:
- how did you build and configured Wine?
- how the Wine prefix have been created?
- how do you install the application?
- I run the following script to build and configure wine. (Is it right -
there's no clear instructions on this in the Wiki)
#!/bin/bash mkdir -p ./wine{32,64} cd wine64 ../wine-git/configure --enable-win64 make depend && make cd ../wine32 ../wine-git/configure --with-wine64=../wine64 make depend && make sudo make install cd ../wine64 sudo make install cd ..
- Running off an uncreated WINEPREFIX ( export WINEPREFIX=~/.wine-pradis-test
) where the directory ~/.wine-pradis-test doesn't exist
- I unzipped the installer into its own directory ["mkdir -p ~/PI && cd ~/PI
&& unzip ~/Downloads/pradis6_01_0024.exe"](I hate those winzipped installers!) and then run the file as normally: "wine ~/PI/PradisInstaller.exe"
Oh, and I've also tried running it without the install step from the wine32 directory.
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #17 from Nicholas van Oudtshoorn vanoudt@gmail.com 2010-05-21 03:19:11 --- Done a bit more fiddling (and looking at +relay) logs. The install seems to crash when running c:\Program Files\Common Files\InstallShield\Driver\11\Intel 32\ISBEW64.exe
Running that manually produces exactly the same crash.
http://bugs.winehq.org/show_bug.cgi?id=22784
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #28112|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=22784
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #28114|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #18 from Dmitry Timoshkov dmitry@codeweavers.com 2010-05-21 03:42:27 --- http://wiki.winehq.org/Wine64 has some instructions how to build a shared 32/64-bit setup.
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #19 from Nicholas van Oudtshoorn vanoudt@gmail.com 2010-05-21 03:49:24 --- (In reply to comment #18)
http://wiki.winehq.org/Wine64 has some instructions how to build a shared 32/64-bit setup.
Yep - that's what I based my install script on [I tidied it up a bit wrt mkdir though] There's no mention of how to *install* the shared 32/64-bit setup on that page though... am I right in thinking it's like I've done:
# having just compiled wine32, in wine32 directory sudo make install cd ../wine64 sudo make install
?
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #20 from Dmitry Timoshkov dmitry@codeweavers.com 2010-05-21 04:19:26 --- There is another page http://wiki.winehq.org/Wine64ForPackagers which clarifies where 32/64-bit parts need to be installed.
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #21 from Alexandre Julliard julliard@winehq.org 2010-05-21 06:54:41 --- (In reply to comment #20)
There is another page http://wiki.winehq.org/Wine64ForPackagers which clarifies where 32/64-bit parts need to be installed.
Yes but make install takes care of that.
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #22 from Austin English austinenglish@gmail.com 2012-03-19 14:52:56 CDT --- This is your friendly reminder that there has been no bug activity for 650 days. Is this still an issue in current (1.4 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=22784
--- Comment #23 from Nicholas van Oudtshoorn vanoudt@gmail.com 2012-03-22 21:27:30 CDT --- Yes - this is still an issue in the latest git. Installation only works when run with WINEARCH=win32 in a clean prefix.
http://bugs.winehq.org/show_bug.cgi?id=22784
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |win64
http://bugs.winehq.org/show_bug.cgi?id=22784
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |focht@gmx.net Resolution| |DUPLICATE Summary|Pradis installer fails with |Pradis installer fails with |ole errors |ole errors (Install Shield | |engine fails in 64bit | |WINEPREFIX)
--- Comment #24 from Anastasius Focht focht@gmx.net 2012-04-22 15:42:45 CDT --- Hello,
this looks like bug 24611 (Install Shield fails on 64bit multilib wine if WINEPREFIX was created by 64bit wine).
InstallShield Engine:
--- snip --- $ pwd /home/focht/.wine/drive_c/Program Files (x86)/Common Files/InstallShield/Driver/11/Intel 32
$ file * ID: empty IDriver2.exe: PE32 executable (GUI) Intel 80386, for MS Windows IDriver.exe: PE32 executable (GUI) Intel 80386, for MS Windows IDriverT.exe: PE32 executable (GUI) Intel 80386, for MS Windows iGdiCnv.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows ISBEW64.exe: PE32+ executable (GUI) x86-64, for MS Windows ISBEW64.tlb: data IScrCnv.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows _ISRES1033.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows ISRT.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows IUserCnv.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows objpscnv.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows --- snip ---
32-bit installer:
--- snip --- 0043:Starting process L"Z:\home\focht\Downloads\xxx\setup.exe" (entryproc=0x41e77c) ... 0024:Call msi.MsiInstallProductA(0032be30 "C:\users\focht\Temp\_is1ffa\ISScript11.Msi",0044a5e0 "REBOOT=ReallySuppress ADDLOCAL=ISScript,ISScript64A") ret=0040e208 ... 0043:Call advapi32.RegCreateKeyW(80000000,001c32d0 L"Interface\{36645116-7766-46CF-8235-B363BDCBC5F3}",0032b1f8) ret=7de36809 0043:Ret advapi32.RegCreateKeyW() retval=00000000 ret=7de36809 ... 0043:Call advapi32.RegCreateKeyW(80000000,001c32b0 L"Interface\{36645116-7766-46CF-8235-B363BDCBC5F3}\ProxyStubClsid",0032b1f8) ret=7de36809 0043:Ret advapi32.RegCreateKeyW() retval=00000000 ret=7de36809 ... 0043:Call advapi32.RegCreateKeyW(80000000,001c2db0 L"Interface\{36645116-7766-46CF-8235-B363BDCBC5F3}\ProxyStubClsid32",0032b1f8) ret=7de36809 0043:Ret advapi32.RegCreateKeyW() retval=00000000 ret=7de36809 ... 0043:Call advapi32.RegCreateKeyW(80000000,001c2ed0 L"Interface\{36645116-7766-46CF-8235-B363BDCBC5F3}\TypeLib",0032b1f8) ret=7de36809 0043:Ret advapi32.RegCreateKeyW() retval=00000000 ret=7de36809 ... 0034:Call KERNEL32.CreateProcessW(0023f500 L"C:\windows\system32\rpcss.exe",0023f500 L"C:\windows\system32\rpcss.exe",00000000,00000000,00000000,3900000000,00000000,00000000,0023f710,0023f780) ret=7f24fdc35bfe ... 0039:Call KERNEL32.__wine_kernel_init() ret=7fbbe801c63e 0034:Ret KERNEL32.CreateProcessW() retval=00000001 ret=7f24fdc35bfe ... 0034:trace:ole:CoGetPSClsid () riid={36645116-7766-46cf-8235-b363bdcbc5f3}, pclsid=0x23e010 0034:Call advapi32.RegOpenKeyExW(ffffffff80000000,0023de30 L"Interface\{36645116-7766-46CF-8235-B363BDCBC5F3}\ProxyStubClsid32",00000000,00020019,0023ddd0) ret=7f24fdbff5f2 0034:Ret advapi32.RegOpenKeyExW() retval=00000002 ret=7f24fdbff5f2 0034:warn:ole:CoGetPSClsid No PSFactoryBuffer object is registered for IID {36645116-7766-46cf-8235-b363bdcbc5f3} 0034:err:ole:marshal_object couldn't get IPSFactory buffer for interface {36645116-7766-46cf-8235-b363bdcbc5f3} --- snip ---
ORCA:
--- snip --- Registry536 0 Interface{36645116-7766-46CF-8235-B363BDCBC5F3}\ProxyStubClsid {00020424-0000-0000-C000-000000000046} ISBEW64.tlb Registry537 0 Interface{36645116-7766-46CF-8235-B363BDCBC5F3}\ProxyStubClsid32 {00020424-0000-0000-C000-000000000046} ISBEW64.tlb Registry538 0 Interface{36645116-7766-46CF-8235-B363BDCBC5F3}\TypeLib {A3A8C7E0-1676-4494-9A1A-BB2F340EB860} ISBEW64.tlb Registry539 0 Interface{36645116-7766-46CF-8235-B363BDCBC5F3}\TypeLib Version 1.0 ISBEW64.tlb Registry540 0 TypeLib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860} ISBEW64.tlb Registry541 0 TypeLib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860}\1.0 ISENG64Lib ISBEW64.tlb Registry542 0 TypeLib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860}\1.0\0 ISBEW64.tlb Registry543 0 TypeLib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860}\1.0\0\win32 [!isbew64.tlb] ISBEW64.tlb Registry544 0 TypeLib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860}\1.0\FLAGS 0 ISBEW64.tlb Registry545 0 TypeLib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860}\1.0\HELPDIR [INTEL_32] ISBEW64.tlb --- snip ---
Interface keys get added only to 32 bits registry:
--- snip --- HKEY_CLASSES_ROOT\Wow6432Node\Interface{36645116-7766-46CF-8235-B363BDCBC5F3} HKEY_LOCAL_MACHINE\Software\Classes\Wow6432Node\Interface{36645116-7766-46CF-8235-B363BDCBC5F3} HKEY_LOCAL_MACHINE\Software\Wow6432Node\Classes\Interface{36645116-7766-46CF-8235-B363BDCBC5F3} --- snip ---
The typelib part is added to 32 and 64 bits registry:
--- snip --- HKEY_CLASSES_ROOT\Typelib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860} HKEY_LOCAL_MACHINE\Software\Classes\Typelib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860} ... HKEY_CLASSES_ROOT\Wow6432Node\TypeLib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860} HKEY_LOCAL_MACHINE\Software\Classes\Wow6432Node\TypeLib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860} HKEY_LOCAL_MACHINE\Software\Wow6432Node\Classes\TypeLib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860} --- snip ---
Adding the missing Interface to 64 bits registry gets it further:
--- snip --- 0042:trace:ole:CoGetPSClsid () riid={36645116-7766-46cf-8235-b363bdcbc5f3}, pclsid=0x23e010 0042:Call advapi32.RegOpenKeyExW(ffffffff80000000,0023de30 L"Interface\{36645116-7766-46CF-8235-B363BDCBC5F3}\ProxyStubClsid32",00000000,00020019,0023ddd0) ret=7feaf28e35f2 0042:Ret advapi32.RegOpenKeyExW() retval=00000000 ret=7feaf28e35f2 0042:Call advapi32.RegQueryValueW(00000070,00000000,0023dde0,0023dddc) ret=7feaf28e3697 0042:Ret advapi32.RegQueryValueW() retval=00000000 ret=7feaf28e3697 0042:Call advapi32.RegCloseKey(00000070) ret=7feaf28e36c3 0042:Ret advapi32.RegCloseKey() retval=00000000 ret=7feaf28e36c3 0042:trace:ole:__CLSIDFromString L"{00020424-0000-0000-C000-000000000046}" -> 0x23e010 0042:trace:ole:CoGetPSClsid () Returning CLSID={00020424-0000-0000-c000-000000000046} 0042:trace:ole:CoGetClassObject CLSID: {00020424-0000-0000-c000-000000000046},IID: {d5f569d0-593b-101a-b569-08002b2dbf7a} ... 0042:trace:ole:PSFacBuf_CreateStub ({36645116-7766-46cf-8235-b363bdcbc5f3},0x2c4540,0x23e0a0) 0042:Call advapi32.RegOpenKeyA(ffffffff80000000,0023db40 "Interface\{36645116-7766-46cf-8235-b363bdcbc5f3}\Typelib",0023de68) ret=7feaf22b8fc5 0042:Ret advapi32.RegOpenKeyA() retval=00000000 ret=7feaf22b8fc5 0042:Call advapi32.RegQueryValueExA(00000070,00000000,00000000,0023d7a4,0023dda0,0023d7ac) ret=7feaf22b906a 0042:Ret advapi32.RegQueryValueExA() retval=00000000 ret=7feaf22b906a 0042:Call advapi32.RegQueryValueExA(00000070,7feaf23a8bb5 "Version",00000000,0023d7a4,0023dad0,0023d7a8) ret=7feaf22b9116 0042:Ret advapi32.RegQueryValueExA() retval=00000000 ret=7feaf22b9116 0042:Call advapi32.RegCloseKey(00000070) ret=7feaf22b9189 0042:Ret advapi32.RegCloseKey() retval=00000000 ret=7feaf22b9189 0042:Call advapi32.RegQueryValueA(ffffffff80000000,0023dc70 "Typelib\{A3A8C7E0-1676-4494-9A1A-BB2F340EB860}\1.0\0\win64",0023d9c0,0023d7a0) ret=7feaf22b91ec 0042:Ret advapi32.RegQueryValueA() retval=00000002 ret=7feaf22b91ec 0042:err:ole:_get_typeinfo_for_iid Could not get typelib fn? 0042:err:ole:PSFacBuf_CreateStub No typeinfo for {36645116-7766-46cf-8235-b363bdcbc5f3}? 0042:err:ole:marshal_object Failed to create an IRpcStubBuffer from IPSFactory for {36645116-7766-46cf-8235-b363bdcbc5f3} with error 0x80004005 ... --- snip ---
--- snip --- REGEDIT4
[HKEY_CLASSES_ROOT\Typelib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860}] @=""
[HKEY_CLASSES_ROOT\Typelib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860}\1.0] @="ISENG64Lib"
[HKEY_CLASSES_ROOT\Typelib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860}\1.0\0] @=""
[HKEY_CLASSES_ROOT\Typelib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860}\1.0\0\win32] @="C:\PROG~5P2\COMM~CP1\INST~JM1\Driver\11\INTE~MEX\ISBEW64.tlb"
[HKEY_CLASSES_ROOT\Typelib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860}\1.0\FLAGS] @="0"
[HKEY_CLASSES_ROOT\Typelib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860}\1.0\HELPDIR] @="C:\Program Files (x86)\Common Files\InstallShield\Driver\11\Intel 32\"
... --- snip ---
Adding Win64 part get makes the installer work
--- snip [HKEY_CLASSES_ROOT\Typelib{A3A8C7E0-1676-4494-9A1A-BB2F340EB860}\1.0\0\win64] @="C:\PROG~5P2\COMM~CP1\INST~JM1\Driver\11\INTE~MEX\ISBEW64.tlb" --- snip ---
Making this bug a dupe of bug 24611 because that bug is more generic, has more applications (affects all InstallShield engines).
Regards
*** This bug has been marked as a duplicate of bug 24611 ***
http://bugs.winehq.org/show_bug.cgi?id=22784
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #25 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-04-30 14:52:06 CDT --- Closing DUPLICATE bugs.
-
wine-bugs＠winehq.org