Never thaught about pointing my temps to the C:/ drive... sounds good. But how do you set it to do so? Is it just these Prerendered Files folder you choose in the Prefs or all your system's (XP) Temps? In this second case, how do you make it ?
I'd like to know how to point ALL the Temp files I make into the same big subdivided folder cause I've always had them all over the place without exactly knowing how come...

And I guess I'll re-install Vegas and other SF apps on the Raid array ("0"), different partition than the OS. Like I've been doing for quite a good time now. I only had a doubt because I noticed this recommandation on the Sony site, as I said. Thay probably say that so it's easier for them to troubleshoot by phone or the Net if they have to, no?

My guess is that you will be doing a lot of work for very little gain by reinstalling Vegas on another drive. I would certainly make some measurements before and after. My guess is that you won't be able to measure any difference whatsoever because the actual program code is not accessed that often.

I would instead recommend changing the location for your swap file and temp files, both very easy things to do, and easy to reverse. Keep a small (16MB) swap on C: and then set your main swap file to a folder on a different physical drive.

Paging file changes:

1. Right click on My Computer.
2. Select Properties.
3. Click on the Advanced tab.
4. Click on the Settings button under the Performance heading.
5. Click on the Advanced tab.
6. Click on the Change button under the Virtual Memory heading.
7. Set the Custom size for Initial and Maximum sizes for each drive. For C:, I use 16 and 32 and then on E: (my second physical drive) I set 768 and 1024. Feel free to make these larger, if you wish.

To change the TEMP location, follow steps 1-3 above, and then click on the Environment button.

The only real benefit to installing Vegas (or any other app) on a second drive, is that it's much easier to deal with if you lose your boot drive or crapped out OS. Otherwise, there is little to zero benefit

For my swap/page file I set the maximum and minimum to the same value. This way Windows does not try to "manage it" in the middle of operations.

The page file also doesn't become defragmented (provided you either set your page file up early or that your drive still has an empty block bigger than your page file.)

Thanks John for the "Temp pointer". I'll certainly do it.
As for memory, (swap/page file) I usually go exactly your way, buster.
Thanks everybody.

"I'm planning re-installing on a RAID array 0, different partitions for my OS and my programs.
Any comments ?"

Yes. Don't partition.

Partitioning was developed way back when hard disk capacity exceeded the OS address space. When you partition a disk, you get what the OS thinks are separate drives, but it's all still one physical disk.

Your best editing performance comes from having the OS and application programs on a separate physical drive from your media files.

You know Steve, I didn't catch the word "Partition" in the post....
FuTz, Steve's right, you'll gain nothing. I was thinking you were doing separate physical drives.

Yeah, keep the O/S and programs on one partition. Create a second partition on the first drive for other stuff. Then, put your media files on a separate physical drive. Partitioning is still VERY useful on the first drive to help you do image backup of the programs and O/S, without having to create a giant backup image that includes media files, etc. I usually partition the C: drive to around 10 GBytes, and then create a D: partition for the rest of the first drive. I never partition any other drives.

One very good reason for partitioning is for system security. I see it practiced in Linux more than Windows.

The idea here is to put data that can grow onto a separate partition so that it doesn't fill up your boot drive and cause headaches. So, for instance, you would put your renders and temp files on a separate partition, or a separate drive would be even better of course. The goal is to keep from accidentally filling the boot drive and making your system nearly unusable.

In Linux the Swap file gets it's own partition, and the area where log files and other similar data goes would also get it's own partition.

If you were to do this with Windows, and if it would cooperate-which it won't, you'd have a partition for the swap, and a partition for system restore data, temp files, downloaded files, and logs, and a partiton for user data. Add to that separate physical discs for Vegas media and renders.

One security exploit has been to force programs to write log data until they fill the partition and lock up the system. It's mean spirited. We had this happen on our Win2003 server when the mail server filled up the system partition with logs. Down went the mail server for a night.

Rob Mack

My oh my... my mikstake.
What I usually do is put OS on one physical drive and the apps on another physical drive.
OS and Apps each having their own partition on their respective drive. Think about an imitation of Raid where two drives do the work instead of one...
What I just had:
10Go for XP (I used around 6,5Go so far)
12Go for Apps (I used around 3,5Go...)

