[Bug 31741] python.org 64-bit Python 2.7.3 installer: selecting preferred installation folder does nothing (32-bit bootstrapper process needs custom action script/dll executed in 64-bit server process)

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=31741

--- Comment #8 from Anastasius Focht <focht at gmx.net> ---
Hello tahoar,

--- quote ---
But there are similar problems with Java and Python's 64-bit installers on Wine
as I mentioned in my my last comment.
--- quote ---

then please explain 'similar' on a technical level (with +relay,+msi logs).

FYI just tested the 64-bit installer from Oracle
(http://ghaffarian.net/downloads/Java/JRE/jre-7u45-windows-x64.exe to avoid
that Oracle EULA garbage) and the installation went fine in 64-bit WINEPREFIX.

Run from install folder:

--- snip ---
$ pwd
/home/focht/.wine/drive_c/Program Files/Java/jre7/bin

$ file *.exe
jabswitch.exe:   PE32+ executable (console) x86-64, for MS Windows
javacpl.exe:     PE32+ executable (GUI) x86-64, for MS Windows
java.exe:        PE32+ executable (console) x86-64, for MS Windows
java-rmi.exe:    PE32+ executable (console) x86-64, for MS Windows
javaw.exe:       PE32+ executable (GUI) x86-64, for MS Windows
javaws.exe:      PE32+ executable (GUI) x86-64, for MS Windows
jp2launcher.exe: PE32+ executable (GUI) x86-64, for MS Windows
keytool.exe:     PE32+ executable (console) x86-64, for MS Windows
kinit.exe:       PE32+ executable (console) x86-64, for MS Windows
klist.exe:       PE32+ executable (console) x86-64, for MS Windows
ktab.exe:        PE32+ executable (console) x86-64, for MS Windows
orbd.exe:        PE32+ executable (console) x86-64, for MS Windows
pack200.exe:     PE32+ executable (console) x86-64, for MS Windows
policytool.exe:  PE32+ executable (console) x86-64, for MS Windows
rmid.exe:        PE32+ executable (console) x86-64, for MS Windows
rmiregistry.exe: PE32+ executable (console) x86-64, for MS Windows
servertool.exe:  PE32+ executable (console) x86-64, for MS Windows
ssvagent.exe:    PE32+ executable (GUI) x86-64, for MS Windows
tnameserv.exe:   PE32+ executable (console) x86-64, for MS Windows
unpack200.exe:   PE32+ executable (console) x86-64, for MS Windows

$ wine ./java.exe -version
fixme:heap:HeapSetInformation 0x240000 0 0x23fcb0 4
fixme:heap:HeapSetInformation 0x350000 0 0x23eff0 4
fixme:seh:RtlAddFunctionTable 0x6a0170 1 6a0000: stub
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
--- snip ---

or within 'cmd.exe' shell:

--- snip ---
C:\Program Files\Java\jre7\bin>java -version
fixme:heap:HeapSetInformation 0x240000 0 0x23fcb0 4
fixme:heap:HeapSetInformation 0x350000 0 0x23eff0 4
fixme:seh:RtlAddFunctionTable 0x6a0170 1 6a0000: stub
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
--- snip ---

Your terminal output:

--- snip ---
Z:\home\tahoar\tools\installers>java -version
Can't recognize 'java -version' as an internal or external command, or batch
script.
--- snip ---

This only works if the installation path where the 'java.exe' binary lives is
registered in Windows PATH environment variable.

http://docs.oracle.com/javase/tutorial/essential/environment/paths.html

Please make yourself familiar how Windows/Wine works.

Regards

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.