Why run 32bit AutoCAD on 64bit Windows


AutoCAD R13 | AutoCAD R14 | AutoCAD 2000 | AutoCAD 2000i |AutoCAD 2002 | AutoCAD 2004 | AutoCAD 2005 | AutoCAD 2006 | AutoCAD 2007

Users of these really old AutoCAD versions have literally been using them for over a century, and because of that fact moving to a new version of AutoCAD is extremely disruptive for them. Being able to old versions of AutoCAD on new versions of Windows restores efficient workflows and concepts.

AutoCAD installation error messages solved!

  • Wrong OS. AutoCAD supports Windows NT 4.0, Windows NT 5.0, Windows 95 and Windows 98
  • This app cannot run on your PC

These blocking AutoCAD setup issues are completely solved by using our Longbow Converter solution.

Significant 3rd Party ObjectARX, VBA, VB6 investment

Some users can also run into issues where they have significant investments in 3rd party ObjectARX, LISP, VBA or VB6 applications that only run on their existing version of AutoCAD.

Our Longbow Converter solution allows them to be installed alongside these old versions of AutoCAD once again.

 



AutoCAD 2008 | AutoCAD 2009 | AutoCAD 2010 | AutoCAD 2011 |AutoCAD 2012 | AutoCAD 2013 | AutoCAD 2014 | AutoCAD 2015 | AutoCAD 2016 | AutoCAD 2017 | AutoCAD 2018 | AutoCAD 2019


AutoCAD installation error messages solved!

Users of these versions of AutoCAD are generally restricted from installing their AutoCAD with messages like

  • This operating system is not supported by AutoCAD
  • You cannot install this product on the current operating system
  • You are attempting to use this 32-bit installer on a 64-bit operating system
  • This is a 32-bit AutoCAD ‘version’. It cannot be installed on 64-bit Windows

All solved by using our Longbow Converter solution…

Slow VBA Performance

Other users are impacted by severe performance issues when running their VBA code on 64bit AutoCAD. You may not even be able to run your VBA code on 64bit AutoCAD. This is because AutoCAD VBA runs in a completely separate executable (exe), away from AutoCAD on 64bit Windows, making it almost 1200 times slower than AutoCAD VBA running 32bit AutoCAD. Installing 32bit AutoCAD solves the problem and restores performance… This issue is solved by using our Longbow Converter solution.


Significant 3rd Party ObjectARX, LISP, VBA, VB6 investment

Some users can also run into issues where they have significant investments in 3rd party ObjectARX, VBA or VB6 applications that only run on their existing 32bit version of AutoCAD.

3rd party extensions like

  • Bentley Road, Bentley Inroads, Site Design, Bentley MX, Bentley WaterCAD, ProSteel 3D 
  • Microvellum Cabinet Maker, Smartlister, Vitruvian Built, SmartMachining, CGSurvey
  • Stabiplan’s StabiCAD and StabiBase, AutoStage Pro, EBOM Electrical, ER Mapper,
  • Softdesk AEC, Softdesk Building Systems, Softdesk Civil/Survey,  GE XA21 DBF
  • YFCAD InteriCAD 6000 7000 T5, CADCode/ACAM, Accubid CADLive, Keytrix, AutoTURN
  • Tyco Sprinkcad, SurveyMBS, Flairbase Amine, AutoNest, Easy Hatch, ProCAD, Mitek WoodEngine,
  • 20-20 CAP Studio, 20-20 SymbolSource for Allsteel, BlueCielo InnoCielo Meridian
  • CADKON, C & G Surveying software for AutoCAD, PAMCAD, FastrackCAD, EDMWire
  • GlobalCad Toolbox LT, ELCOVISION, APS for Architecture, Carson Survey, 3DConstructor
  • Mensch und Maschine, Basepoint, Softech PLM and RMData AutoCAD based products  
  • Mentor Graphics VeSys, faciliCAD, BOSS RiverCAD Pro, AutoCAD OEM, SOFiCAD (all SOFiSTiK AutoCAD plugins), and more!

Solved by using our Longbow Converter solution.

Leave a Reply

Your email address will not be published. Required fields are marked *