Windows XP 64-Bit Customer Preview Program
MBCook writes "I just notice that Microsoft has a new Windows XP 64-Bit Customer Preview Program starting today (February 3rd). If you have a AMD Opteron or Athlon64, you can go to the download page to get your copy. It's a pre-release copy that will expire in 360 days (which probably means the final will be out by then). Now Intel just changed their 64-bit plans, and all of a sudden this appears. Speculate away!"
"I just notice" that this post wasn't proofed before it was posted.
CB
free ipod and free gmail!
I wonder if a 64 bit OS will make any performance difference for the average desktop user. Since its not like any normal people have more than a gig of ram anyways. Is it possible that it could even slow down 32 bit apps?
We don' need no stinkin' speculation, why this is as obvious as a cow on a haystack!
Seriously, just what grounds do you need for bringing charges of industrial manipulation of the market by the two largest players ? Ok, there's no evidence (yet!), but just how thin can you stretch credulity before SNAP! ?
Simon
Physicists get Hadrons!
If Intel can't stay compatible with AMD's lineup they could end up behind. That would certainly be a first for Intel.
Intel and Microsoft may or may not have a business deal to promote Intel's 64-bit processors. Microsoft wouldn't do this for AMD, because splitting the processor targets would cost Microsoft money. Developing for two processors is more expensive than developing for one. There's no need to delve into anti-corporate mumbo-jumbo to explain this one. It's simple economics, and probably good business from Bill Gates' point of view.
--Guns don't kill people, abortion clinics kill people.
I speculate in a couple days Microsoft will deny this release exists, as they suddenly pull it to give their old cartel partner a chance to catch up and save face.
Consider this:
Microsoft has an evaluation operating system for the Yamhill before Intel actually ships. That doesn't just look like they've been playing patty-cake, but that Intel is running to keep up with AMD. How embarrassing. What's Moore's Law got to say about this? "Every 2 years Intel will get a little further behind where they need to be, by an ever increasing margin until operating systems exists for processors they haven't even designed yet."
A feeling of having made the same mistake before: Deja Foobar
I appreciate the link to Microsoft's website. I've been looking all over for that thing and haven't had any luck finding it. You've saved me from a lot more time spent searching, my friend.
Will the AMD64 build include Windows Media Player? It was left out of the IA64 version due to what I can only assume are 64-bit cleanliness issues with the DirectShow API and WMP code. I can only assume that an AMD64 build would allow 32-bit builds of DirectShow and WMP which execute through the WoW abstraction layer.
Windows XP 64-Bit Edition is designed to address the most demanding needs of technical workstation users who require large amounts of memory
System Requirements:
PC with an AMD Athlon64 or Opteron processor
256MB RAM
Yeah, I know they're minimum requirements, but it's amusing to think that anyone who needed this OS would actually have to refer to them.
The coolest voice ever.
Micrososft is doing this to keep us distracted away from Linux until Longhorn comes out. Two years is a long time, so we can always expect bits and pieces of "neato" stuff in the meantime.
What?
I went to the site and odered a copy of the CD. First Microsoft OS I have bought for many years, but for $US7.95 (including international delivery) the price is quite reasonable and comparable to the competition.
I still recall reading the article in Wired magazine a few months back. A company approached them with an offer to provide them perfect diamond wafers (produced at less then $5/wafer) and Intel did not take the offer because they have not gotten their full investment back on the silicon. So given that they refused to have an easy method of increasing their processor spead by a very big number, it is not surprising that they still haven't gotten 64 bit over AMD... Shame, Intel used to be the best. -A
I mod down so you can mod up. Your welcome.
I suppose it means windows will take 1/2 the time to crash and at least twice as long to write out dump files
Rus
CPanel + Root from $35/mo - 10% off with discount code SLASHDOT
Damn, I never get it straight. Is this software free as in speech or free as in beer? Since the software is only good for about a year, I'd guess this is free as in beer, because my beer has an expiration date too. But does that mean Linux is free as in speech because it doesn't have an expiry? Of course some really skunky beers don't either. Now, can you have free as in beer in a cathedral? All the cathedrals I've been too serve wine. So is this free Windows free as in wine?
See, it's this kind of thing that is holding up the adoption of Linux. It's too confusing.
FLR
I don't read too much into this; Microsoft already told Intel that they (Intel) will in fact stay compatible with AMD because they will not be releasing three separate 64-bit editions of their operating systems (Itanium, x86-64, ???).
In this case, I think the monopoly is working for us in preventing Intel from fracturing the market, which I am quite sure they would love to do.
So in this respect, I think Microsoft is just having the usual Microsoft delays. One of the biggest is supporting Read vs ReadExecute memory pages on the x86-64 chips. A Lot of code, including microsoft code (ATL anyone?), breaks the standards and is having to be cleaned up to work.
In addition, Itanium lacked WMP, DirectX, and many other features that customers will NOT do without on Athlon64 systems, meaning even more development time.
Natural != (nontoxic || beneficial)
char is 8-bit, nearly by definition
short is 16-bit
int is 32-bit (DOS and Xenix are not modern)
long is 32-bit on all Windows OSes
long is the same size as a pointer Linux, BSD, Mac
void* is the natural size for the machine
long long is 64-bit
So 32-bit Windows and 32-bit UNIX have the
same sizes a each other. 64-bit systems differ,
because Windows sets sizeof(long)==4 and a
UNIX system sets sizeof(long)==sizeof(void*).
After installing this release on my MSI K8T-Neo Board, I have no drivers for scanner, printer (LPT1 unsupported...), ISDN PCI Card, Wireless LAN card and many other things.
I spent nights searching and begging for drivers. Thank you Microsoft for bringing this truly Linux user feeling to the Windows platform.
You can see official AMD benchmark results of various programs running on Windows XP 32-bit edition vs. Windows XP 64-bit edition beginning on page 36 of this PDF. The results have three columns: time in seconds on WinXP 32-bit w/ 32-bit executable, time in seconds on WinXP 64-bit with 32-bit executable, and time in seconds on WinXP 64-bit with 64-bit executable.
Erlang.org: wow
The big issue for me are the cases where the stupid machine just locks up and does fuck all for 20 seconds or so. CPU meter shows 3% utilization, no disk activity. What is the stupid thing doing?
Same goes for UNIX systems, its not the processing thats the issues, or even the legitimate I/O delays, its the cretinous delays built into broken device drivers and applications.
On Windows, the process locking up everything here most often seems to be explorer.exe. I've found that going into task manager, killing and running it from there (since you just lost your start menu with the run command) will restore the machine to normal.
Using that little trick every time it starts acting stupid, my windows box is running quite nicely for weeks. Doing it doesn't interrupt any of the applications or services running, the kernel is handling that just fine. Quite silly really.
Kjella
Live today, because you never know what tomorrow brings
Bla bla beowulf bla bla.
Hacker Media
It's a pre-release copy that will expire in 360 days (which probably means the final will be out by then).
Not necessarily, maybe not even likely, particularly for something as big as an XP release. Many's the time that Microsoft has slipped a release beyond such dates. And in many of those cases, an update or date extender patch appeared to cover the slippage (sometimes several such patches).
and the Opteron can hold it one register. Just prefix the instruction with the OTHER size prefix byte. (for those who don't already know, most intel instructions if operating on a 16-bit short require a prefix byte. On the Opteron, you use a different prefix to get 64-bit ints and the extended regs)
There are plenty of places where it makes sense to use 64-bit regs, especially in the kernel when involving counters, timers, GIDs, and such.
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
Here: http://www.microsoft.com/windowsserver2003/64bit/e xtended/trial/default.mspx
Beta of course.
"TK-421, why aren't you at your post?"
Finally, we'll be able to have an integer big enough to count the number of lies SCO has told so far.
boycott slashdot February 10th - 17th check out: altSlashdot.org
The last time I checked, NT is built on something called a "Hardware Abstraction Layer" that made it relatively painless to port NT from MIPS to x86 and then to PowerPC. (NT was designed on MIPS R4000 machines which themselves were completely designed internally by Microsoft. This effort was deemed necessary to keep the codebase free of x86-specific assumptions and optimizations since portability was a key NT goal.) The hardest part about getting your system to run on a new 64-bit platform is getting drivers to work; generally you need lots of support from hardware vendors to accomplish this feat. Getting the OS itself to compile is the easy part.
But I doubt seriously that Windows NT is "so optimized for the older 32bit platform." The kernel is clearly portable to other architectures, and was in fact developed FIRST on a non-x86 architecture with different properties (page size, Endian-ness, etc). This leads me to believe that it is emphatically not "optimized" specifically for 32-bit x86. If you have evidence otherwise, I would like to see it.
Much more mature? Perhaps you were unaware of Windows XP 64-bit Edition? Sure, it only runs on Itanium, but do you not honestly think that for Microsoft to have released it in early 2003 that they would probably have been working on it and testing it for at least a couple years prior to that? Also, from Microsoft's website, I notice that they have also implemented a 32-bit emulation layer for Itanium called "Windows On Windows 64" (WOW64) that lets the OS run 32-bit X86 code. Does Suse have this capability built-in?
The other issue which I pointed out earlier is the driver situation. You can't really call a product "much more mature" unless its drivers are more mature. I don't see a clear win either way at the moment.