Author Topic: autosave Q...  (Read 8281 times)

0 Members and 1 Guest are viewing this topic.

t-bear

  • Guest
autosave Q...
« Reply #15 on: August 04, 2004, 04:14:09 PM »
Quote
.....a bak1, bak2, bak3, etc...


<SHUDDER!>
That's all I need.... "now creating....*.bak379,244"....

sinc

  • Guest
autosave Q...
« Reply #16 on: August 04, 2004, 04:29:18 PM »
Quote from: t-bear
Quote
.....a bak1, bak2, bak3, etc...


<SHUDDER!>
That's all I need.... "now creating....*.bak379,244"....

File Not Saved Error: disk full (79,957,946,535 of 79,957,946,545 bytes used)  :D

sinc

  • Guest
autosave Q...
« Reply #17 on: August 04, 2004, 04:39:17 PM »
Quote from: ronjonp
So how do you get the *.bak files to save to a certain directory when using a qsave? Currently, it saves them to the same path as the drawing. I would like to isolate them to one directory rather that having them scattered all over the network.

Thanks,

Ron

Make sure you've thought this through before you do this.  It can work if you have strict naming conventions for your files that result in no two drawings having the same name, regardless of the directory or project they may be in, but it can still cause problems, especially in multi-user environments...

Most of the time, if you're trying to get to the .bak file, having it right there with the original drawing is the most convenient place for it.  Just configure your automated-backup software (you have some, right?  :D ) to ignore the .bak files, and make sure they're deleted before you archive a project.

ronjonp

  • Needs a day job
  • Posts: 7527
autosave Q...
« Reply #18 on: August 04, 2004, 04:51:20 PM »
Quote
Make sure you've thought this through before you do this. It can work if you have strict naming conventions for your files that result in no two drawings having the same name, regardless of the directory or project they may be in, but it can still cause problems, especially in multi-user environments...


Good point....I'll research it further.

What part of Colorado you from Sinc?

Windows 11 x64 - AutoCAD /C3D 2023

Custom Build PC

CADaver

  • Guest
autosave Q...
« Reply #19 on: August 04, 2004, 05:23:35 PM »
Quote from: t-bear
If I use this, doesn't it overwrite the last *.bak?  There would be no more .baks than with doing a normal qsave....right?  One .bak per .dwg in a folder.....

Ahhhhh, Ron. Reverse problem, eh?  This is getting interesting.
Autosave makes subsequent BAKs as it goes, so if you've been working for a while without a save you can have several.

AUTOSAVE was designed for a catostrophic failure of the system.  Based on the savetime, it makes a ???.$SV file.  This file is deleted when you save or exit the program properly.

If BAK is on, AUTOSAVE takes the old $SV and makes a BAK, if you've properly saved or exited there is no $SV to make a BAK from, so autosave renames the $SV and begins to make new BAKs

sinc

  • Guest
autosave Q...
« Reply #20 on: August 04, 2004, 08:42:39 PM »
Quote from: ronjonp
What part of Colorado you from Sinc?

From Pueblo, currently living in the Colorado Springs area, although I tend to think of Boulder as "home"...

t-bear

  • Guest
autosave Q...
« Reply #21 on: August 05, 2004, 08:02:20 AM »
Pueblo...C. Springs....Boulder..... That 'bout covers the state from north to south.  Notice you didn't mention Denver .... so I won't either.  Lived in Montezuma for a few years, working for Keystone.  That's waaaaay back when it was first started.  Did you know that Montezuma and St. Johns were both considered for the state capitol when Colorado was applying for statehood?  Talk about going up on capitol hill......!

CADaver

  • Guest
autosave Q...
« Reply #22 on: August 05, 2004, 08:08:59 AM »
Lived in Denver for a year back in the early '80's, workin' fer Stearns-Rogers.  I'd move back tomorrow if I could talk the wife into it.

M-dub

  • Guest
autosave Q...
« Reply #23 on: August 05, 2004, 08:45:02 AM »
That's a big IF...anytime you bring 'The Wife' into the mix...

:roll: ;)

CADaver

  • Guest
autosave Q...
« Reply #24 on: August 05, 2004, 10:01:42 AM »
Quote from: M-dub
That's a big IF...anytime you bring 'The Wife' into the mix...

:roll: ;)
Yeah buddy, she didn't like being cold, and when we moved from Denver to Chicago, she liked being colder even less.  So here we are on the Texas Gulf coast, it was 103F here yesterday with 98%humidity  :cry: ... well she ain't cold.

M-dub

  • Guest
autosave Q...
« Reply #25 on: August 05, 2004, 10:33:54 AM »
Quote from: CADaver
Yeah buddy, she didn't like being cold, and when we moved from Denver to Chicago, she liked being colder even less.  So here we are on the Texas Gulf coast, it was 103F here yesterday with 98%humidity  :cry: ... well she ain't cold.


A lot of people around here complain about the cold as well, but I'd gladly take 5 frigid days over 1 extremely hot & humid day.  As far as I'm concerned, people should only be allowed to complain about 1 season.  It's either too hot or too cold.  Myself, I complain about heat.  It's a lot easier to warm up than it is to cool down.  Camping last weekend was great weather.  it got a little hot when the wind died down, but I like it around 85 degrees.

CADaver

  • Guest
autosave Q...
« Reply #26 on: August 05, 2004, 12:02:12 PM »
Quote from: M-dub
It's a lot easier to warm up than it is to cool down.
You can put on the right clothes to get warm, but you can strip down to arrestable and still be hot.

M-dub

  • Guest
autosave Q...
« Reply #27 on: August 05, 2004, 12:04:49 PM »
I was going to say exactly that.  It takes a little more effort / technology / money to cool down.

Like you said, if you're cold, put a sweater and a hat on or light a fire.  If you're hot, hope you've got a pool or an air conditioner, etc.

pmvliet

  • Guest
autosave Q...
« Reply #28 on: August 05, 2004, 02:07:38 PM »
Normally AutoCad will create the BAK where the file is located. Here in our office we move the BAK's to th user's lcoal C:\DWG\Bak directory.
Eventually you would take up twice the space on the server with each DWG having equivalent BAK.

There is a variable in AutoCad called MoveBAK. You can set this to anywhere you want it to be. Moving it to a local machine does a couple things. It keeps the server clean. If multiple people work on a file, the work they do is saved as a BAK on their local machine. So if person A does work on a file and is done working. Person B goes into the file and say erases all of A's work. After you go over and slap B's head, you can go to person A's computer and get their BAK file.

BAK's will overwrite the existing and be a perpetual back-up. I have seen sequential but I am not sure how this occurs or what causes it.

Pieter

CADaver

  • Guest
autosave Q...
« Reply #29 on: August 05, 2004, 03:03:45 PM »
Quote from: pmvliet
Normally AutoCad will create the BAK where the file is located. Here in our office we move the BAK's to th user's lcoal C:\DWG\Bak directory.
Eventually you would take up twice the space on the server with each DWG having equivalent BAK.

There is a variable in AutoCad called MoveBAK. You can set this to anywhere you want it to be. Moving it to a local machine does a couple things. It keeps the server clean. If multiple people work on a file, the work they do is saved as a BAK on their local machine. So if person A does work on a file and is done working. Person B goes into the file and say erases all of A's work. After you go over and slap B's head, you can go to person A's computer and get their BAK file.

BAK's will overwrite the existing and be a perpetual back-up. I have seen sequential but I am not sure how this occurs or what causes it.

Pieter


You're talking actual drawing BAK's, we're talking AUTOSAVE file BAK's