Fix AutoCAD 2010 Fatal Error: Unhandled Exception e0434f4dh

Awesome link to fix an annoying problem. Thanks to the contributor


Fix AutoCAD 2010 Fatal Error: Unhandled Exception e0434f4dh1
Ricky Williams March 09, 2011 Apps, News
I was having trouble with this Fatal Error: Unhandled Exception e0434f4dh in AutoCAD 2010. When it happens AutoCAD prompts you to save the drawing and then crashes, usually on startup so there is no drawing to save anyway. Well hopefully the fix can save other people the time of re-installing AutoCAD, which is not a fun thing to do. So read on to save yourself some time.

I searched the web for the error and luckily there were a ton of forums found, but I found the solution at the first one I visited. You can read through the forum thread on Autodesk here if you like. The fix does involve editing the registry, so as usual I must warn that editing the registry can have dire consequences. If edited incorrectly your computer could become highly unstable or unable to boot at all requiring a reload of Windows. You can however backup the registry to be able to restore it and fix any damage you may do, you can find instructions on how to do that here.

Shall we begin, the fix requires a very quick edit of the registry. Once you’ve backed it up using the method above, follow these steps:

In the registry editor go to the following registry key
HKEY_CURRENT_USER\Software\autodesk\AutoCAD\R18.0\ACAD-8000:409\WebServices\CommunicationCenter
In the right pane of the registry editor you will find a key ”LastUpdateTimeLoWord” with a dword value of 4be447d0
Double click this key and type in the value “0″ that is a zero and you type it without the quotes and hit Enter
The key should now have the value 00000000 displayed
Exit the registry editor and the change takes effect instantly

You are now able to open AutoCAD 2010 and work just like before, Happy drafting.

WisDOT Reports

all the reports are in the reports.dll file.

Access the reports via the "netload" command

or add to registry.

See following file for help.

"C:\ProgramData\Autodesk\C3D 2010\enu\Data\Reports\Net\USWI\WisDOT Reports - Readme.pdf"

standard cad configuration location

"C:\Users\sdebaker.RELEE\AppData\Local\Autodesk\LandXML Reporting\RepGenSettings.xml"

Import styles in Civil 2010

To import all styles from one drawing or template to another in 2010, simple create a new point style. Select the marker tab, check Use AutoCAD BLOCK symbol for marker, right click in block area and select browse. Set dwt or dwg at the bottom and select source. Click ok and all styles are imported to the drawing. The only difference is this does not override existing styles that already exist in the drawing.

Found at http://civil3dguru.blogspot.com/2010/06/undocumented-aec-style-commands-civil.html

Wisconsin 1938 Maps

Here is the link http://maps.sco.wisc.edu/WHAIFinder/

Rename Blocks and other stuff

before copying a block(s) with duplicate name use the "ren" command to rename all the blocks, if applicable you can use the "Rename to" to add a prefix on multiple blocks.
example:
existing block name "TREE1"
rename to "9-12-01_*"
this will create the new block name as "9-12-01_TREE1"

If the wildcard is used you can rename all the blocks and preserve the original name.

CTB vs STB

http://www.caddmanager.com/CMB/2009/08/cad-standards-ctb-vs-stb/

Land XML US Foot

Problem:
Some applications that are set to use US survey Foot will honor the “foot” value in the LandXML. The application will convert the coordinates when reading the file from International Foot to US Survey Foot, which results in the coordinates having a different value as to the original coordinates. The application may or may not warn it is going to convert the coordinates.

This is not a wide spread issue because CAiCE, InRoads, SurvCE and Trimble currently does not convert the coordinates when reading LandXML files. Known applications that do honor the “Foot” value in LandXML file is Leica Office Geomatics and Land Desk Development.

One should always check coordinate values when importing data to verify the coordinates have not change.

Solution:
Edit LandXML file with text editor and modify the linearUnit="foot" to linearUnit="ussurveyfoot”. Be very careful not to change anything in the file except to modify the text “foot” to “ussurveyfoot”.

If you are working with external customers I would suggest always modifying the LandXML file and set the units to US Survey Foot. Currently InRoads XM allows you to set the linear units when you create the LandXML file. Make sure to always check the setting because it defaults to International Foot.

Mouse freezes up after bringing in points

cui
rollover
cogo points
uncheck - STYLE