Hi - the problem I am going to describe is not new. Just now I restarted Parallels with XP (on a 15 GB virtual disc - expanding) after I closed XP down with the exit of the last Parallels session. After starting up Parallels, XP begun to start as it should, but it took about 20 minutes to become fully loaded with endless HD activity. After this, XP responds fully speedy and behaves normal. This happenes here and then. In those cases RESUMING is very slow, too. If I restart my MacBook Pro, the startup time returns to normal. Looks like this effect accumulates with time up of the MacBook (I now a little over 6 days). Any proposals or ideas?? Any help would be greatly appreciated.
This raises a bunch of questions. First, is it just Macbook up time, or Parallels up time (if you shut down the Parallels app, does it "reset"?) Then there's the question of indexing drives. Both OSX and XP do whole drive indexing. I had much Mac disk activity until I exempted my VM folders from spotlight indexing. I'm using Win2k with MS indexing disabled, but XP may try to do more. Curious. Let us know what you find.
Thanks for the message. I was referring to MacBook uptime. I disabled Spotlight indexing for the Parallels folder in my home directory (with the virtual HDs) - I shall see if that changes anything. Since I am not too familiar with the subtleties of XP - where do I disable the WIN indexing??
The suggested procedure(s) helped a little, but now I have the suspicion that running a PPC program via Rosetta kills (not only) Parallels performance. This shows for instance only small sized XP windows without the Parallels toolbar etc. After a restart all works fine again. Would be interesting to know if others can support my point?
