View Single Post
  #4  
Old August 20th 05, 05:23 PM
David
external usenet poster
 
Posts: n/a
Default

For the record, /maxmem=2000 did nothing to solve the issue.

David

"Maurice N ~ MVP" wrote:

Check the amount of FREE space on your hard drive(s). You really need plenty of free space on your HD.

Check on the size of your Hiberfil.sys file (normally on root of C drive --- C:\ )

Check the Windows Explorer "View" options --- set it to show you all folders; all system folders; & hidden files.
Bring up Windows Explorer / Tools / Folder Options/ select VIEW Tab and look at all of settings listed.

"CHECK" (turn on) Display the contents of system folders.

Under column, Hidden files and folders----choose ( *select* ) Show hidden files and folders.
Next, un-check Hide extensions for known file types.
Next un-check Hide protected operating system files.

Now then, in Windows Explorer, go to My Computer. See how much free space is on your HD.

Run Disk Cleanup to free up space.
Search for all .tmp files & remove them. Find your \Temp folders & clean them out.

I'm going to offer for your consideration, the following quote by Alex Nichol, MS-MVP, on a similar situation as yours.

quote
As an experiment, I suggest using a run of MSConfig.exe and in that
Boot.ini page, click the Advanced button, and try selecting and setting
/MAXMEM down to say 2000 from the 2048 (going to 2GB was probably great
overkill anyway, and you will not miss 48MB)


--
Alex Nichol MS MVP (Windows Technologies)
Bournemouth, U.K.

endquote

--
Maurice N
MVP Windows - Shell / User
-----


David wrote:
I have a Dell Inspiron 9300 with 2GB of ram, and about 1 time in 3,
when I try to hibernate, I get the following error: "Insufficient
System Resources Exist to Complete the API".

The computer has SP2 pre-installed. I know this is related to the
memory in the computer (over 1GB has problems with hibernate), but, I
really, really, really like to hibernate the computer vs. stand-by,
and would really like to know if there's a fix for this issue. All KB
articles talk about the problem in SP1, and the fix included in SP2,
but, that's obviously not the case. Anything new on the solving this
issue front?

David


Ads