Anyone able to get this to work on win 7 32 bit, US edition of diablo 3? the OP wrote the mklink bat for diablo based on RU version, so the file locations may be different. I am not sure what i need to edit and it seems that no matter what I do I can't get it to work. The game either launches and freezes at startup, or it starts and says I'm missing a required file.
What are the benefits of using Windows 7 over Windows XP? Windows XP would use less RAM (presumably) but are there some worthwhile updates to CPU scheduling or memory allocation that make W7 worth it? I've researched this but I haven't been able to find an answer. EDIT: Before it's mentioned, I know that the host needs to have Windows 7 because the cap for RAM on windows XP is something like 4 or 8 GB.
As stated earlier in this thread, it is not possible to make a network link to an exe, therefore it is not possible to use one instance of Diablo 3 on the host machine available to X virtual machines.
Currently running 1 guest + 4 clones. Everything is running smooth with 80% CPU load on i5 2500k @4.6GHz The only problem is my GPH dropped from 600 to 400k on sarkoth, using AGB. I can't find the reason, because like i said it's running smooth. after a lot of observation I figured only, that DB crash and bot gets stuck more often, but that's highly unlikely to result in way less GPH. Any ideas?
At this point I am not even sure that virtualization is worth it. I am averaging 50% load on an i7-3770k with only 5 of them running. Not sure if it is on my end, but it definitely sucks since I could have 3 times the amount running without VMware.
Instead of using clones do it take more computer resources to just make brand new guest OS for each instance of Diablo? I ask because I couldnt make the user name change under my clone OS's.
You have 2 files to modify the registry, in the zip file. What are these 2 files for? enable-close-programs.reg and disable-close-programs.reg Also if anyone need the US version of the D3 file and is lazy or dont wanna change it here it is. mkdir "C:\Diablo III" mkdir "C:\Diablo III\Data_D3" mkdir "C:\Diablo III\Data_D3\PC" mkdir "C:\Diablo III\Data_D3\PC\MPQs" mkdir "C:\Diablo III\Data_D3\PC\MPQs\Cache" copy "Z:\Diablo III\Data_D3\PC\MPQs\Cache" "C:\Diablo III\Data_D3\PC\MPQs\Cache" mklink "C:\Diablo III\Data_D3\PC\MPQs\ClientData.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\ClientData.mpq" mklink "C:\Diablo III\Data_D3\PC\MPQs\CoreData.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\CoreData.mpq" mklink "C:\Diablo III\Data_D3\PC\MPQs\HLSLShaders.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\HLSLShaders.mpq" mklink "C:\Diablo III\Data_D3\PC\MPQs\Sound.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\Sound.mpq" mklink "C:\Diablo III\Data_D3\PC\MPQs\Texture.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\Texture.mpq" mklink /D "C:\Diablo III\Data_D3\PC\MPQs\Win" "Z:\Diablo III\Data_D3\PC\MPQs\Win" mklink /D "C:\Diablo III\Data_D3\PC\MPQs\base" "Z:\Diablo III\Data_D3\PC\MPQs\base" mklink "C:\Diablo III\Data_D3\PC\MPQs\base-Win.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\base-Win.mpq" mklink /D "C:\Diablo III\Data_D3\PC\MPQs\enUS" "Z:\Diablo III\Data_D3\PC\MPQs\enUS" mklink "C:\Diablo III\Data_D3\PC\MPQs\enUS_Audio.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\enUS_Audio.mpq" mklink "C:\Diablo III\Data_D3\PC\MPQs\enUS_Cutscene.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\enUS_Cutscene.mpq" mklink "C:\Diablo III\Data_D3\PC\MPQs\enUS_Text.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\enUS_Text.mpq" mklink "C:\Diablo III\Data_D3\PC\realmlist.dtf" "Z:\Diablo III\Data_D3\PC\realmlist.dtf" mklink "C:\Diablo III\.agent.db" "Z:\Diablo III\.agent.db" mklink "C:\Diablo III\BattlenetAccount.url" "Z:\Diablo III\BattlenetAccount.url" mklink /D "C:\Diablo III\Bnet" "Z:\Diablo III\Bnet" mklink "C:\Diablo III\Diablo III Launcher.exe" "Z:\Diablo III\Diablo III Launcher.exe" mklink "C:\Diablo III\Diablo III.exe" "Z:\Diablo III\Diablo III.exe" mklink "C:\Diablo III\Diablo III.mfil" "Z:\Diablo III\Diablo III.mfil" mklink "C:\Diablo III\Diablo III.tfil" "Z:\Diablo III\Diablo III.tfil" mklink /D "C:\Diablo III\InspectorReporter" "Z:\Diablo III\InspectorReporter" mklink "C:\Diablo III\Launcher.db" "Z:\Diablo III\Launcher.db" mklink /D "C:\Diablo III\Logs" "Z:\Diablo III\Logs" mklink "C:\Diablo III\Manual.url" "Z:\Diablo III\Manual.url" mklink "C:\Diablo III\Microsoft.VC90.CRT.manifest" "Z:\Diablo III\Microsoft.VC90.CRT.manifest" mklink "C:\Diablo III\SetupWin.mpq" "Z:\Diablo III\SetupWin.mpq" mklink "C:\Diablo III\TechSupport.url" "Z:\Diablo III\TechSupport.url" mklink /D "C:\Diablo III\Updates" "Z:\Diablo III\Updates" mklink "C:\Diablo III\fmodex.dll" "Z:\Diablo III\fmodex.dll" mklink "C:\Diablo III\icudt44.dll" "Z:\Diablo III\icudt44.dll" mklink "C:\Diablo III\icuin44.dll" "Z:\Diablo III\icuin44.dll" mklink "C:\Diablo III\icuuc44.dll" "Z:\Diablo III\icuuc44.dll" mklink "C:\Diablo III\ijl15.dll" "Z:\Diablo III\ijl15.dll" mklink "C:\Diablo III\msvcp90.dll" "Z:\Diablo III\msvcp90.dll" mklink "C:\Diablo III\msvcr90.dll" "Z:\Diablo III\msvcr90.dll" mklink /D "C:\ProgramData\Battle.net" "Z:\Battle.net"
Ahh cool thanks, I made one VM workstation with 4gigs and 2 processors 2 cores. I thought it would be fast but when it loads Diablo it takes forever to give me the login screen you know if i can accelerate that somehow?
Hi, new here and trying to set this up, can anyone upload their Windows 7 ultimate sp1 x32 lite v3 by nil-nt.iso file? googling it yields nada.
I just wanted to pop in real quick and thank you for this comprehensive guide, before setting up the vm's last night I had very little experience with VMware and virtualization in general. Your instructions are flawless and I had the first machine running in ten minutes, I'm now running four bots.