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

  Re: RE: Talsiman/Postie
  By: vorlon to deon on Tue Apr 19 2022 02:50 pm

 > I think things are getting confussed. Everything was compiled on the
 > m68k, with only config files copied for a starting place.

Yeah I did get that. I just wanted to confirm that you didnt lift the squish (or jam) files from intel and was trying to read them from hpt compile on m68k.

 > The message base files got created by the respective program.

Got it.

 > 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.

I was trying to understand this:

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

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

I think this will help to confirm whether endianness is an issue.

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

Talisman/Postie rejecting the packet (as well as not reading the squish mail files) could still be an endian issue (the error you provided when opening a packet certainly fits that description), even if the answer to the first question is yes. Apam should jump in and comment, but it seems he's not around...


....лоеп
--- SBBSecho 3.15-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

.