Board index FlightGear The FlightGear project

FlightGear 2.6 on Windows 2000

Questions about the FlightGear organisation, website, wiki etc.

FlightGear 2.6 on Windows 2000

Postby fojtik » Mon May 21, 2012 7:42 pm

Just try to:
1, Install official release of flightgear 2.6 - installer works
2, Completely delete a content of direcrory C:\Program Files\FlightGear 2.6\bin\Win32\
3, Replace its contents with http://www.penguin.cz/~fojtik/flightgear/fg_win32.zip

This version is slightly bit more optimized to use SSE2 instruction set, so even XP and Windows 7 users could try it.

And the result you could observed here:
Image :lol: :lol: :lol: :lol: :lol:

It would be nice if the file fg_win32.zip would be pushed to official flightgear ftp.
fojtik
 
Posts: 12
Joined: Thu Feb 09, 2012 9:42 pm

Re: FlightGear 2.6 on Windows 2000

Postby kyokoyama » Mon May 21, 2012 11:00 pm

Considering how intensive FlightGear's program is, I'm amazed that a Windows 2000 can run FG2.6...!

Thank you for sharing this proof. :shock:
Look for "B-BIRD" "N127KY" or "AVA0004" -that's me.

Despite having over 1700 posts here, I am not even close to being the most skilled guy here... I'm just words and bad drawing, not experience. :P
kyokoyama
 
Posts: 1988
Joined: Sun May 03, 2009 2:16 am
Location: Earth
Callsign: B-BIRD, N127KY
Version: 2.12.1
OS: Windows Vista

Re: FlightGear 2.6 on Windows 2000

Postby Rick Ace » Thu May 24, 2012 3:03 pm

kyokoyama wrote in Mon May 21, 2012 11:00 pm:Considering how intensive FlightGear's program is, I'm amazed that a Windows 2000 can run FG2.6...!

Thank you for sharing this proof. :shock:

Well, depending on the specifications of the system that's running the OS, it may not be too absurd. The system itself is more of a limitation than the OS.
Rick Ace
 
Posts: 1023
Joined: Fri May 14, 2010 6:02 pm
Location: New York City
Callsign: rickace
Version: 2.6.0
OS: Vista

Re: FlightGear 2.6 on Windows 2000

Postby fojtik » Sun Sep 15, 2013 2:42 pm

Rick Ace wrote in Thu May 24, 2012 3:03 pm:Thank you for sharing this proof. :shock:

Well, depending on the specifications of the system that's running the OS, it may not be too absurd. The system itself is more of a limitation than the OS.

It is only Microsoft's intention to shutdown Win2k. It produces C-runtime that calls function EncodePointer and DecodePointer. The OS is artifically obsoleted by this decision.
http://www.codeproject.com/Questions/536448/DecodePointerpluscouldplusnotplusbepluslocatedplus
If you remove these calls even from MSVC2012 it will run without any problem.

W2K will automatically obsolete several years later with new hardware that does not have drivers.
fojtik
 
Posts: 12
Joined: Thu Feb 09, 2012 9:42 pm


Return to The FlightGear project

Who is online

Users browsing this forum: No registered users and 1 guest