LT Suite has been an issue reading paths?

[Anonymous]

My (tomwin7) drafting  computer has been an issue reading paths for a few weeks now.

I repaired my autocad program thinking it was the issue, but it is not.

I had no issue before with opening drawings direct from the folders, but now I get errors.

One is a user account control error1.jpg

The second is a There is a problem sending this command to the program, error2.jpg

Another part of this Issue is the shortcuts to my second drive disappear or up until I changes to some new ones, it would X out the drive icons I put on the screen.

I am starting to think this may be a motherboard issue as it mostly happens on my E: drive, but it gives the same errors if I try to open a drawing on my C: drive.

One thing I was able to do was drag and drop a DWG into a drawing I am working on, That will no longer happen. It worked in the past.

Any Ideas?

[pendean]

1. Turn off or disable Windows UAC.
2. Read this, itm may help: http://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Unable-...
3. E drive is what/where?
4. INSERT ommand does wonders in fixing problmatic DWG files.

[Anonymous]

UAC was disabled. That stopped the first error message. The second was
stopped by changing the startup from acadlt.exe to autocad dwg launcher,
Must be a change in Inventor LT Suite.



I will not give up the drag and drop I have been using for the last 10 years
to insert. Been using it for blocks. In Fact it worked after installing
Version 2015.



This computer has 2 drives, one for system files and programs, the other for
drawing storage. The Inventor application is not a network version, it is a
stand-alone install and runs as administrator.



Tom Visocky



Del Zotto Products of Mn, Inc.

1900 County Road 1

Wrenshall, MN 55797

Phone: (218) 384-3066

Fax: (218) 384-3088

Email: tom.v@delzottoproducts.com



Check out our products at http://www.delzottoproducts.com

[pendean]

drag-n-drop is an INSERT function, regardless of the actual method you use: methodology is irrelevant to my comment. good to know you found fixes.