Autodesk Technology Managers Forum
Share your knowledge, ask questions, and engage with fellow CAD/BIM Managers.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Getting lockups on File->Oopen in 2009 on win 7 32 bit system

4 REPLIES 4
Reply
Message 1 of 5
JamesMaeding
582 Views, 4 Replies

Getting lockups on File->Oopen in 2009 on win 7 32 bit system

While this is a 2009 question, I have a feeling this applies to all acad versions on win 7.

Several times a day, when I go to open a file, autocad locks up the entire computer.

I have to hit the power button to unlock.

There does not seem to be a pattern, it happens on different folders and files.

I cannot check task manager as everything is locked hard.

Its a new dell system, I do not expect it would be a driver issue or anything.

My guess is its some conflict with the windows shell, and Autocad's open dialog box.

Thx for any ideas in advance.


internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties

4 REPLIES 4
Message 2 of 5
Anonymous
in reply to: JamesMaeding

Are the files local or on a network?

Message 3 of 5
JamesMaeding
in reply to: Anonymous

well, the Open dialig box shows the desktop and all network drives, so its a mix.

I've seen acad act really slow when you have some invalid printer, or shortcut that points to nothing, but the user experiencing this did not have time to set anything fancy up, it happened as soon as he got the machine a couple weeks ago.

 


internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties

Message 4 of 5
Anonymous
in reply to: JamesMaeding

If they copied some settings over from a previous computer, there may be directory conflicts between the versions, such as drive letters not mapped the same.

Message 5 of 5
JamesMaeding
in reply to: Anonymous

may be, but I am seeing enough odd things happen on my win 7 64 bit system that it makes the items connected to the windows shell as suspect.

For my win 7 64 bit machine, I can replicate an acad lock up (not whole computer though) by pasting a path into the lisp (getfiledlg...) file dialog box.

Why? I would bet some little function deep down is not compatible with 64 bit.

But not sure how that plays in with win 7 32 bit.

 

I don;t think we can solve this unless someone else sees the same behavior, and we can compare notes.

The worst thing is the lockups are random, so I cannot do all the normal troubleshooting things like unmap network drives.

very frustrating since I don't know if a rebuild will even help...


internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Administrator Productivity


Autodesk Design & Make Report