Mystery Error

[djackson.71012]

Has anyone ever heard of this error "error: bad argument type: stringp nil"

it doesnt seem to be causing any problems in AutoCAD, but I get this ever with ever drawing I open up.

If you have ever heard of it, and know how to get rid of it....please let me know....our CAD guys are stumped..

thanks alot

D.Jack!

[BrenBren]

This is from a KB article

This error occurs when the Start in folder for the shortcut that starts AutoCAD is a Universal Naming Convention location (UNC path) on the network. The following example shows UNC paths used in the shortcut properties:
Target = \\bilbo\apps\acad\acad.exe /c c:\acad2000

Start in = \\bilbo\apps\acad

One solution to this problem is to map a drive to the AutoCAD folder, and then change the Start in folder to the mapped drive.

To map a drive in Microsoft® Windows®:

1. In Windows Explorer, click Network Neighborhood and browse to and select the AutoCAD folder on the network drive.
2. Right-click the AutoCAD folder and choose Map Network Drive from the shortcut menu.
3. Assign an unused drive letter (For example, T), and then choose OK.

To change the Start in folder for the shortcut that starts AutoCAD:

1. On the Windows desktop, right-click the icon for the shortcut that starts AutoCAD and choose Properties from the shortcut menu.
2. On the Shortcut tab, change the Start in location to use the mapped network drive. In the following example, T is the drive that was mapped from the AutoCAD folder on the network: Start in = T:\
   
3. Choose OK.

You should now be able to start AutoCAD without encountering the error.

[mjfarrell]

You have something in your start-up that loads
some old piece of LISP programming that is not happy.

http://usa.autodesk.com/adsk/servlet...linkID=2475323

[Glenn Pope]

It looks like you have a lisp routine that is loading and it has an error in it some where. You'll need to remove each routine one by one and restart AutoCAD tell you don't get that message. Which ever was the last routine you removed will be the one with the error.

Then when you find the one with the problem, you can post it in the lisp forum to see if anyone can figure out the error.

[djackson.71012]

I really hope this works.....thanks alot for your quick response!!!

[BrenBren]

Let us know if it works.