TIP: Click on subject to list as thread! ANSI
echo: cis.os9.6809.coco
to: Paul Hanke 73467,403 (X)
from: James Jones 76257,562
date: 1990-11-01 21:13:51
subject: #7936-RSDOS2OS9

#: 7937 S10/OS9/6809 (CoCo)
    01-Nov-90  21:13:51
Sb: #7936-RSDOS2OS9
Fm: James Jones 76257,562
To: Paul Hanke 73467,403 (X)

To correct a module header, you'd need some notion of what it's supposed to
look like--e.g. what kind of module it's supposed to be, where something that
looks like the module name is, and so forth.  Once you have that, you can use
something like DED to stuff in the values you think should be there--and update
the parity check and CRC if need be.

That's dangerous work, though--no telling what changes you missed!  So, my
advice to you would be, if a module doesn't make it through ident (unless it's
something you've changed in a way that you understand, and forgot to update the
CRC on), don't try to fix it, get a clean version.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.