> Hi,
>
> I've been using VPC for awhile now, but I've been starting to use VPC more
> frequently for testing. This is on a machine with Win2K Server and 2.5GB
> of memory.
>
> I've noticed that I'm frequently getting situations where VPC (and the
> guest hosts) will either freeze completely, or I get a popup error saying
> "An error has occurred" (and asking if I want to send something to MS).
> This happens frequently when I try to run the following guests:
>
> Guest1: Win2K Server SP4, 900MB memory allocated
> Guest2: Win2K Server SP4, 700MB memory allocated
> Guest3: Win2K Server SP4, 512MB memory allocated
>
> I especially notice this happening when more than one of the guests happen
> to be trying to start simultaenously, but it'll happen even when I start
> the guests one at a time.
>
> The total memory allocated for the guests is about 2.1GB, and I'm
> wondering if the ~400MB that is left for the host might not be enough and
> causing these problems?
>
> Thanks,
> Jim

> One way to find out is to reduce the ram allocated until the problem
> dissappears.
>
> "ohaya" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Hi,
>>
>> I've been using VPC for awhile now, but I've been starting to use VPC more
>> frequently for testing. This is on a machine with Win2K Server and 2.5GB
>> of memory.
>>
>> I've noticed that I'm frequently getting situations where VPC (and the
>> guest hosts) will either freeze completely, or I get a popup error saying
>> "An error has occurred" (and asking if I want to send something to MS).
>> This happens frequently when I try to run the following guests:
>>
>> Guest1: Win2K Server SP4, 900MB memory allocated
>> Guest2: Win2K Server SP4, 700MB memory allocated
>> Guest3: Win2K Server SP4, 512MB memory allocated
>>
>> I especially notice this happening when more than one of the guests happen
>> to be trying to start simultaenously, but it'll happen even when I start
>> the guests one at a time.
>>
>> The total memory allocated for the guests is about 2.1GB, and I'm
>> wondering if the ~400MB that is left for the host might not be enough and
>> causing these problems?
>>
>> Thanks,
>> Jim
>
>

> Hi,
>
> I just got the additional 2GB in today, and installed it.
> Unfortunately, my mobo apparently only can handle ~3.3GB, even with 4
> sticks of 1GB RAM. Anyway, it's about 700MB more than I had before, and
> the guest hosts STILL hang occasionally.
>
> I'm running a memory test now, to see if that could be the problem, but
> does anyone have any other ideas about what the problem might be?
>
> I've also increased the swap disk size on each guest to about 2.5GB, but
> still the same problem :(!!
>
> Jim
>
>
>
> ohaya wrote:
>>
>> Colin,
>>
>> Unless I'm misunderstanding your suggestion, I don't think that I can do
>> that, because if I reduce the memory allocated for the guest hosts, as I
>> posted originally, the apps that I'm running in the guest hosts (in
>> particular, two instances of BEA WebLogic in the larger guests) won't
>> run.
>>
>> I've increased the pagefile size on the larger guests to over 2.5GB, but
>> am still having the problem.
>>
>> I have an additional 2GB of RAM on order and will try that when it gets
>> here, but if anyone has any other suggestions, please post. Also FYI, I
>> have VM Additions installed on all 3 guests.
>>
>> Jim
>>
>> Colin Barnhorst wrote:
>> > One way to find out is to reduce the ram allocated until the problem
>> > dissappears.
>> >
>> > "ohaya" <(email address - cut out)> wrote in message
>> > news:(email address - cut out)...
>> >> Hi,
>> >>
>> >> I've been using VPC for awhile now, but I've been starting to use VPC
>> >> more
>> >> frequently for testing. This is on a machine with Win2K Server and
>> >> 2.5GB
>> >> of memory.
>> >>
>> >> I've noticed that I'm frequently getting situations where VPC (and the
>> >> guest hosts) will either freeze completely, or I get a popup error
>> >> saying
>> >> "An error has occurred" (and asking if I want to send something to
>> >> MS).
>> >> This happens frequently when I try to run the following guests:
>> >>
>> >> Guest1: Win2K Server SP4, 900MB memory allocated
>> >> Guest2: Win2K Server SP4, 700MB memory allocated
>> >> Guest3: Win2K Server SP4, 512MB memory allocated
>> >>
>> >> I especially notice this happening when more than one of the guests
>> >> happen
>> >> to be trying to start simultaenously, but it'll happen even when I
>> >> start
>> >> the guests one at a time.
>> >>
>> >> The total memory allocated for the guests is about 2.1GB, and I'm
>> >> wondering if the ~400MB that is left for the host might not be enough
>> >> and
>> >> causing these problems?
>> >>
>> >> Thanks,
>> >> Jim
>> >
>> >

>
> Colin,
>
> Unless I'm misunderstanding your suggestion, I don't think that I can do
> that, because if I reduce the memory allocated for the guest hosts, as I
> posted originally, the apps that I'm running in the guest hosts (in
> particular, two instances of BEA WebLogic in the larger guests) won't run.
>
> I've increased the pagefile size on the larger guests to over 2.5GB, but
> am still having the problem.
>
> I have an additional 2GB of RAM on order and will try that when it gets
> here, but if anyone has any other suggestions, please post. Also FYI, I
> have VM Additions installed on all 3 guests.
>
> Jim
>
> Colin Barnhorst wrote:
> > One way to find out is to reduce the ram allocated until the problem
> > dissappears.
> >
> > "ohaya" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> >> Hi,
> >>
> >> I've been using VPC for awhile now, but I've been starting to use VPC more
> >> frequently for testing. This is on a machine with Win2K Server and 2.5GB
> >> of memory.
> >>
> >> I've noticed that I'm frequently getting situations where VPC (and the
> >> guest hosts) will either freeze completely, or I get a popup error saying
> >> "An error has occurred" (and asking if I want to send something to MS).
> >> This happens frequently when I try to run the following guests:
> >>
> >> Guest1: Win2K Server SP4, 900MB memory allocated
> >> Guest2: Win2K Server SP4, 700MB memory allocated
> >> Guest3: Win2K Server SP4, 512MB memory allocated
> >>
> >> I especially notice this happening when more than one of the guests happen
> >> to be trying to start simultaenously, but it'll happen even when I start
> >> the guests one at a time.
> >>
> >> The total memory allocated for the guests is about 2.1GB, and I'm
> >> wondering if the ~400MB that is left for the host might not be enough and
> >> causing these problems?
> >>
> >> Thanks,
> >> Jim
> >
> >

