mdoerr@uklirb.UUCP (02/02/87)
I experienced problems when uudecoding disasmbl.tos, too. But as I noticed, that the program has been posted by someone on BITNET, I examined the file more closely. And this is, what I've found: 1. Some lines are short of a few bytes. -> Fill those lines with trailing blanks until they line up with all the other lines. 2. There are a lot of tildes ('~' == 0x7e) in the file. Tilde is not a valid character in an uuencoded file. But I happened to remember a posting by someone on the net who found out, that these tildes started out as pointers ('^' == 0x5e). -> Change all tildes (0x7e) to pointers (0x5e). Next: Now uudecode that modified file, then unarc disasmbl.arc to get disasmbl.tos. The program is really nice, the author even left labels in the object. How I did notice that? Well I disassembled disasmbl.tos with itself and was surprised to see, that all the major routines and data areas were given nice descriptive labels. Now it would be really nice, if it could add all the missing comments :-) *** FLAME ON *** Shoot that #$%@ BITNET-hosts! *** FLAME OFF *** Have fun, Michael Doerr. Uni. of Kaiserslautern (Germany), uucp: ...!seismo!unido!uklirb!mdoerr
silvert@dalcs.UUCP (02/14/87)
I've tried suggestions from this article as well as from Lindahl, padding with blanks, changing tildes, etc. Still can't get it together -- if I get an arc file, I can't decode it (bad decode tree). Would very much like this program, so could someone either mail me a copy or repost it? -- Bill Silvert Marine Ecology Laboratory, Dartmouth, NS, Canada CDN or BITNET: silvert@cs.dal.cdn -- UUCP: ..!{seismo|utai}!dalcs!silvert ARPA: silvert%dalcs.uucp@seismo.CSS.GOV -- CSNET: silvert%cs.dal.cdn@ubc.csnet