1.13 PTR with WINE under Linux

Quick question to the group :

Has anyone got this working? I have had no trouble with previous D2 patches up to and including 1.12, using D2 under WINE with (in this case) Ubuntu 9.10 "Karmic Koala", but when I try to pick the "Classic Beta" realm, the Blizzard updater consistently aborts with a "... cannot open file... d2exp.mpq" error, even though the .mpq file is clearly there. (Note : Due to how this particular PC is set up, D2 is not installed in the standard WINE "\Program Files" directory... I wonder if that has something to do with it? Maybe the patch freaks out if it doesn't find your Diablo files in the default location?)

I have tried various modifications to the WINE registry and have followed the steps suggested in other Forums, but no luck so far. It's too bad that they don't seem to have a downloadable, stand-alone patch .exe for the 1.13 PTR test, because I have had better results with that kind of patch and D2 under WINE in the past.

Any suggestions would be welcomed...

Cheers

Mr. Bill|||I had to patch in windows because it didnt work through ubuntu and wine. If you're not dual booted I'm not sure i can help.|||Try to create link in the default directory?|||Quote:








Try to create link in the default directory?




Tried that.

I think this is either a bug in the on-line installer (although I noticed that it downloads an .exe into your D2 folder), or something strange about how WINE translates the Linux "/" path delimiter to the equivalent Windows "\" character.

What is weird and frustrating about it is, this particular instance of D2 under WINE on this particular computer, had no trouble with the 1.12 patch... so clearly something is different with the 1.13 PTR thing.

Has anyone been able to get the 1.13 PTR patch working with an instance of D2 under "normal" Windows XP, but with D2 not in the default "C\Program Files\Diablo II" folder?

Cheers

Mr. Bill|||Quote:








Has anyone been able to get the 1.13 PTR patch working with an instance of D2 under "normal" Windows XP, but with D2 not in the default "C\Program Files\Diablo II" folder?




I had 1.13a working in
Code:

"E:\diablo\Diablo II"

without a hitch on XP.

I haven't bothered with 1.13b yet due to SCII beta ~_~

Edit to add code tags as is a colon followed by a backslash, not a face.|||Quote:








I had 1.13a working in
Code:

"E:\diablo\Diablo II"

without a hitch on XP.

I haven't bothered with 1.13b yet due to SCII beta ~_~

Edit to add code tags as is a colon followed by a backslash, not a face.




Change your d2 start script to change the working dir to the d2 directory. Works without a hitch.


Code:

#!/bin/sh
export WINEPREFIX=$HOME/.wine-d2b 
cd /mnt/drive_l/Programme/d2b
wine /mnt/drive_l/Programme/d2b/Diablo\ II.exe -skiptobnet

|||i had this same problem, but i found the problem was solved after deleting the various cache files in the d2 folder and the failed patch file. I'd be careful though, just make sure you don't delete the wrong thing.|||Will probably do a full re-install when I upgrade my main computer to Lucid Lynx, "real soon now"... I have three other Ubuntu boxes working fine with 1.13 so this is a "whenever I get around to it" type of thing.

Incidentally, did any of you know that (apparently), D2 LoD doesn't work in XP as a guest OS under VirtualBox (Karmic as host)? It installs fine, even runs the video test, but then simply produces no screen output (at all) when you try to start it up within a virtualized XP session. After much checking back and forth between the Forums and Google, the reason seems to be that VirtualBox doesn't fully support DirectX.

Haven't tried the GLIDE driver, but as D2 works fine under WINE (most of the time), here again there's not much incentive to troubleshoot the whole thing.

Have any of you gotten D2 working under any kind of hypervisor, be it VirtualBox or (say) VMware?

Cheers

Mr. Bill|||Dumb question, what does PTR mean?

Also, with Wine, I just installed D2 and LOD from the downloadable installer from the Blizzard store and had no problems, seems to work in both Wine and Cedega. One sort of major annoyance though, when I ran D2 on my laptop which has an Intel graphics adapter, it seemed to screw up the colors for everything outside D2 even after D2 quits... if anyone has had this happen and fixed it I'd love to know. Oh and if anyone knows how to get it to use 3D/perspective mode that'd be cool too, getting annoying trying to fight monsters I can't see behind opaque walls.|||Quote:








Will probably do a full re-install when I upgrade my main computer to Lucid Lynx, "real soon now"... I have three other Ubuntu boxes working fine with 1.13 so this is a "whenever I get around to it" type of thing.

Incidentally, did any of you know that (apparently), D2 LoD doesn't work in XP as a guest OS under VirtualBox (Karmic as host)? It installs fine, even runs the video test, but then simply produces no screen output (at all) when you try to start it up within a virtualized XP session. After much checking back and forth between the Forums and Google, the reason seems to be that VirtualBox doesn't fully support DirectX.

Haven't tried the GLIDE driver, but as D2 works fine under WINE (most of the time), here again there's not much incentive to troubleshoot the whole thing.

Have any of you gotten D2 working under any kind of hypervisor, be it VirtualBox or (say) VMware?

Cheers

Mr. Bill




I'm no expert here, but I've looked into VMWARE and such, and one thing I can tell you is, the one thing It can't do like a normal pc is any kind of 3d acceleration.

Now I'm not sure if Diablo would work under it... but I would advise against trying. That's one thing people say about virtual boxing, is don't try to game, for that you're better off with a dual boot.