> Colin,
>
> What you say "That is normal", what do you mean by "That"? Do you mean
> the guests hanging is "normal"?
>
> Jim
>
>
>
> Colin Barnhorst wrote:
>> That is normal on XP x86.
>>
>> "ohaya" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> Hi,
>>>
>>> I just got the additional 2GB in today, and installed it.
>>> Unfortunately, my mobo apparently only can handle ~3.3GB, even with 4
>>> sticks of 1GB RAM. Anyway, it's about 700MB more than I had before, and
>>> the guest hosts STILL hang occasionally.
>>>
>>> I'm running a memory test now, to see if that could be the problem, but
>>> does anyone have any other ideas about what the problem might be?
>>>
>>> I've also increased the swap disk size on each guest to about 2.5GB, but
>>> still the same problem :(!!
>>>
>>> Jim
>>>
>>>
>>>
>>> ohaya wrote:
>>>> Colin,
>>>>
>>>> Unless I'm misunderstanding your suggestion, I don't think that I can
>>>> do
>>>> that, because if I reduce the memory allocated for the guest hosts, as
>>>> I
>>>> posted originally, the apps that I'm running in the guest hosts (in
>>>> particular, two instances of BEA WebLogic in the larger guests) won't
>>>> run.
>>>>
>>>> I've increased the pagefile size on the larger guests to over 2.5GB,
>>>> but
>>>> am still having the problem.
>>>>
>>>> I have an additional 2GB of RAM on order and will try that when it gets
>>>> here, but if anyone has any other suggestions, please post. Also FYI,
>>>> I
>>>> have VM Additions installed on all 3 guests.
>>>>
>>>> Jim
>>>>
>>>> Colin Barnhorst wrote:
>>>>> One way to find out is to reduce the ram allocated until the problem
>>>>> dissappears.
>>>>>
>>>>> "ohaya" <(email address - cut out)> wrote in message
>>>>> news:(email address - cut out)...
>>>>>> Hi,
>>>>>>
>>>>>> I've been using VPC for awhile now, but I've been starting to use VPC
>>>>>> more
>>>>>> frequently for testing. This is on a machine with Win2K Server and
>>>>>> 2.5GB
>>>>>> of memory.
>>>>>>
>>>>>> I've noticed that I'm frequently getting situations where VPC (and
>>>>>> the
>>>>>> guest hosts) will either freeze completely, or I get a popup error
>>>>>> saying
>>>>>> "An error has occurred" (and asking if I want to send something to
>>>>>> MS).
>>>>>> This happens frequently when I try to run the following guests:
>>>>>>
>>>>>> Guest1: Win2K Server SP4, 900MB memory allocated
>>>>>> Guest2: Win2K Server SP4, 700MB memory allocated
>>>>>> Guest3: Win2K Server SP4, 512MB memory allocated
>>>>>>
>>>>>> I especially notice this happening when more than one of the guests
>>>>>> happen
>>>>>> to be trying to start simultaenously, but it'll happen even when I
>>>>>> start
>>>>>> the guests one at a time.
>>>>>>
>>>>>> The total memory allocated for the guests is about 2.1GB, and I'm
>>>>>> wondering if the ~400MB that is left for the host might not be enough
>>>>>> and
>>>>>> causing these problems?
>>>>>>
>>>>>> Thanks,
>>>>>> Jim
>>>>>
>>

> That is normal on XP x86.
>
> "ohaya" <(email address - cut out)> wrote in message news:(email address - cut out)...
>> Hi,
>>
>> I just got the additional 2GB in today, and installed it.
>> Unfortunately, my mobo apparently only can handle ~3.3GB, even with 4
>> sticks of 1GB RAM. Anyway, it's about 700MB more than I had before, and
>> the guest hosts STILL hang occasionally.
>>
>> I'm running a memory test now, to see if that could be the problem, but
>> does anyone have any other ideas about what the problem might be?
>>
>> I've also increased the swap disk size on each guest to about 2.5GB, but
>> still the same problem :(!!
>>
>> Jim
>>
>>
>>
>> ohaya wrote:
>>> Colin,
>>>
>>> Unless I'm misunderstanding your suggestion, I don't think that I can do
>>> that, because if I reduce the memory allocated for the guest hosts, as I
>>> posted originally, the apps that I'm running in the guest hosts (in
>>> particular, two instances of BEA WebLogic in the larger guests) won't
>>> run.
>>>
>>> I've increased the pagefile size on the larger guests to over 2.5GB, but
>>> am still having the problem.
>>>
>>> I have an additional 2GB of RAM on order and will try that when it gets
>>> here, but if anyone has any other suggestions, please post. Also FYI, I
>>> have VM Additions installed on all 3 guests.
>>>
>>> Jim
>>>
>>> Colin Barnhorst wrote:
>>>> One way to find out is to reduce the ram allocated until the problem
>>>> dissappears.
>>>>
>>>> "ohaya" <(email address - cut out)> wrote in message
>>>> news:(email address - cut out)...
>>>>> Hi,
>>>>>
>>>>> I've been using VPC for awhile now, but I've been starting to use VPC
>>>>> more
>>>>> frequently for testing. This is on a machine with Win2K Server and
>>>>> 2.5GB
>>>>> of memory.
>>>>>
>>>>> I've noticed that I'm frequently getting situations where VPC (and the
>>>>> guest hosts) will either freeze completely, or I get a popup error
>>>>> saying
>>>>> "An error has occurred" (and asking if I want to send something to
>>>>> MS).
>>>>> This happens frequently when I try to run the following guests:
>>>>>
>>>>> Guest1: Win2K Server SP4, 900MB memory allocated
>>>>> Guest2: Win2K Server SP4, 700MB memory allocated
>>>>> Guest3: Win2K Server SP4, 512MB memory allocated
>>>>>
>>>>> I especially notice this happening when more than one of the guests
>>>>> happen
>>>>> to be trying to start simultaenously, but it'll happen even when I
>>>>> start
>>>>> the guests one at a time.
>>>>>
>>>>> The total memory allocated for the guests is about 2.1GB, and I'm
>>>>> wondering if the ~400MB that is left for the host might not be enough
>>>>> and
>>>>> causing these problems?
>>>>>
>>>>> Thanks,
>>>>> Jim
>>>>
>
>

> Hi,
>
> I just got the additional 2GB in today, and installed it.
> Unfortunately, my mobo apparently only can handle ~3.3GB, even with 4
> sticks of 1GB RAM. Anyway, it's about 700MB more than I had before, and
> the guest hosts STILL hang occasionally.
>
> I'm running a memory test now, to see if that could be the problem, but
> does anyone have any other ideas about what the problem might be?
>
> I've also increased the swap disk size on each guest to about 2.5GB, but
> still the same problem :(!!
>
> Jim
>
>
>
> ohaya wrote:
>>
>> Colin,
>>
>> Unless I'm misunderstanding your suggestion, I don't think that I can do
>> that, because if I reduce the memory allocated for the guest hosts, as I
>> posted originally, the apps that I'm running in the guest hosts (in
>> particular, two instances of BEA WebLogic in the larger guests) won't
>> run.
>>
>> I've increased the pagefile size on the larger guests to over 2.5GB, but
>> am still having the problem.
>>
>> I have an additional 2GB of RAM on order and will try that when it gets
>> here, but if anyone has any other suggestions, please post. Also FYI, I
>> have VM Additions installed on all 3 guests.
>>
>> Jim
>>
>> Colin Barnhorst wrote:
>> > One way to find out is to reduce the ram allocated until the problem
>> > dissappears.
>> >
>> > "ohaya" <(email address - cut out)> wrote in message
>> > news:(email address - cut out)...
>> >> Hi,
>> >>
>> >> I've been using VPC for awhile now, but I've been starting to use VPC
>> >> more
>> >> frequently for testing. This is on a machine with Win2K Server and
>> >> 2.5GB
>> >> of memory.
>> >>
>> >> I've noticed that I'm frequently getting situations where VPC (and the
>> >> guest hosts) will either freeze completely, or I get a popup error
>> >> saying
>> >> "An error has occurred" (and asking if I want to send something to
>> >> MS).
>> >> This happens frequently when I try to run the following guests:
>> >>
>> >> Guest1: Win2K Server SP4, 900MB memory allocated
>> >> Guest2: Win2K Server SP4, 700MB memory allocated
>> >> Guest3: Win2K Server SP4, 512MB memory allocated
>> >>
>> >> I especially notice this happening when more than one of the guests
>> >> happen
>> >> to be trying to start simultaenously, but it'll happen even when I
>> >> start
>> >> the guests one at a time.
>> >>
>> >> The total memory allocated for the guests is about 2.1GB, and I'm
>> >> wondering if the ~400MB that is left for the host might not be enough
>> >> and
>> >> causing these problems?
>> >>
>> >> Thanks,
>> >> Jim
>> >
>> >

