Re: WinXP not detecting all memory



A friend of mine just bought an XP system which was advertised as
having 256M DDR. I happened to drop by his offfice when he had just
set up the system. Not being too familiar with XP, I poked around, and
in System Properties, I saw that he had only 192M.
Then I happened across this well-hidden gem on the Microsoft site.
"Memory size information does not appear correctly in System
Properties in Microsoft Windows XP Service Pack 2"
http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;888664
The blurb says that the FINNISH version of XP SP2 has a problem in
which System Properties reports incorrect (probably lower than actual)
physical memory. The "workaround" is "Click Start, point to All
Programs, point to Accessories, point to System Tools, and then click
System Information". In other words, don't use System Properties when
looking for reliable information. There is no possibility of a fix
mentioned.
I don't think that this bug exists in just the FINNISH version. I will
have to run down to my friend's office on Monday to see if I get the
correct report from Sysinfo.
I think MS is hiding an error by suggesting it's a FINNISH problem,
but I'll bet it's universal.

Since I don't have XP, can some of you guys who run XP compare what is
reported by System Properties and what is reported by System
Information, and report on it here?

Joe from Massachusetts



"Joe Cougar" <elcapitan25@xxxxxxxxx> wrote in message
news:25162-4367E59D-1301@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >
> > Yeah wrote:
>
> >Just finished building a friend's computer with
> > Windows XP Home SP2 installed.
> ---------------------------------
> Installing our fine Service Pak 2 might help.
> --
> - Frank DeLucca -
> MS-MPV
> Microsoft Corparation
> -----------------------------------
> He says he has it already.
> I'm a near total newbie here but if it was me I'd read the docs
for
> the motherboard. Wouldn't you need to know if t was an "interleaved"
> memory?
> Also wouldn't it be enough that the CPU recognizes the Ram?
> Sorry if this is no help.I'm trying to learn this stuff and
thought
> I'd ask some dumb questions.
> I better go now....
>


.



Relevant Pages

  • Re: Alocated Memory Error (SQLSERVR)
    ... I had the same problem except, my memory hog was SBSMONITORING. ... critical and you don't want it grabbing all that RAM. ... Server 2000 SP4, ... However my daily status report is sent out ...
    (microsoft.public.windows.server.sbs)
  • RE: Crytical alert in server performance report
    ... Which performace report are you running? ... How much physical memory are you running? ... Windows Small Business Server Team ... | You can disable this alert or change the threshold using the task Change ...
    (microsoft.public.windows.server.sbs)
  • Re: Report Layout
    ... it does not work for my report.. ... And now it displays fine and I don't run out of memory. ... Why don't you have a peek at the picturebox properties. ... quality is critical for this form.. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: 2.6.19: ACPI reports AC not present after resume from STD
    ... When reporting AC state ACPI just reads contents of system memory ... I updated mentioned bug report with more detailed ... Will the kernel allocate partial page or will the kernel ignore ... Mark e820 reserved memory areas as nosave for suspend/resume ...
    (Linux-Kernel)
  • RE: Re-installation of SBS Monitoring causing store.exe report to
    ... I have already re-installed the monitoring tools. ... I am getting the store.exe memory report in the morning ... after you install Microsoft Exchange Server 2003 ...
    (microsoft.public.windows.server.sbs)