[01:52:27] &lt;<font color="#0000C0">Wudan</font>&gt; a day later, Wudan realizes that LordNLptp was referring to disassembly of the original U7 executable.  Now that's just silly.<BR>
[01:52:51] &lt;<font color="#0000C0">Wudan</font>&gt; that'd be like climbing Mt Everest 99% of the way and then taking a helicopter to the top.<BR>
[03:28:05] &lt;<font color="#0000C0">servus</font>&gt; Getting usable knowledge from disassembly of something like the U7 exe would certainly not be a 'helicopter'. In many ways, it's easier to get the answers in other ways.<BR>
[04:03:44] &lt;<font color="#0000C0">Wudan</font>&gt; well, it does seem rather pointless to start picking apart the exe at this stage<BR>
[04:04:34] &lt;<font color="#0000C0">Wudan</font>&gt; i think disassembly is probably a harder task than I would be willing to undertake, and a harder task than lordnlptp thinks it must be<BR>
[04:06:38] &lt;<font color="#0000C0">Wudan</font>&gt; exult works so well i forgot there was another engine for playing u7 :)<BR>
[14:01:32] &lt;<font color="#EF7AD0">Darke2</font>&gt; In this situation disassembly tends to only really useful if you have a specific question you want answered, that you can't solve by either file analysis or by rewriting a suitable replacement algorithm. Things like working out what an obscure, only used once usecode function does, or working out a compression algorithm works so you can decompress a data file yourself.<BR>
[16:22:52] &lt;<font color="#0000C0">pupnik</font>&gt; o/<BR>
[18:48:28] <FONT COLOR="#008080">---</FONT> <font color="#616161">Sev is now known as Sevalecan</font><BR>