1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Upgrade 7000 to 7048 version.

Discussion in 'Windows 7' started by r.leale, 2009/03/15.

  1. 2009/03/15
    r.leale Lifetime Subscription

    r.leale Well-Known Member Thread Starter

    Joined:
    2002/01/17
    Messages:
    647
    Likes Received:
    4
    Hi All,

    After running Windows 7 version 7000 since its release, and having installed version 7022 on a friends computer to replace an invalid XP Pro, I decided to try the latest version. I upgraded my 7000 64 bit installation from a downloaded version 7048 iso file just to see how it would go.

    Booting from the DVD got the message 'Remove the dvd, boot the original OS, and then start the upgrade from within Windows'. I did this, selected 'Run Set-up' then 'Install now'. Windows copied temporary files, went on line to search for updates, and I selected 'Upgrade' Got the warning that it may take several hours and the Windows files were copied across. Then the new steps started - 'Identifying system files and settings to be gathered' then 'Identifying User files, settings and programs to be gathered'.

    Three re-boots during the upgrade but no user intervention needed, took longer than a clean install, about two hours, of which the longest periods were the identifying and gathering steps. Final re-boot, retap the unlock key, and up came my desktop with all my icons and shortcuts in place. All my installed programs have been found and are working.

    One unusual thing did happen though. Before I started the upgrade I had de-activated my Photoshop installation in case the upgrade went pear-shaped, but when I opened it to check its working it had been re-activated!

    I am now beginning to wonder why all the fuss about the differences between 64 and 32 bit installations. I have a 64 bit OS installed, and all my 32 bit apps are working perfectly, eg Mailwasher, Qimage, PocoMail, and all my hardware has the necessary drivers installed.

    I haven't had time to check out all the improvements yet in 7048 but it looks good! Must be getting close to the RC!

    Roger:D
     
  2. 2009/03/15
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,687
    Likes Received:
    107
    Please note that the only public release by Microsoft has been the 7000 build.
     

  3. to hide this advert.

  4. 2009/03/16
    r.leale Lifetime Subscription

    r.leale Well-Known Member Thread Starter

    Joined:
    2002/01/17
    Messages:
    647
    Likes Received:
    4
    Yes, I was aware of that Arie, but not really concerned for several reasons.

    a. If MS did not want these "leaked" versions to be used, they could require a new activation key.

    b. I am sure that MS are profiting from the useful feedback from these "leaked" versions.

    c. By allowing the continued use of these "leaked" versions MS are spared the pain of a Beta 2, which would be taken up by many thousands of users who would then bleat about MS sending out software with bugs.

    d. Are they really "leaked" or just let loose?

    Roger
     
  5. 2009/03/23
    perbear

    perbear Inactive

    Joined:
    2009/02/09
    Messages:
    3
    Likes Received:
    0
    With the chance of Arie hunting me with a whip; I had real problems with build 7048 and was very unsure if I should go for the (then) recently leaked 7057. In hindsight I was glad I did. I find it more stable. I have experienced that my folder structure is intact on my test computer but have not been able to bring my installed software with me from one build to the next.
     
  6. 2009/03/24
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    The problem with running builds that have not been released by MS is you have no idea if you are going to be running a build that may have known issues. And believe me, many 'interim' builds have known issues. These builds are not passed through the same testing regime as an official (public) release would be.
     
    Arie,
    #5

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.