Re: Another SLOW Question ... In article <LX0xg.8246$8j3.2844@twister.nyroc.rr.com>, ddonath1@twcny.rr.com
says...
[SNIP]
Basically, Scratch Disk (size, location, etc.) provide PS (and some other
programs, set from within those programs) with additional "virtual" memory to
process images. You will run out of RAM at some point. Ideally, a machine
should be configured around these guidelines"
1.) OS and programs C:
2.) Images D:
3.) Scratch Disk E: - G:, where these are big and fast physical HDDs.
OK, so you have C: & D:. Assuming that they are physical HDDs, and not
partitions (virutal drives), the best solution would be to set D: as your
first Scratch Disk, and C: as your second. Keep D: as clean as is possible.
With HDD prices falling, it's pretty easy to acquire additonal drives for
Scratch Disk use. Again - big and fast. All you have to worry about is the
controller, but if your MoBo doesn't allow more HDDs, a separate controller,
say a PCI board can work fine.
Reason to keep Scratch Disk HDD free is so PS can use all of it, and not end
up with fragmented TMP files. As PS will (should) clean out this HDD, when
closed, it is always empty, except when you are actually working in PS. You
should not need to de-fragment, but it doesn't hurt to check it once in a
while, especially if you have a PS crash.
If you use C: (OS, PS and Scratch Disk, plus whatever else) they will be
fighting for time through your controller and fighting fragmentation all of
the time.
Hope this makes sense.
Hunt
Noone@hunt.com (Hunt)
|
|
