Windows Vista RC1 - Upgrade from Windows XP x64? -- NOT!

"We were guessing about Iraq. We are not guessing about Iran. If they get nuclear weapons they will foster terror on a scale that cannot be imagined." -- Benjamin Netanyahu



Well, they put out RC1 today and I think I have been getting wiser in my young age with BETAs and stuff -- I've been smart enough to hold off on the various Vista Betas. Not a bad decision after reading some of the horror story blog entries.

But you know, "RC1" is by definition so substantially a final release that I decided to down it and install on my second hard drive - the one that currently runs Windows XP x64 - and which I hardly use anyway.

So I burned the DVD, booted up into the XP OS, and inserted the DVD and let it come up. Guess what? The Upgrade section is greyed out!


I'm like, "Wait a minute! This is a Release Candidate!"

Bottom line, this is what people are going to get when they buy this and you can't even upgrade over a valid Windows XP x64 edition?

Well then, Vista can wait. I don't know what the technical explanation or rationale for this is, but it's pretty poor in my book! Guys, 64-bit has come of age. If you want feedback from developers and BETA testers on your last push to bring out the product, then give them the tools to upgrade over an existing 64-bit OS, for Christ's sake!

Maybe I'll put it on my notebook which runs XP 32 bit. And then, maybe I'll just make a new partition and put it on that - although I'm not thrilled at having to install second copies of all my "stuff" just to try out this sucker...

N.B. -- I did make a new partition on my x64 Turion notebook, and installed Vista RC1 x64 on it. It seemed to run very nicely, but it didn't recognize my sound card at all. And this is a plain- vanilly Gateway that is extremely popular, they sell out of Best Buy like hotcakes off a grill. Microsoft, you guys need to spend more time on the 64-bit stuff - the drivers, being able to upgrade over an existing Windows XP installation, and more. I don't care if it takes you an extra six months. Get it right -- I can wait!

Comments

  1. peterbromberg4:35 PM

    Sorry to sound so "moronic", pal, but here is the detail from the download page on Microsoft Connect:

    Title Windows Vista RC1 (v5600-16384) for X86 and X64 (English)
    Release Date 9/1/2006
    Size 6,261.47 MB
    Version RC1 (v5600-16384)
    Category Build
    Milestone RC1

    X86
    CRC: 0xB3519FCA
    SHA: 0xE00B4EBBC81FB420CF047973B95A9CFB7CDF51B7

    vista_5600.16384.060829-2230_x86fre_client-LR1CFRE_EN_DVD.iso


    X64
    CRC: 0x59C867D0
    SHA: 0x8E4DE7A72C828A3543FF1663243EB0836DA07EEA

    vista_5600.16384.060829-2230_x64fre_client-LR1CxFRE_EN_DVD.iso




    Distribution Source:
    United States Europe Asia

    Files in Download:
    vista_5600.16384.060829-2230_x86fre_client-LR1CFRE_EN_DVD.iso, 2,584.25 MB

    vista_5600.16384.060829-2230_x64fre_client-LR1CxFRE_EN_DVD.iso, 3,677.22 MB

    -- do you see the download marked x64? That's the one I burned, my friend.

    ReplyDelete
  2. Anonymous12:20 AM

    I have installed only 32bit myself on clean install but looking around on forums on I believe upgrading XP to Vista is done when you are all ready booted into XP then insert Vista CD then follow instructions to upgrade not booting up from CD where you are correct only option is installing Vista. Did you try within XP?

    ReplyDelete
  3. peterbromberg6:23 AM

    Yup. Thanks for trying to help though!

    ReplyDelete
  4. Anonymous8:13 PM

    ya... it sucks. I installed it nicely in in laptop from xp sp2... but the 64 bit wont upgrade. Now it si a pain to move 80 GB of data :(

    Kaustav
    photoshoot.in

    ReplyDelete
  5. Anonymous10:30 PM

    Bad news -- I've just downloaded the RTM from MSDN to upgrade my Win XP x64 to Vista x64 and it's the same case in the RC as it is in the RC (true to the term 'RC').

    I'm debating if I want to upgrade at all, because I don't feel up to the week long task of getting all of the apps reinstalled and their options set the way I fancy.

    I'm bummed. MSFT, Please give me an upgrade tool!

    -Ryan

    ReplyDelete
  6. peterbromberg6:44 AM

    Heh. Don't hold your breath, I've already given up on it. Apparently Microsoft feels that their 64-bit OS versions are second-class citizens.

    ReplyDelete
  7. Anonymous5:53 PM

    xp x64 seemed to be an experiment gone wrong at MS. By not really understanding how to build a multi-target (32 & 64 bit) OS, they did what seemed to make sense..
    With vista they corrected many of these issues.

    basically all the bits are in the wrong places. so in order to "upgrade" they'd have to make sever registry changes, alter install paths, etc. (OR -- just leave things as is, but it'd be difficult for the user to maintain later).

    So, from their perspective it probably just seems like the number of x64 installations that would upgrade to vista aren't worth the development time it would take to write and test all the cleanup code.

    So, their solution I think is to give you the transfer cable software which will shove all your data onto an external drive.. you then do a clean install, re-install all your apps, and then transfer back your data and settings.

    I'd think that if they can sucessfully do the transfer back and forth, they should be able to automate that process in the upgrade phase, but I imagine the application installation paths and registry entries are the big problem

    ReplyDelete
  8. peterbromberg6:09 PM

    Right, but you are commenting on a post that I made a long time ago. Things have changed a lot since then. I run Vista x64 and it's great.

    ReplyDelete

