Forum Discussion
Mosel does not see a DSO module provided by a C++ application - could Windows security be the problem?
We have an old C++ application that uses Xpress optimizer internally. It works by calling Mosel using `XPRMrunmod()`. In addition, it uses callbacks defined in the C++ application via `XPRMdsofct`, ...
Once more thanks for the answers.
I have updated the return-value checking of XPRMregstatdso() accordingly.
I have also found that we are actually setting `MM_NICOMPAT` to 4007000 for 32-bit builds.
This corresponds to version 8.3 or 8.4, but the user has reported the problem also with 32-bit Xpress 8.6, which would seem to exclude the compatibility issue as the source of the problem. (Though I cannot be sure that they are running the versions they say they use - I have therefore added reporting of XPRMgetversion() and XPRMgetversions(2) to the latest build...)
By the way, should I be using XPRM_NICOMPAT instead of MM_NICOMPAT? As far as I can see, XPRM_NICOMPAT is used only in one place and that is to defined MM_NICOMPAT if it is not defined (in xprm_ni.h)