NOW, what I'm probably gonna do is put OS and Apps on the same drive and same partition, since I just learned I wouldn't see much difference. But I have to think about it a little more because I like the idea of doing a re-install of XP without earsing all my Apps, just repointing those after the fresh install. If I go this same way I'll give XP a 12-14 Go this time and a little less for the Apps. I like to have "headroom" on these drives so I can very easilly make my defrags, for one reason. But since we don't do much of these re-installs nowadays (it's not Win98 anymore, which caused me lots of blues screens/ trouble in my "debuts"), I'll think about it.
I always put my media on different drive(s). And render to another one from the media.


Now I'm waiting for an answer from these guys at Promise: my system kind of "artificially functions" on WinXP (which I didn't lose either) now but since I didn't re-built my Raid array, if I add my storage disks everything gets messed up because the Bios points at the IDE drives to boot since there's no array defined. I guess I'll have to re-format when I rebuild the array so I just spent the last 24 hours burning data and resaving it on external drives since this "artificially functionning" system recognizes these Firewire ext. drives... Just crossing my fingers for a Promise' miracle that would allow me to re-build this array without re-formatting the drives...

Re-re edited... while John Cline was already answering (sorry!)

I do exactly the same thing as John Meyer. I put my O/S and programs on the C partition and use the D partition for any "transient" data like the system temp folder, the temporary files folder for Internet Explorer or other programs and also for downloads. Generally, anything that isn't video, audio or project graphics. I also keep files I reuse all the time, like logos, backgrounds and my client's "slates" on the D drive.

A lot has been said here on this forum about no longer needing to defragment hard drives. While it may have become less necessary these days, it hasn't become totally unnecessary. Keeping just the O/S and programs on the C drive keeps fragmentation minimized (although, not completely eliminated because Windows itself constantly changes and updates a lot of files on the system drive.) As John Meyer pointed out, keeping only the O/S and programs on the system drive keeps the backup images compact (and relevant) by not backing up a bunch of extraneous, temporary stuff.

John

Johnmeyer, nice suggestions. Do you put both system AND user temps on the different physical drive?

-jerry

Yep! Same thing: I keep what I like to call "daily storage" on the remaining Go's of these partitions and the "real stuff" on different drives.
I checked to repoint my Temp files to another direction but following the instructions, I can't seem to just enter a browsed location in the fields; the system asks for a "value", which I have no clue about what this is... I expected a location like D:/Temp files/etc etc... not something like "%USERPROFILE%\Local Settings\Temp"
Any idea or recommandation?

If you have multiple users, then they each have their own temp folder based on their user name under "Documents and Settings." If your user name is "futz", then the system translates "%USERPROFILE%\Local Settings\Temp" to become "C:\Documents and Settings\futz\Local Settings\Temp"

Just create a folder named "temp" on your D drive and change the setting to
"d:\temp" and you'll be "good to go."

John

Thanks! I'll try that as soon as these Promise guys answer me.



So far, I essentially got this :
"Case Problem:
I replaced an Asus P4P800E-Deluxe mobo for the exact same model (first one died). On the previous one, I had a RAID array ("0" / performance) with two identical 80Go drives. I didn't lose any data on any of my drives (both OS and storage). I'd like to re-install my system without losing any data either, is that possible? everything seems to run fine now except since I didn't go through the FastBuild Utility and re-built my array, if I plug my additionnal storage drives on the system, everything gets messed up. I figure I have to re-build the array but I guess I'll have to re-format the OS/RAID drives too, ain't it? Is there a way to bypass this re-formattting and rebuild my array without having to re-install everything? Thanks

Case Solution:
Hi With array 0 this mean you have both drives combine as one single drives. Since everything is working correct why do you want to do a clean installed over again? If you are planning to re-installed Window on array 0 than both drives will need to be reformat unless you run a Window repair console. Thank "


The guy said "Since everything is working correct why do you want to do a clean installed over again?"... well, back to the original question with more explanations I guess...