Post a Comment

Popular posts from this blog

Some observations on Script Callbacks, "AJAX", "ATLAS" "AHAB" and where it's all going.

I've taken a more than cursory interest in the whole Remote Scripting (.NET species) vs. AJAX and now ATLAS discussion, mostly because I started using Remote Scripting since Microsoft first released it, and because I continued to refine it after seeing Brent Ashley's excellent work with JSRS, which was one of the first "real" cross-browser solutions back in 2000 (that's the turn of the Century for you history buffs). Now Bertrand Leroy, a Microsoft guy whose work I like , has authored some very interesting ASP.NET 2.0 script callback stuff that he points to on his blog, and he is obviously (at least, to me he is) involved quite heavily in the development of this new ATLAS infrastructure that they'll preview at PDC. Leroy's most recent post brings to the surface what I agree are the major differences between the "AJAX a - la .NET" approach as popularized by Michael Swartz with his AJAX.NET library, and Leroy's RefreshPanel, the ASP.NET 2.0 b
Read more

IE7 - Vista: "Internet Explorer has stopped Working"

Image
This one was a bitch. All of a sudden for no reason at all, out of the blue, I get this dialog "internet Explorer has stopped working". I didn't install any new software, crap- I didn't do anything! So here I am using FIREFART to go on the internet and find out what to do! Damn! Good thing I've got the sucker on the same machine (I'm not "anti-Firefox", i just don't use it that much except to check my page renderings). The Fix The fix (at least for me): 1) Go into Control Panel, and choose "Internet Options". 2) Under the "Advanced" tab, press the "RESET" button at the lower right: Don't ask me why this happens, or why the fix works. That's a BUG, D00D - I don't care how you slice it!
Read more

FIREFOX / IE Word-Wrap, Word-Break, TABLES FIX

One of the most annoying things a developer (who would normally delight in writing code, not futzing with markup) can have is getting rendering issues between different browsers. The two biggest players are of course Internet Exploder and Firefart (as I lovingly like to refer to each). In most cases that's going to take care of 98 percent of your total site traffic. IE has had a proprietary "word-break" style attribute for a long time, and this made it into the CSS 3.0 spec. But that doesn't necessarily help you with Firefox right now. Firefox literally - (and I consider this completely idiotic, since it's been in their bug database for FIVE YEARS) does not have a reliable CSS style element to force table cell content to break in the middle of a word in order to stop the content from expanding your table / div off the page or over other content on the page. Here's a partial fix, which will work for most tables and browsers. The style declaration (I call it m
Read more