Slashdot Mirror


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!"

13 of 417 comments (clear)

  1. Actual Performance Difference by neomage86 · · Score: 5, Interesting

    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?

    1. Re:Actual Performance Difference by Zeinfeld · · Score: 4, Interesting
      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?

      Its been a long time since I had performance issues due to CPU bottlenecks. My twin processor 650MHz box works just as fast as my 2.4GHz single processor box in practice.

      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.

      I would like Windows to have a meter built in that would show which processes were waiting and the resources they were waiting on.

      My other pet peeve is what the cretins at Checkpoint think is an acceptable VPN client. Every time the credentials time out a box appears for me to re-enter my credentials. Only I use cert based credentials stored in CAPI so all I am doing is hitting OK. Even so the box locks the user interface for about 90 seconds while it does something. Oh @$#(& it did it again.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    2. Re:Actual Performance Difference by Miguelito · · Score: 5, Interesting

      Well I did some benchmarks using openssl's built in speed tests, and running in 64 bit vs 32 bit made a HUGE difference. Of course that was running a 64bit openssl as well. The opterons I have access to even beat the Itanium2s I have access to at work. By a lot in the smaller bit key sizes, but still either tied or beat the ia64 in the larger key sizes.

      Here are the charts I made in OpenOffice on the data I collected. Even a 2GHz opteron beat a 3.2Ghz Xeon in 32 bit mode. :)

      Of course this was just a benchmark, but it does show that things that use openssl would benefit from running under 64bit on an opteron.

      --
      - My favorite error message: xscreensaver, running on an old Sparc 5 w/ 8bit color: bsod: Couldn't allocate color Blue
    3. Re:Actual Performance Difference by Soko · · Score: 4, Interesting

      NT for Alpha had no long pointers and the same 4GB memory limit etc. as its IA32 counterpart. The processor was certainly 64 bits, but the OS was 32 bits at it's core. IIRC there were some places where they had to use 64 in order to get the thing to load, but not where it counted.

      If Microsoft had actually used the Alpha to it's fullest potential, all of my servers would likely be runnning 21464s, not Xeons.

      Yes, I'm still mad at DEC/Compaq/HP for squandering the Alpha tech. *grumble*

      Soko

      --
      "Depression is merely anger without enthusiasm." - Anonymous
    4. Re:Actual Performance Difference by Zeinfeld · · Score: 3, Interesting
      No, no: what he meant was that sometimes (quite often, actually) one process or the whole desktop becomes unresponsive, even though almost no CPU time is being used, the hard drive isn't working, no network traffic should be occuring etc. You just have to assume that something is waiting for something, but there is absolutely no indication what it is. I see such delays almost every day; mostly on Windows (XP and 2000), but occasionaly on Linux too.

      Yep, that is it. I know how to use perfmon, I can recognize an explorer crash. But sometimes the thing just goes off to sleep.

      I noticed a similar issue with dotNET, it can take an awful long time to parse XML and while it is busy it can be stuck at 22% utilization on a 2 proc machine.

      Outlook is also good at doing this when you make the mistake of using MAPI connect mode. The idiots at MSFT used RPC. The program can hang for an hour synchronizing.

      This is all stupid programming, not all in the O/S. I want the O/S to point the finger at the programmer responsible. I want his picture on a Web site.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
  2. Intel will have to follow AMD by Random+BedHead+Ed · · Score: 5, Interesting
    At this point there's enough Opteron stuff out there that Intel can't avoid implementing an architecture compatible with amd64. Yes, I think the timing is probably not a coincidence. Though I'm sure Microsoft wasn't waiting for Intel, they probably informed Groves and Co. of the release in advance.

    If Intel can't stay compatible with AMD's lineup they could end up behind. That would certainly be a first for Intel.

    1. Re:Intel will have to follow AMD by dellis78741 · · Score: 3, Interesting

      The thing that annoys me the most is that Intel has guessed wrong badly twice in trying to drive the market deeper into their corner(RAMBUS, Itanium) and AMD has guessed right both times (DDR, X86-64) and all the time Intel cranks out a profit every quarter and AMD come's up for air for a couple of quarters every other year. If Intel were going against an equal-sized adversary they'd be chapter 11 some years ago for making such mistakes.

      --
      ======= ~\_/~\_O Burmese
  3. Windows Media Player? by ikewillis · · Score: 3, Interesting

    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.

    1. Re:Windows Media Player? by ikewillis · · Score: 4, Interesting
      Evidently you haven't heard about the Windows-on-Windows (WoW) subsystem utilized on AMD64 processors:

      "The Microsoft(R) WOW64 (Windows(R) on Windows) subsystem will allow most 32-bit applications to launch seamlessly on 64-bit Windows," said Brian Marr, Windows product manager. "WOW64 is designed to provide interoperability and great performance on AMD64 processors across the 32/64-bit boundaries. As customers migrate to 64-bit Windows XP and Windows Server, they will have a code base that will support both 32- and 64-bit applications."

      While it's wonderful Linux understands multiple ABIs natively, Windows does not, and utilizes WoW to seamlessly launch 32-bit applications on 64-bit builds of Windows.

    2. Re:Windows Media Player? by Deagol · · Score: 3, Interesting
      How far down will XP-64 thunk, anyway? Are the 16-bit and 32-bit layers at the same level? Or does 16-bit sit on top of 32-bit? So a 16-bit Windows app will be thunked through 2 layers now?

      (Sorry -- I just had to make this post. I remember when all the rags had countless articles on "thunking" when Win95 came out. Will we have the same when the first mass-market 64-bit OS hit the streets? Not that I know of any good PC rags these days -- suggestions?)

  4. Intel is not impressing me these days by AviLazar · · Score: 4, Interesting

    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.
  5. sizeof (long long) == 8... by Ayanami+Rei · · Score: 4, Interesting

    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
  6. Re:64-bit Windows by kylef · · Score: 3, Interesting
    Despite MS market share, I'd guess that there are a lot more 64-bit linux installations around than 64-bit windows.

    You might be correct, but honestly both of us are just speculating. To be honest, I think neither Linux nor Windows can match the number of Solaris 64-bit installations there are in the world. But again, it would be interesting to see some data on the matter. My point was only that one can't call Linux "a much more mature platform," as the previous poster did.

    I do know that HP and one or two others are shipping Itanium2 servers full-steam at the moment, despite Intel's recent 64-bit malaise. It's almost a given that all of those will be running 64-bit Windows. I've seen a demo of a HP 64-bit workstation running 64-bit Windows, and it was really nice. It even had accelerated video drivers, but I don't know what video hardware.

    MS has a big disadvantage here, because they need to wait for their ISV's to produce 64-bit programs as well as drivers.

    This is absolutely correct. If you have source code, you can (usually) just recompile for 64-bit user-mode applications. Otherwise you wait for an ISV to produce a binary for you. But Linux64 is in the same boat with Windows64 as far as drivers go. Arguably worse, since manufacturers have been (until now) unwilling to make their drivers open source and generally produce Linux drivers only after Windows drivers are already complete. And as we all know, the KEY to PC users' hearts is seamless hardware support!