> It wont boot because of the hardware differences most likely, you'll need to
> do a repair install to get it to boot.
>
> --
> Bob Comer <Microsoft MVP Windows - Virtual Machine>
>
>
>
>
>
>
> "Josh" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> >I used the seemingly spiffy product DriveImage XML from RunTime software to
> > create an image of my 4GB virtual C: drive, running Windows server 2003.
> > I
> > created a new 6GB VHD, attached it to my existing VPC and partitioned and
> > formatted it to use all 6 GB. Then, I created a new VPC with the 6GB VHD
> > as
> > the primary drive and used a BartPE CD with DI-XML plug-in to restore the
> > old
> > image to my new virtual drive. Now, when I try to boot from the new VHD,
> > it
> > just hangs up after the BIOS/RAM check.
> > I asked the RunTime folks, and they said that their software wasn't
> > designed for virtual hard drives, only real ones. :P It's my
> > understanding
> > that it should make any difference. Is this true? I've seen plenty of
> > posts
> > suggesting using Ghost to transfer virtual drives.
> > --
> > Josh Smith
>
>
>

>I used the seemingly spiffy product DriveImage XML from RunTime software to
> create an image of my 4GB virtual C: drive, running Windows server 2003.
> I
> created a new 6GB VHD, attached it to my existing VPC and partitioned and
> formatted it to use all 6 GB. Then, I created a new VPC with the 6GB VHD
> as
> the primary drive and used a BartPE CD with DI-XML plug-in to restore the
> old
> image to my new virtual drive. Now, when I try to boot from the new VHD,
> it
> just hangs up after the BIOS/RAM check.
> I asked the RunTime folks, and they said that their software wasn't
> designed for virtual hard drives, only real ones. :P It's my
> understanding
> that it should make any difference. Is this true? I've seen plenty of
> posts
> suggesting using Ghost to transfer virtual drives.
> --
> Josh Smith

> Just to clarify, there is no physical hardware difference. The drive
> image
> was created from a Virtual PC on the same machine as the new Virtual PC.
> I
> also have the same problem if I replace the original VHD of my VPC with
> the
> larger new virtual drive. The only difference should be that the VHD (and
> corresponding drive partition) is now bigger - is that what you are
> referring
> to?.
>
> --
> Josh Smith
>
>
> "Robert Comer" wrote:
>
>> It wont boot because of the hardware differences most likely, you'll need
>> to
>> do a repair install to get it to boot.
>>
>> --
>> Bob Comer <Microsoft MVP Windows - Virtual Machine>
>>
>>
>>
>>
>>
>>
>> "Josh" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> >I used the seemingly spiffy product DriveImage XML from RunTime software
>> >to
>> > create an image of my 4GB virtual C: drive, running Windows server
>> > 2003.
>> > I
>> > created a new 6GB VHD, attached it to my existing VPC and partitioned
>> > and
>> > formatted it to use all 6 GB. Then, I created a new VPC with the 6GB
>> > VHD
>> > as
>> > the primary drive and used a BartPE CD with DI-XML plug-in to restore
>> > the
>> > old
>> > image to my new virtual drive. Now, when I try to boot from the new
>> > VHD,
>> > it
>> > just hangs up after the BIOS/RAM check.
>> > I asked the RunTime folks, and they said that their software wasn't
>> > designed for virtual hard drives, only real ones. :P It's my
>> > understanding
>> > that it should make any difference. Is this true? I've seen plenty of
>> > posts
>> > suggesting using Ghost to transfer virtual drives.
>> > --
>> > Josh Smith
>>
>>
>>

