Will probably fix deep-linking problem on Deuce's system.

aren't the same it's assumed to be an IPv6 address.

<access_d> i'm guessing my might have made a quick init script at one point, but the one on CVS works (besides the opts function being depricated soon)
<access_d> so if anyone would care to remove line 22, that will fix it. :)

(accidentally bumped 2 versions in previous commit)

memcpy calls and explicit setting of fields to 0) - this code is just bad.
The only functional change should be that the SBBSecho product code (0x12FF)
and major/minor version number is now added to headers of type 2+ packets
generated by SBBSecho. Type 2 and 2.2 packets will have just 0xff for the
product code and the SBBSecho major version number in the product "serial
number" field (as is the common practice). I guess everyone's using type 2+
packets these days? You don't get 5D addresses with 2+, but SBBSecho doesn't
really do anything with 5D addresses anyway. <shrug>

Print wanring if type 2+ orig/dest zones don't match the zone fields in the
type-2 portion of the header.
Updated some pkt header field names in fidodefs.h.

system's address was being added to SEEN-BY list twice when destination zone
was different than the system's zone.
Another experimental change for Joe (1:249/303) and Wilfred: when parsing
SEEN-BYs from incoming packets, assume the zone of the nodes in the SEEN-BYs
is the same as the origin zone of the packet, rather than the destination zone
of the packet.

Add a div per message to push message reply forms into.

can still be updated.

been open()ed.

Trach the latest page view in data/user/%04d.ecweb and display this info
in the who's online sidebar.

Removed 'getmessage' condition (would call printMessage from forum.ssjs, which wasn't used, didn't work, and has been removed.)