Re: [M100] Python (Linux) version of mComm

Ken, Thanks for all the feedback and changes. One of the main reasons for converting the code to Python was for this was to give users the ability to easily tweak it when things like this are found. Glad to see it's working. Kurt On Thu, Apr 2, 2020, at 4:49 PM, Ken Pettit wrote: > Hey Kurt,

Re: [M100] Python (Linux) version of mComm

Hi John, Yes, 35 and 49 are the "mystery" and 14 is what I added for QueryExtended. Ken On 4/2/20 5:00 PM, John R. Hogerhuis wrote: Yes, I meant not supported by LaddieAlpha. By the way my source shows TS-DOS mystery commands for 14, 35, 49 (all decimal) But you are using 14 as

Re: [M100] Python (Linux) version of mComm

Yes, I meant not supported by LaddieAlpha. By the way my source shows TS-DOS mystery commands for 14, 35, 49 (all decimal) But you are using 14 as QueryExtended. I guess I have that wrong and it's not a mystery it was always a NEWDOS extension. -- John. On Thu, Apr 2, 2020 at 4:53 PM Ken

Re: [M100] Python (Linux) version of mComm

On 4/2/20 4:41 PM, John R. Hogerhuis wrote: On Thu, Apr 2, 2020 at 3:57 PM Ken Pettit > wrote: John, In DLPilot, LaddieCon, DLPlus, etc., what do you do if you get an opcode that is not supported? Ken Looks like LaddieAlpha outputs "Unknown

Re: [M100] Python (Linux) version of mComm

Hey Kurt, Yes, they are in TS-DOS. I need to track down the conditions under which they are sent. The response for them is: 12h 01h 00h checksum I also have added extended TPDD feature support using opcodes: // Expanded requests for potential future Model "T" DOS usage #define

Re: [M100] WiModem TPDD

Yup yup. Just need a male to male adapter. On Thu, Apr 2, 2020 at 2:47 PM Joshua O'Keefe wrote: > > > On Sun, Mar 29, 2020 at 1:21 PM John R. Hogerhuis > wrote: > >> On Sun, Mar 29, 2020 at 11:36 AM Stephen Adolph >> wrote: >> >>> 1) in an M100, is a genderchanger all that is needed? or do

Re: [M100] Python (Linux) version of mComm

Hey John, Yeah, what I added to my local copy of mComm: Response: 12h 01h 36h checksum Where 36h is the error code for "invalid parameter". Ken On 4/2/20 4:41 PM, John R. Hogerhuis wrote: On Thu, Apr 2, 2020 at 3:57 PM Ken Pettit > wrote: John, In

Re: [M100] Python (Linux) version of mComm

Thanks for testing this Ken. I wasn't even aware of the "mystery opcodes" prior to your email. I'll add that snipet of code to the next release. Does TS-DOS even use them? I'm not sure I've seen them when trapping for requests I haven't accounted for. I'll have to take another look at my

Re: [M100] Python (Linux) version of mComm

On Thu, Apr 2, 2020 at 3:57 PM Ken Pettit wrote: > John, > > In DLPilot, LaddieCon, DLPlus, etc., what do you do if you get an opcode > that is not supported? > > Ken > > Looks like LaddieAlpha outputs "Unknown request type" but doesn't send anything if it gets an unknown opcode. I suppose I

Re: [M100] Python (Linux) version of mComm

John, In DLPilot, LaddieCon, DLPlus, etc., what do you do if you get an opcode that is not supported? Ken On 4/2/20 3:39 PM, John R. Hogerhuis wrote: I will try to figure out why NEWDOS doesn't timeout if the mystery opcodes have no response. It is unclear what a true TPDD does

Re: [M100] Python (Linux) version of mComm

Looks like mComm is also not happy with the "QueryExtended" opcode I added. This is an opcode in NEWDOS that queryies for higher baud rates, Condensed List, server name, etc. which are all supported in NADSBox FW 1.14 and higher (and used by NEWDOS). These could be implemented in other TPDD

Re: [M100] Python (Linux) version of mComm

> > > > I will try to figure out why NEWDOS doesn't timeout if the mystery > opcodes have no response. It is unclear what a true TPDD does with > these opcodes, or if they can simply be removed from NEWDOS with no > side-effects. > > I seem to recall that for DLPilot, LaddieCon, DLPlus I found

Re: [M100] Python (Linux) version of mComm

Hey Guys (and especially Kurt), I tested NEWDOS using VirtualT by connected to mComm on Ubuntu via two pseudo terminals created with 'socat'. I had to make a couple of minor changes to mComm to get it to run with /dev/pts terminals, but no big deal. I ran into the same issue with NEWDOS

Re: [M100] WiModem TPDD

On Sun, Mar 29, 2020 at 1:21 PM John R. Hogerhuis wrote: > On Sun, Mar 29, 2020 at 11:36 AM Stephen Adolph > wrote: > >> 1) in an M100, is a genderchanger all that is needed? or do you also >> need a null modem? any other considerations? >> > > Gender changer and power, that's it. > Just

Re: [M100] WiModem TPDD

> On Apr 2, 2020, at 11:58 AM, John R. Hogerhuis wrote: > Are you saying that LaddieAlpha is exiting when the connection breaks? > > It shouldn't do that. My test version doesn't do that. > Oh... I think I added a feature for Steve at some point, if you send > LaddieAlpha a newline by itself

Re: [M100] WiModem TPDD

On Thu, Apr 2, 2020 at 11:41 AM Joshua O'Keefe wrote: > > I've set LaddieAlpha up to re-start after the TCP connection closes by > adding a simple while loop around invocation. > Are you saying that LaddieAlpha is exiting when the connection breaks? It shouldn't do that. My test version

Re: [M100] WiModem TPDD

regarding delay; The original request (I think it was from me) was to find a way to tolerate WAN latencies that can be significant, 100msec or more. I think that's where the delay feature shines. I found I needed delay tolerance when going across a service provider routed network. I agree that

Re: [M100] WiModem TPDD

My WiModem232 arrived last night, so I thought I'd provide a bit of a trip report: I'm drawing WiModem power from a pocket size USB battery I had lying around unused. It's a little awkward to splay out on your lap if you're on the couch, but it works! I did have to scrounge around to find a USB

[M100] Just got my 100

Ken Pettit wrote: " You know, I think I actually *was* born with a soldering iron in my hand. Or was it a keyboard? I keep forgetting. Ken " No wonder your mother complained... -CH-