>> Just to clarify, there is no physical hardware difference.
>
> Actually there is, VPC emulates a certain set of hardware and it's not the
> same as what your host has. (S3 Trio Video, simple IDE, bus mouse and
> keyboard, SB16 sound card, Intel 21140A NIC, Intel 440BX chipset.)
>
> When transferring an image from a real PC to a virtual one, it's just
> exactly as if you were transferring an image from a real PC to another
> real PC with a totally different hardware config.
>
> --
> Bob Comer <Microsoft MVP Windows - Virtual Machine>
>
>
>
> "Josh" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Just to clarify, there is no physical hardware difference. The drive
>> image
>> was created from a Virtual PC on the same machine as the new Virtual PC.
>> I
>> also have the same problem if I replace the original VHD of my VPC with
>> the
>> larger new virtual drive. The only difference should be that the VHD
>> (and
>> corresponding drive partition) is now bigger - is that what you are
>> referring
>> to?.
>>
>> --
>> Josh Smith
>>
>>
>> "Robert Comer" wrote:
>>
>>> It wont boot because of the hardware differences most likely, you'll
>>> need to
>>> do a repair install to get it to boot.
>>>
>>> --
>>> Bob Comer <Microsoft MVP Windows - Virtual Machine>
>>>
>>>
>>>
>>>
>>>
>>>
>>> "Josh" <(email address - cut out)> wrote in message
>>> news:(email address - cut out)...
>>> >I used the seemingly spiffy product DriveImage XML from RunTime
>>> >software to
>>> > create an image of my 4GB virtual C: drive, running Windows server
>>> > 2003.
>>> > I
>>> > created a new 6GB VHD, attached it to my existing VPC and partitioned
>>> > and
>>> > formatted it to use all 6 GB. Then, I created a new VPC with the 6GB
>>> > VHD
>>> > as
>>> > the primary drive and used a BartPE CD with DI-XML plug-in to restore
>>> > the
>>> > old
>>> > image to my new virtual drive. Now, when I try to boot from the new
>>> > VHD,
>>> > it
>>> > just hangs up after the BIOS/RAM check.
>>> > I asked the RunTime folks, and they said that their software wasn't
>>> > designed for virtual hard drives, only real ones. :P It's my
>>> > understanding
>>> > that it should make any difference. Is this true? I've seen plenty
>>> > of
>>> > posts
>>> > suggesting using Ghost to transfer virtual drives.
>>> > --
>>> > Josh Smith
>>>
>>>
>>>
>
>

> If I read it right, the OP imaged a vhd, not his host hard drive.
>
> "Robert Comer" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>>> Just to clarify, there is no physical hardware difference.
>>
>> Actually there is, VPC emulates a certain set of hardware and it's not
>> the same as what your host has. (S3 Trio Video, simple IDE, bus mouse
>> and keyboard, SB16 sound card, Intel 21140A NIC, Intel 440BX chipset.)
>>
>> When transferring an image from a real PC to a virtual one, it's just
>> exactly as if you were transferring an image from a real PC to another
>> real PC with a totally different hardware config.
>>
>> --
>> Bob Comer <Microsoft MVP Windows - Virtual Machine>
>>
>>
>>
>> "Josh" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> Just to clarify, there is no physical hardware difference. The drive
>>> image
>>> was created from a Virtual PC on the same machine as the new Virtual PC.
>>> I
>>> also have the same problem if I replace the original VHD of my VPC with
>>> the
>>> larger new virtual drive. The only difference should be that the VHD
>>> (and
>>> corresponding drive partition) is now bigger - is that what you are
>>> referring
>>> to?.
>>>
>>> --
>>> Josh Smith
>>>
>>>
>>> "Robert Comer" wrote:
>>>
>>>> It wont boot because of the hardware differences most likely, you'll
>>>> need to
>>>> do a repair install to get it to boot.
>>>>
>>>> --
>>>> Bob Comer <Microsoft MVP Windows - Virtual Machine>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> "Josh" <(email address - cut out)> wrote in message
>>>> news:(email address - cut out)...
>>>> >I used the seemingly spiffy product DriveImage XML from RunTime
>>>> >software to
>>>> > create an image of my 4GB virtual C: drive, running Windows server
>>>> > 2003.
>>>> > I
>>>> > created a new 6GB VHD, attached it to my existing VPC and partitioned
>>>> > and
>>>> > formatted it to use all 6 GB. Then, I created a new VPC with the 6GB
>>>> > VHD
>>>> > as
>>>> > the primary drive and used a BartPE CD with DI-XML plug-in to restore
>>>> > the
>>>> > old
>>>> > image to my new virtual drive. Now, when I try to boot from the new
>>>> > VHD,
>>>> > it
>>>> > just hangs up after the BIOS/RAM check.
>>>> > I asked the RunTime folks, and they said that their software wasn't
>>>> > designed for virtual hard drives, only real ones. :P It's my
>>>> > understanding
>>>> > that it should make any difference. Is this true? I've seen plenty
>>>> > of
>>>> > posts
>>>> > suggesting using Ghost to transfer virtual drives.
>>>> > --
>>>> > Josh Smith
>>>>
>>>>
>>>>
>>
>>
>
>

