eLockViolation

eLockViolation

john.uhden
Mentor Mentor
5,223 Views
20 Replies
Message 1 of 21

eLockViolation

john.uhden
Mentor
Mentor

I am setting up my clent's laptop, which he claims "automatically" upgraded itself from Win7 to Win10.  He thought his AutoCAD 2002 would not run, but it does.  That's the good news.

The bad news is that programs that I wrote years ago, that have run flawlessly in Win2K, XP, and Win7 are now experiencing elockviolations ("LWPOLYLINE creation failed ... error:  C#0000005 ...") or something like that on his laptop.

 

I presume that there's something in my code that is causing it, but I have no idea where to look first.  Are there typical situations that cause this error in AutoLisp?  The only thing special is that it's wrapped in a VLX.

 

Wait.  I just checked my code.  The "LWPOLYLINE creation failed" message is built into my program to report an entmake failure.  Might the entmake including a new layer be part of the problem?  It never has before.  Or is 2002 doomed to not work correctly in Win10.

 

The *error* function does contain (command "_.Undo" "_End").  I wonder if converting to some Visual Lisp would circumvent this issue.

John F. Uhden

0 Likes
Accepted solutions (1)
5,224 Views
20 Replies
Replies (20)
Message 21 of 21

john.uhden
Mentor
Mentor

IT'S FIXED!!

 

One of you whiz kids pointed me to Longbow.  I installed it on my client's Win10 laptop, reinstalled AutoCAD 2002, and no more errors.  YAY!

 

Thank you all for your tireless effort in helping me out.

 

BTW, I did try excluding acad.exe from the DEP settings before installing Longbow, but to no success.  In fact AutoCAD didn't even make it through acaddoc.lsp without crashing.  So Longbow must be pretty smart stuff.  Thank goodness!

John F. Uhden

0 Likes