State of Allegiance in Linux
-
One-Man-Bucket
- Posts: 1248
- Joined: Sun Jun 19, 2005 7:00 am
-
privateerm
- Posts: 273
- Joined: Sun Aug 05, 2007 2:17 am
- Location: NB Canada
Alright, I did package the DLLs in the list up together and told wine to use the native libraries only for these. There were some warning messages immedietly when I told wine to use the native ddraw.dll, kernel32.dll and a couple of others. Those libraries are what make wine wine. Anyway, I tried it and it crashed(of course I was warned). I then told wine to use all the libraries that I was warned about and tried again. No load, but no warning. Now I need to go through each of the remaining libraries and see if I can isolate one.
Note: What specifically was the hex crash address the rest of you were receiving. It is possible it was the address for one of the function call in one of the given DLLs. Let me know and ill go through and see if it matches up.
Note: What specifically was the hex crash address the rest of you were receiving. It is possible it was the address for one of the function call in one of the given DLLs. Let me know and ill go through and see if it matches up.
Blah blah blah blah (breath) blah blah blah blah (breath) oh, what was this thread about again......
While I'd prefer to run in wine, I was able to authenticate successfully with ASGS and get Allegiance up and running with the new vmware beta (6.5), it does support directx 9.0c.
The only problem I have, is that mouse control goes wild.
edit: nevermind about the mouse problem. That was just a problem with my synergy2 client, which doesn't work well with alleg. vmware workstation 6.5 worked just fine. I'm happy to be playing alleg in linux.
The only problem I have, is that mouse control goes wild.
edit: nevermind about the mouse problem. That was just a problem with my synergy2 client, which doesn't work well with alleg. vmware workstation 6.5 worked just fine. I'm happy to be playing alleg in linux.
Last edited by echoism on Thu Sep 04, 2008 4:16 pm, edited 1 time in total.
-
Grimmwolf_GB
- Posts: 3711
- Joined: Wed Jul 02, 2003 7:00 am
- Location: Germany
- Contact:
Please read this:
http://www.freeallegiance.org/forums/index...ost&p=52895
http://www.freeallegiance.org/forums/index...ost&p=52895
The Escapist (Justin Emerson) @ Dec 21 2010, 02:33 PM:
The history of open-source Allegiance is paved with the bodies of dead code branches, forum flame wars, and personal vendettas. But a community remains because people still love the game.
Yeah, I did read that. And, obviously it is mistaken. ASGS authenticated successfully in vmware. I did nothing special.
I do see where it can become an issue of identifying clients by hardware, but is there still a need for that?
Hardware isn't difficult to change. If anything, the inconvenience added probably outweighs the benefits. Perhaps I am mistaken, I am new to the alleg community, and I don't know the history behind taking that route in the first place. I'm not looking to stir up old sorespots.
If whoever wrote ASGS doesn't want it to run in vmware, it isn't that hard to block, the display adapter is VMware SVGA II, the network adapter is VMware PCNet Adapter, the mouse is VMware Pointing Device, etc. If software specifically doesn't want to be compatible with vmware, it is trivial to check for any of those.
I do see where it can become an issue of identifying clients by hardware, but is there still a need for that?
Hardware isn't difficult to change. If anything, the inconvenience added probably outweighs the benefits. Perhaps I am mistaken, I am new to the alleg community, and I don't know the history behind taking that route in the first place. I'm not looking to stir up old sorespots.
If whoever wrote ASGS doesn't want it to run in vmware, it isn't that hard to block, the display adapter is VMware SVGA II, the network adapter is VMware PCNet Adapter, the mouse is VMware Pointing Device, etc. If software specifically doesn't want to be compatible with vmware, it is trivial to check for any of those.
-
badpazzword
- Posts: 3627
- Joined: Thu Jan 12, 2006 8:00 am
- Contact:
-
privateerm
- Posts: 273
- Joined: Sun Aug 05, 2007 2:17 am
- Location: NB Canada
Thats awesome that it works in VM ware. Now, if anyone else wants to try it, your accounts will be linked /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" /> My two cents is to let him play. VM ware on linux means more people playing. Just need to find a new way to authenticate......
Blah blah blah blah (breath) blah blah blah blah (breath) oh, what was this thread about again......
Yeah, I suspect that might be an issue.
I'm not entirely sure how far down it looks at hardware to uniquely identify a system, I don't have much experience with such systems, but I do know that I've only really seen that with a ms windows environment. Vmware is pretty simplified in that respect. Most of them will probably look identical. I know that if I get the game working under Wine, the same problem will exist. Most Wine environments look identical to an application.
I suppose it wouldn't be too difficult to use the ip subnet that someone is connecting from as another factor to uniquely identify them. Not a complete solution, but that might help limit false-positive account merging.
I'm not entirely sure how far down it looks at hardware to uniquely identify a system, I don't have much experience with such systems, but I do know that I've only really seen that with a ms windows environment. Vmware is pretty simplified in that respect. Most of them will probably look identical. I know that if I get the game working under Wine, the same problem will exist. Most Wine environments look identical to an application.
I suppose it wouldn't be too difficult to use the ip subnet that someone is connecting from as another factor to uniquely identify them. Not a complete solution, but that might help limit false-positive account merging.