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

how do you stop these .exe from running?

 

is there a way to actually change the hardware ID? Because there is a lot of shared things across the VM's starting with unique CPU ID. Are they allowed to sniff it out to begin with?

 

(removed)

 

when i try to run D3 from cmd, diablo 3 just hangs on startup.. wtf

 

Hi, im running ESXI, witch i tend to get the maximum performance out of my server..

Specs : 8 cores 4gb ram 128mb vram on one VM (lightweight ISO)


Results : 1 or 0 FPS? with those numbers its not even worth trying to start the bot


what major superimportant part did i miss? lightweight image, max vram, max cores and enough ram? and im running all this on SAS drives in raid 0
(troughput 3-400 mb R/W )

Awesome guide though ^^

thank you

 

This is just an awesome guide, i will rep you for it. But i will not use vmware anymore as last time i got banned, i got banned all the way trought Vmware, so they can totally see trought it, its just a time consuming and CPU/ram loss for me now. I convinced myself that vmware doesnt offer the protection i tought from blizzard. Il just go straight 6 accounts from one PC cause when the ban comes it will come to all 6 regardless i use vmware or not.

But thanks for the guide, very well done and put up.

 

The second VM that launches Diablo 3 takes a long time, the D3 window comes up grey for a good few minutes - is that normal? Once its finally launched it runs just fine, its as if it takes VMWare a long time to give access to the GPU or something

 

Anonbot that might just be. It is pretty intensive to start a virtualized D3, far more then normal I have noticed while watching the CPU useage on hostpc while starting a game, but a few MINUTES seems never right

 

(removed)

 

Vm was setted pretty much like in your guide, i did not use V p N as "blizz ban's by ip its total bs", they don't ban by ip, because it can easily people from same Uni, workplace, etc can have the same IP, they only ban by same MAC adress. Ip ban is a story for little children. + Static V P N adresses has even higher chances of ban since blizz know's pretty much most of them. So its easy for them to check who uses what IP. Each VMware instance has a different MAC adress itself so i dont have to change that any other way.

I used AGB on 2 , and Slim petes profile for barbarian on one. - But this has nothing to do with it.
Ive been botting 24/7 on all 4 accounts, but the 4th survived(was botting core not sarkoth like the rest) EVEN IF i ran the 3rd and 4th account from the same windows (my windows not Vmware instance), so therefore is my question if they saw me using a bot on my own windows and mac adress they also saw my monk instance then, but they didnt ban that. The question is why. Unless, they dont check Ip/mac adress....

 

can someone help me with this? I can't get d3 to run from cmd, it just freezes on startup at the logo of diablo's head.

 

I've narrowed down the problem to be something to do with the way the OP links the files. If i install a new D3 copy in each VM i don't have the issue. I think its something to do with file locking maybe.. I'm not sure exactly which bit is causing the issue yet but i'm getting closer.

I think rather than doing all the linking with a .bat file i might just install D3 on the first VM and make linked clones from that. Sure my other copies will grow a little bit with each patch - but the complexity is greatly reduced.

Edit: redid everything from scratch without linking, can load 10 currently with less than 20% CPU load (hex core intel), there are even still some cores on the host not being used . Also found better performance to give each VM 1 CPU with 2 cores, 2GB RAM. My PC has 64GB RAM so i stuck the main VM that had everything else cloned off on a 20GB RAM drive.

 

Are the games startable without cmd prompt?

 

When I get to this step:

Important part here.
9a) Navigate to the folder wher your VMware Guest is stored and find .vmx file and open it in editor.
Add these lines somewhere in file:

mainMem.useNamedFile=FALSE
MemTrimRate=0
prefvmx.minVmMemPct = "100"
prefvmx.useRecommendedLockedMemSize = "TRUE"
sched.mem.pshare.enable = "FALSE"




I get a "Dictionary Problem." when I try to turn on that VM. If I don't add those lines it runs fine... I am adding it to the .vmx file in My Documents/Virtual Machines/Windows

Any ideas what I am doing wrong?

 

(removed)

 

I saved it as a UTF-8 and the path is C:\Users\Xherion\Documents\Virtual Machines\Windows 7x everything should be english

Nothing else in the .vmx file needs changed right? Just need to copy/paste those 5 lines into it somewhere in the file

 

(removed)

 

Hopefully you can see whats wrong.. [: thanks alot for taking the time to help!

 

(removed)

 

Awesome, that did it. So it was the "MemTrimRate=0" in there twice that caused the problem I guess. Thanks for finding that.