Sent: 12/10/2008
From: Grand_Poobah <(email address - cut out)>
Message:I don't really see anything wrong or missing except that the Event Log
seems a bit sparse as to what actually happened. That report it gave
you is generic for "I don't know what really happened" in Microsoftspeak.
The amounts of RAM looks OK, but I notice that you only have 2Gb of RAM
total. Try temporarily cutting down on your guest RAM to perhaps 750Mb
and see if the error still happens. It could very well be that you have
so much going on in your host that pulling 1G of RAM away to run VPC
might just trigger the error.
I am not familiar with Windows Server 2003 so I don't know what it's
minimum/preferred RAM settings are but the temporary reduction shouldn't
hurt just to see if it will run reliably.
GP
--->
Show quoted text
> VPC operating system: windows server 2003
> PC operating system: Windows XP
>
> Event log:
>
> Event Type: Error
> Event Source: Microsoft Virtual PC 2007
> Event Category: None
> Event ID: 1000
> Date: 10.12.2008
> Time: 22:27:50
> User: N/A
> Computer: LKRISTIA
> Description:
> The description for Event ID ( 1000 ) in Source ( Microsoft Virtual PC 2007
> ) cannot be found. The local computer may not have the necessary
> registry information or message DLL files to display messages from a remote
> computer. You may be able to use the /AUXSOURCE= flag to retrieve
> this description; see Help and Support for details.
> The following information is part of the event: virtual pc.exe; 6.0.192.0;
> unknown; 0.0.0.0; f5464cc6.
>
> I've sent error message to Microsoft, but never received an answer
>
> RAM 2 GB
>
> RAM allocated to the VM: 1046 MB
>
> Thanks
>
> "Grand_Poobah" wrote:
>
>> In no particular order:
>>
>> What is your host operating system?
>> What is your guest operating system?
>> Does your Event Log have any related errors in it?
>> Do you send the error message to Microsoft?
>> If you do, does Microsoft give you a link to a possible solution?
>> How much RAM does your system have?
>> How much have you allocated to the VM?
>>
>> We need a little bit more information to make any sort of informed guess
>> as to your problem.
>>
>> GP
>>
>> --->
>>> When I try to start Virtual PC i sometimes get errormessage: Microsoft
>>> Virtual PC 2007 has encountered a problem and needs to close.
>>> The only way I can then start the Virtual PC is by rebooting my computer.
>>> Any ideas how to fix this?
Sent: 12/10/2008
From: Grand_Poobah <(email address - cut out)>
Message:--->
Wow. You're right. Not much at all.
GP
Show quoted text
> "Grand_Poobah" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>
>> I am not familiar with Windows Server 2003 so I don't know what it's
>> minimum/preferred RAM settings are
>
> Probably a lot less than you'd imagine:
> http://technet.microsoft.com/en-us/windowsserver/bb430827.aspx
>
>
Sent: 12/10/2008
From: "Mark Rae [MVP]" <(email address - cut out)>
Message:"Grand_Poobah" <(email address - cut out)> wrote in message
news:(email address - cut out)...
Probably a lot less than you'd imagine:
http://technet.microsoft.com/en-us/windowsserver/bb430827.aspx
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
Show quoted text
> I am not familiar with Windows Server 2003 so I don't know what it's
> minimum/preferred RAM settings are
Sent: 12/11/2008
From: Bo Berglund <(email address - cut out)>
Message:On Wed, 10 Dec 2008 16:51:16 -0600, Grand_Poobah
<(email address - cut out)> wrote:
I run a virtual Win2003 Enterprise server 24/7 with 256 Mb RAM. It
works quite happily with that.
--
Bo Berglund (Sweden)
Show quoted text
>
>I am not familiar with Windows Server 2003 so I don't know what it's
>minimum/preferred RAM settings are but the temporary reduction shouldn't
>hurt just to see if it will run reliably.
>
Wiki