Sent: 12/01/2008
From: simpleton
Message:Is VPC gonna complain if I want *.vhd on D: instead of C:?
Ric
"Bo Berglund" wrote:
Show quoted text
> On Mon, 1 Dec 2008 09:26:02 -0800, simpleton
> <(email address - cut out)> wrote:
>
> Can I just hook the HD... and plunk it in?
>
> >"Bo Berglund" wrote:
> >
> >> No, you can't.
>>>...
> >>
> >> It is *not* a "plunk" operation.....
> >> --
>
>>"simpleton" wrote:
>>
> >That's too bad. ... like a partition in a dual-boot system,
> >without the need to reboot the other VM?
> >
>
>>"Bo Berglund" wrote:
>>
> No that is not really how it works...
> No 30Gb directory created for example...
>
> VPC creates a "virtual machine" which is defined in two files
> (initially). One is the Virtual Machine Configuration file (*.vmc),
> which holds the data for the VPC2007 application to handle the
> specifics of this machine like how much memory it uses, which hard
> drives are connected to it, networking etc.
>
> The other is one or several Virtual Hard Drive files (*.vhd) which
> represent the contents of the hard disks in the virtual machine. There
> are two kinds of VHD files, one that immediately assigns the complete
> size of the disk to the VHD file (very wasteful of host system disk
> space) and the other is the dynamically expanding type. This starts
> out as a very small file on the host system (35 kb or so) even if it
> is set to hold 32 Gb or more data. The file will expand on the host as
> the virtual machine adds data to its hard drive.
>
> When VPC2007 starts a virtual machine it will do so based on the vmc
> file contents and the vhd disk drive. What happens next is that the
> virtual machine boots up in a window on your host system and it looks
> for bootable media, which it won't find at first because now you have
> to install the operating system on to the virtual hard disk in exactly
> the same way you do it on a physical computer. You need the install CD
> for this.
>
> However, in your case you could instead use the Acronis tools to
> create a VHD image of your hard disk from the physical computer and
> then use this as your drive in the virtual computer. That is what I
> meant by migrating the physical computer.
>
> Once all this is sorted out you will have a PC running in a window on
> your host PC and this PC can be accessed via the network just like any
> other networked PC can. So you should be able to do what you did
> before via the network also with this virtual computer.
> The virtual PC behaves to all intents and purposes exactly like a
> physical computer.
>
> --
>
> Bo Berglund (Sweden)
>
Sent: 12/01/2008
From: "Steve Jain [MVP]" <(email address - cut out)>
Message:On Mon, 1 Dec 2008 10:24:04 -0800, simpleton
<(email address - cut out)> wrote:
No, it's just a file. Does Word complain if you save a *.doc file on
the D: drive?
VPC is an application, and the .vmc and .vhd files that make it up are
essentially data documents. They can be located anywhere on the
system that has a drive letter and the necessary space to hold the
files.
Ideally, you SHOULD run your OSes on a different hard drive than the
host OS is running on. Multiple OSes on a single hard drive are one
of the biggest performance issues with VMs.
I only run VMs on the C: drive of my laptop, and then only the single
one I need access to at all times, otherwise, all my VMs are scattered
over other hard drives, both internal and external.
--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/
Show quoted text
>Is VPC gonna complain if I want *.vhd on D: instead of C:?
>
>Ric
>
Sent: 12/01/2008
From: "Steve Jain [MVP]" <(email address - cut out)>
Message:On Mon, 01 Dec 2008 20:45:12 +0100, Bo Berglund <(email address - cut out)>
wrote:
Good point to bring up.
--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/
Show quoted text
>On Mon, 01 Dec 2008 11:10:48 -0800, "Steve Jain [MVP]"
><(email address - cut out)> wrote:
>
>>On Mon, 1 Dec 2008 10:24:04 -0800, simpleton
>><(email address - cut out)> wrote:
>>
>>>Is VPC gonna complain if I want *.vhd on D: instead of C:?
>>>
>>>Ric
>>>
>>
>>No, it's just a file. Does Word complain if you save a *.doc file on
>>the D: drive?
>>VPC is an application, and the .vmc and .vhd files that make it up are
>>essentially data documents. They can be located anywhere on the
>>system that has a drive letter and the necessary space to hold the
>>files.
>>Ideally, you SHOULD run your OSes on a different hard drive than the
>>host OS is running on. Multiple OSes on a single hard drive are one
>>of the biggest performance issues with VMs.
>>I only run VMs on the C: drive of my laptop, and then only the single
>>one I need access to at all times, otherwise, all my VMs are scattered
>>over other hard drives, both internal and external.
>
>And just to clarify more:
>If you have a large *physical* drive partitioned as two or more
>logical drives it won't help performance-wise to put the vhd file of a
>guest on one of the extra partitions! THis is because the hard drive
>read head will still have to move between the C: and the other drive
>on ths single physical drive.
>You need different physical hard disks....
Sent: 12/01/2008
From: "Steve Jain [MVP]" <(email address - cut out)>
Message:On Mon, 1 Dec 2008 22:10:19 +0100 (CET), George Orwell
<(email address - cut out)> wrote:
In my experience, disk contention is always one of the major
performance issues, but I've only been using VPC since 2001...
--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/
Show quoted text
>In article <(email address - cut out)>
>"Steve Jain [MVP]" <(email address - cut out)> wrote:
>>
>> Ideally, you SHOULD run your OSes on a different hard drive than the
>> host OS is running on. Multiple OSes on a single hard drive are one
>> of the biggest performance issues with VMs.
>
>Only if you're running mulitple disk intensive VMs, otherwise this is not true.
Sent: 12/01/2008
From: "Mark Rae [MVP]" <(email address - cut out)>
Message:"simpleton" <(email address - cut out)> wrote in message
news:(email address - cut out)...
http://blogs.msdn.com/virtual_pc_guy/search.aspx?q=migrating&p=1
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
Show quoted text
>> VPC does *not* use physical hard drives, it uses emulated hard drives
>> that are data files on the host system.
>> So you would have to migrate your old PC into a virtual machine by
>> cloning the old physical drive to a virtual hard disk using software
>> like Ghost or Acronis.
>> Then you have to cope with the differences in hardware seen from the
>> virtual machine compared to the physical hardware seen from the old
>> machine's operating system. Hopefully the OS will handle it but
>> possibly via a repair install afterwards.
>>
>> It is *not* a "plunk" operation.....
>
> So, if I understand it, VPC creates a 30Gb directory, mirrors the old
> drive
> into it, then boots a new VM from it, like a partition in a dual-boot
> system,
> without the need to reboot the other VM?
Sent: 12/01/2008
From: "Steve Jain [MVP]" <(email address - cut out)>
Message:On Tue, 02 Dec 2008 01:37:26 +0100, Anonymous Remailer
<(email address - cut out)> wrote:
Whatever
--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/
Show quoted text
>In article <(email address - cut out)>
>"Steve Jain [MVP]" <(email address - cut out)> wrote:
>>
>> On Mon, 1 Dec 2008 22:10:19 +0100 (CET), George Orwell
>> <(email address - cut out)> wrote:
>>
>> >In article <(email address - cut out)>
>> >"Steve Jain [MVP]" <(email address - cut out)> wrote:
>> >>
>> >> Ideally, you SHOULD run your OSes on a different hard drive than the
>> >> host OS is running on. Multiple OSes on a single hard drive are one
>> >> of the biggest performance issues with VMs.
>> >
>> >Only if you're running mulitple disk intensive VMs, otherwise this is not true.
>>
>> In my experience, disk contention is always one of the major
>> performance issues, but I've only been using VPC since 2001...
>>
>
>Then you haven't been using it as long as I have and you're wrong as usual.
Sent: 12/01/2008
From: Bo Berglund <(email address - cut out)>
Message:On Mon, 1 Dec 2008 09:26:02 -0800, simpleton
<(email address - cut out)> wrote:
No that is not really how it works...
No 30Gb directory created for example...
VPC creates a "virtual machine" which is defined in two files
(initially). One is the Virtual Machine Configuration file (*.vmc),
which holds the data for the VPC2007 application to handle the
specifics of this machine like how much memory it uses, which hard
drives are connected to it, networking etc.
The other is one or several Virtual Hard Drive files (*.vhd) which
represent the contents of the hard disks in the virtual machine. There
are two kinds of VHD files, one that immediately assigns the complete
size of the disk to the VHD file (very wasteful of host system disk
space) and the other is the dynamically expanding type. This starts
out as a very small file on the host system (35 kb or so) even if it
is set to hold 32 Gb or more data. The file will expand on the host as
the virtual machine adds data to its hard drive.
When VPC2007 starts a virtual machine it will do so based on the vmc
file contents and the vhd disk drive. What happens next is that the
virtual machine boots up in a window on your host system and it looks
for bootable media, which it won't find at first because now you have
to install the operating system on to the virtual hard disk in exactly
the same way you do it on a physical computer. You need the install CD
for this.
However, in your case you could instead use the Acronis tools to
create a VHD image of your hard disk from the physical computer and
then use this as your drive in the virtual computer. That is what I
meant by migrating the physical computer.
Once all this is sorted out you will have a PC running in a window on
your host PC and this PC can be accessed via the network just like any
other networked PC can. So you should be able to do what you did
before via the network also with this virtual computer.
The virtual PC behaves to all intents and purposes exactly like a
physical computer.
--
Bo Berglund (Sweden)
Show quoted text
>
>"Bo Berglund" wrote:
>
>> No, you can't.
>> VPC does *not* use physical hard drives, it uses emulated hard drives
>> that are data files on the host system.
>> So you would have to migrate your old PC into a virtual machine by
>> cloning the old physical drive to a virtual hard disk using software
>> like Ghost or Acronis.
>> Then you have to cope with the differences in hardware seen from the
>> virtual machine compared to the physical hardware seen from the old
>> machine's operating system. Hopefully the OS will handle it but
>> possibly via a repair install afterwards.
>>
>> It is *not* a "plunk" operation.....
>> --
>That's too bad. When I got both machines networked, I just shared the whole
>C: drive on the Win98 machine, so I already have the ability to run
>everything on it from where I sit. Would be better if I Icould get rid of it.
>
>So, if I understand it, VPC creates a 30Gb directory, mirrors the old drive
>into it, then boots a new VM from it, like a partition in a dual-boot system,
>without the need to reboot the other VM?
>
Sent: 12/01/2008
From: "Mark Rae [MVP]" <(email address - cut out)>
Message:"simpleton" <(email address - cut out)> wrote in message
news:(email address - cut out)...
No. In fact, that would be a good idea...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
Show quoted text
> Is VPC going to complain if I want *.vhd on D: instead of C:?
Sent: 12/01/2008
From: Bo Berglund <(email address - cut out)>
Message:On Mon, 01 Dec 2008 11:10:48 -0800, "Steve Jain [MVP]"
<(email address - cut out)> wrote:
And just to clarify more:
If you have a large *physical* drive partitioned as two or more
logical drives it won't help performance-wise to put the vhd file of a
guest on one of the extra partitions! THis is because the hard drive
read head will still have to move between the C: and the other drive
on ths single physical drive.
You need different physical hard disks....
--
Bo Berglund (Sweden)
Show quoted text
>On Mon, 1 Dec 2008 10:24:04 -0800, simpleton
><(email address - cut out)> wrote:
>
>>Is VPC gonna complain if I want *.vhd on D: instead of C:?
>>
>>Ric
>>
>
>No, it's just a file. Does Word complain if you save a *.doc file on
>the D: drive?
>VPC is an application, and the .vmc and .vhd files that make it up are
>essentially data documents. They can be located anywhere on the
>system that has a drive letter and the necessary space to hold the
>files.
>Ideally, you SHOULD run your OSes on a different hard drive than the
>host OS is running on. Multiple OSes on a single hard drive are one
>of the biggest performance issues with VMs.
>I only run VMs on the C: drive of my laptop, and then only the single
>one I need access to at all times, otherwise, all my VMs are scattered
>over other hard drives, both internal and external.
Sent: 12/01/2008
From: George Orwell <(email address - cut out)>
Message:In article <(email address - cut out)>
"Steve Jain [MVP]" <(email address - cut out)> wrote:
Only if you're running mulitple disk intensive VMs, otherwise this is not true.
Il mittente di questo messaggio|The sender address of this
non corrisponde ad un utente |message is not related to a real
reale ma all'indirizzo fittizio|person but to a fake address of an
di un sistema anonimizzatore |anonymous system
Per maggiori informazioni |For more info
https://www.mixmaster.it
Show quoted text
>
> Ideally, you SHOULD run your OSes on a different hard drive than the
> host OS is running on. Multiple OSes on a single hard drive are one
> of the biggest performance issues with VMs.
Sent: 12/01/2008
From: "Mark Rae [MVP]" <(email address - cut out)>
Message:"Steve Jain [MVP]" <(email address - cut out)> wrote in message
news:(email address - cut out)...
Yeah, what do you know? LOL!
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
Show quoted text
>>> Ideally, you SHOULD run your OSes on a different hard drive than the
>>> host OS is running on. Multiple OSes on a single hard drive are one
>>> of the biggest performance issues with VMs.
>>
>>Only if you're running mulitple disk intensive VMs, otherwise this is not
>>true.
>
> In my experience, disk contention is always one of the major
> performance issues, but I've only been using VPC since 2001...
Sent: 12/02/2008
From: Nomen Nescio <(email address - cut out)>
Message:In article <#(email address - cut out)>
"Mark Rae [MVP]" <(email address - cut out)> wrote:
Not much obviously.
Show quoted text
>
> "Steve Jain [MVP]" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>
> >>> Ideally, you SHOULD run your OSes on a different hard drive than the
> >>> host OS is running on. Multiple OSes on a single hard drive are one
> >>> of the biggest performance issues with VMs.
> >>
> >>Only if you're running mulitple disk intensive VMs, otherwise this is not
> >>true.
> >
> > In my experience, disk contention is always one of the major
> > performance issues, but I've only been using VPC since 2001...
>
> Yeah, what do you know? LOL!
>
Sent: 12/02/2008
From: Anonymous Remailer <(email address - cut out)>
Message:In article <(email address - cut out)>
"Steve Jain [MVP]" <(email address - cut out)> wrote:
Then you haven't been using it as long as I have and you're wrong as usual.
Show quoted text
>
> On Mon, 1 Dec 2008 22:10:19 +0100 (CET), George Orwell
> <(email address - cut out)> wrote:
>
> >In article <(email address - cut out)>
> >"Steve Jain [MVP]" <(email address - cut out)> wrote:
> >>
> >> Ideally, you SHOULD run your OSes on a different hard drive than the
> >> host OS is running on. Multiple OSes on a single hard drive are one
> >> of the biggest performance issues with VMs.
> >
> >Only if you're running mulitple disk intensive VMs, otherwise this is not true.
>
> In my experience, disk contention is always one of the major
> performance issues, but I've only been using VPC since 2001...
>
Sent: 12/02/2008
From: "Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut>
Message:
"George Orwell" <(email address - cut out)> wrote in message
news:(email address - cut out)...
Note to self. Ignore this guys advice.
Show quoted text
> In article <(email address - cut out)>
> "Steve Jain [MVP]" <(email address - cut out)> wrote:
>>
>> Ideally, you SHOULD run your OSes on a different hard drive than the
>> host OS is running on. Multiple OSes on a single hard drive are one
>> of the biggest performance issues with VMs.
>
> Only if you're running mulitple disk intensive VMs, otherwise this is not
> true.
>
>
Sent: 12/02/2008
From: "Mark Rae [MVP]" <(email address - cut out)>
Message:"Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut> wrote in message
news:(email address - cut out)...
Simplest solution would be to add him to your killfile, as I have just done.
Steve's (and Bob Comer's) advice can be relied upon.
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
Show quoted text
>>> Ideally, you SHOULD run your OSes on a different hard drive than the
>>> host OS is running on. Multiple OSes on a single hard drive are one
>>> of the biggest performance issues with VMs.
>>
>> Only if you're running mulitple disk intensive VMs, otherwise this is not
>> true.
>>
> Note to self. Ignore this guy's advice.
Sent: 12/02/2008
From: Dave U. Random <(email address - cut out)>
Message:In article <(email address - cut out)>
"Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut> wrote:
Note to self. Another moron who knows nothing about how PCs work.
Show quoted text
>
>
> "George Orwell" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > In article <(email address - cut out)>
> > "Steve Jain [MVP]" <(email address - cut out)> wrote:
> >>
> >> Ideally, you SHOULD run your OSes on a different hard drive than the
> >> host OS is running on. Multiple OSes on a single hard drive are one
> >> of the biggest performance issues with VMs.
> >
> > Only if you're running mulitple disk intensive VMs, otherwise this is not
> > true.
> >
> >
> Note to self. Ignore this guys advice.
Sent: 12/02/2008
From: Dave U. Random <(email address - cut out)>
Message:In article <(email address - cut out)>
"Mark Rae [MVP]" <(email address - cut out)> wrote:
Sure, it you want bad advice.
Show quoted text
>
> "Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut> wrote in message
> news:(email address - cut out)...
>
> >>> Ideally, you SHOULD run your OSes on a different hard drive than the
> >>> host OS is running on. Multiple OSes on a single hard drive are one
> >>> of the biggest performance issues with VMs.
> >>
> >> Only if you're running mulitple disk intensive VMs, otherwise this is not
> >> true.
> >>
> > Note to self. Ignore this guy's advice.
>
> Simplest solution would be to add him to your killfile, as I have just done.
>
> Steve's (and Bob Comer's) advice can be relied upon.
>
Sent: 12/03/2008
From: Nomen Nescio <(email address - cut out)>
Message:In article <(email address - cut out)>
"Bill Grant" <not.available@online> wrote:
Too bad he can't grasp the fact that it's a PC issue and not a VPC issue.
For example, one VPC is calculating pi to 1,000 places while another is doing a defrag.
In this case does it matter where the .vhd files are?
Show quoted text
>
>
>
> "Dave U. Random" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > In article <(email address - cut out)>
> > "Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut> wrote:
> >>
> >>
> >> "George Orwell" <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >> > In article <(email address - cut out)>
> >> > "Steve Jain [MVP]" <(email address - cut out)> wrote:
> >> >>
> >> >> Ideally, you SHOULD run your OSes on a different hard drive than the
> >> >> host OS is running on. Multiple OSes on a single hard drive are one
> >> >> of the biggest performance issues with VMs.
> >> >
> >> > Only if you're running mulitple disk intensive VMs, otherwise this is
> >> > not
> >> > true.
> >> >
> >> >
> >> Note to self. Ignore this guys advice.
> >
> > Note to self. Another moron who knows nothing about how PCs work.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> Since Steve Jain was a test engineer for Connectix before Microsoft even
> bought the company, I know whose advice on VPC I would rely on.
Sent: 12/03/2008
From: "Bill Grant" <not.available@online>
Message:
"Dave U. Random" <(email address - cut out)> wrote in message
news:(email address - cut out)...
Since Steve Jain was a test engineer for Connectix before Microsoft even
bought the company, I know whose advice on VPC I would rely on.
Show quoted text
> In article <(email address - cut out)>
> "Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut> wrote:
>>
>>
>> "George Orwell" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > In article <(email address - cut out)>
>> > "Steve Jain [MVP]" <(email address - cut out)> wrote:
>> >>
>> >> Ideally, you SHOULD run your OSes on a different hard drive than the
>> >> host OS is running on. Multiple OSes on a single hard drive are one
>> >> of the biggest performance issues with VMs.
>> >
>> > Only if you're running mulitple disk intensive VMs, otherwise this is
>> > not
>> > true.
>> >
>> >
>> Note to self. Ignore this guys advice.
>
> Note to self. Another moron who knows nothing about how PCs work.
>
>
>
>
>
>
>
>
>
>
>
>
Sent: 12/03/2008
From: "Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut>
Message:
"Dave U. Random" <(email address - cut out)> wrote in message
news:(email address - cut out)...
I am glad you finally outed yourself as a moron. You just showed how stupid
you are because you just proved you know absolutely nothing.
Show quoted text
> In article <(email address - cut out)>
> "Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut> wrote:
>>
>>
>> "George Orwell" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > In article <(email address - cut out)>
>> > "Steve Jain [MVP]" <(email address - cut out)> wrote:
>> >>
>> >> Ideally, you SHOULD run your OSes on a different hard drive than the
>> >> host OS is running on. Multiple OSes on a single hard drive are one
>> >> of the biggest performance issues with VMs.
>> >
>> > Only if you're running mulitple disk intensive VMs, otherwise this is
>> > not
>> > true.
>> >
>> >
>> Note to self. Ignore this guys advice.
>
> Note to self. Another moron who knows nothing about how PCs work.
>
>
Sent: 12/03/2008
From: "Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut>
Message:
"Dave U. Random" <(email address - cut out)> wrote in message
news:(email address - cut out)...
You should try and use one nym also George Orwell. What a fool.
Show quoted text
> In article <(email address - cut out)>
> "Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut> wrote:
>>
>>
>> "George Orwell" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > In article <(email address - cut out)>
>> > "Steve Jain [MVP]" <(email address - cut out)> wrote:
>> >>
>> >> Ideally, you SHOULD run your OSes on a different hard drive than the
>> >> host OS is running on. Multiple OSes on a single hard drive are one
>> >> of the biggest performance issues with VMs.
>> >
>> > Only if you're running mulitple disk intensive VMs, otherwise this is
>> > not
>> > true.
>> >
>> >
>> Note to self. Ignore this guys advice.
>
> Note to self. Another moron who knows nothing about how PCs work.
>
>
Sent: 12/03/2008
From: "Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut>
Message:
"Nomen Nescio" <(email address - cut out)> wrote in message
news:(email address - cut out)...
To bad you change you nym every 3 seconds. It just proves your a troll.
Show quoted text
> In article <(email address - cut out)>
> "Bill Grant" <not.available@online> wrote:
>>
>>
>>
>> "Dave U. Random" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > In article <(email address - cut out)>
>> > "Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut> wrote:
>> >>
>> >>
>> >> "George Orwell" <(email address - cut out)> wrote in message
>> >> news:(email address - cut out)...
>> >> > In article <(email address - cut out)>
>> >> > "Steve Jain [MVP]" <(email address - cut out)> wrote:
>> >> >>
>> >> >> Ideally, you SHOULD run your OSes on a different hard drive than
>> >> >> the
>> >> >> host OS is running on. Multiple OSes on a single hard drive are
>> >> >> one
>> >> >> of the biggest performance issues with VMs.
>> >> >
>> >> > Only if you're running mulitple disk intensive VMs, otherwise this
>> >> > is
>> >> > not
>> >> > true.
>> >> >
>> >> >
>> >> Note to self. Ignore this guys advice.
>> >
>> > Note to self. Another moron who knows nothing about how PCs work.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> Since Steve Jain was a test engineer for Connectix before Microsoft
>> even
>> bought the company, I know whose advice on VPC I would rely on.
>
> Too bad he can't grasp the fact that it's a PC issue and not a VPC issue.
> For example, one VPC is calculating pi to 1,000 places while another is
> doing a defrag.
> In this case does it matter where the .vhd files are?
>
Sent: 12/03/2008
From: Dave U. Random <(email address - cut out)>
Message:In article <#(email address - cut out)>
"Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut> wrote:
ESAD.
Show quoted text
>
> What a fool.
Sent: 12/03/2008
From: "Non scrivetemi" <(email address - cut out)>
Message:In article <#(email address - cut out)>
"Ùpyøurbuttøø" <Ùpyøurbuttøø@Ùpyøurbuttøø.nut> wrote:
It's you're not your, mr gay upyourbutt.
Show quoted text
>
> It just proves your a troll.
Sent: 12/05/2008
From: Magnusb <(email address - cut out)>
Message:In article <(email address - cut out)>, noreply.-
@-.essjae.com says...
However, undo files and session state files will go to the location
where Virtual PC store .VMC (default somewhere in My Documents) so if
you are going to use these features you need to make sure you have
enough disk space on that drive.
Learned this the hard way. Couldn't understand why using undo disks was
so slow until I realized the files were stored under My Documents which
on my machine is redirected to a network drive :-).
You can change the location where VPC store .VMC files. I think you set
the location using an environment variable MYVIRTUALMACHINES if I
remember correctly.
Show quoted text
> No, it's just a file. Does Word complain if you save a *.doc file on
> the D: drive?
> VPC is an application, and the .vmc and .vhd files that make it up are
> essentially data documents. They can be located anywhere on the
> system that has a drive letter and the necessary space to hold the
> files.
Wiki