> If the internal drives are IDE then you probably didn't benefit by the move.
> The ideal situation would be to have the files on a separate spindle on a
> separate controller from the system.
>
> "ohaya" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Hi,
>>
>> I also moved all of the VHDs and VMCs to my internal hard drive
>> (originally they were on an external USB2 drive), and I STILL get the
>> same problem. If anything, it hangs more often.
>>
>> Jim
>>
>>
>>
>>
>> ohaya wrote:
>>> [Posting this from Google Groups]
>>>
>>> Jonathan,
>>>
>>> I thought the PAE was only needed for *above* 4GB or memory?
>>>
>>> Also, even without seeing the whole 4GB, I now have 3,390MB, which
>>> seems like it should be plenty for the list of guests in my earlier
>>> email, and it STILL hangs. I should be clear: ALL the guests hang at
>>> the same time, and in Task Manager, it says "not responding". When I
>>> kill one guest, it kills them ALL.
>>>
>>> FYI, I ran a full memory test all night using Doc Memory on what memory
>>> was there, and it was fine.
>>>
>>> Also when it hangs, Task Manager in the real PC is showing 2-5% usage.
>>>
>>> This has got to be some kind of bug in VPC?
>>>
>>> Jim
>>>
>>>
>>>
>>> Jonathan Maltz [MS-MVP] wrote:
>>>> Hi,
>>>>
>>>> Try adding the /PAE switch to your OS in boot.ini. It should enable
>>>> you to
>>>> take full advantage of the 4 GB of RAM
>>>> (http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx)
>>>>
>>>> --
>>>> --Jonathan Maltz [Microsoft MVP - Windows Server - IIS, Virtual PC]
>>>> http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
>>>> tutorial site :-)
>>>> http://vpc.visualwin.com - Does <insert OS name> work on VPC 2004?
>>>> Find out
>>>> here
>>>> Only reply by newsgroup. I do not do technical support via email. Any
>>>> emails I have not authorized are deleted before I see them.
>>>>
>>>>
>>>> "ohaya" <(email address - cut out)> wrote in message
>>>> news:(email address - cut out)...
>>>>> Hi,
>>>>>
>>>>> I just got the additional 2GB in today, and installed it.
>>>>> Unfortunately, my mobo apparently only can handle ~3.3GB, even with 4
>>>>> sticks of 1GB RAM. Anyway, it's about 700MB more than I had before,
>>>>> and
>>>>> the guest hosts STILL hang occasionally.
>>>>>
>>>>> I'm running a memory test now, to see if that could be the problem,
>>>>> but
>>>>> does anyone have any other ideas about what the problem might be?
>>>>>
>>>>> I've also increased the swap disk size on each guest to about 2.5GB,
>>>>> but
>>>>> still the same problem :(!!
>>>>>
>>>>> Jim
>>>>>
>>>>>
>>>>>
>>>>> ohaya wrote:
>>>>>> Colin,
>>>>>>
>>>>>> Unless I'm misunderstanding your suggestion, I don't think that I
>>>>>> can do
>>>>>> that, because if I reduce the memory allocated for the guest hosts,
>>>>>> as I
>>>>>> posted originally, the apps that I'm running in the guest hosts (in
>>>>>> particular, two instances of BEA WebLogic in the larger guests)
>>>>>> won't
>>>>>> run.
>>>>>>
>>>>>> I've increased the pagefile size on the larger guests to over 2.5GB,
>>>>>> but
>>>>>> am still having the problem.
>>>>>>
>>>>>> I have an additional 2GB of RAM on order and will try that when it
>>>>>> gets
>>>>>> here, but if anyone has any other suggestions, please post. Also
>>>>>> FYI, I
>>>>>> have VM Additions installed on all 3 guests.
>>>>>>
>>>>>> Jim
>>>>>>
>>>>>> Colin Barnhorst wrote:
>>>>>>> One way to find out is to reduce the ram allocated until the
>>>>>>> problem
>>>>>>> dissappears.
>>>>>>>
>>>>>>> "ohaya" <(email address - cut out)> wrote in message
>>>>>>> news:(email address - cut out)...
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I've been using VPC for awhile now, but I've been starting to use
>>>>>>>> VPC
>>>>>>>> more
>>>>>>>> frequently for testing. This is on a machine with Win2K Server
>>>>>>>> and
>>>>>>>> 2.5GB
>>>>>>>> of memory.
>>>>>>>>
>>>>>>>> I've noticed that I'm frequently getting situations where VPC
>>>>>>>> (and the
>>>>>>>> guest hosts) will either freeze completely, or I get a popup
>>>>>>>> error
>>>>>>>> saying
>>>>>>>> "An error has occurred" (and asking if I want to send something
>>>>>>>> to
>>>>>>>> MS).
>>>>>>>> This happens frequently when I try to run the following guests:
>>>>>>>>
>>>>>>>> Guest1: Win2K Server SP4, 900MB memory allocated
>>>>>>>> Guest2: Win2K Server SP4, 700MB memory allocated
>>>>>>>> Guest3: Win2K Server SP4, 512MB memory allocated
>>>>>>>>
>>>>>>>> I especially notice this happening when more than one of the
>>>>>>>> guests
>>>>>>>> happen
>>>>>>>> to be trying to start simultaenously, but it'll happen even when
>>>>>>>> I
>>>>>>>> start
>>>>>>>> the guests one at a time.
>>>>>>>>
>>>>>>>> The total memory allocated for the guests is about 2.1GB, and I'm
>>>>>>>> wondering if the ~400MB that is left for the host might not be
>>>>>>>> enough
>>>>>>>> and
>>>>>>>> causing these problems?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Jim
>>>>>>>
>
>

