Subj : Re: Clearing Houz
To   : Apam
From : deon
Date : Thu Nov 09 2023 04:07 pm

  Re: Re: Clearing Houz
  By: Apam to Deon on Thu Nov 09 2023 12:41 pm

Howdy,

 > |11d|09> |10What's the packet?|07
 > |11d|09> |07
 > |11d|09> |10I see a couple of bad packets, but not from you.|07
 >
 > I deleted the previous one, but now I'm trying to send 00000005.tu0

OK, looks like I might have a bit more work.

Your sending me a file with this M_FILE
[2023-11-09 00:34:08] production.INFO: PB-:+ About to receive a file [00000005.tu0 417 1699309714 0 C47055F5] {"pid":53755}

The issue is the C47055F5 - what's that? (A checksum of the file you are sending me?)

I started implementing compressed transfers (but didnt finish it because to me that compressed transfer logic is not fullproof - as I dont know how much data to expect, and so I need to figure out how to determine when the transfer is completed). From memory though, the value after the offset (0 in this case), from an M_FILE is the compression method to use (and that's whats clrghouz houz is tripping up on).

So I'm rejecting the file (M_SKIP) and recording this error:
[2023-11-09 00:34:08] production.ERROR: PB-:! File Open ERROR [Unsupported compression:C47055F5] {"pid":53755}

So a question, your session started with "OPT CRC", which I wouldnt have replied back with an OPT CRC, so curious why the CRC is still being used? (I'm wondering what order there is if OPT EXTCMD GZ BZ2 is also used.)

I wouldnt mind implementing being able to handle CRC transfers (IIRC, MBSE uses it too) - it was on my list to explore.

So is it possible you can turn it off - if anything temporarily? Otherwise I'll patch my code to ignore it for now before I implement it. (So at least your transfers will work.)


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

.