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.
Anyone found a way to link vmware monitor over virtualization to the main pc monitor? via Isboxer?
I'm still kinda on the fence about VMWare to be honnest, I mean its cool an all but Isboxer is so much nicer looking and without much overhead. when we could be just panicking over a simple game limit counter per hour. Which obviously will be fixed via doing random map or long profile chains.
Try this:
run regedit
HKEY_CURRENT_USER\Software\Blizzard Entertainment\Diablo III REG_SZ Locale "enGB" change to ruRU
Shouldn't that jus simply 'work' ? Only problem I ran into was the "login" limitation from ISboxer. But normally you could just start isboxer on the VM's and then gather it all up on one big isboxer from another pc. I mean the program is meant to supervise several real pc's if need be so vmwares should pose no problem at all.
The shortcut and direct exe doesnt work.
I've written several times it doesnt work that way.
This is command promt.
![]()
Not true, ISBoxer's Window feeds supposedly cannot be sent over different PC's only over one. And since vmware is virtualized to make it seem like more then one its having issues im trying to figure out a way to do it. i posted up on their site.