Vista - Vista installation hangs up

Colin:
Currently the 2200+ has only XPSP2 installed with all updates.
Tomorrow I'll boot from the DVD so that a "Windows old" folder is created to
test the rollback function.


"Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
news:%23TeqxKFtGHA.4252@TK2MSFTNGP02.phx.gbl...
> My conclusion also, except that in addition to following the Upgrade
> Advisor's advice, I found that I needed to gather the data from the
> compatibility report at the start of Setup, exit Setup, remove the listed
> software, reboot XP, and then run Setup. That produced a clean upgrade.
> The wording of the compatibility report is too mild. Finding updates for
> programs is problematical once the upgrade is done because there are many
> cases where the update cannot be applied in Vista.
>
> The info is there and is accurate. Folks getting into trouble are
> regarding it too lightly or are mislead into thinking that they can just
> take care of things later.
>
>
> "Dennis Pack x64, v64 B2 (5384), O2007B2" <dennispack@nospamhotmail.com>
> wrote in message news:erHXUGFtGHA.3324@TK2MSFTNGP04.phx.gbl...
>> Mark:
>>
>> I decided to follow your lead on trying to perform an
>> upgrade installation of Vista x86 over XPSP2. Luckily I had downloaded
>> Vista x86 also because I've been testing Vista x64. I have an AMD 2200+
>> tower that I haven't used in 2 years that needed to be formatted and
>> setup to give to a friend's son for school. The system specifications are
>> AMD 2200+, GF440 video (64mb), NIT and modem with onboard sound, 512mb
>> ram. Before starting I installed all updates, performed a disk cleanup
>> and defragmentation. I uninstalled McAfee including the registry entries,
>> Power DVD and Nero. Then while running XPSP2 I performed an upgrade
>> installation. Vista basic x86 installed due to the system limitations and
>> the installation was clean. After the installation completed everything
>> worked all programs and files were accessible. Performing this type of
>> upgrade from XPSP2 didn't create a "Windows old" file so that there is no
>> way to rollback the installation or perform a repair installation, only a
>> format and clean installation of XPSP2. The conclusion reached by this
>> successful upgrade installation is to read all directions and remove
>> incompatible programs prior to performing the upgrade.
>>
>>
>>
>> "Mark D. VandenBeg" <mvan103@hotmail.com> wrote in message
>> news:ORo2vdEtGHA.1288@TK2MSFTNGP02.phx.gbl...
>>> Second try: same procedure with the exception of running Update Advisor.
>>> UA recommended uninstalling AIM and Norton AV 2003. Uninstalled both,
>>> same result. No Joy.
>>>
>>> Third try: After uninstalling AIM and NAV, went through the registry
>>> manually and cleaned out all Norton/Symantec/AOL references. Lo and
>>> Behold! Vista running, but with some errors.
>>>
>>> I started to track them down when the non-tech girlfriend reminded me it
>>> was her birthday. Oops... (48 hour pause in testing)
>>>
>>> Fourth Try: As above but also uninstalled Trillian before upgrade.
>>> Seemed to be okay. No obvious errors, but the system was visibly
>>> choking on something at shut down/"Sleep." Perhaps the AIM/MSN plug-ins
>>> for Trillian are installation issues?
>>>
>>> Fifth try: Clean install of Win XP Home SP2 with all updates and no
>>> other applications. Smooth and slick.
>>>
>>> Conclusions:
>>>
>>> 1. None of the problems were MSFT software-related. All were MSFT
>>> procedure-related. I offer that 30-40 % of people upgrading will not
>>> use UA. UA needs to be an automated part of the installation,
>>> slip-steamed in, or MSFT is going to have busy phones.
>>> 2. Software vendors need to make their programs install and uninstall
>>> better; way too many little bombs left behind It's almost inconceivable
>>> for coders to plan for every combination for a good install. (This is
>>> not news, unfortunately).
>>> 3. I need a PDA with a better calendar system!
>>>
>>> I hope this helps somebody.
>>>
>>
>>
>
>

