Subj : Re: bbS Servers in Docker
To   : paulie420
From : deon
Date : Mon May 29 2023 11:32:51

  Re: Re: bbS Servers in Docker
  By: paulie420 to deon on Sat May 27 2023 03:38 pm

 > I don't LOVE jgoerzen's way of using 'supervisor' and VNC to get into the

Actually I dont mind it. For the DOS bbs, if you could attach to a dos terminal 















































































that would be good - and perhaps with QEMU cursors you could, but if DOS is run 















































































in a window it works OK.

I actually used this to get multinode running, so each "node" was a new window, 















































































and VNC enabled me to see what was going on in each window.

 > DOS dockers - but he's done a lot of work...
 >  de> The challenge I had, (which may be due to the way I was implementing
 >  de> it), is DOS doesnt give up the CPU, so my poor little APU1D was working
 >  de> hard for very little use. It was also challenging to get a reliable
 >  de> mailer working (so that it had mail) - since zmodem is very fussy if
 >  de> one side is slower than the other. (Which resulted in me starting on

 > Yer above my head already, but for mail I've gained a lot of knowledge from
 > the Renegade guys... they have their [Legacy hardware/VMs] tossing right
 > along.

Which part? The CPU bit is because DOS thinks it owns the CPU and runs it full 
steam. You can load "dosidle" which does give up the CPU, but when you have a 
BBS with a WFC screen (or a mailer), it doesnt give up much :(

The mailer part is if you want to use mail transfers (or for that matter enable 















































































file downloads from the DOS BBS). The common transfer being used (zmodem), is 
not tollerant to each side of the connection having different speeds.

Since DOS BBSes only talk serial ports - the "DOS" side is limited by the speed 















































































of the emulated serial port - say 115200 baud, but the other side is ethernet 
(with operating system buffers). So when a transfer is done, 1 side waits for 
the other to say "I'm finished, or I got it" - and it only waits so long. If it 















































































doesnt get a response then it "timesout".

The problem is, for example, the ethernet side sends a file, it fills up a 
TCP/IP buffer and it thinks the otherside should have got it (and waits for the 















































































ACK) - but the other side is draining the TCP buffer through a slow link 
(115200) and if it takes too long to get to the end of the buffer, the other 
side has given up and gone.

When I wrote my clrghouz mailer, I made zmodem send at a slower speed, and wait 















































































longer before "timeing out" the other side...


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

.