| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | PKT structs {sigh} |
'Lo all.
I got a copy of PKT structs that I devised from the FTS-0001.TXT
document, and it appears as if they're totally and completely useless,
and that I've been modifying my program in vain for the last several
days :<
Here are the structs I have;
======
Type
PacketHeader = Record
origNode : Word; (* of packet, not of messages in packet *)
destNode : Word; (* of packet, not of messages in packet *)
year : Word; (* of packet creation, e.g. 1986 *)
month : Word; (* of packet creation, 0-11 for Jan-Dec *)
day : Word; (* of packet creation, 1-31 *)
hour : Word; (* of packet creation, 0-23 *)
minute : Word; (* of packet creation, 0-59 *)
second : Word; (* of packet creation, 0-59 *)
baud : Word; (* max baud rate of orig and dest, 0=SEA *)
PacketType : Word; (* old type-1 packets now obsolete *)
origNet : Word; (* of packet, not of messages in packet *)
destNet : Word; (* of packet, not of messages in packet *)
prodCode : Word; (* 0 for Fido, write to FTSC for others *)
serialNo : Word; (* binary serial number (otherwise null)*)
password : Array[1..8] of Byte; (* session password (otherwise null) *)
origZone : Word; (* zone of pkt sender (otherwise null) *)
destZone : Word; (* zone of pkt receiver (otherwise null)*)
fill : Array[1..20] of Byte;
end;
Attrib_Flags =
(
Private ,
Crash ,
Recd ,
Sent ,
FileAttached ,
InTransit ,
Orphan ,
KillSent ,
Local ,
HoldForPickup ,
unused ,
FileRequest ,
ReturnReceiptRequest ,
IsReturnReceipt ,
AuditRequest ,
FileUpdateReq
);
PakdMessage = Record
origNode : Word; (* of message *)
destNode : Word; (* of message *)
origNet : Word; (* of message *)
destNet : Word; (* of message *)
AttributeWord: Set of Attrib_Flags;
cost : Word; (* in lowest unit of originator's
currency *)
DateTime : Array [1..20] of Byte; (* message body was last edited *)
end;
======
I just grabbed PKTVIEW, which came with a program called Soupgate (I
didn't want Soupgate, only PKTVIEW :> ).
Here's what it came up with (PKT header only) for a WORKING PKT
generated by Squish/2 v1.11;
653ae921.pkt:
Detected Type 2+ packet
--- PACKET HEADER ---
Packet version : 2
Capability word : 0001
Capability validation : 0100
Product code : 0.122
Product revision : 1.11
Product specific info : 544B5058
Date and time : 1998-11-19 00:37:22
Originating zone : 1
Originating net : 229
Originating node : 604
Originating point : 0
Destination zone : 1
Destination net : 229
Destination node : 600
Destination point : 0
Auxiliary net : 229
Baudrate : 0
Password : ********
(Nothing but the PW altered) and here's what it detected for *MY* PKT;
00000000.PKT:
Detected Type 2 packet
--- PACKET HEADER ---
Packet version : 2
Capability word : 0000
Capability validation : 0000
Product code : 0.0
Product revision : 0.0
Product specific info : 00000000
Date and time : 1998-12-24 20:49:10
Originating zone : (0)
Originating net : 229
Originating node : 604
Originating point : (n/a)
Destination zone : (1)
Destination net : 229
Destination node : 604
Destination point : (n/a)
Auxiliary net : 229
Baudrate : 0
Password :
What the second one SHOULD be, is a PKT from 1:229/604.1 to 1:229/604.0,
but Squish sees it as a bad PKT, and throws it away.
So - does anyone have any structs for creating PKT2+ PKT's?
Please! Anything! I'm on the verge of pulling out my hair here! :<
Stewart Honsberger (AKA Blackdeath) WWW: http://sprk.com/blackdeath
E-Mail: blackdeath{at}tinys.oix.com ICQ: 3484915
... Submitted for your approval.
-!- GOPGP/2 v1.20
--- Msged/2 TE 05
* Origin: Blackdeath BBS - Private (1:229/604)SEEN-BY: 396/1 632/0 371 633/210 260 267 270 284 371 635/444 506 725 728 SEEN-BY: 639/252 670/218 @PATH: 229/604 600 1 2424/10 12/12 396/1 633/260 635/506 728 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.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™.