The Edge of Nowhere

[kemal13]

This is a way to run 2 copies of D2 without any crashes on the same computer.
You need:
2 CD keys for BNet
1 Hex editor


1. Install D2 with key, patch it fully to 1.11 and enter battle.net.
2. Exit Battle.net again
3. copy your whole D2 install to another directory, eg "c:\games\diablo2a"
3. uninstall d2
4. install d2 with the 2nd key

Now you have 2 installs of D2 on your computer but you can't start a 2nd copy since D2 complains that only one copy can be run at the same time.

1. open d2gfx.dll from c:\games\diablo2a in the hexeditor. I used UltraEdit32 for this.
2. search for the bytes "C0 74 45". in Ultraedit: press ctrl-f and make sure the "find ASCII" is UNCHECKED. enter "C0 74 45".
3. the cursor will jump to offset 84ceh. Change the byte "74" to "EB"
4. save d2gfx.dll again

Now the install with the modified d2gfx.dll can be started while the other one is already running. it will work fine. including the usual "diablo ii.exe -w -ns"

[johm]

will the ip restriction be bypassed on this one too or is that the same for anything that does 2 windows?

[kemal13]

What IP restriction? I used this since 1.11 came out without any problems sofar

[OiT]

I think there is a misconception about the IP restriction - there is just something that Blizz has changed that seems to conflict with D2Loader.

I have 2 pc's, and several sets of keys. Of course I can open a session on each PC, without using d2loader.

I also tested and can open a session on each pc WITH d2loader.

BUT, when I open more than one session on 1 PC, the 2nd and subsequent sessions always get c/i within 1 minute!


kemal13 - if I wanted to run more than 2 sessions (like, say 4 on one machine - would I do this with each of sessions 2, 3 & 4 - or 3 & 4 would have to be different?

I have not yet had a chance to test it out for the 2nd session even yet - but will give it a try when I am home from work - thanks for the tip.

[occ-godly]

This does not work, the 2nd installed diablo 2 still drops.

Tested. No Sucess.

[kemal13]

I don't get any disconnections. I've been in game for very long times rushing my own char(s) without any problem.
The first copy of D2 doesn't need any d2gfx.dll editing (but it doesn't hurt either). All additional copies need a modified d2gfx.dll

The downside of my method is, you need approx 1GB diskspace per copy since each copy of D2 needs its own directory.

My guess is this new D2Loader is just a patched 1.10 d2loader which fubars for some reason. possibly a delayed CD copy protection check.

D2 checks with FindWindow for a window with the name "Diablo II". If it finds one it stops with the usual error message. My patch just disables that jump to the error messagebox, rendering that FindWindow call moot and starting D2 no matter if there are already D2 windows or not

[Cauhtemoc]

[minit55]

I have installed on to different HardDisk´s.. one key on each HD and use 1.11 loader on one HD and i can stay in game just FINE...

[jEevion]

Thanks for the great tip Kermal13, had it not been for your post I would have never took the time to get this working again. Your method above worked just fine, but here is what I did to run more than one D2 without losing my connection every 30 seconds, WITH D2Loader

-Copied my current D2 installation into the same directory it was installed in (program files)
-Renamed the two Diablo directories (Diablo IIa, Diablo IIb)
-Installed the 1.11Loader in each installation.
-Sent a shortcut to the desktop from each D2 directory, named them Diablo ONE, Diablo TWO.
-Added the argument -mpq cdkey.mpq in second shortcut (to read the cdkey from cdkey.mpq installed in that directory)

So I guess this means that Blizzard is in fact not disabling multiple instances of Diablo based on IP. I guess each installation of D2 allows for a simultaneous connection to battle.net using a common IP. Hope this information helps.

[lxchar]

sweet so it works all u need is 2 directorys n enuff space for 2 installs of diablo2 yay thanks dude///

[NolF-XeoX]

i've tested that jEevion did work got, but if u use another account to log to ur computer use the second account to run the Diablo IIb and work just fine (with loader)

[jEevion]

NolF-XeoX, are you using a router? If so, my method may not work for you. I have seen many complaints that people with multiple computers connected via a router (common IP address) are unable to stay in a game without getting a C/I. I'm not using a router, and would expect others not using a router to be able to stay in games with more than one character.

[minit55]

I´m in router and have "just" installed on two drives works FINE for me.. for method check post above made by me... GL

[LordTerror]

We are not allowed to post d2loader on this forum, because it is a no CD hack. This is fine though, because it doesn't allow you to run without a CD.

~Stickied.

[Cauhtemoc]

The reason behind Blizzard's bans and realm downs are still largely unknown, but it seems like this particular connection interrupted appears whenever you're trying to use more than copy of the same Diablo installation.

Whether using D2 Loader or not, a separate installation for each Diablo you plan on running should solve the problem. Kemal's way of running two windows work, because he has to use two installations.

So before anyone starts asking about how to avoid connection interrupted, try making a separate installation of Diablo, using either Kemal's method posted above, or simply D2 Loader. It should work, it does for me, and many others.