As long as you understand that there is no rollback button. It is a tedious
and unreliable process at best. It wasn't meant for NT systems. Whatever
you do don't convert anything or mess with NTFS and you have a chance.

"Dennis Pack x64, v64B2 (5384), OPP2007B2" <dennispack@nospamhotmail.com>
wrote in message news:CC051F06-EA3B-406B-935D-AA544B50E7AA@microsoft.com...
> Colin:
> Currently the 2200+ has only XPSP2 installed with all updates.
> Tomorrow I'll boot from the DVD so that a "Windows old" folder is created
> to test the rollback function.
>
>
> "Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
> news:%23TeqxKFtGHA.4252@TK2MSFTNGP02.phx.gbl...
>> My conclusion also, except that in addition to following the Upgrade
>> Advisor's advice, I found that I needed to gather the data from the
>> compatibility report at the start of Setup, exit Setup, remove the listed
>> software, reboot XP, and then run Setup. That produced a clean upgrade.
>> The wording of the compatibility report is too mild. Finding updates for
>> programs is problematical once the upgrade is done because there are many
>> cases where the update cannot be applied in Vista.
>>
>> The info is there and is accurate. Folks getting into trouble are
>> regarding it too lightly or are mislead into thinking that they can just
>> take care of things later.
>>
>>
>> "Dennis Pack x64, v64 B2 (5384), O2007B2" <dennispack@nospamhotmail.com>
>> wrote in message news:erHXUGFtGHA.3324@TK2MSFTNGP04.phx.gbl...
>>> Mark:
>>>
>>> I decided to follow your lead on trying to perform an
>>> upgrade installation of Vista x86 over XPSP2. Luckily I had downloaded
>>> Vista x86 also because I've been testing Vista x64. I have an AMD 2200+
>>> tower that I haven't used in 2 years that needed to be formatted and
>>> setup to give to a friend's son for school. The system specifications
>>> are AMD 2200+, GF440 video (64mb), NIT and modem with onboard sound,
>>> 512mb ram. Before starting I installed all updates, performed a disk
>>> cleanup and defragmentation. I uninstalled McAfee including the registry
>>> entries, Power DVD and Nero. Then while running XPSP2 I performed an
>>> upgrade installation. Vista basic x86 installed due to the system
>>> limitations and the installation was clean. After the installation
>>> completed everything worked all programs and files were accessible.
>>> Performing this type of upgrade from XPSP2 didn't create a "Windows old"
>>> file so that there is no way to rollback the installation or perform a
>>> repair installation, only a format and clean installation of XPSP2. The
>>> conclusion reached by this successful upgrade installation is to read
>>> all directions and remove incompatible programs prior to performing the
>>> upgrade.
>>>
>>>
>>>
>>> "Mark D. VandenBeg" <mvan103@hotmail.com> wrote in message
>>> news:ORo2vdEtGHA.1288@TK2MSFTNGP02.phx.gbl...
>>>> Second try: same procedure with the exception of running Update
>>>> Advisor. UA recommended uninstalling AIM and Norton AV 2003.
>>>> Uninstalled both, same result. No Joy.
>>>>
>>>> Third try: After uninstalling AIM and NAV, went through the registry
>>>> manually and cleaned out all Norton/Symantec/AOL references. Lo and
>>>> Behold! Vista running, but with some errors.
>>>>
>>>> I started to track them down when the non-tech girlfriend reminded me
>>>> it was her birthday. Oops... (48 hour pause in testing)
>>>>
>>>> Fourth Try: As above but also uninstalled Trillian before upgrade.
>>>> Seemed to be okay. No obvious errors, but the system was visibly
>>>> choking on something at shut down/"Sleep." Perhaps the AIM/MSN
>>>> plug-ins for Trillian are installation issues?
>>>>
>>>> Fifth try: Clean install of Win XP Home SP2 with all updates and no
>>>> other applications. Smooth and slick.
>>>>
>>>> Conclusions:
>>>>
>>>> 1. None of the problems were MSFT software-related. All were MSFT
>>>> procedure-related. I offer that 30-40 % of people upgrading will not
>>>> use UA. UA needs to be an automated part of the installation,
>>>> slip-steamed in, or MSFT is going to have busy phones.
>>>> 2. Software vendors need to make their programs install and uninstall
>>>> better; way too many little bombs left behind It's almost
>>>> inconceivable for coders to plan for every combination for a good
>>>> install. (This is not news, unfortunately).
>>>> 3. I need a PDA with a better calendar system!
>>>>
>>>> I hope this helps somebody.
>>>>
>>>
>>>
>>
>>
>

