Evening, > Check out ProcMon, it will perhaps tell you what caused the activity: > http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
Exactly what I was going to suggest. I use it at work (and I'm not supposed to!) and it has helped me solve many an insidious problem with Windows. Cheers, Norman. _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
