>I originally had XP Pro 32 bit, we bought the upgrade to 64 bit. We
>have run
> into some problems with the 64 bit. Can I install the XP Pro 32 bit
> full
> version on Virtual PC while running the 64 bit upgrade on the actual
> computer
> with no licensing implications?

> "Thomas" wrote in message
> news:(email address - cut out)...
>>I originally had XP Pro 32 bit, we bought the upgrade to 64 bit. We have
>>run
>> into some problems with the 64 bit. Can I install the XP Pro 32 bit full
>> version on Virtual PC while running the 64 bit upgrade on the actual
>> computer
>> with no licensing implications?
>
>
> If you use the 32-bit version in the VM which was the base or first link
> in your chain of upgrades, where are you going to get another and
> different version upon which the UPGRADE is based that you want as the
> parent OS? When you upgrade, you don't get to continue using the prior
> version. That is why it is an upgrade, not a replacement and not a full
> version. You keep around the prior version's install media in case you
> have problems with the upgrade. If you started, say, with Windows 98 as
> the only FULL version that you have and you have upgraded to Windows ME,
> then Windows 2000, and then Windows XP, you still only have 1 full version
> and the rest are upgrade versions (all upgrade licenses have to follow a
> chain eventually to a full version).
>
> http://www.microsoft.com/windowsxp/sp2/proeula.mspx
> 8. UPGRADES. To use Software identified as an upgrade, you must first be
> licensed for the software identified by Microsoft as eligible for the
> upgrade. After upgrading, you may no longer use the software that formed
> the basis for your upgrade eligibility.
>
> The upgrade needs to be part of a chain that traces back to a FULL
> version, and that FULL version at the start of the chain cannot be shared
> amongst multiple hosts (real or virtual). For example, you don't get to
> buy a dozen upgrade copies and apply them all against the same full
> version to install the upgrades on a dozen hosts. Once you upgrade, the
> prior version because a unusable placeholder or link in that chain back to
> the non-shared FULL version.

>I originally had XP Pro 32 bit, we bought the upgrade to 64 bit. We have
>run
> into some problems with the 64 bit. Can I install the XP Pro 32 bit full
> version on Virtual PC while running the 64 bit upgrade on the actual
> computer
> with no licensing implications?

>I originally had XP Pro 32 bit, we bought the upgrade to 64 bit. We have
>run
> into some problems with the 64 bit. Can I install the XP Pro 32 bit full
> version on Virtual PC while running the 64 bit upgrade on the actual
> computer
> with no licensing implications?

> "Colin Barnhorst" wrote in message
> news:(email address - cut out)...
>> There is no upgrade. XP Pro x64 is a clean install. The cd is OEM
>> anyway.
>>
>
>
> I figured there was an upgrade version (never seen it myself since I
> always buy OEM versions) if the OP said they had that version. Now that
> you mention it, I can't remember ever seeing a non-OEM version. An OEM
> version *is* a full version, not an upgrade.
>
> Since the 32-bit version is a full version or an upgrade based on some
> other prior license (and not to the x64 version) then it seems the OP
> should be able to do what he wants. The x64 OEM license runs as the
> parent and the separate 32-bit license runs in a VM. However, no
> indication of whether or not the 32-bit version was also an OEM version or
> not (and, if OEM, if it had ever been installed before).

> There is no upgrade. XP Pro x64 is a clean install. The cd is OEM
> anyway.
>

>
> "VanguardLH" wrote ...
>>
>> "Colin Barnhorst" wrote ...
>>>
>>> There is no upgrade. XP Pro x64 is a clean install. The cd is
>>> OEM anyway.
>>
>> I figured there was an upgrade version (never seen it myself since
>> I always buy OEM versions) if the OP said they had that version.
>> Now that you mention it, I can't remember ever seeing a non-OEM
>> version. An OEM version *is* a full version, not an upgrade.
>>
>> Since the 32-bit version is a full version or an upgrade based on
>> some other prior license (and not to the x64 version) then it seems
>> the OP should be able to do what he wants. The x64 OEM license
>> runs as the parent and the separate 32-bit license runs in a VM.
>> However, no indication of whether or not the 32-bit version was
>> also an OEM version or not (and, if OEM, if it had ever been
>> installed before).
>
> There is no such thing as a parent and child relationship with this
> license. The EULA explicitly states (retail) that the user may only
> install one copy of the software. It says nothing about "as many
> times as you want as long as its on the same computer." One copy is
> one copy. The OEM EULA explicitly states that the software is for
> installation on a new computer or a computer without an operating
> system and may not be transferred.
> It makes absolutely no difference whether or not an OEM copy has
> been installed before or not. It may only be installed on one
> device. It may be reinstalled on that device, but it may NOT be
> installed on any other device.