Colin:
What I was trying to do is find a way easily possible for a person
with a single hard drive with only one partition to get from Vista x86 back
to Windows XP. I couldn't find a way to reinstall the "Windows old" folder.
With a OEM or retail disk there is no repair installation avenue available.
The overall finding is that if Vista x86 is installed the only rollback is
to format and reinstall Windows XP. I don't have a PC with a recovery
partition to test.


"Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
news:uyuyI8FtGHA.2036@TK2MSFTNGP05.phx.gbl...
> As long as you understand that there is no rollback button. It is a
> tedious and unreliable process at best. It wasn't meant for NT systems.
> Whatever you do don't convert anything or mess with NTFS and you have a
> chance.
>
> "Dennis Pack x64, v64B2 (5384), OPP2007B2" <dennispack@nospamhotmail.com>
> wrote in message
> news:CC051F06-EA3B-406B-935D-AA544B50E7AA@microsoft.com...
>> Colin:
>> Currently the 2200+ has only XPSP2 installed with all updates.
>> Tomorrow I'll boot from the DVD so that a "Windows old" folder is created
>> to test the rollback function.
>>
>>
>> "Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
>> news:%23TeqxKFtGHA.4252@TK2MSFTNGP02.phx.gbl...
>>> My conclusion also, except that in addition to following the Upgrade
>>> Advisor's advice, I found that I needed to gather the data from the
>>> compatibility report at the start of Setup, exit Setup, remove the
>>> listed software, reboot XP, and then run Setup. That produced a clean
>>> upgrade. The wording of the compatibility report is too mild. Finding
>>> updates for programs is problematical once the upgrade is done because
>>> there are many cases where the update cannot be applied in Vista.
>>>
>>> The info is there and is accurate. Folks getting into trouble are
>>> regarding it too lightly or are mislead into thinking that they can just
>>> take care of things later.
>>>
>>>
>>> "Dennis Pack x64, v64 B2 (5384), O2007B2" <dennispack@nospamhotmail.com>
>>> wrote in message news:erHXUGFtGHA.3324@TK2MSFTNGP04.phx.gbl...
>>>> Mark:
>>>>
>>>> I decided to follow your lead on trying to perform an
>>>> upgrade installation of Vista x86 over XPSP2. Luckily I had downloaded
>>>> Vista x86 also because I've been testing Vista x64. I have an AMD 2200+
>>>> tower that I haven't used in 2 years that needed to be formatted and
>>>> setup to give to a friend's son for school. The system specifications
>>>> are AMD 2200+, GF440 video (64mb), NIT and modem with onboard sound,
>>>> 512mb ram. Before starting I installed all updates, performed a disk
>>>> cleanup and defragmentation. I uninstalled McAfee including the
>>>> registry entries, Power DVD and Nero. Then while running XPSP2 I
>>>> performed an upgrade installation. Vista basic x86 installed due to the
>>>> system limitations and the installation was clean. After the
>>>> installation completed everything worked all programs and files were
>>>> accessible. Performing this type of upgrade from XPSP2 didn't create a
>>>> "Windows old" file so that there is no way to rollback the installation
>>>> or perform a repair installation, only a format and clean installation
>>>> of XPSP2. The conclusion reached by this successful upgrade
>>>> installation is to read all directions and remove incompatible programs
>>>> prior to performing the upgrade.
>>>>
>>>>
>>>>
>>>> "Mark D. VandenBeg" <mvan103@hotmail.com> wrote in message
>>>> news:ORo2vdEtGHA.1288@TK2MSFTNGP02.phx.gbl...
>>>>> Second try: same procedure with the exception of running Update
>>>>> Advisor. UA recommended uninstalling AIM and Norton AV 2003.
>>>>> Uninstalled both, same result. No Joy.
>>>>>
>>>>> Third try: After uninstalling AIM and NAV, went through the registry
>>>>> manually and cleaned out all Norton/Symantec/AOL references. Lo and
>>>>> Behold! Vista running, but with some errors.
>>>>>
>>>>> I started to track them down when the non-tech girlfriend reminded me
>>>>> it was her birthday. Oops... (48 hour pause in testing)
>>>>>
>>>>> Fourth Try: As above but also uninstalled Trillian before upgrade.
>>>>> Seemed to be okay. No obvious errors, but the system was visibly
>>>>> choking on something at shut down/"Sleep." Perhaps the AIM/MSN
>>>>> plug-ins for Trillian are installation issues?
>>>>>
>>>>> Fifth try: Clean install of Win XP Home SP2 with all updates and no
>>>>> other applications. Smooth and slick.
>>>>>
>>>>> Conclusions:
>>>>>
>>>>> 1. None of the problems were MSFT software-related. All were MSFT
>>>>> procedure-related. I offer that 30-40 % of people upgrading will not
>>>>> use UA. UA needs to be an automated part of the installation,
>>>>> slip-steamed in, or MSFT is going to have busy phones.
>>>>> 2. Software vendors need to make their programs install and uninstall
>>>>> better; way too many little bombs left behind It's almost
>>>>> inconceivable for coders to plan for every combination for a good
>>>>> install. (This is not news, unfortunately).
>>>>> 3. I need a PDA with a better calendar system!
>>>>>
>>>>> I hope this helps somebody.
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
>

