I have two legit cdkeys. I run them off the same computer since the games are in 2 different folders and I use 2 different user accounts. I would run one game in one account sign on to b.net make a game etc. Then hit windows key and L key to switch to 2nd user accnt run the second game/cd key and log onto b.net and join my game I made on first acct. Then switch back and forth as needed.

It was all very convenient. It boosted experience, made muling safer, made it easier to pull a mule along with playing characters for xtra socket and forge quests. It worked fine last ladder and worked as early as this morning.

However this afternoon when I log on to b.net the new patch loads. Ok fine I switch to second user account and game and patch that 1 up too.

But NOW if I am logged in on b.net with 1 account and try getting on with 2nd cdkey it locks up and that game cant connect. And it doesnt matter which order I do it in. If I am on user acct b first log on 2 bnet then switch to user account a a cant log on. But if I start on user acct a and log on first then swtich to b and try -- b cant log on :/.

So it doesnt matter which account/cd key I use. Either one CAN log on to b.net just fine as long as the other account isnt on b.net first.

Anyone else having similar problems? And more importantly (hopefully) found a solution?

I will need to try when I get home. I usually play with 3-4 chars at a time to benefit from XP increase and not have to go into pub games too often. However I do use 3-4 computers when I do it, no virtual logins.

This is the way that I did it with Sandboxie. I like this better than making multiple copies of the entire installation because thats wasteful, and this will keep your ignore list no matter which sandboxie you are using.

The snippet at the bottom to create a custom link is also helpful.

1. Create a new Sandbox in Sandboxie (ex: Key2)
2. Configure the new Sandbox
2a. Check "Show sandbox name in window title"
2b. File Migration change value to 524288 (Sandboxie needs to copy d2char.mpq)
2c. Restrictions - uncheck "Drop Rights" (allows use of CDKey changer)
3. Launch Diablo 2 from Sandboxie (use of -w is recommended)
4. Log in to bnet, select a character, and exit
5. Launch Serbys CDKey changer from Sandboxie, change key
6. Repeat this process for each key you would like to use in sandboxie

I don't think so either. Since I got a couple of sets of CD-keys for this ladder I would really appreciate if somebody that uses multiple copies on one computer (legit) could post a quick guide. This will save me some time and give you a better conscience!

I don't think so either. Since I got a couple of sets of CD-keys for this ladder I would really appreciate if somebody that uses multiple copies on one computer (legit) could post a quick guide. This will save me some time and give you a better conscience!

Click to expand...

Basically just install with one keyset, rename the folder (something which doesn't start with the words "Diablo II", that doesn't seem to work) Then install again with second keyset. Run other one normall, right click the other and "run sandboxed"

Right-click the diablo icon and select "run sandboxed". If you also press alt, the dialog about selecting a sandbox will be skipped as well and the default one will be used.

On my computer, a warning about a dropped request thingy appears when starting the game in a sandbox, but that might be a matter of my gfx card driver. If it happens on your computer as well, you can ignore it.