VMware

[lckwjl]

I just downloaded VMware and I am starting to get it setup. I believe I have to make a new virtual machine for every WoW, and a fresh install of every wow client on each machine for 1 bot.. is this correct? Do I need to do anything inside VMware to optimize it or make it anon. I am new to this so I am kinda clueless. What do I have to do to make sure it has an original hareware id, and a different ip (do I need something else for ips?) Any help is appreciated!

 

[lckwjl]

I cant get my cd to install on the machine it is just sitting at .01% any ideas on how to install wow faster

 

[lckwjl]

Almost 100 views and no one knows?

 

[madmaximka]

I cant get my cd to install on the machine it is just sitting at .01% any ideas on how to install wow faster

install vmware tools and copy your wow by dragndrop into vm

 

[botorific]

install vmware tools and copy your wow by dragndrop into vm

It will install by CD but it is really slow, usually due to a long download / copy prior to install. I experienced this and nearly gave up until I saw file sizes increase over time. Just copy a game folder over from another install like last poster recommended.

 

[ultimastealth]

vmware seems like a waste of pc resources, why not just do it all off your pc? not like you will get a ip ban

 

[botorific]

vmware seems like a waste of pc resources, why not just do it all off your pc? not like you will get a ip ban

Yes, VM's are a pain in the ass! Setting up, maintaining, updating, etc. etc.

Do they do the job better - pretty much all down to speculation and...paranoia - and how "important" the account is.

CPUID's, HDD ID's, MACID's, Multiple account folders present on a single computer?

Can these be reported from the WoW client? Sure. Are they - who knows. Yes, Blizz can see it is a VM just the same as a single machine - BUT they can't see that all 5 are on the same physical machine. With enough differences - they have less to work with.

VM's also provide a nice way to separate / bind specific network adapters to each bot if you want to go with your own group of IP / ISP's - rather than working with VPeeN's / VPeeSes.

For example - I can VM on my Cellphone tether. Second VM on a wireless dongle to my neighbors net. Last my non-VM is running my home connection - all connected to one physical piece of hardware.

