Small Update
My starter reads the values from the engine starter like the progressbar etc and displays them on the loading screen.
Even outside of lite-c acknex fights back...it is a witch work to get the percentage of the "8bit" old school starter window. it only works with Tricks
(Width measurement) because Conitec used a custom class "class_WrProgress - the most efficient way possible".Now iam trying to do the same thing for the text, so i can directly read the start infos like cancel etc to react even more stable to engine start events.
edit:
I can really only chuckle at this point... everything in Acknex always puts up a fight XD ...even the measly starter text from the custom "class_wrTextF" can't be read out via message hook or RAM sniffing...crazy XD
...okay, so the only option left is "acklog sniffing." Thank god i can get the percentage from the starter...
edit
If "Diagnose" ist checked in the starter it shows the starter text on the loading info. I gave up on class_wrTextF and grab it from acklock.txt instead.
edit
Danger! I have rewritten the logic. my starter is now in control of the exec. i thought what happens if a faster pc want to go in fullscreen while the old engine just going out of fullscreen?
Thats not good

...so my starter shows the loadings screen, waits for the process to finish plus a few seconds and then starts the new engine.
another edit: Ok it works now. But now im going back to do the exec from engine

...but this time i simply switch in window mode before exit.
Since i can feed and show a progress bar from engine starters progress i "hide" the starter window in window mode on swap via -nwnd (so its still in the task bar if user wants to see details. In "diagnose mode" it shows acklog text like i mentioned).