Slashdot Mirror


Microsoft To Dump 32-Bit After Vista

SlinkySausage writes "Microsoft has used its annual hardware engineering conference to announce that Windows Vista and Server 2008 will be the last versions of Windows capable of booting on 32-bit CPUs such as Intel Pentium 4 and Core Duo. AMD, which introduced 64-bit CPUs early — much to the derision of Intel, which said there was no use for them at the time — must be delighted with Microsoft's decision. Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run."

527 comments

  1. as the owner of a first gen intel mac.... by catbutt · · Score: 5, Funny

    ....I assure you, I'll be alright.

    1. Re:as the owner of a first gen intel mac.... by the_humeister · · Score: 1

      Until Apple also stops supporting 32-bit computing. The way I see it, the 64-bit PowerPC Macs will have a longer support span than the first generation Intel Macs because they're only 32-bit computers.

    2. Re:as the owner of a first gen intel mac.... by gumbi+west · · Score: 2, Insightful
      What, are you nuts? This means that in seven years you're computer won't be able to run a newer MS OS that's worse than Vista, but with MS games that lock out Vista. You'll be stuck with OS 10.8 with a dual boot to XP or Vista or any of a number of *nix OSs. A sad, sad computer it will be.

      Actually, what I thought was crazy is that Apple customers aren't the only ones using the Core processors, why single them out? Is Apple even the largest customer of Intel 32-bit processors?

    3. Re:as the owner of a first gen intel mac.... by CarnivoreMan · · Score: 0, Redundant
      Current computers can hardly run Vista as it is... I dont think it'll be much of a concern when the next iteration of Windows comes out and requires a new set of hefty hardware requirements relative to the state of technology at the time.

      What will the recommended RAM be by then... 8 or 10 Gigs?

    4. Re:as the owner of a first gen intel mac.... by JohnnyGTO · · Score: 0, Redundant

      Me to.

      --
      Si vis pacem, para bellum! For evil to succeed good men need only do nothing!
    5. Re:as the owner of a first gen intel mac.... by Mattintosh · · Score: 1

      There was active 68k code in the classic MacOS right up to the end. The end was over 10 years after they produced the final 68k Mac. That doesn't mean the system would run on 68k, but it does mean that Apple isn't afraid to support legacy code.

      Similarly, if they want OS X to work on 32-bit CPU's for the next 5-10 years, it will. They'll support it. And given the fact that they're still selling 32-bit Core systems (the Mac Mini does not have the Core 2 yet), they'll support it for a long time to come. I'd give it until 2015 before Apple tells Core system users that they're up a certain creek sans paddle.

    6. Re:as the owner of a first gen intel mac.... by kestasjk · · Score: 1

      Your PC will be unable to run a supported version of Mac OS X in 2 years, and will be unable to run the latest lot of software that requires the latest version of Mac OS X in 1 year, let alone the next version Windows in ~5 years.

      --
      // MD_Update(&m,buf,j);
    7. Re:as the owner of a first gen intel mac.... by ceoyoyo · · Score: 2, Funny

      Windows XP recommended memory: 128MB.

      Vista "Premium ready": 1GB.

      So assuming linear increases the successor would recommend 8 GB. Naturally the increase isn't linear though. To calculate that you'd have to fit an exponential to past OS releases, and I've got better things to do.

      It's also interesting to note that XP required a graphics card with 1 MB of RAM. Vista PR (he he) recommends 128-512 MB. Assuming linear increases that's 16 GB of graphics memory for the successor!

    8. Re:as the owner of a first gen intel mac.... by Kadin2048 · · Score: 4, Interesting

      Actually, what I thought was crazy is that Apple customers aren't the only ones using the Core processors, why single them out? Is Apple even the largest customer of Intel 32-bit processors?

      Apparently because on Slashdot, making some sort of backhanded Apple comment at the end of every story guarantees a lot of comments.

      I thought it was a total non sequitur, too. Apple users will be upset? How about all the people who can't reboot into OS X and go on their merry way? I think they're going to be a bit more pissed.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    9. Re:as the owner of a first gen intel mac.... by Anonymous Coward · · Score: 0

      ...seeing as I'll have long since upgraded to a machine of a newer, shinier color.

    10. Re:as the owner of a first gen intel mac.... by ubuwalker31 · · Score: 1

      Luckily, I have a 64 bit Intel Core Duo 2, not a Core Duo.

    11. Re:as the owner of a first gen intel mac.... by ZorinLynx · · Score: 1

      My XP VM on my Macbook Pro has 128MB of RAM assigned to it, and it actually runs pretty well for what I need (primarily sysadmin stuff)

      Just shows how bloated things have gotten.

    12. Re:as the owner of a first gen intel mac.... by h2g2bob · · Score: 1

      Nitpicking, but that's not linear growth. Rather it is exponential growth.

    13. Re:as the owner of a first gen intel mac.... by nine-times · · Score: 4, Insightful

      Yeah, I know. What's the deal with the OP?

      Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run.

      This leads me to a few questions:

      • Of all the people using 32-bit processors, why single out Mac users? Mac users often don't even use Windows at all.
      • ... which leads me to a second question: Is this supposed to be sarcastic?
      • What makes you think Microsoft will stick to this?
      • What makes you think we won't all have new computers before Microsoft releases their successor to Vista?

      Microsoft is notorious for having high expectations and grand plans, taking too long to execute, and dropping most of their features, improvements, and changes before the end product is released.

    14. Re:as the owner of a first gen intel mac.... by AKAImBatman · · Score: 4, Interesting

      Since I've been itching to try out the new Charts feature on Google Spreadsheets anyway, I threw together a spreadsheet of the Windows memory requirements:

      http://spreadsheets.google.com/ccc?key=pdgLUlhjY22 Avkn0zhNfTcQ

      If that isn't a hockey stick chart, I don't know what is.

      BTW, does anyone know how to get the labels to show up correctly?

    15. Re:as the owner of a first gen intel mac.... by ceoyoyo · · Score: 1

      Nope, it's linear growth in system requirements. I did assume the time between releases grows exponetially though. ;)

    16. Re:as the owner of a first gen intel mac.... by Bert64 · · Score: 4, Informative

      Well, mac users often keep their machines for much longer than windows users... I still use a 400mhz G4 and it runs OSX Tiger perfectly well.

      Tho, it does bring up an important question....
      Why did Apple start with core duo processors? They could have made a clean break to 64bit x86 hardware, instead of going 32bit and having to migrate later?

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
    17. Re:as the owner of a first gen intel mac.... by theun4gven · · Score: 1

      Running 10.4 on a 6 year old Mac with no problems. In fact, each successive upgrade, i.e. from 10.3 to 10.4, has caused a noticeable increase in responsiveness in the OS and the programs I run. At this rate, I'm really looking forward to every new iteration of the OS.

    18. Re:as the owner of a first gen intel mac.... by duckbillplatypus · · Score: 1

      Here1 Here! As the owner of a Mac capable of running 64 bit windows, I couldnt care less, if M$ announced it was getting out of the OS market entirley.

    19. Re:as the owner of a first gen intel mac.... by ceoyoyo · · Score: 1

      Don't know anything about Macs, do you?

      Apple started transitioning away from PowerPC two years ago (less a month), a MUCH bigger jump then from 32 bit to 64 bit processors. Machines with PowerPC processors are still supported, and Apple has promised that they will be for a long time. That includes by all the apps.

    20. Re:as the owner of a first gen intel mac.... by NekoXP · · Score: 1

      Because it would have delayed the transition by a year and IBM and Freescale weren't even close to successor chips (and really, still aren't) for Apple's desktop domination plans.

    21. Re:as the owner of a first gen intel mac.... by irote · · Score: 1

      Thanks. I just realised how impressive Google spreadsheets is. It's spectacular to see the notification boxes appearing in quick succession at the bottom right, telling you that yet another person's started looking at the spreadsheet. It's so seamless.

    22. Re:as the owner of a first gen intel mac.... by nine-times · · Score: 1

      Why did Apple start with core duo processors? They could have made a clean break to 64bit x86 hardware, instead of going 32bit and having to migrate later?

      I'm not sure why they wouldn't have. Apple doesn't seem to have a big problem with supporting multiple architectures. I could be running OSX on a G4, G5, Intel 32-bit or Intel 64-bit, and I can't really tell the difference except for speed. They needed to make the transition at a specific time, and so they used the best x86 processors available at the time. The transition to 64-bit hasn't really caused any problems.

    23. Re:as the owner of a first gen intel mac.... by EvilIdler · · Score: 1

      Got a picture? That spreadsheet requires a login :/

    24. Re:as the owner of a first gen intel mac.... by Vancorps · · Score: 1

      I didn't know Windows users sold their old hardware more than Mac users. Last I checked when it was time for a new computer the old one gets moved to the playroom for the kids or becomes a media center PC or in my case became the common computer for my roommates. It's an Athlon 650 running XP perfectly well. It's 8 years now.

      No, there are many differences between OS X and Windows users but this is not one of them.

    25. Re:as the owner of a first gen intel mac.... by Short+Circuit · · Score: 1

      Yup. For even when major Linux distros stop paying to IA32, you'll still have NetBSD on your side.

    26. Re:as the owner of a first gen intel mac.... by Anonymous Coward · · Score: 0

      Why would this upset mac fanboys? will they no longer be able to give steve his blow jobs?

    27. Re:as the owner of a first gen intel mac.... by AKAImBatman · · Score: 1
      Sorry 'bout that. I would have thought that "Make viewable by everyone" meant it was viewable to everyone. Remind me to send Google a bug report on that. :-/

      Here's the graph:
      http://img340.imageshack.us/img340/4554/windowsmem oryrequiremengt0.png

      Here's the data it's pulling:

      Windows 3.1 2
      Windows 95 4
      Windows 98 16
      Windows NT 16
      Windows 2000 32
      Windows ME 64
      Windows XP 128
      Windows Vista 1024
      (Memory is in MB.)
    28. Re:as the owner of a first gen intel mac.... by Dilaudid · · Score: 1

      Why single out Mac users Stupid isn't it. Another take is that Windows 98 users, who still outnumber Mac users, will find their upgrade path involves buying a new PC.

      Furthermore - who cares? Is anyone installing Vista? The only reason that I thought people used it was because it came on their PC. The one thing that does seem relevant to this is the waste of electricity caused by Windows' constant need for more processing power. Can anyone explain why a desktop user actually needs (or even wants) 64 bits? Just in case you need to model an atomic bomb exploding or something?
    29. Re:as the owner of a first gen intel mac.... by yoyhed · · Score: 1

      You can't mix recommended and required amounts of RAM to make Vista look worse. Vista only requires 512MB. And if you're saying these are recommended amounts, I don't know what you do on your Windows machines... sit there idling, staring at the desktop?

      --
      WHO NEEDS SHIFT WHEN YOU HAVE CAPSLOCK/ DAMN1
    30. Re:as the owner of a first gen intel mac.... by cayenne8 · · Score: 1
      Cool graph, thanks for the link.

      Nice chatting with ya....

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    31. Re:as the owner of a first gen intel mac.... by RhadamanthosIsChaos · · Score: 1

      Same chart, only done by release date of the OS: http://spreadsheets.google.com/ccc?key=pZSZFa8zxX5 sJGtZLU3QSHA Appears to not disprove the Parent's point - the memory requirements increased significantly.

      --
      +++OUT OF CHEESE ERROR+++ REDO FROM START +++
    32. Re:as the owner of a first gen intel mac.... by twistedcubic · · Score: 1

      No. You only have two data points, so with the right stretching factor, you can fit almost any flavor of graph to it. Might as well call it logarithmic or doubly exponential.

    33. Re:as the owner of a first gen intel mac.... by anaesthetica · · Score: 1

      Probably in an effort to make the PowerPC-Intel transition as painless as possible. Rosetta eased things, and recompiling for Intel was made less painful through XCode. I'm sure they wanted to keep enough continuity that they didn't alienate their base of developers any more than they had to with a major architecture switch.

    34. Re:as the owner of a first gen intel mac.... by edwdig · · Score: 1

      There was active 68k code in the classic MacOS right up to the end. The end was over 10 years after they produced the final 68k Mac. That doesn't mean the system would run on 68k, but it does mean that Apple isn't afraid to support legacy code.

      If you run in x86 chip in 64 bit mode, you still retain the ability to run 32 bit code. Your kernel has to be fully 64 bit, but it's a very minor issue to keep some things as 32 bit. They could very easily make an OS that requires a 64 bit CPU but yet have the majority of the code be 32 bit.

      Mac Minis still shipping with 32 bit CPUs is the biggest reason for them to keep 32 bit alive.

    35. Re:as the owner of a first gen intel mac.... by AKAImBatman · · Score: 1

      According to the source I listed, 1GB is required for Aero-enabled editions. This is in line with Microsoft's own requirements:

      http://www.microsoft.com/windows/products/windowsv ista/editions/systemrequirements.mspx

      The minimums are lower in many cases, but I chose the recommended where more memory was required for standard features. (e.g. ME requires only 32 MB, but 64 MB is required if you want to run Windows Media Player.) I considered separating out different configurations, but I decided that it would simply obscure the point.

    36. Re:as the owner of a first gen intel mac.... by robgig1088 · · Score: 1

      But remember: at one time, nobody thought you would need more than 64KB of ram.

    37. Re:as the owner of a first gen intel mac.... by GlobalEcho · · Score: 3, Informative

      I believe semilog is more informative (as we discussed). One can see it in this sheet

    38. Re:as the owner of a first gen intel mac.... by yoyhed · · Score: 1

      Look again at that page, scroll down to the bottom. All editions, minimum is 512.

      --
      WHO NEEDS SHIFT WHEN YOU HAVE CAPSLOCK/ DAMN1
    39. Re:as the owner of a first gen intel mac.... by dgatwood · · Score: 1

      The kernel does not have to be 64-bit. Mac OS X (Tiger) supports 64-bit command-line executables on Intel today using a 32-bit kernel just like it does on G5s.

      The only good excuse I can think of for moving to a 64-bit kernel is ever-bloating graphics card memory. Four one gig cards can't be mapped into the kernel's address space. Realistically, things start failing when you have more than about 2-2.5 gigs of VRAM, if memory serves. I guess there are a few other (fairly esoteric) technologies that could also benefit---Infiniband and friends, for example---but graphics cards are the only one that is in common use.

      Even with graphics cards, though, a user-space graphics driver model could largely (if not completely) solve that problem. Using a 64-bit kernel mainly just adds memory pressure for no good reason. Graphics drivers and a few other very specialized drivers notwithstanding, the kernel has no reason to need to address more than a couple of gigs of RAM directly, and likely will not need to do so (again drivers notwithstanding) for a very long time. Do you really need an eight gigabyte buffer cache? Do you really need four gigabytes of mbuf clusters? Doubtful.... Maybe someday, but not any time soon.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    40. Re:as the owner of a first gen intel mac.... by ceoyoyo · · Score: 1

      Shh. We're talking about Windows. I get to make up whatever I want.

    41. Re:as the owner of a first gen intel mac.... by Frostalicious · · Score: 1

      As noted in your spreadsheet chat, memory requirement change per year is not expected to be linear. If you take the log of your data, put year on the X axis, then the change per year appears consistent. It is not clear to me that Vista memory requirements are out of line with historical trends.

    42. Re:as the owner of a first gen intel mac.... by AKAImBatman · · Score: 1

      The 512 MB minimum is with Aero auto-disabled.

    43. Re:as the owner of a first gen intel mac.... by Anonymous Coward · · Score: 0

      The chart's plain wrong though.

      4Mb the minimum for Windows 95? 16Mb the minimum for Windows 98? Only if you want the slowest experience possible. I never got comfortable with 95 till I had 32Mb RAM, and it took 128Mb RAM to truly have Windows 98 in the comfort zone.

      Vista will run with less than 1Gb, which you said was Vista's minimum - it's being sold on machines with 512Mb RAM. If you absolutely disabled everything you could probably squeeze it into 256Mb RAM - which would probably give terrible performance on par with Windows 98 on a 16Mb machine...

      Windows Vista runs flawlessly with 2Gb RAM - twice *your* recommended minimum. The same can't be said with 95, 98 or XP with twice their recommended minimums - 98 would still be slow with 32Mb RAM.

    44. Re:as the owner of a first gen intel mac.... by edwdig · · Score: 1

      Perhaps PowerPC has some extra features to enable it, but on x84-64, you're not getting 64 bit anything unless the kernel is running in 64 bit mode.

      As for the kernel not needing to access more than a couple gigs directly - how do you propose handling memory management past the 4 GB mark? Do you propose only allowing virtual memory (including memory mapped files) on the first 4 GB ?

    45. Re:as the owner of a first gen intel mac.... by timeOday · · Score: 1
      The exponent on system memory requirements and growth has fallen tremendously over the last few years and is not likely to rebound.

      Using the wayback machine for pricewatch, I discovered the following: In 2002, 1GB of PC133 RAM would set you back $144. In 2007, for the same price you can get 1 GB ddr2-1066 1gb or 2GB DDR2-400. The cheapest 1GB module now is PC100 for $60. So in 4 years, RAM has only doubled in capacity for the same price. That's a joke compared to the 80s and 90s, when memory capacity doubled every 18 months or so and just kept getting cheaper.

    46. Re:as the owner of a first gen intel mac.... by marcosdumay · · Score: 1

      By year it is a near well behaved exponential. The problem with the first graph is that vista took a long time to be released.

    47. Re:as the owner of a first gen intel mac.... by AKAImBatman · · Score: 2, Interesting

      They're not *my* recommended requirements. They're pulled from the source pages. (check the column on the right of the first sheet) Those pages appear to pull from the requirements that Microsoft published. I don't know if you remember back in the old days, but Microsoft tended to lowball their memory requirements. (Presumably to sell more copies.)

      If you've got a reliable source that gives different values for these features, please share and I'll update the sheet.

    48. Re:as the owner of a first gen intel mac.... by AKAImBatman · · Score: 1

      Sorry, "for these features" should read "for these OSes". I'm a bit distracted by the spreadsheet at the moment.

    49. Re:as the owner of a first gen intel mac.... by nine-times · · Score: 1

      I didn't know Windows users sold their old hardware more than Mac users. Last I checked when it was time for a new computer

      I think that's what he means: that for Mac users, "time for a new computer" is more of a rare occurrence. I don't have anything to cite, but I've read that there have been studies that suggest Mac users keep their computers longer-- and by "keep" that means "keep using them as their main computer".

      Even within the past year, I've seen people carrying around 500Mhz Powerbook Ti laptops and really using them. I think I could say something like that for Linux-- I know people who use Debian on old IBM Thinkpads and are happy with those machines-- but I haven't seen someone carrying around a 500 Mhz Windows laptop in the past 5 years or so.

      Admittedly, my experience is just anecdotal evidence, but I believe there have been studies that suggest the same thing. It's probably a combination of factors, including the fact that gamers usually run Windows, and gamers are the most likely group to want top-of-the-line systems.

    50. Re:as the owner of a first gen intel mac.... by SEMW · · Score: 3, Insightful

      Many other people have pointed out your mistakes-- using a line graph with a non-continuous x-axis (i.e. name of release), using a linear graph to plot something that should be expected to grow exponentially (think RAM equivalent of Moore's law; doubling every x years is exponential, not linear), etc. I've fixed most by taking your data and plotting the natural logarithm of recommended RAM against the release data:

      Google spreadsheets: http://spreadsheets.google.com/ccc?key=pLElDZW8EaP djJ0gOQ4r0MQ

      PNG (for those who can't view Google Spreadsheets): http://img511.imageshack.us/img511/6696/memoryrequ irementscb5.png

      As you can see, it's pretty much a straight line, exactly as you'd expect.

      --
      What's purple and commutes? An Abelian grape.
    51. Re:as the owner of a first gen intel mac.... by treeves · · Score: 1

      Thanks for the pic. I wanted to see it, but when I followed the link I got this:

              This web browser is not supported.

              We're sorry, but it looks like you're running a web browser that doesn't yet work with Google Docs & Spreadsheets .

              Google Docs & Spreadsheets currently supports:
                  IE 6.0+
                  Mozilla Firefox 1.0.7+ Download Firefox
                  Mozilla 1.7.12+
                  Netscape 7.2, 8.0

      And I'm running Opera 9.2. Opera is not supported by Google Apps.

      --
      ...the future crusty old bastards are already drinking the Kool-Aid.
    52. Re:as the owner of a first gen intel mac.... by AKAImBatman · · Score: 1

      It wasn't a mistake. It was a simple spreadsheet that charted out RAM requirements across the OSes. It was never intended to be a mathematical analysis of the issue. That came after 500+ viewers and one google@google.com showed up!

      The original spreadsheet didn't even map by year!

    53. Re:as the owner of a first gen intel mac.... by AKAImBatman · · Score: 1

      Oh, and I should probably mention that the second tab has a link to Global's semilog sheet. I asked him to create it after he requested that a semilog sheet be done.

    54. Re:as the owner of a first gen intel mac.... by raddan · · Score: 1

      I'm guessing that there was more of a performance benefit to having Rosetta run on dual-core 32-bit than on 64-bit. Pure speculation here, though.

    55. Re:as the owner of a first gen intel mac.... by SEMW · · Score: 1

      It was a simple spreadsheet that charted out RAM requirements across the OSes. It was never intended to be a mathematical analysis of the issue. But you were inviting conclusions about Vista's RAM usage from it; thus, implicitly treating it as if it were a reasonable analysis. Nonwithstanding that in any linear plot of explonentially increasing numbers, the most recent one is always going to far dominate the ones that came before.

      The original spreadsheet didn't even map by year! ...Well, yes, exactly; that was one of the reasons it wasn't very good.
      --
      What's purple and commutes? An Abelian grape.
    56. Re:as the owner of a first gen intel mac.... by porneL · · Score: 1

      Why did Apple start with core duo processors? They could have made a clean break to 64bit x86 hardware, instead of going 32bit and having to migrate later?
      Because when Mac OS X was ported to x86, x86-64 didn't exist yet (Jobs admitted that they had x86 builds since the beginning of Mac OS X).
    57. Re:as the owner of a first gen intel mac.... by uhlume · · Score: 1

      The problem is, you're only looking at capacity, not memory speed. As 32-bit CPUs over the last decade have gotten faster and faster without increasing their address space, the pressure to increase memory speed has been substantially greater than to increase capacity. This will probably shift again as 64-bit chips and operating systems become more prevalent.

      --
      SIERRA TANGO FOXTROT UNIFORM
    58. Re:as the owner of a first gen intel mac.... by spiderbitendeath · · Score: 1

      My main Mac is a iBook G3 Clamshell. 300mhz overclocked to 400mhz. It runs great.

      --
      Sometimes when I'm working on projects things disappear, I suspect gremlins.
    59. Re:as the owner of a first gen intel mac.... by AKAImBatman · · Score: 2, Informative

      But you were inviting conclusions about Vista's RAM usage from it; thus, implicitly treating it as if it were a reasonable analysis.

      "Since I've been itching to try out the new Charts feature on Google Spreadsheets anyway, I threw together a spreadsheet of the Windows memory requirements," hardly sounds like a reasonable analysis. Especially after the parent poster explicitly stated that such growth is not linear. It was information, and information only. i.e. A spreadsheet of Windows Memory Requirements. Exactly as stated.

      Nonwithstanding that in any linear plot of explonentially increasing numbers, the most recent one is always going to far dominate the ones that came before.

      I think that's obvious. However, the memory requirements did double with each generation. (The exception was 95 -> 98 which had a 4x increase.) The 8x increase with Vista is a bit of a first for Windows. Which is a true statement regardless of the time between the OSes. However, that doesn't mean it's an analysis. That's your invention, not mine.
    60. Re:as the owner of a first gen intel mac.... by yoyhed · · Score: 1

      Noted, but my point is that Vista will run VERY comfortably on that 1GB. However, 2000 runs like absolute shit (if at all) on the 32MB you listed, same with XP on 128. More comparable figures to the 1GB for Vista are 128-256 for 2000 and 256-384 for XP.

      --
      WHO NEEDS SHIFT WHEN YOU HAVE CAPSLOCK/ DAMN1
    61. Re:as the owner of a first gen intel mac.... by AKAImBatman · · Score: 1

      No, the point is that those are (AFAIK) Microsoft's figures. Whether they're spectacularly off-base or not is beside the point.

    62. Re:as the owner of a first gen intel mac.... by Anonymous Coward · · Score: 0

      I have to admit I was disappointed and surprised that I cannot view your spreadsheet, apparently, without registering. I can guarantee that will stop me from ever using Google Spreadsheets, myself, if I cannot even share.

    63. Re:as the owner of a first gen intel mac.... by Lee+Cremeans · · Score: 1

      I actually bought a PowerBook G3 (Bronze Keyboard/Lombard) off eBay about a year ago and fixed it up with more memory and a G4 upgrade because I wanted a PowerPC notebook for cheap. It's been surprisingly useful for such an old machine, though I do have some issues with it (no 3D acceleration and the upgrade card drivers crash the machine on resume sometimes). That said, it runs 10.4.9 quite well. Oh, and it's black. :D

    64. Re:as the owner of a first gen intel mac.... by brantondaveperson · · Score: 1
      It's not beside the point if we're talking about how much memory is required by operating systems as they have evolved over the years


      If we're complaining about how MS report the minimum memory for their OSs then fine. But I didn't think we were.

      And chatting in a spreadsheet is so awesome I don't even know where to begin..

    65. Re:as the owner of a first gen intel mac.... by Overly+Critical+Guy · · Score: 1

      Actually, OS X Leopard runs a 32-bit kernel with a 64-bit userspace. That's how it can get away with running 32-bit and 64-bit binaries and drivers natively.

      As for this 64-bit push from Microsoft (assuming it ever comes true given their past promises regarding Vista features that were dropped), it's amusing how non-smoothly their 64-bit transition has gone. Nobody runs 64-bit Windows because barely anything works. Do they simply lack the engineering talent to be able to comfortably run 32-bit drivers or allow developers to ship fat binaries ala Mac OS X so that you're not having to deal with multiple executables? Ah, well, at least the next version of Windows may finally get away from the 25+ year old BIOS and support EFI. Maybe. When Microsoft gets around to it.

      After the flop that is Vista, Microsoft has left a bitter taste in a lot of people's mouths. Not just you guys who always disliked them, but the tech press and even regular folks. I don't trust anything they say or do, especially any promises regarding the next version of Windows ("This time, we'll get it right!). Same old Win32, same old bullshit.

      --
      "Sufferin' succotash."
    66. Re:as the owner of a first gen intel mac.... by Wolfrider · · Score: 1

      --Win2kpro runs acceptably @ 96MB RAM with a little optimization.

      --XP runs acceptably @ ~164MB RAM with a little optimization.

      --Even in a Vmware VM. ;-)

      --
      .
      == WolfriderV6 == I'm willing to admit that *I just might* be wrong... Are you??
    67. Re:as the owner of a first gen intel mac.... by rustalot42684 · · Score: 1

      It's a bit off, because it was only released in 2004, but I have Windows vs Ubuntu here. It's the same data as above, but I got info from Ubuntu release notes also.
      I used only Ubuntu because a) I am lazy (just kidding) b) IMO, it's the distro most oriented towards your mom {i.e. the average user} and therefore a good alternative. Please, don't get into any flamewars.

      Windows vs. Ubuntu

    68. Re:as the owner of a first gen intel mac.... by Vancorps · · Score: 1

      I have heard this too, much like the BMW owner who switches cars more often because he can versus the Toyota owner who is usually more sensible so they keep their vehicles longer. Both cars are quite capable of lasting for very long times but different people buy them. I think that has more to do with it. You touched on that fact a little bit with gamers, they are just one group who are known for their impracticality.

      At the same time there are those of us who are practical that run Windows and buy BMWs. The 650mhz machine is the main machine for the house and will be for the foreseeable future. I took my old machine and made it a media server so storage limitations of the 650mhz box is not a problem. It's more than sufficient for video playback and anything else they've wanted to do thus far. I'm a power user, whether I had a Mac or PC I'd be using something newer anyways. I've seen those 500mhz Ti laptops and they run OS X very slowly despite the two people that responded to your post. Yes it runs, I'll even admit it runs better than I expect assuming the thing has enough ram which is usually the problem with older machines both Mac and PC.

      A 500mhz machine with loads of ram is quite capable of running XP and keep in mind that at the time with the G3, Apple was advertising that it was as fast as a PC processor with twice the clock. That means Windows XP is far less intensive if you believe the advertising. Of course I think we can probably agree its about even. It wasn't until the GHZ mark was reached on the PC side that Apple started getting decimated in performance which took years to recover from even with the G5 breaking about even.

    69. Re:as the owner of a first gen intel mac.... by ShadowBlasko · · Score: 1

      Perhaps I am a bit odd. (Ok, that is a given) but I generally will find a use for older hardware, or donate it.

      I have not been in any great hurry to retire my windows machines. Our "on the road" machine for shows is a 7 year old HP laptop, 700Mhz, *maxed* at 256MB of RAM, and it runs XP Pro just fine. The only time it stumbles is when I hit something java-based.

      Hell, my first (and last) store bought machine is a Sony Vaio PV120, (200Mhx Pentium) that is *still* being used. Maxed out at 128MB of RAM, running Win Me. Granted, it's just a print server/Honeypot machine, but it still runs just fine, and gets used pretty often for friends who come over and "Just wanna check their e-mail".

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order- Ed Howdershelt Via Tass
    70. Re:as the owner of a first gen intel mac.... by dgatwood · · Score: 2, Interesting

      Go get yourself a Mac with a Core 2 Duo processor and see for yourself.

      It is not necessary for the kernel to be 64-bit to support 64-bit executables in user space. It is only necessary for the kernel to know how to manage an MMU that supports 64-bit addressing and for the kernel to maintain all unmapped user-space addresses as 64-bit values. Once mapped into the kernel, the kernel-space representation can safely be a 32-bit value without limiting anything other than the maximum aperture within a 64-bit app that the kernel can directly examine/modify at any one time.

      No special hardware is necessary to do this. The Mac OS X kernel does not use any 64-bit instructions; the same kernel is used for both 64-bit-capable Core 2 Duo CPUs and 32-bit-only Core Duo CPUs. It probably has a few lines of special-cased assembly language at the system call interface layer and the pmap layer (where memory mappings are stored into the MMU) to access the upper halves of registers, so for a dozen instructions per system call, it might be running in 64-bit mode (on x86---on PowerPC, it doesn't even do that, AFAIK), but the kernel as a whole does not run in 64-bit mode.

      If you think back to your Operating Systems class, you'll recall that memory management never really uses pointers. At worst, it uses things that look like pointers but aren't really used as such. Ideally, though, a well-written memory management subsystem just uses integers (or equivalent opaque types). Pointers in a user-space application have no meaning in the kernel. Those user-space addresses generally point to entirely different physical addresses in the kernel unless you get really lucky. Thus as far as the kernel is concerned, they are just numbers. It really doesn't matter whether those numbers are 32 bits in length or 64 bits. As far as the kernel is concerned, it's just a uint64_t or equivalent, which allows for 64-bit numerical computation even on 32-bit CPUs. As long as the kernel doesn't do something careless and truncate it to a 32-bit value, the kernel doesn't care about how long the value is.

      Similarly, physical addresses in RAM are meaningless to the kernel. They are just numbers. As long as the kernel is careful not to truncate those numbers to 32-bit values, it doesn't matter how long they are. The only thing that needs to understand the longer value is the MMU, and of course, it does. All the kernel cares about is that the page 0x000423847362739a maps onto address 0x00341ac0 in the 32-bit kernel address space and also maps onto address 0x000001c538273847 in a user-space process with a 64-bit address space. Those are just numbers that get plugged into the MMU, and it does all the work.

      I could probably implement a kernel that supports 64-bit user space processes with an 8-bit kernel address space if any 64-bit CPU still supported 8-bit addressing. The biggest problem would be finding room in an 8-bit address space to map the page table for a 64-bit process; it might be kind of tight. In theory, though, you could do it. The point is that for 64-bit executable support, the only real requirement is the ability to perform 64-bit math, which can be (and is) easily emulated using a small number of 32-bit math instructions.

      There are exceptions to this, of course. The Linux kernel, for example, historically divided a 4GB address space between user-space apps and the kernel and ensures that the two address spaces do not overlap. There are performance advantages to doing that because you can leave mappings in place during boundary crossing. However, such an layout won't allow 64-bit processes on a 32-bit kernel unless you do some really weird lower-4GB bounce buffer tricks on every system call (at a huge performance loss). It's a feature vs. performance tradeoff, really. I think that Linux has pretty much stopped doing that at this point, but I'm not certain.

      Mac OS X does not do a split address space. The kernel has a full 4GB address spa

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    71. Re:as the owner of a first gen intel mac.... by JohnnyGTO · · Score: 1

      Modded down by a Windows flack.

      --
      Si vis pacem, para bellum! For evil to succeed good men need only do nothing!
    72. Re:as the owner of a first gen intel mac.... by Anonymous Coward · · Score: 0

      No... that was just Bill Gates. Quite the visionary, no?

    73. Re:as the owner of a first gen intel mac.... by toddestan · · Score: 1

      VM's with low memory always run faster than a physical machine with the same amount of memory. The reason is that the host OS will use its disk cache to cache the VM's disk image, hence the VM hitting the swap isn't nearly as slow as a physical harddrive would be. With that said, XP isn't too bad with 128MB so long as you don't actually try to do anything with it.

    74. Re:as the owner of a first gen intel mac.... by amilham · · Score: 1

      The quote people tend to attribute to Gates actually says "640k" is all anybody will need. Gates, however, denies that he ever said that, and there's no proof anywhere that he did.

    75. Re:as the owner of a first gen intel mac.... by toddestan · · Score: 1

      Actually, it's more of a cost thing. If you're replacement computer is going to cost you more money, you're more likely to put off replacing it. Meanwhile, on the PC side of things, why keep dicking around with that P2 when a brand new machine is going to run you $300-$400? Even if you don't want to spend the money, the fact that other people will benefits you indirectly. Just the other day, I retrieved a 866Mhz P3 system with 512MB of ram, a 40GB harddrive, and CD burner from the trash (equilivent Mac: $150-$250 on eBay). With stuff like that free for the taking, why dick around with anything less?

    76. Re:as the owner of a first gen intel mac.... by Anonymous Coward · · Score: 0

      A 500mhz machine with loads of ram is quite capable of running XP and keep in mind that at the time with the G3, Apple was advertising that it was as fast as a PC processor with twice the clock
      XP came out at the end of 2001. By that time, Apple had moved everything but the iBook to the G4.
    77. Re:as the owner of a first gen intel mac.... by edwdig · · Score: 1

      It is not necessary for the kernel to be 64-bit to support 64-bit executables in user space. It is only necessary for the kernel to know how to manage an MMU that supports 64-bit addressing and for the kernel to maintain all unmapped user-space addresses as 64-bit values. Once mapped into the kernel, the kernel-space representation can safely be a 32-bit value without limiting anything other than the maximum aperture within a 64-bit app that the kernel can directly examine/modify at any one time.

      That's fine and dandy in theory, but it doesn't match the x86-64 design. I've got the AMD manuals in front of me now. Read Volume 2 Chapter 1. It says very clearly that the kernel MUST be running as 64 bit code for ANY process to have access to 64 bit functionality. If the kernel isn't running as 64 bit code, it doesn't have access to the control registers and instructions necessary to set up the 64 bit memory management.

      Don't forget, if you enable 64 bit mode, the CPU requires exception and interrupt and handlers to be 64 bit code.

      See Common 64-bit Myths if you'd like further confirmation.

      You should try reading it yourself. It says PowerPC was designed for mixing 32 bit and 64 bit code in the way you're speaking. x86 wasn't. It was designed to mix 16 and 32 bit code in the way you're speaking of though. When you jump to 64 bit mode, it's a clean break.

  2. let's hope by compro01 · · Score: 1

    let's hope that they can get the driver situation figured out by then.

    --
    upon the advice of my lawyer, i have no sig at this time
    1. Re:let's hope by brunascle · · Score: 1

      exactly why i think this is a good idea. not enough pressure is being put on vendors to produce stable 64-bit drivers. this damn well better speed up the process.

    2. Re:let's hope by KlomDark · · Score: 1

      No doubt!

      Have a Belkin USB wireless adapter. They don't offer a 64 bit driver. But RALink, the company that makes the chips in the thing, DO offer a 64-bit driver. But Belkin won't tell you that.

      And 64-bit Flash (Not that I really want such a thing), why is that taking so long? Sick of the 'blip' noise with every page I hit with 64-bit IE wanting me to install flash to see some lame ad. And you click on it and "There's no 64-bit Flash, but you can run Flash on a 32-browser running on your 64-bit OS" And Why The Fuck would I want to do that?

    3. Re:let's hope by shaitand · · Score: 1

      At the rate Microsoft is going they won't have that 64bit only OS out for a decade. I doubt this will speed up anything.

    4. Re:let's hope by Ryan+Amos · · Score: 1, Funny

      And 64-bit Flash (Not that I really want such a thing), why is that taking so long? Sick of the 'blip' noise with every page I hit with 64-bit IE wanting me to install flash to see some lame ad. And you click on it and "There's no 64-bit Flash, but you can run Flash on a 32-browser running on your 64-bit OS" And Why The Fuck would I want to do that?

      I believe we call that a "feature."

    5. Re:let's hope by PatriceVignon · · Score: 1

      And 64-bit Flash (Not that I really want such a thing), why is that taking so long? Sick of the 'blip' noise with every page I hit with 64-bit IE wanting me to install flash to see some lame ad. And you click on it and "There's no 64-bit Flash, but you can run Flash on a 32-browser running on your 64-bit OS" And Why The Fuck would I want to do that? No Flash on any webpages if I run 64-bit browsers? Where do I sign up?
    6. Re:let's hope by sabre86 · · Score: 1

      https://shipit.ubuntu.com/

      Then select the 64 bit version.

      Hope you don't watch Youtube, though.

  3. New operating system by Mantaman · · Score: 5, Funny

    Does this mean that MS are going to inflict another operating system on us in the near future?

    1. Re:New operating system by timelorde · · Score: 5, Funny


      Depends on what your definition of "near" is...

    2. Re:New operating system by An+ominous+Cow+art · · Score: 5, Funny

      Also depends on what your definition of "new" is...

    3. Re:New operating system by Mercano · · Score: 4, Funny

      Also depends on what your definition of "operating system" is...

      --
      #include <signature.h>
    4. Re:New operating system by mypalmike · · Score: 4, Funny

      Most importantly, it depends on what your definition of "operating" is.

      --
      There are 0x40000000 types of people: those who understand 32-bit IEEE 754 floating point, and those who don't.
    5. Re:New operating system by Anonymous Coward · · Score: 3, Funny

      Also depends on what your definition of "us" is...

    6. Re:New operating system by Anonymous Coward · · Score: 1, Funny

      Also depends on your what your definition of "is" is.

    7. Re:New operating system by wiredlogic · · Score: 1

      What is this "inflict" you speak of?

      --
      I am becoming gerund, destroyer of verbs.
    8. Re:New operating system by Dachannien · · Score: 3, Funny

      In some very minor way, it also depends on what your definition of "?" is.

    9. Re:New operating system by ROMRIX · · Score: 3, Funny

      I think we can all agree on the definition of "inflict" in this case.

    10. Re:New operating system by Gilmoure · · Score: 1

      Does it involve bending over?

      --
      I drank what? -- Socrates
    11. Re:New operating system by SpaceLifeForm · · Score: 1

      It's clear the MS is mean.

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
    12. Re:New operating system by PHPfanboy · · Score: 4, Funny

      .... so we have no disagreement that it will be inflicted

      --
      29 mpg. YMMV.
    13. Re:New operating system by tumbleweedsi · · Score: 1

      Also depends on your definition of "us".

      --
      Be nice, sponsor me: http://jailbreak.ragabonds.org.uk
    14. Re:New operating system by bean123456789 · · Score: 1

      ...and for the kill... Depends on what your definition of "is" is

    15. Re:New operating system by complete+loony · · Score: 1

      That depends on your definition of "us".

      --
      09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
    16. Re:New operating system by Anonymous Coward · · Score: 0

      Seems the scores on those comments depend on what your definition of "funny" is...

    17. Re:New operating system by Anonymous Coward · · Score: 0

      Also there appears to be no disagreement over the term "future", or as some would add... "lack of"

  4. So this means by zappepcs · · Score: 1

    that we'll see 32 bit computing for another 20 years? Seriously, it took them how long to bring Vista to the market? Something tells me that its going to take a lot longer for MS to move beyond that to the next version of Windows. There doesn't seem to be a lot of uptake on Vista. It might take 3 more years to get to SP2, never mind beyond Vista.

    1. Re:So this means by bagboy · · Score: 1

      >> beyond Vista

      This has potential for being a great marketing phrase for the Next-Gen Windows..... "Beyond Vista - Expand your horizons and imagine the possibilities..."

    2. Re:So this means by ChetOS.net · · Score: 2, Informative

      Windows XP came out in October 2001. Vista in November 2006. That is little over 5 years, not 20.

      However, I understand your sentiment.

      --
      "If God had intended us to walk he would not have invented roller skates." -- Willy Wonka
    3. Re:So this means by zappepcs · · Score: 1

      (start sarcasm) Yeah, I can see it now, after a fresh install your desktop is full of shortcuts to malware and worm installation scripts so that you can choose how you want to be p0wned (end sarcasm)

    4. Re:So this means by hesiod · · Score: 1

      > (end sarcasm)

      Psh... I don't forsee the sarcasm about Vista ending any time soon.

    5. Re:So this means by Anonymous Coward · · Score: 0

      Looks like we'll need an updated definition:

      "Microsoft Windows....a 32 bit operating system, patched on a 16-bit shell, of an 8-bit disk operating system, written on a 4-bit computer for a 2 bit company that doesn't like competition 1 bit."

      (Googled for above sentence)...

  5. As though any processor by Spamalope · · Score: 5, Insightful

    made today will be able to run the Microsoft replacement for Vista. Why worry?

    1. Re:As though any processor by aichpvee · · Score: 2, Funny

      Exactly! At the rate they're going the next windows should hit retail sometime around 2017.

      --
      The Farewell Tour II
    2. Re:As though any processor by iainl · · Score: 5, Insightful

      2017 might be comedy exaggeration. But

      1) Who bought a 32-bit processor for Christmas?

      2) Who bought something capable of running Vista in 2001 when XP launched?

      --
      "I Know You Are But What Am I?"
    3. Re:As though any processor by level_headed_midwest · · Score: 1

      There are still many notebooks being shipped with 32-bit Core Duo and Celeron M processors even today, and not just in low-end machines. It will be some time and probably a new CPU/chipset (past the Santa Rosa refresh, that is) generation to push the Core Duos out. Penryn and the 30-series chipsets ought to force a refresh of most notebooks that Santa Rosa/G965 and the Core 2 Duo didn't catch, and those are supposed to come out late 2007. Windows "Vienna" is supposed to ship in about 3 years, so it's entirely plausible that somebody would try to put a new OS on a machine that's a little over 2 years old instead of buying new. This will not be an issue for desktops as most new desktops were 64-bit starting in 2004, with the last 32-bit desktop Semprons and Northwood Celerons bowing out around the end of 2005.The last 32-bit desktops would be roughly 5-6 years old when "Vienna" ships, so they'll be candidates for replacement rather than upgrade.

      A computer bought in 2001 could probably run Vista, especially if somebody was willing to drop some more now-much-cheaper RAM (if it's not RDRAM :D ) and a low-end AGP Direct3D 9-capable video card in there. My folks got a 1.8 GHz P4 Willamette in late 2001 and it has an ancient NV TNT2 AGP GPU, a 120 GB HDD, and 512 MB DDR-266, upgradeable to 2 GB. Replacing the old AGP card with something like an ATi x1300 in AGP and putting the full 2 GB RAM in the machine would enable it to run Vista. Would it be fast? Not really as the P4 Willy isn't all that fast even with XP. But it will certainly run Vista if somebody put $150 into it.

      --
      Just "gittin-r-done," day after day.
    4. Re:As though any processor by vasqzr · · Score: 1


      And take about 4GB of RAM.

    5. Re:As though any processor by Alien54 · · Score: 2, Funny

      you forget, it's a 64 bit processor, so the sweet spot will be 16gig of ram to run your windows checkbook program

      --
      "It is a greater offense to steal men's labor, than their clothes"
    6. Re:As though any processor by aichpvee · · Score: 1

      I think you're confusing your checkbook with your notepad...

      --
      The Farewell Tour II
    7. Re:As though any processor by InsaneProcessor · · Score: 1

      Since M$ is the king of "Nothing new invented here", XP is the last OS you will ever need in your lifetime.

      --

      Athiesm is a religion like not collecting stamps is a hobby.
    8. Re:As though any processor by Jozer99 · · Score: 2, Informative

      Quite a few people. I know someone who celebrated the XP launch by buying a new computer, 1.6 GHz P4 Geforce 4 Graphics 512MB of RAM 80GB HD DVD and CD-RW That runs Vista just fine, as you can see, and was actually not that expensive back in the latter half of 2001 (probably around the $1500 mark).

    9. Re:As though any processor by Anonymous Coward · · Score: 0

      And what about IPv6 and DX10 and new hardware without old OS support and when XP updates are no longer available and installing on machines and then having to find the drivers for XP that Vista would have included and etc and etc... This is just my OPONION i'm not gonna tell everybody to think like me, but that was a pretty short-sighted comment.

    10. Re:As though any processor by rapidweather · · Score: 1
      Might be a long time before the Microsoft replacement for Vista appears for end users, but I bet they will go through a long beta testing time, just like they did with Vista.
      Although it is true that 64 bit is "better" than 32 bit, we all worry (I do) about obsolete machines, still good, and obsolete linux operating systems. My Knoppix remaster is 32 bit, based on Knoppix 3.4. I could get ahold of the latest 64 bit knoppix, and start putting all of my stuff in there, and have it done. That won't be easy, and I cringe when I see the 64 bit AMD machines in the stores, at a good price, too. What if they took over, and ruled the World? Would I wind up staying up late at night, for eons, trying to get my stuff migrated to 64 bit? Would I wind up having two remasters, one 32 bit for all of the old 32 bit machines out there, and one for the 64 bit machines.
      I would hope that Microsoft is just planning some "out there, pie in the sky stuff" just to please the stockholders, by going with all 64 bit. You know that Toyota announced that in about 12-14 years, all of their cars would be equipped with hybrid power plants, at the same cost as a car with only a gasoline engine. No difference in price. The big difference is that Toyota is tops, and they know where they need to go to stay on top, whereas Microsoft always has us linux folks after them. It just works out that way, we are not "after them" as much as we are putting together OS's that do what we want, exactly, in a secure on-line environment. Using my remaster every day, I cannot image using something like Windows 98, or XP for that matter. I don't want be become part of somebody's botnet, or have my keystrokes logged when I do online banking. I have the Guarddog firewall, on by default, no user action needed. Any other livecd linux do that? If I go to Gibson Research Corporation, and run the Shields UP tests, I always get "Your system has achieved a perfect "TruStealth" rating. Not a single packet, etc." report.
      As a round about way of checking for botnet infection, since I use IceWM as my default WM, I have the nice little processor activity window, and the broadband activity window right down there on the toolbar where I can see them. I don't have anything like that, nearly as handy, in my Fedora Core 6 installation on this same box, dual boot. Kinda makes me nervous not to have those items there in FC 6. Any botnet setup would really show up as stolen bandwidth, and processor activity. Not that my livecd linux could be infected by a virus, but anything is possible.
      So, it's not like Microsoft is going to suddenly make us all have 64 bit machines, but eventually, that would be the case. Otherwise, Knoppix would not offer a 64 bit version, if they did not see the benefits.
      As long as there is a Microsoft, always wanting more powerful hardware for each new version, we will have to come up with Linux OS's that use those machines.
      I have an Inspiron 1505 being built by Dell, due here the middle of June, and I can't wait to run my remaster on it, if possible before even booting up Vista. Lets see, Dual Core, 2 GB RAM, ATI 256 MB card, lots of Microsoft-inspired power to be had.

      If there were no Microsoft, would anything like the Inspiron 1505 be available at that price?

      Rapidweather

    11. Re:As though any processor by level_headed_midwest · · Score: 2, Insightful

      XP has support for IPv6 already. Direct3D 10 supposedly can be grafted into XP- it's only a question of whether the driver will need to be hacked to do so or not. New hardware can prove to be a thorny issue as 64-bit Vista and Vienna drivers cannot load into a 32-bit XP kernel.

      --
      Just "gittin-r-done," day after day.
    12. Re:As though any processor by InvalidError · · Score: 2, Informative

      This will not be an issue for desktops as most new desktops were 64-bit starting in 2004, with the last 32-bit desktop Semprons and Northwood Celerons bowing out around the end of 2005. The only mass-market 64bits desktop chip available in 2004 was the Athlon64... 64bits Prescott/Pentium D did not become widely available until early 2005. Pentium D 5x0 Prescotts that shipped in 2004 do not have EM64T but all other models (5x1, 5x2, 6xx, 8xx, 9xx) that started shipping in 2005 do.

      Your first sentence becomes true about half-way through 2005 where even 32bits Celerons started being phased out and Northwood supplies completely dried up.

      I remember building my current PC after a few weeks of pondering whether I preferred NW's lower power, the upcoming Prescott's 64bits or dual-dice 8xx. In the end, I opted for the 3.0GHz NW while it was still available at Prescott-like prices in September. Since I upgraded that computer from 1GB RAM to 3GB RAM last year, I plan to tough it out until I can get 2x2GB of reasonably priced DDR3 at some point through 2008 - assuming I will not be more interested in getting a new laptop by then.
    13. Re:As though any processor by iamhassi · · Score: 1

      "There are still many notebooks being shipped with 32-bit Core Duo and Celeron M processors even today, and not just in low-end machines."

      So? Honestly would you want to use the computer you're using now to run whatever bloatware M$ thinks up 3-5 years from now?

      Who out there buys their computer and thinks "gee I sure hope I can run the new OS coming out in a few years!"

      Besides, who cares if it'll run the next OS? I don't run Vista now after all the horrible crap I've heard about it on /. and my system is more than capable with a 1.8ghz clocked at 3ghz core 2 duo with 2gb ram and 1 tera hd. I won't need vista for awhile (if ever) and might not even run the next OS, just depends on what the market's like by then.

      --
      my karma will be here long after I'm gone
    14. Re:As though any processor by Alien54 · · Score: 1

      point being that it would be pitiful if a checkbook program would need 16 gigs of ram to load. What are you doing, simulating a hand-written register for Mr Scrooge?

      --
      "It is a greater offense to steal men's labor, than their clothes"
    15. Re:As though any processor by daskinil · · Score: 1

      I have a 1 year old laptop with integrated Intel graphics, with 34mb of video ram. According to Nvidia Vista ready test, this computer is not able to run vista. However i've been running vista WITH aero for 6 months now without a hitch, it evens seams faster than XP. But maybe thats just cause it looks ALOT nicer.

    16. Re:As though any processor by StikyPad · · Score: 1

      The Geforce 4 wasn't introduced until April 2002.

    17. Re:As though any processor by richlv · · Score: 1

      Who out there buys their computer and thinks "gee I sure hope I can run the new OS coming out in a few years!"

      i do. and now 9 years old computer is running latest slackware quite fine, thank you.
      though f*&%# you, nvidia, for fixing a problem in your drivers latest version that doesn't support my video adapter anymore ;> (for the record, video adapter was upgraded some 3 or 4 years ago from ati to nvidia, as nvidia still had better drivers than ati for linux).
      --
      Rich
    18. Re:As though any processor by Jozer99 · · Score: 1

      I guess it was a geForce3, then, wasn't it?

    19. Re:As though any processor by jonadab · · Score: 1

      January 2017, according to my Windows Vienna Development Timeline. However, this all-64-bit announcement was not something I anticipated. The next thing my timeline was looking for at this point was an announcement about the filesystem, and not until fourth quarter this year. It remains to be seen what significance this announcement will have, and whether it will place Vienna development ahead of schedule (versus my timeline projections) or simply turn out to be a detail I did not forsee.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    20. Re:As though any processor by StikyPad · · Score: 1

      I don't know -- he's your friend -- but either it was a GF3, or you're mistaken about the time of purchase. Point is, a system built at XP launch wouldn't meet the minimum Vista reqs.

  6. Windows on Mac 32-bit by Anonymous Coward · · Score: 0

    Are you kidding!? I'm ecstatic that Vista is the last Windows that could potentially run on my beloved MacBook Pro - even after I sell it at some time in the future, I'll sleep better at night knowing it won't be running the latest showstopper bug from Redmond.

  7. Mac Owners (not) Running Windows by ShedPlant · · Score: 2

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run. I personally doubt most Mac owners will care too much about running the competition's OS.
    1. Re:Mac Owners (not) Running Windows by Sancho · · Score: 2, Insightful

      I don't know. Some people attribute the raging success of Apple's computer line in the past couple of years to the switch, because virtualization is now much better. Certainly most of the geeks I know that run Apple only switched because they could use virtualization to run those apps that they could not live without, as well as for testing in other OSs.

    2. Re:Mac Owners (not) Running Windows by catbutt · · Score: 1

      Most Mac owners do not actually work for Apple Inc, so therefore Microsoft is not "the competition".

    3. Re:Mac Owners (not) Running Windows by gnasher719 · · Score: 1

      '' I personally doubt most Mac owners will care too much about running the competition's OS. ''

      If they run Windows, they run it to access some Windows-only application, not to get a flashy, tasteless user-interface, so Macintosh users are much better off with Windows XP anyway.

    4. Re:Mac Owners (not) Running Windows by billcopc · · Score: 1

      It's not so much the virtualization, as hardware VT is apparently slower than VMWare (big big blunder!). More important is the fact that you can have Mac OS and Windows on the same machine on Intel Macs. Windows has drivers for everything, so it runs everywhere. Mac OS does not, it only has support for Apple boards.

      Apple's success is partly due to the fact that they've practically removed the barrier to entry. People who were curious about a Mac, but couldn't justify buying a second computer, or didn't want to risk switching, now can have both... 100% legally and supported.

      --
      -Billco, Fnarg.com
    5. Re:Mac Owners (not) Running Windows by Sancho · · Score: 2, Interesting

      The hardware VT bit is a bit misleading. Some instructions are slower under Intel's VT instruction set than under software emulation or native virtualization. However some instructions are faster. A virtualization company who tests these things will be able to utilize some of the hardware VT to gain an edge.

      Regardless, VMWare uses native virtualization in all of its products, meaning it still needs to be run on the same type of CPU. It runs the instructions directly on the CPU, so the switch to Intel was still important. Virtual PC for the Mac uses emulation, which is much slower.

      Of course, being able to boot Windows is certainly a factor, too. Before Boot Camp, though, it was probably beyond the capabilities of most people.

    6. Re:Mac Owners (not) Running Windows by mrchaotica · · Score: 1

      I was under the impression that the "raging success" has been going on since about the first iMac, or at least the introduction of OS X, both of which happened long before the Intel switch.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    7. Re:Mac Owners (not) Running Windows by babyrat · · Score: 0, Offtopic

      Since when is an 'owner' of a MAC in 'competition' with Microsoft?

      I use Windows here at work - I don't consider myself to be in competition with Apple.

      I own a Yamaha motorcycle. I don't consider myself to be in competition with Suzuki (ok, maybe at the occasional red light if there happens to be a Suzuki next to me)

    8. Re:Mac Owners (not) Running Windows by vandon · · Score: 1

      not to get a flashy, tasteless user-interface

      Wait, wait, wait...I thought everyone was saying that Vista copied the Mac interface. Are they now saying that the Mac interface is flashy and tasteless?
    9. Re:Mac Owners (not) Running Windows by toddestan · · Score: 1

      I personally doubt most Mac owners will care too much about running the competition's OS.

      Where have you been? The biggest thing in the Mac world for the past year or so is the fact that you can now run Windows.

    10. Re:Mac Owners (not) Running Windows by MoHaG · · Score: 1

      ....Certainly most of the geeks I know that run Apple only switched because they could use virtualization to run those apps that they could not live without, as well as for testing in other OSs. I switched because I was curious about OS X and the Intel Macs at least gave me a backup plan if OS X was not sufficient for my needs. On PowerPC you had no real option of running Windows, with Intel you at least have that option if OS X does not work out.

      I know Linux was an option for the PowerPC, but if you need applications that does not run under OS X (such as certain Matlab toolboxes, which I run on my desktop), they are unlikely to work under Linux.
    11. Re:Mac Owners (not) Running Windows by billcopc · · Score: 1

      I'm still waiting for the day we can partition PCs like mainframes, each slice running an independent OS yet sharing all the hardware. Something like VMware ESX, but for the mainstream. Linux on one half, Windows on the other, and the ability to switch between the two at will (or route them to dedicated monitors and input devices). As a software developer, I have three options:

      1. Run one main OS, and encapsulate the other in VMware with reduced performance.
      2. Run two separate PCs, which means double the cost, double the space, and double the cabling.
      3. Dual boot one machine and hope no one's there to point and laugh

      Right now I use #2, but it's a pain in the butt. The systems are never pegged and I really just have more hardware than I need. If I could condense the two into one beefy rig and dynamically assign processors/memory to each one as needed, it would not only save me money, but it would make it much easier to maintain as I only have one set of hardware to support rather than 2-3. One power supply, one RAID controller, one chassis to cool.

      --
      -Billco, Fnarg.com
    12. Re:Mac Owners (not) Running Windows by rising_hope · · Score: 1

      I used to care. Then I realized I don't need to, mostly. Instead, the Windows partition of boot camp is feeling like this 40GB boat anchor partition eating up space on my hard drive. As a recent "switcher," I can definitely say I would not have switched if Boot Camp wasn't an option. And, for the first week or so, while I was dipping my feet in the water, I probably spent more time in Windows than OS X. Then came my install of Parallels, which let me only use Windows when I needed it. Finally, it just took up so much time to boot and resources, I ended up using Mac OS X native apps. At this point, about the only thing I have left I really keep Windows around for is for installation of apps on my Windows Mobile phone & for Streets & Trips for weekend road trips, for which I've not found a good substitute. And, the more I use Mac OS X, the more I'm realizing how subtle and brilliant many of the features are. There are some grips I have about the OS, but in general, I find it really polished. (Too few view options in Finder, no "snap to grid" feature to keep icons organized.) Then, there are some features I find so useful, it drives me crazy when I have to use my PC laptop at work, now. Particularly, the trackpad gestures. For windows users looking for a solid piece of hardware, Apple makes a great piece of hardware. And, once you start to actually use OS X, you'll realize how little you actually need Windows, and how much better (overall) the OS X experience is. I feel like one of those annoying zealots now. Meh.

  8. I thought vista was the last one? by Gharbad · · Score: 2, Insightful

    Wasn't all the talk during vista's development that it would be the last operating system they'd make?

    I know that was taken back a while ago. Just saying.

    --
    "Gharbad no Hurt!" -Gharbad
    1. Re:I thought vista was the last one? by norminator · · Score: 1

      I'm pretty sure they never said they'd never make another operating system... They are primarily an OS company. What they said was that they weren't ever going to screw up on the development process of an OS again like they did Vista. They'll use different strategies to build the next OS (hopefully a shorter release cycle, less feature creep, fewer features dropped, fewer unrealistic promises, etc...). Hopefully it really does turn out different.

      Although this news sounds horrible. At one point Bill Gates talked about how eventually hardware would be free or nearly free, subsidized by the software. With Vista, and now this, they don't care at all about being friendly to low-power hardware (aka cheap or portable hardware) with their desktop OS. Linux looks more and more "ready for the desktop" all the time.

    2. Re:I thought vista was the last one? by harry666t · · Score: 2, Funny

      >Wasn't all the talk during vista's development that it would be the last operating system they'd make?

      World's End scheduled for late 2012.

      Vista *will be* their last OS.

    3. Re:I thought vista was the last one? by maxume · · Score: 1

      I bought a laptop last fall for $800. As far as I can tell, XP Pro accounted for less than $100 of that price. Given that Windows is what I know and that I will use the computer most days for at least 3 or 4 years, $100 is nearly as cheap as free. In another 12 or 18 months, I imagine that a $800 or $900 laptop will run Vista just fine.

      Linux needs to convince me that I will be just as comfortable as I am on Windows to get me to switch, not cost less(I ran Slackware for a while in 1998, perhaps I should give it another go sometime; those free bootable Ubuntu discs are pretty spiffy).

      --
      Nerd rage is the funniest rage.
  9. Obligatory... by mosel-saar-ruwer · · Score: 3, Funny


    ...2^64 bytes of RAM should be enough for anyone.

    1. Re:Obligatory... by mcpkaaos · · Score: 3, Funny

      Well, the systems will handle 2^64 bytes of RAM, but Windows will probably reserve the upper 2^48.

      --
      It goes from God, to Jerry, to me.
    2. Re:Obligatory... by Anonymous Coward · · Score: 0

      Please tell me I'll be dead before 2^64 bytes of RAM is not enough for anyone's processes. 4 gigabyte (4294967296 byte) core files are bad enough; I don't want to be the programmer that has to debug a process with a 16 exabyte (18446744073709551616 byte) memory footprint.

    3. Re:Obligatory... by dascandy · · Score: 1

      Actually, you'll only be able to access the lower 2^48 bytes due to an architectural limit imposed by the paging system. It's maximally 4 levels of paging (9 bits to each) plus 12 on the page -> 9 * 4 + 12 = 48 bits of addressing. And Windows will take the top 2^47 of that, yeah.

    4. Re:Obligatory... by TheThiefMaster · · Score: 2, Interesting

      Actually, last time I checked modern 64-bit cpus could actually only address 2^40 bytes of Ram, because you couldn't physically attach that much ram to them. 2^39 starting at 0 and 2^39 at the other end of the 64-bit spectrum.

      Essentially the upper half IS reserved for the OS (which is much more than 2^48, it's 2^63), but it will be a long while before it's a problem, because at the moment there's a big no-man's-land between the valid program and OS memory addresses.

    5. Re:Obligatory... by edwdig · · Score: 1

      Actually, last time I checked modern 64-bit cpus could actually only address 2^40 bytes of Ram, because you couldn't physically attach that much ram to them. 2^39 starting at 0 and 2^39 at the other end of the 64-bit spectrum.

      2^40 is the physical RAM limit. AMD didn't bother to connect more pins to the memory bus simply because it's going to be a long time before anyone tries to put that much RAM into a PC. Reduced the number of pins needed in the chip socket and cut costs.

      I believe the virtual memory goes to 2^48. Not sure the logic on that one, but it was probably to cut down on the size of page tables. I'm sure it's also one of those things that when the time comes, they'll add a setting in newer chips to enable more bits.

    6. Re:Obligatory... by Chris+Burke · · Score: 1

      2^40 is the physical RAM limit.

      Originally, yes. At some point it was increased to 2^48, matching the virtual address space. I'm not sure why since I doubt anyone even server customers were reaching the limit. Let's see: 8 sockets times 2 dram channels times 4 dimm slots times 2 GB dimms = 128 GB, and I'm not even sure you can populate 4 dimms per channel in a server setup. Still, that's 2^37, only a few doublings from 2^40. So they probably wanted to make sure they didn't ever have a problem by increasing the address space now.

      I believe the virtual memory goes to 2^48. Not sure the logic on that one, but it was probably to cut down on the size of page tables.

      Yeah, I'm pretty sure that was a major motivation too.

      I'm sure it's also one of those things that when the time comes, they'll add a setting in newer chips to enable more bits.

      They planned this from the get-go, which is why the spec requires that every address be in "canonical" form, which basically means the address is sign-extended from the highest supported bit. This keeps some too-clever-for-their-own-good programmer from realizing that they have a 64-bit address, but really the hardware only uses 48 of them, so that's 16 bits in which to stick some other piece of data. If that was allowed, then when the size of the virtual address space was increased that application would break.

      --

      The enemies of Democracy are
    7. Re:Obligatory... by marcosdumay · · Score: 1

      That's still a much better situation than now, that the systems can handle 2^31 bytes of memory, but Windows reserves the highter 2^30.

    8. Re:Obligatory... by SEMW · · Score: 1

      Excellent; so that leaves over 99.998% of the memory for everything else!

      --
      What's purple and commutes? An Abelian grape.
    9. Re:Obligatory... by edwdig · · Score: 1

      Originally, yes. At some point it was increased to 2^48, matching the virtual address space. I'm not sure why since I doubt anyone even server customers were reaching the limit.

      Never knew they actually made the change. Must've happened during the switch to the AM2 socket, as they would have to change the socket layout to do it. There wouldn't have been any advantage to limiting it to 2^40 if the socket still had the connections.

    10. Re:Obligatory... by StikyPad · · Score: 1

      But 48 is 75% of 64! What you're saying could only be true if we were discussing expon..

      Oh wait.

    11. Re:Obligatory... by Dominic_Mazzoni · · Score: 1

      Ah, sign extend - the infamous SEX instruction!

  10. Hope by Anonymous Coward · · Score: 0

    I can only hope this somehow leads to better 64bit support with the various Linux distributions.

    BETTER I say!

    1. Re:Hope by sqrt(2) · · Score: 1

      Linux is years ahead of MS in 64 bit support. Most distros have 64 bit versions along with the 32 bit ones. I have the AMD64 version of Feisty on my laptop (along with Vista Ultimate--32bit) and support is excellent.

      --
      If you build it, nerds will come. Soylentnews.org
    2. Re:Hope by vitya404 · · Score: 1

      If you are talking about binary-only packages, I share your opinion: why can't they compile/build it for other architectures too?
      You don't have this problem with open source: the code is (very much) CPU-independent.

    3. Re:Hope by HTMLSpinnr · · Score: 1

      However I bet you're still running the 32-bit version of Firefox for Flash support (unless you went the plug-in wrapper route). Sometimes the things that make the 64-bit experience lie outside the realm of the OS itself (i.e. 3rd party drivers, Adobe, etc.)

      --
      $ man woman *
      -bash: /usr/bin/man: Argument list too long
    4. Re:Hope by Anonymous Coward · · Score: 0

      Not every amd64 64-bit Linux is good. Some of them fail at supporting 32-bit very well; often they provide only base libraries (libc/X client libraries) and require users to build their own, find the package from an i386 repository and force it to install, or use statically compiled programs. It would be nice if package managers were aware of this and could help with installing 32-bit libraries.

      Solaris does it best; amd64/i386 are treated as the same platform, just with two different kernels/sets of drivers. The base userland is kept 32-bit yet 64-bit libraries + JRE are available. The same installer will work for a 32-bit and 64-bit installer. By default the 64-bit kernel is installed and booted on a 64-bit system, but the 32-bit kernel is still available at the grub boot screen.

    5. Re:Hope by edwdig · · Score: 1

      There's no 64 bit Flash because your Flash code is compiled into native code at run time. The compiler needs to be rewritten to make it work. Open sourcing the code wouldn't magically fix that.

    6. Re:Hope by vitya404 · · Score: 1

      That is exactly what I'm saying, but open sourcing would fix it. The only trick: open source flash. I mean the macromedia/adobe thing. You know, that runs your code... And currently it is not OSS. If it would be, we would already have 64bit flash up and working.

    7. Re:Hope by raxx7 · · Score: 1

      Users are still running the 32 bit version of Internet Explorer for flash support. They just don't know about it. :)
      Like Linux, Windows for x86-64 supports mixing 32 and 64 bit applications in the same system.
      Some independent software vendors feel that there is little point in porting (some of) their applications to 64 bit and thus will take their time in porting them.
      Among them, Adobe has no roadmap to release 64 bit Flashplayer or Reader for either Windows or Linux.

    8. Re:Hope by edwdig · · Score: 1

      That is exactly what I'm saying, but open sourcing would fix it. The only trick: open source flash. I mean the macromedia/adobe thing. You know, that runs your code... And currently it is not OSS. If it would be, we would already have 64bit flash up and working.

      No, you wouldn't have it up and running. Look at major projects like OpenOffice and Mozilla. It was years before a significant chunk of work on those projects was done by outside contributors. Compilers are pretty high up the list of difficult things to do. You're living in a fantasy land if you think people would be able to learn how the Flash code base works and write a new compiler for it in a short time period.

    9. Re:Hope by Danga · · Score: 1

      If you are talking about binary-only packages, I share your opinion: why can't they compile/build it for other architectures too?

      Because doing so would then say it is supported on those architectures which a company may not want to officially do. If you have a fairly large project that has been coded for 32-bit architectures for many, many years you can't just compile it for 64-bit architectures and hope it all ends up working because it probably will end up with bugs. Also, if your application has no need for "64-bitness" then why compile it that way and effectively double its size but get no performance gain? These are things you have to consider when you are working on large applications that have been around for a while and you also have a large user base.

      If an application does not need to be compiled for a 64-bit platform because it has nothing to gain from it then what is so bad about running the 32-bit binary version on the 64-bit platform?

      You don't have this problem with open source: the code is (very much) CPU-independent.

      Somewhat true, but you have to have someone willing to make it so. For a complicated project like OO.org or something similar changes just don't get made quickly and depending how complicated the work is to be done it may take quite some time. So a problem still exists because unless you can do the work yourself you will be SOL until someone else does that work which is the exact same case you would be in with closed source software.

      --
      Hey, there is only one Return and it's not of the King, it's of the Jedi.
  11. Don't fall into the trap by ArcherB · · Score: 4, Informative

    Windows Vista and Server 2008 will be the last versions of Windows capable of booting on 32-bit CPUs such as Intel Pentium 4 and Core Duo Before anyone falls into the trap I almost fell into, please note that the Core Duo is not the 64-bit capable Core2 Duo.
    --
    There is no "I disagree" mod for a reason. Flamebait, Troll, and Overrated are not substitutes.
    1. Re:Don't fall into the trap by sqrt(2) · · Score: 2, Funny

      Well, I bet that was awkward.

      --
      If you build it, nerds will come. Soylentnews.org
    2. Re:Don't fall into the trap by hackstraw · · Score: 5, Informative

      Before anyone falls into the trap I almost fell into, please note that the Core Duo is not the 64-bit capable Core2 Duo.

      Thanks for the heads up.

      I find the "PC" world funny. I've used higher end equipment for quite some time, and I've found myself back into "commodity" land and its pretty confusing.

      The summary says "AMD, which introduced 64-bit CPUs early". Huh?

      DEC Alpha chips were introduced in 1992 and were 64-bit. SPARC went 64-bit in 1995. MIPS went 64-bit in 1991. PA-RISC in 1996.

      AMD came out with 64bit/32bit hybrid chips in what? 2002-2003?

      How is this early?

      Also, Intel introduced the Itanium, a pure 64-bit chip in 2001. They had a strange i860 chip in the late 80s that was 64-bit.

      I've been running 64-bit linux for about 10 years plus or minus 6 months.

      To me, I find the x86_64 stuff to be a hack and late to the game. The only reason its remotely interesting is that its cheap, but calling this new or interesting is completely wrong.

    3. Re:Don't fall into the trap by seaturnip · · Score: 1

      "Early" relative to Intel's implementation of x86-64. All those other 64-bit CPUs you mention aren't x86 compatible and hence irrelevant to the workstation market.

    4. Re:Don't fall into the trap by 0123456 · · Score: 3, Insightful

      "All those other 64-bit CPUs you mention aren't x86 compatible and hence irrelevant to the workstation market."

      A few years ago, those 64-bit CPUs _WERE_ the workstation market.

    5. Re:Don't fall into the trap by jellomizer · · Score: 1

      It is not that much of a trap. Most users use their computers for 4 or 5 years and get a new one. Microsoft releases a new version of their OS every 4 or 5 years. So there is no big deal. It may be a larger esentive for developers to make sure their apps run on 64 bit systems more then the PC user.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    6. Re:Don't fall into the trap by Jeff+DeMaagd · · Score: 1

      I really don't think it's going to make any difference. If they released another OS three years after Vista, that means that the Core Duo will be about four years old. I think it's safe to say that a four year old computer is generally not worth the hassle of a new operating system. If it gets Vista-like delays, then that system would be six years old.

    7. Re:Don't fall into the trap by curmudgeous · · Score: 1

      The summary should have said "...x86 compatible 64-bit CPUs". The DEC Alpha was a great chip but it couldn't run x86 software (which is pretty much what killed it).

    8. Re:Don't fall into the trap by Anonymous Coward · · Score: 2, Funny

      A few years ago, those 64-bit CPUs _WERE_ the workstation market.

      Yeah, all 5,000 seats of it.

    9. Re:Don't fall into the trap by Anonymous Coward · · Score: 0

      Correction. Aren't relevent to the MS Windows market

    10. Re:Don't fall into the trap by Chas · · Score: 4, Informative

      "DEC Alpha chips were introduced in 1992 and were 64-bit. SPARC went 64-bit in 1995. MIPS went 64-bit in 1991. PA-RISC in 1996."

      And how many did you see, across the board, in consumer grade "Bob Everyman" systems?

      "How is this early?"

      Because Intel was basically telling people (rightly) that they really didn't need 64-bit on consumer workstations and laptops for another 10-15 years. AMD said "we've got it and we're releasing it". The adoption of the x64 stuff by Intel only reinforces this.

      "Also, Intel introduced the Itanium, a pure 64-bit chip in 2001."

      Which SUCKS for general computing use, and requires ridiculously complex "intelligent" compilers to eke decent performance out of your code.

      "They had a strange i860 chip in the late 80s that was 64-bit."

      Misconception. The data buses were 64-bits wide. And the FPU register depth was 64-bit (however, today's FPU have registers 80-bit deep by comparison).

      "I've been running 64-bit linux for about 10 years plus or minus 6 months."

      When did this become about dicksizing?

      "To me, I find the x86_64 stuff to be a hack and late to the game."

      As has been said about just about EVERY x86 development for most of the last 30 years. However, there's a reason why x86 is still the dominant platform extant. Underneath all the hacks and kludges and other cruft, the basic platform is stable, completely documented, and TIME TESTED. As such, the development community is orders of magnitude larger than any other. And, as a byproduct, the user community, who only cares about getting their hands on their personal favorite app, is several more orders of magnitude larger still compared to the user space of every other platform extant COMBINED.

      Yes, inertia may NOT be the best reason for holding on to a platform. However, as long as the platform does what's required of it, what's the legitimate bitch?

      --


      Chas - The one, the only.
      THANK GOD!!!
    11. Re:Don't fall into the trap by JasterBobaMereel · · Score: 1

      Can you tell that to all the people running Windows CE on a ARM 32bit processor ... On their Phone/PDA

      --
      Puteulanus fenestra mortis
    12. Re:Don't fall into the trap by cimetmc · · Score: 1

      No, that's wrong. What killed the Alpha was HP's business decision to drop the Alpha in favour of the Itanium.
      The Itanium while not so much a success in terms of units sold, was nevertheless in incredible success in the hype it created and cause most of the competing processors (PARISC, Alpha, MIPS) to abandon the market even before the Intanium shipped! Only Sun with the Sparc and IBM with their Power architecture didn't follow the hype and continued with their processors.

    13. Re:Don't fall into the trap by gertam · · Score: 1

      Hear hear! This is exactly what I was going to say. Having lived through Compaq/HPs disastrous decision up close, I can tell you that CxO types were showing us with great certainty how the Itanium was projected to outperform the EV8 (alpha) within 3 years. If they had ever built the EV8 it would undoubtedly be smashing not only the actual results that the Itanium has turned in, but those bogus predictions as well.

      Itanium was supposed to become the "Industry Standard" commodity CPU. Instead it is a niche player that had Intel backpedaling to support AMD's extensions to x86. Never trust your CxO when discussing technology. They are swayed by their Marketing buddies that buy them drinks on the golf course more than their own employees.

    14. Re:Don't fall into the trap by killpog · · Score: 1

      Unless you want it. I've got Debian Sid running on a Toshiba Satellite P105 w/Core Duo. Price. Wery, Wery Cheep. $600.00 US. Works great.

    15. Re:Don't fall into the trap by Anonymous Coward · · Score: 0

      Intel was not late to the game 29 years ago, when they introduced 8086. At the time they had a 16-bit microprocessor two years before their competitors. The product was not so elegant as the latter products, but it was enough.

      x68 is harder for hardware, mostly because of the varying instruction lengths. It's strength lies mostly in the old advantage. That does include good documentation etc.

      Although Vista's successor doesn't support 32 bits, the hardware most likely does.

    16. Re:Don't fall into the trap by Bassman59 · · Score: 1

      The summary should have said "...x86 compatible 64-bit CPUs". The DEC Alpha was a great chip but it couldn't run x86 software (which is pretty much what killed it).

      Don't forget that NT ran rather well (as well as one could expect it to run, anyway) on Alpha boxes. There were a handful of non-DEC companies selling Alpha workstations and they all pretty much died when NT on Alpha was killed.

    17. Re:Don't fall into the trap by Chris+Burke · · Score: 2, Insightful

      However, there's a reason why x86 is still the dominant platform extant. Underneath all the hacks and kludges and other cruft, the basic platform is stable, completely documented, and TIME TESTED.

      BWA HA HA HA HA HA HA!

      Sorry, I'm not trying to make fun, that was an excellent post so stumbling across that small clause thrown in there made me Laugh Out Loud.

      Sadly, there is a lot in x86 that isn't documented. Especially if you're looking for all that documentation in one place, but even without you're never going to find every piece of undocumented behavior. The worst part is that a lot of it you would never think could matter but ends up mattering a lot. Some of it has been discovered and documented on the net, others is "documented" only in the heads of the engineers who made the chips. This is ultimately in my opinion one of the only relevent digs against x86. It makes it extremely difficult to make fully compatible x86 chips, which is part of why there are so few people making them.

      Still, as long as all the AMD and Intel engineers aren't wiped out simultaneously, we should be okay. Transmeta and Via still know how to make x86 chips too. But pretty much any other ISA is better documented than x86.

      --

      The enemies of Democracy are
    18. Re:Don't fall into the trap by SEMW · · Score: 1

      DEC Alpha chips were introduced in 1992 and were 64-bit. SPARC went 64-bit in 1995. MIPS went 64-bit in 1991. PA-RISC in 1996." And how many did you see, across the board, in consumer grade "Bob Everyman" systems? Windows NT 4, hardly a niche OS, supported Alpha and MIPS.
      --
      What's purple and commutes? An Abelian grape.
    19. Re:Don't fall into the trap by multipartmixed · · Score: 1

      > Don't forget that NT ran rather well (as well as one could expect it to run, anyway) on Alpha boxes.

      Yeah, I got really excited when I debugging something on XP a couple of years ago, and got the Windows NT ARC Loader screen.

      I thought that had only been a DEC Alpha thing... (seriously -- I'm not an MS guy but ran Linux on an Alpha UDB for years)

      --

      Do daemons dream of electric sleep()?
    20. Re:Don't fall into the trap by jeremyp · · Score: 1

      Windows NT was originally released for x86, Alpha (and MIPS I think).

      --
      All I want is a secure system where it's easy to do anything I want. Is that too much to ask ~~ Randall Munroe
    21. Re:Don't fall into the trap by Anonymous Coward · · Score: 0

      When I was young & beautifull many years ago a 16-bit CPU was a 16-bit CPU not because of the address bus width but because of the amount of bits in the registers. That made 8086 and 8088 16-bit and their adress bus was btw. 20 bits wide (wich gave us 1 Mb of address space).
      Intel was very happy because MS didn't really push for 64-bits. It wasn't right for the consumer it was cheap for Intel (and for MS).
      ...and pls. keep FPU's out of this, their register depth is chosen for a given precision wich is required by ANSI or/and IEEE, they've got those large registers long time ago.

    22. Re:Don't fall into the trap by Anonymous Coward · · Score: 0


      And how many did you see, across the board, in consumer grade "Bob Everyman" systems?



      Here's a nickel kid, buy yourself a real computer.

    23. Re:Don't fall into the trap by Anonymous Coward · · Score: 1, Funny

      Yeah I know. My Nintendo 64 was 64 bit and those things are way outdated now.

    24. Re:Don't fall into the trap by Anonymous Coward · · Score: 0

      "Which SUCKS for general computing use, and requires ridiculously complex "intelligent" compilers to eke decent performance out of your code."

      That is a gross exaggeration. I work with HP-UX and OpenVMS on Itanium hardware and the compilers are pretty good today for general purpose code and database systems on Itanium hardware have good performance.

    25. Re:Don't fall into the trap by bored · · Score: 1
      But pretty much any other ISA is better documented than x86.

      Having actually done a decent amount of programming on some other platforms, I find this funny. Usually with x86 there is just a big gap in the manual about some piece of behavior or another. With the other platforms there is usually a line that says "the behavior is undefined". Which is _SO_ much better.

    26. Re:Don't fall into the trap by pinkfloydhomer · · Score: 1

      You are right that AMD wasn't the first company to make a 64-bit CPU. But they were the first to make a widely adopted 64-bit CPU. X86-64 has proven to be a much better way in practice to spread 64-bit to the mases, than was Itanium, let alone the Alpha or the crappy SPARCs.

      Also, X86-64 is not a hack. It is by far the cleanest and best branch on the X86-tree. The performance you get out of a modern AMD or Intel X86-64 CPU greatly surpasses what you will ever get from those old 64-bit CPUs that you mention, and even today, there are no competitors. The fastest SPARC is still a lot slower and a lot more expensive than the cheapest X86-64 CPU. X86-64 is not a hack, it is state of the art. /David

    27. Re:Don't fall into the trap by Chas · · Score: 1

      Yeah. And the reason Microsoft dumped these platform ports is because they were SO successful.

      --


      Chas - The one, the only.
      THANK GOD!!!
    28. Re:Don't fall into the trap by Chas · · Score: 1

      "That is a gross exaggeration."

      No. I think it spells out the problem quite nicely. Plus, your definition of "pretty good" and mine can vary by quite a bit.

      --


      Chas - The one, the only.
      THANK GOD!!!
  12. What? by drinkypoo · · Score: 0, Flamebait

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run."

    Owners of intel macs are mostly laughing up their sleeves because they're not running Windows.

    I doubt many mac users will install Vista at all, opting for Windows XP for compatibility.

    Windows software is only becoming less important in any case.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    1. Re:What? by Mantaman · · Score: 1

      you must be new here .. welcome to slashdot .. the place where we slag off ms whenever we can :)

    2. Re:What? by Jeremi · · Score: 1
      So...everybody on slashdot proclaims that Vista sucks so bad that it is the final nail in Microsoft's coffin...yet they are not happy that Windows will be discontinuing 32 bit support in 5 to 10 years???


      See the linked names above each post, the ones with a number next to them? Those are user names. They indicate that various posts were written by various people, each with their own opinions and worldview. Slashdot is not, in fact, a message board whose population consists of just you and one other wildly prolific and inconsistent poster.

      --


      I don't care if it's 90,000 hectares. That lake was not my doing.
    3. Re:What? by DriveDog · · Score: 1

      Should have said: "Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may be thrilled knowing that Vista will be the last Windows they will be asked to run."

    4. Re:What? by Anonymous Coward · · Score: 1, Funny
      Slashdot is not, in fact, a message board whose population consists of just you and one other wildly prolific and inconsistent poster.

      Hey! Look at MY name - I am a wildly profilic and inconsistent poster!

    5. Re:What? by WinterSolstice · · Score: 1

      Precisely... because, you know, all those of us who bought a first gen Intel Mac did it specifically to run Windows :D

      Honestly, I got one because I wanted to be able to easily run my old (pre Win95) games. They didn't run very well on PPC. If I had know how bad Adobe CS2 would suck on Intel, I wouldn't have even gotten one then. I'd have waited until CS3.

      --
      An operating system should be like a light switch... simple, effective, easy to use, and designed for everyone.
    6. Re:What? by ceoyoyo · · Score: 1

      Whew. I was getting worried about that guy. He's gotten a lot more prolific in recent years too.

  13. Windows timelines by Sancho · · Score: 1

    Anyone running a Mac is used to major upgrades not working (or rather, not working well) with old software. That's not going to be a problem. Besides, if the release dates of Vista and Vista++ are as far apart as the release dates of XP and Vista, most of those 1st gen Intel Macs probably won't be in use anymore.

    1. Re:Windows timelines by Anonymous Coward · · Score: 0

      Besides, if the release dates of Vista and Vista++ are as far apart as the release dates of XP and Vista...

      Actually, I've got an all-day meeting in five years. How about five years and a day?

    2. Re:Windows timelines by EvilTwinSkippy · · Score: 1

      Well part of that has to do with the fact that most of the companies writing software for the Mac 10 years ago are still in business and still writing new versions of the software.

      Apple has a less of a tendency of gobbling up, smothering, or otherwise competing with their customers.

      --
      "Learning is not compulsory... neither is survival."
      --Dr.W.Edwards Deming
    3. Re:Windows timelines by falcon5768 · · Score: 1
      You might be surprised. We still use first generation iMacs (as in tray load 233 mhz)

      Apple users tend to hold on to their machines for a long time. But then those of us who do tend to not be using Windows products anyway.

      --

      "Slashdot, where telling the truth is overrated but lying is insightful."

  14. Mac owners don't care by lightversusdark · · Score: 1

    Legacy Intel Mac owners are more likely nonplussed by the fact that if there was any advantage to running Vista over XP, be it through Boot Camp / Parallels; and the licensing of Vista didn't already forbid this in most cases, then after a product scheduled for release in 2008 reaches End-Of-Life, they will be unsupported.

    --
    "There is nothing nice about Steve Jobs and nothing evil about Bill Gates." - Chuck Peddle
  15. I wonder why that would be? by BJH · · Score: 1, Funny

    Could it possibly be because the next version of Windows will require more than 4GB of memory to run? ;)

    (Yeah, yeah, I know about PAE. It's a joke.)

    1. Re:I wonder why that would be? by Chris+Snook · · Score: 1

      I don't think you're off the mark there. During the lifetime of Vista, > 64 GB configurations will become common. During the lifetime of the next version, they'll become routine, and 32-bit will be bumping its head on the ceiling even with PAE.

      --
      There's no failure quite as dissatisfying as a complete and total solution to the wrong problem.
  16. This will make things interesting by einhverfr · · Score: 3, Insightful
    The real questions are:
    • will hardware vendors stop releasing 32-bit chips?
    • Will companies upgrade hardware in orer to get the latest version of Windows?
    • Will this help provide more incentive for a Linux desktop?
    • Will this increase the amount of lead going into our landfills?
    --

    LedgerSMB: Open source Accounting/ERP
    1. Re:This will make things interesting by theelectron · · Score: 1

      will hardware vendors stop releasing 32-bit chips?
      No, there are companies that still produce and sell 8 bit chips.http://www.microchip.com/

      Will this increase the amount of lead going into our landfills?
      What? Are you basing this on 64 bit chips being larger? Anyway, no. RoHS is influencing the American market quite a bit, so I would imagine that since these will be new chips following those guidelines, they will actually reduce the amount of lead going into landfills.
    2. Re:This will make things interesting by KlomDark · · Score: 1

      No, I think he means all the older 32-bit machines that will be heading for the landfill.

    3. Re:This will make things interesting by garcia · · Score: 2

      Well you certainly have hit all the buzztopics on the head haven't you?

      will hardware vendors stop releasing 32-bit chips?

      Probably not but they certainly won't become the main product. The main product is selling chips to people running Windows and if it's not supported in 32-bit the demand for new chips that are 32-bit will drop.

      Will companies upgrade hardware in orer to get the latest version of Windows?

      It depends but probably. Once the EOL happens for XP/Vista they will be forced to upgrade in order to keep up with everyone else.

      Will this help provide more incentive for a Linux desktop?

      No. People upgrade their computers when it "runs slow" (Spyware, old hardware, etc) and that happens every 2-5 years anyway. People are just going to do it and buy whatever the Big Box store or Dell is offering on special. I have a feeling that it will be 64-bit.

      Will this increase the amount of lead going into our landfills?

      Not anymore than it already has been increasing. People will upgrade on their normal computer lifetime schedule. There won't be a mad dash (just like there wasn't for Vista) to upgrade.

    4. Re:This will make things interesting by darkwing_bmf · · Score: 1
      will hardware vendors stop releasing 32-bit chips?

      Who cares? That's not relevant. Hardware companies still produce 16-bit chips but that doesn't mean most people are still using 16-bit desktop computers.

    5. Re:This will make things interesting by mycroft822 · · Score: 1

      If you look at the market distribution of microprocessor sales, the PC market share is very small. The biggest use of processors is in the embedded systems sort of market. As technology progresses, various products get more flashy, and 32 bit chips get cheaper to make, they will get used more in those sort of applications. So in short, probably not.

    6. Re:This will make things interesting by ACS+Solver · · Score: 1

      The real question is how soon the next Windows comes out. If Microsoft returns to frequent releases, and the next OS comes out in 2009, it will see slow adoption, as 64-bit will still be rare on lower-end PCs and poorer countries. If it's another longer dev cycle, with 2011-2012 for the OS, then 64-bit CPUs will be on every PC that could benefit from an OS upgrade anyway. In 2012, there'll probably be as many 32-bit CPUs as there are older Pentium IV-level CPUs now with an under 2GHz clock.

    7. Re:This will make things interesting by El+Gigante+de+Justic · · Score: 1

      will hardware vendors stop releasing 32-bit chips? Nope - if they can keep making them smaller, less power hungry, and with less heat output, they'll have a use in various embedded systems. Will companies upgrade hardware in order to get the latest version of Windows? Eventually, yes. My company is currently in the process of upgrading to Core 2 Duo workstations so we can run Vista in VmWare more efficiently (needed for software testing). Once 64 bit only Windows comes out, we'll probably have to upgrade to something that lets us run virtual 64 bit Windows as well. Will this help provide more incentive for a Linux desktop? Not likely. While Linux is getting easier to install and use, your average consumer will continue to purchase Windows, because they have used it in the past or use it at work. Apple will probably make some headway since people know the name and it has the advertising power, but Linux just isn't going to catch on with Joe Blow consumer until I can purchase a Linux box, put any hardware I want into it with no problems, attach any peripheral I want with no problems, etc. Plug and play and driver support are a big deal. My wife and I currently have two printers because there aren't drivers for my Dell printer avaiable for her Mac (though that's Dell's issue, not Windows or Macs). Will this increase the amount of lead going into our landfills? Municipal computer recycling programs are growing, and there are lots of small companies that will take your old equipment for less than what the city currently charges for lots of that stuff. As people get more and more educated about identity theft and the like, I suspect more people will take their computers to businesses where they can verify the hard drive has been destroyed; or maybe just do what I do and keep it for myself to be reformatted and used again in an enclosure.

    8. Re:This will make things interesting by El+Gigante+de+Justic · · Score: 1

      Crap, I've been posting on phpBB boards too much and forgot to add line breaks, sorry about that.

    9. Re:This will make things interesting by Chris+Burke · · Score: 2, Insightful

      will hardware vendors stop releasing 32-bit chips?

      As far as AMD and Intel are concerned, 32-bit-only processors are nearly gone already.

      Will companies upgrade hardware in orer to get the latest version of Windows?

      Maybe, but it's more likely just to upgrade the system specs like they're having to do with Vista rather than to support 64-bit. The upgrade needed to run Vista probably entails purchasing a 64-bit processor, even if they don't use a 64-bit OS.

      Will this help provide more incentive for a Linux desktop?

      Nope.

      Will this increase the amount of lead going into our landfills?

      Can't see how, but I don't know.

      --

      The enemies of Democracy are
    10. Re:This will make things interesting by theelectron · · Score: 1

      Yes, but I would imagine they are heading there anyway, especially by the time the next version of Windows comes out. So requiring 64bit won't really affect the lead in landfils.

    11. Re:This will make things interesting by billcopc · · Score: 2, Interesting

      Will this increase the amount of lead going into our landfills?


      No, but it will increase the amount on my hydro bill when I build a cluster of "obsolete" 32-bit processors in the basement :)

      Just because Microsoft gives up on something, doesn't mean everyone else has to. Just look at Vista, it was more exciting when it was still vaporware. Even people buying new Vista-ready PCs still prefer XP, because Vista does hardly anything new, certainly nothing better. Microsoft should have released a new Theme pack for XP instead. I'm sticking witn XP for as long as I can, despite having a perfectly fast dual-core with gobs of ram and a beast of a graphics card. I didn't buy all that nice kit to waste all its power on a filesystem and mouse driver... I spent the cash to do video processing, rendering and GAMING! Anything that takes power away from those primary activities is a bad thing. That's why I like Linux because I can make it as lean as I want to squeeze out a few extra cycles.

      If I wanted a pretty OS, I'd buy a Mac. They manage the slick graphics without the outlandish hardware requirements, and they can actually do two things at once without both processes stuttering.
      --
      -Billco, Fnarg.com
    12. Re:This will make things interesting by Short+Circuit · · Score: 1

      Will companies upgrade hardware in orer to get the latest version of Windows? Based on release rate, figure on Office 13 doing it. Office 11 already has mechanisms in place to make it difficult for low-end users to share documents with users of Office 2003 and earlier. It wouldn't surprise me if Office 13 held features that made it a pain to go back to Office 11/12.
    13. Re:This will make things interesting by mmkkbb · · Score: 1

      You can just change your default posting mode to plain old text. Then your line breaks will be translated to
      s

      See?

      --
      -mkb
    14. Re:This will make things interesting by NSIM · · Score: 1
      # will hardware vendors stop releasing 32-bit chips?

      Pretty much already have, all the current gen x86/AMD are 64-bit capable

      # Will companies upgrade hardware in orer to get the latest version of Windows?

      They won't need to anymore than they already do.

      # Will this help provide more incentive for a Linux desktop?

      Don't see any particular reason why it should.

      # Will this increase the amount of lead going into our landfills?

      Huh?

    15. Re:This will make things interesting by Anonymous Coward · · Score: 0

      1) No, there is still a large market for small processors, especially for embedded systems, kiosks, and other lower demand applications. I.e. the doorlock at your local hotel does not require 64-bit MS O/S to let you into your room.

      2) No. Companies are slow on roll-out. They are not going to wholesale dump all their IT investment just because MS dumps a new O/S on the market. They will standardize on higher end gear, maybe, but expect 2-3 years to cycle through their install base.

      3) Likely, since it will still run current software. As long as Linus keep supporting 32 bit, we'll have it for a long time, and salvaged hardware will be turned into linux.

      4) That equipment not re-deployed as Linux will likely end up in land-fills, so yes to that, too. 3 and 4 are not mutually exclusive.

    16. Re:This will make things interesting by level_headed_midwest · · Score: 1

      64-bit CPUs show up on pretty much all desktop computers today, regardless of price, and have done so for some time. The "budget" chips are generally just lower-clocked main-line with smaller buses and less cache. If the parent chip is 64-bit, then the budget chip will also be 64-bit. Why take it out if it's already there? Intel and AMD have been making 64-bit chips for 3 years and there wasn't that big of a delay between the top-line chips being 64-bits and the cut-down budget versions being made. There is a little delay to sell used-to-be top-line chips in budget systems, but the catch-up is rather quick. The only exception to this rule is in notebooks, where the parent chips were 32-bit Pentium Ms and Core Duos. The budget chips didn't magically grow x86_64 extensions that the parent chips didn't have, so they are 32-bit. But all new notebook chips are 64-bit and thus the budget chips will be also.

      The really poor countries generally have a real hodgepodge of old and cast-off hardware, so who really knows what they're running. There aren't generally all that many machines in those countries anyway, and the ones they do have probably can't handle a completely new OS anyway. And it's not like somebody with an annual income of $500 would spend 80% of it on a Microsoft Windows license anyway. So that point is pretty well moot.

      --
      Just "gittin-r-done," day after day.
    17. Re:This will make things interesting by ACS+Solver · · Score: 1

      If you take a look at Eastern/Central Europe, you'll see that most desktop PCs are without 64-bit support. But the real issue isn't that people here won't spend a large part of their income on a Windows license. They already don't do that. Still, as long as people in these countries continue to use their XP/Vista PCs, with pirated copies of the OS, Microsoft retains dominance. If they can't even pirate it because of the need for 64-bit CPUs, they'll just look for another OS to run.

    18. Re:This will make things interesting by PinkyGigglebrain · · Score: 1

      "Probably not but they certainly won't become the main product. The main product is selling chips to people running Windows and if it's not supported in 32-bit the demand for new chips that are 32-bit will drop."

      Actually, no.

      About 90% of the processors made are for non-desktop applications, mostly embedded systems. Your right about the fact that the companies who have desktops/laptops as their core market will produce the systems that sell, but the chip makers will continue to make whatever the rest of the processor market wants, be it 4-bit(yes, they still make them) or 128-bit cores.

    19. Re:This will make things interesting by PinkyGigglebrain · · Score: 1

      As far as AMD and Intel are concerned, 32-bit-only processors are nearly gone already

      I don't know about AMD but for intel about 90% of the chips they make are NOT for desktops but for embedded aplications, its a bigger market, more stable too, and they will not turn their backs on it.

    20. Re:This will make things interesting by marcosdumay · · Score: 1

      1: Yes, but not because of lack of support. When Windows* needs 1GB of memory just to barely run, one'll expect people to want more than 2GB (maximum for normal 32 bit systems). Thus, people'll want 64 bit systems (just in time to avoid year 2038 bug).

      2: They'll probably be already on 64 bit systems by the time Microsoft releases a new Windows (if they ever release one).

      3: Probably no. But if Linux fail to be mainstream by the time, it must have a big intrinsical problem.

      4: Probably no, since people don't hush to upgrade their OS by a long time now (since 95 I guess).

      In short, that's a huge piece of non-news. Did you really expect next Windows to run on (currently being abandoned) 32 bit PCs?

      * Going out of Windows is an option, but even then people will have uses for more memory.

    21. Re:This will make things interesting by Chris+Burke · · Score: 1

      Yeah, and at least the most well known chip, x-scale, isn't even x86. I'm only talking about non-embedded markets here.

      --

      The enemies of Democracy are
  17. seven year cycles by Anonymous Coward · · Score: 0

    This will matter in what, 2014?

  18. not the end of the world by jollyreaper · · Score: 1

    We're likely to keep running Server 2003 in the office for years before even contemplating an upgrade. By the time we hit the 64-bit wall, it'll be time to retire these servers from the frontlines anyway. (5 years, maybe more?) I think a greater concern is the utter piggishness of Windows in the first place, requiring so much horsepower just to boot to the friggin' desktop. If you want to get your ear ripped off with a rant, just ask a programmer to contrast the performance and bloat of simple "hello, world" programs as written in C vs. C# and the whole .net nonsense.

    --
    Kwisatz Haderach
    Sell the spice to CHOAM
    This Mahdi took Shaddam's Throne
    1. Re:not the end of the world by sid0 · · Score: 1

      Oh, come on. .NET isn't for Hello World programs. Hello World running faster in C tells you jack squat about performance vs .NET, or the features.

    2. Re:not the end of the world by Mattintosh · · Score: 1

      I'm a C# fanboy (and a Mac fanboy, oddly enough), and I promise not to rant.

      I'm fairly certain that if you're writing against the .NET CLR, then bloat isn't your concern. It's pretty obvious that .NET has that as a bullet-point feature (so does JRE, to be fair). You're using .NET because it allows you to quickly develop stuff that does what you need, not because it's the most efficient code possible.

      I'm also certain that if you're writing "Hello, World!"-level programs, then you're not among those who care about bloat and performance. If you are, then echo echo Hello, World! > helloworld.bat is probably WAY more efficient.

      I just don't understand the hate... C# and .NET are actually good products from Microsoft. Hate the crap like Windows. Don't bring down the good stuff.

    3. Re:not the end of the world by Anonymous Coward · · Score: 0

      Well, really, they're just rehashes of products from Sun.

      So I don't know if you'd call them GOOD exactly, maybe better than the last version of Visual Retardation Enterprise Studio Ultimate Extreme(tm).

    4. Re:not the end of the world by jollyreaper · · Score: 1

      "Hello, world" were the first examples he used when ranting about it. He had more specific gripes when getting into the meat of the code he was working on but I don't know all the details and would probably get half of them wrong trying to repeat them. He works on custom database stuff for investment firms.

      I know that there's a balancing act between code speed, size, and rate of creation. With most balancing acts, trying to max the optimization on one end will bork things on the other end. Of course, many companies don't even get as far as size and speed, their motto is "if it compiles, ship it." The disaster follows.

      --
      Kwisatz Haderach
      Sell the spice to CHOAM
      This Mahdi took Shaddam's Throne
    5. Re:not the end of the world by Shados · · Score: 1

      In other news, RDBMS are full of "bloat" when all you want is persist a simple string of text to disk, what nonsense! No such problem with plain text files!

  19. Fortunately for first gen Mac users... by turboflux · · Score: 1

    ... it will be at least 5 years before a new version of Windows comes out. That is, if they even want to install Windows in the first place.

    Not only that, but it doesn't apply just to Mac users - it would apply to anyone running an early Core Duo, would it not?

  20. Can macromedia do the impossible, heh.. by GreggBz · · Score: 2, Funny

    The Real Motivation:
    Buh-Bye Flash, hello Starlight! (or whatever it's called)

  21. Oh... by Anonymous Coward · · Score: 0

    Won't have to worry about it for the next 5-8 years...or however long it takes them to put out a new OS.

  22. I wouldn't worry... by Sometimes_Rational · · Score: 1

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run.

    I wouldn't worry about that. When the next version of Windows comes out 5 to 10 years from now, those macs will be nearly out of date anyway.
    --
    Warning: The intelligence of this post may be larger than it appears.
  23. Is there a tangible reason to drop 32-Bit? by anss123 · · Score: 3, Interesting

    Linux, *BSP, etc, etc, are happy to support 32-Bit/64-Bit at the same time. I tried out the 64-Bit version of Windows Vista in VMWare (which can run 64-Bit Vista on top of 32-Bit Vista) and the only "benefit" I got was that my old 16-Bit apps stopped running. (Got several great 16-Bit games, and a 16-Bit dictionary.) What can the newfangled 64-Bit future Windows do that won't be feasible with a 32-Bit version lurking around?

    1. Re:Is there a tangible reason to drop 32-Bit? by 19thNervousBreakdown · · Score: 4, Funny

      ... a 16-Bit dictionary.

      Abridged, I assume?

      --
      <xml><I><am><so><damn>Web 2.0</damn></so></am></I></xml>
    2. Re:Is there a tangible reason to drop 32-Bit? by shoptroll · · Score: 1

      16-bit games? Shouldn't you be running those in DOSBox?

      --
      Insert Sig Here
    3. Re:Is there a tangible reason to drop 32-Bit? by Anonymous Coward · · Score: 1, Funny

      What can the newfangled 64-Bit future Windows do that won't be feasible with a 32-Bit version lurking around?

      It can use all the bits in your processor instead of half of them.

    4. Re:Is there a tangible reason to drop 32-Bit? by Waffle+Iron · · Score: 1

      Abridged, I assume?

      No, just segmented...

      aa:rdvark
      ab:aci
      ...
      zu:cchini
      zy:gote
    5. Re:Is there a tangible reason to drop 32-Bit? by LWATCDR · · Score: 1

      Not a chance.
      The child of Vista will "require" a 64-Bit CPU to boot but you can bet your bottom dollar that it will run 32 and even 16 bit code.
      Microsoft will not throw out compatibility. If they required you to buy all new software to upgrade then you might as well move to a Mac or Linux.
      Microsoft lives because they keep running old code.
      I can still run Turbo Pascal in Windows XP and I wouldn't be shocked if I could in the child of Vista.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    6. Re:Is there a tangible reason to drop 32-Bit? by pandrijeczko · · Score: 1
      I can still run Turbo Pascal in Windows XP and I wouldn't be shocked if I could in the child of Vista.

      Ahem! You missed the words "demonic", "hellspawn" and "bastard" between "the" and "child". Do take more care in future.

      --
      Gentoo Linux - another day, another USE flag.
    7. Re:Is there a tangible reason to drop 32-Bit? by david.given · · Score: 2, Funny

      ... a 16-Bit dictionary.
      Abridged, I assume?

      Yeah, it'd only contain 32768 words...

    8. Re:Is there a tangible reason to drop 32-Bit? by EvanED · · Score: 1

      The child of Vista will "require" a 64-Bit CPU to boot but you can bet your bottom dollar that it will run 32 and even 16 bit code.

      By my understanding, Vista has already dropped support for 16 bit code.

      In Windows NT (generic term for NT, 2K, XP, Vista...), programs don't make direct system calls. In fact, the system call interface (called the Native API) is somewhat undocumented and completely unsupported. In fact, the Windows build process automatically generates system call numbers during each build. Instead, NT has a notion of subsystems that provide a "view" of the system calls through a different API. The one that 99% (this statistic from a study from Out Of My Ass, Inc.) of Windows programs use is called the Windows subsystem (previously the Win32 subsystem) because it provides Windows API calls (previously the Win32 API). In other words, the Windows subsystem translates Win32 API functions to NT system calls. For instance, CreateFile behind the scenes calls the NT function NtCreateFile. While named similarly, they have different arguments. In general, Win32 API functions may make no system calls or multiple system calls, and also do some other bookkeeping stuff.

      (If you remember during the MS antitrust trial people were saying that Office had an unfair advantage because MS was using undocumented APIs -- I'm pretty sure that this is what they were talking about. And from what I hear, when the Windows team found out that the Office team was using their native API, they were none to happy.)

      Anyway, the point of this is as follows. When you run a 16-bit program in the 32-bit version of NT, it does NOT run in the Windows subsystem. It runs in a different subsystem made for running 16-bit programs. (It's called Windows on Windows 16, or WOW16. If you look in your processes list and you run a 16-bit program, you'll see it there as wowexec.exe.) The same thing is true if you run 32-bit programs in 64-bit Windows: it runs in a separate subsystem, WOW64. (Don't ask me why it's not WOW32...)

      Now, WOW16 is not shipped with 64-bit versions of Windows. Thus your support for DOS and Win3.1 applications (unless they use Win32s... wow, that's something I didn't think I'd say again) has *already* been dropped from 64-bit versions.

      I suppose it's possible they'll add it back... but I doubt it.

    9. Re:Is there a tangible reason to drop 32-Bit? by EvanED · · Score: 1

      By my understanding, Vista has already dropped support for 16 bit code.

      Just to clarify, this should say x64 Vista. 32-bit builds of Vista still come with WOW16.

    10. Re:Is there a tangible reason to drop 32-Bit? by LWATCDR · · Score: 1

      I haven't tried to run Turbo Pascal on 64 bit vista yet. You may very well be right about 16 bit code. I still will bet big money that Child of Vista will run 32 bit code just fine.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    11. Re:Is there a tangible reason to drop 32-Bit? by EvanED · · Score: 1

      I still will bet big money that Child of Vista will run 32 bit code just fine.

      Oh, I'm sure too. I would say there's probably another decade and a half or two of support for 32-bit applications.

    12. Re:Is there a tangible reason to drop 32-Bit? by Short+Circuit · · Score: 1

      AMD64 has several ISA enhancements (Such as additional GPRs) which make developing software for them much more efficient, which will aid in improving application performance.

    13. Re:Is there a tangible reason to drop 32-Bit? by Anonymous Coward · · Score: 0

      I'll blow my comment-for-the-day just to say: damn, that was a funny reply!

    14. Re:Is there a tangible reason to drop 32-Bit? by LWATCDR · · Score: 1

      The problem with this no 16 bit or no 32 bit code is that it really is a waste. Very few programs need 64 bit integers or 64 bit address spaces. All things being equal and frankly on the X86 they are not equal a 32 bit program should run faster and use less memory than a 64bit program. I really don't see much need for a 64bit music player or word processor or for most people a 64-bit spreadsheet. Four gigabytes is enough memory for most applications.
      Oh well the abundance and waste of cpu cycles and memory bandwidth marches on.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    15. Re:Is there a tangible reason to drop 32-Bit? by teg · · Score: 1

      DRM. 32 bit windows is open compared to what 64 bit is.... no more uncertified drivers for you,they might interfere with DRM. Can't have customer's convenience in the way of full DRM, you know.

    16. Re:Is there a tangible reason to drop 32-Bit? by Jackie_Chan_Fan · · Score: 1

      Right so i'll stay limited to 3.5 gigs of ram and 2gigs per process, just cause with 32bit i can use open drivers...

      i'll take 64-bit any day over 32bit. 32bit is dead

  24. Time to burn for Intel Mac users. by Lethyos · · Score: 1

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run.

    If the XP to Vista roadmap is any indication, I figure they have at least five years before they have to worry about the next major Windows release not running on their machines.

    --
    Why bother.
    1. Re:Time to burn for Intel Mac users. by SoTuA · · Score: 1

      Exactly. Most of those first-get Mac users will have happily upgraded to whatever 64-bit chip Intel sells for next-get Macs a long time before Microsoft's next Windows incarnation hits beta.

  25. YES! by Quantam · · Score: 4, Interesting

    As a programmer I've been waiting for this. I was actually disappointed that Vista would support 32-bit CPUs, but I guess there was no way around that, given how common 32-bit x86s still are. Having one architecture to support will make things much easier, as well as get people to actually update their legacy code. Now if MS could get them to actually fix all the problems due to generally crappy code (like requiring admin)...

    --
    You have tried to support your argument with faulty reasoning! Go directly to jail; do not pass Go, do not collect $200!
    1. Re:YES! by locokamil · · Score: 0

      You do realize that a 64 bit OS will not mean legacy apps will get rewritten... it'll mean that the market for 16bit emulation software will explode.

    2. Re:YES! by Applekid · · Score: 1

      It's still not going to be "one" architecture. CPUs are still going to have their own specialized instructions and extra sets (Intels SSE83 and AMD's 3DNOWFORREALTHISTIME).

      Also, not necessarily at you, but if any Windows developer does so in C or C++, you have been using the new headers with 64-bit compatibility warnings, haven't you?

      --
      More Twoson than Cupertino
    3. Re:YES! by Undertaker43017 · · Score: 2, Interesting

      Dream on!

      You think the hardware vendors are waiting around? They are already dreaming of 128-bit CPU's.

      In 7-8 years when/if Vista's successor is ready the hardware vendors will already have had 128-bit CPU's on the market for at least a year, and convinced everyone that they need one.

    4. Re:YES! by Anonymous Coward · · Score: 0

      "Having one architecture to support will make things much easier, as well as get people to actually update their legacy code."

      We already have one architecture to support! It's 32 bit. Transitioning to another one will just cause headaches.

    5. Re:YES! by BlackSnake112 · · Score: 1

      128-bit? Skip that I'm going for 65536-bit. (and 131072-bit is never going to catch on)

    6. Re:YES! by nine-times · · Score: 1

      Apple manages to support 32-bit and 64-bit architectures for both PPC and Intel. Linux supports *tons* of different architectures. Why is it that it's a particular stumbling block for Microsoft and Microsoft developers?

      I'm not a developer, so I'll admit that I'm not really that knowledgeable, but it seems to me that if it's too difficult for programmers to support different architectures, the solution isn't to restrict supported architectures, but rather to improve the ability to develop across multiple architectures. Ideally you should be able to develop a program once and have it run on any architecture and on any OS with minimal changes.

      If you don't agree, consider that the Intel x86-64bit processors probably won't be around forever. What happens the next time Microsoft decides to change their preferred platform. Do all the old platforms just become obsolete? Shouldn't they be working towards making these sorts of transitions seamless.

    7. Re:YES! by Alexpkeaton1010 · · Score: 1

      I like requiring admin. I want to know when your shatty code is running!

    8. Re:YES! by Anonymous Coward · · Score: 0

      Microsoft also supports different architectures. At this time 3 (X86, X64 and IA64). In the past they uspported PPC, MIPS, Alpha.

      I bet Vista, if not even XP, has no way to work on a 80386 without changes even if the instruction set is the same, just to be able to use some instructions like CMPXCHGwhatever or SYSCALL/SYSENTER. Yes, bar some isolated place they *could* run on a 386 but would that make sense ? The only thing gained would be geekness (look! my OS runs on a 386sx/25!!! now we clicked start, in an hour or so we will be able to click "run" and then write notepad and before tomorrow we are editing on a 386sx/25..). Even as little as it may seem supporting an old CPU has big costs (testing, coding, etc) which are cut if not justified by market figures.

      Now let's think about Vista. The only reason it supports x86 and hasn't dropped x64 yet is because of late Intel CPUs. Pentium-D and above all Pentium-M and Core Duo were 32bit only. People with first gen Pentium 4 or Athlon XPs simply will not upgrade to Vista.
      When next Windows will come (optimistically 2009/2010 ?) what will the market for Athlon XPs be ? How many people will spend 500$ for Windows Whatever to run it on an Athlon XP 3200 ?

      They have NO difficulty (well no more than anyone else) on programming on different architectures, but it has a cost for no gain.

      The only reason for Linux and *BSD to run on so many architectures (compared to running on, say, the most used 5 o 10) is the geekness factor. Open Source OS live on the geekness factor and they cannot betray it because they rely on geeks for their marketing, for better and for worse.

    9. Re:YES! by jgrahn · · Score: 1

      Apple manages to support 32-bit and 64-bit architectures for both PPC and Intel. Linux supports *tons* of different architectures. Why is it that it's a particular stumbling block for Microsoft and Microsoft developers?

      I'm not a developer, so I'll admit that I'm not really that knowledgeable, but it seems to me that if it's too difficult for programmers to support different architectures [...]

      I am, and it's not. Unless you move to really exotic architectures with 16-bit chars or ints or something, or if your code sucks, or if it's written in assembler. The odd bug might turn up, but nothing out of the ordinary. Moving between big- and little-endian would add a bit to the risk.

      If you write in higher-level languages than C (like Perl or Python) chances something goes wrong are really slim.

    10. Re:YES! by nine-times · · Score: 1

      The only reason for Linux and *BSD to run on so many architectures (compared to running on, say, the most used 5 o 10) is the geekness factor.

      Not really. I don't know which architectures you have in mind, but a large part of the reason it runs on so many architectures is because people want to use Linux on those architectures. Linux gets used all over the place, even in embedded systems.

    11. Re:YES! by jimicus · · Score: 1

      Maybe they'll do some arithmetic in 128 bits of precision but I doubt the address space will be 128 bits.

      2^64 is a big number. In bytes, it's 16 exabytes. Even 2^40 (the useable address space in a current 64-bit CPU), works out at a terabyte.

    12. Re:YES! by Chris+Burke · · Score: 2, Insightful

      You think the hardware vendors are waiting around? They are already dreaming of 128-bit CPU's.

      Well I see what you're getting at (hardware vendors wanting to sell upgrades), but no, they aren't dreaming of 128-bit cpus. Because 64 bits is really going to be enough for a long time. 2^64 is huge.

      Previous jumps made a lot more sense. 4 to 8 to 16 was automatic, as soon as transistor budgets was high enough it made sense to do it. 16 bits wasn't ever sufficient, either -- 64k isn't even a very long text file, and PCs had ten times that much ram already that needed to be addressed through segments. 32 bits gives you 4GB of address space, which is starting to get pretty reasonable, and was more than sufficient for quite a while, but also not ridiculously huge. Servers bumped up against it first, but when AMD released the Opteron even my not-too-expensive home desktop had 2GB of RAM. Intel may have been right that desktops didn't exactly need 64-bit, but overal the time was ripe to change.

      The thing is, though, that while Moore's Law is exponential, increasing bits is super-exponential, as in 2^2^N. So every time we double the number of address bits, we double the number of generations it takes for memory densities to catch up. 32-bit can address 64,000 times more than a 16 bit machine. 64-bit machines can address 4 billion times more memory than 32-bit.

      So it's going to be a while -- at least twenty years even if the exponential growth in memory capacity continues unabated -- before there's any point to even considering 128-bit addressing. Yes, hardware vendors may like to promote upgrades, but it's easy enough to do so just by offering more performance/lower power/whatever other features. Adding bits means adding cost in datapaths, in pins, and in having to convince software vendors to re-write so there's any point in having those extra bits and datapaths in the first place, and if none of the software people want those bits they won't buy in and then it's just wasted.

      Oh, and if/when we do ever switch to 128-bit addressing, which I'm predicting won't be for another 2 decades at least, then we will never switch to 256-bit addressing, at least not until we leave the Milky Way and are no longer satisfied by being able to address every particle in a single galaxy uniquely.

      --

      The enemies of Democracy are
    13. Re:YES! by Undertaker43017 · · Score: 1

      Sorry, it would seem by the responses (and the mods) that my sarcasm didn't come through very well...

    14. Re:YES! by syousef · · Score: 1

      As a programmer I've been waiting for this. I was actually disappointed that Vista would support 32-bit CPUs

      You know those end users who keep calling you a propeller-head and space cadet and generally tease or ridicule you? This is why. They just want their stuff to work and not to have to re-learn things every 5 mins.

      --
      These posts express my own personal views, not those of my employer
    15. Re:YES! by Quantam · · Score: 1

      Waaugh! Cry some more. It's been 22 years since the 32-bit x86 (the 386) came out, and the 16-bit to 32-bit transition was actually much harder than this 32-bit to 64-bit transition (I actually did some 16-bit DOS programming). Or, if you prefer, 11 years or so since Windows 95 came out.

      Now run home to mommy. The adults are talking, here. Oh, and while you're leaving, take your crappy admin-required programs with you.

      --
      You have tried to support your argument with faulty reasoning! Go directly to jail; do not pass Go, do not collect $200!
    16. Re:YES! by Quantam · · Score: 1

      "Apple manages to support 32-bit and 64-bit architectures for both PPC and Intel. Linux supports *tons* of different architectures. Why is it that it's a particular stumbling block for Microsoft and Microsoft developers?"

      Such a change requires the program be recompiled (assuming the code itself doesn't prevent use of 64-bit pointers for one reason or another). A moment of critical thought would reveal the answer for Linux. As for Apple, I'd bet money that it's related to the fact that there are almost two orders of magnitude more users of MS systems (Windows now, but DOS in the past) than of Macs, as well as the number of programs available and I'd bet the number of essential systems (I'm thinking of things like accounting or custom business software that runs on office computers). And from what I hear from my Mac programmer friend, they seem to have more influence over their coders in general.

      "if it's too difficult for programmers to support different architectures, the solution isn't to restrict supported architectures, but rather to improve the ability to develop across multiple architectures."

      It's funny you should mention that, as I write a little unofficially open-source (I haven't got around to officially releasing it with a formal license yet) Windows/POSIX cross-platform library of things that are typically very difficult to port (things like multi-core programming, asynchronous I/O, cross-architecture communication, etc.). Yet I doubt even my library will get most people to write portable code. And portability is just one of the major things people don't know how to do; add things like multithreading (the kind that allows your program to take full advantage of multiple cores; actually, myself and a friend are currently working on setting up a parallel programming class at his university), not require admin (mainly applies to sucky Windows programs), etc. I'm pushing for all of these, but I doubt I'll be able to change the world.

      "Ideally you should be able to develop a program once and have it run on any architecture and on any OS with minimal changes."

      It's not difficult like writing a game for the Cell (shudder), but it is a bit tricky. It's very common to store bit flags in a pointer because they're unused. Between converting the pointer to an integer to do bit manipulation and back, and the way programs (like Blizzard games) like to use the high bit, there's a lot of code that won't work right without being fixed. Even worse, people will usually typecast the pointer to an integer with a fixed size (the size on the processor they're writing for), which isn't forward compatible. Now, moving to 32 bits from 16 bits was a whole different ballgame (as pointers worked fundamentally differently, not just larger); such conversions were a huge pain for programs larger than 64 KB.

      "If you don't agree, consider that the Intel x86-64bit processors probably won't be around forever. What happens the next time Microsoft decides to change their preferred platform. Do all the old platforms just become obsolete? Shouldn't they be working towards making these sorts of transitions seamless."

      Haha, we can only hope; x86 is a pretty icky architecture (though that's not likely to ever become dominant, I personally am a big fan of the MIPS architecture; there's a reason it's so commonly used in teaching assembly classes - it has an incredibly nice instruction set and architecture). But that's what they said 10-20 years ago. At the rate things are going, there's no guarantee that Windows will move off of x86 before MS goes out of business (which is equally uncertain). In either case, they've really made the 32-bit to 64-bit transition as seamless as theoretically possible, short of a full, buggy emulator (the Mac approach).

      --
      You have tried to support your argument with faulty reasoning! Go directly to jail; do not pass Go, do not collect $200!
    17. Re:YES! by syousef · · Score: 1

      Such maturity you display. Anyone who makes arguments that include crying onomatopoeia and tells their opponent to "run home to mommy" has some serious issues. How do you expect anyone to take you seriously acting like such a 3 year old ass clown?

      Software shouldn't be replaced just because it's old. It should be replaced when something offers the users an advantage.

      Idiot.

      --
      These posts express my own personal views, not those of my employer
    18. Re:YES! by Quantam · · Score: 1

      Mmm. Miss the entire point of the post, reply to something else, declare self winner and call other person an idiot, profit! Excellent debating strategy you have, there; bet you get a lot of satisfaction from it. Let me spell it out very carefully: we are in one of the most rapidly changing industries in the most productive period ever in history. Here, 22 years is an eternity. Anyone who complains about having to learn one new thing in this industry in 22 years is, as I pointed out, a total and complete crybaby (not to mention roadkill in the labor market). In fact, just that x86 has been the dominant chip for as long as it has is astounding.

      As for offering an advantage, I totally agree. Unfortunately, you appear to have absolutely no idea what kind of advantages are on the market here, or you wouldn't have been able to come to the faulty conclusion that I advocate doing totally random things. And given your aversion to learning, I suspect it'd be far more productive to do work (or heck, even play World of Warcraft) than to try to explain it to you.

      Do you work at McDonalds, by any chance? No wait, that was a stupid question. Obviously not, as you'd have to learn a new recipe every couple of years, if you did. Now excuse me while I (or perhaps I should say "we", as there are many, MANY of us) go maintain the status quo of light-speed progress while your brain shrivels up and dies in your learning deprivation chamber.

      --
      You have tried to support your argument with faulty reasoning! Go directly to jail; do not pass Go, do not collect $200!
    19. Re:YES! by syousef · · Score: 1

      The old Profit!!! joke? You've lost the credibility to so much as attempt to attack my debating style because clearly you're about 12 and living in your parents basement.

      22 years is an eternity? You must be young and dumb. I've worked on systems that have run for 15 years - before i was even in computing professionally - they show no sign of quitting and are constantly evolving, and I make good living servicing them.

      The rest of your deluge of "quips" are neither funny nor deserve any kind of reply. You don't actually have a point, it's just an incoherent rant about how shit you think I am. Get a life and get a clue dude.

      --
      These posts express my own personal views, not those of my employer
    20. Re:YES! by Quantam · · Score: 1

      "22 years is an eternity? You must be young and dumb. I've worked on systems that have run for 15 years - before i was even in computing professionally - they show no sign of quitting and are constantly evolving, and I make good living servicing them."

      I get the feeling you've given up on saying anything you actually believe, because the only way to keep fighting at this point is to make stuff up as you go. I notice you've not responded to any of my points from the very beginning, but rather reiterated your assertion that I'm wrong without proof, and mixed in varying insults in the process. In fact, the only fact you've stated in all of your three posts (assuming it's true) is that you work on old systems. Do you really expect to win a debate like that? But I guess when you're as special as you are, making arguments (which, by definition, involves evidence and reason) is beneath you.

      Normally, right here I'd give you a lengthy tour of the technological progress of the last 22 years, containing dozens of specific examples. But frankly, as you've not actually made any attempt to refute any of my previous points, I'd have to be remarkably stupid to spend any effort making further points. So, I shall write one very brief and narrow paragraph on the x86 clock speed, as an example of what would be here, were I to actually spend the effort to write this section.

      In the last 22 years, the x86 has increased from a clock speed of 16 Mhz to 2.9 Ghz: an increase of 183 times. This number is extremely misleading, however, as the 386 was single-core, single-cycle, single-ALU, with strong instruction ordering; new CPUs now have up to 4 cores, multiple instructions are executed concurrently on each core out of order, and with SIMD instructions allowing multiple values to be calculated per instruction. Of course this is still misleading, as the number of cycles per instruction has decreased dramatically. For example, the 386 could perform approximately 421 thousand 32-bit integer multiplications per second, while the Core 2 quad can perform almost 12 billion of the same - a speedup of 28,000 times.

      Now, are you QUITE done fighting a losing battle and looking like an idiot in the process? Simply being loud and insulting is not enough to win a debate with someone who actually knows what they are talking about.

      --
      You have tried to support your argument with faulty reasoning! Go directly to jail; do not pass Go, do not collect $200!
    21. Re:YES! by syousef · · Score: 1

      I get the feeling you're an asshole who refuses to believe anything that is true. I'm working on a system that's been running since '91. We're adding a new J2EE front end with the latest Spring frameworks, Hibernate etc. The core code for the business engine is C on VMS. It's not going to be replaced for some time because it's rock solid and performs as it should. Both front and back ends continue to make use of the increases in speed/processing power your mention.

      You know what you can do with your childish rant about throwing everything away and starting again every few years. You obviously wouldn't know an enterprise system if it bit you on the arse.

      --
      These posts express my own personal views, not those of my employer
    22. Re:YES! by Quantam · · Score: 1

      Well, I should congratulate you. In one post you've managed to provide some real (and interesting) information, and at the same time refute your entire argument (I can only hypothesize that that was the whole reason it took you so long to spit it out). It sounds like you've done a fine job (I'm giving you the benefit of the doubt, here) of updating that system with much more modern technology which didn't even exist when the machine was brought into service. That must have been a lot of work, and required learning many things to accomplish. Now what were you saying about having to learn one new thing in 22 years being for propeller-heads (that's referring to the bleeding edge, right? I'm afraid I'm not familiar with that term or "space cadet", or other such insults, and can only guess the meaning based on context)?

      Again you've managed to completely misunderstand every single one of my posts, and compensate by throwing random insults. I have never advocated wholesale replacement of an entire system. I have, from the very first post (in which it was explicitly stated, a fact which obviously went so far over your head that it got hijacked and flown into a major landmark) advocated an incremental improvement in existing programs to take advantage of newer, better hardware, and reduce the complexity and cost of both hardware and software (have you ever taken a hardware design course? how about an operating systems concepts class?). Apparently you're not just making your own stuff up as you go along, but you're also making up "my" stuff as you go along.

      --
      You have tried to support your argument with faulty reasoning! Go directly to jail; do not pass Go, do not collect $200!
    23. Re:YES! by syousef · · Score: 1

      You really are a joke. What special school debating team did you escape from? You start your reply to my post with "Waaugh! Cry some more" and call me a child then complain about my insults? What are you smoking?

      My entire point: Backward compatibility is important and old software shouldn't (and sometimes can't!) be thrown away.

      --
      These posts express my own personal views, not those of my employer
  26. Huh? by bakes · · Score: 5, Insightful

    Microsoft themselves still don't support 64-bit yet. I installed the 64-bit version of SQL Server 2005 only to find it doesn't support 64-bit for SQL Mail and SSIS - you have to run the 32-bit versions of them under WoW64. Someone else has already mentioned drivers. If Microsoft can't or won't support their own software under 64 bit environments, they are going to have a heck of a time convincing developers to push everything over.

    I fear there will be a loooooooong transition time - just as well they gave everyone an early warning.

    --
    Ho! Haha! Guard! Turn! Parry! Dodge! Spin! Ha! Thrust!
    1. Re:Huh? by Control+Group · · Score: 1

      Er...what?

      I run several SQL 2005 instances, one of them a 2-node cluster of SQL 2005 SP1 64-bit on Windows 2003 R2 SP2 64-bit, and I don't have this problem. SSIS works just fine. I don't use SQL Mail, so I can't speak to it, but unless SQL Server set up and is running WoW64 without telling me (which, I admit, isn't impossible), SSIS works just dandy in 64-bit land.

      --

      Reality has a conservative bias: it conserves mass, energy, momentum...
    2. Re:Huh? by cbreaker · · Score: 1

      WoW isn't really that big of a deal, you know.

      The code still runs native on X86-64 CPU's; it's just that a few extra DLL's have to be loaded. In real world performance, often times running apps in WoW is faster then running the whole OS is 32-bit land, depending on the application. Some 32-bit games, for instance, benefit from having 64-bit drivers for video and disk access, and I'd imagine that a heavy app like SQL benefits even more if you have more then 3 GB RAM.

      Your argument is really kinda weak. WoW is a great function of Windows, it's just too bad MORE things don't work under it. Most applications do run great, though.

      --
      - It's not the Macs I hate. It's Digg users. -
    3. Re:Huh? by Anonymous Coward · · Score: 0

      World of Warcraft?! When did that go 64-bit?

    4. Re:Huh? by bakes · · Score: 1

      Your argument is really kinda weak. WoW is a great function of Windows, I wasn't complaining about WoW specifically, more that the application is not supported natively in 64-bit mode. Particularly for one of their flagship server environments.
      --
      Ho! Haha! Guard! Turn! Parry! Dodge! Spin! Ha! Thrust!
    5. Re:Huh? by cbreaker · · Score: 1

      Do you really need 64-bit "native" code on the e-mail function of SQL server? (note the quotes around Native; 32-bit code runs native too.)

      To me, I think I'd rather use more stable, proven code, even if it IS running under WoW. I'm guessing they would have gone with all 64-bit native tools if the code was ready, but it wasn't, so you can use the 32-bit code until such time as it is. Because WoW is fairly low overhead and the code runs natively on the CPU, it's a fairly good trade-off.

      I just don't think the argument is valid. The important pieces run on 64-bit compiled executables, and the rest still runs natively (albeit after loading a few more libraries.)

      --
      - It's not the Macs I hate. It's Digg users. -
  27. Does this mean they're dumping Windows Mobile? by sethawoolley · · Score: 1

    64-bit will be overkill on embedded systems for a long time coming...

    Thank Saint IGNUcious I won't have to deal with that monstrosity in the future.

  28. What? by MontyApollo · · Score: 1
    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run.

    So...everybody on slashdot proclaims that Vista sucks so bad that it is the final nail in Microsoft's coffin...yet they are not happy that Windows will be discontinuing 32 bit support in 5 to 10 years???

  29. What's the big deal? by east+coast · · Score: 1

    By the time the next version of Windows comes around people who currently own P4s and Core Duos aren't going to be worried about upgrading the OS on their existing machines.

    Not to mention that it's all too common for software/hardware manufacturers to make these grandiose kinds of statements only to retract it at a later date. I've never seen the axe fall on such a standard without at least a few false announcements of abandonment. For example: I was told 2-3 years ago that both ATI and nVidia were both going to drop their AGP cards after the current (X800 era) versions. Way to go PCI-E!

    --
    Dedicated Cthulhu Cultist since 4523 BC.
    1. Re:What's the big deal? by profplump · · Score: 1

      Part of the reason they make announcements like this is to let other vendors in on their plans: MS would probably prefer to stop releasing a 32-bit OS and programs, but they need (at least the big) PC makers to stop selling 32-bit systems before that can happen. Similarly PC makers don't want to move to the (at least for now) more expensive 64-bit systems if MS is still offering up-to-date products for their more profitable 32-bit systems.

      It's the same deal with ATI -- they'd love to only make one card type, and as soon as they see AGP sales drop off I'm sure they will. But that can't happen until PCIe has been the standard video slot on motherboards for at least a few years. So they announce their intent long before they're prepared to act, in the hopes of encouraging other people to move with them, thereby mitigating the chicken/egg problem.

  30. About Damn Time by shoptroll · · Score: 1

    This has been long overdue. From what I've read there's a lot more security enhancements in Vista 64-bit than 32-bit. I would like to move over to a 64-Bit windows platform, but the last time I tried it with XP, all my hardware was able to work with it except for Palm who insists on 32-bit drivers. Not sure about iPods either. Palm was higher on the stuff-that-must-work priority list than my iPod at the time.

    This also should allow Microsoft to cut back on the size of windows since they, at least in my mind, ought to be able to cut out a good portion of their legacy hardware support (things like the ISA bus and stuff which should not be found on (I hope) 64-bit processor motherboards). Although this will be a very scary version to be running for the first couple of months as hardware manufacturers are dragged kicking and screaming into 64-bit land. Same with software authors. UAC was just a test run ;) Hopefully, they will really just gut the entire OS and start from the ground up this time. Windows has needed a clean break from its history for a long time in my book.

    --
    Insert Sig Here
    1. Re:About Damn Time by sys_mast · · Score: 1

      Call me crazy, but I thought that ISA support was removed from Windows with XP?

      OK, a quick Google search comes up with ISA NON-plug/pray support is removed, so that is a portion of ISA products.

      see articles like this for reference http://www.windowsnetworking.com/articles_tutorial s/wxpisanc.html

      So, it seems like this is a continuation of what XP did, do any new motherboards have ISA anymore? it's been a long time since I've seen one, and I can't think of any ISA card worth running today...

      --
      Those who can, do.
  31. Indeed... by Cadallin · · Score: 1
    So judging by the trends in Microsoft's development cycles, we'll see this Vista replacement somewhere around 2018 then? Pardon me while I burst into panic. By then computers might even be fast enough to give acceptable performance with Vista! I kid, I kid.

    But seriously, I think this is probably the least of any Mac users worries. Generally, Bootcamp is used for backwards rather than forwards compatibility. The forward compatibility is Mac OS. Windows is for legacy apps.

  32. It really makes no difference by postbigbang · · Score: 3, Insightful

    when you consider that it took many more years for Vista than was planned; the next Windows release ought to come about retirement age for most of us.

    That and as Microsoft seems to feel that your next PC will be a cell/mobile phone, I'm waiting for the advent of the 64-bit mobile phone processor. Imagine its 128-bit predecessor. You'll be able to address every bit in the known universe with the memory map on *that* one.

    Or, perhaps 'legacy' hardware will get some much needed added life, by utilizing ultra-fast 32-bit processors that just do work far faster than their 64-bit equivalents-simply because code maturity will force opmitizations.

    --
    ---- Teach Peace. It's Cheaper Than War.
    1. Re:It really makes no difference by Kuvter · · Score: 1

      64-bit mobile ought to be enough for anybody.

      --
      "To be is to do." --Socrates
      "To do is to be." -- Aristotle
      "Do-Be-Do-Be-Do..." --Sinatra
    2. Re:It really makes no difference by Anonymous Coward · · Score: 0

      Imagine its 128-bit predecessor.
      Just a quick note from your local AC - you meant "successor", not "predecessor".
    3. Re:It really makes no difference by Undertaker43017 · · Score: 1

      I'm still pretty happy with 640K of memory, I am having trouble getting this "Windows" program to load though...

    4. Re:It really makes no difference by ichigo+2.0 · · Score: 1

      You'll be able to address every bit in the known universe with the memory map on *that* one.

      There is at least 10^80 atoms in the observable universe, so you would need a 266-bit processor to address it. Go with a 512-bit processor and your rig should be future proof in addition to being able to run DNF.

    5. Re:It really makes no difference by postbigbang · · Score: 1

      Hmmm. Leptons.... other charmed particles. Perhaps we need a kilobit processor. Windows 71 ought to work on that, eh?

      --
      ---- Teach Peace. It's Cheaper Than War.
  33. In many ways, this is a good idea for Microsoft! by Theovon · · Score: 1

    A large part of Microsoft's inability to modernize many aspects of Windows has been their need to retain backward compatibility with all sorts of crappy old software that did all sort of bad things that would break when the OS was recompiled. While it sucks for people with 32-bit machines, this is an opportunity for Microsoft to stop diverting resources to making old junk work and dedicate those resources to making actual improvements to the OS.

    They have to do it this way. Apple doesn't have this problem because they made a clean break in 2000 with OSX. With OSX, they could start over with new APIs and a whole new way of doing things that shed a lot of the crud from the past. As long as Microsoft supports 32-bit and 16-bit Windows code, they're going to be held back. Ditching 32-bit processors is a forcing function that they can use to draw a line in the sand for all of the users. They'll surely still run Win32 code, but users won't have an expectation that all old stuff will work problem-free.

    Microsoft is rightly bitched at for a lot of things that they do wrong. But what's ironic is that whenever they've broken backward compatibility, they get bitched at for that moreso than any other vendor. Of course, with old Linux code, that's mostly a recompile, but Apple was really drastic in their moves from OS9 to OSX and from PPC to x86. Some people complained, but most people just accepted it.

  34. Mac Owners by whisper_jeff · · Score: 1

    "Owners of first-generation Intel Macs ... may not be so happy knowing that Vista will be the last Windows they will be able to run."

    But they will take solace in the fact that they can still run OSX which is better.

  35. I'm so delighted by CranberryKing · · Score: 1

    since I have an AMD64. But wait I also have a 32-bit sempron. I guess I'm not so happy. Oh drat! Who honestly gives a toss about a planned operating system years away running or not running on their current hardware. I have a recent mobo and I still wouldn't want to try running vista on it.

  36. Yes, because by Kelz · · Score: 1

    Hardware that was out when WinXP came out can run vista.

    1. Re:Yes, because by ceoyoyo · · Score: 1

      And hardware that was out when Vista came out is 64-bit so (at least as far as this announcement is concerned) will be able to run Vista's successor. That doesn't mean you'd WANT to.

  37. MS software engineering by nanosquid · · Score: 1

    Apparently, it's just too hard for Microsoft to do what Linux distributions have done for several years now: support 32 bit and 64 bit simultaneously.

    1. Re:MS software engineering by Anonymous Coward · · Score: 0

      Apparently, it's just too hard for Microsoft to do what Linux distributions have done for several years now: support 32 bit and 64 bit simultaneously. Ummm, that's what they do at the moment, so you can hardly argue that it's 'too hard' for them...
    2. Re:MS software engineering by Anonymous Coward · · Score: 0

      Oh, I can very much argue that. Of course, they "can" produce two versions. But Microsoft is a huge company with huge resources and they can't do what Linux has done for years? Either they are discontinuing the 32bit version because they want to screw their users, or it's just too costly and hard for them to do it. Take your pick.

  38. My Core 2 Duo iMac... by bpprice · · Score: 1

    ... won't be bothered with Vista or even XP anytime soon, 64-bit or not. I have enough of that junk to deal with at work, and home I don't need one bit of it. If there was even one Windows application that truly mattered to me, perhaps - but there ain't. It is difficult to imagine why I would ever bother with a dual boot setup in order to get real things accomplished. That's just sad. It is true that I don't play games on computers, and if I did I might want Windows for that (at least for the next couple of years until Windows is less common) - but there are plenty of other things to do in my life right now. I barely have time for all the people and projects in my First Life, and so there is no Second Life!

  39. Smart planning, given their usual delays... by nick_davison · · Score: 1

    Sure, we scoff now.

    You forget, Vista was originally announced when 8 bit CPUs were common. It was only delay after delay that held them up until 32 bit CPUs were the low end and 64 bit ones were pretty common.

    In 2088, when they finally ship their new version, we'll likely all be running megabit CPUs. We still won't have our long promised flying cars however. This of course assumes Moore's law - which will still have regular discussions on Slashdot about how it's reached its limits.

  40. Hardware will not like windows too by Anonymous Coward · · Score: 0

    Well I don't expect any future windows to run at decent speed in the latest hardware either. :D

  41. Tainted by MrPerfekt · · Score: 1

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run.

    Call me crazy, but I didn't buy my Mac to run Windows. So I won't be "not so happy". Thanks for speculating though!

    --
    I just wasted your mod points! HA!
  42. Will it matter? by palladiate · · Score: 1

    In the 6-8 following years of Vista, wouldn't a entry level 64-bit cpu that's faster and more efficient than your old machine cost a rather small amount? Is this important?

    My bigger worry is if Microsoft can create a 64-bit OS that functionally operates on my Core2. That's the day I'm waiting for. I'm tired of not having any functionality of my custom box when running XP64 or Vista64- no ATI or Nvidia drivers that work without kernel panics, no sound drivers that work with my Realtek on DVDs, randomly scorched Raid 0 with an Intel controller. I should say, that the 64-bit Linux kernel works fine, and I can do most everything but watch YouTube in Ubuntu running at 64-bit

    Fixing that will be much harder than creating very affordable new cpus. Seriously, does anyone expect their computers to run the latest Microsoft junk in 6 years?

    1. Re:Will it matter? by RockoTDF · · Score: 1

      www.getautomatix.com
      Will solve all your 64 bit codec and flash related woes.

      --
      There is more to science than physics!

      www.iomalfunction.blogspot.com
  43. No by buddha42 · · Score: 1

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run."
    No, I'm pretty sure they won't give the slightest crap whatsoever.
  44. How long to roll out 46 bit only? by foniksonik · · Score: 1

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run.


    So what, we'll need to upgrade our machines in 6 years or so? That's well within the typical Mac lifecycle... though just barely. Unlike standard PCs Macs are typically used for ~5 years before being upgraded. The OS just keeps getting better and faster so the older machines actually work better than when they were introduced... Linux seems close to this, though only if you limit your media options.

    --
    A fool throws a stone into a well and a thousand sages can not remove it.
  45. Old versions forever! by Ngarrang · · Score: 1

    This is certainly good news for Win95 and Win98 users. For a minute there, they thought they were going to have to upgrade, but with the future Windows OSes no longer competing for the 32-bit space, the market share for even Win2k should now become stable.

    --
    Bearded Dragon
  46. Re:In many ways, this is a good idea for Microsoft by shoptroll · · Score: 1

    If MS was smart, they'd provide some sort of virtualization functionality into the next OS that allows stragglers to run their old applications on the OS. However, hardware manufacturers *cough* PALM *cough* need to wake up and do something. This decision isn't exactly a big surprise. We've had 64-Bit XP since 2002-2003ish.

    --
    Insert Sig Here
  47. Sure... by Frosty+Piss · · Score: 1

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run."

    Is this really an issue? I mean, isn't XP Pro the last reasonably respectible OS Microsoft made? Why would they run Vista at all? Why would they want to?

    --
    If you want news from today, you have to come back tomorrow.
    1. Re:Sure... by SEMW · · Score: 4, Funny

      Is this really an issue? I mean, isn't XP Pro the last reasonably respectible OS Microsoft made? 2007

      Yes.

      2002

      What? Windows XP Pro is crap, bloated, and has ridiculous hardware requirements. Wasting system resources on a Fisher-price UI? No thanks! 2000 is the last reasonably respectible OS Microsoft has made.

      2000

      Windows 2000? I think not -- it requires 64MB of RAM for god's sake; and recommends 128MB! Who has that much RAM? Bloated piece of crap. 98 is the last reasonably respectible OS Microsoft has made.

      1996

      Windows 98? I think not! It barely does more than Windows 95 did, but have you seen how much bigger the sysreqs are due to bloated crap like active desktop and IE4? No, 95 is the last reasonably respectible OS Microsoft has made.

      1995

      No, Windows 95 is crap, bloated, and has ridiculous hardware requirements. Can you believe it needs a 32-bit CPU? What applications need 32-bit, anyway? None! Bigger isn't always better, you know; and that's certainly true for 32bit/16bit. 3.11 is the last reasonably respectible OS Microsoft has made.

      1992

      Windows 3.11? Crap, bloated, and has ridiculous hardware requirements. What use is a GUI, anyway? I can do things faster at the command line. Give me MS-DOS 5 and-day.

      1991

      MS-DOS 5? Crap, bloated, and has ridiculous hardware requirements. COMMAND.COM is over 47kB, can you believe it? I long for the good old days of 2.0 and 3.0.

      1983

      MS-DOS 2/3? Bah. Who needs the bloat? Give me something lean and mean like CP/M any say.

      1976

      CP/M? A general purpose operating system? Who needs it? Everyone knows it's more efficient to have different machines to do different tasks. Do one thing and do it well, I say.

      etc., etc.
      --
      What's purple and commutes? An Abelian grape.
    2. Re:Sure... by Monkey · · Score: 1

      Aww... you left out the one release of Windows where all the bitching and moaning was actually substantiated and nobody adopted it.

  48. This is good news... by bitRAKE · · Score: 1

    Windows has always bit off more than it could chew.

  49. BashDot by TopSpin · · Score: 1

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run. Question: Circa 2013* or so when a replacement for Vista actually appears, exactly how many "first-generation" Intel Mac operators that actually use their by-then 7 year old systems to run Microsoft operating systems will actually care?

    Answer: Both.

    Please. I wouldn't be surprised or disturbed to learn the latest version of OS X isn't be supported on 32 bit Macs by the time Microsoft replaces Vista. If history is any guide there is at least one processor architecture change-over in store for Apple between now and then.

    * Figuring XP-to-Vista development time as the lower bound for Vista's replacement.

    --
    Lurking at the bottom of the gravity well, getting old
  50. Hold on a minute by CyZooNiC · · Score: 0

    It would be nice if they would "fix" the current problems with windows XP x64 and Vista x64 before through all their eggs in the 64 bit basket. I've regretted the purchase of XP x64 and sure wish I would have gone with the 32 bit version since almost nothing works properly from drivers to software. Sure it's the fault of the 3rd party drivers and software but where is the backwards compatibility support? And if large manufactures like HP won't provide drivers for new printers they release who will? I still can't print on my HP2600n using XP x64!

  51. Stock up on old hardware by iminplaya · · Score: 1

    I would buy it by the truckload if I had the money. I don't know how long it could sit before it corrodes away, but it sure will come in handy to insure that at my neighbors could have an affordable machine over the next decade at least. I would advise also that people stop buying the latest new gadget every week. This all really stinks for those who normally have no need to upgrade when the old stuff is working perfectly fine. Got a ten year old MMX machine that works perfectly with win98 and office 97. And these people are trying to break it by making all the new formats incompatible. At the same time, I think I'll take up the fine art of dumpster diving and continue to help people break away from Microsoft. Come to think of it, this really shouldn't an issue anymore. The Microsoft stranglehold is an irrational illusion, now that we have a viable alternative. Just need CAD and some games to keep gen-pop happy.

    --
    What?
    1. Re:Stock up on old hardware by BlackSnake112 · · Score: 1

      I have a PII 266 with 512MB of ram that still runs great. Granted no 64 bit computing on it bit does run as my file server just fine. Since the mother board has 5 PCI slots I have 5 SATA cards in it. Lots of disk space using an old motherboard and cpu. IT takes a while to boot up when the power goes out, aside from that it is fine.

    2. Re:Stock up on old hardware by iminplaya · · Score: 1

      Agreed. I think the big problem will be simple "corrosion" for lack of a better word. One bad cap, and poof. Surface mount components are a bit tricky to install with a 100 watt soldering iron. The really good news will come with desktop replicators where we can simply "print out" new hardware. Then we shall truly be "free at last" from the tyranny of the current situation. This will finally put the means of production in the hands of the people and the chains will fall away. I'm very optimistic that we are close to achieving that goal. The negative possibility is that of the powers that be will make a great attempt to restrict access to such equipment. The cool thing is that once it's out, there will be no stopping it.

      --
      What?
  52. Step 1 by nurb432 · · Score: 1

    Step 2 will be to restrict booting unless the board has TPM enabled.

    --
    ---- Booth was a patriot ----
  53. In other news by Anonymous Coward · · Score: 0

    IPV4 addresses are obsolete, we'll get rid of them and adopt IPV6 by 2002.

  54. The real news here is... by Anonymous Coward · · Score: 0

    So you're saying that 5 years down the road, Microsoft isn't going to support Intel processors from 2 years ago. Maybe you haven't noticed the Vista system requirements, but the only newsworthy element of this story is that there's a 7-year delta to "unsupported" in there instead of the current 3-year delta.

  55. Microsoft To Dump 32-Bit After Vista? by digitalderbs · · Score: 1

    That's odd. I thought they already did that before Windows 95.

  56. Bad Thing? by TheNinjaroach · · Score: 1

    It might take 3 more years to get to SP2
    And giving system admins more time between applying Service Packs is a bad thing?
    --
    I went to eat some animal crackers and the box said, "Do not eat if seal is broken." I opened the box and sure enough..
  57. Sure it is the last one by sqlrob · · Score: 1

    And Windows 95 was the last 16/32 hybrid
    Oh no, Windows 98 will *really* be it.
    Whoops, Windows 98SE will be it!
    Windows ME will, we really mean it this time!

    1. Re:Sure it is the last one by default+luser · · Score: 1

      Windows 95 contained 16-bit code, but the OS required a 32-bit processor.

      This is as-opposed to Windows 3.x, which can run in real mode on a 16-bit processor, or in protected mode on a 32-bit processor.

      --

      Man is the animal that laughs.
      And occasionally whores for Karma.

    2. Re:Sure it is the last one by sqlrob · · Score: 1

      Correct, although major parts of it (the message loop, the GDI) were 16 bits and there was a global lock for running 16 bit code. Because of this, it was still way too easy for runaway apps to lock the machine.

      MS kept saying everything consumer would be true 32 bit RSN after the release of 95. It took until XP.

  58. Good! by default+luser · · Score: 4, Interesting

    The 4GB memory barrier is fast-aproaching for high-end users, and dealing with it is a MESS. Most motherboards don't support PAE (either due to lack of re-mappable PCI address space, or even lack of 36-bit address lines!), so we have a hard-limit of 2-3GB in the most popular version of Vista (32-bit). This is going to be a rough few years for game developers.

    I really don't see why Microsoft went 32-bit on this version anyway...I'd say over %80 of the potential upgrade platforms and over %95 of all shipping PCs today support x86-64 mode. But when you look back, history paves the way:

    Windows 386 = Windows 2.0 with 32-bit enhancements bolted-on. Equivilant of Windows XP 64
    Windows 3 = crossover version with support for 16-bit and 32-bit processors. Equivilant of Vista.
    Windows 95 = supports only 32-bit processors. Equivilant to the next revision of Windows.

    Too bad Microsoft didn't have the balls to jump the gun and make Vista 64-bit only.

    --

    Man is the animal that laughs.
    And occasionally whores for Karma.

    1. Re:Good! by Shados · · Score: 1

      Considering Vista 32 bit runs -almost- everything, and people cry like crazy about bad backward compatibility, can you imagine the rampage if they had dropped 32 bit? Microsoft employees would get burned on stakes in public places.

    2. Re:Good! by default+luser · · Score: 2, Interesting

      That's why they have WOW64 mode on their 64-bit operating systems. Tghe x86-64 platform was designed with full 32-bit compatibility in mind. This is why I was amazed MS didn't make Vista a core 64-bit OS - like the 386 (running 16-bit applications in 32-bit mode), it has support for running 32-bit applications in 64-bit mode.

      This provides excellent backward-compatibility for 32-bit apps, with all the benefits of a 64-bit OS and drivers. This allows you to unify development of applications and drivers to one platform, instead of splittiing it between Vista 32 and 64.

      Right now Vista 64 is the black sheep becausde all focus is on the 32-bit version.

      --

      Man is the animal that laughs.
      And occasionally whores for Karma.

    3. Re:Good! by Mr+Z · · Score: 1

      I don't think they're talking about dropping 32-bit app support. That would be suicide. They're just dropping the ability to boot the OS on 32-bit machines. x86-64 machines can run 32-bit binaries while in 64-bit mode. They just can't run 16-bit binaries.

      By the time Vista's successor comes out, 64-bit x86 processors will have been on the market about 10 years, I'm guessing. That's about the same length of time as we saw between the introduction of the 386 (1985) and Windows 95.

      --Joe
    4. Re:Good! by Shados · · Score: 1

      My understanding is, even with 32 bit app support, there are compatibility issues, like with games, drivers, etc, no?

    5. Re:Good! by The+Bungi · · Score: 1
      Too bad Microsoft didn't have the balls to jump the gun and make Vista 64-bit only.

      They need this final release cycle to get rid of all the 16-bit stuff still running out there on XP and 2000. Surprising amounts of people still run those types of apps, so now they have a few years' notice to upgrade or switch platforms. I was disappointed as well, but they have no choice.

    6. Re:Good! by SEMW · · Score: 1

      Unify development of drivers, yes; but there's a hell of a lot of hardware out there that manufacturers can't be bothered to continue to develop drivers for, but with 32-bit 2000/XP drivers that still kindof work on 32-bit Vista.

      --
      What's purple and commutes? An Abelian grape.
    7. Re:Good! by Sebastopol · · Score: 1

      Actually, 4GB was the 486 and P5 limit.

      In 1995 the Pentium Pro introduced 36-bit addressing and combined with windows PAE at the time, could address 64 gibibytes (yes, "gibibytes") of memory.

      wiki it.

      --
      https://www.accountkiller.com/removal-requested
    8. Re:Good! by mczak · · Score: 1

      I really don't see why Microsoft went 32-bit on this version anyway...I'd say over %80 of the potential upgrade platforms and over %95 of all shipping PCs today support x86-64 mode I think this number might be a bit overestimated. There are still lots of notebooks sold with core duo (or pre-merom celeron M), though yes on the desktop you'd have trouble finding a pc without x86-64.
    9. Re:Good! by default+luser · · Score: 1

      In 1995 the Pentium Pro introduced 36-bit addressing and combined with windows PAE at the time, could address 64 gibibytes (yes, "gibibytes") of memory.

      Do you make a habit out of reading the first sentence of a post and then commenting on it with a smart response?

      The second sentence of my post, for your reference:

      Most motherboards don't support PAE (either due to lack of re-mappable PCI address space, or even lack of 36-bit address lines!), so we have a hard-limit of 2-3GB in the most popular version of Vista (32-bit).

      PAE is not some magic bullet. Support is required in three places: OS, chipset and motherboard itself.

      Vista supports PAE just fine, so that's not a problem. The problem lies in the hardware:

      Most consumer motherboard chipsets do not support the remapping of memory-mapped I/O space required to support PAE. Even then, some motherboards omit the extra 4 bits of address lines as a cost savings feature. You usually have to trade-up to server boards to get these types of features, and even some of those fall short.

      While the limitations of 32-bit Vista may spark a renewed interest in motherboards having proper PAE support, it's too little, too late. I also consider PAE a pretty crappy band-aid for a problem that already has a solution (Vista 64). This was the focus of my original post: we could have avoided this whole memory mess if Vista were purely flat 64-bit.

      --

      Man is the animal that laughs.
      And occasionally whores for Karma.

    10. Re:Good! by default+luser · · Score: 1

      I think this number might be a bit overestimated. There are still lots of notebooks sold with core duo (or pre-merom celeron M), though yes on the desktop you'd have trouble finding a pc without x86-64.

      Think so, eh? Yeah, I pulled those numbers out of my ass, based on the general trend to replace Core Duo models with Core 2 Duo models. I figured the only places still selling Core Duos and Pentium Ms were selling closeout models (with the exception of embedded shops). Unfortunately, there's no easy way to get sales numbers for a single procesor model.

      Intel essentially threw a wrench in the 64-bit machine when they announced that the Core Duo was 32-bit. I think Microsoft would have a lot more solid ground to stand on regarding a 64-bit-only Vista if Intel hadn't dragged their feet so long on the Pentium M, and then released that stopgap.

      --

      Man is the animal that laughs.
      And occasionally whores for Karma.

    11. Re:Good! by Anonymous Coward · · Score: 0

      A mess? Rough years for games developers? Seems someone forgot the times of 64k paragraph-shifted interposed segments... Do I have to add the "operating system" environment that had to be handled?

  59. And will there be by Z00L00K · · Score: 1
    another Windows after Vista? If you see what M$ says Vista is the Ultimate OS...

    OK, we have heard that before...

    There is also the question about where the Linux bandwagon goes if Microsoft has the stamina to produce another major OS release after Vista. There have been arguments that Vista is the last of it's kind. From what I have recognized, Vista is a step forward from XP as NT was a step forward from W98. (ME doesn't count).

    --
    If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
  60. Irrelevant by Anonymous Coward · · Score: 0

    Did anyone seriously expect whatever follows Vista to run on ANY current hardware?

    This isn't a slam. But you would have to be blind not to realize that every new version of windows makes requirements that net out to you have to get a new machine.

    This has always been the case (since Windows 98 required a computer with a CDROM?)

    You could get away with upgrading a beefy NT box to 2000, or a beefy 2000 box to XP. I haven't heard of anyone upgrading a box from XP to Vista. The requirements of Vista are just too high for most XP boxes.

    Whatever follows Vista will have SEVERAL requirements that make reusing existing boxes (including most existing 64 bit boxes) impractical.

    1. Re:Irrelevant by BlackSnake112 · · Score: 1

      machines that we had to test vista on (we did get 128MB video cards):

      PIII 800 with 512 MB ram and 1gb RAM
      P4 1.8, 2.0, 2.4, 2.8 ghz machines with 512 MB, 1 GB , 2 GB RAM
      and few P4 with HT, and pent D 805,820,840,945 with 1GB and 2GB RAM
      no AMD cpus are in the old systems so I will leave them out of this.

      final result:

      The PIII machines could run vista with all the eye candy turned off. Do this to people you really like to annoy. It was better but still painful for the single threaded p4 machines. More RAM helped but it still was slow. The P4 with HT and the dual core machines did run vista best. The ram amount should be 2 GB not 1 GB. Dual core (or the HT procs) do not spike the CPU when you start up applications. The single threaded cpus get nailed when one starts up applications. I usually start up email, fire fox, opera, a few directory listings (each of my network drive mappings in separate explorer windows). Starting all of this kills the single threaded cpus. The dual core (or HT) cpus could do this without slowing down too much. I am not going to go near the compliers yet, still testing those.

      I cannot say as to how photoshop and it's cousins work, I do not use them. I am guessing that more horsepower == better.

      ** the AMD cpus that were tested were all AMD 64 based and they ran vista good. Again 2 GB ram was needed.

  61. Dear Boss, This is URGENT!! by Anonymous Coward · · Score: 0

    I know the Company had decided not to buy in to Vista because of the many issues with the test farm. But Vista is going to be the last OS that will run on our 32 bit infrastructure so I think we need to buy those 500 licenses NOW.

    Cordially,

    Eddy (your nephew)

  62. I suppose that's possible... but by anss123 · · Score: 5, Funny

    But running an emulator just for a quick game of Missile Command, Asteroids, Centipede, Battlezone, tempest, Tetris, etc, etc, is annoying.

    The other day I put Win 3.11 up against Windows Vista at Chess. Just to clarify I played Chess Titans up against Chess.exe from the Microsoft Entertainment pack, at expert level.

    With Vista being the newcomer Titan's got to play first. After about 30 seconds of thinking, Vista made it's _first_ move, in which chess.exe responded to immediately. From there a furious battle across the board started, with chess.exe taking more and more time to think along the way.

    After about a half an hour of playtime the game ended with Windows 3.11 crashing, In some sort of ironic twist, one move from checkmating.. Vista.

    Heh.

    Chess.exe might have had an advantage in that it is thinking on the opponents turn, but I'm still surprised Chess Titans was beat out by a fifteen year old program made for a computer a thousand times slower. Go Microsoft!

    1. Re:I suppose that's possible... but by Mr+Z · · Score: 1

      Hmmm... I wonder how it'd do against Intellivision Chess? :-)

    2. Re:I suppose that's possible... but by koreaman · · Score: 1

      Allowing chess.exe to think on its opponent term is actually a gigantic handicap in its favor. I'm not surprised it won.

    3. Re:I suppose that's possible... but by shaitand · · Score: 1

      'but I'm still surprised Chess Titans was beat out by a fifteen year old program made for a computer a thousand times slower. Go Microsoft!'

      I'm not surprised at all. Being made for a computer a thousand times slower means that it was made to operate more efficiently. You throw more beef at it and it just runs faster. 10 years ago the most efficient stuff being coded now would have been considered extremely bloated.

    4. Re:I suppose that's possible... but by shoptroll · · Score: 1

      Try the D-Fend front end. Works pretty well.

      --
      Insert Sig Here
    5. Re:I suppose that's possible... but by nostrad · · Score: 1

      Quick question: If that chess engine works so well and fast, why isn't it used in Vista (aside from it not being made by MS). Something must be seriously wrong if consumer market chess games has degraded that much. It'd be as if the AI in FPS:s got worse and worse over the years.

    6. Re:I suppose that's possible... but by Doctor+Faustus · · Score: 1

      Maybe because too many of us got frustrated losing every time on the easiest setting.

    7. Re:I suppose that's possible... but by shaitand · · Score: 1

      'If that chess engine works so well and fast, why isn't it used in Vista'

      Because it is 16 bit and the code probably won't even run on Vista. There are probably additional features and such in the new one and according to the GP the old one apparently crashes. Then as someone else already pointed out, people are tired of having computer chess opponents that slaughter the average player on the easiest setting.

      It isn't that things don't improve in general, it is just that programmers focus on the pace of development now and not efficiency. They use general purpose libraries, they add a couple CPU instructions with every function call and now programmers like to encapsulate every spec of code into a function. OO is even worse.

      Instead of coding the desired functionality as efficiently as possible, programmers typically implement the desired functionality as rapidly as possible. They still try to squash bugs, they still aim for stability, they just skip the efficiency factor in most applications.

      What difference do a couple extra instructions here and there make? A few extra branches in that general purpose library to discover what the correct code path in this application? Not much, until you realize that your computer is running numerous layers of code bloated in that manner. When everyone is doing things the same way now it adds up to billions of wasted cpu cycles, megs or even gigs of poorly utilized memory.

      Nobody (including me) wants to go all the way back to the old way of doing things. The fact is that the new way is much easier, even a 12 year old can be a programmer thanks to bloated shared libraries. It is also much faster. People say don't re-invent the wheel. I say that we aren't talking about the wheel, we are talking about something more like the internal combustion engine and you re-invent it if you want any hope of ever having a better internal combustion engine.

    8. Re:I suppose that's possible... but by syousef · · Score: 1

      I see this all the time. Unless you're playing very good chess it doesn't matter what the strongest engine is.

      --
      These posts express my own personal views, not those of my employer
  63. Affording MS an opportunity... by ElboRuum · · Score: 1

    ...to do something they should have done (but didn't) at one (any one) of the previous Windows releases:

    Shitcan the old code and start from scratch. At its heart, Win32 is dangerous and unsecured, an acceptable, if generally undesirable, answer to the needs of a more 'civilized' age.

    Backward compatibility is only desirable if doing so doesn't compromise forward progress or prevent the correction of certain unacceptable conditions (like swiss-cheese security). XP (at the barest minimum, I'd have argued Windows 2000) should have been a complete OS rewrite.

    Oh, big deal. So your freeware Solitaire game won't run on the new OS. If this is really that important to you, KEEP YOUR OLD BOX! No one said you had to throw the damn thing out, now did they?

    If MS is really shitting bricks about F/OSS, then the way forward is clear: dump the junk. This late in the game, however, to bring a brand spankin' new OS about might be a moot issue. Free alternatives would then effectively be "mature product".

    So, Bill? Given any thought to the next Age of Empires? Maybe MS should stick to writing apps FOR an OS, rather than the OS itself.

    1. Re:Affording MS an opportunity... by SEMW · · Score: 1

      ...to do something they should have done (but didn't) at one (any one) of the previous Windows releases: Shitcan the old code and start from scratch But they did do that, with Windows NT. NT 3.1 was written from the ground up, from scratch, as a completely 32-bit OS. Backwards compatibility with 16-bit apps was crap, but the architecture was good. And what happened? It took them over 8 years to persuade the market to switch over to it from the old architecture. They only acheived it in the end by devoting an entire Windows release (XP) to the task of retrofitting the NT kernel (i.e. Windows 2000) with a ton of emulation subsytems to let it run most Windows 9x/DOS apps. People care about backwards compatibility. And the biggest customers are the big businesses with their own custom business-specific software. If they can't run their apps on newer WIndows releases, they'll stick with the old one and eventually switch over to ReactOS or Wine. For Microsoft, dumping backwards compatibility would be equivalent to giving market share to Linux etc. on a platter.
      --
      What's purple and commutes? An Abelian grape.
  64. Find - Replace by narced · · Score: 1

    I'm wondering if the only change they are going to make is... Find - UInt32 Replace - UInt64 Compile... ship... PROFIT!

  65. Help me out here by Anonymous Coward · · Score: 0

    > Owners of first-generation Intel Macs that used (32-bit only) Core Duo
    > CPUs may not be so happy knowing that Vista will be the last Windows they
    > will be able to run.

    Is this some mindless dig at Mac users? Nobody that I see is bothering with Vista, least of all folk already running superior operating systems like OSX and linux.

  66. Buh Bye....... by Anonymous Coward · · Score: 0

    Seing how Windoze is becomming more and more of a bug laden, DRM ridden peice of crap,
    I won't be shedding any tears over this.

  67. Class Action? by KlomDark · · Score: 0, Flamebait

    I want to know what the deal is with all the computer companies selling 64-bit machine with 32-bit versions of Windows. Shouldn't that be illegal? Like buying a Lamborghini, but only half the cylinders have spark plugs in them.

  68. And? by 427_ci_505 · · Score: 1

    Most AMD processors (or maybe all now, I'm not too current) are 64bit capable. Intel has had EM64T for a while now. Mac users probably don't give a shift, and old 32-bit computers (they will be when the next Windows rolls around) are likely not going to be capable of running the OS anyways. From the point of writing software, drivers and the like, I would appreciate if someone could enlighten me as to how different/difficult/etc. it is to write or rewrite for 64bit instead of 32bit systems.

  69. Only mac users? by PadRacerExtreme · · Score: 1

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run.

    And window users not on Intel macs won't be upset by the same thing? Oh wait, I forgot where I was. Non-mac and non-linux people are not allowed to be upset by anything.....

    --
    Just remember - if the world didn't suck, we would all fall off.
  70. I'd Be More Angry... by Nom+du+Keyboard · · Score: 1
    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run.

    I'm more angry about being locked out of any 64-bit version of OS-X, than Vista. Given that that it takes MS 5 years at least to to come out with the next OS, my current Mac will be long gone before that.

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  71. What do we care? by HangingChad · · Score: 1

    Considering how long it took Microsoft to field Vista there's a good chance we'll all be dead by the time the next OS limps out the door.

    --
    That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
  72. as the owner of a first gen PPC mac.... by gumbi+west · · Score: 2, Informative

    I've got 10.4.9 running on a computer I bought in 2000, that makes it 7 years, not 2 for running the latest OS X. It is true though that there were 1998 computer that can not run OS X, and OS X was released in 2001--so that was a 3 year window. But at the time, 10.1 wasn't really ready for prime time, and OS 9 was still the main OS.

    1. Re:as the owner of a first gen PPC mac.... by Anonymous Coward · · Score: 0

      I've got 10.4.9 running on a computer I bought in 1996. Granted it's not officially supported (nor was OS X ever officially supported on that machine), but it works just fine. Powermac 7600 with a 900Mhz G3 FTW.

      I have nothing else to add, I just wanted to brag a bit.

    2. Re:as the owner of a first gen PPC mac.... by UnknownSoldier · · Score: 1

      OS 10.3.9 running on a PowerMac G3 333 MHz here.

      Works fine for email, web browsing, and Diablo2 muling. :-)

    3. Re:as the owner of a first gen PPC mac.... by raddan · · Score: 1

      That does beat me. I'm running 10.4.9 on a machine I bought in 1999. Granted, every single part except the mothboard has been replaced, so it's not exactly recognizable anymore (1.4 GHz G4, Lian-Li case, RAID 0, etc). As you can imagine, it's been a point of pride for me, so even though it sits next to a 2.5 GHz AM2, it still gets all of the work, and I've been very happy with it.

    4. Re:as the owner of a first gen PPC mac.... by Nimey · · Score: 2, Informative

      You don't have a first-gen PPC Mac unless it has a PowerPC 601 processor. *Maybe* a 603. Those would be from about 1994.

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    5. Re:as the owner of a first gen PPC mac.... by Anonymous Coward · · Score: 0

      You don't have a first get PPC, as others have stated, but you also don't have the oldest machine that 10.4 is officially supported on. I have it running on a B&W PowerMac G3 with a 350MHz processor. That machine was built in 1998. It worked fine when that machine had 256MB of RAM. I upgraded too 768MB because I could, but I didn't need to.

  73. What about Flash? by filesiteguy · · Score: 1

    Hmm.

    I wonder if they'll finally have a 64-bit version of flash I can run on my soon-to-be-standard 64-bit version of Vista...

    http://donutmonster.com/stuff/NoFlash.jpg

    Of course does this mean my 16-bit DOS apps will have to run in a virtual VDM?

    1. Re:What about Flash? by pandrijeczko · · Score: 1
      my 16-bit DOS apps

      Sssh! That word is the Microsoft equivalent of the "N" word, please take extreme care when using it.

      Mention *anything* about the command line and Ballmer starts on the furniture...

      --
      Gentoo Linux - another day, another USE flag.
  74. Mac users will be upset? by Anonymous Coward · · Score: 0

    "Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run."

    I'd probably be more concerned about the hundreds of millions of PC users that won't be able to run Vista on their current rig. Then again, the timeline for a Vista replacement is what -- never + 3 months?

  75. Just an excuse for more MS bloat. by pandrijeczko · · Score: 1
    It really would be nice to see a new Microsoft OS run fast and stable on the platforms of the day, rather than having to wait several years down the line when PCs have got faster, Service Packs have been applied & everyone has learnt all the tweaks & optimisations for the OS. For example, Windows XP came out in 2001 but it's only been in the time since SP2 that it's become (in my opinion at least) a stable and usable OS (after getting rid of the default kindergarten XP GUI anyway).

    When are Microsoft going to get it into their *THICK MONEY-GRABBING SKULLS* that one operating system topology cannot be all things to all men. This is one of the major reasons why Linux is giving them an ass-kicking at the moment (and long may it continue to do so) - you take a single kernel that can itself be configured in a myriad of monolithic or modular ways, then throw on just about any combination of GNU tools that you like, meaning you can embed it into a mobile phone or put it on a big Beowulf (hurrah!) server cluster. You can run a GUI or not run a GUI and if you run a GUI, you can run a big fat one like KDE or a small thin one like FVWM - whatever you like.

    This decision about supporting 64-bit only in future is *PURELY* about financial gain, nothing more. There will still be the endless layered bloat we are accustomed to that still ultimately drives your PC to a crawl, with (no doubt) the added instabilities of 32-bit software emulation as a poor attempt at providing backwards compatibility.

    --
    Gentoo Linux - another day, another USE flag.
  76. Sounds to me... by Guppy06 · · Score: 1

    ... that'll be at least another five years for the next version of Windows to come along, then. It'll take at least that long for hardware manufacturers to start writing 64-bit drivers consistently. I got a brand-new 64-bit laptop and it didn't even include the option of 64-bit Vista. Heck, Microsoft's own anti-virus offering doesn't even work in 64-bit.

    Windows 9x may not have liked it, but at least it could use 16-bit drivers.

  77. Why would I be unhappy? by moo083 · · Score: 1

    As the owner of a first gen intel mac, I don't understand what I'm supposed to be upset about. The next version of Windows probably won't be out until 2010 at the earliest, probably more like 2012. By that point, I will have a new machine. So I don't understand what the fuss is all about. In five years, even regular consumers will be ready for their next machine, except of course for the few hold outs and poor people, but they wouldn't upgrade their OS anyways. I think someone made an issue of something that is not there.

  78. Not dropping 32 bit software by Chris+Burke · · Score: 1

    I do not believe that Microsoft is dropping support for 32-bit applications from future operating systems; that would be foolish. The whole reason AMD64 took off as opposed to IA-64 is that it's backward compatible and supports running 32-bit applications within a 64-bit OS with no speed penalty. Compared to other things an OS does, supporting 32-bit apps within a 64-bit OS is easy.

    What they mean is that the OS itself will only run on a 64-bit capable processor. You will have to have a processor with the x86-64 extensions. That's all. Not a big deal, either, since it won't be long until all non-embedded processors sold by AMD and Intel are 64-bit capable. By the time the successor to Vista comes out certainly.

    Not related to your post, but the summary mentions how AMD should be "delighted". No, not really. AMD would have been ecstatic if a fully functional non-beta 64-bit Windows had been out 3-4 years ago when they had x86-64 and Intel did not. Instead they relied on Linux to help them sell based on 64-bit. Now, when both are selling 64-bit mainstream processors, it doesn't matter much. AMD/Intel processors will still have to support 32-bit operating systems into eternity, so they don't get anything out of MS dropping support.

    --

    The enemies of Democracy are
  79. They just added 3 more years to the devel cycle by gelfling · · Score: 1

    MS couldn't deliver most of what they originally intended for Vista, like a new FS, even by adding years to the development cycle and millions of dollars and over a year of effort to such critical items as the shutdown sound wav file.

    Now wouldn't we see a few things before they jettison 32 bit such as all these intended enhancements. To say nothing of the DRM uber alles that always lurks in the background. Oh and Zune 2, and buying another online service, and fixing patch management, and fixing security bugs, and trying to kill Google, Mac and Linux.

    Seems like chucking everything just to make money for Intel is awfully ambitious of them. They just added 3 more years to the development cycle for the next turn of the crank for an OS. With current cycles running 6 years, adding 3 more, even if they started today would give them a release date of Christmas 2015.

    But it's clear that Intel won't stand still for 9 more years so of course MS will release 64 bit 'enhanced enterprise' support in service packs. Which won't work right, won't install right, won't support many applications, will mess with security even more, and the millions of other unintended consequences that will happen.

    Clearly the reason that Redmond said that Vista will represent the 'last of its kind' vis a vis operating systems is that they are coming to terms with the fact that they can't get this work done anymore and the resulting product is such a massive clunky abortion that it's ungovernable. But it puts them in a tough place because Redmond doesn't have a good track record of starting from scratch.

    1. Re:They just added 3 more years to the devel cycle by Tim+Browse · · Score: 1

      They just added 3 more years to the development cycle for the next turn of the crank for an OS.

      Why? It's not like they don't have 64-bit versions of Vista already.

  80. I'm touched at your concern, but... by boyfaceddog · · Score: 1

    the next version of Windows could be five years away. I'm pretty sure people will have time to adjust. Still good news for everyone that MS is moving forward. Can't wait to see what they need to change.

    BTW - I am doing a little informal research on SD. I will now get myself modded down as Troll. Observe:

    MS SUCKS!

    (I don't really think MS sucks, but this IS science.)

    --
    Here will be an old abusing of God's patience and the king's English.
  81. Mac user -- don't really care. by Gribflex · · Score: 1

    "Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run."

    Vista is going to be around until at least 2010 as the flagship OS for MSFT. Likely later. It will still be usable for at least 2 years or after that. So I bought a new Intel based Mac in January 2007. This means that it will be at least three years before MSFT releases a new OS, and another two before I'm compelled to install it. 5 years is long enough for me to comfortably say 'this hardware is too old to support this new fangled OS.'

    Now, if they were dropping 32-bit support for Vista, that would be a concern.
    For Vista++, meh. I don't really care.

  82. Who cares by Anonymous Coward · · Score: 0

    I am the proud owner of a MacBook, and I could care less if my computer can't run the next Windows after Vista... when's that going to be released anyways, 2012? If I'm really worried at that point, I'll buy a new computer! The average consumer buys a new computer every 3 to 4 years anyways, so what's the point of the hype?

  83. no surprise by phrostie · · Score: 1

    this isn't that big of a deal.

    it's like when everyone moved from 286's to 386's or vaccume tubes to intigrated circuits.
    the 32bit processor will have nitch uses(lower power requirements and apps that just don't require the horsepower), but it's days are numbered.

    some day you all will tell your kids you remember 32bit processors and they will ask to go to the science museum to see them.

  84. Let me just be the first to say... by Anonymous Coward · · Score: 1, Informative

    "You'll be able to address every bit in the known universe with the memory map on *that* one." ...nobody will ever need to address more than every bit in the known universe.

  85. Like they'll be fast enough to run it otherwise... by iainl · · Score: 1

    Yes, I know that Vista took a lot longer to get here than it was supposed to. But really: if you bought your PC when XP came out in 2001, it would probably have had a Pentium 3 in it.

    Are you planning on upgrading that machine to run Vista?

    I thought not.

    --
    "I Know You Are But What Am I?"
  86. Oh well by openldev · · Score: 1

    By 2013, which will be how long it take Microsoft to make a new operating system, we will all have 64-bit processors anyway. Not that I really care anyway, since I use Linux ...

  87. MS 64bit == Non-Free Drivers by asphaltjesus · · Score: 2

    As has been mentioned before on /. Microsoft will require signed drivers on their 64 bit OS

    http://www.microsoft.com/whdc/system/platform/64bi t/kmsigning.mspx

    Implications of this are:

    1. Chilling effect to new devices.
    2. Sets the stage for tighter DRM handcuffs.

    From Microsoft's perspective these aren't bad things as they directly benefit Microsoft shareholders though, so I guess it's a wash.

    --
    Got Trader Joe's? friendwich.com RSS feeds work now!
    1. Re:MS 64bit == Non-Free Drivers by ls+-la · · Score: 0

      As has been mentioned before on /. Microsoft will require signed drivers on their 64 bit OS It won't be long after signing is required that Microsoft's private key is known.
  88. So in 8 years, it's all 64-bit? by mr_mischief · · Score: 1

    At the rate MS puts out "new" OSes, there's not going to be any 32-bit processors outside the embedded device realm. Hell, there may not be many 64-bit ones left, either.

  89. Well of course they're dropping 32-bit! by Abalamahalamatandra · · Score: 1

    Vista is such a bloated pig it barely fits on a 32-bit system (it only performs acceptably with 2G of memory), and we know by now that every new OS release from Microsoft is even more of a bloated pig than the one before.

    Consequently, anyone should be able to see that the next OS they release won't fit on a 32-bit system, much less have room for applications to run. This just makes good sense.

  90. In Related News... by kwilliam · · Score: 0

    Ubuntu and Dell released a joint statement announcing that their Linux based operating system will continue to be available in 32-bit form. A Dell executive said, "We expect to save a tremendous amount of money by using older processors in our consumer models, which will come dual booted with Ubuntu Zippy Zebra and Windows XP!"

  91. my "no expert" opinion by Chris+whatever · · Score: 1

    if Xp is still strong after almost 7 years, and vista more WindowME in terms of popularity, we should see another O.S. around 2010 or a revamped version of vista with more configurability or compatibility with software, so we are left with 3 years with 32 bit.

    I think even with 32 bit dead in the water, we'll have those computers around for a while, CPU speed aint increasing as fast as it was, maybe when they get a new technology we'll see 4 ghz up to 6 ghz sprouting for the comomn machine.

    "Dont kill me for the lack of insight, i'm no god of information and no i did not take a week of my life to support my comment by reading other stuff"

  92. Oh noes! by njfuzzy · · Score: 1

    Does anyone out there really expect a current/recent low end machine, made by anyone (not just Apple) to be able to run Windows Peppermint, or whatever they call it, when it comes out in 2014?

    --
    My Photography - http://ian-x.com
    The Deathlings (comic) - http://thedeathlings.com
  93. *Shrug* by Arkaic · · Score: 1

    I think I can scrape up enough money for a new 64 bit PC in the 5 to 8 years it will take to see a successor to Vista. Oh wait...I run linux at home.

  94. It's the 16-Bit apps that's keeping me 32-Bit by anss123 · · Score: 1

    However by 2014 (when the next MS OS gets out ;) I probably stopped caring about my beloved 16-Bit apps anyhow.

    But it still feels like progress for the sake of progress. I use several older applications because they have the feature I need, start up fast, and use memory in the single digit megabytes.

    Take PSP 4.12, for instance. The install directory take 6 MB total, and while running I can keep several images open without bothering my other memory hungry apps. PSP 9 running clean eats up more memory then PSP 4.12 consume in harddrive and memory totaled with several images opened.

    Hell, a simple text editor written in .net consume 10 Megabytes of memory and take more than a split second to start up. Hurray for progress.

    1. Re:It's the 16-Bit apps that's keeping me 32-Bit by 0123456 · · Score: 1

      "Hell, a simple text editor written in .net consume 10 Megabytes of memory and take more than a split second to start up. Hurray for progress."

      Yeah, but you try editing a 2^64 character text file in a 16-bit text editor :) !

  95. The sun is likely to be a cold, dark lump of coal by blueZ3 · · Score: 2, Funny

    by the time the successor to Vista comes out. I doubt very much anyone will care about it not running on ~20 billion-year-old hardware. Not even Mac users :-)

    --
    Interested in a Flash-based MAME front end? Visit mame.danzbb.com
  96. Thanks by palladiate · · Score: 1

    Thanks for the heads-up, but I broke down already and installed automatix when I couldn't get 32-bit Firefox to work with the flash plugin. Thanks for the help, though.

  97. Boo hoo. by Gryffin · · Score: 1

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run.

    The summary is right, all the people who own first-gen Intel Macs, and want to run Windows on them, are thoroughly heartbroken.

    All three of them.

    --
    Learn from the mistakes of others. You won't live long enough to make them all yourself.
  98. Re:Vista already threw out 16-bit by Anonymous Coward · · Score: 0

    So you won't be running 16-bit in Microsoft Panorama... Don't bet your last buck.

  99. Who Cares? by Anonymous Coward · · Score: 0

    I'm going to dump Windows after XP SP2 is no longer available!

    The only reason I use Windows is to play all the games that are only available to the Win32 platform. Why would I buy some new version of Windows that doesn't support the games I already have, and still love to play?

    (BF2, Wolfenstein, Starcraft, Warcraft, Company of Heroes, Counter Strike)

  100. The real question is: by Anonymous Coward · · Score: 0

    Will there be 64-bit drivers?

    1. Re:The real question is: by Monkey · · Score: 2, Interesting

      In order for a vendor to provide Microsoft approved "Certified for Vista" drivers, the company also has to release an x64 version of the driver.

  101. 64-bit is annoying because of its 32-bit ints by Anonymous Coward · · Score: 1, Interesting

    Let's hope that when 128-bit machines come out, gcc makes its ints have the same width as the pointer.

    The number of programs that break on compiling for 64-bit because of the retro 32-bit ints is just plain ridiculous. Sure, I agree, that's because they weren't written very well in the first place, but you can't expect to fix everyone's old programs when recompiling code to larger architectures. That doesn't scale.

    That was a *very* poor decision by gcc designers, and unnecessary. The "natural" size of an integer register on any given architecture (which is 64-bit on both Intel and AMD 64-bit architectures) should also be the size chosen for gcc's int.

    1. Re:64-bit is annoying because of its 32-bit ints by Anonymous Coward · · Score: 0

      That was a *very* poor decision by gcc designers, and unnecessary. The "natural" size of an integer register on any given architecture (which is 64-bit on both Intel and AMD 64-bit architectures) should also be the size chosen for gcc's int.

      That's a bad idea, a larger int means more data to transfer, when you really don't often need ints larger than 2 billion. Besides, the native word size on amd64 is 32 bits. You need an REX prefix to use 64 bits for most instructions.

      Besides, by the time we need 128 bits (after the sun has expanded to swallow the earth and we're all mourning it in our distant space colonies), most of these broken applications will have had to deal with the 64/32 bit problem.
  102. They think so. by twitter · · Score: 1

    Does this mean that MS are going to inflict another operating system on us in the near future?

    They think they are about to own a GNU operating system. Vista's a flop and shows how out of steam WinDOS really is.

    --

    Friends don't help friends install M$ junk.

  103. 32-bit Macs were a mistake anyway by Animats · · Score: 1

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs...

    That was a wierd decision on Apple's part, since they had a 64-bit PowerPC system when they forced their user base to go back to 32 bits.

    1. Re:32-bit Macs were a mistake anyway by SirMeliot · · Score: 1

      Core Duo is faster and nothing an iMac is likely to be used for will benefit much from 64 bits.

      64 bits don't always mean better. Remember the Atari Jaguar.

    2. Re:32-bit Macs were a mistake anyway by Anonymous Coward · · Score: 0

      Agreed. It was a little odd, especially considering the whole industry has or is moving to 64-bits, they took a momentary step backwards.
      There is no reason to be 32-bit any more except laziness.

  104. Has to be said by UnknowingFool · · Score: 1

    64-bits ought to be enough for everybody.


    Thanks, I'll be here all week. Tip your wait staff.

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  105. Not gonna happen by melted · · Score: 1

    Majority of people upgrade their PCs every 5 to 7 years. Knowing Microsoft a bit, I just don't see them saying to their customers "you're SOL, your system is too old". For Server, maybe this will happen (most people use 64 bit already there), but there's no way in heck this will happen for Client.

  106. Poor mac users by suv4x4 · · Score: 1

    Microsoft To Dump 32-Bit After Vista

    Ok, Vista's to have several major SP, the first of which is in the works. We're looking at 5-6 years just for Vista to get adopted at acceptable levels.

    The next major Windows realistically will come at least 7-8 years from now, take around 5-6 years again to get adopted.

    So we're talking around 2020.

    And never mind what Microsoft support, the majority of software is expected to support previous OS for a few more years, as is customary.

    So we're talking around 2025.

    Raise you hand everyone who uses 18 year old laptop. Anyone? Well, Mac users got nothing to worry about then.

    1. Re:Poor mac users by Doctor+Faustus · · Score: 1

      Raise you hand everyone who uses 18 year old laptop
      Using an 18 year old on my lap? Are we still talking about computers?

  107. Forever. by twitter · · Score: 2

    that we'll see 32 bit computing for another 20 years?

    32, 16 and 8 where it's useful. In the free world, it's just a compile option. Even M$ can't be so stupid as to disregard embedded and low power platforms.

    This is just M$ psycho-hype along the lines of "DOS is dead" they used to move Win3.1, 95, 98, W2K and XP as they slowly and painfully compiled their little system to 32 bits. That took them 20 years, not because it was hard but because they wanted to charge you for every "upgrade". Such stuff makes less sense in a world full of free alternatives that already offer the same things.

    --

    Friends don't help friends install M$ junk.

  108. Cool. When? by ceeam · · Score: 1

    After Vista? When is it due? Around 2020?

    1. Re:Cool. When? by marcosdumay · · Score: 1

      They'll probably delay to 2038... So nobody can complain about lack of 32 bit support, and MS can call it a feature.

  109. Re:The sun is likely to be a cold, dark lump of co by lilfields · · Score: 1

    While I take note of your Microsoft pun seemingly seen in a Mac commercial, which is all too typical and was completely expected when I saw "Microsoft" in the article title; I was under the impression that the next Windows would be released much quicker than Vista, in fact I was under the impression that "Vienna" is what pushed Vista out of the door with the lack of some of the earlier features promised. 2009 isn't very far away.

  110. Microsoft is getting smartter by r4g3 · · Score: 0

    Maybe they just got the hint, and with pride, they cant back out without an excuse... watch them take linux and shape it into something else// just like they took dos and messed it upp

  111. next for MS? by Anonymous Coward · · Score: 0

    Like there is even going to be a next for Microsoft.

  112. Mod parent up by Lazerf4rt · · Score: 1

    Most informative post in this discussion so far.

    And I would also add that when developers indiscriminately build their applications in 64-bit mode, it usually results in a performance drop. Storing all pointers as 64-bit values results in a bigger data structures, bigger stacks, and therefore less L1/L2 cache coherence, and worse overall performance. This won't change for a while.

    For today's applications, 32-bit is the sweet spot. 64-bit addressing has its place, but that place is pretty limited right now.

  113. Inaccurate? by FreshMeat-BWG · · Score: 1

    I am here. I was (am) here for the keynotes and the technical sessions. In each case this comment has been made, the speaker has very specifically said the last 64-bit *server* OS will be Windows Server 2008. Unless this came from a separate interview than the keynote or one of the technical sessions I have been in, the article may be inaccurate.

  114. Windows Developent is Strange. by twitter · · Score: 1

    As a programmer I've been waiting for this. I was actually disappointed that Vista would support 32-bit CPUs

    Yeah, it's really cool when compiler switches go away. I love it when that happens.

    Having one architecture to support will make things much easier, as well as get people to actually update their legacy code.

    I know M$ thinks of developers as "Pawns" but does anyone really think that being forced to recompile code is a good thing? What happened to the famous "backward binary compatibilty" M$ is supposed to be good for?

    Now if MS could get them to actually fix all the problems due to generally crappy code

    Now you almost make sense. Wouldn't it be nicer if you could just compile it yourself to whatever platform fit your needs? So that YOU could make hardware choices and do all of the above when it was in YOUR best interest?

    --

    Friends don't help friends install M$ junk.

    1. Re:Windows Developent is Strange. by malevolentjelly · · Score: 1

      Now you almost make sense. Wouldn't it be nicer if you could just compile it yourself to whatever platform fit your needs? So that YOU could make hardware choices and do all of the above when it was in YOUR best interest? of course, of course-

      Well played. Because every business user and their mother needs to know about compiler flags. If you want to make your own operating system, just don't use windows- it's a complete desktop solution. It's not what you want.

      For you and the 10's of thousands of users who are interested in recompiling everything from the ground up, we have linux. For the rest of people who prefer to have an out-of-the-box useful system, we have Windows, Mac, and (increasingly) Ubuntu (I know this is Linux, shut up).

      By 2009, x86-64 should be well distributed- I think even EM64T works in 64-bit vista. It's not a big deal. Windows will be ready for it, Mac will (really easy to upgrade their platform) and Linux will. Why is this such a big deal? You can build all sorts of goofy desktop systems that run Windows, anyway- if you want to run PPC or Sparc, you can enjoy the wonderful experience of linux without binary support (no flash! :( ). You people should be hatin' on mac.
  115. re: mac by Rage+Maxis · · Score: 1

    as an owner of a core2duo machine ... (macbook) ... I can barely run Vista.

    I'm not worried about running the NEXT operating system. I mean, who ... but the cutting edge hardware-wise can run a brand new MS OS anyways? Think about the PC you owned when XP was released. Can it run Vista? Doubt it. Not without a new Video card, at least.

    --
    --- ask me about nihilism, I will have nothing to tell you.
  116. Let the PRICES HIT THE FLOOR/Why this is GREAT! by Anonymous Coward · · Score: 0
    I think it is great that Microsoft is ending support for 32 bit machines! Once they stop putting out new operating systems for 32 bit hardware, the price of legacy 32 bit technology will drop to the floor! Of course, only in the M$ world is it necessary to buy a new vastly more powerful machine every 2 years to run the latest version of "Office". Once deemed unable to run the new operating system and newer applications (and no longer supported), a lot of businesses and corporations are doing to dump/write off their inventories. Nevermind that a 32 bit machine is STILL a powerful computer capable of all sorts of applications besides running "Word". As that I doubt peripheral cards are going to make an instantaneous jump to 64 bit land, there will continue to be a lot of supported hardware.

    Where Microsoft willfully creates a vacuum, Linux, Freebsd, Netbsd, Openbsd, and others can fill in. In the end, that "abandoned" 32 bit machine may LOOK like a general purpose computer but it could be a router, a home control system, a robot, a cheap node in a render farm, a pbx/voicemail system, a mail server appliance, a dedicated web server, a file server, a game server, an arcade machine simulator, or nearly anything the mind can imagine...

    It will get really interesting when all that "obsoleted" hardware starts making rounds in secondary/used markets. Do you think someone in India or Africa (or Europe for that matter) is really going to care whether the machine now more easily within their grasp is 32 or 64 bits? If it doesn't run Windows products at all (or is confined to old Windows products) do you think they will find utility for it? I think so.

    Ok, more accurately stated... I HOPE SO...

    There is a lot of installed 32 bit technology out there that need not "miss" the love and attention of Microsoft. A 32 bit Athlon 2100 is far from an orphan like a Commodore Amiga (No offense to Amiga enthusiasts). Being able to directly use much of the same hardware as its more powerful 64 bit big brother and with the help of open source projects, 32 bit machines will also continue to enjoy some level of interoperability with 64 bit platforms as well.

    Thanks Microsoft-- for abandoning 32 bit machines, once their prices drop in response to the flawed perception that you make productivity possible perhaps the greater access to cheaper hardware will lead more people to discover the real productivity that always seemed to frighten you when you couldn't squelch or appropriate it.

    This is great news!

  117. The answer to all the above is: by Chas · · Score: 1

    Yes. Eventually.

    --


    Chas - The one, the only.
    THANK GOD!!!
  118. Vista's replacement has a name!!! by kjkeefe · · Score: 1

    They just announced the name of Vista's successor... Microsoft Vaporware. Vista was the end folks...

    --
    1, 2, 3, 4, 5... That's the combination on my luggage!
    1. Re:Vista's replacement has a name!!! by cashman73 · · Score: 1

      But,. . . will Microsoft Vaporware run Duke Nukem Forever?

    2. Re:Vista's replacement has a name!!! by Hotawa+Hawk-eye · · Score: 4, Funny

      I heard Vista's successor was named Microsoft Windows Forever. It was supposed to be out last month, but they decided to rewrite it to use a new engine. Shouldn't be long now ...

  119. Ohhh please! by Anonymous Coward · · Score: 0

    I don't remember being able to buy any DEC Alpha or a 64 bit Sparc chip on the consumer level... that's what AMD brought us. And being a nitpicker is not good for your pressure :P

  120. total non-issue by TheGratefulNet · · Score: 1

    no one I know runs vista. no one I know PLANS to run vista. no BUSINESS I know plans to adopt vista.

    (heck, I have a free shrink-wrap legit copy of vista ultimate. it will be sold or given away but never installed by me).

    xp runs 'mostly fine'. there is zero reason to 'upgrade'. xp will be around for another 5 yrs, at least.

    by that time, the free unix world (and mac, too) has some time to FINALLY displace MS from the desktop. it CAN be done. it HAS to be done - the alternative (vista, drm, uber-control, uncontrolled 'patching' and feature reduction from remote updates, etc) is just too much backwardness to think about ;(

    vista exists MOSTLY (it sure seems) to inflict DRM on the user. its interesting that nvidia, for example, has video HTPC style accelerated drivers for their new 8-series cards - but ONLY for vista. xp will come 'much later'. linux - maybe never. the intention is clear: for high def movies, the industry wants you to be forced into vista. vista is total (remote) control. lack of user control, in other words. and the way they get you to do that is to encourage you to go to vista by holding the high-def carrot in front of you.

    but guess what - with tools like 'anydvd' (for HD and BD) - you really do NOT need vista to watch HDTV. give it more time and there really will be no valid reason for vista anymore.

    let vista die. its well on its way, now.

    --

    --
    "It is now safe to switch off your computer."
  121. The real reason by ceeam · · Score: 1

    Of course the real reason for it is that it will require more than 4 Gigs of RAM.

    [Not funny]

  122. Sun already got rid of 32-bit long ago by gd23ka · · Score: 2, Interesting

    Beginning with Solaris 10, 32-bit Hardware is no longer supported on SPARC.
    The operating system still ships with support to run 32-bit applications.

    Microsoft will certainly never be a serious contender in the tiers of
    professional computing filled by Sun and IBM and I know you can argue that
    with me for arguments sake but after everything is said and done it is
    still IBM Mainframe/AIX muscle and Sun Solaris tendon that make the world
    go around. And as far as rotating the globe goes, Microsoft excels of course at
    marketing spin so while the major players all abandoned 32-bit more or less
    quietly one wonders how Microsoft will flaunt and celebrate the fact in
    front of a impressionable lay public.

  123. Zealots are strange by The+Bungi · · Score: 1
    What happened to the famous "backward binary compatibilty" M$ is supposed to be good for?

    It's been twenty years+ of pretty fuckin' good compatibility. I still have an XP machine running Corel DRAW! 3.0, which was released in 1992. I know companies that stil run VB3 apps on Windows 2000 and XP. As more and more legacy software is replaced, the need to support it becomes less important, so Microsoft can move on. This is actually good for everyone, including hardware makers. Costs are also reduced dramatically.

    In any case, Microsoft (or "M$") supports whatever they make for decades as well. RHEL gets EOLed after what, three years? And even now Mozilla is thinking of dropping Firefox support for older Linux versions.

    Wouldn't it be nicer if you could just compile it yourself to whatever platform fit your needs? So that YOU could make hardware choices and do all of the above when it was in YOUR best interest?

    Nice straw man, especially from the wipe-and-reload-the-distro-of-the-day types. Most people don't care about compiling their own code to target different architectures or word sizes or endianess. You're making the argument that it's somehow important to be able to support the 8088 for commodity consumer software until the mountains crumble into the sea. Other than a few isolated niche cases - who the hell cares.

    Although not from the "M$ WINBLOZE LOLOLRZ" crowd, this is the same bull we all got when moving from 16 to 32-bit. "OMG, the end of the world, nothing will work, someone kill me". Same thing every time.

  124. 64-bit?!?! That old crap? by Mateo_LeFou · · Score: 1

    I assure you that by the time Vista's successor is actually coded and released, 64-bit architectures will seem very quaint.

    --
    My turnips listen for the soft cry of your love
    1. Re:64-bit?!?! That old crap? by Anonymous Coward · · Score: 0

      I assure you that by the time Vista's successor is actually coded and released, 64-bit architectures will seem very quaint. No, by the time Vienna comes out, 64-bit architectures will be pretty standard and their being a big deal will be what seems quaint. But I really don't think 128-bit architectures will displace 64-bit quite as quickly as you describe.
  125. Bingo by IceFox · · Score: 1

    With Vista sucking up ram just to boot and everyone recommending you start out with 2GB of ram this is a lot of indications that ram is going to be a big problem for windows users in the near future. You can only buy so much ram with 32bit systems and some laptops limited you to 2GB. Windows applications like to use ram and Windows LOVES to use ram. So to cram in a few more features that they think we want 64bit is the way to go.

    --
    Do you changes clothes while making the "chee-chee-cha-cha-choh" transformation sound?
  126. They dumped 64 bit long ago by supe · · Score: 1

    When they stopped offering an OS for an Alpha.
    Fact is, still have a ~400 alpha that flies with
    OpenBSD. Who cares about what MS anyway except
    Wall Street.

  127. So,,, by DragonWriter · · Score: 1

    Microsoft has used its annual hardware engineering conference to announce that Windows Vista and Server 2008 will be the last versions of Windows capable of booting on 32-bit CPUs such as Intel Pentium 4 and Core Duo.


    So, given other recent Slashdot Microsoft news, we should expect that the successors to Vista and Server 2008 will only run on 64-bit or better mobile phones that split their screens to support multiple users on the same phone?

  128. Intel Macs by painandgreed · · Score: 1

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run."

    Umm,... by time the next version of Windows after Vista comes out, it'll be probably four versions of OS X later and two new comptuers for me. I fully expect that my Mac in 6 years time will be more than able to run whatever MS throws out there... should I wish to install it on my computer to play games.

  129. 16-bit dictionary? by BUL2294 · · Score: 1

    Would it be WordPerfect Random House dictionary? I still use that today as it's all of 10MB installed, is blazingly fast, super compressed (today's processors make it instantaneous), and has every cuss word and jargon (that was in use in 1994)...

    --
    Windows 3.1x calc: 3.11 - 3.10 = 0.00
    1. Re:16-bit dictionary? by anss123 · · Score: 1

      Nope. I've come to rely on dictionary.com for my English needs; the 16-Bit app is in my native tongue. I've tried to find a more modern equivalent, but it's always "almost but not quite."

  130. AMD Fanboys on the march- even in the press by wevets · · Score: 1

    The article that gave rise to this post is a canard. Actually, Core 2 Duo processors are 64-bit. The platforms they're built into might not be, but that's because in the real world today, few need, let alone can use, due to lack of drivers and apps, 64-bit computing. This is more an issue for the PC OEMs and MoBo vendors than the processor folks, either AMD or Intel.

    When there's actual demand (and drivers and apps), there will be plenty of 64-bit computers. The processors are there already.

    1. Re:AMD Fanboys on the march- even in the press by aelfwyne · · Score: 1

      Read better.

      He said "Core Duo" not "Core 2 Duo".... the Core Duo series chips were basically just re-badged P4 chips.... However, I thought all of those were 64 bit anyway, though I could be mistaken. Core Solo definitely did have some non-64 bit versions, and there are a lot of laptops that aren't that old with Core Solo chips.

      --
      -- If it ain't broke - overclock it more.
    2. Re:AMD Fanboys on the march- even in the press by Guy+Harris · · Score: 1

      the Core Duo series chips were basically just re-badged P4 chips

      More like re-badged (and SSE3-enhanced, and dual-cored) Pentium M's.

      However, I thought all of those were 64 bit anyway, though I could be mistaken.

      I think most Pentium 4's were 64-bit at that point. However, no Pentium M's were; Core Duo (and Core Solo) were 32-bit only.

    3. Re:AMD Fanboys on the march- even in the press by Monkey · · Score: 1

      However, I thought all of those were 64 bit anyway, though I could be mistaken

      These P4 chips had the EM64T enabled: All P4 6xx models and P4 5x1 models ( 541, 551, 561 etc.). Also, the Celeron D 3x1 and 3x6 models (331, 336, 341, 346 etc.) had EM64T (Extended Memory 64 Technology) on them.
      These were the first Intel CPUs to have EM64T enabled, and I believe all subsequent models had this technology implemented.

    4. Re:AMD Fanboys on the march- even in the press by NoNickNameForMe · · Score: 1

      Hmm. I wonder if the EMT64 support was purely a microcode update or did it require changes to the CPU itself. Anyone knows?

  131. Grammar Nazi by noidentity · · Score: 1

    "AMD, which introduced 64-bit CPUs early -- much to the derision of Intel, which said there was no use for them at the time -- must be delighted with Microsoft's decision."

    Sentence does not parse. There's no matching comma for the first. Moral: if you're going to get fancy with sentences, do it right.

  132. what problem? by SuperDre · · Score: 0

    why would this be a problem? most people who still don't have vista propably don't even have all the hardware to run it anyway.. I'm running XP x64 and must admit that it runs much better than my XP 32bit version, so I wouldn't miss it. and let's not forget, current XP and vista will run good enough for the next 5 a 10 years, so why even bother with arguing...

  133. The REAL Reason... by BinaryOpty · · Score: 1

    It's pretty obvious, the real reason Windows Next will require 64-bit processors is because it will take up 4GB of RAM while running, meaning you'll need more than that to actually be able to do anything.

  134. Doubt it. by phoric · · Score: 1

    Just like most of Microsoft's plans for future OS's, I doubt this one will actually come to fruition. The typical mom and pop computer user isn't going to run out and replace their good ol' 32bit system anytime soon.

    1. Re:Doubt it. by OneSmartFellow · · Score: 1

      You can say that again. I cannot get my in-laws to accept my free old P4 running XP to replace their PII with Win98. I want to give it to them, becuase, frankly, trekking to their place every couple of weeks to undo all the weird shit they do to their system is really getting boring.

      They absolutely refuse to try to use XP, since they are only now able to remember how to use their 98 system, after having it for 5 years.

      I hope I never get like that !

  135. Nice blinders, slave. Re:Zealots are strange by twitter · · Score: 1

    Nice straw man, especially from the wipe-and-reload-the-distro-of-the-day types. Most people don't care about compiling their own code to target different architectures or word sizes or endianess. You're making the argument that it's somehow important to be able to support the 8088 for commodity consumer software until the mountains crumble into the sea. Other than a few isolated niche cases - who the hell cares.

    Indeed, that is a nice straw man, Bungi. The argument that I'm making is that hardware choice is nice. You know, there is a world of computing outside of x86. Alpha, PowerPC, Cell, ARM and others all come to mind. That there are distros to run all of these which can, yes, be wiped and reloaded without loss of user data, is a good proof of that demand. But it's more than that, Debian runs on a dozen or so platformsso you don't have to do everything yourself. That's the power of free software - when one person has solved a problem, everyone has the solution.

    M$ has managed how many platforms again? How much do SDK's cost per platform? And you like it that way? Dude, the lack of choice is a serious failure of the non free software model. Even judged within the selfish limits of non free software's world view, being forced to move from one platform to another is a PITA that's going to cost you time and money. Bend over Bungi, Bill Gates has got a few software deals for you.

    --

    Friends don't help friends install M$ junk.

  136. Vista should have never been 32-bit by Jackie_Chan_Fan · · Score: 1

    Way to wake up Microsoft. 32bit has hit the wall with ram usage.

    1. Re:Vista should have never been 32-bit by smash · · Score: 1

      Pentium Pro onwards supports 36 bit addressing in 32 bit protected mode.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  137. Itanium is a *successor* of Alpha by DrYak · · Score: 2, Insightful

    cause most of the competing processors (PARISC, Alpha, MIPS) to abandon the market even before the Intanium shipped

    Not exactly.
    HP collaborated with the design of the Itanium. Thus pulling out of the market before the Itanium arrived was a logical decision from the point of view that they were going to replace the Alpha with their newer baby jointly-developed with Intel.

    MIPS continued for some time after the Itanium and was progressively dropped when its sales went to low, both from workstation and embed markets.

    (PARISC : I don't know. I suspect it to be somewhat similar situation).

    What kills processors is two fold :
    The main reasons is a big ball and chain called "binary legacy".
    - Business are used to run Windows on their workstation. Microsoft has never supported additional platforms for long time (Alpha has only had 1 NT version made for it. Itanium had only 1 XP version made for it) because supporting multiple platform is hard for them (the only reason they'll keep support for 64bit x86_64, is that they'll kill 32bits instead and thus they'll still have only 1 main architecture to support). Thus there was a lack of interest from the largest consumers because of this absence (of course there are a lot of shops running Unices. But they aren't profitable on the same level as Dell's consumers).
    - And even if you had the corresponding OS for your platform, you still need to have software to run on it. And the problem at any time that something new arrives, is that there a huge decade of legacy to run of it. Yes every time a new designs arrive, it may be largely superior. But corporation's PHB don't give a damn about deisng quality. They only want to know if their applications will run. Alpha wasn't compatible at all with x86 application. Neither 68k back in its days. Nor MIPS. Nor PARISC. Itanium had lousy compatibility because it was mostly done in software and thus was running much slower than the rest. Transmeta only survived because it has decent speed in running x86 code and has very low power requirements. The main reason that Itanium flunked and AMD64 prevailed is that the later was an extension to x86. Yes, this extension is a hack. But a hack that has full backward compatibility, and that can be plugged into a PC and run today's OS with today's applications. Backward compatibility has been both the x86's main advantage and main problem.
    - Also there's the problem of drivers. Even if the newer arch. uses standard bus such as PCI where you can plug all your existing hardware, you still have to get drivers for it. And few manufacturer are going through the hassle of supporting another additional binary format. Linux is already too much for them, exotic CPU are beyond them. Early adopter of Windows XP 64bits (both Itanium and AMD64) will remember.
    - Compare this to the Linux world where, becuase the source is freely available, and there project such as Debian that take care to have only very stable code. : switching to a newer architecture is mostly a matter of recompiling the code for the new platform. That's why Linux was almost available overnight for AMD64, running on Transmeta simulators before the actual hardware was available. It mostly had only to be recompiled and could be done easily because it leveraged work done to port the code to other 64bits platforms (Sparc64, or the other 64bits arch you mention).

    In a perfect world were everyone is using opensource, those arch. you mention could have survived, no mater what marketing is heard from Intel and every one could benefit from the latest great processor with clean and perfect architecture. But in a world were Microsoft has a huge monopoly on desktop machines and everyone runs binary apps and drivers, only hacks of the pre-existing arch can have significant impact. That's why you haven't seen anything revolutionary for the past 35 years (software compatible since the 8bit 8008 in 1972, binary compatible since the

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:Itanium is a *successor* of Alpha by drsmithy · · Score: 1

      Business are used to run Windows on their workstation. Microsoft has never supported additional platforms for long time (Alpha has only had 1 NT version made for it. Itanium had only 1 XP version made for it) because supporting multiple platform is hard for them (the only reason they'll keep support for 64bit x86_64, is that they'll kill 32bits instead and thus they'll still have only 1 main architecture to support). Thus there was a lack of interest from the largest consumers because of this absence (of course there are a lot of shops running Unices. But they aren't profitable on the same level as Dell's consumers).

      Windows NT was available on x86, Alpha, MIPS from its first release in 1993. In 1995, NT 3.51 added PPC. Support for MIPS and PPC was dropped around 1997-98 and support for Alpha in about 1999 (Windows 2000 still had an Alpha version up until RC2). In 2001 Itanium support was added and in 2003 x86_64 was added.

      There was also an internal port in the mid 90s to SPARC and, IIRC, PA-RISC. This was probably NT 3.51 and/or NT 4.0.

      The implication that Windows NT is not, or was not, "portable" and that Microsoft "has difficulty" porting it to new platforms, has no foundation in reality.

      This mean that when Windows-the-next (tm) comes out, either there will be a massive switch toward other OS (very likely in university labs) or it will see an even slower reception than Windows Vista is currently experiencing.(very likely on Joe 6-pack's older 32bits machine).

      This argument is made frequently (and similar ones have been in the past with earlier releases), but it's difficult to see any sort of logic behind it. Most sales of Windows are through an OEM channel, not individuals buying upgrades. Further, most people who are buying upgrades, are doing so to put on a relatively high-end PC.

      The suggestion that the next version of Windows only supporting 64 bit hardware ca. 2010 is going to cause any meaningful migration to other platforms, doesn't even pass the laugh test, given that:

      * Most sales of that version of Windows would be for new (ie: x86_64) hardware;
      * Of the remainder, most would be for relatively high end (ie: x86_64) hardware;
      * The transition period will be measured in years; and
      * All mainstream alternatives will almost certainly be in the same position

  138. Re:as the owner of a PPC mac.... by gumbi+west · · Score: 1

    You're right! The 601 is the first gen PPC, the 604 and low end version (603) was the second generation. My G3 and G4 systems definitely don't qualify. What I was thinking is that they are the oldest new-world Apples, but they aren't even in that group, that would be an original iMac... Sigh. Last time I try to change my subject.

  139. The Linux community says THANK YOU to Microsoft. by DrYak · · Score: 4, Insightful

    This decision by Microsoft to drop 32bit support *may* boost Linux (and other OS) adoption.

    Currently I know some friends who uses old machines and a lot of machines in the university (specially in labs). All those are still based on P2/P3 or other CPUs of that era. 10 years old processors.

    "A next Windows" has no chance of happening before 2013, considering their current release speed of 6 years between XP and Vista. Worse if we take into account that Microsoft has promised to build an entirely new capability-based microkernel OS. Which is very unlikely, given their tendency of scraping newer non-eyecandy idea out of Vista because of time constraints.

    By the time Microsoft finally releases their next piece of shit, there will be a lot of 10 years old, 2003-era processors everywhere (Intel Pentium-IV, 32-bits only Intel Core, AMD Athlon XP, early 32bits AMD Semprons) :
    This mean that when Windows-the-next (tm) comes out, either there will be a massive switch toward other OS (very likely in university labs) or the new OS will see an even slower reception than Windows Vista is currently experiencing (very likely on Joe 6-pack's older 32bits home machine).

    The last similar switch of technology requirement was Windows 95 : the first consumer oriented widely diffused Microsoft OS that could only run on 32bits protected mode CPUs.
    In 1995 (okay, 1996) when it came out, Intel 80386 where 10 years old and had finished displacing the 16bit only older 80286.
    99% of home computer where equipped with 32bits Windows 95-"mostly"-capable CPU ranging from 386 to Pentium.
    That's why it went went "somewhat more smoothly".
    Throwing out the 32bit arch is TOO MUCH early. Microsoft should wait until it is completely phased out of the market, in most segment (if possible, including the small embed/ITX market of people making low-power boxes. Current VIA chips are 32bits only). The problem is, maintaining compatibility for more than 1 architecture has always been too much work for Microsoft (Alpha and MIPS got only a couple of NT releases. Itanium hasn't got a much high number of OSes), in contrary of the OpenSource community.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
  140. Re:Nice blinders, slave. Re:Zealots are strange by The+Bungi · · Score: 1
    M$ has managed how many platforms again?

    Irrelevant my dear flocktard. Microsoft writes commercial software that runs on commodity mass-produced hardware. That's what they've always done, and that's what they'll always do. You can have the 28 niche platforms and architectures. Unless you were interested in the m68k, which etch dropped. Oops.

    How much do SDK's cost per platform?

    About $0.00, last I looked.

    lack of choice is a serious failure of the non free software model

    It's not a "failure" if you never intended to support all those platforms. You might count it as an advantage of Linux or whatever and I'll agree, but that does not translate into it being a "failure" on Microsoft's part. Why is that so hard to understand? "Microsoft doesn't do X - HAHA! THEY FAIL!!" C'mon.

    being forced to move from one platform to another

    As usual you exaggerate in the name of zealotry. Whatever your perceived damage done by doing x-or-y because of Microsoft happens rarely enough and goes smoothly enough that it doesn't really matter. Plus, you get support for decades if you decide not to. That's the little detail you keep forgetting, I suppose on purpose.

    Bend over Bungi, Bill Gates has got a few software deals for you.

    Ah, always a fan of scat humor and sexual references. If I didn't know better I'd say you were twelve.

  141. Can't even buy 64-bit Vista now.. by 787style · · Score: 1

    Pre-installed that is. Must be because all the adware junk that OEM's try to dump on their customers won't work in 64-bit Vista.

    Microsoft thinks they have the driver issue fixed by forcing all drivers that are WHQL'd to be 32 and 64 bit, but WHQL certification is beginning to lose it's relevance. Now that any driver can go into the "unclassified" category, all the stability guarantees WHQL provided will go away, and will simply become a rubber stamping body.

  142. Re:The sun is likely to be a cold, dark lump of co by noewun · · Score: 1

    I was under the impression that the next Windows would be released much quicker than Vista, in fact I was under the impression that "Vienna" is what pushed Vista out of the door with the lack of some of the earlier features promised. 2009 isn't very far away.

    If you believe Microsoft's published release schedules I have a lovely bridge to sell you. Low use, well maintained and just had a new paint job.

    --
    I am a believer of momentum and curves.
  143. And thus Intel surported Linux... by Anonymous Coward · · Score: 0

    and Linux took over Microsoft in OS usage.

  144. who cares... by jay2003 · · Score: 1

    It will be at least 10 years before software vendors stop supporting Vista maybe 15 since it will probably will take MS 10 years to get the next OS out. I just bought a copy of XP to run under Parallels. Could have bought Vista for the same price but its more of a memory hog and all I really need is the ability to run occasional Windows only app. I couldn't care less about the features in Vista or whatever comes after it.

    I'm surprised everyone missed Microsoft's real reason for doing this. Vista 64-bit requires signed drivers. Yes you can disable driver signing on Vista but it something only about 5% of Windows users would feel comfortable doing. The next Windows will probably make disabling driver signing more difficult or maybe even impossible. Microsoft will have effectively locked down what you can run on your own hardware for Windows users.

    1. Re:who cares... by wellingj · · Score: 1

      I'm surprised everyone missed Microsoft's real reason for doing this. Vista 64-bit requires signed drivers. Yes you can disable driver signing on Vista but it something only about 5% of Windows users would feel comfortable doing. The next Windows will probably make disabling driver signing more difficult or maybe even impossible. Microsoft will have effectively locked down what you can run on your own hardware for Windows users.

      ahem.....Told you so
  145. Re:The sun is likely to be a cold, dark lump of co by lilfields · · Score: 1

    I don't know why you were modded up, your comment was pretty redundant; if we consider that it will be 64-bit only, don't you think the upgrade cycle will have been shrunk? Considering you only have to make one standing core edition? Even if the product is pushed back it won't take as long as it once did, given this information. I'm sure Windows Vista is more part of a transition model than it is an actual key operating system.

  146. Re:The Linux community says THANK YOU to Microsoft by yahooadam · · Score: 1

    its about time, i mean MS is already delaying UEFI because vista doesn't support it - although Linux is capable of running it, and does on server motherboards

    I don't even know why vista has a 32 bit version, most people who upgrade have to upgrade their computer, and anything these days is 64bit anyway, so why have 2 versions of vista, of which vista 64bit is getting crappy driver support so its useless anyway

    Also, by the time MS release their next OS 32bit wont support enough ram so they need 64bit anyway for the terabytes of ram the next OS will need

  147. Pipped to the post by SEMW · · Score: 1

    Ooops! I didn't see see GlobalEcho's reply before posting mine; s/he did the same thing before me.

    --
    What's purple and commutes? An Abelian grape.
  148. 7 more years of 32 bits by foolinator · · Score: 1

    Computers will be sooo much faster once we can let the 32 bit cousins go. 16 to 32 bit didn't take long at all.. But my favorite quote: "Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run." It's too bad that Vista will be the only windows OS for another 5-7 years. Anyone who can afford an apple will have a new one by then.

    1. Re:7 more years of 32 bits by smash · · Score: 1

      Erm... 16 bits to 32 bits didn't take long in hardware, but it took from about ~1980 (8086 XT with DOS) to 1996/2000 (NT4/2k/decent linux dist) in terms of "defact standard" software. 15 years. Sure, the amiga, mac and ST were fully 32 bit years before that, but they didn't grab the bulk of the market.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  149. Good Point by nobodyman · · Score: 1
    Microsoft is notorious for having high expectations and grand plans, taking too long to execute, and dropping most of their features, improvements, and changes before the end product is released.

    Exactly. Wish I had mod points.

    Years ago, Microsoft claimed Vista was going to depricate win32, and that the .NET framework was going to be *the* windows API?
  150. +1 Informative by uhlume · · Score: 1

    Nice work. If only my unused mod points hadn't expired this morning...

    --
    SIERRA TANGO FOXTROT UNIFORM
  151. No, they didn't. by ElboRuum · · Score: 1

    Not in the way that was meaningful. Actually, the Win32 API should have been scrapped by XP. NT 3.1 is a security nightmare, as is every OS spawned using the Win32 API as its core functionality. NT 3.1 predates the Web-as-Disease-Vector concern, ergo, no real addressing of security. Once security became an issue Win32, was officially obsolete. One could argue that NT 4 should have been the OS dump. Win 2K was another opportunity. XP was the last gasp.

    "For Microsoft, dumping backwards compatibility would be equivalent to giving market share to Linux etc. on a platter."

    Interesting.

    A free operating system is considered to be a competitor of one that costs money. Seems to me that this equation has only one possible end.

    Given the amount of software that was incompatible with XP, it is clear that backwards compatibility isn't really all that important. It certainly hasn't been handing Linux market share since users seemed to be OK with sacrificing a bit of backwards compatibility for a reasonably stable OS. And as someone else in this thread correctly stated, OSX was a complete rewrite and it didn't seem to harm adoption.

    To your statement, assuming truth to your surmise, if Windows cannot compete with other OSes because they've finally made the transition to dinosaur, then let Darwinian principles take over and naturally select it out, rather than artificially controlling the market to allow continued existence.

    Risking market share with a rewrite is the ONLY way Windows can survive. Windows is a bloated OS whose base code is about 15 years out of date, and because they refuse to make the statement "your old programs WILL NOT WORK on this new OS", they will continue to tweak a system and con people into paying for a continuous upgrade path, and that's a strategy headed for the dungheap.

    Linux is gaining strength because people have had it with the "upgrade and pay through the nose, or don't and be obsoleted" MS revenue strategy used on every single one of their product lines.

    The only way proprietary software can compete with F/OSS is by making a better product with a singular focus. And for MS that means a clean break from the past, an assumption of inherent risk on a new product absorbing the lessons of the past, and a strategy of long-term technology investment, rather than short-term planned obsolescence. I just wonder if they have the talent for that kind of forward thinking. I'm doubting it.

    Will it take the opportunity? Probably not. GM and Microsoft have a lot in common. All the effort is in figuring out new ways to prop up and extend the revenue stream, and very little is going to product development.

    Maybe being forced to play as a newbie will bring their best efforts forward. Maybe it'll drown the whole company. Who knows? Who cares? People will adapt to the playing field they're presented.

  152. Re:The sun is likely to be a cold, dark lump of co by noewun · · Score: 4, Insightful

    None of this touches the twin problems which makes Microsoft's release schedules so awful: the religion of backwards compatibility and a overly-managed, near-chaotic corporate culture which emphasizes endless meetings and paper trails over innovation. Both of these items stem from something Microsoft can't control, which is the necesity of leaning on Windows/Word as their two dominant profit engines. Essentially, Microsoft has worked their way into a position in which true innovation (of the kind Apple was forced into with the failures of Copland and Pink and the adoption of OS X) is nearly impossible, because anything which threatens to cut off a sizeable portion of their user base directly threatens the company's bottom line.

    In other words, the problem isn't Windows per se, or 32- versus 64-bit, or any other technical issue. The problem is Microsoft needs Windows simultaneously to be the same old operating system you've been using for years and the latest, greatest thing, and it can't be both. For a technology point of view, the best thing would be to really remake Windows from the ground up as Apple was forced to do with OS X and just tell people that if they bought their machine before 2001 they're out of luck. But they can't, and won't, do this, so their release schedule will continue to be contrained by the need to do two opposing things at the same time.

    --
    I am a believer of momentum and curves.
  153. ONE REASON by y86 · · Score: 0

    Cost.

  154. Yes, memory by Sycraft-fu · · Score: 1

    The 4GB limit is becoming more and more of a problem. Especially since you don't ever really get 4GB ona 4GB system, since PCI devices grab memory addresses for their own use. 3.3 or so is usually what I see. While it is still somewhat "high end" to need that much memory, it has entered the consumer space. There are games now that want 2GB to themselves, if they can have it (Supreme Commander) and so on.

    While it may not be a real problem right now, it will be in 4-5 years which is likely when we see the next version of Windows.

    Also, the bitching about 16-bit apps is silly. If you have a legacy app, like a game, run it in an emulator. DOSBox does an excellent job. If the thing is newer, there's not really an excuse for using 16-bit code.

    Basically what it comes down to is MS wants to maintain only a single codebase (which makes sense) and they project that by the time the next version of Windows comes out, 64-bit will be all that is being sold. They are probably right about that.

  155. Timing, more than anything else, I'd guess by mbessey · · Score: 1

    I worked at Apple at the time, and had figured out that a version of OS X for some new architecture was being readied for release about a year before the announcement was made. At the time, I had assumed that AMD-64 was the new architecture, but I turned out to be wrong about that. I think the reason they went with 32-bit x86 simply comes down to timing. The overall 64-bit support in the rest of the OS wasn't there yet, even for PPC. At the time, 64-bit PPC apps were limited to the BSD libraries - no Carbon, no Cocoa.

    Once the decision was made to go with Intel as the processor supplier, the timing of the switch meant that 32-bit was the only model that could be supported out of the gate. Now, Apple has previously said that they're going to be improving 64-bit application support for future versions of OS X. I fully expect that Leopard, or whatever comes after, will have support for 64-bit applications using the full range of system services. A lot of hard work has gone into making the 32-bit to 64-bit transition as smooth as possible. Writing 64-bit console apps for PPC is basically a matter of changing a single compiler option, and viola - you can use dozens of gigabytes of memory just as easily as writing 32-bit code.

    I expect that the support of x86-64 in OS X will be similar. For the developers that use it, it'll be a trivial change. The users won't even know which applications are 64-bit enabled.

  156. Basically ya by Sycraft-fu · · Score: 1

    Windows keeps the same model for virtual address space. It splits it right down the middle, lower part for user, upper part of kernel. So in 64-bit space that's 8 exabytes for each. Should the day ever come where we actually have systems with more than 8 exabytes of RAM then we'll have the same per process limitations we are seeing today.

    Please remember that is all deals with virtual address space, not real RAM usage, however. The OS shuffles things around in actual RAM as it sees fit, however it presents the split down the middle virtual space to each program running in it, which limits the amount of memory the program can access.

  157. Ooh. 5 more years by pestilence669 · · Score: 1

    "Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run."

    That's funny. Being that Vista took 5 years to get out the door, I don't see what all the fuss is about. So... your new Mac won't run the newest version of Windows when it's released in five years. What's the big deal? It's a Macintosh anyway. Had you purchased an early Dell model, the problem would be the same.

    In any case, Microsoft has made bold declarations like this before. Remember when they said all future Windows releases would use the NT kernel?... back in 95? Then there was Windows 98, ME, and all the interim abominations. I wouldn't be surprised if they offer Vista "ME."

  158. and we care because? by EdelFactor19 · · Score: 1

    seeing as Vista is just getting out the door, and given the increased production times trend (win95,win98, XP (2002 or so?), Vista:2007
    so I don't think that we will see Windows "broken unbreakable glass" (what I'm calling their next version) until well into 2013 or so...
    with that said and given the massive upgrades required to PROPERLY run windows Vista it isn't applicable to todays hardware because most of the x86_32 stuff can barely run it.
    Personally I don't care much, I've seen Vista and I don't see any major motivation for an upgrade. So there won't be a new OS after Vista on 32, fine by me. XP is stable enough to run the windows junk that I need, If i absolutely had to I suppose years from now I could install a discount Vista...
    But what's going to be improved about the new OS or even Vista that even motivates me to get it.

    People like to run out and by the latest Windows simply because its the latest, thas all they care to know. I say why pay for something you don't need. What does Vista offer you that XP isn't doing well enough for you. What is winNext going to offer that makes it needed or worth upgrading to. I dont care what it runs on if I dont want or need it. Seriously for the bulk of people out there, for whom Email, word processing and internet browsing is the entirety of what they do, 64 bit processors are unneeded. Why focus on improving the current system when you can just deprecate it and release a new one like microsoft does.

    This could open up the door even wider for Linux to become a mainstream OS for people who don't have any need to buy a 64bit processor in the future but for whatever unforeseen reason need to migrate to a supported OS.

    Telling me what your next release is going to support for hardware without telling me what the next release even addresses is sorta pointless. I don't give a crap what your next thing does until I know if I even WOULD want it anyways. It seems rather backwards to me. The telling sign that microsoft doesn't know how to advertise, other than Aero I don't know why I would want to upgrade to Vista. Vista's features consist pretty much entirely of new versions of applications as opposed to OS enhancements, at least as advertised. Most of it seems like GUI catchup to KDE/GNOME/OSX (aqua).

    I think what they really did is shoot themselves in the foot. Now anyone who was thinking about buying a new machine to get vista shuoldnt, they should wait because whatever they get will be made obsolete when x86_64 becomes the only supported thing.

    It all really comes down to the fundamental problem of what are the OS updates and new versions actually accomplishing other than GUI updates and bundling applications or updating current ones.

    --
    "Jazz isn't dead, it just smells funny" ~Frank Zappa
    EdelFactor
  159. Don't Throw Me in the Briar Patch... by mkcmkc · · Score: 1

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run.

    Where can I go to sign up to have Vista be the last Windows I have to run?

    --
    "Not an actor, but he plays one on TV."
    1. Re:Don't Throw Me in the Briar Patch... by nsayer · · Score: 1
    2. Re:Don't Throw Me in the Briar Patch... by mkcmkc · · Score: 1

      Heh. I almost would, but they don't yet seem to reliably boot Ubuntu...

      --
      "Not an actor, but he plays one on TV."
  160. Except you are wrong by Sycraft-fu · · Score: 2, Informative

    They don't require MS's signature on drivers, just a signature. You can self sign. Many drivers are signed that way. The Creative Labs audio drivers, for example. Those pieces of shit wouldn't pass WHQL validation, but they don't have to. Creative self signs them. Likewise the Truecrypt kernel module is self signed (though not because it sucks).

    This doesn't stop free, open drivers, just requires the people releasing them to sign them. If the driver isn't MS signed, Vista pops up a little box saying "The driver is signed by Company X, do you want to trust them and install?" Click yes and it installs, and you aren't bothered again.

    The idea isn't to stop third parties, it is to prevent people from compromising drivers. If you think you are installing Tryecrypt, but the digital signature is instead form "Joe's L33t Hax0r Shack", you should probably think about stopping the install and talking to the TC foundation since they have probably been hacked.

    1. Re:Except you are wrong by mpapet · · Score: 1

      I'd be wrong if my statement never came true.

      But it will. How can that be?! It's true because Microsoft has an obligation to their shareholders to return above-average profits. They do that by creating barriers to entry. Right now the signed driver barrier is low, later on, the barrier will be raised steadily.

      --
      http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    2. Re:Except you are wrong by Sycraft-fu · · Score: 1

      Ahh, glad to know that you can see the future with perfect clarity... Or maybe you are just yet another FUD spewer who is projecting what they want to be real as to what will be.

  161. Re:The sun is likely to be a cold, dark lump of co by lilfields · · Score: 1

    The problem is Microsoft needs Windows simultaneously to be the same old operating system you've been using for years and the latest, greatest thing, and it can't be both
    Hence I said Vista was part of a transitional model, the next release will probably be much more swift. Microsoft's bottom line is impacted by equity, Microsoft is a cash machine, but they have lost a substantial portion of their net worth in stock. This is in part due to unpolished/delayed releases and thus bad PR, which seem to hide the value of the overall company (good will) as opposed to exposing it which Apple and Google have done with their produce innovations. Note their company P/Es are much higher than Microsoft's even though Microsoft is still growing at a fairly rapid rate. There is market demand, and there is...stock market demand, I doubt Microsoft wants to remain a $300 billion company from now until the end of time, which is essentially the same as it has been since early 2002 despite its growth.
  162. MS Word 2010 will exceed 32-bit address limits by Locutus · · Score: 1

    The public announcments will follow that the reason for this is because the popular ODF file format is so inefficient that supporting it natively in MS Word 2010 causes Word to exceed the addressing limits of 32-bits.

    In more news, the new Microsoft Windows Infirmary will have a minimum memory requirement of 4GB. ;-)

    LoB

    --
    "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  163. Re:The sun is likely to be a cold, dark lump of co by noewun · · Score: 1

    I don't think they can do this, though, because of their religion of backwards compatibility. Too many corporations still run old software which requires Windows to be enormously backwards compatible. Walking away from these applications/companies, IMO, is something which Microsoft is absolutely unwilling to do, largely because their corporate culture is ossified and unimaginative. 95% of their effort seems to go towards keeping the status quo functioning rather than looking towards the future.

    --
    I am a believer of momentum and curves.
  164. Shame it's not true by Anonymous Coward · · Score: 0

    http://blogs.msdn.com/iainmcdonald/archive/2007/05 /17/weird-how-people-get-stuff-wrong.aspx

    Future versions of Windows Server after {the upcoming Longhorn / 2008} will be 64-bit only, but not the client OS.

  165. For "game developers"?? by Anonymous Coward · · Score: 1, Insightful

    What are you smoking? The two top-end game consoles (Xbox360 and PS3) have 512MB of main memory, which is shared between graphics AND everything else. Compared to that, a limitation of 2-3 GB on PC games is practically no limitation at all.

    The people who are running out of memory are DBA and server farm operators. Maybe MMO server developers have problems with the 4GB limit.

    In practice, everybody who struggles with the 4GB limit is buying their own hardware anyway, so they can buy PAE-capable boards and run PAE-capable software on them.

    4GB is not a practical limitation for everyday consumers (yet), and I don't expect it will be for at least 10 more years, no matter HOW bloated Microsoft makes their software.

  166. Gates is eating his words now by Anonymous Coward · · Score: 0

    Remember?

    "Four Gigabytes should be enough for anyone." -- Bill Gates

  167. Will They Still Dump Core Memory? by VGfort · · Score: 1

    ..after Vista, that is the real question :p

  168. Opportunities in Microcomputing by mbstone · · Score: 1

    This will open up a new market for people who want simple applications that run, say, on an 8088 with 640K RAM. You'll be able to print documents instantaneously!

  169. Re:The sun is likely to be a cold, dark lump of co by lilfields · · Score: 1

    Then why would they make their next operating system 64-bit only? Seems contradictory to their "status quo", and still that doesn't have anything to do with the release date or anything I said in the previous post.

  170. Or... by Rix · · Score: 1

    They'll just stay with Vista, or more likely XP.

    1. Re:Or... by master5o1 · · Score: 0

      Or even Windows 2000 if you're like me and prefer that over XP and Vista. Although I use Ubuntu, and have never had XP or Vista on any of my own computers, but my mum and *other* relations have XP, Vista. My brother also uses Ubuntu -- Hooray! Two intelligent people out of what? 12 ... Atleast my cousin is also thinking of ditching XP from her laptop for Ubuntu... Oh this will probably be modded low if it is still being moderated for going into stupid off-topic places but meh :P

      --
      signature is pants
  171. Apple: Recent Success? by andersh · · Score: 1

    No, Apple has enjoyed a very successful year thanks to the Intel switch alone. In fact they are expecting further growth thanks to A. Adobe products for the intel OS X and B. Paralllels' virtualization products.

  172. Re:The sun is likely to be a cold, dark lump of co by MrLizardo · · Score: 1

    It's not like you can't run 32-bit code on a 64-bit kernel. I'm sure that applications running in 32-bit mode on 64-bit "Vienna" will have some restrictions imposed on them (such as not being able to access DRMed content, and somesuch) but it would be downright foolish of them to just up and make everyone compile their programs for x86_64. Microsoft has already shown that they care about *software* backwards compatibility quite a bit more than *hardware* backwards compatibility. Anyways, I'm willing to go on record as betting that most well-written, API following, 32-bit binaries compiled for Windows XP will work just fine on 64-bit Vienna.

    -Mr. Lizard

    --
    ^I'm with stupid.^
  173. landfills? note: 2 billion PCs by 2008 by proto · · Score: 1


    I was amazed by the fact that it took 25 years to reach one billion PCs. That number will change to two billion by 2008 according to Gartner Dataquest.
    You know what this is leading toward. Without a nation wide effort of recycling its a slow and steady progression of these PCs ending up in closests, storage facilities and land fills. This subject doesn't grab the media's attention like such subjects as Global warming or dirty bombs, but considering the toxic materials PC are made with it should at least raise some questions. The picture in my mind references a tv PSA of long ago. I see a decades worth of computers tossed back and marked as obsolete, while an Native american looks toward you and sheds a tear (ok so he wasn't really an Indian but its sentiment that I wanted you to remember),

  174. Mac owners left in the lurch? by nsayer · · Score: 1

    Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows they will be able to run. I dunno. It seems like a cleansing thought to me.

    But just to play the devil's advocate here, I've upgraded 3 mac minis to Merom CPUs, which have the 64 bit extension and virtualization features. I am not sure, but I believe the iMac CPUs are also socketed (they may not have even sold any iMacs without Core 2 - not sure). Seems like the only folks *really* left in the lurch would be 1st gen iBook owners.

    But in any event, I believe that by the time Vista's successor arrives, macs (and perhaps even Linux desktop boxen) will have enough market presence that we won't really be bemoaning the software monoculture anymore. Already there are only two things for which I must use Windows and have no Mac alternative: Netflix Instant Viewing (and they will have that available for mac in the future at some point) and playing at pokerstars.com (which I don't do too much since Full Tilt Poker has a mac client).

  175. Intel Macs Retire In 2012 ... new Windows by then? by gig · · Score: 1

    > Owners of first-generation Intel Macs that used (32-bit only) Core Duo CPUs may not be so happy knowing that Vista will be the last Windows
    > they will be able to run.

    For recycling purposes, both Apple and Dell say 7 year life span. Time is up on 32-bit Macs in 2012. I haven't heard anyone seriously suggest that Windows Vista will be replaced with a new version of Windows by 2012. Inside Microsoft they may say so but on one hand who believes them and on the other, when they suggest to ship post-Vista Windows in 2010 people get angry at the idea that the next shake up will come so soon.

  176. Server Only! by F.Prefect · · Score: 1

    Microsoft is transitioning the server line to 64-bit exclusive. Not the client line. You'll note that TFA has been updated to clarify this.

    --
    --Ford Prefect
  177. So basically... by Plekto · · Score: 1

    This means that Vista is a dead-end OS with a 2-3 year shelf-life at best. Somehow this shouldn't be any surprise to people.

  178. Comment by Bill Laing clarified by alienfluid · · Score: 4, Informative
    So it seems like it's the Server SKU that is going to be 64-bit only, and not the client OS:

    UPDATE | Microsoft's Alex Heaton has clarified the comment of Bill Laing, on which this story is based. "Bill Laing, a General Manager in the Microsoft Windows Server Division, has been quoted as saying that Windows Server 2008 will be the last 32-bit operating system. Bill is a server guy and indeed Windows Server 2008 is the last 32-bit server operating system - all future operating systems for server hardware from Microsoft beyond Windows Server 2008 will be 64-bit," Heaton said.

    "A few folks took Bill's comments on Windows Server and applied them to Windows Client deriving that Windows Vista would be the last 32-bit operating system. That is an incorrect extension. While Windows Vista includes both 32-bit and 64-bit and there is a growing community of drivers for 64-bit Windows Vista we have not decided when Windows Client will follow Windows Server and become 64-bit only."

  179. This absurdity of it all !! by leachim6 · · Score: 1
    This is absurd for multiple reasons
    1. Why would Microsoft dump its largest market ?
    2. Why do consumers need 64 bit by the next version of windows if they don't need it today
    3. Why would Microsoft assume the ubiquity of 64 bit cpu's ... there doesn't seem to be demand for them today ... why in
    This entire concept seems absurd ... it is Microsoft after all though
    --
    This comment was laboriously planned and extremely well thought out by Mike Donaghy @ http://mikedonaghy.org
    1. Re:This absurdity of it all !! by smash · · Score: 1
      It's not absurd at all.

      People who *buy* microsoft OSes typically buy hardware on a regular basis. Vista won't be "end of life" for at least 5 years if the track record of Win2k/WinXP is anything to go by.

      In 5 years time, your current PC will have either expired, or those who are interested in buying Microsoft's latest and greatest will have upgraded at *least* once.

      I doubt you'll be able to buy non-64 bit capable x86 within 12-18 months, if not already (haven't checked).

      Given that an Imac has quite severe RAM expansion limits, my bet is that it wouldn't be usable for Vista+1 in any case, even if it will run on a 32 bit cpu.

      As to why do consumers need 64 bit? For the most part, they don't. Really, most tasks you can get done with a Pentium 2 and Linux/Windows 98/etc. As developments in manufacturing tech advance though, the cost of manufacturing 64 bit parts drops rapidly towards the cost of producing 32, or 16, or 8 bit parts.

      Or, you can look at it this way... PCs are too slow. Really, if you want to be picky about it - *any* time i have to spend waiting for disk access, rendering, compression, etc is wasted time I'll never get back.

      There's little demand for 64 bit cpus today, because there's simply a lack of 64 bit software to make them relevant yet.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    2. Re:This absurdity of it all !! by smash · · Score: 1

      Err... by imac, i meant "mac mini"...

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    3. Re:This absurdity of it all !! by leachim6 · · Score: 1

      That is a good point , In 5 years I guess 64 bit hardware will be pretty ubiquitous
      I still don't think MOST consumers will benefit ... but more and more people are doing
      things such as Video Rendering/encoding and especially Gaming ...
      Maybe the 64 bits will be put to more use than I though

      --
      This comment was laboriously planned and extremely well thought out by Mike Donaghy @ http://mikedonaghy.org
  180. Obligatory by DragonHawk · · Score: 1

    When did this become about dicksizing?

    You must be new here.

    ;-)

    --

    dragonhawk@iname.microsoft.com
    I do not like Microsoft. Remove them from my email address.
  181. Microsofts decision a boon for Linux by lsatenstein · · Score: 1

    Linux will remain on 32 bit systems (as well as 64bitters) as it does now, for a long long time. Reason:== There are many many developers in less affluent countries who only have 32 bit machines. Vista is for the rich, thats all I have to say. It offers so little more than XP that I will continue with the latter. By the way, there is a clone of XP that is being tested. Wow. Will we have a clone of Vista, minus some look and feel?

    --
    Leslie Satenstein Montreal Quebec Canada