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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
