Forums > Dev

Error 14001 loading external

January 15, 2009 | 8:55 am

I’ve seen a couple people have this 14001 error trying to load an external, but haven’t found a proper fix.

I’m using Visual Studio 2008 and trying to compile the TUIO Client from reactivision I can compile it, but when I try to load it into max, I’m getting a 14001 error. The binary version works just fine, but when I compiled a version it doesn’t and the output sizes are different.

Are there any special VS parameters that need to be changed to get this linked correctly and working? There’s a Visual Studio project within the TUIO Client external (above) that I’m using to compile the external.


February 16, 2010 | 11:43 pm

has any one used TUIO client on Windows 7 to use reactivision and max?

My patch works properly in OSX but when I try in windows, I can’t even open TUIO client objects although I have imported them in my external folders …

any idea what the problem could be?


February 17, 2010 | 12:04 pm

I would start by making sure that Max can find any DLL dependencies. The best place for these is in the "support" folder in your Max application folder.

When someone asks about the 14001 error it usually ends up indicating that the Microsoft C Runtime DLL cannot be found (and that the external object is compiled to link against it).

The MSVC DLL is installed by Microsoft’s dev tools, so it’s easy for an external developer to not notice the problem on their own machine. In the Max 5 SDK there are examples that link against an alternative "Max C Runtime". An alternative approach used by the Jamoma project is to link against a static version of the MSVC rather than the dynamically loaded version.

I hope this helps.

Viewing 3 posts - 1 through 3 (of 3 total)