First look: Windows XP x64 Edition FINAL

[ULJarad]

It plays worse for you?

[][nSaNe]

yup. it sure does... im not sure i use the omegas in xp and i used the ATI drivers in 64.. in xp i tweak the settings for the drivers.. in x64 i did too a lil.
but not all the way. its prolly something strange.. i dont have network support so i havent downloaded and updates or anything. so i dunno whats up with that.. but i never really played farcry that much anyways.
im a css and bfv lover.

[Jupiler]

Looks like Creative has released some new x64 drivers for their Audigy 2 ZS series.
Most files are dated 04/19/2005, so pretty new.
In case someone is interessted :

http://uk.europe.creative.com/suppor...ds/welcome.asp

[Special_K]

hmmm - that link couldn't find any drivers for K =/

this is where K downloaded the latest Aug16th drivers from

[Jupiler]

hmmm - that link couldn't find any drivers for K =/

this is where K downloaded the latest Aug16th drivers from

I presume you have the Audigy 2 ZS?
If so, select Soundblaster \ Audigy 2 \ Audigy ZS, then click next.
After that, choose the OS (x64), and you'll see the new drivers and Audio Console for the ZS series.

[Special_K]

ahhh - that's why - no ZS here =[

wonder if they will work though?

hmmmmm /K ponders

[ewitte]

LOL. I had no problems with the beta versions. Here are my results on two setups

s754 Clawhammer 6800GT -- Eventually got into Safe Mode and Installed the chipset drivers. Seemed to load fine but eventually gave me blue screens at startup.

s939 San Diego X800XL --

Overclocked (prime stable) - reboots itself when it tries to load
Stock CPU Normal Mode - Hung
Stock CPU Safe Mode - Booted fine. Installed chipset drivers.
Stock CPU Normal Mode - I think it booted fine here until I installed the x64 Catalyst drivers

Stock CPU Normal OR Safe mode - Locks up

All lockups are at acpi???.dll

I've redownloaded the image. I hope that helps. Also I got the MSDN VL version but they don't provide a key for that

Eric

[madpete]

ewitte, can I ask you do you have TCCD? And what is your dram voltage?
If you are above 2.8v try lowering it to 2.7v or 2.75v, this was the only thing that could get me remotely stable in Win64.

[ewitte]

ewitte, can I ask you do you have TCCD? And what is your dram voltage?
If you are above 2.8v try lowering it to 2.7v or 2.75v, this was the only thing that could get me remotely stable in Win64.

I'll try that. I'm running 2.8v. Even normal XP does not load at 2.9v so that could be it. Whats up with TCCD? Its very strange because memtest will run forever on it.

Eric

[madpete]

I honestly have no idea why, but i swear on my system thats what it is (it took me weeks to figure that out ). Wierd thing is that I can run memtest, prime, superpi, winxp (32bit) at high volts with no probs. But anything over 2.75v and Win64 goes tits up, your guess is as good as mine.

[ewitte]

I honestly have no idea why, but i swear on my system thats what it is (it took me weeks to figure that out ). Wierd thing is that I can run memtest, prime, superpi, winxp (32bit) at high volts with no probs. But anything over 2.75v and Win64 goes tits up, your guess is as good as mine.

Actually I'm set to 2.7v already.

[mikem]

Insane....
Are you running only 512 megs of ram?
FarCry seems more jerky to me too....however I noticed the hdd seems to be working its butt off, as I only have 512.

[ewitte]

It seems I have x64 working now but not the X800 drivers Bluescreen everytime I install them. I tried two versions so far.

[Cornelious0_0]

I'll be back to chime in with my 2 cents in the next day or two....downloading Server 2003 X64 Enterprise Edition atm...and I have all my drivers waiting.

I'm hopin' for the best.....and I actually can't wait to get using windowblinds with the above skin...cus I'm using a black/grey theme right now, and that's the nicest I've ever seen.

[[_Silence_]]

Installed Windows XP x64 today. Runs my system @ default but when I try my stable speeds in Windows XP on this x64 version it always gives me a blue screen, saying MACHINE_CHECK_EXEPTION. Anyone knows why?

[Cornelious0_0]

Installed Windows XP x64 today. Runs my system @ default but when I try my stable speeds in Windows XP on this x64 version it always gives me a blue screen, saying MACHINE_CHECK_EXEPTION. Anyone knows why?

I also noticed that.....I only saw it when I knew I was pushing it to far, but the point is that in WinXP it at least gets me into windows.

Other then that, which I've seen people bringing up, Server 2003 X64 Enterprise is running fine for me in my bench partition...but I can't switch my main partition over yet 'cus the Server OS doesn't have the same legacy hardware driver support that XP does, and my Cirus Logic 2MB PCI card gets stuck at 800x600 4bit color, whereas I can do 1024x768 16bit in XP.

As soon as I can get my hands on a PCI Radeon 7000 or GeForce MX4000 that I can install drivers for I'm switching my main partition to server 2003 X64, overall i like the OS, much more responsive....and I'm simply bored of XP and the same old loading screen.

[uscfan]

Stupid microsoft. I hope that the drivers start coming soon. Linux has been ahead of the game for quite some time, they had 64-bit support last year and I'm pretty sure they had it before that just not as mainstream.

Are there really performance increases with the 64-bit os? Anandtech tested Farcry 64 edition and the numbers didnt seem to great.

[fatfreepork]

how is microsoft stupid because they released a 64-bit os? linux has no driver support because most people use windows. and as a user of windows xp, you can't really complain.

[Cornelious0_0]

Are there really performance increases with the 64-bit os? Anandtech tested Farcry 64 edition and the numbers didnt seem to great.

It still stands that games/apps need to be written to take (true) advantage of the 64bit OS...there are some smaller/insignificant gains here and there in some games and benchies...but nothing huge...because not much is actually written FOR the operating system. I think the only reason I saw small SuperPi 1M advantages after the switch was 'cus I went from a tweaked out WinXP Pro install, to a tweaked out Server 2003 X64 install....and Server 2003 itself is most likely what's behind the time differences.