FleetOps 3.1.x on Wine 1.2 RC 4
Program aborts? Network configuration? Graphic errors? Bugs? Post your question here.
posted on June 19th, 2010, 7:36 am
First a question: Is your Armada2.exe a different binary? I have assumed this in WineHQ. The "installer" is.
After you press the launch button, FleetOps needs 1) on Windows quite long to start and 2) 10x longer with Wine on Linux. For 2), the red progress bar disappers, because the process finished, but then it need 5-10 minutes! And with Wine warnings on more than 1 hour! Any reason known?
What about using multiple cores to speed up the starting process? I have an Athlon 64 dual core at 2GHz, the very first one, but in most cases it's still not so bad. In future we will have more cores, and not much more GHz.
Is there a demo version of FleetOps possible for the Wine guys which doesn't need the Star Trek Armada 2 CD?
regards
Bojan
After you press the launch button, FleetOps needs 1) on Windows quite long to start and 2) 10x longer with Wine on Linux. For 2), the red progress bar disappers, because the process finished, but then it need 5-10 minutes! And with Wine warnings on more than 1 hour! Any reason known?
What about using multiple cores to speed up the starting process? I have an Athlon 64 dual core at 2GHz, the very first one, but in most cases it's still not so bad. In future we will have more cores, and not much more GHz.
Is there a demo version of FleetOps possible for the Wine guys which doesn't need the Star Trek Armada 2 CD?
regards
Bojan
posted on June 24th, 2010, 11:09 am
welcome to the forums, Bojan!
the binary itself is unchanged, a loader dll is being attached to do the magic
wine is currently totally untested. it is absolutely normal that after the loading bar appears it takes more time to finish loading. that is because armada at that point starts loading all the ship models etc which can take some time.
you can use any armada 1.1 no cd patch for fleet operations. other than that, there are some known problems.
though some wine fixes are planned, in theory the wine developers should take care that all windows apps run as if they were on windows
(we both know that won't happen soon considering the amount of other incompatible programs)
the binary itself is unchanged, a loader dll is being attached to do the magic

wine is currently totally untested. it is absolutely normal that after the loading bar appears it takes more time to finish loading. that is because armada at that point starts loading all the ship models etc which can take some time.
you can use any armada 1.1 no cd patch for fleet operations. other than that, there are some known problems.
though some wine fixes are planned, in theory the wine developers should take care that all windows apps run as if they were on windows

Who is online
Users browsing this forum: Google [Bot] and 11 guests