Results 1 to 5 of 5

Thread: Fatal error, maybe caused by recent change in WhipArc

  1. #1
    Member
    Join Date
    2005-02
    Posts
    17
    Login to Give a bone
    0

    Angry Fatal error, maybe caused by recent change in WhipArc

    Hi guy,
    Recently I have my Autocad LT2002 just shut down by itself, or come up with the message:
    "Unhandled access violation writing 0X8055d exception at 332becdbh."
    then it shutdown.
    Anybody out there can help me with this?
    ( I must say that the software started to go wrong after I have change the :' whiparc:0' to ' whiparc:1' . Is this the case? and i have 5 drawings open at the time.)
    Any help will be appreciated.
    Last edited by huuthu_nguyen; 2005-04-04 at 10:07 PM.

  2. #2
    The Silent Type Mike.Perry's Avatar
    Join Date
    2000-11
    Posts
    13,656
    Login to Give a bone
    0

    Default Re: Fatal error, maybe caused by recent change in WhipArc

    Hi

    What happens if you set system variable WhipArc back to 0 (Zero)?

    Just for your info, I have experienced one or two issues / problems in the past when I've had WhipArc set to 1 (One). Changing it back to 0 (Zero) always cured these issues / problems.

    Have a good one, Mike

  3. #3
    Member
    Join Date
    2005-02
    Posts
    17
    Login to Give a bone
    0

    Default Re: Fatal error, maybe caused by recent change in WhipArc

    Hi Mike,
    Thanks for your suggestion. It all go back to normal now. I guest I will not do "whiparc" again.
    Greatly appreciated.

  4. #4
    AUGI Addict Glenn Pope's Avatar
    Join Date
    2001-05
    Location
    Austin, TX USA
    Posts
    2,201
    Login to Give a bone
    0

    Default Re: Fatal error, maybe caused by recent change in WhipArc

    Am I the only who thinks Autodesk needs to remove whiparc from autocad. Every computer I have seen, with every version of AutoCAD, would crash several times with whiparc turned on. There is defiantly a bug in the routine. Yet Autodesk has nothing in its knowledge base (that I have found anyway) about it. Other then to turn it off if you experience slow down.

    Ok, off my soapbox.

  5. #5
    The Silent Type Mike.Perry's Avatar
    Join Date
    2000-11
    Posts
    13,656
    Login to Give a bone
    0

    Default Re: Fatal error, maybe caused by recent change in WhipArc

    Hi Glenn

    I totally agree with you, but personally I would like to see Autodesk fix it properly or implement something else (ViewRes is so out dated).

    Being the **** retentive I am, the below is the closes Autodesk come to admitting there is a problem with WhipArc (I'm sure you found this one) -

    ID: TS40613 - Object snaps fail to work with block objects

    Mike

Similar Threads

  1. Replies: 3
    Last Post: 2013-03-27, 05:41 PM
  2. 2012: Revit mep: Export to dwg fatal error. Sync fatal error as well
    By Scottybill in forum Revit MEP - General
    Replies: 5
    Last Post: 2012-11-30, 09:47 PM
  3. Creating shaft caused floor finish to change???
    By thomas.denney836893 in forum Revit Architecture - General
    Replies: 6
    Last Post: 2011-06-22, 03:04 PM
  4. Replies: 20
    Last Post: 2008-07-09, 03:22 PM
  5. Replies: 2
    Last Post: 2005-11-04, 01:46 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •