I'm trying to use clearmem in XP Sp2 to free up memory for a rendering
program but get this output:

* FAILure --> Line=400 File=d:\nt\sdktools\clearmem\clearmem.c (pid=0xC04
tid=0

xF6C)

* RC=0x8 (Not enough memory)

* AccessSection() - VirtualAlloc

**************************

**************************

* FAILure --> Line=332 File=d:\nt\sdktools\clearmem\clearmem.c (pid=0xC04
tid=0

xF6C)

* RC=0x8 (Not enough memory)

* FlushCache() - AccessSection

**************************

**************************

* FAILure --> Line=168 File=d:\nt\sdktools\clearmem\clearmem.c (pid=0xC04
tid=0

xF6C)

* RC=0x8 (Not enough memory)

* main() - FlushCache

The machine in question has 2 gigs of ram so I am wondering if changes in
sp2 have broken clearmem although I haven't been able to find any info or
updates on this.

Thanks for any help

That program was released with the NT 4.0 Resource Kit - no documentation I
can find says it is certified for use with Win2k or XP - so you have been
basically taking your chances and your chances are all used up.

P.S. It was also a diagnostic tool, if was not designed for the scenario in
which it is being used.

--
Star Fleet Admiral Q @ your service!
"Google is your Friend!"
www.google.com

***********************************************

"Lee Hurd" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm trying to use clearmem in XP Sp2 to free up memory for a rendering
> program but get this output:
>
> * FAILure --> Line=400 File=d:\nt\sdktools\clearmem\clearmem.c (pid=0xC04
> tid=0
>
> xF6C)
>
> * RC=0x8 (Not enough memory)
>
> * AccessSection() - VirtualAlloc
>
> **************************
>
> **************************
>
> * FAILure --> Line=332 File=d:\nt\sdktools\clearmem\clearmem.c (pid=0xC04
> tid=0
>
> xF6C)
>
> * RC=0x8 (Not enough memory)
>
> * FlushCache() - AccessSection
>
> **************************
>
> **************************
>
> * FAILure --> Line=168 File=d:\nt\sdktools\clearmem\clearmem.c (pid=0xC04
> tid=0
>
> xF6C)
>
> * RC=0x8 (Not enough memory)
>
> * main() - FlushCache
>
> The machine in question has 2 gigs of ram so I am wondering if changes in
> sp2 have broken clearmem although I haven't been able to find any info or
> updates on this.
>
> Thanks for any help
>
>

It came with the XP Professional resource kit, and the documentation states
it runs on all platforms so you are misinformed on that account. As for
clearing memory not being what it was designed for I have no idea what
you're talking about there.

"Admiral Q" <Star_Fleet_Admiral_Q(NOSPAM)@(SPAMNOT)hotmail.com> wrote in
message news:(E-Mail Removed)...
> That program was released with the NT 4.0 Resource Kit - no documentation
> I
> can find says it is certified for use with Win2k or XP - so you have been
> basically taking your chances and your chances are all used up.
>
> P.S. It was also a diagnostic tool, if was not designed for the scenario
> in
> which it is being used.
>
> --
> Star Fleet Admiral Q @ your service!
> "Google is your Friend!"
> www.google.com
>
> ***********************************************
>
> "Lee Hurd" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I'm trying to use clearmem in XP Sp2 to free up memory for a rendering
>> program but get this output:
>>
>> * FAILure --> Line=400 File=d:\nt\sdktools\clearmem\clearmem.c (pid=0xC04
>> tid=0
>>
>> xF6C)
>>
>> * RC=0x8 (Not enough memory)
>>
>> * AccessSection() - VirtualAlloc
>>
>> **************************
>>
>> **************************
>>
>> * FAILure --> Line=332 File=d:\nt\sdktools\clearmem\clearmem.c (pid=0xC04
>> tid=0
>>
>> xF6C)
>>
>> * RC=0x8 (Not enough memory)
>>
>> * FlushCache() - AccessSection
>>
>> **************************
>>
>> **************************
>>
>> * FAILure --> Line=168 File=d:\nt\sdktools\clearmem\clearmem.c (pid=0xC04
>> tid=0
>>
>> xF6C)
>>
>> * RC=0x8 (Not enough memory)
>>
>> * main() - FlushCache
>>
>> The machine in question has 2 gigs of ram so I am wondering if changes in
>> sp2 have broken clearmem although I haven't been able to find any info or
>> updates on this.
>>
>> Thanks for any help
>>
>>
>
>