I will continue to dig for information regarding this, but has anyone set up a scratch disk for Solidworks to use? If so how was it done?
What's a Scratch Disk?
A scratch disk is a directory or ideally a seprate no-OS bearing drive where a large resource intensive program writes and reads data to. Think of it as a virtual memory on steroids.
Adobe Illustrator and Photoshop use this. Boosts productivity and load times.
Interesting, I've never heard that term before.
I do this manually, I have only program files on the C: Drive and all data files on the F: Drive.
I do this for security and backup. If the computer fails or crashes, I just remove the F: Drive and plug it into another computer, no data lost.
Is that what you mean?
Similar in concept, but no files are actually saved to the drive.
The way you manage data is the same as how I do it at home, or would do it here if we didn't have a massive PDM server.
You mean the "temp" files are not on the C: drive?
In SolidWorks, use the System Options to change the locations of the listed folders, for example, to the F: Drive.
In the SolidWorks Task Scheduler, you can set the location of the Temp file(s).
I'll give it a whirl.
Thank you everyone.
Isn't that essentially what a Raid does? As far as security and back-ups go?
Um...not to be critical or anything, but how is that secure or good for backups? Wouldn't a crash potentially harm the F drive as well? And what if the F drive crashes?
Unless you're backing up each evening to the F drive so you have two copies of everything? That would be better, tho a single power surge could still potentially kill both drives. And I'm hoping F is SATA/ESATA and not USB.
And if you're just worried about the computer just not booting up, there's no reason you can't just remove the C drive and plug it into another computer and mount it there. (Unless the C drive is fried, but that's the same situation as if the F drive were fried.)
Seems like you'd be better off if your data drive were in another room. Without a RAID setup, at the very least you'd be better off saving everything locally (C, F, whatever) and backing up to a NAS somewhere. Better for backup purposes as you have two (relatively) independent copies of everything.
p.s. And at one point many moons ago a VAR did tell me to move the windos paging file to a separate drive, and to make it a constant size.
I've been using this method for 10 years.
No, if the computer crashes, the F: drive is not affected. The only affect would be if the computer crashed while writing to the F: drive.
I've had 2 computers crash and I've just moved to another computer and plugged in the F: drive and kept on working. We have 6 computers in our company. The real hassle is contacting SolidWorks and deactivating the account on the crashed computer.
I think he meant that if you are limitted by the 4GB ram limit of a 32b, switch to a 64b system (for that, you need to install a new version of the OS).
For the scratch disk... I don't remember if Solidworks gives you a possibility to add one, but in my memory of file management, solidworks keeps everything into the ram, and write data only when you push the save button. Then, you need to ask how Windows manage the memory because all the memory space is not only constituted by RAM only... and after that, things gets complicated... (that should be the simple way of presenting things).
Lately, people start to have huge amount of ram on their computer, especially on i5/i7 system system are available with 8-12 GB of ram (limited to the max Dimm size currently available on the market), so if people does not use all the ram (for example, if during your normal work, you don't exceed 6GB of consumption), then, they use the remaining ram as a virtual disk and put the pagefile on it. Works pretty good (especially with a SSD to avoid reducing its lifespan.)
Josh may be correct in assuming the windows page file acts like the PS and AI scratch file.
First hit on Google: http://support.microsoft.com/kb/307886
Worth a shot?
If it works, make sure to report back! This would be well a well suited application for a solid state drive....
Retrieving data ...