Howdy, hoping somebody could help clarify something for me. Does anybody use qico (or did)?
I've been playwith qico (another ifcico ftn mailer), mainly because ifcico from the debian repositories coredumps when you change some config settings like debugging. It also looks like I can call a tossing action after received mail, which I havent figured out how to do with ifcico (unless I used cron). I'm using it to send mail to my 1995 BBS that is Portal of Power 0.62.
I noticed that ZedZap transfers wouldnt start, I started debugging the code, and noticed that a <CR> <LF> where not sent from POP with a HEX header (after the CRC) - only an XON.
I was curious as to why ifcico was working, and from it's code it looks like it doesnt check for <CR><LF> either - in fact it looks like it discards anything received after the CRC (if the CRC matches) (up to the size of the header).
So I made the a similar change for qico (I exit if I get the XON), and it works, just wondering if this the right course of action and if there are any side affects?
Never used QICO, but ZedZap is a variant of ZMODEM. If it helps, you can look at the ZMODEM implementation we use for SEXYZ here: http://cvs.synchro.net/cgi-bin/viewcvs.cgi/src/sbbs3/zmodem.c?view=log
Re: ZMODEM with QICO
By: Digital Man to alterego on Sun Apr 12 2020 05:53 pm
Never used QICO, but ZedZap is a variant of ZMODEM. If it helps, you can look at the ZMODEM implementation we use for SEXYZ here: http://cvs.synchro.net/cgi-bin/viewcvs.cgi/src/sbbs3/zmodem.c?view=log
So, if I'm reading your code correctly, you are not checking that you actually get the <CR> and <LF> right? (zmodem_recv_hex_header() line 1077).
If I read correctly, *if* you get the CR, you then drop the next char, which is probably the LF. But if you didnt get the CR, it doesnt matter, you return TRUE anyway... (In my case the next char is not CR but XON.
So, its sounds my fix is OK.
Another question if I may, I've noticed that the transfer is stalling each 65536 bytes. Its correctly restarting, but I was wondering if there is something that had to be done every 0xffff bytes received (and is not being done, and thus the constant resend).
Do you do anything special every 0xffff bytes received or sent?
So, if I'm reading your code correctly, you are not checking that you actually get the <CR> and <LF> right?It does *wait* for the CR though. And yes, if recieved, assumes the next char would be an LF and wait to receive it as well.
(zmodem_recv_hex_header() line 1077).
Re: ZMODEM with QICO
By: Digital Man to alterego on Sun Apr 12 2020 10:17 pm
So, if I'm reading your code correctly, you are not checking that you actually get the <CR> and <LF> right?It does *wait* for the CR though. And yes, if recieved, assumes the next char would be an LF and wait to receive it as well.
(zmodem_recv_hex_header() line 1077).
Sorry, for clarity.
Do you wait for the CR, or what for the next char? If the next char is not CR, it returns true anyway...?
It was for any char. If a char is received and it's a CR, then it waits for another char. Both chars, if received, are discarded. In
any case, the function return true (success).
On 04-13-20 10:28, alterego wrote to All <=-
@VIA: VERT/ALTERANT
Howdy, hoping somebody could help clarify something for me. Does
anybody use qico (or did)?
On 04-13-20 10:28, alterego wrote to All <=-
Howdy, hoping somebody could help clarify something for me. Does
anybody use qico (or did)?
I'd be interested in your mods. :)
Sysop: | Kurt Hamm |
---|---|
Location: | Columbia, SC |
Users: | 8 |
Nodes: | 20 (0 / 20) |
Uptime: | 135:25:56 |
Calls: | 2,804 |
Calls today: | 1 |
Files: | 64 |
Messages: | 854,509 |