> "Colin Barnhorst" wrote in message
> news:(email address - cut out)...
>>
>> "VanguardLH" wrote ...
>>>
>>> "Colin Barnhorst" wrote ...
>>>>
>>>> There is no upgrade. XP Pro x64 is a clean install. The cd is OEM
>>>> anyway.
>>>
>>> I figured there was an upgrade version (never seen it myself since I
>>> always buy OEM versions) if the OP said they had that version. Now that
>>> you mention it, I can't remember ever seeing a non-OEM version. An OEM
>>> version *is* a full version, not an upgrade.
>>>
>>> Since the 32-bit version is a full version or an upgrade based on some
>>> other prior license (and not to the x64 version) then it seems the OP
>>> should be able to do what he wants. The x64 OEM license runs as the
>>> parent and the separate 32-bit license runs in a VM. However, no
>>> indication of whether or not the 32-bit version was also an OEM version
>>> or not (and, if OEM, if it had ever been installed before).
>>
>> There is no such thing as a parent and child relationship with this
>> license. The EULA explicitly states (retail) that the user may only
>> install one copy of the software. It says nothing about "as many times
>> as you want as long as its on the same computer." One copy is one copy.
>> The OEM EULA explicitly states that the software is for installation on a
>> new computer or a computer without an operating system and may not be
>> transferred.
>
> Parent, as in the OS under which Virtual PC runs. Nothing to do with
> licensing. With Virtual PC, VMWare Server, and other virtualization
> products, there is the parent OS (or host OS) and the child OS (or guest
> OS).
>
>> It makes absolutely no difference whether or not an OEM copy has been
>> installed before or not. It may only be installed on one device. It may
>> be reinstalled on that device, but it may NOT be installed on any other
>> device.
>
> So far, we don't what type of license is associated with the 32-bit
> version of Windows. Even if it was an OEM version, and as long as the OP
> runs it under VPC on the same hardware host after its first use, how would
> running a 32-bit OEM license of Windows in a VM and always on the same
> hardware host violate its license?
>
> While you have noticed the x64 version must be an OEM version and because
> it was already installed on the hardware host then that is where it
> remains - and, according to the OP, is what the OP intends to do. So far,
> we don't know what license type is for the 32-bit version.

> If your XP x86 came pre-installed on the computer you may not use it on any
> other computer, even a virtual one (OEM copy of Windows is non-tranferrable)
> .
>
> If your XP x86 is a retail copy that you purchased and installed yourself
> then you may use the license in a virtual machine (Retail copy of Windows
> permits transfer to a new machine).
>
> XP Pro x64 is OEM only and since installing it does not tie any license to
> previous software, whether you can re-use the XP x86 license depends
> entirely on whether the XP x86 Windows is OEM or Retail.
>
> "Thomas" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> >I originally had XP Pro 32 bit, we bought the upgrade to 64 bit. We have
> >run
> > into some problems with the 64 bit. Can I install the XP Pro 32 bit full
> > version on Virtual PC while running the 64 bit upgrade on the actual
> > computer
> > with no licensing implications?
>

> In VPC parent and child have entirely different meanings. They
> refer to differencing disks. The proper terms here are Host and
> Guest.

> "Colin Barnhorst" wrote in message
> news:(email address - cut out)...
>> In VPC parent and child have entirely different meanings. They refer to
>> differencing disks. The proper terms here are Host and Guest.
>
>
> I use multiple virtualizing products. I don't care what Microsoft choose
> for its particular slang. As in any conversation, context is important.