> physical to virtual.
> In article <(email address - cut out)>, in the
> microsoft.public.virtualpc news group, Robert Comer
> <(email address - cut out)> says...
>
>> > Just to clarify, there is no physical hardware difference.
>>
>> Actually there is, VPC emulates a certain set of hardware and it's not
>> the
>> same as what your host has. (S3 Trio Video, simple IDE, bus mouse and
>> keyboard, SB16 sound card, Intel 21140A NIC, Intel 440BX chipset.)
>>
>> When transferring an image from a real PC to a virtual one, it's just
>> exactly as if you were transferring an image from a real PC to another
>> real
>> PC with a totally different hardware config.
>>
>>
>
> You're missing the point, this was virtual to virtual, not
> physical to virtual.
>
> --
> Paul Adare - MVP Virtual Machines
> It all began with Adam. He was the first man to tell a
> joke--or a lie. How lucky Adam was. He knew when he said a
> good thing, nobody had said it before. Adam was not alone
> in the Garden of Eden, however, and does not deserve all
> the credit; much is due to Eve, the first woman, and Satan,
> the first consultant." - Mark Twain

> Just to clarify, there is no physical hardware difference. The drive
> image
> was created from a Virtual PC on the same machine as the new Virtual PC.
> I
> also have the same problem if I replace the original VHD of my VPC with
> the
> larger new virtual drive. The only difference should be that the VHD (and
> corresponding drive partition) is now bigger - is that what you are
> referring
> to?.
>
> --
> Josh Smith
>
>
> "Robert Comer" wrote:
>
>> It wont boot because of the hardware differences most likely, you'll need
>> to
>> do a repair install to get it to boot.
>>
>> --
>> Bob Comer <Microsoft MVP Windows - Virtual Machine>
>>
>>
>>
>>
>>
>>
>> "Josh" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> >I used the seemingly spiffy product DriveImage XML from RunTime software
>> >to
>> > create an image of my 4GB virtual C: drive, running Windows server
>> > 2003.
>> > I
>> > created a new 6GB VHD, attached it to my existing VPC and partitioned
>> > and
>> > formatted it to use all 6 GB. Then, I created a new VPC with the 6GB
>> > VHD
>> > as
>> > the primary drive and used a BartPE CD with DI-XML plug-in to restore
>> > the
>> > old
>> > image to my new virtual drive. Now, when I try to boot from the new
>> > VHD,
>> > it
>> > just hangs up after the BIOS/RAM check.
>> > I asked the RunTime folks, and they said that their software wasn't
>> > designed for virtual hard drives, only real ones. :P It's my
>> > understanding
>> > that it should make any difference. Is this true? I've seen plenty of
>> > posts
>> > suggesting using Ghost to transfer virtual drives.
>> > --
>> > Josh Smith
>>
>>
>>

> > Just to clarify, there is no physical hardware difference.
>
> Actually there is, VPC emulates a certain set of hardware and it's not the
> same as what your host has. (S3 Trio Video, simple IDE, bus mouse and
> keyboard, SB16 sound card, Intel 21140A NIC, Intel 440BX chipset.)
>
> When transferring an image from a real PC to a virtual one, it's just
> exactly as if you were transferring an image from a real PC to another real
> PC with a totally different hardware config.
>
>

