botting with vmware workstation

This may be overkill, but i am actually very jittery about botting where my main account is. The value is far to great to risk it. So i jammed a pc at my brothers computer. I dish out like 20bucks for electricity a month to bott my brains out, and not risk alot. With botting, there is always a risk, but this makes it easier to cope with. I dont bott for money, just personal value, so giving a little extra money isnt a huge deal. Plus, people around me are much happier, as im not always running to the pc to check on the bots....i use a internet program that controls the computer over there. So i can make profiles, change settings and all that jazz from my home, from work etc via internet explorer basically. dont count on great performance though, as lagg is a factor. All i can say, learn to click-to-move function and use it well..

anyone else that has any advanced or weird setups where the tin-foil hat is pertruding through the ethernet?

 

Can I use linked clones or do they need to be full clones?

 

i need some help whit that, i have a ATI 5670HD but the VMeare Station dont detect him, and i can run WoW in VMW, any one can help me ??

 

Say, have you tried using ReactOS for the operating system of your guest machines to set this up? I just started playing with all of this and decided I would ask as you may be farther along than me.

Frontpage - ReactOS Website

 

So last night I decided to give this a go. My goal wasen't to hide my clients but to free up my main rig to do other things whilst I bot. I built one VM with 2cpu's and 4gb of ram and installed Windows 7 x64 with the goal two run two clients + honorbuddy. I know that the main bottleneck will be disk I/O so with that in mind I threw in 2x 10k SAS drives I had collecting dust and set them to Raid 0 for the OS and WOW client. Whilst not as good as SSD it didn't cost me anything.

Everything went well once WOW was up and all graphic details reduced to low the only problem was useing the mouse to move (not click to move), the character went crazy just spinning on the spot. I remember the mouse option within WOW called 'Mouse Harwdare Acceleration'. Disabling this feature stopped any crazy character movement and everything went back to normal. I am very happy with the result and will continue to use this from now on. If anybody is interested here is the relavent harware I am running it on.

I7 920 @3.8ghz
18gb of generic ram.
Asus P6T WS pro (onboard SAS)
60gb SSD for OS
2x 146gb 10k SAS Raid 0 (VM and WOW)
ATI 6870 vid card.

Each client runs 35-45FPS.

 

Which version of VMware are you running and did you tick the option on the vm to allow 3d graphics. I cant remember if it was on by default. Also disable your onboard graphics if you have one. You dont want to confuse vmware at all.

 

Im not sure, but what the reason to make VMware with different IP for botting? You officialy can play 5 accs from 1 PC (mboxing), so if you get banned on 1 of 5 accs,
and Blizz goes to investigate connections to other from this IP, the result will depend on how properly you made you gold tranfers and so on.
Even if you want to bot 5+ accs on one PC(10,15,??) use VPN coonection and make all precautions like different accs real info, automated schedule logging in/off.
In this way Blizz wont block all of them, cause you will look like a school, college or inet cafe.

 

I've encounted a problem with sharing Data directory from host OS.
MKLinking worked perfectly, direct file transferring between shared directory & virtual harddrive within guest OS doesn't seem to expose any slowdowns, but when I try to start WoW, it becomes terribly slow. TERRIBLY. Like 3-4 minutes just to see login screen.
It only affects loading process - starting wow or logging on your character. General performance\framerates are unaffected.
Slowdowns disappear when files are placed directly on virtual drive instead of linking.
VMWare Workstation 8.0, no evident hardware bottlenecks. Host - Win7 x64, guest - Win7 x64 (tried with 32 bit version as well). Shared via Virtual Machine settings with "map as a network drive" enabled.

Any suggestions?

 

Nevermind, just downloaded VMWare 8.0.1 update and the problem were solved by itself!