> Colin,
>
> I just moved the guests in question to a 2nd IDE drive, and I am seeing
> exactly the same problem. This 2nd drive is on the 2nd IDE port on my
> motherboard because I don't have a 2nd IDE controller available.
>
> So now, so far, I have increased physical memory and added a 2nd drive
> for the guests, and am still having this problem.
>
> BTW, am I the only one who is seeing this behavior? Or is this
> occurring for others at all?
>
> Thanks,
> Jim
>
>
> Colin Barnhorst wrote:
>> If the internal drives are IDE then you probably didn't benefit by the
>> move. The ideal situation would be to have the files on a separate
>> spindle on a separate controller from the system.
>>
>> "ohaya" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> Hi,
>>>
>>> I also moved all of the VHDs and VMCs to my internal hard drive
>>> (originally they were on an external USB2 drive), and I STILL get the
>>> same problem. If anything, it hangs more often.
>>>
>>> Jim
>>>
>>>
>>>
>>>
>>> ohaya wrote:
>>>> [Posting this from Google Groups]
>>>>
>>>> Jonathan,
>>>>
>>>> I thought the PAE was only needed for *above* 4GB or memory?
>>>>
>>>> Also, even without seeing the whole 4GB, I now have 3,390MB, which
>>>> seems like it should be plenty for the list of guests in my earlier
>>>> email, and it STILL hangs. I should be clear: ALL the guests hang at
>>>> the same time, and in Task Manager, it says "not responding". When I
>>>> kill one guest, it kills them ALL.
>>>>
>>>> FYI, I ran a full memory test all night using Doc Memory on what memory
>>>> was there, and it was fine.
>>>>
>>>> Also when it hangs, Task Manager in the real PC is showing 2-5% usage.
>>>>
>>>> This has got to be some kind of bug in VPC?
>>>>
>>>> Jim
>>>>
>>>>
>>>>
>>>> Jonathan Maltz [MS-MVP] wrote:
>>>>> Hi,
>>>>>
>>>>> Try adding the /PAE switch to your OS in boot.ini. It should
>>>>> enable you to
>>>>> take full advantage of the 4 GB of RAM
>>>>> (http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx)
>>>>>
>>>>> --
>>>>> --Jonathan Maltz [Microsoft MVP - Windows Server - IIS, Virtual PC]
>>>>> http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
>>>>> tutorial site :-)
>>>>> http://vpc.visualwin.com - Does <insert OS name> work on VPC 2004?
>>>>> Find out
>>>>> here
>>>>> Only reply by newsgroup. I do not do technical support via email.
>>>>> Any
>>>>> emails I have not authorized are deleted before I see them.
>>>>>
>>>>>
>>>>> "ohaya" <(email address - cut out)> wrote in message
>>>>> news:(email address - cut out)...
>>>>>> Hi,
>>>>>>
>>>>>> I just got the additional 2GB in today, and installed it.
>>>>>> Unfortunately, my mobo apparently only can handle ~3.3GB, even with 4
>>>>>> sticks of 1GB RAM. Anyway, it's about 700MB more than I had
>>>>>> before, and
>>>>>> the guest hosts STILL hang occasionally.
>>>>>>
>>>>>> I'm running a memory test now, to see if that could be the
>>>>>> problem, but
>>>>>> does anyone have any other ideas about what the problem might be?
>>>>>>
>>>>>> I've also increased the swap disk size on each guest to about
>>>>>> 2.5GB, but
>>>>>> still the same problem :(!!
>>>>>>
>>>>>> Jim
>>>>>>
>>>>>>
>>>>>>
>>>>>> ohaya wrote:
>>>>>>> Colin,
>>>>>>>
>>>>>>> Unless I'm misunderstanding your suggestion, I don't think that I
>>>>>>> can do
>>>>>>> that, because if I reduce the memory allocated for the guest
>>>>>>> hosts, as I
>>>>>>> posted originally, the apps that I'm running in the guest hosts (in
>>>>>>> particular, two instances of BEA WebLogic in the larger guests)
>>>>>>> won't
>>>>>>> run.
>>>>>>>
>>>>>>> I've increased the pagefile size on the larger guests to over
>>>>>>> 2.5GB, but
>>>>>>> am still having the problem.
>>>>>>>
>>>>>>> I have an additional 2GB of RAM on order and will try that when
>>>>>>> it gets
>>>>>>> here, but if anyone has any other suggestions, please post. Also
>>>>>>> FYI, I
>>>>>>> have VM Additions installed on all 3 guests.
>>>>>>>
>>>>>>> Jim
>>>>>>>
>>>>>>> Colin Barnhorst wrote:
>>>>>>>> One way to find out is to reduce the ram allocated until the
>>>>>>>> problem
>>>>>>>> dissappears.
>>>>>>>>
>>>>>>>> "ohaya" <(email address - cut out)> wrote in message
>>>>>>>> news:(email address - cut out)...
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I've been using VPC for awhile now, but I've been starting to
>>>>>>>>> use VPC
>>>>>>>>> more
>>>>>>>>> frequently for testing. This is on a machine with Win2K Server
>>>>>>>>> and
>>>>>>>>> 2.5GB
>>>>>>>>> of memory.
>>>>>>>>>
>>>>>>>>> I've noticed that I'm frequently getting situations where VPC
>>>>>>>>> (and the
>>>>>>>>> guest hosts) will either freeze completely, or I get a popup error
>>>>>>>>> saying
>>>>>>>>> "An error has occurred" (and asking if I want to send something to
>>>>>>>>> MS).
>>>>>>>>> This happens frequently when I try to run the following guests:
>>>>>>>>>
>>>>>>>>> Guest1: Win2K Server SP4, 900MB memory allocated
>>>>>>>>> Guest2: Win2K Server SP4, 700MB memory allocated
>>>>>>>>> Guest3: Win2K Server SP4, 512MB memory allocated
>>>>>>>>>
>>>>>>>>> I especially notice this happening when more than one of the
>>>>>>>>> guests
>>>>>>>>> happen
>>>>>>>>> to be trying to start simultaenously, but it'll happen even when I
>>>>>>>>> start
>>>>>>>>> the guests one at a time.
>>>>>>>>>
>>>>>>>>> The total memory allocated for the guests is about 2.1GB, and I'm
>>>>>>>>> wondering if the ~400MB that is left for the host might not be
>>>>>>>>> enough
>>>>>>>>> and
>>>>>>>>> causing these problems?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Jim
>>>>>>>>
>>
>>