The Windows.old folder is not functional for rolling back. It is an old
Win9x feature carried over to NT. Your findings are consistent with the
warning on GetReady:

"In addition, once you install Windows Vista Beta 2 (or RC1) you cannot roll
back to the previous operating system installation-you will either have to
acquire and install the final released edition of Windows Vista or reinstall
a previous edition of Windows."

"Dennis Pack x64, v64B2 (5384), OPP2007B2" <dennispack@nospamhotmail.com>
wrote in message news:2384A49D-E545-4DCD-9828-1BC7694BBEF7@microsoft.com...
> Colin:
> What I was trying to do is find a way easily possible for a person
> with a single hard drive with only one partition to get from Vista x86
> back to Windows XP. I couldn't find a way to reinstall the "Windows old"
> folder. With a OEM or retail disk there is no repair installation avenue
> available. The overall finding is that if Vista x86 is installed the only
> rollback is to format and reinstall Windows XP. I don't have a PC with a
> recovery partition to test.
>
>
> "Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
> news:uyuyI8FtGHA.2036@TK2MSFTNGP05.phx.gbl...
>> As long as you understand that there is no rollback button. It is a
>> tedious and unreliable process at best. It wasn't meant for NT systems.
>> Whatever you do don't convert anything or mess with NTFS and you have a
>> chance.
>>
>> "Dennis Pack x64, v64B2 (5384), OPP2007B2" <dennispack@nospamhotmail.com>
>> wrote in message
>> news:CC051F06-EA3B-406B-935D-AA544B50E7AA@microsoft.com...
>>> Colin:
>>> Currently the 2200+ has only XPSP2 installed with all updates.
>>> Tomorrow I'll boot from the DVD so that a "Windows old" folder is
>>> created to test the rollback function.
>>>
>>>
>>> "Colin Barnhorst" <colinbarharst(remove)@msn.com> wrote in message
>>> news:%23TeqxKFtGHA.4252@TK2MSFTNGP02.phx.gbl...
>>>> My conclusion also, except that in addition to following the Upgrade
>>>> Advisor's advice, I found that I needed to gather the data from the
>>>> compatibility report at the start of Setup, exit Setup, remove the
>>>> listed software, reboot XP, and then run Setup. That produced a clean
>>>> upgrade. The wording of the compatibility report is too mild. Finding
>>>> updates for programs is problematical once the upgrade is done because
>>>> there are many cases where the update cannot be applied in Vista.
>>>>
>>>> The info is there and is accurate. Folks getting into trouble are
>>>> regarding it too lightly or are mislead into thinking that they can
>>>> just take care of things later.
>>>>
>>>>
>>>> "Dennis Pack x64, v64 B2 (5384), O2007B2"
>>>> <dennispack@nospamhotmail.com> wrote in message
>>>> news:erHXUGFtGHA.3324@TK2MSFTNGP04.phx.gbl...
>>>>> Mark:
>>>>>
>>>>> I decided to follow your lead on trying to perform an
>>>>> upgrade installation of Vista x86 over XPSP2. Luckily I had
>>>>> downloaded Vista x86 also because I've been testing Vista x64. I have
>>>>> an AMD 2200+ tower that I haven't used in 2 years that needed to be
>>>>> formatted and setup to give to a friend's son for school. The system
>>>>> specifications are AMD 2200+, GF440 video (64mb), NIT and modem with
>>>>> onboard sound, 512mb ram. Before starting I installed all updates,
>>>>> performed a disk cleanup and defragmentation. I uninstalled McAfee
>>>>> including the registry entries, Power DVD and Nero. Then while running
>>>>> XPSP2 I performed an upgrade installation. Vista basic x86 installed
>>>>> due to the system limitations and the installation was clean. After
>>>>> the installation completed everything worked all programs and files
>>>>> were accessible. Performing this type of upgrade from XPSP2 didn't
>>>>> create a "Windows old" file so that there is no way to rollback the
>>>>> installation or perform a repair installation, only a format and clean
>>>>> installation of XPSP2. The conclusion reached by this successful
>>>>> upgrade installation is to read all directions and remove incompatible
>>>>> programs prior to performing the upgrade.
>>>>>
>>>>>
>>>>>
>>>>> "Mark D. VandenBeg" <mvan103@hotmail.com> wrote in message
>>>>> news:ORo2vdEtGHA.1288@TK2MSFTNGP02.phx.gbl...
>>>>>> Second try: same procedure with the exception of running Update
>>>>>> Advisor. UA recommended uninstalling AIM and Norton AV 2003.
>>>>>> Uninstalled both, same result. No Joy.
>>>>>>
>>>>>> Third try: After uninstalling AIM and NAV, went through the registry
>>>>>> manually and cleaned out all Norton/Symantec/AOL references. Lo and
>>>>>> Behold! Vista running, but with some errors.
>>>>>>
>>>>>> I started to track them down when the non-tech girlfriend reminded me
>>>>>> it was her birthday. Oops... (48 hour pause in testing)
>>>>>>
>>>>>> Fourth Try: As above but also uninstalled Trillian before upgrade.
>>>>>> Seemed to be okay. No obvious errors, but the system was visibly
>>>>>> choking on something at shut down/"Sleep." Perhaps the AIM/MSN
>>>>>> plug-ins for Trillian are installation issues?
>>>>>>
>>>>>> Fifth try: Clean install of Win XP Home SP2 with all updates and no
>>>>>> other applications. Smooth and slick.
>>>>>>
>>>>>> Conclusions:
>>>>>>
>>>>>> 1. None of the problems were MSFT software-related. All were MSFT
>>>>>> procedure-related. I offer that 30-40 % of people upgrading will not
>>>>>> use UA. UA needs to be an automated part of the installation,
>>>>>> slip-steamed in, or MSFT is going to have busy phones.
>>>>>> 2. Software vendors need to make their programs install and uninstall
>>>>>> better; way too many little bombs left behind It's almost
>>>>>> inconceivable for coders to plan for every combination for a good
>>>>>> install. (This is not news, unfortunately).
>>>>>> 3. I need a PDA with a better calendar system!
>>>>>>
>>>>>> I hope this helps somebody.
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>