<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I'd suggest checking task manager to see <br>
a) what processes are using most CPU time, and<br>
b) how much memory each process is using.<br>
<br>
I've sometimes found a process using a large amount of memory can be
the cause of such things. If that gives you any reasonable indication,
then there's a place to start investigations.<br>
<br>
Not sure what to suggest if that doesn't prove useful.<br>
<br>
Cheers,<br>
Adam.<br>
<br>
joseph harris wrote:
<blockquote cite="mid:00ea01c85e87$805466b0$d1bd28d5@looperman9"
type="cite">
<pre wrap="">From: "David Precious"
</pre>
<blockquote type="cite">
<pre wrap="">Adam Cork wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I used to be on this (and the main WDVL list) but set my
status to idle
on both, as I wasn't getting time to run through the mail I
received
each day (mainly on the main list). But since the server
changeover on
the social list, I appear to have been set to receive messages
again.
I thought I should make my presence known, don't know if any
of you
remember me - I never posted much before.
</pre>
</blockquote>
<pre wrap="">I remember you Adam - welcome back :)
</pre>
<blockquote type="cite">
<pre wrap="">Anyway, Joseph, the system idle process is designed to account
for all
unused CPU time, so will often show 99% usage. Basically
whatever isn't
used up by other processes.
</pre>
</blockquote>
<pre wrap="">Exactly right - the "idle process" isn't really a process at
all, it's
just showing what CPU usage isn't being used by other
processes.
--
David Precious
<a class="moz-txt-link-abbreviated" href="mailto:davidp@preshweb.co.uk">davidp@preshweb.co.uk</a> :: <a class="moz-txt-link-freetext" href="http://blog.preshweb.co.uk/">http://blog.preshweb.co.uk/</a>
</pre>
</blockquote>
<pre wrap=""><!---->
Thank you both and Hi! Adam. In that case is there a useful way
of finding out why the machine is so 'sticky' at present.
Occasionally it works at a reasonable speed, but mostly it comes
as near as may be to a cracsh without the actual blood on the
road. [Sorry Matt, don't let me put you off ;-)].
I imagine it is cloggy registry syndrome, but maybe I should
start somewhere else?
TIA
Joseph Harris
_______________________________________________
wdvltalk-social mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wdvltalk-social@wdvltalk-social.org.uk">wdvltalk-social@wdvltalk-social.org.uk</a>
<a class="moz-txt-link-freetext" href="http://lists.preshweb.co.uk/mailman/listinfo/wdvltalk-social">http://lists.preshweb.co.uk/mailman/listinfo/wdvltalk-social</a>
(This is via the new sever, lyla)
</pre>
</blockquote>
</body>
</html>