Hello , im new to this whole VM thing , and im also in general not pro with neither software nor hardware stuff. I've managed to follow through most of the guide , and i've managed to get 1 VM running with Diablo + DB running fine ( took few seconds before diablo actually gets started , but it runs smooth afterwards ). I made a clone and now im trying to run a 2nd machine , but it diablo takes forever to start , and it even freezes when i try enter a game. I have a new laptop with Intel i7 - 2670QM @ 2.20 Ghz and 8 GB Ram . I've assigned 1.5G Ram to each machine and 2 Processors x 2 Cores on each aswell. Task Manager shows like ~20 % Cpu Usage and max 50 % Physical memory usage on each VM , so i dont understand why Diablo and DB are so slow. Someone kind enough to help me out?
dunno if it was mentioned, but instead doing that cmd stuff all the time, just rename your Diable III.exe on your VM Guest to d.exe and then create a -launch shortcut to it.
http://i.imgur.com/jvB7I.png Any ideas how to fix this? tried to copy demonbuddy to VM Guest, tried to run it from Z:, nothing works Edit: lol, after 2 hours I figured it out that renaming Diablo III.exe was stupid xD
hi, i got diablo to run flawlessly, but seem like after demonbuddy ran it lags everything including the game can you help me out
read 19 sites and didn't find an answer: copy "Z:\Diablo III\Data_D3\PC\MPQs\Cache" "C:\Diablo III\Data_D3\PC\MPQs\Cache" this 1 always gives me the error: Z:\Diablo III\Data_D3\PC\MPQs\Cache* The System cannot find the file specified. 0 files copied but when i go to the folder via explorer and Z:\Diablo III\Data_D3\PC\MPQs\Cache, it exists.
I have the same issue, just copy it manuallly, it works fine. Though I have so many crashes when run 2bots in VM.
And another problem, for: mklink /D "CrogramData\Battle.net" "Z:Battle.net" I get "Access denied", i tried to remove the cross by read only but won't work.
Just open Notepad and add following: 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\ruRU" "Z:\Diablo III\Data_D3\PC\MPQs\ruRU" mklink "C:\Diablo III\Data_D3\PC\MPQs\ruRU_Audio.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\ruRU_Audio.mpq" mklink "C:\Diablo III\Data_D3\PC\MPQs\ruRU_Cutscene.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\ruRU_Cutscene.mpq" mklink "C:\Diablo III\Data_D3\PC\MPQs\ruRU_Text.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\ruRU_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:\ProgramData\Battle.net" echo CHECK FOR ERRORS! SHOULD NOT BE ANY. pause ----------------------- After that, save it as D3copy.bat same for DB: echo EDIT FILE FIRST! pause mkdir "C:\Demonbuddy" mkdir "C:\Demonbuddy\Settings" mkdir "C:\Demonbuddy\CompiledAssemblies" mklink "C:\Demonbuddy\Demonbuddy.exe" "Z:\Demonbuddy\Demonbuddy.exe" mklink "C:\Demonbuddy\fasmdll_managed.dll" "Z:\Demonbuddy\fasmdll_managed.dll" mklink "C:\Demonbuddy\IronPython.dll" "Z:\Demonbuddy\IronPython.dll" mklink "C:\Demonbuddy\Microsoft.Dynamic.dll" "Z:\Demonbuddy\Microsoft.Dynamic.dll" mklink "C:\Demonbuddy\Microsoft.Scripting.dll" "Z:\Demonbuddy\Microsoft.Scripting.dll" mklink "C:\Demonbuddy\Microsoft.Scripting.Metadata.dl l" "Z:\Demonbuddy\Microsoft.Scripting.Metadata.dl l" mklink "C:\Demonbuddy\RemoteASMNative.dll" "Z:\Demonbuddy\RemoteASMNative.dll" mklink "C:\Demonbuddy\System.Data.SQLite.dll" "Z:\Demonbuddy\System.Data.SQLite.dll" mklink /D "C:\Demonbuddy\Help" "Z:\Demonbuddy\Help" mklink /D "C:\Demonbuddy\Plugins" "Z:\Demonbuddy\Plugins" mklink /D "C:\Demonbuddy\Profiles" "Z:\Demonbuddy\Profiles" mklink /D "C:\Demonbuddy\Routines" "Z:\Demonbuddy\Routines" mklink /D "C:\Demonbuddy\Rules" "Z:\Demonbuddy\Rules" pause REM mklink /D "C:\Demonbuddy\Logs\" REM OR if you want to have separate logs for each VM REM mklink /D "C:\Demonbuddy\Logs\" "Z:\Demonbuddy\Logs\yourvmwarepcname" REM and dont forget to create a folder on "Z:\Demonbuddy\Logs\yourvmwarepcname" REM if you want all setting for your character be in one place, do next REM mklink /D mklink /D "C:\Demonbuddy\Settings\yourbot#btag" "Z:\Demonbuddy\Settings\yourbot#btag"
When configuring the "Enable Shared Folders" and install VM-Ware Tools, you'll have a Z: drive which leads to your battle.net / d3 / DB folders.
When I try to log in to DB from VM guest with the diablo III window open, I get this error: Demonbuddy v1.0.952.222 started Logging in... Error attaching to Diablo III, Reason:System.IO.FileNotFoundException: Could not load file or assembly 'fasmdll_managed.dll' or one of its dependencies. The specified module could not be found. File name: 'fasmdll_managed.dll' at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc) at Zeta.ZetaDia.TryInitialize(Process proc, String& reason) Does anyone understand what this is saying or know why I would be getting this error. I'm pretty sure I have my .bat files set up correctly, along with my other files. Diablo runs fine, but DB gets this error.
I'm not sure I understand what you mean. You just copy the folder "Demonbuddy" from your C:\Demonbuddy on VM guest to the desktop and run the .exe from there. Or do you mean you just copy the whole demonbuddy folder from VM host to the desktop of VM Guest? Either way I still get that error. What is causing it? I saw earlier on in this thread that someone else was having a similar problem, but it did not seem to be resolved, or if it was, the solution wasn't posted.
There is an easier way to do the mklink commands... Creating a hardlink for each file and directory is extremely excessive. No need for those mkdir or copy commands either. Originally I used Map Network Drive instead of VMWare's shared folders feature but I am now finding that using VMWare's shared folders feature is more secure because it doesn't expose these shared folders to your entire network, just the Virtual Machine. the the mklink commands: Code: mklink /D "C:\Program Files\Diablo III\" "Z:\Diablo III\" mklink /D "C:\ProgramData\Battle.net\" "Z:\Battle.net\" mklink /D "C:\DemonBuddy\" "Z:\DemonBuddy\" After running these three commands, make your way to C:\Program Files\Diablo III\, right click on Diablo III.exe and Send To> Desktop (create shortcut). Make your way to the desktop, right click on Diablo III shortcut, hit Properties, and change shortcut target to "C:\Program Files\Diablo III\Diablo III.exe" -launch Good to go.
If anyone else was having the same problem that I was, I just found the solution. I was missing some windows files that I needed. There is a wizard for DB that you can run to make sure you have all the files you need to run DB, I ran that and it fixed my problem: View attachment DemonBuddyWizard.zip
After 2 hours of setting up, finaly I can post some results. Hardware: ? Procesor AMD Phenom II X4 955 3,2 GHz @ 3,6 Ghz Black Edition (Deneb) ? Motherboard MSI 870A-G54 FX ? 16 GB RAM (4x4 GB Patriot 1333EL 1066 MHz) ? NVIDIA GeForce GTS 450 1024 MB 128 bit (880/975/1760 MHz) ? SSD OCZ Solid 3 60 GB ? 2x Samsung HD103SJ 1 TB BEFORE: One diablo per one virtual machine. Each VM have its own copy of diablo 3 inside, so every VM have 20 GB. 2xVM per Samsung discs. SSD wasnt used. Win7 x64 Pro installed, without any tweaks. Total disk space used: 80 gb CPU load: 100% GPU load: 42% RAM used: 12,5 GB AFTER: Using VM scheme from this thread. Shared Diablo 3 on SSD drive, and 1 mother VM + 3 linked clones, places on SSD also. Win7 from ISO given by OP. Really light! Total disk space used: 14 gb CPU load: 100% GPU load: 40% RAM used: 10,5 GB CONCLUSION: Diablo 3 loading time after restart is MUCH longer (like 5-8 times longer) in this (AFTER) VM model, than my previous (BEFORE). Diablo 3 is running more smooth in this VM model (AFTER), after it starts. FPS more stable. Less ram usage because of using Win7 lite great distribution AMD is fucking shit when it comes to virtualization. Max 5x diablo 3 at once. If you have several magnetic disc and lot of space, definetly go with my first model (BEFORE). Much faster loading, no problems in setup. If you have AMD and you want to use DB in VM - forget it. Go buy i5/i7 or change bot. I don't use DB at all, because its performance in VM is just horrible. If you are banned every 1-2 weeks, and changing accounts very often - definetly use VM model described in this thread. Thanks for great tutorial.
if i run 1 bot from vmhost and 1 bot from vmguest do they both look like different pcs? i am asking because i am having problems to run lag-free both bots on two vmguests and would like to try out 1-bot-vmhost + 1-bot-vmguest combo
I can get Diablo 3 and Demonbuddy running fine in VMWare Workstation 8, but after about 20 minutes of actually working, for some reason Diablo 3 and Demonbuddy just shutdown. What could be causing it to shutdown, after running fine for about 20 minutes ?