> Colin,
>
> I just moved the guests in question to a 2nd IDE drive, and I am seeing
> exactly the same problem. This 2nd drive is on the 2nd IDE port on my
> motherboard because I don't have a 2nd IDE controller available.
>
> So now, so far, I have increased physical memory and added a 2nd drive for
> the guests, and am still having this problem.
>
> BTW, am I the only one who is seeing this behavior? Or is this occurring
> for others at all?
>
> Thanks,
> Jim
>
>
> Colin Barnhorst wrote:
>> If the internal drives are IDE then you probably didn't benefit by the
>> move. The ideal situation would be to have the files on a separate
>> spindle on a separate controller from the system.
>>
>> "ohaya" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> Hi,
>>>
>>> I also moved all of the VHDs and VMCs to my internal hard drive
>>> (originally they were on an external USB2 drive), and I STILL get the
>>> same problem. If anything, it hangs more often.
>>>
>>> Jim
>>>
>>>
>>>
>>>
>>> ohaya wrote:
>>>> [Posting this from Google Groups]
>>>>
>>>> Jonathan,
>>>>
>>>> I thought the PAE was only needed for *above* 4GB or memory?
>>>>
>>>> Also, even without seeing the whole 4GB, I now have 3,390MB, which
>>>> seems like it should be plenty for the list of guests in my earlier
>>>> email, and it STILL hangs. I should be clear: ALL the guests hang at
>>>> the same time, and in Task Manager, it says "not responding". When I
>>>> kill one guest, it kills them ALL.
>>>>
>>>> FYI, I ran a full memory test all night using Doc Memory on what memory
>>>> was there, and it was fine.
>>>>
>>>> Also when it hangs, Task Manager in the real PC is showing 2-5% usage.
>>>>
>>>> This has got to be some kind of bug in VPC?
>>>>
>>>> Jim
>>>>
>>>>
>>>>
>>>> Jonathan Maltz [MS-MVP] wrote:
>>>>> Hi,
>>>>>
>>>>> Try adding the /PAE switch to your OS in boot.ini. It should enable
>>>>> you to
>>>>> take full advantage of the 4 GB of RAM
>>>>> (http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx)
>>>>>
>>>>> --
>>>>> --Jonathan Maltz [Microsoft MVP - Windows Server - IIS, Virtual PC]
>>>>> http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
>>>>> tutorial site :-)
>>>>> http://vpc.visualwin.com - Does <insert OS name> work on VPC 2004?
>>>>> Find out
>>>>> here
>>>>> Only reply by newsgroup. I do not do technical support via email.
>>>>> Any
>>>>> emails I have not authorized are deleted before I see them.
>>>>>
>>>>>
>>>>> "ohaya" <(email address - cut out)> wrote in message
>>>>> news:(email address - cut out)...
>>>>>> Hi,
>>>>>>
>>>>>> I just got the additional 2GB in today, and installed it.
>>>>>> Unfortunately, my mobo apparently only can handle ~3.3GB, even with 4
>>>>>> sticks of 1GB RAM. Anyway, it's about 700MB more than I had before,
>>>>>> and
>>>>>> the guest hosts STILL hang occasionally.
>>>>>>
>>>>>> I'm running a memory test now, to see if that could be the problem,
>>>>>> but
>>>>>> does anyone have any other ideas about what the problem might be?
>>>>>>
>>>>>> I've also increased the swap disk size on each guest to about 2.5GB,
>>>>>> but
>>>>>> still the same problem :(!!
>>>>>>
>>>>>> Jim
>>>>>>
>>>>>>
>>>>>>
>>>>>> ohaya wrote:
>>>>>>> Colin,
>>>>>>>
>>>>>>> Unless I'm misunderstanding your suggestion, I don't think that I
>>>>>>> can do
>>>>>>> that, because if I reduce the memory allocated for the guest hosts,
>>>>>>> as I
>>>>>>> posted originally, the apps that I'm running in the guest hosts (in
>>>>>>> particular, two instances of BEA WebLogic in the larger guests)
>>>>>>> won't
>>>>>>> run.
>>>>>>>
>>>>>>> I've increased the pagefile size on the larger guests to over 2.5GB,
>>>>>>> but
>>>>>>> am still having the problem.
>>>>>>>
>>>>>>> I have an additional 2GB of RAM on order and will try that when it
>>>>>>> gets
>>>>>>> here, but if anyone has any other suggestions, please post. Also
>>>>>>> FYI, I
>>>>>>> have VM Additions installed on all 3 guests.
>>>>>>>
>>>>>>> Jim
>>>>>>>
>>>>>>> Colin Barnhorst wrote:
>>>>>>>> One way to find out is to reduce the ram allocated until the
>>>>>>>> problem
>>>>>>>> dissappears.
>>>>>>>>
>>>>>>>> "ohaya" <(email address - cut out)> wrote in message
>>>>>>>> news:(email address - cut out)...
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I've been using VPC for awhile now, but I've been starting to use
>>>>>>>>> VPC
>>>>>>>>> more
>>>>>>>>> frequently for testing. This is on a machine with Win2K Server
>>>>>>>>> and
>>>>>>>>> 2.5GB
>>>>>>>>> of memory.
>>>>>>>>>
>>>>>>>>> I've noticed that I'm frequently getting situations where VPC (and
>>>>>>>>> the
>>>>>>>>> guest hosts) will either freeze completely, or I get a popup error
>>>>>>>>> saying
>>>>>>>>> "An error has occurred" (and asking if I want to send something to
>>>>>>>>> MS).
>>>>>>>>> This happens frequently when I try to run the following guests:
>>>>>>>>>
>>>>>>>>> Guest1: Win2K Server SP4, 900MB memory allocated
>>>>>>>>> Guest2: Win2K Server SP4, 700MB memory allocated
>>>>>>>>> Guest3: Win2K Server SP4, 512MB memory allocated
>>>>>>>>>
>>>>>>>>> I especially notice this happening when more than one of the
>>>>>>>>> guests
>>>>>>>>> happen
>>>>>>>>> to be trying to start simultaenously, but it'll happen even when I
>>>>>>>>> start
>>>>>>>>> the guests one at a time.
>>>>>>>>>
>>>>>>>>> The total memory allocated for the guests is about 2.1GB, and I'm
>>>>>>>>> wondering if the ~400MB that is left for the host might not be
>>>>>>>>> enough
>>>>>>>>> and
>>>>>>>>> causing these problems?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Jim
>>>>>>>>
>>

> Just to try something -- try adding the /NoExecute=AlwaysOff to your OS
> line in the boot.ini, just to see if that makes any difference. (This turns
> off DEP)
>

> Bob,
>
> A couple of questions:
>
> 1) Are you suggesting putting this in the boot.ini for the 'real' PC, or
> in the boot.ini for the guest hosts, or for BOTH?
>
> 2) From what I've been able to find, this parameter is only for Windows
> XP SP2 and Win2K3? Is it applicable to Win2K Server SP4 also?
>
> Jim
>
>
>
> Robert Comer wrote:
>> Just to try something -- try adding the /NoExecute=AlwaysOff to your
>> OS line in the boot.ini, just to see if that makes any difference.
>> (This turns off DEP)
>>

> in the boot.ini for the guest hosts, or for BOTH?
> 2) From what I've been able to find, this parameter is only for Windows XP
> SP2 and Win2K3? Is it applicable to Win2K Server SP4 also?
> Bob,
>
> A couple of questions:
>
> 1) Are you suggesting putting this in the boot.ini for the 'real' PC, or
> in the boot.ini for the guest hosts, or for BOTH?
>
> 2) From what I've been able to find, this parameter is only for Windows XP
> SP2 and Win2K3? Is it applicable to Win2K Server SP4 also?
>
> Jim
>
>
>
> Robert Comer wrote:
>> Just to try something -- try adding the /NoExecute=AlwaysOff to your OS
>> line in the boot.ini, just to see if that makes any difference. (This
>> turns off DEP)
>>

> Task Manager on the 'real' PC. I can pretty much tell when this hangs
> occurs: The CPU utilization graph drops almost immediately to ~2%.
>
> Task Manager shows all the guest hosts and the VPC console as "not
> responding".
> Bob,
>
> I tried adding that to the boot.ini for my 'real' PC, and it hung again.
>
> Also, something I didn't mention: I've been monitoring performance with
> Task Manager on the 'real' PC. I can pretty much tell when this hangs
> occurs: The CPU utilization graph drops almost immediately to ~2%.
>
> Task Manager shows all the guest hosts and the VPC console as "not
> responding".
>
> Jim
>
>
> ohaya wrote:
>> Bob,
>>
>> A couple of questions:
>>
>> 1) Are you suggesting putting this in the boot.ini for the 'real' PC, or
>> in the boot.ini for the guest hosts, or for BOTH?
>>
>> 2) From what I've been able to find, this parameter is only for Windows
>> XP SP2 and Win2K3? Is it applicable to Win2K Server SP4 also?
>>
>> Jim
>>
>>
>>
>> Robert Comer wrote:
>>> Just to try something -- try adding the /NoExecute=AlwaysOff to your OS
>>> line in the boot.ini, just to see if that makes any difference. (This
>>> turns off DEP)
>>>

>
> > Also, something I didn't mention: I've been monitoring performance with
> > Task Manager on the 'real' PC. I can pretty much tell when this hangs
> > occurs: The CPU utilization graph drops almost immediately to ~2%.
> >
> > Task Manager shows all the guest hosts and the VPC console as "not
> > responding".
>
> Interesting. I haven't ever seen something like that and don't have a clue
> why it would do that.
>
> --
> Bob Comer <Microsoft MVP Windows - Virtual Machine>
>
> "ohaya" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Bob,
> >
> > I tried adding that to the boot.ini for my 'real' PC, and it hung again.
> >
> > Also, something I didn't mention: I've been monitoring performance with
> > Task Manager on the 'real' PC. I can pretty much tell when this hangs
> > occurs: The CPU utilization graph drops almost immediately to ~2%.
> >
> > Task Manager shows all the guest hosts and the VPC console as "not
> > responding".
> >
> > Jim
> >
> >
> > ohaya wrote:
> >> Bob,
> >>
> >> A couple of questions:
> >>
> >> 1) Are you suggesting putting this in the boot.ini for the 'real' PC, or
> >> in the boot.ini for the guest hosts, or for BOTH?
> >>
> >> 2) From what I've been able to find, this parameter is only for Windows
> >> XP SP2 and Win2K3? Is it applicable to Win2K Server SP4 also?
> >>
> >> Jim
> >>
> >>
> >>
> >> Robert Comer wrote:
> >>> Just to try something -- try adding the /NoExecute=AlwaysOff to your OS
> >>> line in the boot.ini, just to see if that makes any difference. (This
> >>> turns off DEP)
> >>>

