as mentioned in my last sentence: I do know this script, but I would rather understand what the underlying problem is than to just run some random script.
(edit)
The trick in that script seems to be to patch those DLLs. Interestingly, I see no documentation on that anywhere. I did not see anyone suggesting this on the forums. The IDS filnames are not something that’s commonly found discussed a lot; certainly not with this applied patch.
Each of the IDS dlls is checked for offset 0x3C (e_lfanew), which gives us the location of the actual start of the NT header. Then we write zero in the place where the PE-Header plus 40 bytes, according to ImHex’s patterns, this is the majorOperatingSystem field. We seem to be overwriting this with . That’s where I was wrong. I looked at the wrong offset!0 instead of 6 (likely meaning Windows Vista and later)
I performed these changes manually, but I’m still getting the errors regarding ids_peak_ipl.dll while starting TD.