home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Lion Share
/
lionsharecd.iso
/
bbs_oth
/
packp201.zip
/
PACKPEEK.DOC
< prev
next >
Wrap
Text File
|
1992-01-02
|
4KB
|
62 lines
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* "PackPeek"<tm> v 2.01 - a Fidonet(R) FTS0001 and FSC0039 *.PKT disassembler *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
(C) Copyright 1987 thru 1991 Mike Ratledge
"FidoNet"(R) is a registered trademark of Tom Jennings and Fido Software.
This is a complete rewrite of my now-ancient "PackPeek" program - the source
code was lost to Hurricane Hugo... (which explains why you haven't seen any
new versions in the last two years) Anyway - I decided to get it out and
polish it up a bit and add FSC-0039 support as well as extensibility to the
FTSC product code (PID) table.
Version 2.00 was a quick thrown-together rewrite I did in about three hours
one night when I was PO'd about something I forget now <grin>... This 2.01
does a much better job of things (heck - I threw in another couple hours!).
Version 2.01 also has "help" and a few other options - try "PackPeek -?".
I also fixed numerous things reported by Gerard van der Land and others,
including wrong 4D point address display, locking up on "unusual" files,
going beserk if you hit a function key and noting ill-formed end-of-packet.
PackPeek v 2.01 uses the "FTSCPROD.xxx" list maintained and issued by Rick
Moore, the chairman of the Fidonet Technical Standards Committee. It uses
the first one it finds in current subdir or PATH, and displays more detailed
information for each message creator in that list. You must rename the file
"FTSCPROD.xxx" to "FTSCPROD.PID" for XRS to find it either in the current
directory or on the PATH. Currently, "PackPeek" only supports 256 product
codes - when we exceed that I'll see how Rick zigs and zag accordingly. If
any entry in that file exceeds 80 characters, it is truncated.
You can manually edit "FTSCPROD.xxx" yourself to keep it up-to-date or add
some program you are testing, for example. You should replace your copy of
FTSCPROD.xxx every time a new one is issued, so you're working with the most
up-to-date list all the time! Note: PackPeek makes absolutely no attempt to
intelligently analyze the "FTSCPROD.PID" list. It considers the first two
bytes in each line to be the two-digit FTSC product ID in hex, and ignores
lines beginning with ";". I have included a not-to-ancient version of the
FTSCPROD.xxx file I found laying around on my home system, added the product
code for Harry Lee's new MilqueToast CUA/SAA Binkley clone I'm alpha testing
and that's what you've got - there is likely a newer one out already!
PackPeek displays 2D, 3D and/or 4D to and from addresses depending upon what
it finds in each packet. I also added 'smarts' to support any screen size
(height or width) instead of forcing you into 80x25 color mode, supporting
any screenwidth and 43- (EGA) and 50-line (VGA) modes as well.
PackPeek is a working tool I use - feel free to distibute it as you see fit
with no restrictions except that a fee may not be charged for doing so, the
archive contents are unaltered and my copyright notices may not be removed.
As such, I don't plan to do any major heavyweight revamping of it, but when
you find a *.PKT or *.?UT file it doesn't handle correctly, please forward
me a copy so I can figure out what I left out!
As usual, you get the "Smokin' Software" 'give-a-ware' no-fault guarantee:
"If it breaks in two - you own both parts!"
Mike Ratledge
January 2nd, 1991