> Hi,
>
> I was going through the posts on this thread, and noted that I had not
> mentioned that this machine has an AMD64-3000 CPU. Is it possible that
> that might be causing the problem?
>
> Jim
>
>
>
> Robert Comer wrote:
>>
>> > Also, something I didn't mention: I've been monitoring performance
>> > with
>> > Task Manager on the 'real' PC. I can pretty much tell when this hangs
>> > occurs: The CPU utilization graph drops almost immediately to ~2%.
>> >
>> > Task Manager shows all the guest hosts and the VPC console as "not
>> > responding".
>>
>> Interesting. I haven't ever seen something like that and don't have a
>> clue
>> why it would do that.
>>
>> --
>> Bob Comer <Microsoft MVP Windows - Virtual Machine>
>>
>> "ohaya" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Bob,
>> >
>> > I tried adding that to the boot.ini for my 'real' PC, and it hung
>> > again.
>> >
>> > Also, something I didn't mention: I've been monitoring performance
>> > with
>> > Task Manager on the 'real' PC. I can pretty much tell when this hangs
>> > occurs: The CPU utilization graph drops almost immediately to ~2%.
>> >
>> > Task Manager shows all the guest hosts and the VPC console as "not
>> > responding".
>> >
>> > Jim
>> >
>> >
>> > ohaya wrote:
>> >> Bob,
>> >>
>> >> A couple of questions:
>> >>
>> >> 1) Are you suggesting putting this in the boot.ini for the 'real' PC,
>> >> or
>> >> in the boot.ini for the guest hosts, or for BOTH?
>> >>
>> >> 2) From what I've been able to find, this parameter is only for
>> >> Windows
>> >> XP SP2 and Win2K3? Is it applicable to Win2K Server SP4 also?
>> >>
>> >> Jim
>> >>
>> >>
>> >>
>> >> Robert Comer wrote:
>> >>> Just to try something -- try adding the /NoExecute=AlwaysOff to your
>> >>> OS
>> >>> line in the boot.ini, just to see if that makes any difference. (This
>> >>> turns off DEP)
>> >>>

> I doubt it.
>
> It sounds like either a driver issue, or some other piece of software you
> have on your PC is interfering with VPC somehow. (any shell enhancement
> software running?)
>

> What I don't understand is that these are suppose to be "VIRTUAL" guest
> hosts, right? Why would a problem in one guest host (if there is one),
> cause ALL of the guest hosts to hang? Aren't they suppose to be isolated?
> It seems move like VPC *itself* is hanging, but what could something
> within a guest host be doing that would cause that???
> Bob,
>
> What do you mean by "shell enhancement software"?
>
> The way it hangs is really strange. I typically have 3 guests running
> when it happens. When I watch Task Manager, there's activity, then all of
> a sudden CPU utilization just drops. At that point, all 3 of the guests'
> windows are frozen (the VPC console also, if I had it displayed).
> Everything "outside" of VPC seems to still work, i.e., I can open up a
> browser on the host, etc.
>
> Then, if I try to close one of the guests' windows by clicking on the "X",
> all 3 windows die.
>
> What I don't understand is that these are suppose to be "VIRTUAL" guest
> hosts, right? Why would a problem in one guest host (if there is one),
> cause ALL of the guest hosts to hang? Aren't they suppose to be isolated?
>
> It seems move like VPC *itself* is hanging, but what could something
> within a guest host be doing that would cause that???
>
> Jim
>
>
>
> Robert Comer wrote:
>> I doubt it.
>>
>> It sounds like either a driver issue, or some other piece of software you
>> have on your PC is interfering with VPC somehow. (any shell enhancement
>> software running?)
>>

>> What do you mean by "shell enhancement software"?
>
> Something that changes the appearance/functionality of windows explorer.
>
>> What I don't understand is that these are suppose to be "VIRTUAL" guest
>> hosts, right? Why would a problem in one guest host (if there is one),
>> cause ALL of the guest hosts to hang? Aren't they suppose to be isolated?
>
> Virtual PC is pretty much a single threaded app, so it makes sense that when
> the main thread in Virtual PC dies, everything dies. Virtual Server
> wouldn't act the same.
>
> Something is blocking the main VPC thread on your PC, and that's why it does
> what it does, unfortunately I don't know what that might be. Is there any
> kind of message in the event viewer system and Application logs?
>
>> It seems move like VPC *itself* is hanging, but what could something
>> within a guest host be doing that would cause that???
>
> That's exactly what it sounds like to me too, but I kind of doubt its
> something in a guest that's doing it, it sounds like something else on the
> host.
>
> Is there some kind of power management software running (something to quite
> the fans or throttle back the CPU? (on the host)

> Bob,
>
> Comments below, interspersed....
>
> Thanks for 'hanging in there' with this one...
>
>
> Robert Comer wrote:
>>> What do you mean by "shell enhancement software"?
>>
>> Something that changes the appearance/functionality of windows explorer.
>
> Then, no, I don't have any shell enhancement software...
>
>
>
>>
>>> What I don't understand is that these are suppose to be "VIRTUAL"
>>> guest hosts, right? Why would a problem in one guest host (if there
>>> is one), cause ALL of the guest hosts to hang? Aren't they suppose
>>> to be isolated?
>>
>> Virtual PC is pretty much a single threaded app, so it makes sense
>> that when the main thread in Virtual PC dies, everything dies.
>> Virtual Server wouldn't act the same.
>>
>> Something is blocking the main VPC thread on your PC, and that's why
>> it does what it does, unfortunately I don't know what that might be.
>> Is there any kind of message in the event viewer system and
>> Application logs?
>
>
> I *am* seeing the following under Application Logn (these events seem to
> come in pairs, and the offset shown in the 2nd event is the same as in
> the popup when I get the "Unexpected" error):
>
> Event Type: Error
> Event Source: Microsoft Virtual PC 2004
> Event Category: None
> Event ID: 1001
> Date: 7/24/2006
> Time: 4:49:44 AM
> User: N/A
> Computer: TESTWIN2K
> Description:
> The description for Event ID ( 1001 ) in Source ( Microsoft Virtual PC
> 2004 ) cannot be found. The local computer may not have the necessary
> registry information or message DLL files to display messages from a
> remote computer. The following information is part of the event: 143763969.
> Data:
> 0000: 42 75 63 6b 65 74 3a 20 Bucket:
> 0008: 31 34 33 37 36 33 39 36 14376396
> 0010: 39 0d 0a 9..
>
> Event Type: Error
> Event Source: Microsoft Virtual PC 2004
> Event Category: None
> Event ID: 1000
> Date: 7/24/2006
> Time: 4:49:06 AM
> User: N/A
> Computer: TESTWIN2K
> Description:
> The description for Event ID ( 1000 ) in Source ( Microsoft Virtual PC
> 2004 ) cannot be found. The local computer may not have the necessary
> registry information or message DLL files to display messages from a
> remote computer. The following information is part of the event: virtual
> pc.exe, 5.3.582.27, virtual pc.exe, 5.3.582.27, 0005ba8b.
> Data:
> 0000: 41 70 70 6c 69 63 61 74 Applicat
> 0008: 69 6f 6e 20 46 61 69 6c ion Fail
> 0010: 75 72 65 20 20 76 69 72 ure vir
> 0018: 74 75 61 6c 20 70 63 2e tual pc.
> 0020: 65 78 65 20 35 2e 33 2e exe 5.3.
> 0028: 35 38 32 2e 32 37 20 69 582.27 i
> 0030: 6e 20 76 69 72 74 75 61 n virtua
> 0038: 6c 20 70 63 2e 65 78 65 l pc.exe
> 0040: 20 35 2e 33 2e 35 38 32 5.3.582
> 0048: 2e 32 37 20 61 74 20 6f .27 at o
> 0050: 66 66 73 65 74 20 30 30 ffset 00
> 0058: 30 35 62 61 38 62 0d 0a 05ba8b..
>
>
>
>
>
>
>>
>>> It seems move like VPC *itself* is hanging, but what could something
>>> within a guest host be doing that would cause that???
>>
>> That's exactly what it sounds like to me too, but I kind of doubt its
>> something in a guest that's doing it, it sounds like something else on
>> the host.
>>
>> Is there some kind of power management software running (something to
>> quite the fans or throttle back the CPU? (on the host)
>
> I have AMD Powernow in the "Services", but I set that to not start since
> yesterday, and the problems still have been occurring since then...
>
> Jim
>

>> 1) Are you suggesting putting this in the boot.ini for the 'real' PC, or
>> in the boot.ini for the guest hosts, or for BOTH?
>
> The "real" pc.
>
>> 2) From what I've been able to find, this parameter is only for Windows XP
>> SP2 and Win2K3? Is it applicable to Win2K Server SP4 also?
>
> You are correct, sorry, I had forgotten about the W2K. This wont make any
> difference.
>

