bouncing to disk on an XP system

I've seen a number of people stating they have trouble "bouncing to disk" on an XP system, usually getting a message that they are out of CPU power. Digidesign has provided a number of reasons and things to do which I have tried with some success. The most effective method, and one which has dramtically increased the response of my protools software, was to install a slave hard drive in my PC. I loaded all of the Protools LE software onto this drive and operate protools sessions from this second drive. That way the computer's operating system is not working on the same drive as the protools. Speed improved and latency decreased. Additionally, I don't appear to be limited in the the number of tracks I can add. Has anyone else done this and if so have you seen any negative affects.

The BTD issue was fixed in Pro Tools 6.4 Rail

Pathfinder...Is Protools all you have installed on the second drive?..Do you keep your audio files on a separate drive? What about your 3rd party plugins and such?..Idea sounds intriguing, as I have nothing but a molasses slow response from 6.4.. I can't say whether bounce to disc was fixed with 6.4, because I've yet to finish anything, what with all the locking and rebooting that goes on, on a daily basis since I installed 6.4

BTD was definitely a bug...they found and destroyed it in 6.4.

I'm still interested in hearing the details of Pathfinders setup..Forget the bug.

The system used the protools on one drive and everything else on another. All protools sessions were stored on the external drive. I did have some issues with it recognizing autotune and amplitube. I tried to work through the problems but my system crashed. Unfortunately we had a severe lightening storm that got through and took out my computer (power supply, mother board, and the video board) I had it rebuilt with a faster processor but went back to the single internal hard drive. My IT guy tells me it makes sense to run the operating system on a separate hard drive from all other software but not to split up the applications as I did. Also, I could never figure out a way to load reason, live, etc, and make them go to anything but the 'c' drive. I guess you could load everything on the 'c' drive and put your operating system on 'D' drive and change the boot sequence to look at the 'D' drive first. I may try this in the future but since the melt down, I only have one drive. I just got the computer back today so I'll let you know if I try the two drive system again. my IT guy recommends the operating system use a 10,000 rpm drive and the other drive can be a 7,200rpm unit.

get a new IT guy