EasyGerb is an AutoCAD ARX app, the source code has been stable for over 12+ years, and the only real changes moving forward have been additional security/anti-virus protocols, and other measures introduced in each new AutoCAD release (new c++ library requirements, etc.). All EasyGerb binaries are also code signed using our corporate certificate to ensure the integrity of the executable binary files we produce.
Here's a list of open/existing AutoCad vulnerabilities, https://www.cvedetails.com/vulnerability-list/vendor_id-3855/Autodesk.html
If any crashing occurs, here's the most import steps to follow:
1. Enter your Proxy details before activation, https://support.numericalinnovations.com/support/discussions/topics/14000018592
2. Follow Autodesk recommendations (such as assign EasyGerb to a Trusted Path, etc.),
If problems persist try using our stand alone product ACE Translator 3000. ACE is an independent software program that performs the "exact same conversion" as EasyGerb except you will import your AutoCAD DWG or DXF and export as Gerber. It also does much more than EasyGerb. Here's some more information about ACE, https://www.numericalinnovations.com/collections/ace-translator-3000
Note: When purchasing our Numerical Cloud subscription, you get ACE and EasyGerb together; giving you the ability to simultaneously use either conversion solution. https://www.numericalinnovations.com/products/monthly-plan
Thanks again.
Simon
Simon Garrison
The problem is that trying to activate EasyGerb after loading it in AutoCAD causes AutoCAD to crash with a fatal write-related error. We’ve tried a number of things to fix the problem, including removing any existing EasyGerb .cfg files from the user’s folder, and ensuring that users are given write access to any AutoCAD and Numerical Innovations folders in UAC. Researching similar errors online hasn’t been particularly fruitful, and Event Viewer just shows that AutoCAD encountered an error and closed. We eventually reached out to Autodesk and Numerical Innovations for help. A technician from Autodesk had a remote session with us using a laptop from one of the users affected by this issue, but was unable to figure out the problem.