ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ TRON V1.21 PROGRAM INFORMATION ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ Programmed by the SMILESOFT Company (Germany) The SMILESOFT COMPANY consists of three 18-20 year old coders! ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Sections ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. What is Tron 2. Requirements 3. Language 4. Technical infos 5. Options 6. The universal expander 7. Help on errors 8. Syntax 9. Infos on compressors 10. Greetings ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. What is Tron? ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Tron is an decompressor for files packed with compressors like PKLITE or DIET. In case you don't know, such programs use different data compression routines to make a file smaller. Files which were compressed with one of these pack programs will still stay executable for the system but they will be much smaller. Another reason for compressing is that a second person has no chance to change any bytes inside a compressed program with a hex editor or something like that. But this feature has disadvantages, too. For example a virus scanner is not able to detect a virus under the compression structure. And on some systems a decompression routine wastes a lot of time (8086 or lower, hehe). It might also be possible that you use a program like stacker to compress your hardisk, in this case the stacker compression makes the file bigger than it was before. These are the primary reasons why we decided to write Tron. Tron itself is able to decompress most common packers as there are PKLITE, DIET, LZEXE, TINY, etc..we have written unpacking routines for the most used packers today, we will not support scrambler's which are spreaded in local areas or special crypt code for intros because it's hardly to believe that you get ever in touch with such programs. If you have one and you are a registered user and the universal expander cannot handle it then send the concerned file to us, we will immediately return it unprotected. Some of the compression programs supported by tRON have a build in expand function! But for insiders it is no problem to trick this functions out! Simply change the header signature "MZ" into "ZM" and the original programs cannot handle their own files any longer. The header signature can be found at the start of an EXE file! And this is only one of many known possibilities. To use the universal expander on compressed or protected exe files you must register first. The rebuilding code for the relocation entrys is disabled in the unregistered version. The activation code for the protected mode unit is also skipped. It might also be possible that the next versions of tRON will only be spreaded to registered users to avoid hackers from searching backdoors in the unpacking system. This is because tron was written for our own purposes and should not be avaiable to coders of encryption or compression programs. However it is we decided to release this version of tRON to the public. Although tRON has been tested on several systems, we cannot guarantee that tRON will be without bugs. Therefore, we do not take responsibility for any damage directly or indirectly caused by tRON as a result of known or unknown errors in it. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 2. What do we need to run TRON? ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ - 640 Kb Memory (Tron needs 16-21 Kb of the system memory) - EGA/VGA/HGC - MS-DOS 3.3+ - 80286+ (normal modus, real mode universal expander) - 80386+ (protected mode universal expander) - a compressed file ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 3. Language ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ Pure HARDCORE Assembler! What else? 16 & 32 bit technology! ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 4. Technical Infos ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ First tron uses DOS to load a file into memory. After loading, it searches for the presence of a packing code. Is such a routine discovered, tron makes some changes to the original compression code, through this changes the pack routine tells tron what it had to know about the file, for example the informations needed to rebuild the original header or the expanded size and the relocation items. If the compressors make no trouble, the file can be written back to disk without problems. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 5. Options ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ -i = info only If you just want to know if a file is packed or with which packer it was compressed, then use this option. Using this option tron will not try to decompress the file. -e = expand to header size Normally TRON tries to make the smallest possible EXE-File. But most linkers allign the header on a sector (512 Bytes). In some cases these files can be loaded faster because DOS is only able to read a whole sector into memory. (1 Sector has 512 Bytes), figger it out! -x No diverting of Interrupts This can be used if TRON aborts unpacking through the call of an system-interrupt! Normally this shows that an expanded program has begin to operate! If you skip the interrupt diverting the file is normally executed without checking for illegal interrupt calls! This can be useful on files you want to expand with the univeral expander or if the protection code calls interrupts (like PGM-PACK)! Warning! In some cases it is possible that a file under these circumstances is EXECUTED! Don't use this on virus infected files! -u = real mode universal expander with user variable filesize and expand breakpoint etc. or autodetection if nothing is entered. -p = protected mode universal expander with user variable filesize and program start! This option is for files which use debugger fooling code! Like using the single-step interrupt or divide by 0 and so on. Totally disabled in the unregistered version. Needed to unpack Protect! 4.00 5.00 EXE and COM files. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 6. The universal expander (most functions are disabled in public version) ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ This is really a nice thing! You are now able to unpack almost every file which uses standard compression or special encryption code. Via the single step interrupt of the CPU, Tron traces through the hole code of a program. If some circumstances are given tron assumes that the protection has disappeared and the original program code is now in the memory. With a little trick we succeded in rebuilding the orignal header of the file. First we had problems to recover all relocation entrys on exe files, but now this works very well. The file length cannot be exactly determined, on most files there is a difference from 0 Bytes to 2 KBytes more as the original file has. To solve this problem you are prompted to enter a filesize. If nothing is entered tron uses an estimated size. You can also enter a breakpoint where execution stops or an opcode dependent breakpoint if tron doesn't stop at the right instruction. If you don't enter anything TRON switches into autodetection mode. In the unregistered version of tron you are only able to use the real mode unit, also the relocations can not be rebuilded unregistered. IMPORTANT: If you are not a programmer or assembly coder you should only change the filesize when you are prompted for! Effect rate on debugging traps: uni expand method ³ tron (1.20) ³ possible in further versions ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ real mode ³ 2 % ³ 3 % protected mode ³ 35 % ³ 90 % We know about 3 technics to fool this tron version, we don't hope you'll get in touch with such a beast. Also we have some trouble with the IRQ redircection from protected to real mode. It would be nice if we get some facts about this. I can't understand that an Interrupt 09 is either an IRQ 0 or an exception interrupt. Two functions with calling one interrupt? 6.1 User defined breakpoint (relative to CS:0000h) Usefull if a an expanded files hangs because the autodetection of tron has failed (possible on very small files). The breakpoint is the first instruction of the expanded file! (after the last instruction of the compression code) 6040:0010 ...................... (first instruction of the packer) 6040:0015 decompression code 6040:0018 .......... 6040:001A ........ ...... 6040:024D retf (last instruction of the packer) | (starts the original file) | \ / 6000:000A mov dx,5824 <-+ (first instruction of the expanded file) 6000:000D mov ds,dx | + --- breakpoint should be here (6040h-6000h=40h) The breakpoint adress is relativ to CS:0000! CS stays for the first value of the CPU-CS-segment register at the start of a program. Tron assumes that you enter a hexadecimal value. At the above program a correct entry would look this way: Enter breakpoint (relativ to CS:0000h): CS-40h:000Ah This types of input strings will be accepted: 1. CS:120h = CS:120 (numbers are always assumed as hex format) 2. CS+10:120 = CS+10h:120h 3: CS-10:120 = CS-10h:120h 6.2 User defined breakpoint times (decimal) Every time the breakpoint is reached this value is decremented by 1 until it is 0. Usefull if your breakpoint has the same adress like a instruction of a compression code. If nothing is entered the default value is 1. This variable is assumed as a decimal variable and is not used in autodetection mode. If you have entered an breakpoint opcode (5.3) this value is only decremented if the first instruction byte matches with your opcode. 6.3 User defined breakpoint opcode (Hexadecimal) To make really sure that the breakpoint is the right you can enter the first opcode of the breakpoint instruction. ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 7. Help on univeral expander errors ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ What should I do if 1. the expanded program hangs? - the estimated file size is to short. Some code is missing at the end. you can enter a bigger filesize if you are prompted for. - maybe tron has determined a wrong breakpoint, so enter one on your own. if you have no knowledge about assembler you must finish here. - the program wasn't packed or protected before using tron so there is no need of trying to unpack it - the program makes a crc-check and hangs on mismatch, use your debugger! - the program uses some bad tricks, use the protected mode unit (-u) and try again. 2. the message "Aborting due to call of interrupt" is shown? - Look if the program is really crypted or compressed. If you are absolutely sure that the interrupt was called through the compression code, add the -X option on the command line and try again. This is very usefull on compressors like PgmPack or Sea-Axe. 3. the message "Access to single step int requested" is shown? - The program tries to hook the interrupt tron uses to step through the code, in this case use the protected mode unit for unpacking. 4. tron hangs up in real mode (Uohhh...very nasty) - the program has found a backdoor in tron and elimated it. - the program uses some anti-debugging stuff tron can't deal with. - the program has hooked INT 01 in a strange way and tron is left alone...(merde) In all three cases try to use the -u command to skip anti-debugging instructions. 5. tron hangs up in protected mode - there is a bug inside tron this might be possible due to the fact that we didn't have a debugger to test our protected mode procedures. This is really a big problem, - the program uses anti-debugging code that can't be handled by the virtual task system of tron at this time. - wait for improvment of this unit ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 8. Syntax ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ usage: TRON [options] [c:][\path]Infile [[c:][\path]Outfile] The default extension for the expanded file is *.exp For example: The Command: TRON SMILE.EXE [Return] generates two files: - Smile.exe | the expanded EXE file | (the file decompressed with tron) - Smile.bak | the orginal file | (the compressed file) ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 9. Notes on different encrypting & packing routines ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 1. Protect! EXE / COM Known: 1.00, 2.00, 3.00, 4.00, (5.00) Tron isn't able to detect COM files protected with v5.00 because of the very good mutation of the code! Our routine succeded on 99% of the files but there may be other COM files which have the same structure without beeing protected, and so this routine is very messy! If you have a short routine which is able to detect the 4.0 and 5.0 files correctly please contact us. All versions before 3.0 were a joke. However, v3.0 is somewhat improved. There are few, simple anti debugging tricks. From v4.0+ there are some major changings. It seems that the author has coded round the clock to do this! Improvements are the mutation of the structur and debugger fooling code inside the decrypting routine. It would take a long time to code an correct unpacker for that, because we would have to test all mutations with the unpacking scheme, that's too much work. If you are a REGISTERED user you can unprotect them with the protected mode unpacking unit of TRON (-p)! (Hehe, yeahh Jeremy, try something else, nice cat and mouse game, really good idea with the mutation, don't think that a normal unpacking program will be able to open 100% of the v5.00+ files.) Just make a new version, but remember, we can do the same! If your program runs under windows, the next tron version will defeat your protection. And to all users of Protect! No software protection will be total secure! Don't use a compression code under the protect structure. Only compress after a file is protected. It takes one minute to get the original file if a known packer was used. (otherwise it takes two) hey Jeremy, v5.0 is really a cool program! By Jeremy Lilley. (Scramble, .EXE .COM, 4.0+ very nasty) 2. ICE (Special) Known: 1.00 (Released 1988) ICE is a program which scramples and compresses COM files (not EXE files) yet allows them to be fully functional. The program makes it difficult to alter the orginal program and it has the added bonus of compressing COM files without detracting from their usefulness. ICEd COM files still run as they did before ICE offers protection agains viruses in that ICE can scramble COMMAND.COM and make it difficult for viruses to attach themselves to the scramble program. By Keith P. Graham (Scramble, .COM only, easy to hack) 3. TinyProg (Generic) Known: Tiny 1.0, 3.3, 3.8, 3,9 Tested on Tiny 3.3, 3.8, 3.9 with password and Data Header! Should also open Tinys with text inside or kind like that. To open a "tiny" with a password, you should know the password. Also, a new kind of tinys with large text files in them is supported. Newer Tiny Versions 3.8+ have a smart anti debugging routine in them We are searching for TinyProg v3.5 and v3.6! By Tranzoa, Co. (Compress, CRC check, .EXE only, good) 3.1 PkTiny (Tiny) Pktiny is a simple program which puts a pklite header into a tinyprogged file. Then it modifies the file in a way that an unpacker isn't able to correctly determine the size of the tiny user data area. I am not sure why the program uses a pklite header because no unpacker known to me identifys pklite compression on such files. By Thomas M”nkemeyer (Fooling, .EXE .COM, nice) 4. EXE Pack (Generic) Known: 3.60, 3.64, 3.65, 4.00, 5.31.009 There are plenty of ExePack versions. Tron knows about 5 of them. They are all less effective, sometimes the ouputfile gets bigger than the orginal one. This is a small joke. By MicroSoft corp. (Compress, .EXE only, old and deffective) 5. LZEXE (Generic) Known: 0.90, 0.91 No mutations found. Makes CRC checked and packed EXE-Files. By Fabrice Bellard. (Compress, .EXE only, old and freeware) 6. PKLite (Generic) Known: 1.00(á), 1.03, 1.05, 1.10, 1.12, 1.13, 1.14, 1.15, 1.20 From 1.14+ PkWare added a small encryption routine inside the registered Version to make Pklited files harder to extract! Pklite is the most used compressor today, there are a lot of hacks circulating. In some boards pklite 1.20 was declared to be a hack, but we think it's an official version now! Version 1.20 of Pklite has a different encryption routine. By PKWare (Phil Katz's). (Compress, EXE & COM, the best compression) 7. PROPACKER (Special) Known: 2.08 Emphasis on packed size Emphasis on packed size, locked By Rob Northern Computing, UK. (Compress, .EXE only, good) 8. DIET (Generic) Known: 1.00d, 1.02b, 1.10a, 1.20, 1.44, 1.45f Diet is also capable of acting like STACKER - such files are not supported by tron. By Teddy Matsumoto. (Compress, EXE & COM, very good) 9. SEA-AXE Known: 2.0 There are not many files around of this antique. The packed code is saved in an overlay area behind the sea-axe code. By System Enhancement Associates (Compress, .EXE only, old and less effective) 10. PGMPak (Generic) Known: 1.15 Not easy to extract. There are some nice tricks used to make unpacking harder, we couldn't use our normal unpacking routines. PgmPak doesn't give you full memory, it also keeps its name in the end of the compressed file as an overlay. By Todor Todorov. (Compress, .EXE, good) 11. OPTLink This is the program is found on all norton programs. We haven't found a distributed version of this packer. 12. DeltaPack Known: 1.0 Found on some bbs intros. By ? (Scramble, .?, easy to hack) ------------------------------------------------------------------------------- Special thanks for the 32 bit part goes to TRAN of Renaissance for releasing his protected mode header to the public. Hello Tran, If you want to get a registered version of tron just write us a letter. Other unprotecting Software that is worth to be used: Xopen v3.20 (Ady/Israel) opens really a lot, well done Ady, what about a gratis registration for us? You will get a registered version of TRON too...nice to see that there are other people which know what they do. Unp v3.30 (Ben Castricum/The Netherlands) This program is freeware and has a lot of features! Hello ben, your unpacker is the one liked most by us. Just look at tron. StickBuster v2.40r (Lihor Cohen/Israel) We believe to have seen this program under another name a few months before... From all unpackers we discovered, StickBuster is the one which handles the most compressors, but these are mainly very antique or only spreaded in local areas. Hey Lihor, work on your user-interface!!! ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ 10. Greetings ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ to all who find this program usefull! always nice... AND TO Enzo, Sonic, Maroon, Fox, Ant, D.E.L., Byte Stefan Kuhn (Bitblaster BBS) Lihor Cohen, Ben Castricum, Ady, Mc Afee, Pkware, Id Software, Waldi, Tobias, Sandra, Torte, Tina, Michaela, Sascha, Udo, J”rg, Steffen, Baur, Rissman, Gairing, Forki (TG'94) Homeless Hotdogs, Slayer, Metallica, Real 2 Real, Design, Marusha etc. msg to MDS: legends_will_never_die Smilesoft-Productions Michael B., Alexander G., Teddy, If you are a coder of an expanding or decrypting program please send your program to us, of course you'll get a registered version of tron without paying money. Send all bugreports to me! Use the adress below. We are happy about every letter we receive from you! Just write what you think. Michael Bauder 73230 Kirchheim Kornbergstraáe 14 Germany