I havenít encountered the packed script itself yet, only the supporting libs and the bound files, during runtime. Nowhere inside %TEMP%, not in a recognisable format anyway.
But what we need is not the script but the bound files, well, in that case I have some bad news (I think). Way before I installed the strace implementation or Process Explorer, I tried to figure out what was in view for the script, and did a system("dir"); ó I got the files from the directory where I had started the EXE from and not where the unpacked script mysteriously and temporarily lives. And the bound files are nowhere to be seen there unfortunately (I havenít re-checked, but I think I would have noticed if there had been .dll files where normally there isnít a single one), only in the previously discussed PID-labeled directory in %TEMP%. So Iím afraid Iíll need that absolute path.