Windows API calls = problem


    Sep 03 2006 | 10:14 am
    We have a Windows code to retrieve some hardware informations. This code
    is working well as an .exe (or any other form) and is compiling fine
    when called from / put inside an external. But it doesn't return the
    expected values, or worse, it often returns NILL or 0, when called in
    Max. We suppose, after wasting hours, that Max prevent the calls to
    ntdll.dll, and also the use of windows.h. As explained p324 of the
    WritingExternals.pdf, if the usage of Windows API seems to be
    compromised, we should ask you...
    In the need of your answer,
    best regards
    f.e + m.o
    --
    f.e chanfrault | aka | personal computer music
    > >>>>>> http://www.personal-computer-music.com
    > >>>>>> |sublime music for a desperate people|

    • Sep 03 2006 | 10:22 am
      Sorry that you're having trouble. I've written plenty of externals
      which use windows.h + various Windows API calls, so I know that it's
      possible. I'm afraid you may need to be more specific (e.g. send
      source code and project files so that someone can determine what
      isn't set up properly).
      jb
      Am 03.09.2006 um 12:14 schrieb f.e:
      > We suppose, after wasting hours, that Max prevent the calls to
      > ntdll.dll, and also the use of windows.h. As explained p324 of the
      > WritingExternals.pdf, if the usage of Windows API seems to be
      > compromised, we should ask you..