> I'm appearently not savy with the total computing experience, as I'm
> reading
> here. But, I need to ask you, if I understand the question from Thomas
> correctly, does this mean that while using 64 bit, one can operate, within
> that windows, a fake, for lack of a better word, computer, using 32 bit
> windows; given that I'm using less then 4 gig's of memory, in the same
> computer? This would certtainly circumvent having to use a partitioning
> device/software; if I really felt it neccesary to use 32 bit compatable
> games/applications/ect? Let's put it this way, I bought the 64 bit system
> without realizing it's issues, and now have buyers remorse. I use it for
> high
> def video editing, but can't use it for my games. Some backwords
> compatability would be nice, or at least a way to get around it, without
> using two computers. Any Ideas?
>
> "Colin Barnhorst" wrote:
>
>> If your XP x86 came pre-installed on the computer you may not use it on
>> any
>> other computer, even a virtual one (OEM copy of Windows is
>> non-tranferrable)
>> .
>>
>> If your XP x86 is a retail copy that you purchased and installed yourself
>> then you may use the license in a virtual machine (Retail copy of Windows
>> permits transfer to a new machine).
>>
>> XP Pro x64 is OEM only and since installing it does not tie any license
>> to
>> previous software, whether you can re-use the XP x86 license depends
>> entirely on whether the XP x86 Windows is OEM or Retail.
>>
>> "Thomas" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> >I originally had XP Pro 32 bit, we bought the upgrade to 64 bit. We
>> >have
>> >run
>> > into some problems with the 64 bit. Can I install the XP Pro 32 bit
>> > full
>> > version on Virtual PC while running the 64 bit upgrade on the actual
>> > computer
>> > with no licensing implications?
>>

> Very Alice in Wonderland, really. "When I use a word it means just what I
> want it to mean"!
>
> "Colin Barnhorst" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> That's just nuts!
>>
>> "VanguardLH" <(email address - cut out)lid> wrote in message
>> news:(email address - cut out)...
>>> "Colin Barnhorst" wrote in message
>>> news:(email address - cut out)...
>>>> In VPC parent and child have entirely different meanings. They refer
>>>> to differencing disks. The proper terms here are Host and Guest.
>>>
>>>
>>> I use multiple virtualizing products. I don't care what Microsoft
>>> choose for its particular slang. As in any conversation, context is
>>> important.
>>
>

> That's just nuts!

