PDA

Click to See Complete Forum and Search --> : Recoving an InDesign document


akiger
09-18-2008, 07:42 PM
I am a Quark user. Like forever. I am just now wandering around in InDesign and am using it for a small 40 page catalog. So far, I like what I see, however, I had to do a force quit on the application because it hung up when importing an image. The document was saved several times prior to this, so I know that all was not lost, but is there a way to recover that file?

Quark gives you a Recovered Files folder on the desktop. PLEASE tell me that Adobe has a safety net like this too.

Title should have been "RECOVERING"... sorry.

seosamh
09-18-2008, 07:48 PM
indesign creates a temporary file which saves every so often(or something along those lines, you see the file next to the original in the finder when you open an indd),

when you open indesign again it should load up the crashed file, click yes to the message that comes up, your document should open at that last auto saved point. generally pretty recent.

CkretAjint
09-18-2008, 08:03 PM
when you open indesign again it should load up the crashed file, click yes to the message that comes up, your document should open at that last auto saved point. generally pretty recent.

This has been my experience as well. :)

Craig B
09-18-2008, 08:06 PM
ditto.

akiger
09-18-2008, 11:24 PM
Ok, all is well. I had to restart my computer for some reason, then restart ID and it popped up. Thanks everyone.

Back to work....

Broacher
09-19-2008, 02:04 PM
^ Tip: if ID hung on a photo placement, my guess is that you were trying to place a real hunker. Possibly an EPS image? ID will try to generate a jpg of placed images and EPS images tend to be whoppers. In Quark, the default is to NOT generate a med rez preview, but to look for the low rez embedded one (with EPSs, anyhow). You can tell ID to behave that way too, if needed, or run in 'normal' view mode.

But the real reason I'm bringing this up is that it could be that you're running on a system with either low RAM, and/or minimum disk space-- or highly fragmented disk space. Might want to check that out before getting too far ahead with that catalogue. If the restore file gets too far fragmented and goes south... it's not good.

garricks
09-19-2008, 02:40 PM
One more bit of info: When you have a file open, Indy creates a temporary file in the same directory/folder. The icon is a lock, and the file begins with a tilde (~) and ends with the extension .idlk. If, when you restart, the restore routine fails to start automatically, double-clicking on the .idlk file will force it. If the Indy file won't open, you can try trashing the .idlk file, but you'll lose any changes you made that are stored in it, so it's a last resort option.