Recommended Posts

This may be miles off, but the call system is different in 4053, also the cool stuff is now in milrender.dll. It also has a different launch system, maybe it's just activated by calling it once. The other thing is no-one has mentioned the WmgExecute function, one of sbctl's exports, it might do somthing with the right arguments??

This may be miles off, but the call system is different in 4053, also the cool stuff is now in milrender.dll. It also has a different launch system, maybe it's just activated by calling it once. The other thing is no-one has mentioned the WmgExecute function, one of sbctl's exports, it might do somthing with the right arguments??

yes, I have also noticed that!

WmgExecute seems quite interesting, but I guess only Microsoft know the right arguments :crazy:

Michael

it seems there are few mistakes - ex. "Creat" - "Create" and other small mistakes, but because of them some of the functions can't start. also many of the functions in milcore.dll are missing [tried by replacing the original mil's with the included in the package]. and when i try to execute the mil.bat file, i only get "Error reporting" window for every runll32 call. so, i think it should work on #4051. if you can activate dce, i'd be glad to show us the results [screenies or something else].

Edited by fr1sk3y
I might be getting blind, buit take a look at where the time is - doesnt it look a bit transparent??

Id say thats part of some kind of DCE effect - am I right??? just installed LH4053...betasirc..

Take a look and give me some opinions

I'm sorry to disappoint you, but I don't see any transparency in this screenshot! :no:

Michael

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.