Errors when printing and recovering

[Tabetha]

AutoCad 2006 full
Microsoft Windows XP
Version 2002
Service Pack 2

I've been arguing with this for three hours now, and i can't find a thing about it online by googling it.

I merrily work on my drawing, then I want to print my drawing....not a problem until now. It tells me it's spooling and happily printing away, and suddenly I get this:

"Internal Error:
!scandr.cpp@802: ePermanentlyErased"

Ok....fine. It closes the drawing. I re-open AutoCad and it asks me if I want to recover my files, and of course I do. So it starts speedily recovering my files, restoring blocks and layers, and all kinds of other things that zip by too fast to read....then it grinds to a halt and I get this:

"FATAL ERROR:
Unhandled Access Violation Reading 0x0004 Exception at 477ed6h"

And there end my woes, because now my drawing is locked away in some violation zone I can't get to. I've tried restarting CAD, restarting my system, threatening it with large magnets....

Help??

[LSR]

If your AutoCAD works, your only recourse to recover that file is to look for your autosave file (filename.sv$),
and covert it to drawing file (filename.dwg), just replace the sv$ to dwg.
It usually reside in C:\Windows\Temp...filename.sv$ (or do a search).
I hope that your save time is set to every 5 minutes otherwise even if you are
succesfull in converting it, you'll lose some of your work.

[Groutie]

What about your filename.bak file. This should be perfect up to your last qsave/saveas. Rename .bak to .dwg and off you go. More reliable than .sv$ if you're in the habit of qsaving after every input.

[Galingula]

If you get it open, Purge/Audit/Delete Layer Filters

[Tabetha]

We've been obsessive about saving work here for a while now, fortunately. I had a co-worker open it, and the same thing happened on her computer.

Then, on a whim, I had her grab just the critical portion of the x-ref on the page I was having trouble with, paste it into a new drawing, and replace the existing x-ref with the new one...and it worked perfectly...I can print anywhere I want to now.


And so I'm working away, and suddenly it does it again! Different x-ref on the page I tried to print. I suppose I'll try what I did last night, but it seems like an awful lot of work. I'm guessing something, somewhere is corrupted, whether its a layer or a whole file.

I don't have any layer filters on, the project isn't big enough. The only tell-tale that something was wrong was my drawing got boggy and slow about 1/2 an hour ago. Other than that, it's been smooth sailing all day....maybe it doen't like 3pm?

Thanks

[Cad64]

I had similar problems with some files one time and this is what I did: Open all of your xrefs and Audit them to fix any errors that may be present. Delete all layer filters and then purge everything out of them that is not being used. When Cad crashed, it may have corrupted some of your xrefs.

Concerning your Autocad slow down, delete your Temp files and empty your Recycle Bin to free up resources for Autocad to operate. You may also want to defrag your computer.

[brassworks]

If you get a daily diet of "Fatal Error" messages, try this:

Command: WHIPTHREAD Set variable to <0>

I don't really know what it means, or what it does, but this was the advice from CarlB at a different forum some time ago, and it has helped a lot.

[dtkell]

I had similar problems with some files one time and this is what I did: Open all of your xrefs and Audit them to fix any errors that may be present. Delete all layer filters and then purge everything out of them that is not being used. When Cad crashed, it may have corrupted some of your xrefs.

Concerning your Autocad slow down, delete your Temp files and empty your Recycle Bin to free up resources for Autocad to operate. You may also want to defrag your computer.


If you get a daily diet of "Fatal Error" messages, try this:

Command: WHIPTHREAD Set variable to <0>

I don't really know what it means, or what it does, but this was the advice from CarlB at a different forum some time ago, and it has helped a lot.

I agree with CAD64. That has aleways fixxed problems for me.
This is the first time I've heard of "whipthread", but mine is set to zero.
I did know of "whiparc" being set to zero if you are having crashes while panning and zooming. If changing the systemvariable doesn't fix it, you need to remove from registry and try again.