1. The IDE hard drives have slipped from DMA to lower DMA modes to PIO.
Since Windows XP was unreliable in reporting what it is at, the fix is to set all channels to PIO, OK your way back and then go back to set to DMA. I will no longer write dissertations on this. Here's the link -> http://winhlp.com/node/10
2. The mouse actually is old and the clicker doesn't....
3. It's a single core machine and the "event queue" is full. No, there is no real fix for that. More CPU cores help.
4. Yes. It can happen in 7. There is no perfect OS.
5. Why not reduce the CPU load when it matters?
I have 2 desktops both working on BOINC projects (malariacontrol). These are low priority processes eating all spare CPU-cycles. One desktop is a dual-core machine, the second a single-core both with 2GB RAM running Vista Home (enough free memory). The disks of both machines still have a lot of spare capacity. Both machines seem to freeze every now and then. On the first machine, I am always playing music from internet (accuradio.com through IE) and this stops sometimes completely (I get a pause in the music for up to 5 seconds). On the second machine, the mouse (Logitech cordless) sometimes does not react at all (it simply misses clicks or double clicks). On that machine, I have installed ThreadMaster which restricts permanently running processes such as malariacontrol to use no more than, say, 90% of the CPU-cycles. This improves the performance of the mouse, but it is still missing clicks. On the first machine, I use relatively heavy applications such as Nikon Scan (photo scanning) and Corel Paint Shop Pro. These applications (and others such as Windows explorer) sometimes do not react for a long time (up to 10 seconds!) while Windows displays ?not reacting? in the top line of the window of that application.
Before I started using these 2 machines under Vista, I have used XP based machines with basically the same configuration for years. And I never experienced this kind of odd behaviour at all. It seems as if the schduler in Windows sometimes 'forgets' processes to have them run. So, my questions are:
Is anybody else experiencing the same strange behaviour?
If so, what could I do to solve the problem?
And, finally, could I expect Windows 7 not to exhibit this problem?
Thanks for your advice.