Dan Nigrin

Anyone have information on what could be causing my standalone app to report "Error 193 loading external XXXXX" in the Max Console on a Windows machine, where XXXXX is one of several 3rd party externals I'm using?

The app works correctly on many different machines, it's just this one that's giving this error. The OS is Windows 10 64-bit, the app was built with Max 8 so is 64-bit, and all of the above externals are also 64bit, and as I said working fine on other machines. 

The app works correctly on many different machines, it's just this one that's giving this error.  The OS is Windows 10 64-bit, the app was built with Max 8 so is 64-bit, and all of the above externals are also 64bit, and as I said working fine on other machines.  

Stumped!

Anyone have information on what could be causing my standalone app to report "Error 193 loading external XXXXX" in the Max Console on a Wind

error-193-loading-external

I using the printer machine but In this, many error will occur which is really important for us. And which is harmful to the printer. Then, I go to the technical support to solve all the problem which is really good for us. I can also go to the 

I using the printer machine but In this, many error will occur which is really important for us. And which is harmful to the printer. Then,  I go to the technical support to solve all the problem which is really good for us. I can also go to the printer repair near me to solve all the error problem. 

Probably missing older vcredistributables DLLs.

Had same issues once, copying msvcp and msvcr DLLs

100, 110 and 120 into standalone folder fixed it.

Probably missing older vcredistributables DLLs.
Had same issues once, copying msvcp and msvcr DLLs
100, 110 and 120 into standalone folder fixed it.



Thanks - and yes this is my line of investigation so far. It's a standalone that I distribute to others, and I bundle the 120 (Visual Studio 2013) files together with my app, so I know it's not that one. I've started testing sending the user the 140 file (Visual Studio 2015) first, if that doesn't work will try the others as well.... For my own help when I refer to this thread in the future (!), this is a very good thread in terms of info mapping the number of the files to the VS version: 

https://cycling74.com/forums/standalone-missing-msvcp120-dll-on-windows

Thanks - and yes this is my line of investigation so far.  It's a standalone that I distribute to others, and I bundle the 120 (Visual Studio 2013) files together with my app, so I know it's not that one.  I've started testing sending the user the 140 file (Visual Studio 2015) first, if that doesn't work will try the others as well....   For my own help when I refer to this thread in the future (!), this is a very good thread in terms of info mapping the number of the files to the VS version:  https://cycling74.com/forums/standalone-missing-msvcp120-dll-on-windows 