CAD Forum - tips, tricks, discussion and utilities for AutoCAD, Inventor, Revit and other Autodesk products [www.cadforum.cz] ARKANCE | CONTACT - CZ | SK | EN | DE
RSS channel - CAD tips RSS tips
RSS discussions

Discussion Discussion forum

?
CAD discussions, advices, exchange of experience

CAD Forum - Homepage CAD discussion forum - ask any CAD-related questions here, share your CAD knowledge on AutoCAD, Inventor, Revit and other Autodesk software with your peers from all over the world. To start a new topic, choose an appropriate forum.

Please abide by the rules of this forum.
This is a peer-to-peer forum. The forum doesn't replace the official direct technical support provided by ARKANCE for its customers.
How to post questions: register or login, go to the specific forum and click the NEW TOPIC button.
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Topic ClosedNETLOAD in AutoCAD 2012

 Post Reply Post Reply
Author
John Connor View Drop Down
Senior Member
Senior Member


Joined: 01.Feb.2011
Location: United States
Using: AutoCAD 2018
Status: Offline
Points: 7175
Direct Link To This Post Topic: NETLOAD in AutoCAD 2012
    Posted: 19.Aug.2011 at 11:47
Find and open your acad.exe.config file (can be opened with Notepad) and see if it looks like this:

<configuration>

  <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0"/>
  </startup>

<!--All assemblies in AutoCAD are fully trusted so there's no point generating publisher evidence-->
   <runtime>       
    <generatePublisherEvidence enabled="false"/>   
   </runtime>
</configuration>
"Humans have a strength that cannot be measured. This is John Connor. If you are reading this, you are the resistance."

<<AutoCAD 2015>>

Back to Top
KSmedes View Drop Down
Newbie
Newbie


Joined: 09.Aug.2011
Location: United States
Using: AutoCAD 2010,2011,2012. Revit 2011,2012
Status: Offline
Points: 10
Direct Link To This Post Posted: 18.Aug.2011 at 22:37
Thanks John.  Here is the deal.  We loaded AutoCAD per specs. On our Windows 7 machines we found that we needed to have .NET framework 4.0 to get this particular .dll to run. Not sure if it would be different on xp machines. Here is the mind boggler. We have a couple of XP machines that work and several that don't.  We have tried to mimic everything on the ones that work and no go. When I type in netload and browse to the folder and select the .dll it doesn't even give me an error just acts like I didn't even enter the command. I think I am running out of options and may be forced to us only windows 7.
K Smedes
Back to Top
John Connor View Drop Down
Senior Member
Senior Member


Joined: 01.Feb.2011
Location: United States
Using: AutoCAD 2018
Status: Offline
Points: 7175
Direct Link To This Post Posted: 18.Aug.2011 at 17:46
Windows XP?  Did you keep your version of Windows current with all service packs and updates?  Were you ever prompted to install the Windows Imaging Component (WIC)?
"Humans have a strength that cannot be measured. This is John Connor. If you are reading this, you are the resistance."

<<AutoCAD 2015>>

Back to Top
John Connor View Drop Down
Senior Member
Senior Member


Joined: 01.Feb.2011
Location: United States
Using: AutoCAD 2018
Status: Offline
Points: 7175
Direct Link To This Post Posted: 18.Aug.2011 at 17:32
Personally I think you should be using .NET Framework 3.5 Service Pack 1 not 4.  I think your computer expert is ill-informed.  Anyway, it does not surprise me that he pointed the finger at AutoCAD.  You do know .NET Framework is a Microsoft product right?

I asked you if you followed AutoDesk's recommended advice not your so-called software expert.  There is a BIG difference between the two.


Edited by John Connor - 18.Aug.2011 at 17:33
"Humans have a strength that cannot be measured. This is John Connor. If you are reading this, you are the resistance."

<<AutoCAD 2015>>

Back to Top
KSmedes View Drop Down
Newbie
Newbie


Joined: 09.Aug.2011
Location: United States
Using: AutoCAD 2010,2011,2012. Revit 2011,2012
Status: Offline
Points: 10
Direct Link To This Post Posted: 18.Aug.2011 at 17:15
Yes we followed the procedure recommended by the software export. He told us it was a CAD issue not a microsoft issue.
K Smedes
Back to Top
John Connor View Drop Down
Senior Member
Senior Member


Joined: 01.Feb.2011
Location: United States
Using: AutoCAD 2018
Status: Offline
Points: 7175
Direct Link To This Post Posted: 18.Aug.2011 at 12:09
Microsoft has a specific procedure for installing .NET as I am sure you are aware.  Did you follow that procedure exactly?
"Humans have a strength that cannot be measured. This is John Connor. If you are reading this, you are the resistance."

<<AutoCAD 2015>>

Back to Top
Bilikier View Drop Down
Newbie
Newbie


Joined: 18.Aug.2011
Location: United States
Using: AutoCAD2012
Status: Offline
Points: 4
Direct Link To This Post Posted: 18.Aug.2011 at 08:56
Originally posted by KSmedes KSmedes wrote:

We have systems running in windows XP that are not recognizing the "NETLOAD" Command. We have tried to update the NET 4 and that did not help. We have one XP system that loaded it fine but have not been able to do it on other machines? Any thoughts?
Why do not you take your computer to the software expert... He can easily install that software into your computer....!! May be there is some manufacturing problem with the software or it may not be matching with the compatibility of the hardware of your system. 
Back to Top
KSmedes View Drop Down
Newbie
Newbie


Joined: 09.Aug.2011
Location: United States
Using: AutoCAD 2010,2011,2012. Revit 2011,2012
Status: Offline
Points: 10
Direct Link To This Post Posted: 15.Aug.2011 at 21:12
We have systems running in windows XP that are not recognizing the "NETLOAD" Command. We have tried to update the NET 4 and that did not help. We have one XP system that loaded it fine but have not been able to do it on other machines? Any thoughts?
K Smedes
Back to Top

Related CAD tips:


 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0,148 seconds.