Anybody good at disassembly????

Jerome Fine replies: I realize this will not help your specific problem, but I want to add that there are two basic types of disassembler: (a) Those that start from the final executable file - probably the majority (b) Those that start from the OBJ file. For the PDP-11, about the best program that I use is DECODE with a few enhancements - the most important being the ability to allow an odd address label in the case of an .Ascii text definition. Also helpful for RT-11 users is a comment inserted when an expansion for an EMT macro like .LookUp is found or .ReadF or many others. There is also the start of some code to handle overlays, but not complete. DISSAV is also available. For the second type (b), there is UNMAC which also has some enhancements that allow UNMAC to be applied to itself. Specifically, even though the original source is in FORTRAN 77, the OBJ files can be put through UNMAC to produce a *.MAC file that can be assembled via MACRO to produce a slightly different OBJ file but which then LINKs to produce a final SAV file that is identical to the original UNMAC.SAV file produced from the OBJ files that were produced by the FORTRAN 77 compiler in the first place. Note that the original UNMAC could not do that without substantial intervention by hand if at all. By the way, while I realize that most members of this list are focused toward hardware, the few of us who like software do not seem to mention it very much, as if software is not important. Perhaps those of you who are the hardware type could explain to me why the software holds so little interest. While I agree that the hardware is needed to run the software (well not actually anymore in the case of a PDP-11), I have never seen anything useful from a system that has dumb software. But why does someone feel that the solution is complete when the hardware is working? Sincerely yours, Jerome Fine