'sockbufW overrun' when uploading large file

[andy5995]

Uploading a 100MB+ file to a BBS with minicom and modemu2k, I got several 'sockBufW overrun' messages during the transfer. The file appeared to be ok after transfer though, probably due to crc checking done by minicom, lsrz, the BBS or wherever it's done. ;)

The sockBufW message was generated by modemu2k though

modemu2k/src/sockbuf.c

Line 110 in 102d6bb

fputs ("\asockBufW overrun.\n", stderr);

@aianson On the Musescore appimage I uploaded, is the md5sum 8a7c100a19fd78e1c43fccd5c1db27a6 ?

And the file size 160305128 ?

[aianson]

On Mon, 12 Jul 2021 10:28:02 -0700 Andy Alt ***@***.***> wrote: Uploading a 100MB+ file to a BBS with minicom and modemu2k, I got several 'sockbufW overrun' messages during the transfer. The file appeared to be ok after transfer though, probably due to crc checking done by minicom, lsrz, the BBS or wherever it's done. ;)

Using BBBS Toy-4 zmodem uploads seemed to be broken, completely. That seems to be fixed in Toy-5, or at least it is working better. I think I can make lrzsz an option if need be. I'll look into that.

@aianson On the Musescore appimage I uploaded, is the md5sum 8a7c100a19fd78e1c43fccd5c1db27a6 ? And the file size 160305128 ?

Yes, the size and md5sum looks good to me. There are also new Toy-5 bterm packages including a 32/64bit for linux, RaspberryPi, Windows and OS/2 versions. Bterm uses what it calls BZLL mode by default. BZLL has two features, when you log in your password is transfered as an MD5SUM, of some sort so it provides a bit of password security. When you transfer files it happens slowly in the background so you can browse the BBS while you do that. That is fine for small files like offline packets and replies but it's not so good for large files. You can toggle BZLL mode with F5 but you can't turn it off mid session. If you log in with BZLL you are stuck with it for that session. Bterm may make your life better, or not.. ;) FTP is also an option. If you log into the BBS ftp server with your bbs username and password you can upload/download files and mail packets and replies. In the case of mail packets you will always get a file called "grab", so you may want to rename it trmb.qwk for qwk or trmb.th0 for a blue wave packet. The same is true of your replies. Your reply packet may be called trmb.rep or trmb.new but you always have to send BBBS a file called "grab". If you do that the BBS will import/export those packets for you at the ftp prompt and you will be able to see that the upload was successfully imported or not. One thing to keep in mind about ftp transfers is that when you log in you will always be in ascii mode so you need to type "binary" and go into binary mode before download/uploading binary files. Nothing good is going to happen with binary files in ascii mode. ;)

[andy5995]

On Mon, 12 Jul 2021 10:28:02 -0700 Andy Alt @.***> wrote: Uploading a 100MB+ file to a BBS with minicom and modemu2k, I got several 'sockbufW overrun' messages during the transfer. The file appeared to be ok after transfer though, probably due to crc checking done by minicom, lsrz, the BBS or wherever it's done. ;)
Using BBBS Toy-4 zmodem uploads seemed to be broken, completely. That seems to be fixed in Toy-5, or at least it is working better. I think I can make lrzsz an option if need be. I'll look into that.

I don't think there's a need. I was referring to the lrzsz on my end, and poorly expressing that I don't really understand how the CRC checking works for file transfers. ;)

@aianson On the Musescore appimage I uploaded, is the md5sum 8a7c100a19fd78e1c43fccd5c1db27a6 ? And the file size 160305128 ?
Yes, the size and md5sum looks good to me.

Thanks for confirming

Bterm may make your life better, or not.. ;)

Oh, I hadn't heard of Bterm before. I had tried syncterm and it seemed pretty good.

I gotta use modemu2k though, so I can find bugs, and maybe even fix them one day. :)

I don't think the sockBufW messages I got are going to be very problematic, since the file transfer worked, but it would be good if I could figure out the cause and fix it sometime. I honestly don't understand the modemu2k code base very well yet, but maybe someday.