On 4/16/21 7:16 PM, John R. Hogerhuis wrote:
"not a screaming cpu"
On the one hand TS-DOS can timeout on delays. I think the glug-glug
performance of Wifi and Bluetooth makes it not work.
On the other hand, it's possible and Steve is concerned that a fast
sender could overrun the Model 100's receive buffer when responding to .
TPDD packets are about 128 bytes maximum, while the Model 100's receive
buffer is 64-bytes.
Unrelated, TS-DOS likes to give up because of DSR deasserted, another
complicating factor.
Since TPDD emulators have been functional for decades on hardware as old
as TRS-80 desktop PCs, so who knows. As to Powermac I'd be more
concerned the emulator causing buffering delays.
I wonder if TEENY uses the receive queue or it does direct I/O? That's
always a good diagnostic tool. You cannot trip up its timeouts, because
it doesn't implement any. So if TEENY has problems I think it would mean
buffer overrun on receive.
-- John.
It now comes out he's using softwindows in macos 9 to run the original
ms-dos desklink.com. And the serial port on that machine is really a
rs-422 port that can operate in a rs-232 mode, sort-of.
All bets are off. Was there ever any native macos-before-osx tpdd
servers? That would probably be best for his case.
He has not been able to get teeny to transfer a file. The symptoms sound
like missing DSR line in his special mac modem cable. But who knows.
I told him about the option to generate a TEENY that doesn't need DSR
from the TEENY.EXE manual.
--
bkw
