That's mostly what the first part of my question is about. I dont know much about it, but I heard or read somewhere that SW files sometimes can benefit from being purged of obsolete info in a similar way that ACAD files do.
"Purging" files is (among others) an ACAD thing. It cleans up dwg files.
The nearest thing for SW would be Unfrag or Eco-Squeeze which remove the Windows "shadow" crap. Neither of those are recommended by SW, but most people have found they work well.
Depending on your version of SW it can leave behind the "~$yourfilename" files in the folder that you were working on if SW crashes with a file open. Also if SW crashes it can leave behind alot of files in your temp folder, I'm in the habit of cleaning that folder every morning before I start any application. Also, depending on your SW version, it will put backup copies of your files into the "TempSWBackupDirectory" folder. That folder can get fairly large and needs cleaned out on a regular basis. I'm not smart enough to know why, but it doesn't appear that SW2007 does that any longer. The only other "purging" you can do that is similar to ACAD is deleting the unused blocks out of your drawing files. I have never found that to make any difference in file size or performance like it would in ACAD (especially if you don't use blocks in SW).
sounds good. I didnt mean to throw everyone with the "purging", I was meaning along the lines of "house keeping". Thanks all for the input, and stop now, the more the better. For the temp stuff, I have the batch that I think it was SBaugh posted of someone elses and use it every night when shutting down. Works very well. thanks again.
Not that I have seen it happen myself, but SW will tell you if you use Ecosqueeze that if the file corrupts the refuse to help you or support you... because you used a compression tool that they didn't write... so "Use at your Own risk"
I hear that with the "use at own risk", just reaching for anything I can that's free due to the stinginess of my company and not being able to beef up my computer
Ecosqueeze won't make your computer run any better. It just reduces the file size on disk. Cleaning up your temp files is certainly a different matter, though.
Not looking to make my computer run better, just assuming that any "cleaning" of files would work toward improving the efficiency of the computer in working with file(s).
Thanks Yoda, Look to the ideas I will. A lot of that is already incorporated in our setup and the way we do things, but there are some items there I will look at more closely. I really think it's mostly about the RAM though, but I could be wrong. I have 1GB, from what I have read, that is for all intents and puposes a min for what we sometimes get into. I could be wrong though. Just a revisit, Handle, I hope what I wrote in response to your post didnt come across the wrong way, I was just trying to express that in my way of thinking, there is a difference between "making the computer run better" and setting things up to allow a better output from the same level of computer performance, much in the same way that a simple cylinder will process better than a 1000-part assy with 400 top-level-mates. That's all I was getting at. And I'm not implying an understanding of file architecture or SW processing of the files.
Scott, I heard the warning about Unfrag late last year and it was first I heard of it. Do you know how long they've been cautioning against it? I know my VAR still has it on their website.
First time I've heard of this warning was some five-six years ago when I started using Unfrag. Since than I've used Unfrag on thousands and thousands of SW files and never had a single problem. I've never heard of anyone having a corrupt file due to Unfrag.
![[cheers]](/data/assets/smilies/cheers.gif "[cheers] [cheers]")
![[pc2]](/data/assets/smilies/pc2.gif "[pc2] [pc2]")