Subj : RE: Talsiman/Postie
To   : deon
From : vorlon
Date : Tue Apr 19 2022 10:46 pm


 >> Hpt/Magicka = Work (Jam message base)
 >> Hpt/Talsiman = Not Work (Squish message base)
 >> Talsiman/Postie = Work, but the hub/postie reject the packets as bad.
 >> (Squish message base)
 >>
 >> Hpt can't read squish filse created by Talsiman/Postie.
 >> Talsiman/Postie can't read squish files created with hpt.
 >>
 >> Talisman dosn't support JAM message bases. That's how I found the 
 >> Squish message base issue above, as hpt supports squish. But not in 
 >> this configuration.

 d> I was trying to understand this:

 d> hpt(m68k) generates a packet and is read OK by hpt(intel) (or some 
 d> other mail tosser I guess...)?

Yes. The messages that came from Magicka/Hpt (This point) pass through the net633 ftn hub, that's running HPT (Intel).

 d> can hpt(m68k) read it's own squish files OK?

Yes. This message is using the squish message base created by hpt. I compiled the msged editor to make sure it was doing that.

 d> I'm not sure what "Not Work" means (for Squish) - I dont recall if you 
 d> described that error you were seeing. Not sure if there is a "debug 
 d> mode" that might help..?

Talisman can only read/write squish message bases.

 d> Talisman/Postie rejecting the packet (as well as not reading the 
 d> squish mail files)

Talisman/postie only can't read the squish mail files if they are created with hpt & vice versa.

Talisman/Postie can read write them ok, but then the packet is rejected at the hub.

 d> could still be an endian issue (the error you provided when opening a packet certainly fits that 
 d> description), even if the answer to the first question is yes.
 d> Apam should jump in and comment, but it seems he's not around...

Until Apam show's up, we wont know.

--- msged/lnx 6.3 2022-02-08
 * Origin: Vorlon Empire: Sector 550 (21:1/195.1@fsxnet)

.