Try running the drawing either lightweight or only open the selected sheet you are working on
Happy Fathers day to you as well !!!
I am going to suggest first that you upgrade to SP 5.0 because there were
a lot of issues prior to SP3.1
Once you do that let me know if you are still having the issue.
Thanks for the hint Scott,
I can't update to the "fixed SP" version of SolidWorks because I did not renew my maintenance. After great debate, my VAR got me a SP4.0 disk. I installed it, and the very first thing I did was open then close a file to test the system. SP4.0 completely destroyed the database and I had just lost over 100 hours in a flash. Not even Dessault support could fix the database and so I removed all traces of SP4.0 and went back running something that will not rob me of another 100 hours.
So... back to problem at hand.
All ideas posted so far are good ones. None work though. Accidentally, I think I stumbled across the cause of the problem. I found that if all sheets and all views are set to "draft resolution" that it went back to saving in 3.3 seconds. Hooray! problem solved. Not for long though. What I did to accidentally make it return back to a 3+ minute save was; I first hit CNTL+Q (forced rebuild), then CNTL+S (save). Doing the save sequence while the rebuild process hadn't finish seems to cause it to go back to slow save. It must be garbling the database. I think this is possible because in my system, I use an extended keyboard with user defined keys. I have setup the rebuild and save keystrokes side by side and it is easy to go tap-tap and thus make it try to save during the rebuild (I must slow down, I must slooow dooown).
Fix is to turn on/off just a couple draft resolutions, don't rebuild, save, exit, restart and back to normal.
I'll post later today as hopefully I will be finished with this drawing and if my hypothesis is found correct, I'll update results.
I am so sorry that what I suggested did not work for you.
Wow, I am blown away that upgrading to 4.0 has such adverse affects on your system.
kind of makes me wonder if you were given a corupt disk.
I am glad that you did seem to stumble on your solution though.
Make the views display as Shaded. this will helps reduce file size as well as saving time.