Jump to content

Recommended Posts

Posted

Sometimes when I open a stored autocad file to continue working, the whole program turns itself off! Has anyone else experienced this?

Posted

Haven't experienced the problem you memtion.

 

Perhaps the *.dwg isn't a file generated in AutoCAD?

 

Welcome to the forums Don! We'll soon hear from other forum members unless they're all off this Good Friday. Even so addiction to CAD most'll read your post sometime today. :geek:

Posted

Is it the same drawing every time that causes this, or can it happen with any drawing?

Posted
Sometimes when I open a stored autocad file to continue working, the whole program turns itself off! Has anyone else experienced this?

 

Is there an error message before it shuts down? Did you try drawing recovery? Open an AutoCad session by itself, go into file, drawing utilities, recover and click on the file.

Posted
Haven't experienced the problem you memtion.

 

Perhaps the *.dwg isn't a file generated in AutoCAD?

 

Welcome to the forums Don! We'll soon hear from other forum members unless they're all off this Good Friday. Even so addiction to CAD most'll read your post sometime today. :geek:

thanks for the reply. I'm using the trial version of autocad 2010 and I find it unpredictable, sometimes it turns off just as it starts loading a new session or as I say when i try to open from an existing file. File extensions are correct. No error message shows

Posted

Based on personal experience with this very thing I would uninstall completely, download another copy and try every thing again.

Posted

A year or so ago I had full AutoCAD 2007 shut down on me with no warning of any kind a couple of times. Turns out I needed a bigger memory. Usually it was in a drawing with HUGE amounts of small polyline objects, specifically a millwork catalog with about 800 crown & other types of molding profiles. If I selected a polyline to drag around its arc handles after I had been working the drawing for a while it would just go poof. Another time it did the same thing trying to do a Hatch Edit in a drawing with mega quantities of gradient. There was a lot of high end lobby and conference room furniture with curvy swervy stuff that needed shading so you could sorta see the shapes. All of this was 2D.

 

Anyhow, the point is, the physical memory in your computer is probably too small, which was mentioned previously. My boss bumped from 2 gig up to 4 gig and we never had another issue with those drawings.

Posted

You have to go back in history a bit to understand this.

 

Back in the MS-DOS days Ctrl-Alt-Del would Automatically reboot your computer.

This happened so often when trying to use this newfangled drafting software that they chose to name it Auto CAD.

 

 

 

 

 

 

The preceeding is a late April Fools joke.

Posted

well at times autocad is kinda "sick" hahaha.. at times it does dat.. it happens to me a few times.. so e best thing to do it.. to save every now and then :D "play safe" hehe

Posted
You have to go back in history a bit to understand this.

 

Back in the MS-DOS days Ctrl-Alt-Del would Automatically reboot your computer.

This happened so often when trying to use this newfangled drafting software that they chose to name it Auto CAD.

 

 

 

 

 

 

The preceeding is a late April Fools joke.

 

:lol:And a good one at that. You made me laugh hot coffee out my nose.:lol:

 

Some of us have been doing computers long enough to remember that. I have only been working in AutoCAD since the 2007 Version, but I took my first class way back when 3D was something you needed red and green glasses for.

 

I spent nearly 25 years as a computer programmer.

Speaking from personal experience behind the monitor screen, any program with as many lines of code as AutoCAD is occasionally going to find an unintentional exit and just go away.

 

limited memory resourses can cause a large complicated imperfect program to overwrite stored runtime information, like the subroutine location you just called by clicking something. If the program finds something (or Nothing) where it expected to find executable instructions, it could do anything. It just tries to execute what it finds. If the operating system finds a program running around in places it's not supposed to be, the OS will kill it. It may or may not tell you why.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...