What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[GUIDE] VMware + D3 | they way it shoud be done

Thank you for the guide, it went very smoothly :).

There are a couple things that may need clarification:
How many CPU cores/threads are recommended per VM?
Once the VM is cloned, you will need to make the shared folders map again for each clone.
Do we simply create a shortcut to our Z: on each VM for DB and D3?
I've noticed that running as a shortcut from Z: may be the issue, but I'm running 4 VM's and when I start up D3 on each, the first two load up quickly and the last two may take about 5-10 minutes each for D3 to start up. Any thoughts on this?
 
shaliuno said:
I go for 1 cpu 2 cores on mine rig

Shortcut to C:\ drive where Diablo 3 and DB stay (because you do mklink)
Click to expand...

Thank you for the response. My mklink'd files on C: show 0 bytes. My folder paths and everything are the same as in the .bat files. Any idea what the issue could be here?
 
shaliuno said:
It is ok, it is the way mklink works.
Click to expand...

Ok, I did try to run it using C:\Diablo III\Diablo III.exe -launch through Start>Run. I receive a Blizzard crash error in Russian. I find it odd because I had started it up before using the US client, never had the RU client installed. The D3 client on VM Host is up to date and working. They also run successfully through Z: on each VM.

Screenshot: Capture.webp
 
offtop, how safe is that to play with main while runnin bot on vmware, is vmware appear as another pc in my network for blizzard?
 
hey can someone please answer me if i can run diablo in a vm with the diablo 3 folder copied to that vm..? it stucks at "updating setup files" when i run it
 
Any word on this updater loop problem? I've tried running from Z:\. Tried running from cmd and cmd -launch. Both get stuck at about 60% of simple "updating setup files".

Thanks for any help!
 
Anyone else who was having the update loop problem listen up! I fixed it by setting all the .exe INCLUDING the .exe in the programdata\battle.net\agent folders to compatibility mode-->Windows XP. Booted up first time no problems. Do this to the .exe on your GUEST machine because you cant do it on VMWARE through your network.
 
@shaliuno THX for this a great guide.

Does anyone tested a vmware for linux?
 
Last edited:
many problems solved when i installed VM tools....... i can play diablo now but my final problem is that i can't change the language to russian i can go to option but its blank...
 
Try this:
run regedit
HKEY_CURRENT_USER\Software\Blizzard Entertainment\Diablo III REG_SZ Locale "enGB" change to ruRU
 
anonbot said:
Anyone using any anti vm detection methods? It's very easy to detect if you are running inside of vmware. Video card and hdd driver names have the word "vmware" in them. Also calling specific op codes canl tell a program if its running inside of vmware.
Click to expand...

Warden is not legally allowed to scan outside it's own process, so I doubt they can do anything regarding driver names. And last time I checked, it wasn't forbidden to run Diablo inside a VM.
 
Raoul said:
Warden is not legally allowed to scan outside it's own process, so I doubt they can do anything regarding driver names. And last time I checked, it wasn't forbidden to run Diablo inside a VM.
Click to expand...

Maybe so, but still easy to detect without scanning outside of the process. If i were blizzard id see vmware users as an easy target to flag for "further investigation". I've got some new hardware coming tomorrow 6core i7, 64gb ram yay.. going to run up a bunch of bots. Will do what i can to minimise vmware detection.
 
You must log in or register to reply here.
Back
Top