>I used the seemingly spiffy product DriveImage XML from RunTime software to
> create an image of my 4GB virtual C: drive, running Windows server 2003.
> I
> created a new 6GB VHD, attached it to my existing VPC and partitioned and
> formatted it to use all 6 GB. Then, I created a new VPC with the 6GB VHD
> as
> the primary drive and used a BartPE CD with DI-XML plug-in to restore the
> old
> image to my new virtual drive. Now, when I try to boot from the new VHD,
> it
> just hangs up after the BIOS/RAM check.
> I asked the RunTime folks, and they said that their software wasn't
> designed for virtual hard drives, only real ones. :P It's my
> understanding
> that it should make any difference. Is this true? I've seen plenty of
> posts
> suggesting using Ghost to transfer virtual drives.
> --
> Josh Smith

> When you imaged the old vhd to the new one, did you imaged the whole drive
> or just the partition? If you imaged just the partition, then it's maybe
> that this doesn't work because the master table of the new drive has been
> incorrectly written.
>
> You should partition the new vhd before imaging into it or clone the whole
> old VHD and not just its partition.
>
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: http://cerbermail.com/?QugbLEWINF
>
>
> "Josh" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> >I used the seemingly spiffy product DriveImage XML from RunTime software to
> > create an image of my 4GB virtual C: drive, running Windows server 2003.
> > I
> > created a new 6GB VHD, attached it to my existing VPC and partitioned and
> > formatted it to use all 6 GB. Then, I created a new VPC with the 6GB VHD
> > as
> > the primary drive and used a BartPE CD with DI-XML plug-in to restore the
> > old
> > image to my new virtual drive. Now, when I try to boot from the new VHD,
> > it
> > just hangs up after the BIOS/RAM check.
> > I asked the RunTime folks, and they said that their software wasn't
> > designed for virtual hard drives, only real ones. :P It's my
> > understanding
> > that it should make any difference. Is this true? I've seen plenty of
> > posts
> > suggesting using Ghost to transfer virtual drives.
> > --
> > Josh Smith
>
>
>

>I found the following instructions on the software vendor's FAQ to get my
>new
> VHD to boot , but was unsuccessfull. Can you think of anything else I'm
> missing?
>
> A. Note that you must put the image into an existing partition. If
> necessary
> create a new partition with Windows Disk Management first.
>
> A. To boot from a drive:
> The boot partition should be located on the first drive (DISK0), which is
> usually the master drive.
> The boot partition should be the first partition on the drive.
> The boot partition must be a "primary" partition.
> The boot partition must be "active".
> If your drive still does not boot you can try to set a new "Disk ID".
> Windows remembers old drive letter assignments which can cause problems
> when
> trying to boot from a cloned drive. You can force the removal of old drive
> letter assignments by setting a new Disk ID. Click Tools->Set new Disk ID
> and
> read the instructions.
>
> --
> Josh Smith
>
>
> "Sylvain Lafontaine" wrote:
>
>> When you imaged the old vhd to the new one, did you imaged the whole
>> drive
>> or just the partition? If you imaged just the partition, then it's maybe
>> that this doesn't work because the master table of the new drive has been
>> incorrectly written.
>>
>> You should partition the new vhd before imaging into it or clone the
>> whole
>> old VHD and not just its partition.
>>
>> --
>> Sylvain Lafontaine, ing.
>> MVP - Technologies Virtual-PC
>> E-mail: http://cerbermail.com/?QugbLEWINF
>>
>>
>> "Josh" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> >I used the seemingly spiffy product DriveImage XML from RunTime software
>> >to
>> > create an image of my 4GB virtual C: drive, running Windows server
>> > 2003.
>> > I
>> > created a new 6GB VHD, attached it to my existing VPC and partitioned
>> > and
>> > formatted it to use all 6 GB. Then, I created a new VPC with the 6GB
>> > VHD
>> > as
>> > the primary drive and used a BartPE CD with DI-XML plug-in to restore
>> > the
>> > old
>> > image to my new virtual drive. Now, when I try to boot from the new
>> > VHD,
>> > it
>> > just hangs up after the BIOS/RAM check.
>> > I asked the RunTime folks, and they said that their software wasn't
>> > designed for virtual hard drives, only real ones. :P It's my
>> > understanding
>> > that it should make any difference. Is this true? I've seen plenty of
>> > posts
>> > suggesting using Ghost to transfer virtual drives.
>> > --
>> > Josh Smith
>>
>>
>>