Resouce meter

[David]

Been following the resource meter thread. If RM existed
in XP it would be very useful to me. I posted the
following on the 13th but have had no response. Anyone
got any ideas? It seems amazing to me that I can always
run out of resources so quickly until the disk entries
are purged by chkdsk.

------ posted on the 13th -------------------------------
Every time I shut down windows, the following entries are
left on the disk. If I do not schedule a chkdsk prior to
start-up in order to clean-up before the session (as
below), I very quickly run out of resources for
everything but the most basic of tasks. Any ideas what
these entries might be, the files they represent and how
I might prevent them?

My system is an Athlon 2800 with 1Gb Ram and 120Gb hard
disk running on XP Home.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++
A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 3 unused index entries from index $SII of
file 0x9.
Cleaning up 3 unused index entries from index $SDH of
file 0x9.
Cleaning up 3 unused security descriptors.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

[bronco771]

Rt click the taskber to bring up Task Manager. This will
show your RM. Perform CHKDSK then Disk Cleanup then
Defrag the volume. Remove all progs for which you could
use the original CD i.e.,Britannica 2003 rather than have
them on your drive eating up a lot of resources.
Download Dustbuster, Spybot and RegCleaner. These are
very effective at removing temp files, cookies,viruses
and useless entries from the HD. Use these every day if
necessary.
Listen to your machine. Does it surge? You may be way
overdue for a defrag. If you are running Norton you might
consider switching to McAfee. My Athlon 2.8 runs better
with McAfee.
Go to MSCONFIG and remove all startup applications except
for the Anti-virus prog. Set a system Restore before you
do this. Email me if you need more help.
Good Luck

 

[Alex Nichol]

Been following the resource meter thread. If RM existed
in XP it would be very useful to me. I posted the
following on the 13th but have had no response. Anyone
got any ideas? It seems amazing to me that I can always
run out of resources so quickly until the disk entries
are purged by chkdsk.

The 'resource meter' in Win98/ME referred to a very specific use of he
word 'resource', for memory space used for two 16 bit system data
'heaps'. These structures just do not exist in XP, and there is
therefore no meter. 'Resources' is used in a more general and natural
way. Most common is in relation to memory use, but here you seem
concerned with disk usage. And with some problems on disk causing a bad
shutdown and hence chkdsk run. But from the information one can't go
further than that

 

[cbcb52]

When using RM in windows 98 , it was a very usefull app ,
showing in colors , when my system was near to crash point.
( red )
Although windows XP seems to manage very efficiently the
system resources , I believe ( I might be wrong ) that you
still can crash the system by using to many apps at the
same time .
There are a lot of graphs in task manager
( processes and performance ) -
I am not a computer expert , and those graphs
in performance , don't help me much .
Whitch parameters on the performance tab should
be watched / monitored in order to avoid a system crash ??

 

[David]

Thanks for your time Alex. Here's the gist of my problem
as described in a response to Ron Martell. My original
post, which includes the output from Chkdsk, is
referenced in the reply. If you have any further ideas I
would be grateful

David

--------------------------------------------------------
Yes Ron, under '95/98 etc. it would be a problem opening
too many windows due to the 64k heap constraints. I just
never expected a similar situation under XP. The scenario
is the same - I boot, I load IE, I load Outlook Express,
I load something else and - bang - errors reporting not
enough system resources to do it or the window pops up
with no detail in it (just like windows under 98 when you
get below about 12% of available resources). This is
crazy. What resources am I short of? I have 1Gb RAM and
the CPU utilisation indicates 2%. The only way to get
back to normality is to schedule a Chkdsk then re-boot
every time. It appears to be something to do with old
security descriptors and indexes left on the disk at
shutdown but I cannot understand how that could possibly
be the cause - it's relly bugging me now.

Thanks for your input all the same.

David

 

[Alex Nichol]

Thanks for your time Alex. Here's the gist of my problem
as described in a response to Ron Martell. My original
post, which includes the output from Chkdsk, is
referenced in the reply. If you have any further ideas I
would be grateful

One that might be worth checking is in a run of MSConfig.exe - Boot.ini
p[age, take advanced and see if there is a Memory limit been set.

Another is to see if he page file has been turned off. That is a bad
thing, even with gigabytes of RAM (for some discussion see
www.aumha.org/win5/a/xpvm.htm). Just having none at all on C: with a lot
apparently on a different drive can cause troubles. Another reason is
that there are *some* programs that want (undesirably) to use page file
for themselves and will crash things if there is none provided.

 

[David]

Alex, thanks for your response.

1. there is no memory limit set under the boot section
2. this is a more interesting proposition. I have no page
file on my system drive; I have it on a 2Gb logical drive
of the extended partition of the system disk. I've never
heard of this config causing problems before. Do you have
any further info regarding this setup?

Thanks in advance,
David

-----Original Message-----

Thanks for your time Alex. Here's the gist of my problem
as described in a response to Ron Martell. My original
post, which includes the output from Chkdsk, is
referenced in the reply. If you have any further ideas I
would be grateful

One that might be worth checking is in a run of MSConfig.exe - Boot.ini
p[age, take advanced and see if there is a Memory limit been set.

Another is to see if he page file has been turned off. That is a bad
thing, even with gigabytes of RAM (for some discussion see
www.aumha.org/win5/a/xpvm.htm). Just having none at all on C: with a lot
apparently on a different drive can cause troubles. Another reason is
that there are *some* programs that want (undesirably) to use page file
for themselves and will crash things if there is none provided.

 

[Alex Nichol]

2. this is a more interesting proposition. I have no page
file on my system drive; I have it on a 2Gb logical drive
of the extended partition of the system disk. I've never
heard of this config causing problems before. Do you have
any further info regarding this setup?

There has been extensive experience of trouble if you fail to leave the
possibility of a minimal page file on the C: drive. It is wanted in
some error conditions, if nowhere else, and if you do not set it (I
suggest initial 2, max 50) the system is likely either to eliminate
paging altogether or else set up an enormous file on C. So try that.
See more at my page www.aumha.org/win5/a/xpvm.htm

 

[David]

Thanks again Alex. I've tried re-instating a minimal page
file on the C: drive but the problem persists. I think
I'm going to have to concede defeat on this one and
continue to schedule Chkdsk prior to booting...

Cheers

David