> "Colin Barnhorst" wrote in message
> news:(email address - cut out)...
>> That's just nuts!
>
>
> Yeah, Microsoft, from a company that calls the partition with the boot
> loader the system volume and the partition containing the kernel and
> system files the boot volume (http://support.microsoft.com/kb/314470).

>
> VanguardLH wrote:
>>
>> Yeah, Microsoft, from a company that calls the partition with the
>> boot
>> loader the system volume and the partition containing the kernel
>> and
>> system files the boot volume
>> (http://support.microsoft.com/kb/314470).
>
> Microsoft did not invent this terminology, it has been around since
> there
> have been computers.

> You mean a specific subset of computers for when "as Microsoft defined
> it" for their operating systems.

> No, that's not what I mean. The terminology in question came from the
> mainframe and mini world.

> Paul Adare wrote:
>
> It would not matter so much if the whole MS multi-boot framework
> were not such a mess. If you use a proper boot manager like BootIt
> NG (or even the ancient Ranish Partition Manager) you can arrange
> things so that for each OS the boot and system partition are the
> same (and each doesn't see the boot/system partition of the others).
> Each OS sees itself as C, and if you have a common data partition
> then it will be seen as D.

> That's just nuts!
>
> "VanguardLH" <(email address - cut out)lid> wrote in message
> news:(email address - cut out)...
>> "Colin Barnhorst" wrote in message
>> news:(email address - cut out)...
>>> In VPC parent and child have entirely different meanings. They refer to
>>> differencing disks. The proper terms here are Host and Guest.
>>
>>
>> I use multiple virtualizing products. I don't care what Microsoft choose
>> for its particular slang. As in any conversation, context is important.
>

> Absolutely. They are called virtual machines and there are interesting
> capabilities. I run not only 32-bit virtual machines on Vista x64 by
> running VPC, but I also can run 16-bit virtual machines, like MSDOS 6.22 or
> Windows for Workgroups, as well even though Vista x64 itself cannot run
> 16-bit software.
>
> I do a lot of legacy gaming this way as well. See Ben Armstrong's blogs on
> legacy gaming at
> http://blogs.msdn.com/virtual_pc_guy/.
>
> I run an XP Pro SP2 virtual machine in order to continue to play
> Civilization III Complete and some other games that for one reason or
> another I don't want to or cannot run on Vista. Performance is excellent
> and as long as you don't try to run games that require 3d graphics things go
> very well.
>
> If you are running Vista with 2GB of ram, the allocation of 256mb of ram to
> a virtual machine running XP is no big deal.
>
> Running XP virtual machines works fine on 32-bit as well as 64-bit hosts.
> In fact I have one XP x86 box on which I run Vista Ultimate x86 in a virtual
> machine.
>
> "phillip judd" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > I'm appearently not savy with the total computing experience, as I'm
> > reading
> > here. But, I need to ask you, if I understand the question from Thomas
> > correctly, does this mean that while using 64 bit, one can operate, within
> > that windows, a fake, for lack of a better word, computer, using 32 bit
> > windows; given that I'm using less then 4 gig's of memory, in the same
> > computer? This would certtainly circumvent having to use a partitioning
> > device/software; if I really felt it neccesary to use 32 bit compatable
> > games/applications/ect? Let's put it this way, I bought the 64 bit system
> > without realizing it's issues, and now have buyers remorse. I use it for
> > high
> > def video editing, but can't use it for my games. Some backwords
> > compatability would be nice, or at least a way to get around it, without
> > using two computers. Any Ideas?
> >
> > "Colin Barnhorst" wrote:
> >
> >> If your XP x86 came pre-installed on the computer you may not use it on
> >> any
> >> other computer, even a virtual one (OEM copy of Windows is
> >> non-tranferrable)
> >> .
> >>
> >> If your XP x86 is a retail copy that you purchased and installed yourself
> >> then you may use the license in a virtual machine (Retail copy of Windows
> >> permits transfer to a new machine).
> >>
> >> XP Pro x64 is OEM only and since installing it does not tie any license
> >> to
> >> previous software, whether you can re-use the XP x86 license depends
> >> entirely on whether the XP x86 Windows is OEM or Retail.
> >>
> >> "Thomas" <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >> >I originally had XP Pro 32 bit, we bought the upgrade to 64 bit. We
> >> >have
> >> >run
> >> > into some problems with the 64 bit. Can I install the XP Pro 32 bit
> >> > full
> >> > version on Virtual PC while running the 64 bit upgrade on the actual
> >> > computer
> >> > with no licensing implications?
> >>
>

> My PC came installed with XP Pro 32-bit. I requested that they change my
> software to XP 64, according to our tech people they "switched" the
> license
> from the 32bit to the 64bit through Dell. Does this seem right?
>
> "Colin Barnhorst" wrote:
>
>> Absolutely. They are called virtual machines and there are interesting
>> capabilities. I run not only 32-bit virtual machines on Vista x64 by
>> running VPC, but I also can run 16-bit virtual machines, like MSDOS 6.22
>> or
>> Windows for Workgroups, as well even though Vista x64 itself cannot run
>> 16-bit software.
>>
>> I do a lot of legacy gaming this way as well. See Ben Armstrong's blogs
>> on
>> legacy gaming at
>> http://blogs.msdn.com/virtual_pc_guy/.
>>
>> I run an XP Pro SP2 virtual machine in order to continue to play
>> Civilization III Complete and some other games that for one reason or
>> another I don't want to or cannot run on Vista. Performance is excellent
>> and as long as you don't try to run games that require 3d graphics things
>> go
>> very well.
>>
>> If you are running Vista with 2GB of ram, the allocation of 256mb of ram
>> to
>> a virtual machine running XP is no big deal.
>>
>> Running XP virtual machines works fine on 32-bit as well as 64-bit hosts.
>> In fact I have one XP x86 box on which I run Vista Ultimate x86 in a
>> virtual
>> machine.
>>
>> "phillip judd" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > I'm appearently not savy with the total computing experience, as I'm
>> > reading
>> > here. But, I need to ask you, if I understand the question from Thomas
>> > correctly, does this mean that while using 64 bit, one can operate,
>> > within
>> > that windows, a fake, for lack of a better word, computer, using 32 bit
>> > windows; given that I'm using less then 4 gig's of memory, in the same
>> > computer? This would certtainly circumvent having to use a partitioning
>> > device/software; if I really felt it neccesary to use 32 bit compatable
>> > games/applications/ect? Let's put it this way, I bought the 64 bit
>> > system
>> > without realizing it's issues, and now have buyers remorse. I use it
>> > for
>> > high
>> > def video editing, but can't use it for my games. Some backwords
>> > compatability would be nice, or at least a way to get around it,
>> > without
>> > using two computers. Any Ideas?
>> >
>> > "Colin Barnhorst" wrote:
>> >
>> >> If your XP x86 came pre-installed on the computer you may not use it
>> >> on
>> >> any
>> >> other computer, even a virtual one (OEM copy of Windows is
>> >> non-tranferrable)
>> >> .
>> >>
>> >> If your XP x86 is a retail copy that you purchased and installed
>> >> yourself
>> >> then you may use the license in a virtual machine (Retail copy of
>> >> Windows
>> >> permits transfer to a new machine).
>> >>
>> >> XP Pro x64 is OEM only and since installing it does not tie any
>> >> license
>> >> to
>> >> previous software, whether you can re-use the XP x86 license depends
>> >> entirely on whether the XP x86 Windows is OEM or Retail.
>> >>
>> >> "Thomas" <(email address - cut out)> wrote in message
>> >> news:(email address - cut out)...
>> >> >I originally had XP Pro 32 bit, we bought the upgrade to 64 bit. We
>> >> >have
>> >> >run
>> >> > into some problems with the 64 bit. Can I install the XP Pro 32 bit
>> >> > full
>> >> > version on Virtual PC while running the 64 bit upgrade on the actual
>> >> > computer
>> >> > with no licensing implications?
>> >>
>>

> Yes. You would have only one license whether x86 or x64 but not both. Does
> this have anything to do with Virtual PC? If you are just running XP Pro
> x64 now a good newsgroup for you is microsoft.public.windows.64bit.general.
>
> "Thomas" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > My PC came installed with XP Pro 32-bit. I requested that they change my
> > software to XP 64, according to our tech people they "switched" the
> > license
> > from the 32bit to the 64bit through Dell. Does this seem right?
> >
> > "Colin Barnhorst" wrote:
> >
> >> Absolutely. They are called virtual machines and there are interesting
> >> capabilities. I run not only 32-bit virtual machines on Vista x64 by
> >> running VPC, but I also can run 16-bit virtual machines, like MSDOS 6.22
> >> or
> >> Windows for Workgroups, as well even though Vista x64 itself cannot run
> >> 16-bit software.
> >>
> >> I do a lot of legacy gaming this way as well. See Ben Armstrong's blogs
> >> on
> >> legacy gaming at
> >> http://blogs.msdn.com/virtual_pc_guy/.
> >>
> >> I run an XP Pro SP2 virtual machine in order to continue to play
> >> Civilization III Complete and some other games that for one reason or
> >> another I don't want to or cannot run on Vista. Performance is excellent
> >> and as long as you don't try to run games that require 3d graphics things
> >> go
> >> very well.
> >>
> >> If you are running Vista with 2GB of ram, the allocation of 256mb of ram
> >> to
> >> a virtual machine running XP is no big deal.
> >>
> >> Running XP virtual machines works fine on 32-bit as well as 64-bit hosts.
> >> In fact I have one XP x86 box on which I run Vista Ultimate x86 in a
> >> virtual
> >> machine.
> >>
> >> "phillip judd" <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >> > I'm appearently not savy with the total computing experience, as I'm
> >> > reading
> >> > here. But, I need to ask you, if I understand the question from Thomas
> >> > correctly, does this mean that while using 64 bit, one can operate,
> >> > within
> >> > that windows, a fake, for lack of a better word, computer, using 32 bit
> >> > windows; given that I'm using less then 4 gig's of memory, in the same
> >> > computer? This would certtainly circumvent having to use a partitioning
> >> > device/software; if I really felt it neccesary to use 32 bit compatable
> >> > games/applications/ect? Let's put it this way, I bought the 64 bit
> >> > system
> >> > without realizing it's issues, and now have buyers remorse. I use it
> >> > for
> >> > high
> >> > def video editing, but can't use it for my games. Some backwords
> >> > compatability would be nice, or at least a way to get around it,
> >> > without
> >> > using two computers. Any Ideas?
> >> >
> >> > "Colin Barnhorst" wrote:
> >> >
> >> >> If your XP x86 came pre-installed on the computer you may not use it
> >> >> on
> >> >> any
> >> >> other computer, even a virtual one (OEM copy of Windows is
> >> >> non-tranferrable)
> >> >> .
> >> >>
> >> >> If your XP x86 is a retail copy that you purchased and installed
> >> >> yourself
> >> >> then you may use the license in a virtual machine (Retail copy of
> >> >> Windows
> >> >> permits transfer to a new machine).
> >> >>
> >> >> XP Pro x64 is OEM only and since installing it does not tie any
> >> >> license
> >> >> to
> >> >> previous software, whether you can re-use the XP x86 license depends
> >> >> entirely on whether the XP x86 Windows is OEM or Retail.
> >> >>
> >> >> "Thomas" <(email address - cut out)> wrote in message
> >> >> news:(email address - cut out)...
> >> >> >I originally had XP Pro 32 bit, we bought the upgrade to 64 bit. We
> >> >> >have
> >> >> >run
> >> >> > into some problems with the 64 bit. Can I install the XP Pro 32 bit
> >> >> > full
> >> >> > version on Virtual PC while running the 64 bit upgrade on the actual
> >> >> > computer
> >> >> > with no licensing implications?
> >> >>
> >>
>