onday, October 17, 2016 6:12 PM
Subject: Re: [M100] mComm 1.5
The only time I've seen it go over 64 was when stepping through the T-Word
code and watching the buffer byte while sending a track (128 bytes + header)
from sardine.But I may have been watching the wrong byte in memory.
As far
On Mon, 17 Oct 2016 17:11:28 -0700, John R. Hogerhuis wrote:
Interesting. Might have a use for that, I do some work with vending
machines. The MDB bus used for communication with payment device has
9 bit
data.
Yeah, that looks like the same protocol (not identified as such with
the
kit I w
On Monday, October 17, 2016, Daryl Tester <
dt-m...@handcraftedcomputers.com.au> wrote:
>
> I had this issue when doing 9 bit serial I/O (needed for comms with
> certain equipment) on FreeBSD. The 9 bit hack for traditional UARTs is
> done by manipulating parity generation with each byte write to
On Mon, 17 Oct 2016 15:28:45 -0700, John R. Hogerhuis wrote:
Well android is Linux so that figures.
The problem with the Linux driver is that it follows the standard Unix
driver (which is not typical for Linux, but here we are). Software
flow
control schedules a software interrupt, which ca
On Monday, October 17, 2016, Kurt McCullum wrote:
> The only time I've seen it go over 64 was when stepping through the T-Word
> code and watching the buffer byte while sending a track (128 bytes +
> header) from sardine.But I may have been watching the wrong byte in memory.
>
> As far as the 64
John R. Hogerhuis To: Model 100
Discussion Sent: Monday, October 17, 2016 5:05 PM Subject: Re: [M100] mComm
1.5
On Mon, Oct 17, 2016 at 1:11 PM, Kurt McCullum wrote:
John, Thanks for info. Is that a TELCOM limit? The reason I ask is
because when running virtual T with TS-D
- Original Message -
From: John R. Hogerhuis
To: Model 100 Discussion
Sent: Monday, October 17, 2016 5:05 PM
Subject: Re: [M100] mComm 1.5
On Mon, Oct 17, 2016 at 1:11 PM, Kurt McCullum wrote:
John, Thanks for info. Is that a TELCOM limit? The reason I ask is because
when
Subject: Re: [M100] mComm 1.5
John, Thanks for info. Is that a TELCOM limit? The reason I ask is because
when running virtual T with TS-DOS, I notice that the buffer can go to 255. Or
at least the byte which holds the buffer size.
Kurt
On Monday, October 17, 2016 11:36 AM
On Mon, Oct 17, 2016 at 1:11 PM, Kurt McCullum
wrote:
> John, Thanks for info. Is that a TELCOM limit? The reason I ask is because
> when running virtual T with TS-DOS, I notice that the buffer can go to 255.
> Or at least the byte which holds the buffer size.
>
>
In my experience I've found that
John, Thanks for info. Is that a TELCOM limit? The reason I ask is because when
running virtual T with TS-DOS, I notice that the buffer can go to 255. Or at
least the byte which holds the buffer size.
Kurt
On Monday, October 17, 2016 11:36 AM, John R. Hogerhuis
wrote:
On Mon, Oct
On Mon, Oct 17, 2016 at 7:14 AM, Kurt McCullum
wrote:
> Even though the buffer is 256 bytes in size, TELCOM sends the XON/XOFF
> commands when the buffer is only slightly full, so I have had to block the
> sending of the data in small packets and check for XOFF.
>
>
>
The serial receive buffer is
Just to let everybody know, I have uploaded a new version of mComm to the
members file area. The TPDD side of the program is unchanged. Added to this
version of a button that starts a virtual modem service. So your classic AT
commands will work do 'dial' a Telnet server. SSL connections are supp
Cool!
On Oct 14, 2016 5:32 PM, "Kurt McCullum" wrote:
> Just a heads up to any who are interested. A new version of mComm for
> Android devices is in the final testing stages. This version adds a virtual
> modem. That means you can go to TELCOM and ‘Dial’ a telnet bbs with ATDT
> URL:PORT. I jus
Just a heads up to any who are interested. A new version of mComm for
Android devices is in the final testing stages. This version adds a virtual
modem. That means you can go to TELCOM and 'Dial' a telnet bbs with ATDT
URL:PORT. I just need to kick the tires a bit more, write up some
documentation,
14 matches
Mail list logo
