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

Ken, Were you able to trace down the mystery opcode? I was going through the "Software Manual for Portable Disk Drive (26-3808)" and I have not come up with anything. I did add your code to tpdd.py on my end but try as I may, I have yet to uncover a condition where regular TS-DOS sends out that

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 QueryExtend

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 Pettit

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 reque

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 TPDD_REQ

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 DLP

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 logs.

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 cou

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 w

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 s

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 the

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 runn

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

> On Apr 1, 2020, at 10:13 AM, Ken Pettit wrote: > Hi Joshua, > > Okay, this is good information. Then I need to figure out what is different > between NEWDOS autobaud and regular TS-DOS autobaud. To add some further twists to this: if I have DOS-ON and issue a LFILES command, I get a hang,

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

Joshua, Still somewhat of a mystery. It's something in TS-DOS with the DOS-ON active. It doesn't happen on the NEC when in Bank 1 (Banks 2 and 3 have the problem). Not sure about the 200. But definitely the 102 has the issue. Keep in mind that I doubt the creators of TS-DOS intended it to be us

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

This is what I managed to cobble together when I did my delayed versions. (Keep in mind I could be wrong) TS-DOS uses the M1 / FDC switching to get the directory name. Since a real TPDD will not respond to switching into FDC mode, TS-DOS has to have a timeout. It's in that area where adding a d

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

Hi Joshua, Okay, this is good information. Then I need to figure out what is different between NEWDOS autobaud and regular TS-DOS autobaud. Ken On 4/1/20 10:03 AM, Joshua O'Keefe wrote: On Wed, Apr 1, 2020 at 9:51 AM Ken Pettit > wrote: Yeah, I was planning t

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

On Wed, Apr 1, 2020 at 9:51 AM Ken Pettit wrote: > Yeah, I was planning to try it tonight also using NEWDOS on the M100 to > see if I can replicate the issue Joshua was having. > Hi Ken, I built a little BASIC wrapper to set COM:98n1d (akin to what John used for WiModem dialiing, but without th

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

Yeah, I was planning to try it tonight also using NEWDOS on the M100 to see if I can replicate the issue Joshua was having. Ken On 4/1/20 9:35 AM, Gregory McGill wrote: awesome! On Wed, Apr 1, 2020 at 9:07 AM Joshua O'Keefe mailto:maj...@nachomountain.com>> wrote: Thanks, Kurt, I look

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

Hey Kurt, That's okay, unless you just want to. I found them in /usr/share/mcomm Ken On 4/1/20 9:41 AM, Kurt McCullum wrote: the .deb is for the Debian package installer. I can upload the individual files in a zip if that is more helpful. On Wed, Apr 1, 2020, at 9:02 AM, Ken Pettit wrote:

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

the .deb is for the Debian package installer. I can upload the individual files in a zip if that is more helpful. On Wed, Apr 1, 2020, at 9:02 AM, Ken Pettit wrote: > Hey Kurt, > > Thanks! Umm, where is the .deb trying to install this? > > Ken > > > On 4/1/20 8:36 AM, Kurt McCullum wrote: >

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

awesome! On Wed, Apr 1, 2020 at 9:07 AM Joshua O'Keefe wrote: > Thanks, Kurt, I look forward to trying this out tonight. Just curious, > what wound up being behind that EOF issue you were talking about earlier? > I love a good debugging story. > > On Apr 1, 2020, at 8:36 AM, Kurt McCullum wrot

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

Hi Ken, Here's what the guts of the deb look like: $ dpkg -c mComm_1.2_all.deb drwxrwxr-x kurt/kurt 0 2020-04-01 08:04 ./ drwxrwxr-x kurt/kurt 0 2020-04-01 07:27 ./usr/ drwxrwxr-x kurt/kurt 0 2020-04-01 07:27 ./usr/bin/ -rwxrwxr-x kurt/kurt 142 2020-04-01 07:27 ./us

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

Thanks, Kurt, I look forward to trying this out tonight. Just curious, what wound up being behind that EOF issue you were talking about earlier? I love a good debugging story. > On Apr 1, 2020, at 8:36 AM, Kurt McCullum wrote: > >  > For those interested, I just uploaded an installer for a

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

Hey Kurt, Thanks! Umm, where is the .deb trying to install this? Ken On 4/1/20 8:36 AM, Kurt McCullum wrote: For those interested, I just uploaded an installer for a version of mComm written in Python. It is contained in a .deb install package. This should install on most flavors of Linux. I

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

On 4/1/20 11:36 AM, Kurt McCullum wrote: For those interested, I just uploaded an installer for a version of mComm written in Python. It is contained in a .deb install package. This should install on most flavors of Linux. It was built using Linux Mint. You will need to set permissions to what

[M100] Python (Linux) version of mComm

For those interested, I just uploaded an installer for a version of mComm written in Python. It is contained in a .deb install package. This should install on most flavors of Linux. It was built using Linux Mint. You will need to set permissions to whatever serial port you will be using. I used