Originally Posted By: rharv
In response to your concern about running RB from the C: drive .. you can run the program there, but Save the work to any drive you want.
I'm just talking about running the application on C: (the part that does the work).

You can still save to whatever drive you want (though an external USB will usually be slower).
And it will be even slower if it being used to run both the application AND be the drive it is writing to when it saves. Two different processes taxing a USB drive..

Let's say you run RB from C:, and Save files to F: .. if C: dies you haven't lost anything.

It's just a suggestion and trying to help .. again, I don't work here, most of us forum members do not work here.
Yelling that you're not happy, in a post directed to me, made me want to clarify.
Not sure what you expect me to do personally.

/Have you tried the Live Help Chat option at top?
//Maybe you'll get lucky and someone from PGMusic can take a look and help.


Note: any drive can fail not only C Drives. In most cases the C Drive is the best place to keep System and Programs.

In the case of BB and RB I set them up on the C Drive and the RealTracks, RealDrums (G drive) and my song files and renders on (L) different drives. I do this to make backups etc easier and also different needs on different drives.

I do similar with a number of resource heavy VSTis (some have many gigs of data that I don’t want filling my C Drive which is only a 512 SSD).

Tony

HP i7-4770 16GB 1TB SSD, Win 10 Home,
Focusrite 2i2 3rd Gen, Launchkey 61, Maton CW80, Telecaster, Ovation Elite TX, Yamaha Pacifica 612
BB 2022(912) RB 2022(2), CakeWalk, Reaper 6, Audacity, Melodyne 5 Editor, Izotope Music Production Suite 4.1