yeah I dont see how loadlibrary could achieve what the engine startup couldn't but hey I have seen weirder ..

this is pretty odd behaviour , the only thing I could think of was the standard libraries weren't staticly linked and therefore required the runtime libraries available for dynamic linking ..

the visual studio service packs includes runtimes
for crt mfc etc etc ,so if uts not in there then masterq32 is on to the answer for sure.

like to know what went wrong too if you solve it