Task Manager (I did). But massive HD activity does not necessarily
translate into CPU activity, so often it's not obvious who's the
culprit in there. But at least it's good to kill the task that causes
the activity :-)
But it's probably getting a bit too Windows specific for this list now...
OK, I'll just mention that the process is EXPLORER.EXE.
However, it's applicable for me because it prevents me runing QPC!
The anti-virus has kicked in for a routine scan now, so I'll leave it for
tonight.
--
Dilwyn Jones
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
