XON/XOFF was much more useful in 'the old days' although as you say it's
still useful in certain circumstances.
But yes, with so little space above the high water mark the M100 needs
either a bridge with a large buffer* or *a small packet size if possible,
preferably one character just like
On Mon, Apr 26, 2021 at 7:04 PM Mike Stein wrote:
> WiFi adds an extra element to the problem because unlike
> one-character-at-a-time RS232 the data is in uninterruptible packets; when
> the M100 sends an XOFF to stop sending, the other end doesn't respond until
> it's finished sending the
On 4/26/21 10:03 PM, Mike Stein wrote:
Aside from that you might be able to use a discrete buffer between the
M100 and the modem, such as was used for printers in 'the old days'...
Ahh printer buffers and leg warmers...
--
bkw
WiFi adds an extra element to the problem because unlike
one-character-at-a-time RS232 the data is in uninterruptible packets; when
the M100 sends an XOFF to stop sending, the other end doesn't respond until
it's finished sending the current packet and since the M100 doesn't send
the XOFF until
Yes, but I will try it again at 600 baud of that is the max TELCOM can do
with the screen.
On Mon, Apr 26, 2021, 2:46 PM Alex ... wrote:
> Is it enabled on both sides? On the modem itself and make sure the last
> letter of the STAT string in TELCOM is "E" and not "D"
>
> On Mon, Apr 26, 2021 at
I am using Arcanbyte which ties in to my Wi-Fi so no copper. I did change
both sides to XON/XOFF but I haven't tried 600 baud yet.
On Mon, Apr 26, 2021, 6:46 PM Mike Stein wrote:
> Are you using a 'real' copper POTS telephone line?
>
> On Mon, Apr 26, 2021 at 3:06 PM Alex ... wrote:
>
>> Is
Are you using a 'real' copper POTS telephone line?
On Mon, Apr 26, 2021 at 3:06 PM Alex ... wrote:
> Is it enabled on both sides? On the modem itself and make sure the last
> letter of the STAT string in TELCOM is "E" and not "D"
>
> On Mon, Apr 26, 2021 at 8:27 AM Jeff Gonzales
> wrote:
>
>>
Is it enabled on both sides? On the modem itself and make sure the last
letter of the STAT string in TELCOM is "E" and not "D"
On Mon, Apr 26, 2021 at 8:27 AM Jeff Gonzales wrote:
> I have XON/XOFF set but it is still getting garbled.
>
> On Sat, Apr 24, 2021 at 5:25 AM Alex ... wrote:
>
>>
What John said was your definitive answer.
You simply can't actually go any faster than 600 *reliably*, in TELCOM
with the screen active. It doesn't matter that telcom/basic allow
setting higher speeds.
Even with xon/xoff, when the 100 says "stop sending!", by the time the
xoff byte
I have XON/XOFF set but it is still getting garbled.
On Sat, Apr 24, 2021 at 5:25 AM Alex ... wrote:
> Definitely flow control. My 1200 baud Kantronics KPC-3 does the same thing
> in TELCOM if flow control isn't on.
>
> On Fri, Apr 23, 2021, 22:08 Jeff Gonzales wrote:
>
>> Hi,
>>
>> I just got
Definitely flow control. My 1200 baud Kantronics KPC-3 does the same thing
in TELCOM if flow control isn't on.
On Fri, Apr 23, 2021, 22:08 Jeff Gonzales wrote:
> Hi,
>
> I just got myself an ArcaneByte modem. I connected to the fozztexx BBS
> and posted a message! Not quite as exciting as my
The model 100 can communicate at 76800bps without losing characters... with
hardware flow control and custom software.
But with TELCOM and the model 100's slow screen 600baud is probably the
limit.
Are you using software flow control?
One other thing I found when writing HTERM is that ANSI
Hi,
I just got myself an ArcaneByte modem. I connected to the fozztexx BBS and
posted a message! Not quite as exciting as my first post when I was 9
years old but it was cool getting it set up.
The problem is that I can't get the m100 to run at 1200 baud. It skips
text and displays garbage
13 matches
Mail list logo
