PHWinfo - Afficher un message

10/04/2008, 20h49

Hello,
Yes the numbers can vary.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
>Thread-Topic: PNPMem Warning
>thread-index: AciZ6H41Ki7LDSZPS3ez2xCBEF/I5g==
>X-WBNR-Posting-Host: 207.46.193.207
>From: =?Utf-8?B?Q2FudWNrIGdlb2Zm?= <Canuckgeoff@discussions.microsoft.com>
>References: <90A67409-B65C-4900-9CBB-B39371C8CC0A@microsoft.com>
<OTATEbWbIHA.4180@TK2MSFTNGP06.phx.gbl>
>Subject: Re: PNPMem Warning
>Date: Tue, 8 Apr 2008 19:22:00 -0700
>Lines: 36
>Message-ID: <B1C5E334-8831-4A27-ADB2-76701D562402@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
>Newsgroups: microsoft.public.windows.server.setup
>Path: TK2MSFTNGHUB02.phx.gbl
>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.setup:4004
>NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
>X-Tomcat-NG: microsoft.public.windows.server.setup
>
>Thanks but i'm not using the /3GB switch
>
>"John John" wrote:
>
>> Read here: http://support.microsoft.com/kb/822842
>>
>> John
>>
>> Canuck geoff wrote:
>>
>> > I have a number of W2K3 SP1 servers showing the following warning on
boot. I
>> > found this article
>> >
>> > http://support.microsoft.com/kb/922095
>> >
>> > which seems to be a match, and says i can safely ignore it but can
anyone
>> > tell me if the memory values can vary?
>> >
>> > tia
>> >
>> >
>> > Event Type: Warning
>> > Event Source: PNPMEM
>> > Event Category: None
>> > Event ID: 0
>> > Date: 2/10/2008
>> > Time: 1:03:39 AM
>> > User: N/A
>> > Computer: CAxxxxxxxxxx
>> > Description:
>> > Failed to add memory range starting at 0x100000000 for 0x30000000
bytes.
>> > This operation exceeded the maximum memory capacity of the operating
system
>> > or the server is not configured to support dynamic memory operations
>> >
>> >
>>
>

10/04/2008, 20h49	#2
Darrell Gorter[MSFT] Messages: n/a Hébergeur:	Re: PNPMem Warning Hello, Yes the numbers can vary. Thanks, Darrell Gorter[MSFT] This posting is provided "AS IS" with no warranties, and confers no rights -------------------- >Thread-Topic: PNPMem Warning >thread-index: AciZ6H41Ki7LDSZPS3ez2xCBEF/I5g== >X-WBNR-Posting-Host: 207.46.193.207 >From: =?Utf-8?B?Q2FudWNrIGdlb2Zm?= <Canuckgeoff@discussions.microsoft.com> >References: <90A67409-B65C-4900-9CBB-B39371C8CC0A@microsoft.com> <OTATEbWbIHA.4180@TK2MSFTNGP06.phx.gbl> >Subject: Re: PNPMem Warning >Date: Tue, 8 Apr 2008 19:22:00 -0700 >Lines: 36 >Message-ID: <B1C5E334-8831-4A27-ADB2-76701D562402@microsoft.com> >MIME-Version: 1.0 >Content-Type: text/plain; > charset="Utf-8" >Content-Transfer-Encoding: 7bit >X-Newsreader: Microsoft CDO for Windows 2000 >Content-Class: urn:content-classes:message >Importance: normal >Priority: normal >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992 >Newsgroups: microsoft.public.windows.server.setup >Path: TK2MSFTNGHUB02.phx.gbl >Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.setup:4004 >NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149 >X-Tomcat-NG: microsoft.public.windows.server.setup > >Thanks but i'm not using the /3GB switch > >"John John" wrote: > >> Read here: http://support.microsoft.com/kb/822842 >> >> John >> >> Canuck geoff wrote: >> >> > I have a number of W2K3 SP1 servers showing the following warning on boot. I >> > found this article >> > >> > http://support.microsoft.com/kb/922095 >> > >> > which seems to be a match, and says i can safely ignore it but can anyone >> > tell me if the memory values can vary? >> > >> > tia >> > >> > >> > Event Type: Warning >> > Event Source: PNPMEM >> > Event Category: None >> > Event ID: 0 >> > Date: 2/10/2008 >> > Time: 1:03:39 AM >> > User: N/A >> > Computer: CAxxxxxxxxxx >> > Description: >> > Failed to add memory range starting at 0x100000000 for 0x30000000 bytes. >> > This operation exceeded the maximum memory capacity of the operating system >> > or the server is not configured to support dynamic memory operations >> > >> > >> >