Yes that's it - it is nothing to do with CPU usage - neither is using very much...they are fighting for control.
The network test is CAUSING the "problem"...watch what happens to the context switch count of slim.exe if you stop the test!. Basically - by having that page open AND running the test at the same time you are asking the computer to do a lot of work (actually a lot of thrashign around and very little work!)...I think this is because of the way that the network test is written. Now the impact of this may not be noticeable on some machines - it will depend on their CPU speed, chipset design, ram type etc. My machine is fine, yours has a slight problem. I'll do some more digging. In the meantime, I suggest you look at process explorer again and focus on the context switching counts and the CS Delta (look in the help file). Maybe a developer could comment on why the network test casues this behaviour? Hang on in there Neil! -- Phil Leigh You want to see the signal path BEFORE it gets onto a CD/vinyl...it ain't what you'd call minimal... ...SB3+TACT+Altmann+MF DACXV3/Linn tri-amped Aktiv 5.1 system and some very expensive cables ;o) ------------------------------------------------------------------------ Phil Leigh's Profile: http://forums.slimdevices.com/member.php?userid=85 View this thread: http://forums.slimdevices.com/showthread.php?t=38571 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