> but it kind of looks like that might be the problem?
> Hi,
>
> I have some new info on this.
>
> Out of desparation, I moved the 3 guest hosts to a USB drive, and then
> attached the drive to another machine I had. This other machine has less
> memory (total 2GB) than the earlier machine, and has a Socket A mobo with
> an AMD XP2800+ CPU instead of an AMD64. OS is Win2K Server SP4, same on
> both machines.
>
> Guess what?
>
> Yep, all 3 guests start up and I haven't seen the hanging or unexpected
> exception so far!!
>
> I know that some of you said that the AMD64 CPU shouldn't be a problem,
> but it kind of looks like that might be the problem?
>
> Jim
>
>
> Robert Comer wrote:
>>> 1) Are you suggesting putting this in the boot.ini for the 'real' PC, or
>>> in the boot.ini for the guest hosts, or for BOTH?
>>
>> The "real" pc.
>>
>>> 2) From what I've been able to find, this parameter is only for Windows
>>> XP SP2 and Win2K3? Is it applicable to Win2K Server SP4 also?
>>
>> You are correct, sorry, I had forgotten about the W2K. This wont make
>> any difference.
>>

>> I know that some of you said that the AMD64 CPU shouldn't be a problem,
>> but it kind of looks like that might be the problem?
>
> It could also be something in the chipset or drivers for the AMD64
> motherboard PC, but it definitely is some kind of incompatibility.
>

> Bob,
>
> I have a support case open with MS through my company... Hopefully,
> they'll come up with something.
>
> Jim
>
>
>
> Robert Comer wrote:
> >> I know that some of you said that the AMD64 CPU shouldn't be a problem,
> >> but it kind of looks like that might be the problem?
> >
> > It could also be something in the chipset or drivers for the AMD64
> > motherboard PC, but it definitely is some kind of incompatibility.
> >

> Hi,
>
> For the record:
>
> I worked with support for a couple of days, and they had me run some
> things including something called "ADPLUS". I've sent them what they
> asked for, but no response yet.
>
> In the meantime, I decided to build a new Win2K3 machine, and got
> Virtual Server 2005 R2 on it. I then moved the VPC guests over, and
> ran them, and they all run fine, with no hanging or unexpected errors
> (so far).
>
> I don't know if it's my imagination, but the guests/VMs seem to run a
> lot faster, especially starting up Windows...
>
> Jim
>
>
>
>
> ohaya wrote:
>> Bob,
>>
>> I have a support case open with MS through my company... Hopefully,
>> they'll come up with something.
>>
>> Jim
>>
>>
>>
>> Robert Comer wrote:
>> >> I know that some of you said that the AMD64 CPU shouldn't be a
>> >> problem,
>> >> but it kind of looks like that might be the problem?
>> >
>> > It could also be something in the chipset or drivers for the AMD64
>> > motherboard PC, but it definitely is some kind of incompatibility.
>> >
>

> Interesting, is it still the same hardware?
>

> that I had with VPC?
> Bob,
>
> Sorry, I forgot to clearly explain that.
>
> The Win2K3-SP1/Virtual Server 2005 R2 installation is on the SAME physical
> machine:
>
> Motherboard: MSI K8NGM2-FID
> CPU: AMD64
> Memory: 3.xGB
>
> Also the memory allocated to the VMs is the same as it was under VPC.
>
> I setup a multi-boot configuration so I can still go back to the VPC
> configuration when I'm working on the support case with MS, because I'm
> still hoping that MS will figure out what the problem is so that I can go
> back to VPC.
>
> Also, I copied the VMC, VHD to create a physically different set of files
> for when I'm running under Virtual Server vs. VPC. I know that they're
> suppose to be compatible, but I didn't want to inadverdently have Virtual
> Server change the VHD (especially).
>
> BTW, I was able just do VM "Create" in Virtual Server for two of the three
> VMs, but the 3rd would not start under Virtual Server. I was able to get
> around that by deleting the copy of the .VMC file, and "Add"ing a new VM
> using the existing VHD that I had copied.
>
> I'm kind of curious: Did you expect me to have the same problem with VS
> that I had with VPC?
>
> I'm glad that it's working at least under VS, because between all of the
> hung VPC session and working with MS on this problem so far, I've lost a
> LOT of time :(!! At least now, I can keep on getting some "real" work
> done...
>
> Jim
>
>
>
> Robert Comer wrote:
>> Interesting, is it still the same hardware?
>>

>> I'm kind of curious: Did you expect me to have the same problem with VS
>> that I had with VPC?
>
> Not necessarily, but depending on the cause, you could have.
>

> Hi,
>
> Well, running VPC 2004 SP1 on WinXP Pro SP2 didn't work either... the
> guests still all hung. In fact, it seemed worse on WinXP Pro SP2, because
> not only did the guests and VPC hang, but it eventually hung the "real"
> host also. I had to power the machine down physically.
>
> Jim
>
>
>
> ohaya wrote:
>> Hi,
>>
>> To keep you all posted:
>>
>> - Running the same 3 guests under VPC running on Win2K3-32bit on my AMD64
>> system causes the guests to hang.
>>
>> - I'm told that WinXP Pro (32bit) SP2 is suppose to work. Waiting to
>> test it.
>>
>> Jim
>>
>>
>>
>> Robert Comer wrote:
>>>> I'm kind of curious: Did you expect me to have the same problem with VS
>>>> that I had with VPC?
>>>
>>> Not necessarily, but depending on the cause, you could have.
>>>

> Colin,
>
> Believe me, I wish that the answer appeared already :)...
>
> Yes, I think I mentioned that I did a memory test awhile ago, when I first
> encountered the problem.
>
> I'm getting an indication that support thinks the problem may be because
> of AMD64, I think...
>
> Jim
>
> P.S. I had VPC hang with just a single guest running last night!! So,
> it's not even the particular combination of guests...
>
>
>
> Colin Barnhorst wrote:
>> This is a long thread so I don't remember if this came up, but have you
>> run a memory test? This usage may be surfacing a ram defect.

