Allegiance under Mac/Linux
-
- Posts: 3709
- Joined: Wed Jul 02, 2003 7:00 am
- Location: Germany
- Contact:
-
- Posts: 3211
- Joined: Tue Mar 29, 2005 8:00 am
- Location: my pod
fuzzylunkin1 wrote:QUOTE (fuzzylunkin1 @ Sep 5 2008, 12:11 AM) <{POST_SNAPBACK}>Has anyone tried the most recent version of VirtualBox?
VBox doesn't have direct x accel.
-T
"Therefore I will boast all the more gladly about my weaknesses, so that Christ's power may rest on me." -2 Cor 12:9
"Never know how long I've waited, anticipated your smile pressed against mine." -Running
SaiSoma wrote:QUOTE (SaiSoma @ Sep 5 2008, 07:58 AM) <{POST_SNAPBACK}>Unless the VM can be allowed IF and only IF it reports actual hardware IDs .. which isn't likely:(.
Yeah, I'm not sure which hardware asgs is concerned with. vmware does allow direct hardware ids for some thing, but not for others. vmware's primary goal is to to able to run anywhere, so anything that has a compatibility issue, tends to have a virtual (vmware) driver, and would probably look the same.
I'll be testing it this weekend so we'll know for sure.
Just so we're on the same page, I used vmware workstation 6.5 beta.
I'll be trying it on a few other operating systems this weekend.
I'll be trying it on a few other operating systems this weekend.
-
- Posts: 3626
- Joined: Thu Jan 12, 2006 8:00 am
- Contact:
Heh, if it works on one host OS it's bound to work on all.
Have gaming questions? Get expert answers!
It is true, that I expect the game to work on other operating systems, what I am testing is asgs callsign linking. Some hardware is accessed directly, some is virtualized.
The goal of the tests is two-fold:
1. To determine if the new vmware environment is uniquely identifiable by hardware.
2. To determine if the hardware identification is consistent per host.
If the vmware environment is too generic, then all virtual machines runing asgs would be linked, only allowing one of them online. This would not work well for the community, in which case I should have just kept my mouth shut and enjoyed playing the game on a linux host with nobody the wiser.
However, if asgs' identification is changed per instance of a virtual machine, then someone could just create another one to generate a new id, and effectively bypass the ban system that has been put in place. Additional installs on the same system, using clones, changing config, that all needs to be determined.
If I get the same hardware identification on a given host machine, regardless of which virtual machine I am running, AND that identification is different from other vmware workstation hosts, then it is fine to leave it as-is, and it can be deemed permissible.
The odds are not in favor of both conditions being met, but I am testing them anyway. Perhaps asgs can be updated to work with vmware, perhaps different criteria would work, perhaps not. Once I have some solid tests done, that will give a starting point. As people have pointed out to me, it will probably end up getting disabled.
My perspective is that I'm a newb, and I'm just probing. Hopefully the information will be helpful. Oh, and I have a nanite gun too, but I'm still learning how to aim.
The goal of the tests is two-fold:
1. To determine if the new vmware environment is uniquely identifiable by hardware.
2. To determine if the hardware identification is consistent per host.
If the vmware environment is too generic, then all virtual machines runing asgs would be linked, only allowing one of them online. This would not work well for the community, in which case I should have just kept my mouth shut and enjoyed playing the game on a linux host with nobody the wiser.
However, if asgs' identification is changed per instance of a virtual machine, then someone could just create another one to generate a new id, and effectively bypass the ban system that has been put in place. Additional installs on the same system, using clones, changing config, that all needs to be determined.
If I get the same hardware identification on a given host machine, regardless of which virtual machine I am running, AND that identification is different from other vmware workstation hosts, then it is fine to leave it as-is, and it can be deemed permissible.
The odds are not in favor of both conditions being met, but I am testing them anyway. Perhaps asgs can be updated to work with vmware, perhaps different criteria would work, perhaps not. Once I have some solid tests done, that will give a starting point. As people have pointed out to me, it will probably end up getting disabled.
My perspective is that I'm a newb, and I'm just probing. Hopefully the information will be helpful. Oh, and I have a nanite gun too, but I'm still learning how to aim.