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

hi there. looking for some advice. note is a8quad 8gbram video radeon6620g. i installed vmware8 with winXP sp3 en 1.5ram bridge connection and put there D3 with bot, framework4, c+. optimized with some info that found in the topics like video configurations of the game. in th VM checking internet gives normal speed like on host, proccessor is at 80%, ram used at 800. the problem is that d3 in vm is lagging like crazy and dances with shaman drum still cant help. what steps i need to check first, or someway solve that problem? thanks a lot

 

Got the same problem like many others on the thread.
I'm used to setting up VMwares and stuff, got an i5 4ghz and a radeon 65xx with 8gb RAM, and D3 runs smoothly on 800x600 in the VM. I used to use AutoIt, and that worked nicely. With DB tough, the game suddenly gets extremely choppy and is practically unusable. Outside of the VM, everything works fine.
Drivers are all installed, using workstation 8.0.4, 32 and 64 bit make no difference. Tried various configurations in RAM and CPU, no changes.

Any solutions to this?

 

I'm getting the following error when trying to run demonbuddy on the guest

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'

The files are there. I even tried moving a full directory over to the guest and not using the mklink.

Thoughts?

 

Hi, shaliuno, and what about VMware ESXi? Unlike the workstation its free. But installed directly to the hardware W/O another OS. Works standalone.

 

(removed)

 

ok, thanks

 

Btw: I really thought, that they do investigate based on accounts, not a IPs or volume IDs etc.

 

(removed)

 

V.P.N means what? Standard Virtual private network acc? So you play under one account more chars at one time? Or do you have 6 battle net accs and play only one char per acc at one time?

Because I thought it so, that they can look for accounts which are connecting from different countries and then find your account, because you are connecting from 10 countries and by that way they can decide you re violating the rules and close your acc. Or they can see, that you are playing one acc cloned in one time and again close your acc. OOr did I miss something in understanding your method of boting?

To be honnest, I was wondering, that they have found my only acc where boting have been interlaced with normal playing. Btw: do you use SSD disks for boting? Thanks

 

(removed)

 

How do you mean that "never change location" ? You said that 1 acc gives you 10 IPs in 10 countries. This is what makes me a bit confused.

 

(removed)

 

Wow, just wow. You have not the slightest idea how blizzards agent.exe, or vmware actually works, do you? I have no idea how to build spaceships, so i dont post HOW-TO guides.

For anyone thinking about doing this... Don't expect to be able to update your game clients, at least not using his ISO that does not contain secondary logon service, unless you have a special version of blizzards agent.exe that does not require secondary logon service?

Also i recommend not wasting time trying to "hide" your VMWARE. It is very easy to determine if a user is running virtualized (google SIDT virtualization) blizz could check on this with about 3 lines of code.

 

Does anyone know how I can run Russian version on clone (to bot) and English account on host (to play)? I don't care about HDD space.

Also if blizzard doesn't ban by IP or hardware (or so I assume), would I really need to clone to bot?

 

(removed)

 

Thank you. I'll try this now.

 

For Vmware workstation 8 you need to remove this line,


MemTrimRate=0



And this one should be,

mainMem.useNamedFile=FALSE

mainMem.useNamedFile= "FALSE"


Thank you.

 

Hello. I'm pretty familiar with VMware and followed your steps in guide and I read this WHOLE topic (24 pages) and I still didnt find fix for my problem. Thats why I'm posting.
The problem is: when I launch d3 on fresh vmware guest with win7 (installed from ISO file from your guide) it takes about 5 min to start and when I finnaly log into the game, I can't even join game cause d3 freezes and after next 5 mins it throws me out to main menu. The usage of CPU and ram are really low. I have no idea what I did wrong. I'm pretty sure my mlinks are good and stuff like that.
I'm launching from command line ofc.
my vmware setup for 1 machine:

Code:

1.5gb ram
1 cpu with 2 cores
5gb hdd space

Tried to rotate some settings but didn't work.
My PC:

Code:

16GB of ram
intel i5-3450 @ 3.10GHz
radeon HD 5850
ssd 128 gigs

My mlinks:

Code:

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" 
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\enGB" "Z:\Diablo III\Data_D3\PC\MPQs\enGB"
mklink "C:\Diablo III\Data_D3\PC\MPQs\enGB_Audio.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\enGB_Audio.mpq"
mklink "C:\Diablo III\Data_D3\PC\MPQs\enGB_Cutscene.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\enGB_Cutscene.mpq"
mklink "C:\Diablo III\Data_D3\PC\MPQs\enGB_Text.mpq" "Z:\Diablo III\Data_D3\PC\MPQs\enGB_Text.mpq"
mklink "C:\Diablo III\Data_D3\PC\realmlist.dtf" "Z:\Diablo III\Data_D3\PC\realmlist.dtf"

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 /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"

Code:

mkdir "C:\Diablo III - DB"
mkdir "C:\Diablo III - DB\Settings"
mkdir "C:\Diablo III - DB\CompiledAssemblies"
mklink "C:\Diablo III - DB\gg.exe" "Z:\Diablo III - DB\gg.exe" 
mklink "C:\Diablo III - DB\fasmdll_managed.dll" "Z:\Diablo III - DB\fasmdll_managed.dll" 
mklink "C:\Diablo III - DB\IronPython.dll" "Z:\Diablo III - DB\IronPython.dll" 
mklink "C:\Diablo III - DB\Microsoft.Dynamic.dll" "Z:\Diablo III - DB\Microsoft.Dynamic.dll" 
mklink "C:\Diablo III - DB\Microsoft.Scripting.dll" "Z:\Diablo III - DB\Microsoft.Scripting.dll" 
mklink "C:\Diablo III - DB\Microsoft.Scripting.Metadata.dll" "Z:\Diablo III - DB\Microsoft.Scripting.Metadata.dll"
mklink "C:\Diablo III - DB\RemoteASMNative.dll" "Z:\Diablo III - DB\RemoteASMNative.dll" 
mklink "C:\Diablo III - DB\System.Data.SQLite.dll" "Z:\Diablo III - DB\System.Data.SQLite.dll" 
mklink /D "C:\Diablo III - DB\Help" "Z:\Diablo III - DB\Help"
mklink /D "C:\Diablo III - DB\Plugins" "Z:\Diablo III - DB\Plugins"
mklink /D "C:\Diablo III - DB\Profiles" "Z:\Diablo III - DB\Profiles"
mklink /D "C:\Diablo III - DB\Routines" "Z:\Diablo III - DB\Routines"
mklink /D "C:\Diablo III - DB\Rules" "Z:\Diablo III - DB\Rules"
mklink /D "C:\Diablo III - DB\Logs\" "Z:\Diablo III - DB\Logs\"

Any help appreciated.

 

(removed)

 

On host it works all right. D3 is updated on host, directx too.
when I run mannualy (no cmd) it looks like this:
from disc Z



disc C



both on vmware guest ofc.