> Hi,
>
> To keep you all posted:
>
> - Running the same 3 guests under VPC running on Win2K3-32bit on my
> AMD64 system causes the guests to hang.
>
> - I'm told that WinXP Pro (32bit) SP2 is suppose to work. Waiting to
> test it.
>
> Jim
>
>
>
> Robert Comer wrote:
>>> I'm kind of curious: Did you expect me to have the same problem with
>>> VS that I had with VPC?
>>
>> Not necessarily, but depending on the cause, you could have.
>>

> This is a long thread so I don't remember if this came up, but have you run
> a memory test? This usage may be surfacing a ram defect.

> I have not had an issue with VPC on an AMD64 running XP x86. Puzzling.
>
> "ohaya" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Colin,
>>
>> Believe me, I wish that the answer appeared already :)...
>>
>> Yes, I think I mentioned that I did a memory test awhile ago, when I first
>> encountered the problem.
>>
>> I'm getting an indication that support thinks the problem may be because
>> of AMD64, I think...
>>
>> Jim
>>
>> P.S. I had VPC hang with just a single guest running last night!! So,
>> it's not even the particular combination of guests...
>>
>>
>>
>> Colin Barnhorst wrote:
>>> This is a long thread so I don't remember if this came up, but have you
>>> run a memory test? This usage may be surfacing a ram defect.
>
>

> Hi,
>
> For the record:
>
> While I was working on this problem, I referred the support engineer to
> this thread and to the thread that Gorgo start entitled "Virtual PC 2004
> Problem". In particular, I whether, even though they didn't seem to
> apply, he could send me the two hotfixes mentioned in the latter thread.
>
> He did that yesterday, and I got links for:
>
> 223208_intl_i386_zip.exe
> 240660_intl_i386_zip.exe
>
> along with passwords for unpacking each of those.
>
> For some reason, only the password for 240660_intl_i386_zip.exe worked, so
> I unpacked that, and installed:
>
> vpc2004qfe899525_msdn.msp then
> vpc2004qfe899525_update.msp
>
> which corresponds to http://support.microsoft.com/?kbid=899525
>
> After applying that hotfix, VPC shows "Virtual PC 5.3.582.34".
>
> Because of the password problem, I have not been able to apply the
> 223208_intl_i386_zip.exe hotfix.
>
> Anyway, since applying the above single patch, I've been testing on two
> different configurations, and so far, it *LOOKS LIKE* this hotfix has
> eliminated the HANG PROBLEM!!
>
> This may be just wishful thinking on my part, or may be premature, but I
> hope not, but so far, with several hours of testing with the same 3
> guests, I have not had the hang problem occur (fingers crossed!).
>
> Here's my hardware configuration again, for the record:
>
> Motherboard: MSI K8NGM2-FID
> CPU: AMD64-3000 (Venice core, rev. E)
> RAM: ~3.5GB (3x1GB + 1x512MB)
> "Host" OS'es that I've applied the hotfix to: Win2K Server SP4 and WinXP
> Pro SP2 (32 bit)
> Guests' OS: Win2K Server SP4
>
> I'll post back later, reporting how things are going, but the bottom line
> is that if anyone runs across a similar hang problem, especially with an
> AMD64 CPU, you might want to try the above hotfix.
>
> At this point, if things continue to work, I don't think I'll try to apply
> the other hotfix ("don't fix what is not broken"!).
>
> Thanks for everyone's help!
>
> Jim
>
>
>
> Colin Barnhorst wrote:
>> I have not had an issue with VPC on an AMD64 running XP x86. Puzzling.
>>
>> "ohaya" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>>> Colin,
>>>
>>> Believe me, I wish that the answer appeared already :)...
>>>
>>> Yes, I think I mentioned that I did a memory test awhile ago, when I
>>> first encountered the problem.
>>>
>>> I'm getting an indication that support thinks the problem may be because
>>> of AMD64, I think...
>>>
>>> Jim
>>>
>>> P.S. I had VPC hang with just a single guest running last night!! So,
>>> it's not even the particular combination of guests...
>>>
>>>
>>>
>>> Colin Barnhorst wrote:
>>>> This is a long thread so I don't remember if this came up, but have you
>>>> run a memory test? This usage may be surfacing a ram defect.
>>

> Thanks for the update!
>

> Bob (et al),
>
> BTW, since installing the hotfix, I've noticed that occasionally, I'm
> seeing some problems with what I can only describe as "video bleed-thru"
> among the guests' windows. What I mean by this is that if I click on a
> guest window that is partially under another guest's window, the guest I
> clicked on will come forward, but sometimes, parts of the window that we
> overlapped take a bit before they appear.
>
> I've been experimenting with disabling DirectDraw on the 'real' host,
> using dxdiag, and so far, that seems to mostly eliminate this video
> bleed-thru problem. I'll post back after I've had more of chance to
> work with this.
>
> Thanks,
> Jim
>
>
> Robert Comer wrote:
>> Thanks for the update!
>>

> it, but screen/window refreshes seem just a "bit slower", but that
> "bleed-thru" problem doesn't seem to occur anymore.
> I've been dealing with that "hang" problem for so long, I had forgotten
> how nice it was when VPC "just worked" :)!!
> I guess that the upside of all of that was that I was forced to give VS a
> try, which I'd been wanting to do for awhile.
> Hi,
>
> So far, so good, so good with DirectDraw disabled... Maybe I'm imagining
> it, but screen/window refreshes seem just a "bit slower", but that
> "bleed-thru" problem doesn't seem to occur anymore.
>
> I've been dealing with that "hang" problem for so long, I had forgotten
> how nice it was when VPC "just worked" :)!!
>
> I guess that the upside of all of that was that I was forced to give VS a
> try, which I'd been wanting to do for awhile.
>
> Jim
>
>
>
>
> ohaya wrote:
>> Bob (et al),
>>
>> BTW, since installing the hotfix, I've noticed that occasionally, I'm
>> seeing some problems with what I can only describe as "video bleed-thru"
>> among the guests' windows. What I mean by this is that if I click on a
>> guest window that is partially under another guest's window, the guest I
>> clicked on will come forward, but sometimes, parts of the window that we
>> overlapped take a bit before they appear.
>>
>> I've been experimenting with disabling DirectDraw on the 'real' host,
>> using dxdiag, and so far, that seems to mostly eliminate this video
>> bleed-thru problem. I'll post back after I've had more of chance to work
>> with this.
>>
>> Thanks,
>> Jim
>>
>>
>> Robert Comer wrote:
>>> Thanks for the update!
>>>

>> So far, so good, so good with DirectDraw disabled... Maybe I'm imagining
>> it, but screen/window refreshes seem just a "bit slower", but that
>> "bleed-thru" problem doesn't seem to occur anymore.
>
> Interesting. I've heard of screen redraw problems on some chipsets, I think
> KB889677 had some fixes for that.

> Bob,
>
> So, do you think that I should also apply 889677?
>
> I noticed that 889677 was issued earlier than 899525.
>
> Since I've already applied 899525, if I want to apply 889677, should I
> FIRST apply 889677, then RE-APPLY 899525?
>
> Or are the hotfixes cumulative, i.e., does 899525 already contain the
> changes that were included in 889677?
>
> Jim
>
>
>
> Robert Comer wrote:
>>> So far, so good, so good with DirectDraw disabled... Maybe I'm imagining
>>> it, but screen/window refreshes seem just a "bit slower", but that
>>> "bleed-thru" problem doesn't seem to occur anymore.
>>
>> Interesting. I've heard of screen redraw problems on some chipsets, I
>> think KB889677 had some fixes for that.

> Hotfixes aren't cumulative. It's probably be safest to apply 889677 and
> then reapply 899525. I really am not sure if it'll fix your problem, but I
> think it's worth a try. You can always uninstall VPC again and apply 899525
> to get back to where you are now.
>