C
Colin Barnhorst
Guest
Re: Vista Ultimate 32-Bit to 64-Bit
John, I just doublechecked my last reply and confirmed what I said. I have
Vista Home Basic x64 running in a VMWare Workstation 6 vm and I have a VHP
upgrade edition product key, so I booted the vm with the x64 dvd, entered
the upgrade pk, and Setup proceeded without instructing me to run Setup from
existing Windows like it would if I had booted with the x86 dvd and entered
the same upgrade pk. Same bitness is not a rule. It is simply the
difference in behavior between x86 Setup and x64 Setup when an upgrade pk is
used.
"John Barnes" <jbarnes@email.net> wrote in message
news:Oy5odMEiIHA.4076@TK2MSFTNGP05.phx.gbl...
> Except that upgrade pk's for the same bittness must be run from the
> desktop, not the DVD. Such will be stated if the DVD is inserted and an
> upgrade pk code entered. Only repairs are available from the DVD.
>
> "Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
> news:E31CB557-1B77-433C-B451-D2B656072148@microsoft.com...
>> Inline
>>
>>> Upgrade PKs are not eligible for full "clean" install path.
>> Incorrect. It has nothing to do with the PK (license). It is a software
>> matter. The installation methodology is always at the convenience of the
>> user. Microsoft builds Setup to handle the majority of installs, but any
>> method is acceptible because the user is still bound by the terms of the
>> EULA.
>>
>>>method 2 details provided assume the
>>> original installation of Vista x86 was an upgrade PK also (from XP or
>>> other
>>> valid path.)
>> It may assume that but it is clearly wrong. Vista has always been listed
>> in the upgrade matrix as eligible for upgrade to Vista and the bitness
>> has never been a distinction. It is just simply and plainly an error to
>> instruct a user to install XP when XP may not even have been used on the
>> computer. There are a bunch of computers on sale right now that don't
>> even have XP drivers.
>>
>>>Even though OEM, it is a full license
>> There is no "full" license. The EULA is just the EULA. There are retail
>> and OEM EULAs. The retail EULAs contain wording that apply to upgrades,
>> but there are not seperate "full" and "upgrade" retail EULAs.
>>
>>>and Method 1 applies to get the individual to Vista HP x64.
>> Why in the world would a user have to upgrade from VHP x86 to VHP x64
>> before upgrading to VU x64? Nonsense. The user can just stick his VU
>> x64 dvd in the machine, boot, and enter the upgrade pk. x64 Setup will
>> find an eligible copy of Windows already installed and simply proceed.
>> The VHP x86 migration to VHP x64 would have been a custom install anyway
>> so there is absolutely nothing gained by such a step because all software
>> has to be reinstalled anyway.
>>
>>> If the individual desires to go straight to Vista U x64 with an upgrade
>>> PK,
>>> skipping the version for which they have a full version license, then
>>> Method
>>> 2 is required to meet the EULA.
>> Once again, the EULA does not dictate installation methodology. Read the
>> EULA. In section 14 all that is required is that the user OWN a license
>> eligible for upgrade. Installing the software for which the license will
>> be superceded is not required. In fact, you can upgrade over a retail XP
>> installation, for example, but use a Win2k license that has been sitting
>> on your shelf and then be able to use the XP on another machine later.
>> You can decide that you want the Win2k license superceded so that you can
>> reuse the XP license even though Win2k is not on the machine. The
>> superceded license does not have to be for installed software for it to
>> be the eligible license. It is called "assigning". The mere fact that
>> an operating system license is installed on the computer being upgraded
>> does not force the user to supercede that license. It is the user's
>> choice and if he has another eligible license he may assign it. Don't
>> confuse installation methodology with licensing.
>>
>>
>>
>>>
>> "Mark" <jmhonzell@nospam.insightbb.com> wrote in message
>> news:%236qh4JCiIHA.5260@TK2MSFTNGP03.phx.gbl...
>>> Method 2 makes one important assumption, that the individual installing
>>> x64
>>> has an upgrade PK.
>>>
>>> Upgrade PKs are not eligible for full "clean" install path. There may be
>>> shortcuts to circumvent the method, but it is still an upgrade license.
>>> Since x64 requires a clean install, the method 2 details provided assume
>>> the
>>> original installation of Vista x86 was an upgrade PK also (from XP or
>>> other
>>> valid path.) In this light, the original OS used for the original
>>> upgrade
>>> must be installed first to meet the upgrade path requirements.
>>>
>>> In the original post, Vista HP x86 OEM is already installed on his new
>>> computer. Even though OEM, it is a full license and Method 1 applies to
>>> get
>>> the individual to Vista HP x64. From there, he may upgrade to Vista U
>>> x64
>>> with his upgade PK.
>>>
>>> If the individual desires to go straight to Vista U x64 with an upgrade
>>> PK,
>>> skipping the version for which they have a full version license, then
>>> Method
>>> 2 is required to meet the EULA.
>>>
>>> It may work by your method, but it definately works as written and is
>>> not a
>>> mistake.
>>>
>>>
>>> "Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
>>> news:362A7F9D-09DB-463B-A622-A6FBECC3D276@microsoft.com...
>>>> I have read it before and Method 2 under "Installing a 64-bit version
>>>> of
>>>> Windows Vista on computer that is running a 32-bit version of Windows
>>> Vista"
>>>> is obviously wrong.
>>>>
>>>> It cannot be necessary to install Windows XP. It is an obvious
>>>> mistake.
>>>> Stop a moment and think about it. Reread the title of the section. It
>>>> is
>>>> about installing Vista x64 on Vista x86, not on XP. It simply cannot
>>>> be
>>>> correct because the user may very well not even own XP. It might be
>>>> his
>>>> first computer and came with Vista x86 preinstalled. Where is such a
>>>> user
>>>> supposed to get this XP?
>>>>
>>>> In fact no operating system is necessary at all if the user wants to
>>> install
>>>> twice, once without a pk and the second time with one.
>>>>
>>>> "Mark" <jmhonzell@nospam.insightbb.com> wrote in message
>>>> news:27AE19E4-6E6F-429D-BF66-342536D7BBDE@microsoft.com...
>>>> > My apologies. Thanks for keeping it straight Colin.
>>>> > I misread the original post.
>>>> > The link provided is still correct, just a different section applied.
>>>> > I always try to provide a source. So, read the MS document.
>>>> > (That way you won't curse us when we give you the wrong instruction.)
>>>> >
>>>> >
>>>> > "Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
>>>> > news:93A116FB-1C49-4E79-A9F5-4F12C1D29EC8@microsoft.com...
>>>> >>> Most likely, his VHP is OEM which is not eligible to move to x64.
>>>> >>
>>>> >> Yes it is. (Although it is true that a preinstalled VHP x86 does
>>>> >> not
>>>> >> qualify a person to order a free x64 dvd from MS.)
>>>> >>
>>>> >>> Since he has a VU upgrade PK, he would have to take the path of
>>>> >>> reverting to XP first.
>>>> >>
>>>> >> What XP? He has never had XP on this computer. He said he
>>>> >> purchased
>>> the
>>>> >> computer with VHP preinstalled.
>>>> >>
>>>> >> He upgraded already to Vista Ultimate x86. Vista is always eligible
>>> for
>>>> >> upgrade to Vista. All he has to do is use his upgrade edition
>>>> >> product
>>>> >> key again and install Vista Ultimate x64. As soon as he inputs the
>>>> >> pk,
>>>> >> Setup will search for and find an eligible copy of Windows on his
>>>> >> computer (Vista Ultimate x86). There is no need to "revert" to
>>> anything.
>>>> >>
>>>> >> "Mark" <jmhonzell@nospam.insightbb.com> wrote in message
>>>> >> news:1EFA68BC-2C16-4CE3-AD09-93C19457B7F0@microsoft.com...
>>>> >>> Most likely, his VHP is OEM which is not eligible to move to x64.
>>>> >>> Since he has a VU upgrade PK, he would have to take the path of
>>>> >>> reverting to XP first.
>>>> >>>
>>>> >>> "Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
>>>> >>> news
AD4E40E-661A-48B1-A585-D3412083DE2F@microsoft.com...
>>>> >>>> No it doesn't. A copy of Vista is eligible for an upgrade to
>>>> >>>> Vista.
>>>> >>>> The user who has a copy of VHP x86 preinstalled can upgrade to
>>>> >>>> Vista
>>>> >>>> Ultimate x64 by booting with the x64 dvd and entering his upgrade
>>>> >>>> edition pk. Setup will find the VHP installed and allow the user
>>>> >>>> to
>>>> >>>> proceed since Vista is an eligible product (see the upgrade
>>>> >>>> matrix).
>>>> >>>> The user is not required to perform the upgrade from the desktop
>>>> >>>> of
>>> the
>>>> >>>> existing Windows (in fact he can't). He may then perform a clean
>>>> >>>> install (reformat if he wishes) or perform a custom install to any
>>>> >>>> available volume. 64bit upgrades are very different from 32bit
>>>> >>>> upgrades. I have done these upgrades myself.
>>>> >>>>
>>>> >>>> "Mark" <jmhonzell@nospam.insightbb.com> wrote in message
>>>> >>>> news:BC3B1162-E171-4CE3-8B4A-278B575FE1C1@microsoft.com...
>>>> >>>>> Most likely your current HP version is OEM.
>>>> >>>>> http://support.microsoft.com/kb/932795/
>>>> >>>>> (An upgrade Product Key requires that you revert to XP SP2 prior
>>>> >>>>> to
>>>> >>>>> using it to install x64 from Vista x86.)
>>>> >>>>>
>>>> >>>>> See section:
>>>> >>>>> Installing Vista x64 on a system already running 32-bit version
>>>> >>>>> of
>>>> >>>>> Vista.
>>>> >>>>> Just follow the instructions.
>>>> >>>>>
>>>> >>>>> Key factors in being successful:
>>>> >>>>> 1. Make sure all drivers needed are available out there. They
>>>> >>>>> must
>>> be
>>>> >>>>> x64 versions to work.
>>>> >>>>> Some components still have trouble until x64 is installed. You
>>> may
>>>> >>>>> want to remove them first:
>>>> >>>>> a. Creative sound cards.
>>>> >>>>> b. SLI graphics
>>>> >>>>> c. Mixed SATA and IDE drives. (only have one installed while
>>>> >>>>> installing x64)
>>>> >>>>> When done, put them back in one at a time.
>>>> >>>>> 2. When installing, elect not to update Vista until you are all
>>> done.
>>>> >>>>> 3. If for some reason, it errs prior to complete install, just
>>>> >>>>> start
>>>> >>>>> the x64 DVD again. You don't have to install XP again.
>>>> >>>>>
>>>> >>>>> To make uses of all memory, ensure you "remap" the memory hole
>>> through
>>>> >>>>> your BIOS. If this function is not available in the BIOS, you may
>>> need
>>>> >>>>> to update the BIOS. If still not available, I would question the
>>> need
>>>> >>>>> to go to x64.
>>>> >>>>>
>>>> >>>>> As everyone will be happy to point out semantics... this is not
>>>> >>>>> an
>>>> >>>>> upgrade, but a clean install. Nothing will survive so copy all
>>>> >>>>> your
>>>> >>>>> files first to a safe location.
>>>> >>>>> E-mail addresses transfer by WET.
>>>> >>>>>
>>>> >>>>> Good luck!
>>>> >>>>> Let us know how it goes.
>>>> >>>>> I've been on x64 since Vista was released and it's rock solid.
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> "Seidell23231" <Seidell23231@discussions.microsoft.com> wrote in
>>>> >>>>> message
>>>> >>>>> news:60BE1E54-48E0-4BA1-9874-C2A3B292E050@microsoft.com...
>>>> >>>>>> Hello ALL,
>>>> >>>>>>
>>>> >>>>>> About 8 months ago I purchased Vista Ultimate Upgrade, because I
>>> was
>>>> >>>>>> upgrading the PC I had than from XP Pro to Vista Ultimate.
>>> Upgraded
>>>> >>>>>> all went
>>>> >>>>>> smooth no problems.
>>>> >>>>>>
>>>> >>>>>> Fast forward to today. The old PC has passed on and a New PC
>>>> >>>>>> (HP
>>>> >>>>>> Pavillion
>>>> >>>>>> Elite m9150f with Intel Core 2 Quad) is home and getting setup.
>>> The
>>>> >>>>>> new PC
>>>> >>>>>> came with Vista Home Premium 32-Bit. I have upgraded it to
>>>> >>>>>> Vista
>>>> >>>>>> Ultimate
>>>> >>>>>> 32-Bit, BUT I want to use the 64-Bit since my PC can handle it.
>>>> >>>>>>
>>>> >>>>>> My Question is this ~~ Can I upgrade to Vista 64 with my current
>>>> >>>>>> allocation?
>>>> >>>>>> If YES, please explain, if NO please explain how to fix so I can
>>> use
>>>> >>>>>> 64-Bit.
>>>> >>>>>>
>>>> >>>>>> Thanks ~~ Gunny
>>>> >>>>>
>>>> >>>>
>>>> >>>
>>>> >>
>>>> >
>>>>
>>>
>>>
>>
>
John, I just doublechecked my last reply and confirmed what I said. I have
Vista Home Basic x64 running in a VMWare Workstation 6 vm and I have a VHP
upgrade edition product key, so I booted the vm with the x64 dvd, entered
the upgrade pk, and Setup proceeded without instructing me to run Setup from
existing Windows like it would if I had booted with the x86 dvd and entered
the same upgrade pk. Same bitness is not a rule. It is simply the
difference in behavior between x86 Setup and x64 Setup when an upgrade pk is
used.
"John Barnes" <jbarnes@email.net> wrote in message
news:Oy5odMEiIHA.4076@TK2MSFTNGP05.phx.gbl...
> Except that upgrade pk's for the same bittness must be run from the
> desktop, not the DVD. Such will be stated if the DVD is inserted and an
> upgrade pk code entered. Only repairs are available from the DVD.
>
> "Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
> news:E31CB557-1B77-433C-B451-D2B656072148@microsoft.com...
>> Inline
>>
>>> Upgrade PKs are not eligible for full "clean" install path.
>> Incorrect. It has nothing to do with the PK (license). It is a software
>> matter. The installation methodology is always at the convenience of the
>> user. Microsoft builds Setup to handle the majority of installs, but any
>> method is acceptible because the user is still bound by the terms of the
>> EULA.
>>
>>>method 2 details provided assume the
>>> original installation of Vista x86 was an upgrade PK also (from XP or
>>> other
>>> valid path.)
>> It may assume that but it is clearly wrong. Vista has always been listed
>> in the upgrade matrix as eligible for upgrade to Vista and the bitness
>> has never been a distinction. It is just simply and plainly an error to
>> instruct a user to install XP when XP may not even have been used on the
>> computer. There are a bunch of computers on sale right now that don't
>> even have XP drivers.
>>
>>>Even though OEM, it is a full license
>> There is no "full" license. The EULA is just the EULA. There are retail
>> and OEM EULAs. The retail EULAs contain wording that apply to upgrades,
>> but there are not seperate "full" and "upgrade" retail EULAs.
>>
>>>and Method 1 applies to get the individual to Vista HP x64.
>> Why in the world would a user have to upgrade from VHP x86 to VHP x64
>> before upgrading to VU x64? Nonsense. The user can just stick his VU
>> x64 dvd in the machine, boot, and enter the upgrade pk. x64 Setup will
>> find an eligible copy of Windows already installed and simply proceed.
>> The VHP x86 migration to VHP x64 would have been a custom install anyway
>> so there is absolutely nothing gained by such a step because all software
>> has to be reinstalled anyway.
>>
>>> If the individual desires to go straight to Vista U x64 with an upgrade
>>> PK,
>>> skipping the version for which they have a full version license, then
>>> Method
>>> 2 is required to meet the EULA.
>> Once again, the EULA does not dictate installation methodology. Read the
>> EULA. In section 14 all that is required is that the user OWN a license
>> eligible for upgrade. Installing the software for which the license will
>> be superceded is not required. In fact, you can upgrade over a retail XP
>> installation, for example, but use a Win2k license that has been sitting
>> on your shelf and then be able to use the XP on another machine later.
>> You can decide that you want the Win2k license superceded so that you can
>> reuse the XP license even though Win2k is not on the machine. The
>> superceded license does not have to be for installed software for it to
>> be the eligible license. It is called "assigning". The mere fact that
>> an operating system license is installed on the computer being upgraded
>> does not force the user to supercede that license. It is the user's
>> choice and if he has another eligible license he may assign it. Don't
>> confuse installation methodology with licensing.
>>
>>
>>
>>>
>> "Mark" <jmhonzell@nospam.insightbb.com> wrote in message
>> news:%236qh4JCiIHA.5260@TK2MSFTNGP03.phx.gbl...
>>> Method 2 makes one important assumption, that the individual installing
>>> x64
>>> has an upgrade PK.
>>>
>>> Upgrade PKs are not eligible for full "clean" install path. There may be
>>> shortcuts to circumvent the method, but it is still an upgrade license.
>>> Since x64 requires a clean install, the method 2 details provided assume
>>> the
>>> original installation of Vista x86 was an upgrade PK also (from XP or
>>> other
>>> valid path.) In this light, the original OS used for the original
>>> upgrade
>>> must be installed first to meet the upgrade path requirements.
>>>
>>> In the original post, Vista HP x86 OEM is already installed on his new
>>> computer. Even though OEM, it is a full license and Method 1 applies to
>>> get
>>> the individual to Vista HP x64. From there, he may upgrade to Vista U
>>> x64
>>> with his upgade PK.
>>>
>>> If the individual desires to go straight to Vista U x64 with an upgrade
>>> PK,
>>> skipping the version for which they have a full version license, then
>>> Method
>>> 2 is required to meet the EULA.
>>>
>>> It may work by your method, but it definately works as written and is
>>> not a
>>> mistake.
>>>
>>>
>>> "Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
>>> news:362A7F9D-09DB-463B-A622-A6FBECC3D276@microsoft.com...
>>>> I have read it before and Method 2 under "Installing a 64-bit version
>>>> of
>>>> Windows Vista on computer that is running a 32-bit version of Windows
>>> Vista"
>>>> is obviously wrong.
>>>>
>>>> It cannot be necessary to install Windows XP. It is an obvious
>>>> mistake.
>>>> Stop a moment and think about it. Reread the title of the section. It
>>>> is
>>>> about installing Vista x64 on Vista x86, not on XP. It simply cannot
>>>> be
>>>> correct because the user may very well not even own XP. It might be
>>>> his
>>>> first computer and came with Vista x86 preinstalled. Where is such a
>>>> user
>>>> supposed to get this XP?
>>>>
>>>> In fact no operating system is necessary at all if the user wants to
>>> install
>>>> twice, once without a pk and the second time with one.
>>>>
>>>> "Mark" <jmhonzell@nospam.insightbb.com> wrote in message
>>>> news:27AE19E4-6E6F-429D-BF66-342536D7BBDE@microsoft.com...
>>>> > My apologies. Thanks for keeping it straight Colin.
>>>> > I misread the original post.
>>>> > The link provided is still correct, just a different section applied.
>>>> > I always try to provide a source. So, read the MS document.
>>>> > (That way you won't curse us when we give you the wrong instruction.)
>>>> >
>>>> >
>>>> > "Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
>>>> > news:93A116FB-1C49-4E79-A9F5-4F12C1D29EC8@microsoft.com...
>>>> >>> Most likely, his VHP is OEM which is not eligible to move to x64.
>>>> >>
>>>> >> Yes it is. (Although it is true that a preinstalled VHP x86 does
>>>> >> not
>>>> >> qualify a person to order a free x64 dvd from MS.)
>>>> >>
>>>> >>> Since he has a VU upgrade PK, he would have to take the path of
>>>> >>> reverting to XP first.
>>>> >>
>>>> >> What XP? He has never had XP on this computer. He said he
>>>> >> purchased
>>> the
>>>> >> computer with VHP preinstalled.
>>>> >>
>>>> >> He upgraded already to Vista Ultimate x86. Vista is always eligible
>>> for
>>>> >> upgrade to Vista. All he has to do is use his upgrade edition
>>>> >> product
>>>> >> key again and install Vista Ultimate x64. As soon as he inputs the
>>>> >> pk,
>>>> >> Setup will search for and find an eligible copy of Windows on his
>>>> >> computer (Vista Ultimate x86). There is no need to "revert" to
>>> anything.
>>>> >>
>>>> >> "Mark" <jmhonzell@nospam.insightbb.com> wrote in message
>>>> >> news:1EFA68BC-2C16-4CE3-AD09-93C19457B7F0@microsoft.com...
>>>> >>> Most likely, his VHP is OEM which is not eligible to move to x64.
>>>> >>> Since he has a VU upgrade PK, he would have to take the path of
>>>> >>> reverting to XP first.
>>>> >>>
>>>> >>> "Colin Barnhorst" <c.barnhorst@comcast.net> wrote in message
>>>> >>> news
AD4E40E-661A-48B1-A585-D3412083DE2F@microsoft.com...>>>> >>>> No it doesn't. A copy of Vista is eligible for an upgrade to
>>>> >>>> Vista.
>>>> >>>> The user who has a copy of VHP x86 preinstalled can upgrade to
>>>> >>>> Vista
>>>> >>>> Ultimate x64 by booting with the x64 dvd and entering his upgrade
>>>> >>>> edition pk. Setup will find the VHP installed and allow the user
>>>> >>>> to
>>>> >>>> proceed since Vista is an eligible product (see the upgrade
>>>> >>>> matrix).
>>>> >>>> The user is not required to perform the upgrade from the desktop
>>>> >>>> of
>>> the
>>>> >>>> existing Windows (in fact he can't). He may then perform a clean
>>>> >>>> install (reformat if he wishes) or perform a custom install to any
>>>> >>>> available volume. 64bit upgrades are very different from 32bit
>>>> >>>> upgrades. I have done these upgrades myself.
>>>> >>>>
>>>> >>>> "Mark" <jmhonzell@nospam.insightbb.com> wrote in message
>>>> >>>> news:BC3B1162-E171-4CE3-8B4A-278B575FE1C1@microsoft.com...
>>>> >>>>> Most likely your current HP version is OEM.
>>>> >>>>> http://support.microsoft.com/kb/932795/
>>>> >>>>> (An upgrade Product Key requires that you revert to XP SP2 prior
>>>> >>>>> to
>>>> >>>>> using it to install x64 from Vista x86.)
>>>> >>>>>
>>>> >>>>> See section:
>>>> >>>>> Installing Vista x64 on a system already running 32-bit version
>>>> >>>>> of
>>>> >>>>> Vista.
>>>> >>>>> Just follow the instructions.
>>>> >>>>>
>>>> >>>>> Key factors in being successful:
>>>> >>>>> 1. Make sure all drivers needed are available out there. They
>>>> >>>>> must
>>> be
>>>> >>>>> x64 versions to work.
>>>> >>>>> Some components still have trouble until x64 is installed. You
>>> may
>>>> >>>>> want to remove them first:
>>>> >>>>> a. Creative sound cards.
>>>> >>>>> b. SLI graphics
>>>> >>>>> c. Mixed SATA and IDE drives. (only have one installed while
>>>> >>>>> installing x64)
>>>> >>>>> When done, put them back in one at a time.
>>>> >>>>> 2. When installing, elect not to update Vista until you are all
>>> done.
>>>> >>>>> 3. If for some reason, it errs prior to complete install, just
>>>> >>>>> start
>>>> >>>>> the x64 DVD again. You don't have to install XP again.
>>>> >>>>>
>>>> >>>>> To make uses of all memory, ensure you "remap" the memory hole
>>> through
>>>> >>>>> your BIOS. If this function is not available in the BIOS, you may
>>> need
>>>> >>>>> to update the BIOS. If still not available, I would question the
>>> need
>>>> >>>>> to go to x64.
>>>> >>>>>
>>>> >>>>> As everyone will be happy to point out semantics... this is not
>>>> >>>>> an
>>>> >>>>> upgrade, but a clean install. Nothing will survive so copy all
>>>> >>>>> your
>>>> >>>>> files first to a safe location.
>>>> >>>>> E-mail addresses transfer by WET.
>>>> >>>>>
>>>> >>>>> Good luck!
>>>> >>>>> Let us know how it goes.
>>>> >>>>> I've been on x64 since Vista was released and it's rock solid.
>>>> >>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> "Seidell23231" <Seidell23231@discussions.microsoft.com> wrote in
>>>> >>>>> message
>>>> >>>>> news:60BE1E54-48E0-4BA1-9874-C2A3B292E050@microsoft.com...
>>>> >>>>>> Hello ALL,
>>>> >>>>>>
>>>> >>>>>> About 8 months ago I purchased Vista Ultimate Upgrade, because I
>>> was
>>>> >>>>>> upgrading the PC I had than from XP Pro to Vista Ultimate.
>>> Upgraded
>>>> >>>>>> all went
>>>> >>>>>> smooth no problems.
>>>> >>>>>>
>>>> >>>>>> Fast forward to today. The old PC has passed on and a New PC
>>>> >>>>>> (HP
>>>> >>>>>> Pavillion
>>>> >>>>>> Elite m9150f with Intel Core 2 Quad) is home and getting setup.
>>> The
>>>> >>>>>> new PC
>>>> >>>>>> came with Vista Home Premium 32-Bit. I have upgraded it to
>>>> >>>>>> Vista
>>>> >>>>>> Ultimate
>>>> >>>>>> 32-Bit, BUT I want to use the 64-Bit since my PC can handle it.
>>>> >>>>>>
>>>> >>>>>> My Question is this ~~ Can I upgrade to Vista 64 with my current
>>>> >>>>>> allocation?
>>>> >>>>>> If YES, please explain, if NO please explain how to fix so I can
>>> use
>>>> >>>>>> 64-Bit.
>>>> >>>>>>
>>>> >>>>>> Thanks ~~ Gunny
>>>> >>>>>
>>>> >>>>
>>>> >>>
>>>> >>
>>>> >
>>>>
>>>
>>>
>>
>