I'd have to agree with this. With exception to the *speed* of the HD. If it's slower drive then the current the trade off could be equal.
This could also increase performance a little by putting the virtual memory (swap file) on it's own drive, next to the main drive if using partitions.
I used to use a separate drive for AW and my swap file.
In fact, I put any expanding folders or files on separate drives to limit how much C: becomes fragmented.
I have partisions on a 40GB HD.
I use C: (2GB) for OS, tweaking proggies, and any drivers.
D: (1GB) to store all Temp folders, Temp Internet File, Swap file.
E: (4.5GB) for all my programs, only.
F: (4GB) for all my games.
G: (6GB) for develepment projects and Software install exes.
H: (8GB) for music
I: (5GB) for processing music and video files
etc....
Originally posted by Sundowner
If AH is on dedicated drive, (this includes page file located at the front of another drive) your disk head seek times to AH.exe should be faster due to AH always located at the front of the drive.This should lead to a bit faster AH load times than a drive with both AH and OS.
Also, with only AH being accesed, the dedicated AH drive should fragment at a much slower rate than a drive with both AH and OS. Drive seek times should remain at optimum longer.
Originally posted by Sundowner
If AH is on dedicated drive, (this includes page file located at the front of another drive) your disk head seek times to AH.exe should be faster due to AH always located at the front of the drive.This should lead to a bit faster AH load times than a drive with both AH and OS.
Also, with only AH being accesed, the dedicated AH drive should fragment at a much slower rate than a drive with both AH and OS. Drive seek times should remain at optimum longer.