Topic: Found an interesting error that can be avoided with Ribbon

[sourdough]

Hi all
    I made this great menubar toolbar a ways back, and didn't notice then when you close a C3D 2010 dwg with the Ribbon closed that it will deposit an error in your dwg file loc. I didn't see it sooner because I turn off my speakers when running autocad not to disturb the many. But, I wanted to find out why this was such a nasty error when you peered into to what kind of error it was. In 2009 it doesn't do it, just 2010 C3D. So, beware of this error. I also found that you can dock it on a dual monitor setup with autohide should you need to do so. I thought it was just a permanent fixture to taking away real estate, but in truth it can reside elsewhere than at the top. Just a helpful hint, and realization about a small error found.

Here is the contents of the error message.

FATAL ERROR: Unhandled Access Violation Reading 0x154631b4 Exception at 1344d6ch

10/23/2009 at 07:16:23.084 drawing:
-------------


FATAL ERROR: Unhandled Access Violation Reading 0x118931b4 Exception at 1344d6ch

10/26/2009 at 14:28:49.285 drawing:

MJP

[mjfarrell]

then when you close a C3D 2010 dwg with the Ribbon closed that it will deposit an error in your dwg file loc

What exactly do you mean by drawing file LOC? Is that short for location? Or is that the Log File Location?
I closed the Ribbon, I closed my file, I had no error, I check the LOG no error?  So how or when exactly does the error get created?

I am trying to recreate it here and either am terribly lucky, or there is another symptom or cause.

[sinc]

I suspect MJP is talking about the "acad.err" file.

But I agree, there appears to be something else involved.  I can turn off the ribbon and shut down C3D 2010 without getting any errors.

[mjfarrell]

I suspect MJP is talking about the "acad.err" file.

But I agree, there appears to be something else involved.  I can turn off the ribbon and shut down C3D 2010 without getting any errors.

Thanks for that clarification/confirmation of my tests on this.
I can both
Close the open drawings with the Ribbon closed,
and close C3D completely with either a drawing open, and no drawing open and there is no error generated.

I suspect it has something to do with his custom toolbar(s), or other. (like some lisp, or VBA)

[sourdough]

I suspect MJP is talking about the "acad.err" file.

But I agree, there appears to be something else involved.  I can turn off the ribbon and shut down C3D 2010 without getting any errors.

Hi Sinc

When I turn off the ribbon before I save and have the menubar on and then save it creates an error. acad.err is in the location where the dwg file is saved. If I keep the ribbon on and have the menubar on and save it won't create the error. Also, I have all my toolbars on that are native to acad of my choice. Hope that you find that you can create that error too. But, who knows it might be something else. I got this error before I loaded any lisp routines at install. I used the orginal C3D profile too. Use ribbonclose with menubar on and save any dwg and it left an acad.err file. I might say that you also might want to scan your whole drive and erase what could have been there first to prove this, as I did, then run the test again and scan all drives. The reason was I had open dwgs in more than just my project files because of recovery and using autosave files converted to dwg files and running them. Let me know if anyone tries this and they find this happening.

Thanks
MJP

[sinc]

So far, I haven't been able to find a way to duplicate this error.

[sourdough]

So far, I haven't been able to find a way to duplicate this error.

Sinc,
    My apologies, I found the error in some bad lisp code that was accidentally placed.

MJP

[mjfarrell]

Sinc,
    My apologies, I found the error in some bad lisp code that was accidentally placed.

MJP

a bad  LISP he says....

[sinc]

    My apologies, I found the error in some bad lisp code that was accidentally placed.

No problem.  I've had similar things happen.  It can be easier to find such things once you know someone else can't reproduce the issue.