Slashdot Mirror


Windows XP X64 Goes Gold

Kasracer writes "According to The Inquirer, 'Microsoft has released the final version of Windows XP 64 to manufacturing, meaning that those with machines that have 64-32 bit processors in from AMD and latterly Intel can now see what the extra addressing brings to the party.'"

61 of 359 comments (clear)

  1. If it went gold by Anonymous Coward · · Score: 5, Funny

    ...why are they so afraid of pyrites?

    1. Re:If it went gold by Rosonowski · · Score: 4, Funny

      Well, they're still trying to iron out all the bugs.

      --
      01101001 01100001 01101101 01101110 01101111 01110100 01100001 01101100 01100001 01110111 01111001 01100101 01110010
    2. Re:If it went gold by Everleet · · Score: 5, Funny

      Steeling it should be easy, just watch out for coppers.

      --
      It's tragic. Laugh.
    3. Re:If it went gold by Anonymous Coward · · Score: 5, Funny

      Steeling it should be easy, just watch out for coppers.

      That's not what I've been lead to believe, but your statement gives me a silver of hope.

    4. Re:If it went gold by Kevin+Khatchadourian · · Score: 5, Funny

      A waste of a silver tongue but it lead to this you guys need a kick in the brass, that's what I zinc at least.

    5. Re:If it went gold by kclittle · · Score: 5, Funny
      I think you guys are trying to be funny, but I'm not sure -- I have such a tin ear for puns.

      --
      Generally, bash is superior to python in those environments where python is not installed.
    6. Re:If it went gold by fyngyrz · · Score: 4, Funny
      I thought I smelt an attempt at humor. I mean, generally I don't mine this kind of thing, but something more refined than all these digs is what shows your metal, don't you think? You're just giving people the shaft when you alloy yourself with earthy humor of this type. Crystalize your thoughts, you'll just lava the results. Puns are too mercurial to keep you golden; I suggest you forge something more lasting and fold in some edgy commentary, that'll cut a swath through the readership. Dig?

      Thanks, I'll be here all week.

      --
      I've fallen off your lawn, and I can't get up.
    7. Re:If it went gold by Atmchicago · · Score: 4, Funny

      I think you just alluminated the world of puns for the rest of /.

      --

      You can lead a horse to water, but you can't make it dissolve.

    8. Re:If it went gold by fyngyrz · · Score: 4, Funny
      Curses, foiled again!

      --
      I've fallen off your lawn, and I can't get up.
    9. Re:If it went gold by Junior+J.+Junior+III · · Score: 4, Funny

      If you mangle your English enough with metallic puns, are you in fact actually speaking manganese?

      --
      You see? You see? Your stupid minds! Stupid! Stupid!
  2. Is there a list of softare ready for it? by airjrdn · · Score: 4, Interesting

    Anyone aware of a list of Windows software (perhaps on MS's site) that'll benefit from it?

    1. Re:Is there a list of softare ready for it? by Glonoinha · · Score: 4, Informative

      You can throw 2-3G of memory at 32-bit applications right now using regular XP Professional or 32-bit Windows 2003 Server. With the new 64-bit version of Windows 2003 Server Enterprise you can throw a full TeraByte of physical memory at a single application. Good luck getting that much physical memory in a box right now, but you can get 32G or maybe 64G in a single machine right now if you try real hard (and have a LOT of cash.)

      Something tells me Duke Nukem Forever will take full advantage of the 64-bit platform.

      --
      Glonoinha the MebiByte Slayer
    2. Re:Is there a list of softare ready for it? by ergo98 · · Score: 5, Informative

      With the .NET Framework as "64-bit native", all .NET apps will immediately benefit, and the JIT compiler can take advantage of all of the goodness of x64.

      In the binary world, an upcoming version of SQL Server 2005 x86 is promised.

    3. Re:Is there a list of softare ready for it? by ergo98 · · Score: 5, Informative

      I should note that the 64-bit .NET Framework isn't actually out yet: I don't believe it was delivered with the 64-bit XP. That was more of a "future focused" comment about an upcoming variant of the .NET Framework 2.0 that will be 64-bit.

    4. Re:Is there a list of softare ready for it? by DaHat · · Score: 3, Interesting

      IIRC, 2k and XP pro both are limited to 4 gigs of ram. Assuming you have that much, a single app is pretty much limited to 3 gigs of the system, that leaves just 1 gig for everything else. Move to a 64-bit machine with XP64 with say... 8 gigs, the same app still gets it's 3 gigs of ram (or more if it asks), leaving a full 5 gigs for the rest of the system and other apps.

    5. Re:Is there a list of softare ready for it? by Darren+Winsper · · Score: 4, Informative

      By default, 32-bit XP gives user-mode applications 2GB of addressable space, leaving 2GB for the kernel's address space.

    6. Re:Is there a list of softare ready for it? by DarkEdgeX · · Score: 4, Informative

      No, wrong. Current .NET apps will run in the context of the 32-bit .NET runtime, meaning they won't benefit from the larger address space or the eight additional general purpose registers. In order to run in the context of the 64-bit .NET runtime the header of the executable needs to contain specific flags.

      Also, .NET apps which thunk to external 32-bit DLL's for added functionality won't work with the 64-bit .NET runtime (e.g. - if you call out to kernel32.dll or any of the standard Win32 DLL's your code will, of course, not work with 64-bit DLL's).

      --
      All I know about Bush is I had a good job when Clinton was president.
    7. Re:Is there a list of softare ready for it? by gr3kgr33n · · Score: 4, Informative

      as a person currently running XP-64 Beta, Here are the gripes I have: Drivers must be 64-bit == Most Drivers 'cept nVidia and a select few others are 32 .Net Framework 64 is "out" With the lack of driver support, running XP-64 is a hit or miss operation currently. Luckly my board has most things onboard and gigabyte was kind enough to give me 32-bit versions of all my drivers. Thank you gigabyte for giving me 32 bit drivers with a 64 bit board, shure these guys don't work for microsoft?

      --
      My backup chemistry thesis stored on Data Storing Bacteria mutated; granting me a degree in forensic anthropology. v4sw7
    8. Re:Is there a list of softare ready for it? by x0n · · Score: 3, Informative

      Aye, but there is a /3GB switch you can use in boot.ini:

      "Increases the size of the user process address space from 2 GB to 3 GB (and therefore reduces the size of system space from 2 GB to 1 GB). Giving virtual-memory- intensive applications such as database servers a larger address space can improve their performance. For an application to take advantage of this feature, however, two additional conditions must be met: the system must be running Windows XP, Windows Server 2003, Windows NT 4 Enterprise Edition, Windows 2000 Advanced Server or Datacenter Server and the application .exe must be flagged as a 3-GB-aware application. Applies to 32-bit systems only."

      (take from sysinternals.com, a la Mark Russinovich)

      - Oisin

      --

      PGP KeyId: 0x08D63965
    9. Re:Is there a list of softare ready for it? by truesaer · · Score: 4, Informative
      Here are the gripes I have: Drivers must be 64-bit == Most Drivers 'cept nVidia and a select few others are 32 .Net Framework 64 is "out" With the lack of driver support, running XP-64 is a hit or miss operation currently.


      FYI, 64-bit drivers are required when running in 64-bit long mode on the processor. So it isn't an artificial limitation of Windows 64, but rather a requirement imposed by the processor.

      For those who aren't real familiar with AMD64 architecture, it works basically like this: The processor starts in real mode, and at some point the operating system sets up the necessary mechanisms to support protection, paging, interrupts, etc. At the point it switches the processor into protected mode which is where all modern operating system and code run. There is also a virtual 8086 mode to run native DOS type applications, which is where the run dialog in windows executes. These three modes are known collectively as legacy mode.

      From protected mode if you want to run 64-bit code you need to switch into long mode, which is a collective name for 64-bit mode and compatibility mode. 64-bit mode is a pure 64-bit environment. The operating system must run in this mode, and all drivers must be 64-bit. I believe this is because interrupts automatically switch the processor into 64-bit mode. On a code segment by code segment basis you can also run in compatibility mode, which allows 32-bit code to be run in long mode. That is how all the current 32-bit apps will be able to run even in long mode. so from protected mode the OS must switch into compatibility mode, then into 64-bit mode to run 64-bit code. Once in compatibility mode any interrupt will force a switch to 64-bit mode, which is why drivers need to be 64-bit.


      Its also worth noting that switching from 64-bit mode to compatibility mode and back has been designed to have no performance penalty.

  3. Is it the season? by Hephaestus · · Score: 4, Interesting

    It seems to be the season for OS updates, doesn't it? :-)

  4. Longhorn by Daxx_61 · · Score: 5, Interesting

    What I don't understand is why they didn't just pump the money and development time for 64 into Longhorn. Surely that would have brought down development times, and we could have it sooner?

    --
    Quoth the server, "404."
    1. Re:Longhorn by caston · · Score: 4, Informative
      Because 64 bit Linux has been around for a long time now and its making MS look very very outdated. This shows they are scrambleing to keep up now.

      --
      Beings aspergers AND pulling chicks... I enjoy the challenge!
    2. Re:Longhorn by netrage_is_bad · · Score: 5, Insightful

      It for the Money. If everyone with a 64bit processor buys an essentially recompiled version of XP, and then buys longhorn when it comes out (whenever that is) they have successfully sold one more product than they would have.

    3. Re:Longhorn by MoonFog · · Score: 4, Informative

      The XP version if available for free download and if you're talking about bundling XP-64 with pre-built computers, they would most likely come with Windows XP either way. I think it's more about the fear of losing customers rather than trying to trick people to buy two OS'. Besides, if MS where to go another full year without an OS with full 64 bit support, it could be bad for business.
      I agree to with you to a certain degree, I just think you're maybe a little too paranoid.

  5. Historian Publishes! by Spawn+of+CowboyNeal · · Score: 4, Funny

    Ganymede's report on the CRAPPIEST 64-bit operating systems in the World

    1: Windows XP X64

    that is all.

    1. Re:Historian Publishes! by BinLadenMyHero · · Score: 4, Informative

      Whoever modded this down missed the reference to the excelent Civilization game. It periodicaly lists the top richest/welthiest/militarized/advanced/largest nations of the World.

      In fact, I've played only Freeciv (and not the original one) for a long time, but I'm pretty sure the Historian Publishes were on the original also.

  6. 4/1 by Primal_theory · · Score: 4, Funny

    Ok, is it still april fool's day somewhere?

    --
    Your skill in reading has increased by one point!
  7. And ... by canwaf · · Score: 4, Funny

    Bring on the 64 bit Viruses!

  8. Heh by strider44 · · Score: 5, Funny

    we can now say "finally Windows has caught up with Linux".

    Cue the candid laughter everyone.

    1. Re:Heh by Waffle+Iron · · Score: 5, Informative
      NT4 for Alpha was pure 64-bit

      It's highly debatable whether you could call it "pure 64-bit". A description of the implementation from here:

      Also, the Windows NT implementation on the Alpha was not really true 64 bit, but used a less ambitious system called VLM to allow access to more memory than 32 bit system. Here's a quote from Microsoft about it:
      "As you can see, the VLM APIs don't constitute true 64-bit computing. Sure, you can allocate and use this memory if it's physically present, meaning that virtual memory doesn't work with these addresses. But 99.44 percent of the Win32 API can't work with addresses above 4GB, so it's just you and your 64-bit pointers. Think of it as frontier territory with no newspapers, running water, or phone lines."
    2. Re:Heh by fyngyrz · · Score: 3, Interesting
      Think of it as frontier territory with no newspapers, running water, or phone lines."

      I prefer to think of it as frontier territory without resource and memory leaks, buggy system calls, and insanely bloated, sourcecode-free "objects" that are larger than most applications used to be but provide unique and special capabilities like "buttons" and "checkmarks."

      But that's just me. :-) When I encounter something from Microsoft that is broken (like a file dialog ot the treeview control) then I write my own, make sure it works, fix it ASAP if and when anyone finds anything I missed... so memory where MS's OS fears to tread smells like freedom and clean air. There may not be any toilets, but then again, I don't have to have Microsoft's sewage running all over my applications.

      Real conversation from about 2002:

      CUSTOMER: Why, when I select more than 100 image files in the "load file" dialog, do the files come in in reverse order and missing any that were past about the 105th selected file?

      US: Yeah. Those are problems in Microsoft's file dialog. According to MS, the 100 file limit problem has been in there since Windows 95. The files in reverse order happens because you selected the first file first, and shift-selected the last file, last. You can select the last file first and the first file last, and they'll come out they way you want them. As long as there are under 100 or so names. But you can just download the latest revision of our application and that problem is gone. Along with Microsoft's file dialog.

      We gave them this, instead.
      --
      I've fallen off your lawn, and I can't get up.
  9. April Fool ? by zbeeble · · Score: 3, Funny

    Yesterday's stories where more convincing.

  10. Now only a few more years..... by Laurance · · Score: 4, Insightful

    Now only a few more years and we might have 64 bit applications

  11. Re:Is this Longhorn? by MoonFog · · Score: 4, Informative

    What? This is just a new version of Windows XP, afaik it has nothing to do with Longhorn which is a totally new OS.

  12. can now? by Anonymous Coward · · Score: 5, Informative

    that those with machines that have 64-32 bit processors in from AMD and latterly Intel

    (1) The opteron is a true 64-bit architecture. The em64t (intel thing) is a bit of a bodge (still basically a xeon core, with shades of 32-bit-ness in odd places like memory mapping for devices), but still appears 64 bit.

    (2) Linux people have been running x86-64 Linux for _ages_ now. It's a cheap and cheerful server platform without some of the worst cruddiness of x86, and a cheap, extremely cost effective, and generally excellent scientific workstation and compute cluster platform, and is selling like wild here (euro) anyway.

    1. Re:can now? by Anonymous Coward · · Score: 5, Informative

      Look around for the implications of EM64T not having an IOMMU like AMD64 does. This is what the guy was talking about.

      With EM64T you can't do DMA from devices to addresses above 32bit. This means that the transfers have to be done into a buffer below 4Gb and then copied over to the application buffer (above 4Gb). This implies a serious performance penalty and puts EM64T out of the "true 64bit" bag.

    2. Re:can now? by l3v1 · · Score: 3, Informative

      1) x86-64 is the same on both Intel and AMD. If they were really different, we would target Intel because Intel is shipping 10x the x86-64 volume AMD does.

      As also one of the responses to this point out, you're not entirely right here. As I know it - and I'm not trolling here, just not having too much hands-on experience, so I could be somewhat wrong - they may "seem" equal, that is you can code almost exactly the same on them, but internally Opterons give you a 64bit architecture with all the benefits (and hypetransport being the chocolate on the cake) with 32bit compatibility, while 64bit-extended Xeons seem to be just as the name suggests.

      --
      I am putting myself to the fullest possible use, which is all I can think that any conscious entity can ever hope to do.
  13. Don't get *too* excited yet... by pla · · Score: 5, Informative

    meaning that those with machines that have 64-32 bit processors in from AMD and latterly Intel can now see what the extra addressing brings to the party.

    ...Unless you want to run hardware not built into a mainstream motherboard with support included in XP.

    ...Unless you want to run software using a legacy 16-bit installer (far more common than you might expect, even for programs that don't have a drop of 16-bit code themselves).

    XP for x64 has NO 32-bit hardware driver support. Very very few manufacturers have x64 drivers available yet. Thus, don't feel surprised when you literally can't use any of your fancy toys. On the bright side, NVidia does have beta 64-bit drivers available, so you might luck out. Of course, considering the stability of final-release NVidia drivers, do you really want to use a beta?

    XP x64 has also completely dropped 16bit support. No more old DOS programs. No more Win3.1 programs. More importantly (as I mentioned above), no more installers that used 16 bit code, even for purely 32-bit programs.

    I too look forward to running XP x64 on my Athlon64. But for the moment, the average Joe just doesn't have that as a realistic option. In another six months, perhaps. But not yet.

    1. Re:Don't get *too* excited yet... by Anonymous Coward · · Score: 4, Insightful


      XP x64 has also completely dropped 16bit support. No more old DOS programs. No more Win3.1 programs. More importantly (as I mentioned above), no more installers that used 16 bit code, even for purely 32-bit programs.

      I say good riddence.

      I too look forward to running XP x64 on my Athlon64. But for the moment, the average Joe just doesn't have that as a realistic option. In another six months, perhaps. But not yet.

      Your average Joe probably isn't using a 64 bit x86 chip either.

      The transition has to start sometime. If not now, when?

    2. Re:Don't get *too* excited yet... by pla · · Score: 3, Insightful

      Excuse me but if you are still running a 16-bit application, then you are in a very special situation. And you are keenly aware of that fact.

      The application itself, probably. But you apparently missed the point about the installer... If you can't install your 32 or 64 bit program, you can't use it.

      It might also suprise you just how many programs do still use 16-bit code. A lot of command-line utils, for one. A lot of low-end games (card and puzzle-type), for another. Now, you might say that you never use the command line or play Chips Challenge, in which case, good for you. But most of us just expect our computers to do what we want them to.


      Now, with the 32-bit hardware driver problem, I can understand that. But Microsoft already ran 16-bit apps under emulation since the earliest days of NT (via NTVDM or WOW - If you ever see either of those in yout task manager, you still use 16-bit code for something) - I see absolutely no reason whythey would have discontinued that.

    3. Re:Don't get *too* excited yet... by imsabbel · · Score: 3, Interesting

      INstallers arent a problem.
      There are traps that intercept them and run an installshield/ect emulation.

      --
      HI O WISE PRINCE. WHT TOOK U SO DAM LONG?
  14. It's all fun and games... by Anonymous Coward · · Score: 5, Funny

    "Anyone aware of a list of Windows software (perhaps on MS's site) that'll benefit from it?"

    Solitaire.

  15. Is it worth upgrading? by AGTiny · · Score: 3, Interesting

    I run XP on an AMD64 laptop. Would I gain anything by upgrading to this or not?

    1. Re:Is it worth upgrading? by KidHash · · Score: 5, Informative

      It depends, what do you use your laptop for? Unless you're doing scientific work, or playing a game which is 64-bit optimized, then no.

      And even if you are doing those things, only if the drivers are available.

      Basically, hold off unless you have no choice

  16. Re:Is this Longhorn? by MoonFog · · Score: 5, Informative

    No, Longhorn is the (code) name for the next version of Windows. XP-64 is just an upgrade, adding the 64 bit addressing possibilities to the Windows XP OS.

    Longhorn will not be out until next year at the earliest.

  17. Re:Is this Longhorn? by wpmegee · · Score: 3, Informative

    No. This is just Windows XP. Games and other apps will have to be recompiled to take advantage of it - UT2004 has a beta out, don't know of any others available.

  18. My contribution to the list: by Anonymous Coward · · Score: 3, Informative

    LightWave 3D, by NewTek.

  19. The scientific discovery of the decade.... by carlmenezes · · Score: 3, Funny

    MS Gold can actually rust

    --
    Find a job you like and you will never work a day in your life.
  20. Gold Plating by turgid · · Score: 3, Funny
    Microsoft was well aware of the old saying, "You can't polish a turd," so not to be defeated, they gold-plated it instead.

    /me ducks.

  21. "Can now see" by m50d · · Score: 3, Informative

    Or they could have used SUSE and have seen what it does, what, 5 months ago?

    --
    I am trolling
    1. Re:"Can now see" by rsax · · Score: 4, Informative
      Or they could have used NetBSD which was ported to the AMD 64 bit processor before it was even released..... in 2001.

      Booya!

  22. Re:Oh good... -- No, you are incorrect by Ada_Rules · · Score: 5, Funny
    ...now I get to have twice as many problems than I have now with XP 32? :)
    This is a common misconception. 64 bit computing does not give you twice as many problems as 32 bit computing. Each time you add a bit you double the problems so in fact you will have 2**32 more problems. The only issue I see is that many of the problems do not really show any increase at 64 bits yet so we will have to wait a while for all of the vendors to port them. I hope this clears things up ;)
    --
    --- Liberty in our Lifetime
  23. Re:Is this Longhorn? by Jugalator · · Score: 4, Informative

    I thought longhorn was XP + 64-bit.

    I don't know where all misinformation about Longhorn being aimed for 64-bit processors come from. I keep seeing it everywhere on forums.

    Longhorn will be released just like Windows XP; in 32- and 64-bit editions.

    --
    Beware: In C++, your friends can see your privates!
  24. The biggest challenge for Windows... by Illserve · · Score: 4, Funny

    As processor speed, memory and disk space continue to spiral to ever larger values, Microsoft is really going to be put to task in finding ways to make Windows sluggish.

    Their task is made more difficult by advances in compiler design which find an eliminate trivial solutions that simply chew up CPU time by computing huging cosine tables and then overwriting them.

    New innovation may come from recent advances in polling network devices unnecessarily and hanging various threads until a reply is received. In the case of pulling a device off the network that Windows Explorer had browsed in the last 15 weeks, a given thread can hang for minutes, chewing up processor time in loops that scan network traffic.

    The Windows Development team seems optimistic that they can produce the same crippled user interface on new 64 bit architectures that customers have become familiar with, a valuable marketing strategy in teaching consumers to become suspicious of computers with more responsive interfaces.

  25. "extra addressing...." by Anonymous Coward · · Score: 5, Informative

    The advantages of the AMD-64 archetecture go far beyond the additional address space. The number of general purpose registers is doubled (and, of course made 64 bits wide). This is far more important than the increased address space and, for most code more important than being 64 versus 32 bit.

    Translation: If you've never heard of a register, what this means is that there are twice as many internal storage locations in the processor. moving data between internal registers suffers from no delay, while accesses to memory (ram) is slow and processing cycles can be lost to wait states - basically the processor must pause and wait for the memory access to get done.

    This is why most code when recompiled for the new architecture will see an immediate performance improvement. Some code will see gains from the 64 bit width of these registers - but not as much. Virtually no one will see a benefit from being able to use more than 4gb of ram.

  26. April Fool's Day Was Yesterday by Pensacola+Tiger · · Score: 3, Funny

    Just like Microsoft - one day too late.

  27. Coincidence by ozmanjusri · · Score: 3, Interesting

    Maybe it's my tinfoil hat speaking, but isn't it strange that Microsoft release a 64bit OS just a few weeks after Intel releases their 64bit x86 cpu http://hardware.slashdot.org/article.pl?sid=05/03/ 22/0235246&tid=118&tid=137 even though AMD have had their processor out for more than eighteen months?

    --
    "I've got more toys than Teruhisa Kitahara."
  28. The Horse's Mouth by PizzaFace · · Score: 4, Informative

    Microsoft has a website for Windows XP Professional x64 Edition. The site has a pseudo-technical overview of the product, and more detailed information for developers.

  29. Slashdot bias showing? by Anonymous Coward · · Score: 3, Insightful

    Windows XP X64 went gold on March 31 and we see it on /. two days later?
    Tiger went gold on April 1 and no time was wasted in posting that news.
    Both are closed source operating systems.
    Explain.

  30. Get 64-bit applications now. by Inoshiro · · Score: 4, Interesting

    Grab a 64-bit Linux distribution. Yet another benefit of opensource is that people can freely recompile to 64-bit. I'm running 64-bit KDE 3.4.0 on my 64-bit Linux 2.6.11 on my Opteron 3000+. It runs WoW under 32-bit Cedega nicely as well (in addition to Starcraft/Diablo, etc). No need to chain yourself to a legacy OS for a few applications you can easily run in Linux :)

    I run Slamd64, the x86-64 Slackware.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.