Forum

Battle.net 64 bit prefix issues

Författare Svar
schotty Thursday 24 November 2016 at 21:40
schotty

OK.  I have been working on this and not getting much of anywhere.

 

I have two prefixes, one 32, the other 64 bit.  The 32 bit prefix works perfectly, but the 64 bit one does not at all (yet).  Once installed BNet will barf out near instantly upon launch.

The CLI differs in one error (both have p11-kit and pulseaudio complaints, but the 32 bit one can run any of the wine capable bnet games just fine):

<html><head><title>Object moved</title></head><body>

<h2>Object moved to <a href="http://www.blizzard.com/404">here</a>.</h2>

</body></html>

<html><head><title>Object moved</title></head><body>

<h2>Object moved to <a href="http://www.blizzard.com/404">here</a>.</h2>

</body></html>

<html><head><title>Object moved</title></head><body>

<h2>Object moved to <a href="http://www.blizzard.com/404">here</a>.</h2>

</body></html>

[POL_Wine] Message: Wine return: 0

I saw a few things online regarding corefonts being the culprit.  Well thats installed via my installation script.  Same for LDAP related issues (I can't think of what pacage I could be missing).

 

OS is RHEL 7.3.

Ändrat av schotty

SomeGuy42 Friday 25 November 2016 at 1:21
SomeGuy42Anonymous

Hi, so I've been playing a bit with the 64bit as well & Bnet. OS Ubuntu 16.04 wine 1.9.23-staging

First off I get that html error you quoted also in my 32bit cli.

I got Bnet to work some of the time in 64 bit, it at first died almost instantly, but after Set_OS "win10" it actually worked albeit not every time. I ran it for quite a while, download some game files and whatnot. Only tested actual playing D3 PTR (64bit), it tried to run but the new 64bit update uses DX11 which probably won't ever work in wine.... but Bnet itself seemed to be ok, outside the fact that sometimes it would still die right away when launching. Will do some more testing...

schotty Friday 25 November 2016 at 2:44
schotty

Thanks for the input here.  I made the x86 version of the PoL script for BNet, and would like to hammer out an amd64 one.  Just not sure if I have it with that error cropping up or not.  I am willing to put money on it being a system library, but as with many things Wine, not necessarily the case :D

SomeGuy42 Friday 25 November 2016 at 19:16
SomeGuy42Anonymous

The error for me on app fail is: (only staging shows this for me)

err:seh:setup_exception_record stack overflow 1152 bytes in thread 00ca eip 7bc4bae3 esp 0b0f0eb0 stack 0xb0f0000-0xb0f1000-0xb1f0000

Well I think you're right cause after starting a fresh batch of some testing, looks like Dx11 is playing a role in the 64bit cli as well. Either that or just because the system is x64 it automatically looks for it... I noticed a few dx11 calls in the debug window that I didn't notice in the 32bit prefix. After installing d3dx11 (POL call)(which is what I was doing before to test the new D3) I get the semi-consistent loading of B-net, maybe 66% of the time it works.

So I'm running these settings:
win10 (not sure if it matters but xp doesn't natively run Dx11 so not using it here, I'm also turning off Browser hardware accel. in Bnet)
POL_Install_d3dx11
64bit 1.9.23-staging (non-staging also seems to work, just 'seem' to get more debug info)
libs: "native,builtin" (noticed quite a few errors about them otherwise and less consistent app startage)
msvcp140
ucrtbase
vcruntime140
(+d3dx11_42 & 43 that are auto-added by d3dx11 install)

Hopefully this is helpful and I'm curious how your testing goes

schotty Saturday 26 November 2016 at 22:09
schotty

Thanks for those tips.  Unfortunately I am still getting the same 404 error.

 

 andrew  ~  Desktop  /usr/share/playonlinux/playonlinux --run "Battle.Net" %F
Looking for python... 2.7.5 - wxversion(s): 2.8-gtk2-unicode
selected
[main] Message: PlayOnLinux (4.2.10) is starting
[clean_tmp] Message: Cleaning temp directory
Script started /home/andrew/.PlayOnLinux/shortcuts/Battle.Net
[POL_System_CheckFS] Message: Checking filesystem for Battle.net Launcher.exe
[POL_Wine] Message: Running wine-1.9.23 Battle.net Launcher.exe %F (Working directory : /home/andrew/.PlayOnLinux/wineprefix/battle.net/drive_c/Program Files (x86)/Battle.net)
[POL_Wine] Message: Notice: PlayOnLinux deliberately disables winemenubuilder. See http://www.playonlinux.com/fr/page-26-Winemenubuilder.html
ERROR: ld.so: object '/usr/lib64/pulseaudio/libpulsedsp.so' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object '/usr/lib64/pulseaudio/libpulsedsp.so' from LD_PRELOAD cannot be preloaded: ignored.
p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="http://www.blizzard.com/404">here</a>.</h2>
</body></html>
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="http://www.blizzard.com/404">here</a>.</h2>
</body></html>
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="http://www.blizzard.com/404">here</a>.</h2>
</body></html>
[POL_Wine] Message: Wine return: 0

 

SomeGuy42 Monday 20 February 2017 at 13:19
SomeGuy42Anonymous

try the wine 2.1 staging, works much better for me, even can play d3 in 64bit mode, although performance is very very bad.