Printable View
Quick question:
Will BF2 Run on Windows 2000?
I was going to buy a copy, but the System requirements on the back of the box said Win XP only, but my PC runs 2K. As the two OSes are virtually identical under the hood, I would have thought Win2K would be OK, but needless to say the shop assistant in Game had no idea other than to say that if it did not work there would be no refund.
apparently it does...
http://episteme.arstechnica.com/eve/...m/193006773731
"Nevertheless, BF2 does run under Windows 2000, without any tweaks. All EA do is issue a warning that it hasn't been tested on W2K. But it works, and works well."
Thanks for the link.
I guess if it still does not work then I can do the upgrade I have been putting off for the past couple of years...
Would it be possible to download the demo and try that?
Surely that'd give you a good idea?
I am ahead of you on that, I have downloaded an installed the demo, just waiting for the first map to load. (should It take ages?)
The installer said "This has only been tested on Windows XP" but otherwise did not complain.
....
I have now played some of the demo, and it works fine. Obviously there could be some hidden incompatibility but it looks like there is no problem with Win2K
yes it ALWAYS takes ages to load
Good stuff,
I take it that as you've not replied to the thread in a few hours that it is working well.
I really enjoyed that demo, played it for ages.
Right, this kinda off topic - i've got BF2, it runs fine (not on amazing gxf, but fine). I loaded up the server list, wanting to play online, and i could only find 19 non password protected servers..after a while, i realised that i hadn't patched the game. I dl'd the patch and ran it, it took ages to install (i had to close it after a while) and completely froze my PC..has anyone else had this problem? i think it may be something to do with Norton..
Norton is a possible culprit - it aslways is heh - but with BF2 it's much more likely to be how you patched up the game :)
So your best bet is to re-install completely from scratch (saving your profiles if you wish), and then apply the FULL patch. ie the one that's hundreds of meg in size. This should help to eliminate the possibility of a corrupt install.
Failing that try upgrading gfx etc :)
oh and XP and 2k are not 'virtually identical under the hood', they are different OS's.
This confusion often comes because you can *sometimes* install win2k drivers on windows XP and they will work - and win9X ones will not. This is purely because they are both based on the windows NT kernel/architechture, and so 2k and XP drivers end up being very similar.
I think i found the problem - it's the little feature in Norton that insists on scanning every single archive when you install something, consequently it just keeps scanning the files which is making the patch take ages to run :(
(This is after a reinstall and the full 1.0 to 1.22 patch)