64-bit Windows XP Tested And Reviewed
sebFlyte writes "64-bit Windows is nearly here, despite Microsoft quietly dropping support (and plans for it) for the Itanium on XP ... Windows XP for x64 RC1 has been tested, seemingly fairly thoroughly, and actually looks like a stable OS."
I recently built a Dual Xeon (with EM64T extensions) machine, and I tried Windows XP x64, and it is running pretty well so far. It is backwards compatible with 32-bit applications, but you need to find 64-bit drivers for your hardware. 32-bit drivers will not work.
http://reviews.zdnet.co.uk/software/os/0,39024180, 39183101-5,00.htm
Looks like you drop a few fps when running the 32bit games in a 64bit os. I wonder if new nvidia drivers would make it as fast or faster though...
Live web cams
You and me both. I use it as a gaming OS too. Awesome once you trim down the server fat you don't really need on a desktop. It's XP without the bull, and hand-holding.
I recently upgraded to an Athlon64 3200+ and downloaded the Win64 eval/beta. There's practically no difference between it an Windows XP. I hvaen't had a single weird application incompatibility -- it's running all my 32-bit stuff just fine. I'm a gamer, so "32-bit apps" includes some hefty 3D-accellerated, DirectX-using stuff. I don't have any 64-bit apps to test with.
Hardware support required some initial digging to get drivers, but everything works fine.
In other words, if it weren't for the "64-Bit Edition" on the bootup screen and the Task Manager identifying 32-bit apps as such, I wouldn't really notice a difference between this and regular old WinXP.
Fun with Anagarams! LADS HOST, SHALT DOS. HAS DOLTS. AD SLOTHS, HATS SOLD. ASS HO, LTD.
I actually do this in both a classic and modern sense. Modernly Its Gentoo and XPx64-beta on the modern machine. I've only had it up and running since just 2 weeks prior to christmas, and have had no major hiccups so far. I have concerns about the speed and availibility of service packs and drivers (as in with such a small niche of customers having these processors will Microsoft, and more importantly 3rd party software and driver venders be as dilligent in keeping them updated, prior experience says no) Still It feels faster than having it run XPpro x32. AND it was free for the beta testing, SO, I've got like 340 more days of free OS action to keep me going.
In a Classic sense, right next to the AMD sits an Original, |D|I|G|I|T|A|L| Alpha thats currently running NT4 for Alpha and Gentoo (Though it started out with Red Hat). Running NT4Alpha is one of those things that you never forget. Its fast, stable and relatively virus proof but the biggest problem with it is the LACK OF APPLICATIONS. There were and are no third party apps compiled for NT4Alpha. this was such a major issue that |D|I|G|I|T|A|L| released an emulator thingie, but even that was too little too late to save it.
Thankfully, AMD decided to include Backwards compatibility on the die. because doing it at the higher level chalks up some major performance penalties. But lest we forget, liscensing Alpha technology is the reason we have a lot of the "innovations" boosting speed as of late *cough* Hyperthreading *cough*
---
For great justice move sig
I tried installing it on my R3240 Compaq laptop which has a Athlon64 processor - Installed fine on a external Maxtor USB drive, but when I boot it I get immediate BSOD.
Now the fact that it allowed me to install on a USB external drive is still impressive given the fact that FC3 does not even offer me to install it on USB drive.
But I don't think Microsoft is investing as much testing / development efforts in it compared to what it did during the release of Windows 2000 - which was the first stable kernel from Redmond.
Windows XP 64-bit edition has some major limitations. First, it uses a new driver model that means that all of the 32-bit drivers for your existing hardware will not work with the new Windows. Second, it has no support implemented for legacy 16-bit DOS or Windows apps which will therefore not run on it. The x86-64 cpus have support for running 16-bit software but Micrsoft chose not to enable it. These limitations don't exist for the 64-bit Linux versions. Microsoft ruled the 32-bit desktop but the 64-bit desktop should belong to Linux.
You are feeding the arguments for what I have been saying for years: Not only have the MS monopoly keeped the OS development back. It has also stifled the chip-development. All developers developed for MS-Intel. Nothing else. Most propetary software isn't portable. Therefore there was no applications for NT4 on Alpha. Therefore MS have given up on WindowsNT on PPC even though the OS might be easily portable in itself. Therefore all the superiour architectures to i386 has died.
.Net), which can do hotspot compilation locally. The distribution system of current properetary, closed source software, where precompiled binaries are distributed, kills every attempt to make an architecture which isn't compatible with the dominat i386 (maybe x64 in the future).
If we are going to get new architectures - if it is not already too late - on the desktop we have to take either the route of open source, where each user (in principle) can recompile the application for his architecture, or the route of virtual machines (Java or
There is a good thing happening though: Intel and AMD seems to got stuck wrt. clock-speed. They can't make the CPUs run any faster now. They have to go for hypethreading or multi-core chips. For that to give any performance benifit most applications have to be rewritten. If while doing that people start to think about portability ther might be a chance that those rewritten applications will also run on other architectures. Even PC programmers aren't living in the near-assambler programming world as they did in the 80's and beginning of the 90s anymore!
I have 64 bit fedora core 3 installed on my laptop right now. The OS works great, but there is a big lack of wireless card drivers. Now with 32bit linux, you are able to run the windows wireless drivers using emulation in linux fine; however, since the windows drivers are 32 bit, you can't use them with a 64 bit os! XP64 should bring more 64 bit wireless drivers, which could be emulated in linux, thus allowing me to use wireless in linux, instead of having to boot to windows to get a wireless connection!
Boxing Equipment Reviews
You're kidding, right? Who gives a flying fuck about 16-bit applications anymore? Sure, maybe if your company is running applications from 10 years ago, but if so, I doubt your company will be investing in 64-bit machines for all its staff any time soon.
And oh no, you have to get new drivers! Hint: in Linux, you also have to get new drivers when you upgrade to 64-bit; you're just lucky that you have the source available. In any case, who cares? Your motherboard manufacturer will certainly be supplying 64-bit drivers, and ATI, nVidia, and Creative Labs already supply them for their products. Ok, so a couple of your PCI cards may not have drivers for a couple of months. Well, don't upgrade yet. You live on the bleeding edge, you have to expect a few problems.
When i ran Server 2k3 as my desktop, i had to ADD desktop fat. Turning on the Sound subsystem, install java, turn on graphics acceleration, loosen up security in IE, install firefox, enable direct X, install XP video card drivers (I had an ATi card back then, and they don't produce drivers for 2k3 like nVidia does), turn on image acquisition, turn on the CD burning subsystem, tweak memory usage to make it run more desktop-friendly. The only thing you actually turn off (and really don't have to) is that annoying shutdown tracker.
To me, and this is just me...you might have a totally different definition of "trim", that seems more like adding services that are unneeded for a server. Like i said before, Desktop "fat".
"actually looks like a stable OS."
I remember hearing that about NT, then NT4, then Win2K, then WinXP.
Sorry, Microsoft, you've cried wolf too many times. I don't believe it. Or maybe they mean "stable" as in "as stable as WinXP", i.e., "not very stable".
I've been doing catalog tearsheets for sometime in Photoshop, and I'm routinely getting up to gigabyte+ images. With WIN32 restricting me artifically to 2GB total memory usage per program, I cannot do much better than this without 64 bit support. And in a year or two, I may be pushing that limit.
32 bits is just barely sufficient for me now.
With most processors on the market in the next 2 or three years being 64 bit, who cares? It's the next wave.
Build version 1289 of XP professional is MSDN only at the moment, and is supposed to be released to CPP towards the end of the month.
I am running 64-bit 2003 server at the moment on a 3000+ amd64 and it just flies along. No real issues so far, apart from dvd layback and some motherboard incompatibility with some graphics cards, but that is a seperate issue.
I'd suggest trying it for a while. Some of the default security makes sense now, compared to that in vanilla XP.
- This sig deliberately left blank. Nothing to see, move along.