[Bug 35056] New:=?UTF-8?Q?=20Pro=E2=81=84Engineer=20Wildfire=205?=.0: Fails to start installation
http://bugs.winehq.org/show_bug.cgi?id=35056
Bug #: 35056 Summary: Pro⁄Engineer Wildfire 5.0: Fails to start installation Product: Wine Version: 1.7.7 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: lukasz.wojnilowicz@gmail.com Classification: Unclassified
Created attachment 46746 --> http://bugs.winehq.org/attachment.cgi?id=46746 WINEDEBUG=+relay,+seh,+tid on wine-1.7.7-107-g61358d0
Steps to reproduce: 1) remove ~/.wine 2) wine setup.exe
Behaviour: Nothing.
Expected behaviour: Something.
http://bugs.winehq.org/show_bug.cgi?id=35056
NSLW lukasz.wojnilowicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Installer
http://bugs.winehq.org/show_bug.cgi?id=35056
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net Summary|Pro⁄Engineer Wildfire 5.0: |64-bit PTC Pro Engineer |Fails to start installation |Wildfire V5 installer fails
--- Comment #1 from Anastasius Focht focht@gmx.net 2013-12-05 13:36:30 CST --- Hello folks,
just a hint: try to pre-create the WINEPREFIX using some Wine builtin.
85% of this relay log is just prefix creation/builtins, mainly winemenubuilder -> not very useful.
Additionally multhreading/parallel process startup causes interleaving/corrupted message lines -> try to use 'append' mode.
1) new prefix -> 'notepad', 'winecfg' whatever. Wait until prefix creation finished 2) start the installer as follows:
--- snip --- $ WINEDEBUG=+tid,+seh,+relay wine ./foo.exe >>log.txt 2>&1 --- snip ---
Judging from the log ... this is 64-bit PTC Pro product installer?
Regards
http://bugs.winehq.org/show_bug.cgi?id=35056
NSLW lukasz.wojnilowicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #46746|0 |1 is obsolete| |
--- Comment #2 from NSLW lukasz.wojnilowicz@gmail.com 2013-12-05 13:54:41 CST --- Created attachment 46747 --> http://bugs.winehq.org/attachment.cgi?id=46747 WINEDEBUG=+relay,+seh,+tid on wine-1.7.7-107-g61358d0 v2
(In reply to comment #1)
Hello folks,
just a hint: try to pre-create the WINEPREFIX using some Wine builtin.
85% of this relay log is just prefix creation/builtins, mainly winemenubuilder -> not very useful.
Additionally multhreading/parallel process startup causes interleaving/corrupted message lines -> try to use 'append' mode.
- new prefix -> 'notepad', 'winecfg' whatever. Wait until prefix creation
finished 2) start the installer as follows:
--- snip --- $ WINEDEBUG=+tid,+seh,+relay wine ./foo.exe >>log.txt 2>&1 --- snip ---
Judging from the log ... this is 64-bit PTC Pro product installer?
Regards
I did as you've told but the log is the same size though. Yes it's 64 bit installer and my wine is WoW compilation.
http://bugs.winehq.org/show_bug.cgi?id=35056
--- Comment #3 from Anastasius Focht focht@gmx.net 2013-12-05 14:12:30 CST --- Hello Lukasz,
--- quote --- I did as you've told but the log is the same size though. Yes it's 64 bit installer and my wine is WoW compilation. --- quote ---
The log starts with creation of WINEPREFIX again. You must be doing something wrong then.
For example if you filter out 'winemenubuilder' process which is thread id=000d from the log:
--- snip --- $ du -h +relay.txt 9.7M +relay.txt --- snip ---
--- snip --- $ grep -v "000d:" +relay.txt > new_relay.txt
$ du -h new_relay.txt 728K new_relay.txt --- snip ---
and it still contains all necessary information.
Anyway, this seems to be the culprit:
--- snip --- ... 0024:Call KERNEL32.CreateProcessA(00000000,0033f428 "Z:\home\WINEUSER\virtual-drives\1\dsrc\i486_nt\obj\ptcsetup.exe ",00000000,00000000,00000000,00000008,00000000,00000000,0033fc58,0033fc48) ret=004101a8 0024:Ret KERNEL32.CreateProcessA() retval=00000000 ret=004101a8 0024:Call user32.WaitForInputIdle(0033fc60,00015f90) ret=0040aefc 0024:Ret user32.WaitForInputIdle() retval=ffffffff ret=0040aefc 0024:Call KERNEL32.ExitProcess(00000000) ret=0040afdc ... --- snip ---
'ptcsetup.exe' is probably the main installer but it can't be found within your mounted disk/iso image? Can you check if the executable is present somewhere else?
Also run the 'file' command on the executables found so one can see if this 32-bit or 64-bit PE.
Regards
http://bugs.winehq.org/show_bug.cgi?id=35056
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|-unknown |programs Summary|64-bit PTC Pro Engineer |64-bit PTC Pro Engineer |Wildfire V5 installer fails |Wildfire V5 installer fails | |(64-bit processors not | |reported in volatile | |hardware registry keys) Ever Confirmed|0 |1
--- Comment #4 from Anastasius Focht focht@gmx.net 2013-12-05 15:00:20 CST --- Hello Lukasz,
I think I know what they are trying to do ...
--- snip --- ... 0024:Call KERNEL32.GetSystemInfo(0033daa4) ret=00409f50 0024:Ret KERNEL32.GetSystemInfo() retval=0033daa4 ret=00409f50 0024:Call advapi32.RegOpenKeyA(80000002,00439538 "HARDWARE\DESCRIPTION\System\CentralProcessor\0",0033dad8) ret=00410d05 0024:Ret advapi32.RegOpenKeyA() retval=00000000 ret=00410d05 0024:Call advapi32.RegQueryValueExA(00000030,0043952c "Identifier",00000000,0033dac8,0033d610,0033dacc) ret=00410f04 0024:Ret advapi32.RegQueryValueExA() retval=00000000 ret=00410f04 0024:Call advapi32.RegCloseKey(00000030) ret=0040a0a4 0024:Ret advapi32.RegCloseKey() retval=00000000 ret=0040a0a4 ... 0024:Call KERNEL32.FindFirstFileA(0033f028 "Z:\home\WINEUSER\virtual-drives\1\dsrc\i486_nt",0033eee8) ret=00410340 0024:Ret KERNEL32.FindFirstFileA() retval=0012ff40 ret=00410340 0024:Call KERNEL32.FindClose(0012ff40) ret=0040a986 0024:Ret KERNEL32.FindClose() retval=00000001 ret=0040a986 --- snip ---
It's basically this scheme: http://support.microsoft.com/kb/556009
--- quote --- You can use the following registry location to check if computer is running 32 or 64 bit of Windows Operating System:
HKLM\HARDWARE\DESCRIPTION\System\CentralProcessor\0
You will see the following registry entries in the right pane:
Identifier REG_SZ x86 Family 6 Model 14 Stepping 12 Platform ID REG_DWORD 0x00000020(32)
The above “x86” and “0x00000020(32)” indicate that the Operating System version is 32 bit. --- quote ---
They are either looking for "x86" or the other way around, "AMD64", "Intel64" strings ...
The comment in Wine source indicates an area which needs improvement ;-)
Source: http://source.winehq.org/git/wine.git/blob/57c54bc9ad1e13ee7cd730b2ffb4df834...
--- snip --- 169 static void create_hardware_registry_keys(void) 170 { ... 207 /*TODO: report 64bit processors properly*/ 208 switch(sci.Architecture) 209 { 210 case PROCESSOR_ARCHITECTURE_ARM: 211 sprintfW( idW, ARMCpuDescrW, sci.Level, sci.Revision ); 212 break; 213 default: 214 case PROCESSOR_ARCHITECTURE_INTEL: 215 sprintfW( idW, IntelCpuDescrW, sci.Level, HIBYTE(sci.Revision), LOBYTE(sci.Revision) ); 216 break; 217 } ... 245 for (i = 0; i < NtCurrentTeb()->Peb->NumberOfProcessors; i++) 246 { 247 WCHAR numW[10]; 248 249 sprintfW( numW, PercentDW, i ); 250 if (!RegCreateKeyExW( cpu_key, numW, 0, NULL, REG_OPTION_VOLATILE, 251 KEY_ALL_ACCESS, NULL, &hkey, NULL )) 252 { 253 RegSetValueExW( hkey, FeatureSetW, 0, REG_DWORD, (BYTE *)&sci.FeatureSet, sizeof(DWORD) ); 254 set_reg_value( hkey, IdentifierW, idW ); 255 /*TODO; report ARM and AMD properly*/ 256 set_reg_value( hkey, ProcessorNameStringW, IntelCpuStringW ); ... --- snip ---
Regards
http://bugs.winehq.org/show_bug.cgi?id=35056
--- Comment #5 from NSLW lukasz.wojnilowicz@gmail.com 2013-12-06 10:38:42 CST --- (In reply to comment #4)
Hello Anastasius,
--- quote --- They are either looking for "x86" or the other way around, "AMD64", "Intel64" strings ...
The comment in Wine source indicates an area which needs improvement ;-) --- quote ---
Thanks for finding cause of Wine code failure - now it's known what part of code needs to be flesh out. Have you also analyzed bug #35044 posted by me? It's likewise about 64 bit installer. It's not the same bug but I think it's also an elementary check.
Regards
http://bugs.winehq.org/show_bug.cgi?id=35056
NSLW lukasz.wojnilowicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |minor
--- Comment #6 from NSLW lukasz.wojnilowicz@gmail.com 2013-12-06 10:56:04 CST --- Changing importance to minor as there is workaround. The workaround in my case is: 1) wine regedit 2) go to "HKLM\HARDWARE\DESCRIPTION\System\CentralProcessor\0" 3) change "Identifier" from "x86 Family 6 Model 23 Stepping 6" to "Intel64 Family 6 Model 23 Stepping 6" 4) go to "HKLM\HARDWARE\DESCRIPTION\System\CentralProcessor\1" 5) change "Identifier" from "x86 Family 6 Model 23 Stepping 6" to "Intel64 Family 6 Model 23 Stepping 6"
https://bugs.winehq.org/show_bug.cgi?id=35056
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|programs |registry
https://bugs.winehq.org/show_bug.cgi?id=35056
--- Comment #7 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.51 or newer) wine?
https://bugs.winehq.org/show_bug.cgi?id=35056
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #8 from Fabian Maurer dark.shadow4@web.de --- Any news on this?
-
wine-bugs＠winehq.org -
WineHQ Bugzilla