This CAN be done in a non VM environment (with multiple IP's / Net interfaces) using something like forcebindip.exe - but binding by IP isn't fool proof. Your risk potentially soft locking the account (signin IP pattern trigger) - and logging an IP on an account which you were trying to avoid...

Again - all of this for subterfuge and speculation on how Blizz detects and bans.

If one of my accounts gets some attention - do they see a different CPUID, HddID, MACID, and IP/Network, do different names on the account matter? Who knows!!!

 

[Cocaine]

I don't think VMware is worth it especially if not using different IPs for the virtual machine. I agree a lot of the IDs may be the same. I think they might have their own hddID but doubt the cpuid, macid is changed, however, these can be spoofed and changed.

 

[kravitz]

Easier method than using a CD! Copy all of the contents on your CD's to a folder on your main computer. Share the folder. Once you have the OS on the Vmware installed and set, navigate to the shared folder on your main pc and launch the install. Once you have it

The only way you can get away with different IP's is using a Virtual Network Provider, using several instances of vmware is great for that, granted if your Virtual Network Provider allows you to have multiple instances of the client up at once.

All of your hardware changes in vmware. You do not use a "physical" hard drive. it's a virtual drive with it's own hardware id. The VMware CPU has it's own id as it replicates the cpu, either you chose 1 cpu, 2, 3, 4, 5, 6, 7, 8 cpus, or 1 core 2 cores 3 cores or 4 cores, etc.. etc.. Vmware is all driven by dll's and software so each vmware instance you have is completely different than the other. If you are using a NAT configuration for your network your macid is different, you can physically change the mac within the network properties of vmware (i'm not sure exactly what it was called - haven't used it for a while). If you chose host to host (use the host computers network interface, then yes, your mac id will be identical as you are using your main machines network interface, vs the virtual interface to network.

 

[botorific]

I cant get my cd to install on the machine it is just sitting at .01% any ideas on how to install wow faster

Also - get ONE set up the way you want it - then use the CLONE the VM (linked) option to make it easier on yourself if you are replicating. Saves drive space. Don't make a bunch of snapshots along the way though - it kills performance down the road.

 

[botorific]

I don't think VMware is worth it especially if not using different IPs for the virtual machine. I agree a lot of the IDs may be the same. I think they might have their own hddID but doubt the cpuid, macid is changed, however, these can be spoofed and changed.

Agreed - if your IP resources are limited, what is the point.

I also wonder if how people choose to bot affects this decision at all.

If you're running to farm and sell gold as the goal - bans are to be accepted / expected...go crazy and who cares.

If you care SOMETHING for your bots (different from my Main) - maybe be more complex with your set up, and hope for the best knowing you did all you could.

Right now I'm more casual. I have a core group of 5 bots I set up to run instances with. I control all the loot and use them to level toons on my main quickly. If I lose them, I will be sad - but not the end of the world.

Vs.

I have 1 account that I don't care about and I only started it because I have the available HB session slot available!

Sorry to side track the thread - hope you got yourself running Ick!

 

[foraus]

vm

install the user tools
copy paste your Wow folder and bot's onto a removable hdd
copy paste all your files onto your vm
capture that vdi
and then just deploy it over 10 vms eg wow 1 /wow 2 /wow 3 etc etc

 

[LunaticFringe]

doesnt sandboxie do the same thing without hogging all the resources? plus its free.....always a plus

 

[Rabbit1]

1. A VM for every wow means 1x CPU core 1x 1gb+ Ram. So unless you have a beast PC.
2. Don't install or use a USB follow this guide - Using Shared Folders
- Basically it just shares your wow folder on your PC and your VM can access it.

 

[botorific]

1. A VM for every wow means 1x CPU core 1x 1gb+ Ram. So unless you have a beast PC.
2. Don't install or use a USB follow this guide - Using Shared Folders
- Basically it just shares your wow folder on your PC and your VM can access it.

Couldn't this expose you if all your bots run from that same shared location? I mean, within the VM hard disk, you atleast have the unique Hard Disk ID you are behind.

Maybe with a shared folder, you're still behind that different ID? I don't know.

Granted, separate installations per VM IS A MAJOR pain in the ass and takes up storage - but not terribly if you are using clone-linked VM's for replication.

I'm all for running HB from DropBox to at least minimize that part - though.

I guess if you get nabbed - you can claim you play at an internet gaming cafe where they have WoW installed in this shared manner.

 

[botorific]

The only way you can get away with different IP's is using a Virtual Network Provider, using several instances of vmware is great for that, granted if your Virtual Network Provider allows you to have multiple instances of the client up at once.

You can do this with multiple wifi dongles and and binding vnets to them for each VM as well if you don't want to go the Virtual Net Provider route. You just have to have the hardware and / or means to the networks.
So when I travel, for example...

Netgear Wifi #1 -> 4g cellphone tether (owned) -> vnet1 -> vm1

Netgear Wifi -> Xfiniti wireless in the area etc. (offered "free" from my local cable TV company) -> vnet2 -> vm2

Builtin Wifi -> Hotel wireless ("free" / semi-free)-> local -> physical machine

Overkill...but doable!

 

[kravitz]

You can do this with multiple wifi dongles and and binding vnets to them for each VM as well if you don't want to go the Virtual Net Provider route. You just have to have the hardware and / or means to the networks.
So when I travel, for example...

Netgear Wifi #1 -> 4g cellphone tether (owned) -> vnet1 -> vm1

Netgear Wifi -> Xfiniti wireless in the area etc. (offered "free" from my local cable TV company) -> vnet2 -> vm2

Builtin Wifi -> Hotel wireless ("free" / semi-free)-> local -> physical machine

Overkill...but doable!

Sure, if one had access to all those options. If you did you can insanely shotgun your main networks bandwidth.

 

[madmaximka]

Also - get ONE set up the way you want it - then use the CLONE the VM (linked) option to make it easier on yourself if you are replicating. Saves drive space. Don't make a bunch of snapshots along the way though - it kills performance down the road.

if you clone vmware you get os with same id (CPUID, HDD ID, MACID ...) wrong way...

 

[emub]

I just shared my wow game folder, took a copy of the whole folder and dumped it on my VM_HDD. Way faster than a treditional install.
I also used this method to copy wow to my wifes PC and my laptop. Wow works just fine been copy and pasted to a new location.

If you really are worried about having 2x wow accounts appearing from the same location, just do what I do. Have the VM PC (windows8) dial a (V P N) Service and go through that.



p.s why I cant type V P N without spaces it gets masked as *** when I post hehe?

 

[Darkbound]

There is no point in using a VM, I understand the reasons why you would want that but it's a complete waste of resources I tried doing that, and it was pretty much 1 and half bots per core with FX-8150 at 4 GHz, crashes freezes and low performance at all are just the everyday issues. It's too much of a pain in the as*.. where I need like just 1/2-1/3 of these resources to run the same amount normally.