"Zork") you one file on Hi Ethan I add comments after the decompiling with a merge. The control file just has code start addresses and data block types/addresses. I even deal with labels in a separate file that is later merged to form the complete output file. I even put data in a separate file from the code. I like the idea of just merging it all when done. The disadvantage of this is that only computer generated comments exist on the same line as the code or labels ( like the counts of how many times a label was used ). Human comments are always on separate lines. This is all controlled by the sorted address fields. Comments and labels are attached to specific addresses that are used during the merge of the various files. This way, the comments are not part of the control file ( no specific advantage here ) but by sorting before merging, disassembled code, comments and labels don't need to be placed in the output files in any specific order. Comments only need to have an address to show order. Order of these sub pieces that may have the same address is controlled by the merge order. Comments can be easily extracted from an edited list file by looking for text that doesn't have address. One simply uses the next address after this text for the next iteration. Comments are most easily added this way to the previous output list file and feed back for the next iteration and future iterations by placing them in the comment file. The comment file also has the advantage that it can later be edited to enhance comments or rearrange lines within comments( remember a comment can be multiple lines with the same address ). I used the DOS sort ( 64K limit fixed by splitting files ) and my own merge that takes any size files. It is all handled in a batch file so I just take a break while it runs. Dwight