error: malformed string on input

[Bear31831]

I keep getting this message when I load each drawing. How do I get rid of it? How do I even find out how to find it? I really don't know if it is having any affect or not, but would like to get rid of it.

Thanks for any help.

[jaberwok]

It sounds as if you have a bad lisp routine running every time you open a drawing.
Check for acad.lsp / acaddoc.lsp files and look there.

[mvsawyer]

If you can't find it there, look into MNL files loaded with your menus. Not there either, check in the Startup Suite from APPLOAD and check the lisp files loaded there.

[jdcincy]

It sounds as if you have a bad lisp routine running every time you open a drawing.
Check for acad.lsp / acaddoc.lsp files and look there.

I have this same error and it is causing some of my lisp routines not to load. I see in my loaded applications acad.mnl, acad2014.lisp and some others are ghosted (text not as bold as other text). Im assuming that means those files are not loading. Does that mean I should follow the paths listed and remove those files? I also see some .dll, .fas, .arx and .crx files that are ghosted in load manager should all these be removed?

[mvsawyer]

The grayed out files are loaded. Not sure why some are gray and some are not. They don't need to be removed. If some of your lisps are not loading then it's a good chance that whatever file that those lisp routines reside in, is the file that contains the bad lisp.

[jdcincy]

how do you know what lisp is bad?

[mvsawyer]

Count parentheses.

But seriously, they can be hard to track down. The lisps not loading, are they from a compilation of lisp files or individual .lsp?

[jdcincy]

individual, the one compilation lisp works every time. but I have used these routines for 10 yrs and have never had a problem. Until I got 2014, now only a handful of my lisp routines will automatically loads with every drawing.

[mvsawyer]

Ok, How are you auto loading them?

[mvsawyer]

If it's easy you can try dragging and dropping the files into autocad to find the one that is causing the error.