Re: [M100] mcomm

[Kurt McCullum]

Peter,

That's great that you got the cable figured out. Glad it's working for you.

Kurt

On Tue, Dec 19, 2023, at 12:03 PM, Peter Vollan wrote:
> I got my null modem cables sorted out and I now have Mcomm working and 
> communicating on my Windows 8 laptop.
> I figured you might enjoy hearing some good news from me for once. 
> 
> On Sun, 17 Dec 2023 at 16:03, Kurt McCullum  wrote:
>> __
>> Two things to check.
>> First, in device manager what com port is being assigned to the FTDI adapter.
>> Second. What is the pinout of the cable you are using. mcomm is rather picky 
>> on the cable.
>> From the manual
>> 7 Wire Cable
>> PC
>>  
>> Model-T
>> DCD
>>  1 
>> NC
>>  
>>  
>> RX
>>  2 
>> ←
>>  2 
>> TX
>> TX
>>  3 
>> →
>>  3 
>> RX
>> DTR
>>  4 
>> →
>>  6 
>> DSR
>> GND
>>  5 
>> ↔
>>  7 
>> GND
>> DSR
>>  6 
>> ←
>> 20 
>> DTR
>> RTS
>>  7 
>> →
>>  5 
>> CTS
>> CTS
>>  8 
>> ←
>>  4 
>> RTS
>> RI
>>  9 
>> NC
>>  
>>  
>> 
>> On Sun, Dec 17, 2023, at 12:16 PM, Peter Vollan wrote:
>>> And Device Manager says that my FTDI usb to serial adaptor is working 
>>> properly. 
>>> 
>>> On Sun, 17 Dec 2023 at 12:08, Peter Vollan  wrote:
 Mcomm gives me the message:
 Unabled to start service  (<-sic)
 TDD/TELCOM service started
 
 and then TS DOS just says Drive not ready.
 Windows 8 on a Microsoft Surface Pro
 
>> 

Re: [M100] mcomm

[Peter Vollan]

I got my null modem cables sorted out and I now have Mcomm working and
communicating on my Windows 8 laptop.
I figured you might enjoy hearing some good news from me for once.

On Sun, 17 Dec 2023 at 16:03, Kurt McCullum  wrote:

> Two things to check.
> First, in device manager what com port is being assigned to the FTDI
> adapter.
> Second. What is the pinout of the cable you are using. mcomm is rather
> picky on the cable.
> From the manual
> 7 Wire Cable
> PC
>
> Model-T
> DCD
>  1
> NC
>
>
> RX
>  2
> ←
>  2
> TX
> TX
>  3
> →
>  3
> RX
> DTR
>  4
> →
>  6
> DSR
> GND
>  5
> ↔
>  7
> GND
> DSR
>  6
> ←
> 20
> DTR
> RTS
>  7
> →
>  5
> CTS
> CTS
>  8
> ←
>  4
> RTS
> RI
>  9
> NC
>
>
>
> On Sun, Dec 17, 2023, at 12:16 PM, Peter Vollan wrote:
>
> And Device Manager says that my FTDI usb to serial adaptor is working
> properly.
>
> On Sun, 17 Dec 2023 at 12:08, Peter Vollan  wrote:
>
> Mcomm gives me the message:
> Unabled to start service  (<-sic)
> TDD/TELCOM service started
>
> and then TS DOS just says Drive not ready.
> Windows 8 on a Microsoft Surface Pro
>
>
>

Re: [M100] mcomm

[Peter Vollan]

Hey, I sorted out the com port issue, it is on COM5. So now it does not say
"unabled to start service". But I am still getting Drive Not Ready, So I
think I do need another null modem cable.

On Sun, 17 Dec 2023 at 16:03, Kurt McCullum  wrote:

> Two things to check.
> First, in device manager what com port is being assigned to the FTDI
> adapter.
> Second. What is the pinout of the cable you are using. mcomm is rather
> picky on the cable.
> From the manual
> 7 Wire Cable
> PC
>
> Model-T
> DCD
>  1
> NC
>
>
> RX
>  2
> ←
>  2
> TX
> TX
>  3
> →
>  3
> RX
> DTR
>  4
> →
>  6
> DSR
> GND
>  5
> ↔
>  7
> GND
> DSR
>  6
> ←
> 20
> DTR
> RTS
>  7
> →
>  5
> CTS
> CTS
>  8
> ←
>  4
> RTS
> RI
>  9
> NC
>
>
>
> On Sun, Dec 17, 2023, at 12:16 PM, Peter Vollan wrote:
>
> And Device Manager says that my FTDI usb to serial adaptor is working
> properly.
>
> On Sun, 17 Dec 2023 at 12:08, Peter Vollan  wrote:
>
> Mcomm gives me the message:
> Unabled to start service  (<-sic)
> TDD/TELCOM service started
>
> and then TS DOS just says Drive not ready.
> Windows 8 on a Microsoft Surface Pro
>
>
>

Re: [M100] mcomm

[Kurt McCullum]

Two things to check.
First, in device manager what com port is being assigned to the FTDI adapter.
Second. What is the pinout of the cable you are using. mcomm is rather picky on 
the cable. 
>From the manual
7 Wire Cable
PC
 
Model-T
DCD
 1 
NC
 
 
RX
 2 
←
 2 
TX
TX
 3 
→
 3 
RX
DTR
 4 
→
 6 
DSR
GND
 5 
↔
 7 
GND
DSR
 6 
←
20 
DTR
RTS
 7 
→
 5 
CTS
CTS
 8 
←
 4 
RTS
RI
 9 
NC
 
 

On Sun, Dec 17, 2023, at 12:16 PM, Peter Vollan wrote:
> And Device Manager says that my FTDI usb to serial adaptor is working 
> properly. 
> 
> On Sun, 17 Dec 2023 at 12:08, Peter Vollan  wrote:
>> Mcomm gives me the message:
>> Unabled to start service  (<-sic)
>> TDD/TELCOM service started
>> 
>> and then TS DOS just says Drive not ready.
>> Windows 8 on a Microsoft Surface Pro
>> 

Re: [M100] mcomm

[Peter Vollan]

And Device Manager says that my FTDI usb to serial adaptor is working
properly.

On Sun, 17 Dec 2023 at 12:08, Peter Vollan  wrote:

> Mcomm gives me the message:
> Unabled to start service  (<-sic)
> TDD/TELCOM service started
>
> and then TS DOS just says Drive not ready.
> Windows 8 on a Microsoft Surface Pro
>
>

Re: [M100] mcomm for android

[Gregory McGill]

Looking at this on my phone it seems likely to be a permissions issue with
the newer versions of android..

On Thu, Nov 17, 2022 at 7:27 AM Gregory McGill 
wrote:

> I'll let him know since he's no longer on the list
>
> On Thu, Nov 17, 2022 at 4:59 AM Josh Malone  wrote:
>
>> Yeah, also fails to start on Android 12 (October 1) on Samsung Galaxy S20
>>
>> On Wed, Nov 16, 2022, 23:08 Gregory McGill 
>> wrote:
>>
>>> I tried it on 8,9 so far.. android tv boxes I've had around.. I haven't
>>> tried it on a phone yet
>>>
>>>
>>> On Wed, Nov 16, 2022, 6:38 PM Daryn Hanright  wrote:
>>>
 That's cool! What Android versions are you using it with Greg? My
 phones running Android 12 & it still crashes on start like previous.

 On Thu, Nov 17, 2022, 12:51 PM Gregory McGill 
 wrote:

> The new version has been posted to
> http://www.club100.org/memfiles/index.php?direction=&order=&directory=Kurt%20McCullum/mComm%20Android&;
>
> ver 196 now supports newer versions of android and works properly
>
> note: filenames must be valid model 100 filenames, so i had to rename
> files called FILE.100 to FILE.DO to work, if they aren't valid the 100 
> will
> not transfer and get stuck and a reset is required.. (in ts-dos)
>
> Greg
>

Re: [M100] mcomm for android

[Gregory McGill]

I'll let him know since he's no longer on the list

On Thu, Nov 17, 2022 at 4:59 AM Josh Malone  wrote:

> Yeah, also fails to start on Android 12 (October 1) on Samsung Galaxy S20
>
> On Wed, Nov 16, 2022, 23:08 Gregory McGill 
> wrote:
>
>> I tried it on 8,9 so far.. android tv boxes I've had around.. I haven't
>> tried it on a phone yet
>>
>>
>> On Wed, Nov 16, 2022, 6:38 PM Daryn Hanright  wrote:
>>
>>> That's cool! What Android versions are you using it with Greg? My phones
>>> running Android 12 & it still crashes on start like previous.
>>>
>>> On Thu, Nov 17, 2022, 12:51 PM Gregory McGill 
>>> wrote:
>>>
 The new version has been posted to
 http://www.club100.org/memfiles/index.php?direction=&order=&directory=Kurt%20McCullum/mComm%20Android&;

 ver 196 now supports newer versions of android and works properly

 note: filenames must be valid model 100 filenames, so i had to rename
 files called FILE.100 to FILE.DO to work, if they aren't valid the 100 will
 not transfer and get stuck and a reset is required.. (in ts-dos)

 Greg

>>>

Re: [M100] mcomm for android

[Josh Malone]

Yeah, also fails to start on Android 12 (October 1) on Samsung Galaxy S20

On Wed, Nov 16, 2022, 23:08 Gregory McGill  wrote:

> I tried it on 8,9 so far.. android tv boxes I've had around.. I haven't
> tried it on a phone yet
>
>
> On Wed, Nov 16, 2022, 6:38 PM Daryn Hanright  wrote:
>
>> That's cool! What Android versions are you using it with Greg? My phones
>> running Android 12 & it still crashes on start like previous.
>>
>> On Thu, Nov 17, 2022, 12:51 PM Gregory McGill 
>> wrote:
>>
>>> The new version has been posted to
>>> http://www.club100.org/memfiles/index.php?direction=&order=&directory=Kurt%20McCullum/mComm%20Android&;
>>>
>>> ver 196 now supports newer versions of android and works properly
>>>
>>> note: filenames must be valid model 100 filenames, so i had to rename
>>> files called FILE.100 to FILE.DO to work, if they aren't valid the 100 will
>>> not transfer and get stuck and a reset is required.. (in ts-dos)
>>>
>>> Greg
>>>
>>

Re: [M100] mcomm for android

[Gregory McGill]

I tried it on 8,9 so far.. android tv boxes I've had around.. I haven't
tried it on a phone yet


On Wed, Nov 16, 2022, 6:38 PM Daryn Hanright  wrote:

> That's cool! What Android versions are you using it with Greg? My phones
> running Android 12 & it still crashes on start like previous.
>
> On Thu, Nov 17, 2022, 12:51 PM Gregory McGill 
> wrote:
>
>> The new version has been posted to
>> http://www.club100.org/memfiles/index.php?direction=&order=&directory=Kurt%20McCullum/mComm%20Android&;
>>
>> ver 196 now supports newer versions of android and works properly
>>
>> note: filenames must be valid model 100 filenames, so i had to rename
>> files called FILE.100 to FILE.DO to work, if they aren't valid the 100 will
>> not transfer and get stuck and a reset is required.. (in ts-dos)
>>
>> Greg
>>
>

Re: [M100] mcomm for android

[Daryn Hanright]

That's cool! What Android versions are you using it with Greg? My phones
running Android 12 & it still crashes on start like previous.

On Thu, Nov 17, 2022, 12:51 PM Gregory McGill 
wrote:

> The new version has been posted to
> http://www.club100.org/memfiles/index.php?direction=&order=&directory=Kurt%20McCullum/mComm%20Android&;
>
> ver 196 now supports newer versions of android and works properly
>
> note: filenames must be valid model 100 filenames, so i had to rename
> files called FILE.100 to FILE.DO to work, if they aren't valid the 100 will
> not transfer and get stuck and a reset is required.. (in ts-dos)
>
> Greg
>

Re: [M100] mcomm android issue

[Gregory McGill]

oh and vm mode works fine on android 8.1 didn't test on 10

On Wed, Jul 20, 2022 at 7:31 PM Gregory McGill 
wrote:

> Re: android mcomm
> I've tested it now on android 10 and android 8.1 and both fail ..  I can
> load a directory from ts-dos but file transfer just locks up and sending
> tsdos from the mcomm just crashes the program
>
> 181 and 192
>
> also i can do all this fine from windows mcomm on windows 10 for Brian :)
>
> Greg
>
>
>>

Re: [M100] mcomm android issue

[Gregory McGill]

Re: android mcomm
I've tested it now on android 10 and android 8.1 and both fail ..  I can
load a directory from ts-dos but file transfer just locks up and sending
tsdos from the mcomm just crashes the program

181 and 192

also i can do all this fine from windows mcomm on windows 10 for Brian :)

Greg


On Tue, Jul 19, 2022 at 3:06 AM Brian K. White  wrote:

> On 7/18/22 14:40, Peter Vollan wrote:
> > aren't we talking about Android?
>
> Yes, but originally I thought this referred to win10
>
> "any updates for 10?"
>
> Since mComm for windows doesn't work lately either.
>
> --
> bkw
>
>
> >
> > On Sun, 17 Jul 2022 at 18:40, Brian White  > > wrote:
> >
> > In the case of Windows, I made a powershell script for windows if
> > you want to try that.
> >
> > github.com/bkw777/tsend 
> >
> > get TS-DOS.100 from
> > github.com/bkw777/dlplus/tree/master/clients/ts-dos
> > 
> >
> > , and then use laddiealpha for the tpdd server.
> > http://bitchin100.com/wiki/index.php?title=LaddieCon#LaddieAlpha
> > 
> >
> > --
> > bkw
> >
> > On Sun, Jul 17, 2022, 2:36 PM Gregory McGill
> > mailto:arcadeshop...@gmail.com>> wrote:
> >
> > Kurt,
> >
> > any updates for 10?  I am trying to get a current box working
> >
> > Greg
> >
> > On Tue, Mar 2, 2021 at 7:30 PM Kurt McCullum  > > wrote:
> >
> > __
> > Greg,
> >
> > I was able to do some testing with and Android 9 phone. Bad
> > News, it doesn't work on Android 9. I'm not certain as to
> > why but the first giveaway was when I installed it and I got
> > a message that said it was designed for an older version of
> > Android and may not work under 9. I'll have to see what can
> > be done. It may be a matter of upgrading all my code, or
> > just a re-compile with a new target OS. Either way I have
> > some work to do.
> >
> > Just wanted you to know.
> >
> > Kurt
> >
> > On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:
> >> Alright. Should be an easy test now that I have all the
> >> equipment. The only difference will be I am using a phone
> >> rather than a tv box but the OS version will be the same.
> >> I'll let you know what I find.
> >>
> >> Kurt
> >>
> >> On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:
> >>> correct, push ts-dos from mcomm android 181 on a android
> >>> 9 tv box i just got. whenever i hit ok to send the file
> >>> it just seems to crash mcomm and jumps out of it..
> >>>
> >>> On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum
> >>> mailto:ku...@fastmail.com>> wrote:
> >>>
> >>> __
> >>> Not yet Greg, but I did get the cables needed at I
> >>> have access to an android 9 phone. I'll do my best to
> >>> wrestle it out of my wife's hands tonight and test it
> >>> (Not always easy to do). As I recall it was the
> >>> TS-DOS injection you were having issues with.
> >>>
> >>> Kurt
> >>>
> >>>
> >>> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
>  Glad to hear it! I grew up in 1000 oaks, my mom's
>  still in Camarillo at the village
> 
>  lmk if you get a chance to test that newer android
> issue
> 
>  On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum
>  mailto:ku...@fastmail.com>>
> wrote:
> 
>  __
>  Yes, I am finally settled in my new place in
>  Camarillo. Still unpacking but life is back to
>  normal.
> 
>  Kurt
> 
>  On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill
>  wrote:
> > Is it winter yet? :)did you ever escape?
> >
> > Greg
> >
> > On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum
> >  > > wrote:
> >
> > __
> > :) thanks. A lot more body surfing going on
> > rather than web surfing. It will definitely
> > be a summer to remember.
> >
> > On Fri, Jul 31, 2020, at 12:27 PM, John R.
> > Hogerhuis wrote:
> >>

Re: [M100] mcomm android issue

[Brian K. White]

On 7/18/22 14:40, Peter Vollan wrote:

aren't we talking about Android?


Yes, but originally I thought this referred to win10

"any updates for 10?"

Since mComm for windows doesn't work lately either.

--
bkw




On Sun, 17 Jul 2022 at 18:40, Brian White > wrote:


In the case of Windows, I made a powershell script for windows if
you want to try that.

github.com/bkw777/tsend 

get TS-DOS.100 from
github.com/bkw777/dlplus/tree/master/clients/ts-dos


, and then use laddiealpha for the tpdd server.
http://bitchin100.com/wiki/index.php?title=LaddieCon#LaddieAlpha


-- 
bkw


On Sun, Jul 17, 2022, 2:36 PM Gregory McGill
mailto:arcadeshop...@gmail.com>> wrote:

Kurt,

any updates for 10?  I am trying to get a current box working

Greg

On Tue, Mar 2, 2021 at 7:30 PM Kurt McCullum mailto:ku...@fastmail.com>> wrote:

__
Greg,

I was able to do some testing with and Android 9 phone. Bad
News, it doesn't work on Android 9. I'm not certain as to
why but the first giveaway was when I installed it and I got
a message that said it was designed for an older version of
Android and may not work under 9. I'll have to see what can
be done. It may be a matter of upgrading all my code, or
just a re-compile with a new target OS. Either way I have
some work to do.

Just wanted you to know.

Kurt

On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:

Alright. Should be an easy test now that I have all the
equipment. The only difference will be I am using a phone
rather than a tv box but the OS version will be the same.
I'll let you know what I find.

Kurt

On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:

correct, push ts-dos from mcomm android 181 on a android
9 tv box i just got. whenever i hit ok to send the file
it just seems to crash mcomm and jumps out of it..

On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum
mailto:ku...@fastmail.com>> wrote:

__
Not yet Greg, but I did get the cables needed at I
have access to an android 9 phone. I'll do my best to
wrestle it out of my wife's hands tonight and test it
(Not always easy to do). As I recall it was the
TS-DOS injection you were having issues with.

Kurt


On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:

Glad to hear it! I grew up in 1000 oaks, my mom's
still in Camarillo at the village

lmk if you get a chance to test that newer android issue

On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum
mailto:ku...@fastmail.com>> wrote:

__
Yes, I am finally settled in my new place in
Camarillo. Still unpacking but life is back to
normal.

Kurt

On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill
wrote:

Is it winter yet? :)    did you ever escape?

Greg

On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum
mailto:ku...@fastmail.com>> wrote:

__
:) thanks. A lot more body surfing going on
rather than web surfing. It will definitely
be a summer to remember.

On Fri, Jul 31, 2020, at 12:27 PM, John R.
Hogerhuis wrote:

Congratulations to Kurt McCullum on the
list Quote of the Month

"*/I'm still stuck in a beach house with
only one model-t/*"

:-)

-- John.











--
bkw

Re: [M100] mcomm android issue

[Peter Vollan]

aren't we talking about Android?

On Sun, 17 Jul 2022 at 18:40, Brian White  wrote:

> In the case of Windows, I made a powershell script for windows if you want
> to try that.
>
> github.com/bkw777/tsend
>
> get TS-DOS.100 from github.com/bkw777/dlplus/tree/master/clients/ts-dos
>
> , and then use laddiealpha for the tpdd server.
> http://bitchin100.com/wiki/index.php?title=LaddieCon#LaddieAlpha
>
> --
> bkw
>
> On Sun, Jul 17, 2022, 2:36 PM Gregory McGill 
> wrote:
>
>> Kurt,
>>
>> any updates for 10?  I am trying to get a current box working
>>
>> Greg
>>
>> On Tue, Mar 2, 2021 at 7:30 PM Kurt McCullum  wrote:
>>
>>> Greg,
>>>
>>> I was able to do some testing with and Android 9 phone. Bad News, it
>>> doesn't work on Android 9. I'm not certain as to why but the first giveaway
>>> was when I installed it and I got a message that said it was designed for
>>> an older version of Android and may not work under 9. I'll have to see what
>>> can be done. It may be a matter of upgrading all my code, or just a
>>> re-compile with a new target OS. Either way I have some work to do.
>>>
>>> Just wanted you to know.
>>>
>>> Kurt
>>>
>>> On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:
>>>
>>> Alright. Should be an easy test now that I have all the equipment. The
>>> only difference will be I am using a phone rather than a tv box but the OS
>>> version will be the same. I'll let you know what I find.
>>>
>>> Kurt
>>>
>>> On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:
>>>
>>> correct, push ts-dos from mcomm android 181 on a android 9 tv box i just
>>> got. whenever i hit ok to send the file it just seems to crash mcomm and
>>> jumps out of it..
>>>
>>> On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:
>>>
>>>
>>> Not yet Greg, but I did get the cables needed at I have access to an
>>> android 9 phone. I'll do my best to wrestle it out of my wife's hands
>>> tonight and test it (Not always easy to do). As I recall it was the TS-DOS
>>> injection you were having issues with.
>>>
>>> Kurt
>>>
>>>
>>> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
>>>
>>> Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at
>>> the village
>>>
>>> lmk if you get a chance to test that newer android issue
>>>
>>> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum 
>>> wrote:
>>>
>>>
>>> Yes, I am finally settled in my new place in Camarillo. Still unpacking
>>> but life is back to normal.
>>>
>>> Kurt
>>>
>>> On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
>>>
>>> Is it winter yet? :)did you ever escape?
>>>
>>> Greg
>>>
>>> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum 
>>> wrote:
>>>
>>>
>>> :) thanks. A lot more body surfing going on rather than web surfing. It
>>> will definitely be a summer to remember.
>>>
>>> On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
>>>
>>> Congratulations to Kurt McCullum on the list Quote of the Month
>>>
>>> "*I'm still stuck in a beach house with only one model-t*"
>>>
>>> :-)
>>>
>>> -- John.
>>>
>>>
>>>
>>>
>>>
>>>

Re: [M100] mcomm android issue

[Gregory McGill]

yeah im trying to set up an android based tpdd with a tv box..  i grabbed
one with older android on it see if that works


On Sun, Jul 17, 2022 at 6:40 PM Brian White  wrote:

> In the case of Windows, I made a powershell script for windows if you want
> to try that.
>
> github.com/bkw777/tsend
>
> get TS-DOS.100 from github.com/bkw777/dlplus/tree/master/clients/ts-dos
>
> , and then use laddiealpha for the tpdd server.
> http://bitchin100.com/wiki/index.php?title=LaddieCon#LaddieAlpha
>
> --
> bkw
>
> On Sun, Jul 17, 2022, 2:36 PM Gregory McGill 
> wrote:
>
>> Kurt,
>>
>> any updates for 10?  I am trying to get a current box working
>>
>> Greg
>>
>> On Tue, Mar 2, 2021 at 7:30 PM Kurt McCullum  wrote:
>>
>>> Greg,
>>>
>>> I was able to do some testing with and Android 9 phone. Bad News, it
>>> doesn't work on Android 9. I'm not certain as to why but the first giveaway
>>> was when I installed it and I got a message that said it was designed for
>>> an older version of Android and may not work under 9. I'll have to see what
>>> can be done. It may be a matter of upgrading all my code, or just a
>>> re-compile with a new target OS. Either way I have some work to do.
>>>
>>> Just wanted you to know.
>>>
>>> Kurt
>>>
>>> On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:
>>>
>>> Alright. Should be an easy test now that I have all the equipment. The
>>> only difference will be I am using a phone rather than a tv box but the OS
>>> version will be the same. I'll let you know what I find.
>>>
>>> Kurt
>>>
>>> On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:
>>>
>>> correct, push ts-dos from mcomm android 181 on a android 9 tv box i just
>>> got. whenever i hit ok to send the file it just seems to crash mcomm and
>>> jumps out of it..
>>>
>>> On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:
>>>
>>>
>>> Not yet Greg, but I did get the cables needed at I have access to an
>>> android 9 phone. I'll do my best to wrestle it out of my wife's hands
>>> tonight and test it (Not always easy to do). As I recall it was the TS-DOS
>>> injection you were having issues with.
>>>
>>> Kurt
>>>
>>>
>>> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
>>>
>>> Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at
>>> the village
>>>
>>> lmk if you get a chance to test that newer android issue
>>>
>>> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum 
>>> wrote:
>>>
>>>
>>> Yes, I am finally settled in my new place in Camarillo. Still unpacking
>>> but life is back to normal.
>>>
>>> Kurt
>>>
>>> On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
>>>
>>> Is it winter yet? :)did you ever escape?
>>>
>>> Greg
>>>
>>> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum 
>>> wrote:
>>>
>>>
>>> :) thanks. A lot more body surfing going on rather than web surfing. It
>>> will definitely be a summer to remember.
>>>
>>> On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
>>>
>>> Congratulations to Kurt McCullum on the list Quote of the Month
>>>
>>> "*I'm still stuck in a beach house with only one model-t*"
>>>
>>> :-)
>>>
>>> -- John.
>>>
>>>
>>>
>>>
>>>
>>>

Re: [M100] mcomm android issue

[Brian White]

In the case of Windows, I made a powershell script for windows if you want
to try that.

github.com/bkw777/tsend

get TS-DOS.100 from github.com/bkw777/dlplus/tree/master/clients/ts-dos

, and then use laddiealpha for the tpdd server.
http://bitchin100.com/wiki/index.php?title=LaddieCon#LaddieAlpha

-- 
bkw

On Sun, Jul 17, 2022, 2:36 PM Gregory McGill 
wrote:

> Kurt,
>
> any updates for 10?  I am trying to get a current box working
>
> Greg
>
> On Tue, Mar 2, 2021 at 7:30 PM Kurt McCullum  wrote:
>
>> Greg,
>>
>> I was able to do some testing with and Android 9 phone. Bad News, it
>> doesn't work on Android 9. I'm not certain as to why but the first giveaway
>> was when I installed it and I got a message that said it was designed for
>> an older version of Android and may not work under 9. I'll have to see what
>> can be done. It may be a matter of upgrading all my code, or just a
>> re-compile with a new target OS. Either way I have some work to do.
>>
>> Just wanted you to know.
>>
>> Kurt
>>
>> On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:
>>
>> Alright. Should be an easy test now that I have all the equipment. The
>> only difference will be I am using a phone rather than a tv box but the OS
>> version will be the same. I'll let you know what I find.
>>
>> Kurt
>>
>> On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:
>>
>> correct, push ts-dos from mcomm android 181 on a android 9 tv box i just
>> got. whenever i hit ok to send the file it just seems to crash mcomm and
>> jumps out of it..
>>
>> On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:
>>
>>
>> Not yet Greg, but I did get the cables needed at I have access to an
>> android 9 phone. I'll do my best to wrestle it out of my wife's hands
>> tonight and test it (Not always easy to do). As I recall it was the TS-DOS
>> injection you were having issues with.
>>
>> Kurt
>>
>>
>> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
>>
>> Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at
>> the village
>>
>> lmk if you get a chance to test that newer android issue
>>
>> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:
>>
>>
>> Yes, I am finally settled in my new place in Camarillo. Still unpacking
>> but life is back to normal.
>>
>> Kurt
>>
>> On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
>>
>> Is it winter yet? :)did you ever escape?
>>
>> Greg
>>
>> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum 
>> wrote:
>>
>>
>> :) thanks. A lot more body surfing going on rather than web surfing. It
>> will definitely be a summer to remember.
>>
>> On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
>>
>> Congratulations to Kurt McCullum on the list Quote of the Month
>>
>> "*I'm still stuck in a beach house with only one model-t*"
>>
>> :-)
>>
>> -- John.
>>
>>
>>
>>
>>
>>

Re: [M100] mcomm android issue

[Peter Vollan]

mcomm has not been working for me. In TS DOS the directory is empty except
for an extension, something like .TL


On Sun, 17 Jul 2022 at 11:36, Gregory McGill 
wrote:

> Kurt,
>
> any updates for 10?  I am trying to get a current box working
>
> Greg
>
> On Tue, Mar 2, 2021 at 7:30 PM Kurt McCullum  wrote:
>
>> Greg,
>>
>> I was able to do some testing with and Android 9 phone. Bad News, it
>> doesn't work on Android 9. I'm not certain as to why but the first giveaway
>> was when I installed it and I got a message that said it was designed for
>> an older version of Android and may not work under 9. I'll have to see what
>> can be done. It may be a matter of upgrading all my code, or just a
>> re-compile with a new target OS. Either way I have some work to do.
>>
>> Just wanted you to know.
>>
>> Kurt
>>
>> On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:
>>
>> Alright. Should be an easy test now that I have all the equipment. The
>> only difference will be I am using a phone rather than a tv box but the OS
>> version will be the same. I'll let you know what I find.
>>
>> Kurt
>>
>> On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:
>>
>> correct, push ts-dos from mcomm android 181 on a android 9 tv box i just
>> got. whenever i hit ok to send the file it just seems to crash mcomm and
>> jumps out of it..
>>
>> On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:
>>
>>
>> Not yet Greg, but I did get the cables needed at I have access to an
>> android 9 phone. I'll do my best to wrestle it out of my wife's hands
>> tonight and test it (Not always easy to do). As I recall it was the TS-DOS
>> injection you were having issues with.
>>
>> Kurt
>>
>>
>> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
>>
>> Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at
>> the village
>>
>> lmk if you get a chance to test that newer android issue
>>
>> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:
>>
>>
>> Yes, I am finally settled in my new place in Camarillo. Still unpacking
>> but life is back to normal.
>>
>> Kurt
>>
>> On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
>>
>> Is it winter yet? :)did you ever escape?
>>
>> Greg
>>
>> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum 
>> wrote:
>>
>>
>> :) thanks. A lot more body surfing going on rather than web surfing. It
>> will definitely be a summer to remember.
>>
>> On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
>>
>> Congratulations to Kurt McCullum on the list Quote of the Month
>>
>> "*I'm still stuck in a beach house with only one model-t*"
>>
>> :-)
>>
>> -- John.
>>
>>
>>
>>
>>
>>

Re: [M100] mcomm android issue

[Gregory McGill]

Kurt,

any updates for 10?  I am trying to get a current box working

Greg

On Tue, Mar 2, 2021 at 7:30 PM Kurt McCullum  wrote:

> Greg,
>
> I was able to do some testing with and Android 9 phone. Bad News, it
> doesn't work on Android 9. I'm not certain as to why but the first giveaway
> was when I installed it and I got a message that said it was designed for
> an older version of Android and may not work under 9. I'll have to see what
> can be done. It may be a matter of upgrading all my code, or just a
> re-compile with a new target OS. Either way I have some work to do.
>
> Just wanted you to know.
>
> Kurt
>
> On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:
>
> Alright. Should be an easy test now that I have all the equipment. The
> only difference will be I am using a phone rather than a tv box but the OS
> version will be the same. I'll let you know what I find.
>
> Kurt
>
> On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:
>
> correct, push ts-dos from mcomm android 181 on a android 9 tv box i just
> got. whenever i hit ok to send the file it just seems to crash mcomm and
> jumps out of it..
>
> On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:
>
>
> Not yet Greg, but I did get the cables needed at I have access to an
> android 9 phone. I'll do my best to wrestle it out of my wife's hands
> tonight and test it (Not always easy to do). As I recall it was the TS-DOS
> injection you were having issues with.
>
> Kurt
>
>
> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
>
> Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at
> the village
>
> lmk if you get a chance to test that newer android issue
>
> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:
>
>
> Yes, I am finally settled in my new place in Camarillo. Still unpacking
> but life is back to normal.
>
> Kurt
>
> On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
>
> Is it winter yet? :)did you ever escape?
>
> Greg
>
> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum  wrote:
>
>
> :) thanks. A lot more body surfing going on rather than web surfing. It
> will definitely be a summer to remember.
>
> On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
>
> Congratulations to Kurt McCullum on the list Quote of the Month
>
> "*I'm still stuck in a beach house with only one model-t*"
>
> :-)
>
> -- John.
>
>
>
>
>
>

Re: [M100] mComm

[Peter Vollan]

Sorry, that is a .TR extension. It was working before. I think it may have
something to do with the microSD card I tried to install.

On Fri, 28 Jan 2022 at 14:38, Peter Vollan  wrote:

> Using mComm on my Android tablet and TS-DOS, all of the files are now
> listing only as blank file names all with a .TL extension.
>

Re: [M100] Mcomm

[jonathan.y...@telia.com]

Hello,
I'm pretty sure I ran mcomm on my Nokia 7 plus which is running android 10 
right now, but I can't be 100% sure it did an update since I last connected.  
I'll try again to see
Jonathan
Ursprungligt meddelande
Från : d...@planetnz.com
Datum : 2021-10-22 - 02:49 (CEST)
Till : m...@bitchin100.com
Ämne : Re: [M100] Mcomm
 Yeah am pretty sure it works only on Android 8 (ish).
 
  
 
 
  It does the same thing on my Android 11 phone as you Peter.
 
 
  On Fri, Oct 22, 2021, 11:29 AM Peter Vollan <
  dprogra...@gmail.com> wrote:
  
 
 
  
   Android 11, ELITE T8 Tablet.
  
  
  
   
On Thu, 21 Oct 2021 at 15:09, Gregory McGill <
arcadeshop...@gmail.com> wrote:

   
   

 what version of android?  I had trouble earlier with a tv android box and 
one of the newer versions as well
 
  > Trying to push ts-dos from 
  mcomm android 181 on a android 9 tv box i just got. whenever i hit ok to 
send the file it just seems to crash 
  mcomm and jumps out of it.. 
 



 
  On Thu, Oct 21, 2021 at 1:04 PM Peter Vollan <
  dprogra...@gmail.com> wrote:
  
 
 
  
   Trying to run Mcomm on my Android tablet, it just keeps saying the app 
has stopped.
  
 

   
  
 

Re: [M100] Mcomm

[Daryn Hanright]

Yeah am pretty sure it works only on Android 8 (ish).

It does the same thing on my Android 11 phone as you Peter.

On Fri, Oct 22, 2021, 11:29 AM Peter Vollan  wrote:

> Android 11, ELITE T8 Tablet.
>
> On Thu, 21 Oct 2021 at 15:09, Gregory McGill 
> wrote:
>
>> what version of android?  I had trouble earlier with a tv android box and
>> one of the newer versions as well
>> > Trying to push ts-dos from mcomm android 181 on a android 9 tv box i
>> just got. whenever i hit ok to send the file it just seems to crash mcomm and
>> jumps out of it..
>>
>> On Thu, Oct 21, 2021 at 1:04 PM Peter Vollan 
>> wrote:
>>
>>> Trying to run Mcomm on my Android tablet, it just keeps saying the app
>>> has stopped.
>>>
>>

Re: [M100] Mcomm

[Peter Vollan]

Android 11, ELITE T8 Tablet.

On Thu, 21 Oct 2021 at 15:09, Gregory McGill 
wrote:

> what version of android?  I had trouble earlier with a tv android box and
> one of the newer versions as well
> > Trying to push ts-dos from mcomm android 181 on a android 9 tv box i
> just got. whenever i hit ok to send the file it just seems to crash mcomm and
> jumps out of it..
>
> On Thu, Oct 21, 2021 at 1:04 PM Peter Vollan  wrote:
>
>> Trying to run Mcomm on my Android tablet, it just keeps saying the app
>> has stopped.
>>
>

Re: [M100] Mcomm

[Gregory McGill]

what version of android?  I had trouble earlier with a tv android box and
one of the newer versions as well
> Trying to push ts-dos from mcomm android 181 on a android 9 tv box i just
got. whenever i hit ok to send the file it just seems to crash mcomm and
jumps out of it..

On Thu, Oct 21, 2021 at 1:04 PM Peter Vollan  wrote:

> Trying to run Mcomm on my Android tablet, it just keeps saying the app has
> stopped.
>

Re: [M100] mcomm

[Brian K. White]

On 8/24/21 12:16 AM, Peter Vollan wrote:

I did everything you said. Now, how do I get it to run?


Update from Mint 17.3 to 20.2

or

Read that error message and dig into the mcomm code and find the spot 
where some function id being handed a string data type when it wants a 
bytes data type, and modify the code as necessary to essentially 
backport mcomm to the older version of python and pyserial.



Ok you may think I was joking or being inconsiderate, but in fact that 
is the sincere advice, not only in general, but specifically to address 
this problem.


Last time you said this:
https://www.mail-archive.com/m100@lists.bitchin100.com/msg14268.html

That shows 3 things:
1: You did somehow get python 3.5 installed.
2: That did get you past your original error. (it just ran into some 
other error next)

3: mcomm ended up loading some files from
  /usr/lib/python3/
  and some files from
  /usr/lib/python3.5/

Those two directories might be the same (python3 might be a symlink to 
python3.5), or they might be different. The python3 directory might be 
full of python-3.4 files.
It *looks* like the program ended up loading files from two different 
versions of python. But even if both paths were really 3.5, the next 
step is still the same anyway...


The error message looks like an error in the mcomm code, but since I 
don't have any such error on an even newer version of python, that 
suggests the code is fine, it just needs some newer version of python 
than 3.5. Definitely 3.8.6 is ok, but probably there is some version 
between 3.5. and 3.8.6 where it starts working.


You could try searching for newer python packages to install, but no one 
is going to have python from today compiled for mint from 5 years ago. I 
just spent a few minutes looking and didn't find anything. But I don't 
use Mint myself so I don't know all the likely places to look. Can you 
just install debian or ubuntu packages on mint? I don't know but I would 
not assume that.


You could try building python from source. The directions are actually 
short and simple, it might "just work", but I wouldn't hold my breath on 
that. ;)


I have no idea where you can find a newer version of python for mint 
17.3. mint 20.2 yes, 17.3? no idea. But you can get a current python for 
the current mint no problem.


You could try the newer mint from a live usb thumb drive without 
actually installing just to see if it will actually resolve the problem.


Other options, maybe pyenv ? I've never used it, but people suggest it 
as a way to run different versions of python

https://github.com/pyenv/pyenv/wiki
I do not recommend it. I recommend update your OS to current.

--
bkw






On Mon, 23 Aug 2021 at 18:23, Daryl Tester 
> wrote:


Peter, I responded to this earlier this month.  To quote:

> Earlier, Peter Vollan wrote:
>
>> Do I have the wrong type of Python? I run Mint 17.3.
>
> According to the interwebz, default Python for Mint 17.3 is
Python 3.4, and the traceback
> "SyntaxError: can use starred expression only as assignment
target" is specific to
> < Python 3.5, so yeah, you'll need to get a later version.  See:
>

>
> This does mean you'll need to invoke your script specifically
with "python3.5 ...".


On 24/8/21 10:11 am, Peter Vollan wrote:
>   When I invoke mcomm with "mcomm" at the command line, it calls
the following script:
>
> #!/usr/bin/python3
> """ Launch mcomm
> """
> import subprocess
> import sys
> subprocess.call(["python3", "/usr/share/mcomm/mcomm.py",
*sys.argv[1:]])
>
> ...which yields the following error message:
>
>   File "/usr/bin/mcomm", line 6
>      subprocess.call(["python3", "/usr/share/mcomm/mcomm.py",
*sys.argv[1:]])
>     ^
> SyntaxError: can use starred expression only as assignment target
>
> Sorry to bother everyone with this, I'm sure it is something
simple about python. My python3 is 3.4.3
>

Re: [M100] mcomm

[Daryl Tester]

On 24/8/21 1:46 pm, Peter Vollan wrote:


I did everything you said. Now, how do I get it to run?


What exactly did you do?  The last step of my instructions said:


This does mean you'll need to invoke your script specifically with "python3.5 
...".


Did you try this? If if failed, please say why it failed.  I can't see your 
screen
from here.

In detail:

You need to find where mcomm lives, and invoke it with python3.5.  There are
other ways to fry this fish, but you need to ensure that this step works first.
At a pinch (because my Linux environment is not your Linux environment), try:

$ python3.5 $(which mcomm)

(that is if mcomm is called mcomm, and not mcomm.py - if it is invoked as 
mcomm.py,
please change the appropriate text after the which command).

Cheers,
  --dt


On Mon, 23 Aug 2021 at 18:23, Daryl Tester mailto:dt-m...@handcraftedcomputers.com.au>> wrote:

Peter, I responded to this earlier this month.  To quote:

 > Earlier, Peter Vollan wrote:
 >
 >> Do I have the wrong type of Python? I run Mint 17.3.
 >
 > According to the interwebz, default Python for Mint 17.3 is Python 3.4, 
and the traceback
 > "SyntaxError: can use starred expression only as assignment target" is 
specific to
 > < Python 3.5, so yeah, you'll need to get a later version.  See:
 > 
>
 > This does mean you'll need to invoke your script specifically with "python3.5 
...".


On 24/8/21 10:11 am, Peter Vollan wrote:
 >   When I invoke mcomm with "mcomm" at the command line, it calls the 
following script:
 >
 > #!/usr/bin/python3
 > """ Launch mcomm
 > """
 > import subprocess
 > import sys
 > subprocess.call(["python3", "/usr/share/mcomm/mcomm.py", *sys.argv[1:]])
 >
 > ...which yields the following error message:
 >
 >   File "/usr/bin/mcomm", line 6
 >      subprocess.call(["python3", "/usr/share/mcomm/mcomm.py", 
*sys.argv[1:]])
 >                                                              ^
 > SyntaxError: can use starred expression only as assignment target
 >
 > Sorry to bother everyone with this, I'm sure it is something simple 
about python. My python3 is 3.4.3
 >

Re: [M100] mcomm

[Peter Vollan]

I did everything you said. Now, how do I get it to run?


On Mon, 23 Aug 2021 at 18:23, Daryl Tester <
dt-m...@handcraftedcomputers.com.au> wrote:

> Peter, I responded to this earlier this month.  To quote:
>
> > Earlier, Peter Vollan wrote:
> >
> >> Do I have the wrong type of Python? I run Mint 17.3.
> >
> > According to the interwebz, default Python for Mint 17.3 is Python 3.4,
> and the traceback
> > "SyntaxError: can use starred expression only as assignment target" is
> specific to
> > < Python 3.5, so yeah, you'll need to get a later version.  See:
> > <
> https://stackoverflow.com/questions/34372731/installing-python-3-5-on-linux-mint-17-3
> >
> > This does mean you'll need to invoke your script specifically with
> "python3.5 ...".
>
>
> On 24/8/21 10:11 am, Peter Vollan wrote:
> >   When I invoke mcomm with "mcomm" at the command line, it calls the
> following script:
> >
> > #!/usr/bin/python3
> > """ Launch mcomm
> > """
> > import subprocess
> > import sys
> > subprocess.call(["python3", "/usr/share/mcomm/mcomm.py", *sys.argv[1:]])
> >
> > ...which yields the following error message:
> >
> >   File "/usr/bin/mcomm", line 6
> >  subprocess.call(["python3", "/usr/share/mcomm/mcomm.py",
> *sys.argv[1:]])
> >  ^
> > SyntaxError: can use starred expression only as assignment target
> >
> > Sorry to bother everyone with this, I'm sure it is something simple
> about python. My python3 is 3.4.3
> >
>

Re: [M100] mcomm

[Brian K. White]

From March when you asked the same question:

https://www.mail-archive.com/m100@lists.bitchin100.com/msg14216.html

You need python 3.5 or later, not 3.4
And you had some other problem with your pyserial module, like maybe 
that needs to be updated too.


Welcome to python.

--
bkw



On 8/23/21 8:41 PM, Peter Vollan wrote:
  When I invoke mcomm with "mcomm" at the command line, it calls the 
following script:


#!/usr/bin/python3
""" Launch mcomm
"""
import subprocess
import sys
subprocess.call(["python3", "/usr/share/mcomm/mcomm.py", *sys.argv[1:]])

...which yields the following error message:

  File "/usr/bin/mcomm", line 6
     subprocess.call(["python3", "/usr/share/mcomm/mcomm.py", 
*sys.argv[1:]])

                                                             ^
SyntaxError: can use starred expression only as assignment target

Sorry to bother everyone with this, I'm sure it is something simple 
about python. My python3 is 3.4.3

Re: [M100] mcomm

[Daryl Tester]

Peter, I responded to this earlier this month.  To quote:


Earlier, Peter Vollan wrote:


Do I have the wrong type of Python? I run Mint 17.3.


According to the interwebz, default Python for Mint 17.3 is Python 3.4, and the 
traceback
"SyntaxError: can use starred expression only as assignment target" is specific 
to
< Python 3.5, so yeah, you'll need to get a later version.  See:

This does mean you'll need to invoke your script specifically with "python3.5 
...".



On 24/8/21 10:11 am, Peter Vollan wrote:

  When I invoke mcomm with "mcomm" at the command line, it calls the following 
script:

#!/usr/bin/python3
""" Launch mcomm
"""
import subprocess
import sys
subprocess.call(["python3", "/usr/share/mcomm/mcomm.py", *sys.argv[1:]])

...which yields the following error message:

  File "/usr/bin/mcomm", line 6
     subprocess.call(["python3", "/usr/share/mcomm/mcomm.py", *sys.argv[1:]])
                                                             ^
SyntaxError: can use starred expression only as assignment target

Sorry to bother everyone with this, I'm sure it is something simple about 
python. My python3 is 3.4.3

Re: [M100] mComm

[Daryl Tester]

On 13/8/21 9:59 am, Scott McDonnell wrote:


Type "python --version" in the terminal to check which version you have 
installed.


Note that on Ubuntu/other Debian derived systems (possibly others), "python" is 
typically
a symbolic link to a default installed python, and typically on those systems 
defaults to 2,
*even* if 3 is installed (which it can be, Python versions can coexist side by 
side without
issue).  The upshot is, you may been to run "python3 --version", and even then 
that may
not give you the max version of Python (although unless you're a developer, 
you'll probably
only have one of each, at best).

$ ls -l `which python`
lrwxrwxrwx 1 root root 9 Jul 15  2017 /usr/bin/python -> python2.7
$ ls -l `which python2`
lrwxrwxrwx 1 root root 9 Jul 15  2017 /usr/bin/python2 -> python2.7
$ ls -l `which python3`
lrwxrwxrwx 1 root root 9 Jul 15  2017 /usr/bin/python3 -> python3.5

(yeah yeah, backticks - I'm old, get off my lawn!).

Earlier, Peter Vollan wrote:


Do I have the wrong type of Python? I run Mint 17.3.


According to the interwebz, default Python for Mint 17.3 is Python 3.4, and the 
traceback
"SyntaxError: can use starred expression only as assignment target" is specific 
to
< Python 3.5, so yeah, you'll need to get a later version.  See:

This does mean you'll need to invoke your script specifically with "python3.5 
...".

Cheers,
  --dt

Re: [M100] mComm

[Scott McDonnell]

Type "python --version" in the terminal to check which version you have 
installed.I believe python 3 is required.If it doesn't say you have python 3, 
you will need to install it.I am afraid that is the extent of my experience 
with the python version of mcomm. So hopefully someone else can help you if the 
above does not.
 Original message From: Peter Vollan  
Date: 8/11/21  12:33 AM  (GMT-05:00) To: m...@bitchin100.com Subject: Re: 
[M100] mComm " no such file or directory"On Tue, 10 Aug 2021 at 17:49, Scott 
McDonnell  wrote:Are you starting it with the 
command python3 mcomm.py? Original message From: Peter Vollan 
 Date: 8/10/21  8:39 PM  (GMT-05:00) To: 
m...@bitchin100.com Subject: [M100] mComm When I run mComm on my linux box, I 
get:  File "/usr/bin/mcomm", line 6    subprocess.call(["python3", 
"/usr/share/mcomm/mcomm.py", *sys.argv[1:]])                                    
                        ^SyntaxError: can use starred expression only as 
assignment targetDo I have the wrong type of Python? I run Mint 17.3.MComm is 
also not working on my Android tablet; ts-dos just says disk not ready. I've 
tried all my serial adaptors.

Re: [M100] mcomm android issue

[John R. Hogerhuis]

On Thu, Aug 12, 2021 at 4:34 PM Peter Vollan  wrote:

> There are two versions of mcomm?
>
>>
>>>
At least 3... Windows, Android and Python

Re: [M100] mcomm android issue

[Peter Vollan]

There are two versions of mcomm?


On Thu, 12 Aug 2021 at 16:14, Daryn Hanright  wrote:

> Sorry for replying to an old thread, but was searching for why mComm for
> Android doesn't install on my new Motorola G30 running Android 11.
>
> Exact same symptoms you described in your Android 9 Kurt. The designed for
> old version of Android dialog pops up then the app crashes. I tried both
> the 181 & 192 versions.
>
> Fortunately my old Android 8 device with the cracked screen still works!
>
>
> On Wed, Mar 3, 2021, 4:30 PM Kurt McCullum  wrote:
>
>> Greg,
>>
>> I was able to do some testing with and Android 9 phone. Bad News, it
>> doesn't work on Android 9. I'm not certain as to why but the first giveaway
>> was when I installed it and I got a message that said it was designed for
>> an older version of Android and may not work under 9. I'll have to see what
>> can be done. It may be a matter of upgrading all my code, or just a
>> re-compile with a new target OS. Either way I have some work to do.
>>
>> Just wanted you to know.
>>
>> Kurt
>>
>> On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:
>>
>> Alright. Should be an easy test now that I have all the equipment. The
>> only difference will be I am using a phone rather than a tv box but the OS
>> version will be the same. I'll let you know what I find.
>>
>> Kurt
>>
>> On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:
>>
>> correct, push ts-dos from mcomm android 181 on a android 9 tv box i just
>> got. whenever i hit ok to send the file it just seems to crash mcomm and
>> jumps out of it..
>>
>> On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:
>>
>>
>> Not yet Greg, but I did get the cables needed at I have access to an
>> android 9 phone. I'll do my best to wrestle it out of my wife's hands
>> tonight and test it (Not always easy to do). As I recall it was the TS-DOS
>> injection you were having issues with.
>>
>> Kurt
>>
>>
>> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
>>
>> Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at
>> the village
>>
>> lmk if you get a chance to test that newer android issue
>>
>> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:
>>
>>
>> Yes, I am finally settled in my new place in Camarillo. Still unpacking
>> but life is back to normal.
>>
>> Kurt
>>
>> On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
>>
>> Is it winter yet? :)did you ever escape?
>>
>> Greg
>>
>> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum 
>> wrote:
>>
>>
>> :) thanks. A lot more body surfing going on rather than web surfing. It
>> will definitely be a summer to remember.
>>
>> On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
>>
>> Congratulations to Kurt McCullum on the list Quote of the Month
>>
>> "*I'm still stuck in a beach house with only one model-t*"
>>
>> :-)
>>
>> -- John.
>>
>>
>>
>>
>>
>>

Re: [M100] mcomm android issue

[Daryn Hanright]

Sorry for replying to an old thread, but was searching for why mComm for
Android doesn't install on my new Motorola G30 running Android 11.

Exact same symptoms you described in your Android 9 Kurt. The designed for
old version of Android dialog pops up then the app crashes. I tried both
the 181 & 192 versions.

Fortunately my old Android 8 device with the cracked screen still works!


On Wed, Mar 3, 2021, 4:30 PM Kurt McCullum  wrote:

> Greg,
>
> I was able to do some testing with and Android 9 phone. Bad News, it
> doesn't work on Android 9. I'm not certain as to why but the first giveaway
> was when I installed it and I got a message that said it was designed for
> an older version of Android and may not work under 9. I'll have to see what
> can be done. It may be a matter of upgrading all my code, or just a
> re-compile with a new target OS. Either way I have some work to do.
>
> Just wanted you to know.
>
> Kurt
>
> On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:
>
> Alright. Should be an easy test now that I have all the equipment. The
> only difference will be I am using a phone rather than a tv box but the OS
> version will be the same. I'll let you know what I find.
>
> Kurt
>
> On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:
>
> correct, push ts-dos from mcomm android 181 on a android 9 tv box i just
> got. whenever i hit ok to send the file it just seems to crash mcomm and
> jumps out of it..
>
> On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:
>
>
> Not yet Greg, but I did get the cables needed at I have access to an
> android 9 phone. I'll do my best to wrestle it out of my wife's hands
> tonight and test it (Not always easy to do). As I recall it was the TS-DOS
> injection you were having issues with.
>
> Kurt
>
>
> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
>
> Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at
> the village
>
> lmk if you get a chance to test that newer android issue
>
> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:
>
>
> Yes, I am finally settled in my new place in Camarillo. Still unpacking
> but life is back to normal.
>
> Kurt
>
> On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
>
> Is it winter yet? :)did you ever escape?
>
> Greg
>
> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum  wrote:
>
>
> :) thanks. A lot more body surfing going on rather than web surfing. It
> will definitely be a summer to remember.
>
> On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
>
> Congratulations to Kurt McCullum on the list Quote of the Month
>
> "*I'm still stuck in a beach house with only one model-t*"
>
> :-)
>
> -- John.
>
>
>
>
>
>

Re: [M100] mComm

[Peter Vollan]

" no such file or directory"


On Tue, 10 Aug 2021 at 17:49, Scott McDonnell 
wrote:

> Are you starting it with the command python3 mcomm.py?
>
>  Original message 
> From: Peter Vollan 
> Date: 8/10/21 8:39 PM (GMT-05:00)
> To: m...@bitchin100.com
> Subject: [M100] mComm
>
> When I run mComm on my linux box, I get:
>   File "/usr/bin/mcomm", line 6
> subprocess.call(["python3", "/usr/share/mcomm/mcomm.py",
> *sys.argv[1:]])
> ^
> SyntaxError: can use starred expression only as assignment target
>
> Do I have the wrong type of Python? I run Mint 17.3.
>
> MComm is also not working on my Android tablet; ts-dos just says disk not
> ready. I've tried all my serial adaptors.
>
>>
>>

Re: [M100] mComm

[Scott McDonnell]

Are you starting it with the command python3 mcomm.py?
 Original message From: Peter Vollan  
Date: 8/10/21  8:39 PM  (GMT-05:00) To: m...@bitchin100.com Subject: [M100] 
mComm When I run mComm on my linux box, I get:  File "/usr/bin/mcomm", line 6   
 subprocess.call(["python3", "/usr/share/mcomm/mcomm.py", *sys.argv[1:]])       
                                                     ^SyntaxError: can use 
starred expression only as assignment targetDo I have the wrong type of Python? 
I run Mint 17.3.MComm is also not working on my Android tablet; ts-dos just 
says disk not ready. I've tried all my serial adaptors.

Re: [M100] mcomm on linux

[Kurt McCullum]

Those messages would indicate an error in the pySerial library, not mComm. The 
list_ports functions gets a list of available serial ports. You may want to 
check what version is installed. I think the most recent one is 3.4. There is 
more information at the site below.

https://pyserial.readthedocs.io/en/latest/pyserial.html

Kurt

On Tue, Mar 9, 2021, at 5:57 PM, Peter Vollan wrote:
> Well I've got the "wrapper" file that launches mcomm fixed, so now I am 
> getting the following errors from the actual python script:
> Traceback (most recent call last):
>   File "/usr/share/mcomm/mcomm.py", line 199, in 
> main()
>   File "/usr/share/mcomm/mcomm.py", line 163, in main
> lPorts = serial.tools.list_ports.comports()
>   File "/usr/lib/python3/dist-packages/serial/tools/list_ports_posix.py", 
> line 122, in comports
> return [(d, describe(d), hwinfo(d)) for d in devices]
>   File "/usr/lib/python3/dist-packages/serial/tools/list_ports_posix.py", 
> line 122, in 
> return [(d, describe(d), hwinfo(d)) for d in devices]
>   File "/usr/lib/python3/dist-packages/serial/tools/list_ports_posix.py", 
> line 93, in describe
> return usb_lsusb_string(sys_usb)
>   File "/usr/lib/python3/dist-packages/serial/tools/list_ports_posix.py", 
> line 71, in usb_lsusb_string
> iManufacturer = re_group('iManufacturer\s+\w+ (.+)', desc)
>   File "/usr/lib/python3/dist-packages/serial/tools/list_ports_posix.py", 
> line 44, in re_group
> m = re.search(regexp, text)
>   File "/usr/lib/python3.5/re.py", line 173, in search
> return _compile(pattern, flags).search(string)
> TypeError: cannot use a string pattern on a bytes-like object
> 
> On Thu, 4 Mar 2021 at 02:02, Brian K. White  wrote:
>> On 3/3/21 1:50 PM, Peter Vollan wrote:
>> > FYI my problem persists, despite installing python 3.5
>> 
>> I haven't seen an answer to either mine or others questions that would 
>> nail down that the the installed 3.5 is actually what the script is 
>> using. Merely installing a package doesn't guarantee anything.
>> 
>> You're symptoms are unusual, and so it needs debugging on your end if 
>> you want it to work. You have to investigate and verify things that are 
>> usually just assumed and handled automatically.
>> 
>> When you type "mcomm" is it really running the file you and I and 
>> everyone assumes it is?
>> 
>> $ which mcomm
>> /usr/bin/mcomm
>> 
>> ok good, next, look at that file. The problem sytax occurs right in that 
>> file, not later in the real program file, so *that* file needs to be 
>> executed by a python 3.5 or later executable.
>> 
>> And that file is executed by whatever is on it's shebang line, which is 
>> "/usr/bin/python3", point being, not just "python3", so, you can verify 
>> the interpreter for that file a couple different ways. You can look at 
>> "/usr/bin/python3",
>> 
>> $ ls -l /usr/bin/python3
>> lrwxrwxrwx 1 root root 9 Oct  6 06:28 /usr/bin/python3 -> python3.8
>> 
>> $ /usr/bin/python3 --version
>> Python 3.8.6
>> 
>> 
>> Or you could also add a print statement to show the python version.
>> Insert this line after the import lines and before the subprocess.call() 
>> line:
>> 
>> print(sys.version)
>> 
>> 
>> 
>> Or, better yet, the problem syntax occurs right in the top level wrapper 
>> script, and that entire line really isn't necessary, the entire script 
>> doesn't even need to be python. You could replace the entire contents 
>> with this simpler sh version:
>> 
>> #!/bin/sh
>> exec python3 /usr/share/mcomm/mcomm.py "$@"
>> 
>> What happens when you do that?
>> 
>> -- 
>> bkw

Re: [M100] mcomm on linux

[Peter Vollan]

Well I've got the "wrapper" file that launches mcomm fixed, so now I am
getting the following errors from the actual python script:
Traceback (most recent call last):
  File "/usr/share/mcomm/mcomm.py", line 199, in 
main()
  File "/usr/share/mcomm/mcomm.py", line 163, in main
lPorts = serial.tools.list_ports.comports()
  File "/usr/lib/python3/dist-packages/serial/tools/list_ports_posix.py",
line 122, in comports
return [(d, describe(d), hwinfo(d)) for d in devices]
  File "/usr/lib/python3/dist-packages/serial/tools/list_ports_posix.py",
line 122, in 
return [(d, describe(d), hwinfo(d)) for d in devices]
  File "/usr/lib/python3/dist-packages/serial/tools/list_ports_posix.py",
line 93, in describe
return usb_lsusb_string(sys_usb)
  File "/usr/lib/python3/dist-packages/serial/tools/list_ports_posix.py",
line 71, in usb_lsusb_string
iManufacturer = re_group('iManufacturer\s+\w+ (.+)', desc)
  File "/usr/lib/python3/dist-packages/serial/tools/list_ports_posix.py",
line 44, in re_group
m = re.search(regexp, text)
  File "/usr/lib/python3.5/re.py", line 173, in search
return _compile(pattern, flags).search(string)
TypeError: cannot use a string pattern on a bytes-like object

On Thu, 4 Mar 2021 at 02:02, Brian K. White  wrote:

> On 3/3/21 1:50 PM, Peter Vollan wrote:
> > FYI my problem persists, despite installing python 3.5
>
> I haven't seen an answer to either mine or others questions that would
> nail down that the the installed 3.5 is actually what the script is
> using. Merely installing a package doesn't guarantee anything.
>
> You're symptoms are unusual, and so it needs debugging on your end if
> you want it to work. You have to investigate and verify things that are
> usually just assumed and handled automatically.
>
> When you type "mcomm" is it really running the file you and I and
> everyone assumes it is?
>
> $ which mcomm
> /usr/bin/mcomm
>
> ok good, next, look at that file. The problem sytax occurs right in that
> file, not later in the real program file, so *that* file needs to be
> executed by a python 3.5 or later executable.
>
> And that file is executed by whatever is on it's shebang line, which is
> "/usr/bin/python3", point being, not just "python3", so, you can verify
> the interpreter for that file a couple different ways. You can look at
> "/usr/bin/python3",
>
> $ ls -l /usr/bin/python3
> lrwxrwxrwx 1 root root 9 Oct  6 06:28 /usr/bin/python3 -> python3.8
>
> $ /usr/bin/python3 --version
> Python 3.8.6
>
>
> Or you could also add a print statement to show the python version.
> Insert this line after the import lines and before the subprocess.call()
> line:
>
> print(sys.version)
>
>
>
> Or, better yet, the problem syntax occurs right in the top level wrapper
> script, and that entire line really isn't necessary, the entire script
> doesn't even need to be python. You could replace the entire contents
> with this simpler sh version:
>
> #!/bin/sh
> exec python3 /usr/share/mcomm/mcomm.py "$@"
>
> What happens when you do that?
>
> --
> bkw
>

Re: [M100] mcomm android issue

[Mike Stein]

Ditto!

All the best wishes for ya, Greg!

m

On Wed, Mar 3, 2021 at 11:19 AM John R. Hogerhuis  wrote:

>
>
> On Wed, Mar 3, 2021, 6:31 AM Greg Swallow  wrote:
>
>> but had a mini stroke last Thu.
>>
>> Spent the weekend at the VA Phx hospital being tested. EKG (x3 -- EMT,
>> ER, VA), ECG, Chemical Stress Test, CT Scan, and an MRI (that made more
>> noise than a diesel engine room) all in one day. Left with heart is fine
>> (save for HBP), Vertigo, and stroke evidence that could also indicate M.S.
>>
>>
> Sorry to hear that Greg! Best wishes to you and your family for health or
> at least imperceptibly slow deterioration  :-)
>
> -= Model Ts and Model T'ers Forever =-
>
> -- John.
>
>>

Re: [M100] mcomm on linux

[Kurt McCullum]

Brian,

Great diagnostics procedures. Thanks.

Kurt

On Thu, Mar 4, 2021, at 2:02 AM, Brian K. White wrote:
> On 3/3/21 1:50 PM, Peter Vollan wrote:
> > FYI my problem persists, despite installing python 3.5
> 
> I haven't seen an answer to either mine or others questions that would 
> nail down that the the installed 3.5 is actually what the script is 
> using. Merely installing a package doesn't guarantee anything.
> 
> You're symptoms are unusual, and so it needs debugging on your end if 
> you want it to work. You have to investigate and verify things that are 
> usually just assumed and handled automatically.
> 
> When you type "mcomm" is it really running the file you and I and 
> everyone assumes it is?
> 
> $ which mcomm
> /usr/bin/mcomm
> 
> ok good, next, look at that file. The problem sytax occurs right in that 
> file, not later in the real program file, so *that* file needs to be 
> executed by a python 3.5 or later executable.
> 
> And that file is executed by whatever is on it's shebang line, which is 
> "/usr/bin/python3", point being, not just "python3", so, you can verify 
> the interpreter for that file a couple different ways. You can look at 
> "/usr/bin/python3",
> 
> $ ls -l /usr/bin/python3
> lrwxrwxrwx 1 root root 9 Oct  6 06:28 /usr/bin/python3 -> python3.8
> 
> $ /usr/bin/python3 --version
> Python 3.8.6
> 
> 
> Or you could also add a print statement to show the python version.
> Insert this line after the import lines and before the subprocess.call() 
> line:
> 
> print(sys.version)
> 
> 
> 
> Or, better yet, the problem syntax occurs right in the top level wrapper 
> script, and that entire line really isn't necessary, the entire script 
> doesn't even need to be python. You could replace the entire contents 
> with this simpler sh version:
> 
> #!/bin/sh
> exec python3 /usr/share/mcomm/mcomm.py "$@"
> 
> What happens when you do that?
> 
> -- 
> bkw
> 

Re: [M100] mcomm on linux

[Brian K. White]

On 3/3/21 1:50 PM, Peter Vollan wrote:

FYI my problem persists, despite installing python 3.5


I haven't seen an answer to either mine or others questions that would 
nail down that the the installed 3.5 is actually what the script is 
using. Merely installing a package doesn't guarantee anything.


You're symptoms are unusual, and so it needs debugging on your end if 
you want it to work. You have to investigate and verify things that are 
usually just assumed and handled automatically.


When you type "mcomm" is it really running the file you and I and 
everyone assumes it is?


$ which mcomm
/usr/bin/mcomm

ok good, next, look at that file. The problem sytax occurs right in that 
file, not later in the real program file, so *that* file needs to be 
executed by a python 3.5 or later executable.


And that file is executed by whatever is on it's shebang line, which is 
"/usr/bin/python3", point being, not just "python3", so, you can verify 
the interpreter for that file a couple different ways. You can look at 
"/usr/bin/python3",


$ ls -l /usr/bin/python3
lrwxrwxrwx 1 root root 9 Oct  6 06:28 /usr/bin/python3 -> python3.8

$ /usr/bin/python3 --version
Python 3.8.6


Or you could also add a print statement to show the python version.
Insert this line after the import lines and before the subprocess.call() 
line:


print(sys.version)



Or, better yet, the problem syntax occurs right in the top level wrapper 
script, and that entire line really isn't necessary, the entire script 
doesn't even need to be python. You could replace the entire contents 
with this simpler sh version:


#!/bin/sh
exec python3 /usr/share/mcomm/mcomm.py "$@"

What happens when you do that?

--
bkw

Re: [M100] mcomm on linux

[David Grissom]

I want to thank Kurt Mc., John H,  Stephen A. and many others for their 
development of both the hardware and software that truly extends our Model 
100/102 laptops usefulness.  

I understand the frustration that users can feel in getting some of this 
hardware and software to work on our wonderful little machines.

A few months ago, I decided to build a Poor Man’s TPDD.  I uploaded the build 
and setup my device on Atariage a while back.  In the documentation, I 
described in detail how to setup a fresh install of Raspberry Pi OS with mComm. 
 See link:  Poor Man's TPDD - Raspberry Pi Zero - Tandy Computers - AtariAge 
Forums

While it may not be everyone’s cup of tea to build the project, some of the 
pages in the “Poor Mans TPDD.pdf”  may be useful for those folks trying to get 
started with mComm on a Linux box.

Specifically, see page 15 for information on installation of mComm on Linux.  
In my case it is installed on a $10 Raspberry Pi Zero W.  Page 21 has a link to 
Kurt’s download page

Pages 16 and  21 has some information on Teeny.  Btw, I used a cool little 
program called TrashTalk.  to easily transfer the teeny.do file to my Model 100 
for my testing.  (The web page link is in the pdf. While I don’t go into 
installation and setup detail in the document but it is actually pretty 
straight forward getting Teeny up and running on a Model 100/102.  

Please note that I consider myself a “user”.  I used the information provided 
by all of you folks in the community to create a device that meets my hobby 
needs.  Maybe, this information will provide another viewpoint to get their 
hardware/software up and running.

David G

Sent from Mail for Windows 10

From: Kurt McCullum
Sent: Wednesday, March 3, 2021 1:07 PM
To: m100@lists.bitchin100.com
Subject: Re: [M100] mcomm on linux

I'll look into this when I get a chance Peter. I have not forgotten but thanks 
for the reminder.

Kurt

On Wed, Mar 3, 2021, at 10:50 AM, Peter Vollan wrote:
FYI my problem persists, despite installing python 3.5


On Tue, 2 Mar 2021 at 17:16, John R. Hogerhuis  wrote:


On Tue, Mar 2, 2021 at 4:57 PM Jim Anderson  wrote:
 It's easy to forget that when you're just starting out with this machine

No, I get it. It's complicated. We've lost multiple newbie's coming to the 
list. One guy, "Dunebuggy" departed the list informing us that he had ripped 
all the wires out of his Model 100 and thrown it away, not able to get file 
transfer going.

That said, bootstrap is typically complicated no matter what! If you don't have 
a ROM or REX solution for running TS-DOS, I think TEENY is worth the time to 
figure out.

And you can use it to load DOS100.CO, so, it seems like the best of both worlds.

BTW, another way to inject TEENY is by playing an audio file from an MP3 player 
or phone. That works, if you have the right file. 

CLOAD, or CLOADM, doesn't get easier than that.

Anyone have a known good TEENY audio file? Of course you will need a cassette 
cable, and we all have audio playback devices. Any computer or smart phone 
should do.

-- John.

Re: [M100] mcomm on linux

[Kurt McCullum]

I'll look into this when I get a chance Peter. I have not forgotten but thanks 
for the reminder.

Kurt

On Wed, Mar 3, 2021, at 10:50 AM, Peter Vollan wrote:
> FYI my problem persists, despite installing python 3.5
> 
> 
> On Tue, 2 Mar 2021 at 17:16, John R. Hogerhuis  wrote:
>> 
>> 
>> On Tue, Mar 2, 2021 at 4:57 PM Jim Anderson  wrote:
>>>  It's easy to forget that when you're just starting out with this machine
>> 
>> No, I get it. It's complicated. We've lost multiple newbie's coming to the 
>> list. One guy, "Dunebuggy" departed the list informing us that he had ripped 
>> all the wires out of his Model 100 and thrown it away, not able to get file 
>> transfer going.
>> 
>> That said, bootstrap is typically complicated no matter what! If you don't 
>> have a ROM or REX solution for running TS-DOS, I think TEENY is worth the 
>> time to figure out.
>> 
>> And you can use it to load DOS100.CO , so, it seems like 
>> the best of both worlds.
>> 
>> BTW, another way to inject TEENY is by playing an audio file from an MP3 
>> player or phone. That works, if you have the right file. 
>> 
>> CLOAD, or CLOADM, doesn't get easier than that.
>> 
>> Anyone have a known good TEENY audio file? Of course you will need a 
>> cassette cable, and we all have audio playback devices. Any computer or 
>> smart phone should do.
>> 
>> -- John.

Re: [M100] mcomm on linux

[Peter Vollan]

FYI my problem persists, despite installing python 3.5


On Tue, 2 Mar 2021 at 17:16, John R. Hogerhuis  wrote:

>
>
> On Tue, Mar 2, 2021 at 4:57 PM Jim Anderson  wrote:
>
>>  It's easy to forget that when you're just starting out with this machine
>>
>
> No, I get it. It's complicated. We've lost multiple newbie's coming to the
> list. One guy, "Dunebuggy" departed the list informing us that he had
> ripped all the wires out of his Model 100 and thrown it away, not able to
> get file transfer going.
>
> That said, bootstrap is typically complicated no matter what! If you don't
> have a ROM or REX solution for running TS-DOS, I think TEENY is worth the
> time to figure out.
>
> And you can use it to load DOS100.CO, so, it seems like the best of both
> worlds.
>
> BTW, another way to inject TEENY is by playing an audio file from an MP3
> player or phone. That works, if you have the right file.
>
> CLOAD, or CLOADM, doesn't get easier than that.
>
> Anyone have a known good TEENY audio file? Of course you will need a
> cassette cable, and we all have audio playback devices. Any computer or
> smart phone should do.
>
> -- John.
>

Re: [M100] mcomm android issue

[John R. Hogerhuis]

On Wed, Mar 3, 2021, 6:31 AM Greg Swallow  wrote:

> but had a mini stroke last Thu.
>
> Spent the weekend at the VA Phx hospital being tested. EKG (x3 -- EMT, ER,
> VA), ECG, Chemical Stress Test, CT Scan, and an MRI (that made more noise
> than a diesel engine room) all in one day. Left with heart is fine (save
> for HBP), Vertigo, and stroke evidence that could also indicate M.S.
>
>
Sorry to hear that Greg! Best wishes to you and your family for health or
at least imperceptibly slow deterioration  :-)

-= Model Ts and Model T'ers Forever =-

-- John.

>

Re: [M100] mcomm android issue

[Kurt McCullum]

Greg,

I didn't realize you were using A9. Perhaps this is a hit or miss issue. I 
couldn't get it to work at all on my wife's phone. Glad to here it is working 
for you. 1.81 and 1.92 are almost identical with the exception to the Blue 
Tooth fix in 1.92. I have been testing with 1.81 but I'll have to try the newer 
one.

Kurt

On Wed, Mar 3, 2021, at 6:27 AM, Greg Swallow wrote:
> All, 
> 
> I have also been running mComm on Android 9. Am using mComm v1.92 on a moto 
> G6 officially upgraded to A9. Only issue I had was with Bluetooth as I have 
> added wireless charging to the phone. 
> 
> Kurt worked with me to get the "delay" version of TS-DOS on my M100 via 
> terminal over BT. To do so I used CoolTerm on a Macbook Pro to send the 
> modified .DO against a LOAD"COM:98N1E" in M100 BASIC. One RUN and it's done. 
> next is to configure my REXCPM via BT, but had a mini stroke last Thu. 
> 
> Spent the weekend at the VA Phx hospital being tested. EKG (x3 -- EMT, ER, 
> VA), ECG, Chemical Stress Test, CT Scan, and an MRI (that made more noise 
> than a diesel engine room) all in one day. Left with heart is fine (save for 
> HBP), Vertigo, and stroke evidence that could also indicate M.S. 
> 
> Now that the world stopped spinning, I'm back and wondering what I missed. Is 
> this still mComm 1.81 we're trying on A9? May I suggest trying v1.92? 
> 
> God Bless, 
> 
> GregS <>< 
> 
> 
> Mar 2, 2021 8:45:01 PM Scott McDonnell :

>> FWIW, I have been running mComm on the X96 mini Android TV box which is 
>> Android 9.0. It has been working for me without issue. The only part I can’t 
>> quite get to work is the auto-connect on detection of the USB serial cable. 
>> I have to start the server manually. It also will not stay running in the 
>> background, which means I cannot AutoStart it and operate headless.

>> 

>>  

>> 

>> But, I have it working if I manually start it.

>> 

>>  

>> 

>> https://www.amazon.com/gp/product/B07Q26XFG1/ref=ppx_yo_dt_b_asin_title_o09_s00?ie=UTF8&psc=1

>> 

>>  

>> 


>> *From: *Kurt McCullum <mailto:ku...@fastmail.com>
>> *Sent: *Tuesday, March 2, 2021 10:30 PM
>> *To: *m100@lists.bitchin100.com
>> *Subject: *Re: [M100] mcomm android issue

>> 

>>  

>> 

>> Greg,

>> 

>> 

>> 

>>  

>> 

>> I was able to do some testing with and Android 9 phone. Bad News, it doesn't 
>> work on Android 9. I'm not certain as to why but the first giveaway was when 
>> I installed it and I got a message that said it was designed for an older 
>> version of Android and may not work under 9. I'll have to see what can be 
>> done. It may be a matter of upgrading all my code, or just a re-compile with 
>> a new target OS. Either way I have some work to do.

>> 

>> 

>> 

>>  

>> 

>> Just wanted you to know.

>> 

>> 

>> 

>>  

>> 

>> Kurt

>> 

>> 

>> 

>>  

>> 

>> On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:

>> 

>> 

>>> Alright. Should be an easy test now that I have all the equipment. The only 
>>> difference will be I am using a phone rather than a tv box but the OS 
>>> version will be the same. I'll let you know what I find.

>>> 

>>> 

>>> 

>>>  

>>> 

>>> Kurt

>>> 

>>> 

>>> 

>>>  

>>> 

>>> On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:

>>> 

>>> 

>>>> correct, push ts-dos from mcomm android 181 on a android 9 tv box i just 
>>>> got. whenever i hit ok to send the file it just seems to crash mcomm and 
>>>> jumps out of it.. 

>>>> 

>>>> 

>>>> 

>>>>  

>>>> 

>>>> On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:

>>>> 

>>>> 

>>>>> 

>>>>>  

>>>>> 

>>>>> Not yet Greg, but I did get the cables needed at I have access to an 
>>>>> android 9 phone. I'll do my best to wrestle it out of my wife's hands 
>>>>> tonight and test it (Not always easy to do). As I recall it was the 
>>>>> TS-DOS injection you were having issues with.

>>>>> 

>>>>> 

>>>>> 

>>>>>  

>>>>> 

>>>>> Kurt

>>>>> 

>>>>> 

>>>>> 

>>>>>  

>>>>> 

>>>>> 

>>>>>  

>>>>> 

>>>>> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:

>>>>> 

>>>>> 

>>>>>> Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at 
>>>>>> the village 

>>>>>> 

>>>>>> 

>>>>>> 

>>>>>>  

>>>>>> 

>>>>>> lmk if you get a chance to test that newer android issue

>>>>>> 

>>>>>> 

>>>>>> 

>>>>>>  

>>>>>> 

>>>>>> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:

>>>>>> 

>>>>>> 

>>>>>>> …
>>>>> 

>>>>>  

>>>>> 

>>> 

>>>  

>>> 

>> 

>>  

>> 

>> 

>>  

>> 

Re: [M100] mcomm android issue

[Kurt McCullum]

Thanks Scott. That's good to know.

Kurt

On Tue, Mar 2, 2021, at 7:40 PM, Scott McDonnell wrote:
> FWIW, I have been running mComm on the X96 mini Android TV box which is 
> Android 9.0. It has been working for me without issue. The only part I can’t 
> quite get to work is the auto-connect on detection of the USB serial cable. I 
> have to start the server manually. It also will not stay running in the 
> background, which means I cannot AutoStart it and operate headless.

>  

> But, I have it working if I manually start it.

>  

> https://www.amazon.com/gp/product/B07Q26XFG1/ref=ppx_yo_dt_b_asin_title_o09_s00?ie=UTF8&psc=1

>  


> *From: *Kurt McCullum <mailto:ku...@fastmail.com>
> *Sent: *Tuesday, March 2, 2021 10:30 PM
> *To: *m100@lists.bitchin100.com
> *Subject: *Re: [M100] mcomm android issue

>  

> Greg,

>  

> I was able to do some testing with and Android 9 phone. Bad News, it doesn't 
> work on Android 9. I'm not certain as to why but the first giveaway was when 
> I installed it and I got a message that said it was designed for an older 
> version of Android and may not work under 9. I'll have to see what can be 
> done. It may be a matter of upgrading all my code, or just a re-compile with 
> a new target OS. Either way I have some work to do.

>  

> Just wanted you to know.

>  

> Kurt

>  

> On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:

>> Alright. Should be an easy test now that I have all the equipment. The only 
>> difference will be I am using a phone rather than a tv box but the OS 
>> version will be the same. I'll let you know what I find.

>>  

>> Kurt

>>  

>> On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:

>>> correct, push ts-dos from mcomm android 181 on a android 9 tv box i just 
>>> got. whenever i hit ok to send the file it just seems to crash mcomm and 
>>> jumps out of it.. 

>>>  

>>> On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:

>>>>  

>>>> Not yet Greg, but I did get the cables needed at I have access to an 
>>>> android 9 phone. I'll do my best to wrestle it out of my wife's hands 
>>>> tonight and test it (Not always easy to do). As I recall it was the TS-DOS 
>>>> injection you were having issues with.

>>>>  

>>>> Kurt

>>>>  

>>>>  

>>>> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:

>>>>> Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at 
>>>>> the village 

>>>>>  

>>>>> lmk if you get a chance to test that newer android issue

>>>>>  

>>>>> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:

>>>>>>  

>>>>>> Yes, I am finally settled in my new place in Camarillo. Still unpacking 
>>>>>> but life is back to normal.

>>>>>>  

>>>>>> Kurt

>>>>>>  

>>>>>> On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:

>>>>>>> Is it winter yet? :)did you ever escape?

>>>>>>>  

>>>>>>> Greg

>>>>>>>  

>>>>>>> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum  
>>>>>>> wrote:

>>>>>>>>  

>>>>>>>> :) thanks. A lot more body surfing going on rather than web surfing. 
>>>>>>>> It will definitely be a summer to remember.

>>>>>>>>  

>>>>>>>> On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:

>>>>>>>>> Congratulations to Kurt McCullum on the list Quote of the Month

>>>>>>>>>  

>>>>>>>>> "**I'm still stuck in a beach house with only one model-t**"

>>>>>>>>>  

>>>>>>>>> :-)

>>>>>>>>>  

>>>>>>>>> -- John.

>>>>>>>>  

>>>>  

>>  

>  

>  

Re: [M100] mcomm android issue

[Greg Swallow]

All,

I have also been running mComm on Android 9. Am using mComm v1.92 on a moto G6 
officially upgraded to A9. Only issue I had was with Bluetooth as I have added 
wireless charging to the phone.

Kurt worked with me to get the "delay" version of TS-DOS on my M100 via 
terminal over BT. To do so I used CoolTerm on a Macbook Pro to send the 
modified .DO against a LOAD"COM:98N1E" in M100 BASIC. One RUN and it's done. 
next is to configure my REXCPM via BT, but had a mini stroke last Thu.

Spent the weekend at the VA Phx hospital being tested. EKG (x3 -- EMT, ER, VA), 
ECG, Chemical Stress Test, CT Scan, and an MRI (that made more noise than a 
diesel engine room) all in one day. Left with heart is fine (save for HBP), 
Vertigo, and stroke evidence that could also indicate M.S.

Now that the world stopped spinning, I'm back and wondering what I missed. Is 
this still mComm 1.81 we're trying on A9? May I suggest trying v1.92?

God Bless,

GregS <><

Mar 2, 2021 8:45:01 PM Scott McDonnell :

> FWIW, I have been running mComm on the X96 mini Android TV box which is 
> Android 9.0. It has been working for me without issue. The only part I can’t 
> quite get to work is the auto-connect on detection of the USB serial cable. I 
> have to start the server manually. It also will not stay running in the 
> background, which means I cannot AutoStart it and operate headless.
>  
> But, I have it working if I manually start it.
>  
> https://www.amazon.com/gp/product/B07Q26XFG1/ref=ppx_yo_dt_b_asin_title_o09_s00?ie=UTF8&psc=1
>  
> From: Kurt McCullum[ku...@fastmail.com]
> Sent: Tuesday, March 2, 2021 10:30 PM
> To: m100@lists.bitchin100.com
> Subject: Re: [M100] mcomm android issue
>  
> Greg,
>  
> I was able to do some testing with and Android 9 phone. Bad News, it doesn't 
> work on Android 9. I'm not certain as to why but the first giveaway was when 
> I installed it and I got a message that said it was designed for an older 
> version of Android and may not work under 9. I'll have to see what can be 
> done. It may be a matter of upgrading all my code, or just a re-compile with 
> a new target OS. Either way I have some work to do.
>  
> Just wanted you to know.
>  
> Kurt
>  
> On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:
>> Alright. Should be an easy test now that I have all the equipment. The only 
>> difference will be I am using a phone rather than a tv box but the OS 
>> version will be the same. I'll let you know what I find.
>>  
>> Kurt
>>  
>> On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:
>>> correct, push ts-dos from mcomm android 181 on a android 9 tv box i just 
>>> got. whenever i hit ok to send the file it just seems to crash mcomm and 
>>> jumps out of it.. 
>>>  
>>> On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:
>>>>  
>>>> Not yet Greg, but I did get the cables needed at I have access to an 
>>>> android 9 phone. I'll do my best to wrestle it out of my wife's hands 
>>>> tonight and test it (Not always easy to do). As I recall it was the TS-DOS 
>>>> injection you were having issues with.
>>>>  
>>>> Kurt
>>>>  
>>>>  
>>>> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
>>>>> Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at 
>>>>> the village 
>>>>>  
>>>>> lmk if you get a chance to test that newer android issue
>>>>>  
>>>>> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:
>>>>>> …
>>>>  
>>  
>  
>  

Re: [M100] mcomm android issue

[Scott McDonnell]

FWIW, I have been running mComm on the X96 mini Android TV box which is Android 
9.0. It has been working for me without issue. The only part I can’t quite get 
to work is the auto-connect on detection of the USB serial cable. I have to 
start the server manually. It also will not stay running in the background, 
which means I cannot AutoStart it and operate headless.

But, I have it working if I manually start it.

https://www.amazon.com/gp/product/B07Q26XFG1/ref=ppx_yo_dt_b_asin_title_o09_s00?ie=UTF8&psc=1

From: Kurt McCullum
Sent: Tuesday, March 2, 2021 10:30 PM
To: m100@lists.bitchin100.com
Subject: Re: [M100] mcomm android issue

Greg,

I was able to do some testing with and Android 9 phone. Bad News, it doesn't 
work on Android 9. I'm not certain as to why but the first giveaway was when I 
installed it and I got a message that said it was designed for an older version 
of Android and may not work under 9. I'll have to see what can be done. It may 
be a matter of upgrading all my code, or just a re-compile with a new target 
OS. Either way I have some work to do.

Just wanted you to know.

Kurt

On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:
Alright. Should be an easy test now that I have all the equipment. The only 
difference will be I am using a phone rather than a tv box but the OS version 
will be the same. I'll let you know what I find.

Kurt

On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:
correct, push ts-dos from mcomm android 181 on a android 9 tv box i just got. 
whenever i hit ok to send the file it just seems to crash mcomm and jumps out 
of it.. 

On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:

Not yet Greg, but I did get the cables needed at I have access to an android 9 
phone. I'll do my best to wrestle it out of my wife's hands tonight and test it 
(Not always easy to do). As I recall it was the TS-DOS injection you were 
having issues with.

Kurt


On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at the 
village 

lmk if you get a chance to test that newer android issue

On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:

Yes, I am finally settled in my new place in Camarillo. Still unpacking but 
life is back to normal.

Kurt

On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
Is it winter yet? :)    did you ever escape?

Greg

On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum  wrote:

:) thanks. A lot more body surfing going on rather than web surfing. It will 
definitely be a summer to remember.

On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
Congratulations to Kurt McCullum on the list Quote of the Month

"I'm still stuck in a beach house with only one model-t"

:-)

-- John.

Re: [M100] mcomm android issue

[Scott McDonnell]

FWIW, I have been running mComm on the X96 mini Android TV box which is Android 
9.0. It has been working for me without issue. The only part I can’t quite get 
to work is the auto-connect on detection of the USB serial cable. I have to 
start the server manually. It also will not stay running in the background, 
which means I cannot AutoStart it and operate headless.

But, I have it working if I manually start it.

https://www.amazon.com/gp/product/B07Q26XFG1/ref=ppx_yo_dt_b_asin_title_o09_s00?ie=UTF8&psc=1

From: Kurt McCullum
Sent: Tuesday, March 2, 2021 10:30 PM
To: m100@lists.bitchin100.com
Subject: Re: [M100] mcomm android issue

Greg,

I was able to do some testing with and Android 9 phone. Bad News, it doesn't 
work on Android 9. I'm not certain as to why but the first giveaway was when I 
installed it and I got a message that said it was designed for an older version 
of Android and may not work under 9. I'll have to see what can be done. It may 
be a matter of upgrading all my code, or just a re-compile with a new target 
OS. Either way I have some work to do.

Just wanted you to know.

Kurt

On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:
Alright. Should be an easy test now that I have all the equipment. The only 
difference will be I am using a phone rather than a tv box but the OS version 
will be the same. I'll let you know what I find.

Kurt

On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:
correct, push ts-dos from mcomm android 181 on a android 9 tv box i just got. 
whenever i hit ok to send the file it just seems to crash mcomm and jumps out 
of it.. 

On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:

Not yet Greg, but I did get the cables needed at I have access to an android 9 
phone. I'll do my best to wrestle it out of my wife's hands tonight and test it 
(Not always easy to do). As I recall it was the TS-DOS injection you were 
having issues with.

Kurt


On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at the 
village 

lmk if you get a chance to test that newer android issue

On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:

Yes, I am finally settled in my new place in Camarillo. Still unpacking but 
life is back to normal.

Kurt

On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
Is it winter yet? :)    did you ever escape?

Greg

On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum  wrote:

:) thanks. A lot more body surfing going on rather than web surfing. It will 
definitely be a summer to remember.

On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
Congratulations to Kurt McCullum on the list Quote of the Month

"I'm still stuck in a beach house with only one model-t"

:-)

-- John.

Re: [M100] mcomm on linux

[Kurt McCullum]

I don't know of a good teeny file but I did upload an MP3 for TS-DOS that could 
be played on a phone.

http://www.club100.org/memfiles/index.php?action=downloadfile&filename=DOS100.CO.MP3&directory=Kurt%20McCullum&;

With these instructions: TS-DOS 4.01 in MP3 Format. For those who don't have a 
ROM or DOS loader.
Go to Basic and type 
SOUND OFF 
CLEAR 0, 57089 
RUNM "CAS:DOS100.CO"

Then play the audio file. Of course, this requires an audio cable which is yet 
another issue.

Kurt

On Tue, Mar 2, 2021, at 5:15 PM, John R. Hogerhuis wrote:
> 
> 
> On Tue, Mar 2, 2021 at 4:57 PM Jim Anderson  wrote:
>>  It's easy to forget that when you're just starting out with this machine
> 
> No, I get it. It's complicated. We've lost multiple newbie's coming to the 
> list. One guy, "Dunebuggy" departed the list informing us that he had ripped 
> all the wires out of his Model 100 and thrown it away, not able to get file 
> transfer going.
> 
> That said, bootstrap is typically complicated no matter what! If you don't 
> have a ROM or REX solution for running TS-DOS, I think TEENY is worth the 
> time to figure out.
> 
> And you can use it to load DOS100.CO , so, it seems like 
> the best of both worlds.
> 
> BTW, another way to inject TEENY is by playing an audio file from an MP3 
> player or phone. That works, if you have the right file. 
> 
> CLOAD, or CLOADM, doesn't get easier than that.
> 
> Anyone have a known good TEENY audio file? Of course you will need a cassette 
> cable, and we all have audio playback devices. Any computer or smart phone 
> should do.
> 
> -- John.

Re: [M100] mcomm android issue

[Kurt McCullum]

Greg,

I was able to do some testing with and Android 9 phone. Bad News, it doesn't 
work on Android 9. I'm not certain as to why but the first giveaway was when I 
installed it and I got a message that said it was designed for an older version 
of Android and may not work under 9. I'll have to see what can be done. It may 
be a matter of upgrading all my code, or just a re-compile with a new target 
OS. Either way I have some work to do.

Just wanted you to know.

Kurt

On Tue, Mar 2, 2021, at 10:29 AM, Kurt McCullum wrote:
> Alright. Should be an easy test now that I have all the equipment. The only 
> difference will be I am using a phone rather than a tv box but the OS version 
> will be the same. I'll let you know what I find.
> 
> Kurt
> 
> On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:
>> correct, push ts-dos from mcomm android 181 on a android 9 tv box i just 
>> got. whenever i hit ok to send the file it just seems to crash mcomm and 
>> jumps out of it.. 
>> 
>> On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:
>>> __
>>> Not yet Greg, but I did get the cables needed at I have access to an 
>>> android 9 phone. I'll do my best to wrestle it out of my wife's hands 
>>> tonight and test it (Not always easy to do). As I recall it was the TS-DOS 
>>> injection you were having issues with.
>>> 
>>> Kurt
>>> 
>>> 
>>> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
 Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at 
 the village 
 
 lmk if you get a chance to test that newer android issue
 
 On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:
> __
> Yes, I am finally settled in my new place in Camarillo. Still unpacking 
> but life is back to normal.
> 
> Kurt
> 
> On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
>> Is it winter yet? :)did you ever escape?
>> 
>> Greg
>> 
>> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum  
>> wrote:
>>> __
>>> :) thanks. A lot more body surfing going on rather than web surfing. It 
>>> will definitely be a summer to remember.
>>> 
>>> On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
 Congratulations to Kurt McCullum on the list Quote of the Month
 
 "**I'm still stuck in a beach house with only one model-t**"
 
 :-)
 
 -- John.
>>> 
>>> 
> 

Re: [M100] mcomm on linux

[John R. Hogerhuis]

On Tue, Mar 2, 2021 at 4:57 PM Jim Anderson  wrote:

>  It's easy to forget that when you're just starting out with this machine
>

No, I get it. It's complicated. We've lost multiple newbie's coming to the
list. One guy, "Dunebuggy" departed the list informing us that he had
ripped all the wires out of his Model 100 and thrown it away, not able to
get file transfer going.

That said, bootstrap is typically complicated no matter what! If you don't
have a ROM or REX solution for running TS-DOS, I think TEENY is worth the
time to figure out.

And you can use it to load DOS100.CO, so, it seems like the best of both
worlds.

BTW, another way to inject TEENY is by playing an audio file from an MP3
player or phone. That works, if you have the right file.

CLOAD, or CLOADM, doesn't get easier than that.

Anyone have a known good TEENY audio file? Of course you will need a
cassette cable, and we all have audio playback devices. Any computer or
smart phone should do.

-- John.

Re: [M100] mcomm on linux

[John R. Hogerhuis]

Actually, here is the generic instructions for preparing to launch any CO
file

http://bitchin100.com/wiki/index.php?title=Loading_a_typical_CO_file


And here are instructions about recovering an unresponsive / memory
corrupted laptop.

It actually covers the case of taking a machine from storage, but it does
mention cold start instructions.

http://bitchin100.com/wiki/index.php?title=Recovering_an_Unresponsive_Laptop

-- John.

Re: [M100] mcomm on linux

[Jim Anderson]

> -Original Message-
> But TSLOAD.CO doesn't do anything but loads
> DOS100.CO binary file. Which is 8k.

This is true, but with a difference.  It loads DOS100.CO on demand rather than 
have it reside in your RAM at all times, so when you quit TS-DOS you get the 
RAM back.  Sometimes you might prefer to have it sit there taking up 8k at all 
times, but sometimes you might prefer to have 8k available to work with.

> More than one way to do it!

Well, that's why I suggested two alternatives.  TEENY is definitely smaller, 
but IMHO for some people (and especially for someone just starting out with a 
Model T or with 8-bit computers in general) using TEENY is another hurdle 
compared with the interface of TS-DOS, and they're already trying to overcome 
multiple hurdles at once.  You can learn about how file transfers work with 
TS-DOS and then later decide if you want to learn to operate TEENY to save on 
RAM space.  It's easy to forget that when you're just starting out with this 
machine (like I was a few years ago) it takes a little while before file 
transfers and TPDD servers start to make sense rather than feeling like 
mysterious incantations.  :)







jim

Re: [M100] mcomm on linux

[John R. Hogerhuis]

On Tue, Mar 2, 2021 at 4:24 PM AvantGuard Systems <
cavaug...@avantguardsystems.com> wrote:

> Ok I finally found some documentation on TEENY and it looks like I have to
> use Windows and run TEENY.EXE on it. Grrr
>
>>
>>>
No, no... TEENY.EXE is not TEENY. TEENY.EXE is an "injector". But if you
loaded from a DO you don't need the injector.

Do you have TEENY.CO running?

Here are instructions once it's launched:

http://bitchin100.com/wiki/index.php?title=TEENY

If you need instructions for CLEAR to launch it, let me know.

-- John.

Re: [M100] mcomm on linux

[AvantGuard Systems]

Ok I finally found some documentation on TEENY and it looks like I have to
use Windows and run TEENY.EXE on it. Grrr

 Curtis Vaughan  |  Computer Consultant
   AvantGuard Computer and Security Systems
   Phone: (206) 423-6979 ▪ Web: www.avantguardsystems.com


On Tue, Mar 2, 2021 at 4:15 PM AvantGuard Systems <
cavaug...@avantguardsystems.com> wrote:

> Ok, i've got TEENY.CO running, but have no idea what I'm supposed to do.
> Where are the instructions?
>
>  Curtis Vaughan  |  Computer Consultant
>AvantGuard Computer and Security Systems
>Phone: (206) 423-6979 ▪ Web: www.avantguardsystems.com
>
>
> On Tue, Mar 2, 2021 at 2:37 PM Jim Anderson  wrote:
>
>> > -Original Message-
>> >
>> > Well, if I try to rename ADVENT1.BA to ADVEN.DO, it still says file
>> already exists and
>> > actually it just creates ADVENT1.BA in RAM.
>>
>> Just wanted to point out that when it was suggested to rename the file,
>> the idea was to rename it on the PC end rather than typing a new name for
>> it when you load it through TS-DOS.  If you give a new name, it will only
>> rename the first part of the name - the two character extension cannot be
>> changed during a TS-DOS load or save operation and it will insist on
>> keeping the original file type.
>>
>> One bit of key information you might not be aware of regarding file
>> types, if the file you are transferring is a plain text listing of a BASIC
>> program it must be transferred as a file ending in .DO so that the Model T
>> will know it is a text file.  You can then go into BASIC on the Model T and
>> load it, at which point it will tokenize it and you can save it as a
>> tokenized .BA file.
>>
>> If you load a .BA file using TS-DOS it must be a tokenized file.  You can
>> check by opening the .BA file in a text editor on your PC and see if it's a
>> text listing or if it's a lot of high-ASCII (looks like garbage) with some
>> plain text strings mixed in.
>>
>> Another thing, something you had said in a prior message sounded to me
>> like you thought you needed to load the file from disk (the mComm server on
>> the PC) and then save it in RAM.  It's useful to remember that RAM in the
>> Model T *is* the filesystem, so you don't load into RAM and then save to
>> local storage.  RAM is the local storage.  What the Save function in TS-DOS
>> is used for is to copy files out of the RAM filesystem onto the disk device
>> (the mComm server).  If you've been hitting Load and Save on a bunch of
>> files, maybe take a minute to double-check what's in your mComm TPDD folder
>> to make sure you didn't write back some of these empty or 1-byte files into
>> your PC...
>>
>> The easiest way to remember the meaning of Load and Save is to remember
>> that originally you were Loading files from and Saving files to an external
>> battery-powered floppy drive (the Tandy Portable Disk Drive, hence the
>> acronym TPDD).  Now, we're using a PC with mComm or LaddieAlpha or dlplus
>> or other TPDD emulators, so we're Loading from or Saving to those devices.
>>
>> Aside from these things (which are useful bits of info to know when you
>> are just starting out), I agree that it does sound like your Model T
>> filesystem is corrupt.  The easiest thing to inject is TEENY because it's,
>> well, tiny :) but IMHO even though it's bigger the easiest to deal with
>> would be TSLOAD (by transferring the contents of TSL100.DO from Joshua's S3
>> bucket which he just posted about).  This will create TSLOAD.CO in your
>> machine which loads TS-DOS on demand from the PC whenever you need it, so
>> it's not taking up so much of your Model T's RAM.
>>
>>
>>
>>
>>
>>
>>
>> jim
>>
>>

Re: [M100] mcomm on linux

[AvantGuard Systems]

Ok, i've got TEENY.CO running, but have no idea what I'm supposed to do.
Where are the instructions?

 Curtis Vaughan  |  Computer Consultant
   AvantGuard Computer and Security Systems
   Phone: (206) 423-6979 ▪ Web: www.avantguardsystems.com


On Tue, Mar 2, 2021 at 2:37 PM Jim Anderson  wrote:

> > -Original Message-
> >
> > Well, if I try to rename ADVENT1.BA to ADVEN.DO, it still says file
> already exists and
> > actually it just creates ADVENT1.BA in RAM.
>
> Just wanted to point out that when it was suggested to rename the file,
> the idea was to rename it on the PC end rather than typing a new name for
> it when you load it through TS-DOS.  If you give a new name, it will only
> rename the first part of the name - the two character extension cannot be
> changed during a TS-DOS load or save operation and it will insist on
> keeping the original file type.
>
> One bit of key information you might not be aware of regarding file types,
> if the file you are transferring is a plain text listing of a BASIC program
> it must be transferred as a file ending in .DO so that the Model T will
> know it is a text file.  You can then go into BASIC on the Model T and load
> it, at which point it will tokenize it and you can save it as a tokenized
> .BA file.
>
> If you load a .BA file using TS-DOS it must be a tokenized file.  You can
> check by opening the .BA file in a text editor on your PC and see if it's a
> text listing or if it's a lot of high-ASCII (looks like garbage) with some
> plain text strings mixed in.
>
> Another thing, something you had said in a prior message sounded to me
> like you thought you needed to load the file from disk (the mComm server on
> the PC) and then save it in RAM.  It's useful to remember that RAM in the
> Model T *is* the filesystem, so you don't load into RAM and then save to
> local storage.  RAM is the local storage.  What the Save function in TS-DOS
> is used for is to copy files out of the RAM filesystem onto the disk device
> (the mComm server).  If you've been hitting Load and Save on a bunch of
> files, maybe take a minute to double-check what's in your mComm TPDD folder
> to make sure you didn't write back some of these empty or 1-byte files into
> your PC...
>
> The easiest way to remember the meaning of Load and Save is to remember
> that originally you were Loading files from and Saving files to an external
> battery-powered floppy drive (the Tandy Portable Disk Drive, hence the
> acronym TPDD).  Now, we're using a PC with mComm or LaddieAlpha or dlplus
> or other TPDD emulators, so we're Loading from or Saving to those devices.
>
> Aside from these things (which are useful bits of info to know when you
> are just starting out), I agree that it does sound like your Model T
> filesystem is corrupt.  The easiest thing to inject is TEENY because it's,
> well, tiny :) but IMHO even though it's bigger the easiest to deal with
> would be TSLOAD (by transferring the contents of TSL100.DO from Joshua's S3
> bucket which he just posted about).  This will create TSLOAD.CO in your
> machine which loads TS-DOS on demand from the PC whenever you need it, so
> it's not taking up so much of your Model T's RAM.
>
>
>
>
>
>
>
> jim
>
>

Re: [M100] mcomm on linux

[John R. Hogerhuis]

So TSL100.DO is a 3K file, that can be downloaded through TELCOM or the
RUN"COM  command. It's a text form of a BASIC program that creates TSLOAD.CO,
a 526 byte CO program. But TSLOAD.CO doesn't do anything but loads DOS100.CO
binary file. Which is 8k.

It all works... but if you go straight to TEENY which is only about 300
bytes more than TSLOAD.CO, then you have full ability to transfer files,
including DOS100.CO if you want.

More than one way to do it!

-- John.

Re: [M100] mcomm on linux

[Jim Anderson]

> -Original Message-
> 
> Well, if I try to rename ADVENT1.BA to ADVEN.DO, it still says file already 
> exists and
> actually it just creates ADVENT1.BA in RAM.

Just wanted to point out that when it was suggested to rename the file, the 
idea was to rename it on the PC end rather than typing a new name for it when 
you load it through TS-DOS.  If you give a new name, it will only rename the 
first part of the name - the two character extension cannot be changed during a 
TS-DOS load or save operation and it will insist on keeping the original file 
type.

One bit of key information you might not be aware of regarding file types, if 
the file you are transferring is a plain text listing of a BASIC program it 
must be transferred as a file ending in .DO so that the Model T will know it is 
a text file.  You can then go into BASIC on the Model T and load it, at which 
point it will tokenize it and you can save it as a tokenized .BA file.

If you load a .BA file using TS-DOS it must be a tokenized file.  You can check 
by opening the .BA file in a text editor on your PC and see if it's a text 
listing or if it's a lot of high-ASCII (looks like garbage) with some plain 
text strings mixed in.

Another thing, something you had said in a prior message sounded to me like you 
thought you needed to load the file from disk (the mComm server on the PC) and 
then save it in RAM.  It's useful to remember that RAM in the Model T *is* the 
filesystem, so you don't load into RAM and then save to local storage.  RAM is 
the local storage.  What the Save function in TS-DOS is used for is to copy 
files out of the RAM filesystem onto the disk device (the mComm server).  If 
you've been hitting Load and Save on a bunch of files, maybe take a minute to 
double-check what's in your mComm TPDD folder to make sure you didn't write 
back some of these empty or 1-byte files into your PC...

The easiest way to remember the meaning of Load and Save is to remember that 
originally you were Loading files from and Saving files to an external 
battery-powered floppy drive (the Tandy Portable Disk Drive, hence the acronym 
TPDD).  Now, we're using a PC with mComm or LaddieAlpha or dlplus or other TPDD 
emulators, so we're Loading from or Saving to those devices.

Aside from these things (which are useful bits of info to know when you are 
just starting out), I agree that it does sound like your Model T filesystem is 
corrupt.  The easiest thing to inject is TEENY because it's, well, tiny :) but 
IMHO even though it's bigger the easiest to deal with would be TSLOAD (by 
transferring the contents of TSL100.DO from Joshua's S3 bucket which he just 
posted about).  This will create TSLOAD.CO in your machine which loads TS-DOS 
on demand from the PC whenever you need it, so it's not taking up so much of 
your Model T's RAM.







jim

Re: [M100] mcomm on linux

[Joshua O'Keefe]

On Mar 2, 2021, at 1:04 PM, John R. Hogerhuis  wrote:
> In which case you need something in plain text .DO file format to start with. 
> I think the "IPL.BA"

A solution that worked for me before I had a REX was to inject TSLOAD which is 
small, and use that to run TSDOS off the emulated disk as needed.  This saved a 
few K of RAM over the solution of just keeping TSDOS whole hog on the 
filesystem.

I keep a copy of TSLOAD on my S3 bucket, because I had a fair amount of trouble 
locating it until Kurt dug it up for me.

S3 bucket: http://public.nachomountain.com/files/m100/

Re: [M100] mcomm on linux

[John R. Hogerhuis]

And if you want to ditch TS-DOS RAM altogether, you can just inject TEENY
in one step:

http://club100.org/memfiles/index.php?&direction=0&order=&directory=John%20Hogerhuis/TEENY

This is a TEENY loader in DO format. You run it, and it creates TEENY.CO

It's bare bones but it gets the file transfer job done. It's only downfall
is it has no support for listing directories on either side. You have to
know the names of the files you are transferring, no fancy menu.

And in fact if you want to go back to TS-DOS RAM, once TEENY is installed,
you use TEENY to load DOS100.CO.

So TEENY can be used to bootstrap TS-DOS RAM.

The other advantage of TEENY is it works over even the slowest links. So
Bluetooth, Wifi, etc. should all work without any issues, since TEENY does
not have any timeouts. If it hangs, it hangs until you hit reset.

-- John.

Re: [M100] mcomm on linux

[John R. Hogerhuis]

On Tue, Mar 2, 2021 at 12:25 PM AvantGuard Systems <
cavaug...@avantguardsystems.com> wrote:

> Well, if I try to rename ADVENT1.BA to ADVEN.DO, it still says file
> already exists and actually it just creates ADVENT1.BA in RAM.
> I even tried LOADing a .DO file. Again it says file already exists, but
> this time the file in RAM has 1 bit. In reality it should be around 511.
>
>
By Bit I think you mean byte, but yeah.

ADVEN1.DO should show as about 17875 bytes, not 1 or 511.


> Uh RAM is corrupted possibility. Well, then I have to figure out how
> to get TPDD over to M100 from Linux, right?
>
>
A near certainty. Since you have a known working way to do this from
Windows I suggest you a) do a cold start to clear the corruption and b)
re-inject it from there.

Or embark on the journey of discovery... your choice :-)

In which case you need something in plain text .DO file format to start
with. I think the "IPL.BA"

http://www.club100.org/library/doc/tsdos.html

Section on IPL.BA
I guess the IPL is included with mcomm as a file? Since it is able to
inject it. Maybe you can get it from there.

The other thing you could do is type in the IPL.

-- John.

Re: [M100] mcomm on linux

[Gregory McGill]

pretty easy to do just copy the file listing for it and paste it into a
terminal on the pc side while doing the load on the m100 side

Greg

On Tue, Mar 2, 2021 at 12:25 PM AvantGuard Systems <
cavaug...@avantguardsystems.com> wrote:

> Well, if I try to rename ADVENT1.BA to ADVEN.DO, it still says file
> already exists and actually it just creates ADVENT1.BA in RAM.
> I even tried LOADing a .DO file. Again it says file already exists, but
> this time the file in RAM has 1 bit. In reality it should be around 511.
>
> Uh RAM is corrupted possibility. Well, then I have to figure out how
> to get TPDD over to M100 from Linux, right?
>
>  Curtis
>
> On Tue, Mar 2, 2021 at 12:13 PM John R. Hogerhuis 
> wrote:
>
>>
>>
>> On Tue, Mar 2, 2021 at 12:06 PM Kurt McCullum  wrote:
>>
>>> So true.
>>>
>>> So the philosophy is that when you touch a hot stove, you should get
>>> burned.
>>>
>>>
>> Here endeth the lesson, newbs :-)
>>
>> -- John.
>>
>

Re: [M100] mcomm on linux

[AvantGuard Systems]

Well, if I try to rename ADVENT1.BA to ADVEN.DO, it still says file already
exists and actually it just creates ADVENT1.BA in RAM.
I even tried LOADing a .DO file. Again it says file already exists, but
this time the file in RAM has 1 bit. In reality it should be around 511.

Uh RAM is corrupted possibility. Well, then I have to figure out how to
get TPDD over to M100 from Linux, right?

 Curtis

On Tue, Mar 2, 2021 at 12:13 PM John R. Hogerhuis  wrote:

>
>
> On Tue, Mar 2, 2021 at 12:06 PM Kurt McCullum  wrote:
>
>> So true.
>>
>> So the philosophy is that when you touch a hot stove, you should get
>> burned.
>>
>>
> Here endeth the lesson, newbs :-)
>
> -- John.
>

Re: [M100] mcomm on linux

[John R. Hogerhuis]

On Tue, Mar 2, 2021 at 12:06 PM Kurt McCullum  wrote:

> So true.
>
> So the philosophy is that when you touch a hot stove, you should get
> burned.
>
>
Here endeth the lesson, newbs :-)

-- John.

Re: [M100] mcomm on linux

[Kurt McCullum]

So true.

> So the philosophy is that when you touch a hot stove, you should get burned.
> 
> 

Re: [M100] mcomm on linux

[John R. Hogerhuis]

Ah. I think it is a file format/ extension problem. A Known issue

ADVEN1.BA is misnamed. It is a text file, so its extension should be .DO
not .BA . .BA is only for tokenized basic programs.

TS-DOS sees the BA extension and tries to load the contents as a tokenized
(binary) BASIC program, into that area, and corrupts the file system.

So to load ADVEN1, you need to rename it from your host PC as ADVEN1.DO and
then  load it. Never load a plain text BASIC program from a BA extension.

Also your Model 100 RAM file system is probably corrupted, you must do a
cold start to reset the system.

I added code in LaddieAlpha to detect files misnamed like this. It would
have renamed it on the fly. But I don't think other TPDD servers do this
renaming.

So the philosophy is that when you touch a hot stove, you should get burned.

-- John.

On Tue, Mar 2, 2021 at 11:56 AM AvantGuard Systems <
cavaug...@avantguardsystems.com> wrote:

> Right, so I push Disk to see the files in my TPDD directory. So for
> example, let's say I want to load ADVEN1.BA, which under FILE on the M100
> shows as having 17875 bits (17.9 KB according to the computer). So all's
> good.
> RAM free is 23477
> So I've killed ADVEN1.BA on the RAM side. I go to DISK, push LOAD. A
> dialogue Load as comes up and I usually just keep the same name by entering
> nothing. It says File exists, press any key. When I go to RAM it is there,
> but nothing is in it. Even if I change the name it'll say File exists press
> any key and the new file is also 0 bits
>
>  Curtis Vaughan  |  Computer Consultant
>AvantGuard Computer and Security Systems
>Phone: (206) 423-6979 ▪ Web: www.avantguardsystems.com
>
>
> On Tue, Mar 2, 2021 at 11:48 AM John R. Hogerhuis 
> wrote:
>
>> "But what happens when I load a file is that it will always say that the
>> file already exists, but when I go to RAM it's an empty file. So even if I
>> try to save it, it says it's an empty file."
>>
>> What file are you trying to load?
>>
>> When you launch TS-DOS you are looking at the M100's directory. If you
>> toggle to Disk (I think, F4) you can look at the TPDD directory.
>>
>> Always keep in mind there are two sides... the M100 directory, and the
>> TPDD directory.
>>
>> It sounds like the file in RAM *is* empty and it will stay empty until
>> you delete it or allow it to be overwritten.
>>
>> The other question is, what is in the file on the TPDD side you are
>> trying to load. Obviously if it is empty on the TPDD side it will also be
>> empty when you load a copy into M100 file system.
>>
>> What's the name including extension? How many bytes are in it? If you are
>> in Disk Mode and move the widebar cursor over the file, TS-DOS should tell
>> you a byte count.
>>
>> -- John.
>>
>

Re: [M100] mcomm on linux

[Kurt McCullum]

Is ADVEN1.BA a text file or tokenized basic? Quite a few of the files from 
club100 have a .BA extension but are actually .DO files.

Kurt

On Tue, Mar 2, 2021, at 11:56 AM, AvantGuard Systems wrote:
> Right, so I push Disk to see the files in my TPDD directory. So for example, 
> let's say I want to load ADVEN1.BA , which under FILE on 
> the M100 shows as having 17875 bits (17.9 KB according to the computer). So 
> all's good.
> RAM free is 23477
> So I've killed ADVEN1.BA  on the RAM side. I go to DISK, 
> push LOAD. A dialogue Load as comes up and I usually just keep the same name 
> by entering nothing. It says File exists, press any key. When I go to RAM it 
> is there, but nothing is in it. Even if I change the name it'll say File 
> exists press any key and the new file is also 0 bits
> 
>  Curtis Vaughan  |  Computer Consultant
>AvantGuard Computer and Security Systems
>Phone: (206) 423-6979 ▪ Web: www.avantguardsystems.com
> 
> 
> On Tue, Mar 2, 2021 at 11:48 AM John R. Hogerhuis  wrote:
>> "But what happens when I load a file is that it will always say that the 
>> file already exists, but when I go to RAM it's an empty file. So even if I 
>> try to save it, it says it's an empty file."
>> 
>> What file are you trying to load?
>> When you launch TS-DOS you are looking at the M100's directory. If you 
>> toggle to Disk (I think, F4) you can look at the TPDD directory.
>> 
>> Always keep in mind there are two sides... the M100 directory, and the TPDD 
>> directory.
>> 
>> It sounds like the file in RAM *is* empty and it will stay empty until you 
>> delete it or allow it to be overwritten.
>> 
>> The other question is, what is in the file on the TPDD side you are trying 
>> to load. Obviously if it is empty on the TPDD side it will also be empty 
>> when you load a copy into M100 file system.
>> 
>> What's the name including extension? How many bytes are in it? If you are in 
>> Disk Mode and move the widebar cursor over the file, TS-DOS should tell you 
>> a byte count.
>> 
>> -- John.

Re: [M100] mcomm on linux

[AvantGuard Systems]

Right, so I push Disk to see the files in my TPDD directory. So for
example, let's say I want to load ADVEN1.BA, which under FILE on the M100
shows as having 17875 bits (17.9 KB according to the computer). So all's
good.
RAM free is 23477
So I've killed ADVEN1.BA on the RAM side. I go to DISK, push LOAD. A
dialogue Load as comes up and I usually just keep the same name by entering
nothing. It says File exists, press any key. When I go to RAM it is there,
but nothing is in it. Even if I change the name it'll say File exists press
any key and the new file is also 0 bits

 Curtis Vaughan  |  Computer Consultant
   AvantGuard Computer and Security Systems
   Phone: (206) 423-6979 ▪ Web: www.avantguardsystems.com


On Tue, Mar 2, 2021 at 11:48 AM John R. Hogerhuis  wrote:

> "But what happens when I load a file is that it will always say that the
> file already exists, but when I go to RAM it's an empty file. So even if I
> try to save it, it says it's an empty file."
>
> What file are you trying to load?
>
> When you launch TS-DOS you are looking at the M100's directory. If you
> toggle to Disk (I think, F4) you can look at the TPDD directory.
>
> Always keep in mind there are two sides... the M100 directory, and the
> TPDD directory.
>
> It sounds like the file in RAM *is* empty and it will stay empty until you
> delete it or allow it to be overwritten.
>
> The other question is, what is in the file on the TPDD side you are trying
> to load. Obviously if it is empty on the TPDD side it will also be empty
> when you load a copy into M100 file system.
>
> What's the name including extension? How many bytes are in it? If you are
> in Disk Mode and move the widebar cursor over the file, TS-DOS should tell
> you a byte count.
>
> -- John.
>

Re: [M100] mcomm on linux

[John R. Hogerhuis]

On Tue, Mar 2, 2021 at 11:42 AM AvantGuard Systems <
cavaug...@avantguardsystems.com> wrote:

> I'm wondering how I'm supposed to get that over to M100 should I lose it?
>

Well, many people have a ROM version of TS-DOS either in a option ROM or in
a REX. So they never need to bootstrap TS-DOS into RAM.

TS-DOS RAM version is really big, like 8k, so it is really a non-starter
for me.

For LaddieAlpha, I encourage either REX, a  real option ROM, or TEENY.
TEENY is purely a software thing, but only takes 800 bytes. TEENY can be
injected in DO format using any terminal program. On Linux, that would be
Minicom for me.

I assume there's a version of TS-DOS RAM can also be injected with a
terminal program though I don't think I've ever tried it.

-- John.

Re: [M100] mcomm on linux

[John R. Hogerhuis]

"But what happens when I load a file is that it will always say that the
file already exists, but when I go to RAM it's an empty file. So even if I
try to save it, it says it's an empty file."

What file are you trying to load?

When you launch TS-DOS you are looking at the M100's directory. If you
toggle to Disk (I think, F4) you can look at the TPDD directory.

Always keep in mind there are two sides... the M100 directory, and the TPDD
directory.

It sounds like the file in RAM *is* empty and it will stay empty until you
delete it or allow it to be overwritten.

The other question is, what is in the file on the TPDD side you are trying
to load. Obviously if it is empty on the TPDD side it will also be empty
when you load a copy into M100 file system.

What's the name including extension? How many bytes are in it? If you are
in Disk Mode and move the widebar cursor over the file, TS-DOS should tell
you a byte count.

-- John.

Re: [M100] mcomm on linux

[AvantGuard Systems]

OK back to mcomm on linux. It does seem so far more stable than on windows.
However! when running my CPU is being taxed by python3.
Anyhow After I launch TS-DOS on M100, I can go to Disk and see all the
files that will fit on the screen. Looking at the TSDOS documentation it
seems that I should choose LOAD to put a file into RAM and then I'm
guessing that I would then SAVE it. But what happens when I load a file is
that it will always say that the file already exists, but when I go to RAM
it's an empty file. So even if I try to save it, it says it's an empty
file. If I load it in Basic, there is nothing there. So obviously I'm
missing something.

Another thing I've noticed is that under Windows you can load TPDD to the
M100. But when I launch mcomm on linux there is no such option. I'm
wondering how I'm supposed to get that over to M100 should I lose it?

 Curtis

On Sun, Feb 28, 2021 at 6:46 AM Brian K. White  wrote:

> On 2/26/21 6:28 PM, Chris Fezzler wrote:
>
> > Hey, after I type RUN "COM:98N1E" in BASIC, do I hit ENTER on the M100?
>
> Yes.
>
> --
> bkw
>

Re: [M100] mcomm

[Peter Vollan]

I have now installed python 3.5 and edited the loader file with python3.5.
python3.5 --version yields Python 3.5.2


On Tue, 2 Mar 2021 at 04:10, Brian K. White  wrote:

> On 3/1/21 9:18 PM, Peter Vollan wrote:
> > I just did that and it did not solve the problem. It has something to do
> > with the starred expression.
>
> Yes, and the something is that it was invalid syntax before python 3.5.
>
> Perhaps you installed 3.5, but "/usr/bin/python3" is not linked to that
> version?
>
> --
> bkw
>
>
> > On Mon, 1 Mar 2021 at 17:46, Brian K. White  > > wrote:
> >
> > On 3/1/21 5:22 PM, Kurt McCullum wrote:
> >  > SyntaxError: can use starred expression only as assignment target
> >
> > Simply Googling the error message suggests you need Python 3.5 or
> later.
> >
> > Which means in the source Kurt should update debian/control in his
> > source to say
> > Depends: python3 (>= 3.5),python3-serial
> > and generate a new .deb
> >
> > For now, for you, just manually get python 3.5 or later.
> >
> > --
> > bkw
> >
>
>
> --
> bkw
>

Re: [M100] mcomm android issue

[Kurt McCullum]

Alright. Should be an easy test now that I have all the equipment. The only 
difference will be I am using a phone rather than a tv box but the OS version 
will be the same. I'll let you know what I find.

Kurt

On Tue, Mar 2, 2021, at 10:05 AM, Gregory McGill wrote:
> correct, push ts-dos from mcomm android 181 on a android 9 tv box i just got. 
> whenever i hit ok to send the file it just seems to crash mcomm and jumps out 
> of it.. 
> 
> On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:
>> __
>> Not yet Greg, but I did get the cables needed at I have access to an android 
>> 9 phone. I'll do my best to wrestle it out of my wife's hands tonight and 
>> test it (Not always easy to do). As I recall it was the TS-DOS injection you 
>> were having issues with.
>> 
>> Kurt
>> 
>> 
>> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
>>> Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at the 
>>> village 
>>> 
>>> lmk if you get a chance to test that newer android issue
>>> 
>>> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:
 __
 Yes, I am finally settled in my new place in Camarillo. Still unpacking 
 but life is back to normal.
 
 Kurt
 
 On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
> Is it winter yet? :)did you ever escape?
> 
> Greg
> 
> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum  wrote:
>> __
>> :) thanks. A lot more body surfing going on rather than web surfing. It 
>> will definitely be a summer to remember.
>> 
>> On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
>>> Congratulations to Kurt McCullum on the list Quote of the Month
>>> 
>>> "**I'm still stuck in a beach house with only one model-t**"
>>> 
>>> :-)
>>> 
>>> -- John.
>> 
>> 

Re: [M100] mcomm android issue

[Gregory McGill]

correct, push ts-dos from mcomm android 181 on a android 9 tv box i just
got. whenever i hit ok to send the file it just seems to crash mcomm and
jumps out of it..

On Tue, Mar 2, 2021 at 9:32 AM Kurt McCullum  wrote:

> Not yet Greg, but I did get the cables needed at I have access to an
> android 9 phone. I'll do my best to wrestle it out of my wife's hands
> tonight and test it (Not always easy to do). As I recall it was the TS-DOS
> injection you were having issues with.
>
> Kurt
>
>
> On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
>
> Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at
> the village
>
> lmk if you get a chance to test that newer android issue
>
> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:
>
>
> Yes, I am finally settled in my new place in Camarillo. Still unpacking
> but life is back to normal.
>
> Kurt
>
> On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
>
> Is it winter yet? :)did you ever escape?
>
> Greg
>
> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum  wrote:
>
>
> :) thanks. A lot more body surfing going on rather than web surfing. It
> will definitely be a summer to remember.
>
> On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
>
> Congratulations to Kurt McCullum on the list Quote of the Month
>
> "*I'm still stuck in a beach house with only one model-t*"
>
> :-)
>
> -- John.
>
>
>
>

Re: [M100] mcomm android issue

[Kurt McCullum]

Not yet Greg, but I did get the cables needed at I have access to an android 9 
phone. I'll do my best to wrestle it out of my wife's hands tonight and test it 
(Not always easy to do). As I recall it was the TS-DOS injection you were 
having issues with.

Kurt


On Tue, Mar 2, 2021, at 9:28 AM, Gregory McGill wrote:
> Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at the 
> village 
> 
> lmk if you get a chance to test that newer android issue
> 
> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:
>> __
>> Yes, I am finally settled in my new place in Camarillo. Still unpacking but 
>> life is back to normal.
>> 
>> Kurt
>> 
>> On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
>>> Is it winter yet? :)did you ever escape?
>>> 
>>> Greg
>>> 
>>> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum  wrote:
 __
 :) thanks. A lot more body surfing going on rather than web surfing. It 
 will definitely be a summer to remember.
 
 On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
> Congratulations to Kurt McCullum on the list Quote of the Month
> 
> "**I'm still stuck in a beach house with only one model-t**"
> 
> :-)
> 
> -- John.
 

Re: [M100] mcomm android issue

[Gregory McGill]

Glad to hear it! I grew up in 1000 oaks, my mom's still in Camarillo at the
village

lmk if you get a chance to test that newer android issue

On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:

> Yes, I am finally settled in my new place in Camarillo. Still unpacking
> but life is back to normal.
>
> Kurt
>
> On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
>
> Is it winter yet? :)did you ever escape?
>
> Greg
>
> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum  wrote:
>
>
> :) thanks. A lot more body surfing going on rather than web surfing. It
> will definitely be a summer to remember.
>
> On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
>
> Congratulations to Kurt McCullum on the list Quote of the Month
>
> "*I'm still stuck in a beach house with only one model-t*"
>
> :-)
>
> -- John.
>
>
>

Re: [M100] Mcomm on windows

[Brian K. White]

On 3/2/21 9:30 AM, AvantGuard Systems wrote:
Btw it seems logical that maybe the DISK option (F4) would access the 
virtual disk. But it always says communication error, something like that.


That is the correct button.

Communication error means there is a communication error. Either you 
don't have the right kind of serial cable (like it's missing the DSR/DTR 
lines), or no tpdd emulator (mComm) is running on the host, or it's 
running but not using the com port that goes to the 100, etc.


The TS-DOS manual is here:
http://www.club100.org/library/libdoc.html

--
bkw

Re: [M100] Mcomm on windows

[AvantGuard Systems]

Ok this was stupid Forget all that. Turns out I have unplug the cable
from the computer restart mcomm and then it works.

On Tue, Mar 2, 2021, 06:30 AvantGuard Systems <
cavaug...@avantguardsystems.com> wrote:

> Btw it seems logical that maybe the DISK option (F4) would access the
> virtual disk. But it always says communication error, something like that.
>
> On Tue, Mar 2, 2021, 06:27 AvantGuard Systems <
> cavaug...@avantguardsystems.com> wrote:
>
>> So last night I got mcomm up and running on a Windows machine.
>> Transferred TPDD over to my M100. Saved it. Now what? I've been searching
>> for instructions on how I now access files on my computer to transfer them
>> to the M100. It's emulating a disk, right, so what command do I use to load
>> a file?
>>
>

Re: [M100] Mcomm on windows

[AvantGuard Systems]

Btw it seems logical that maybe the DISK option (F4) would access the
virtual disk. But it always says communication error, something like that.

On Tue, Mar 2, 2021, 06:27 AvantGuard Systems <
cavaug...@avantguardsystems.com> wrote:

> So last night I got mcomm up and running on a Windows machine. Transferred
> TPDD over to my M100. Saved it. Now what? I've been searching for
> instructions on how I now access files on my computer to transfer them to
> the M100. It's emulating a disk, right, so what command do I use to load a
> file?
>

Re: [M100] mcomm

[Brian K. White]

On 3/1/21 9:18 PM, Peter Vollan wrote:
I just did that and it did not solve the problem. It has something to do 
with the starred expression.


Yes, and the something is that it was invalid syntax before python 3.5.

Perhaps you installed 3.5, but "/usr/bin/python3" is not linked to that 
version?


--
bkw


On Mon, 1 Mar 2021 at 17:46, Brian K. White > wrote:


On 3/1/21 5:22 PM, Kurt McCullum wrote:
 > SyntaxError: can use starred expression only as assignment target

Simply Googling the error message suggests you need Python 3.5 or later.

Which means in the source Kurt should update debian/control in his
source to say
    Depends: python3 (>= 3.5),python3-serial
and generate a new .deb

For now, for you, just manually get python 3.5 or later.

-- 
bkw





--
bkw

Re: [M100] mcomm

[Peter Vollan]

I just did that and it did not solve the problem. It has something to do
with the starred expression.


On Mon, 1 Mar 2021 at 17:46, Brian K. White  wrote:

> On 3/1/21 5:22 PM, Kurt McCullum wrote:
> > SyntaxError: can use starred expression only as assignment target
>
> Simply Googling the error message suggests you need Python 3.5 or later.
>
> Which means in the source Kurt should update debian/control in his
> source to say
>Depends: python3 (>= 3.5),python3-serial
> and generate a new .deb
>
> For now, for you, just manually get python 3.5 or later.
>
> --
> bkw
>

Re: [M100] mcomm

[Brian K. White]

On 3/1/21 5:22 PM, Kurt McCullum wrote:

SyntaxError: can use starred expression only as assignment target


Simply Googling the error message suggests you need Python 3.5 or later.

Which means in the source Kurt should update debian/control in his 
source to say

  Depends: python3 (>= 3.5),python3-serial
and generate a new .deb

For now, for you, just manually get python 3.5 or later.

--
bkw

Re: [M100] mcomm android issue

[John R. Hogerhuis]

On Mon, Mar 1, 2021 at 10:24 AM Joshua O'Keefe 
wrote:

>
> > On Feb 28, 2021, at 8:57 PM, John R. Hogerhuis  wrote:
> > So I'm halfway between you and Ken. We should have a west coast Club100
> meeting one of these days.
>
> I'm up in the California wine country and love an excuse to get out of the
> house -- once all this is under control, of course -- so count me in favor
> of a West Coast meetup.


Excellent. The more the merrier!

-- John.

Re: [M100] mcomm

[Kurt McCullum]

Alright, I'll have to dig into it to see what is causing that error.

Kurt

On Mon, Mar 1, 2021, at 1:28 PM, Peter Vollan wrote:
> Okay, no, I have python3
> 
> 
> On Mon, 1 Mar 2021 at 13:23, Kurt McCullum  wrote:
>> __
>> You will need python 3 to run it properly.
>> 
>> On Mon, Mar 1, 2021, at 1:09 PM, Peter Vollan wrote:
>>> I think it is 2.7
>>> 
>>> 
>>> On Mon, 1 Mar 2021 at 12:53, Kurt McCullum  wrote:
 __
 Great. Next check, is python3 installed. The DB installer should require 
 it, but I wanted to check.
 
 The error would indicate that its the *sys.argv[1:] which is causing the 
 error but I'll have to do some more digging as I have not run into this 
 one before.
 
 Kurt
 
 On Mon, Mar 1, 2021, at 12:42 PM, Peter Vollan wrote:
> yes, it is. I used the deb package installer/
> 
> 
> On Mon, 1 Mar 2021 at 12:40, Kurt McCullum  wrote:
>> __
>> is the file mcomm.py located in /usr/share/mcomm? The DEB installer will 
>> put it there but if you pulled it down manually then you need to make 
>> sure the paths are correct or tweak the code to look in the folder you 
>> placed the files.
>> 
>> Kurt
>> 
>> On Mon, Mar 1, 2021, at 12:16 PM, Peter Vollan wrote:
>>> Installing and then running mComm on my linux laptop, I got the 
>>> following error message:
>>> 
>>>   File "/usr/bin/mcomm", line 6
>>> subprocess.call(["python3", "/usr/share/mcomm/mcomm.py", 
>>> *sys.argv[1:]])
>>> ^
>>> SyntaxError: can use starred expression only as assignment target
>> 
 
>> 

Re: [M100] mcomm

[Peter Vollan]

Okay, no, I have python3


On Mon, 1 Mar 2021 at 13:23, Kurt McCullum  wrote:

> You will need python 3 to run it properly.
>
> On Mon, Mar 1, 2021, at 1:09 PM, Peter Vollan wrote:
>
> I think it is 2.7
>
>
> On Mon, 1 Mar 2021 at 12:53, Kurt McCullum  wrote:
>
>
> Great. Next check, is python3 installed. The DB installer should require
> it, but I wanted to check.
>
> The error would indicate that its the *sys.argv[1:] which is causing the
> error but I'll have to do some more digging as I have not run into this one
> before.
>
> Kurt
>
> On Mon, Mar 1, 2021, at 12:42 PM, Peter Vollan wrote:
>
> yes, it is. I used the deb package installer/
>
>
> On Mon, 1 Mar 2021 at 12:40, Kurt McCullum  wrote:
>
>
> is the file mcomm.py located in /usr/share/mcomm? The DEB installer will
> put it there but if you pulled it down manually then you need to make sure
> the paths are correct or tweak the code to look in the folder you placed
> the files.
>
> Kurt
>
> On Mon, Mar 1, 2021, at 12:16 PM, Peter Vollan wrote:
>
> Installing and then running mComm on my linux laptop, I got the following
> error message:
>
>   File "/usr/bin/mcomm", line 6
> subprocess.call(["python3", "/usr/share/mcomm/mcomm.py",
> *sys.argv[1:]])
> ^
> SyntaxError: can use starred expression only as assignment target
>
>
>
>
>

Re: [M100] mcomm

[Kurt McCullum]

You will need python 3 to run it properly.

On Mon, Mar 1, 2021, at 1:09 PM, Peter Vollan wrote:
> I think it is 2.7
> 
> 
> On Mon, 1 Mar 2021 at 12:53, Kurt McCullum  wrote:
>> __
>> Great. Next check, is python3 installed. The DB installer should require it, 
>> but I wanted to check.
>> 
>> The error would indicate that its the *sys.argv[1:] which is causing the 
>> error but I'll have to do some more digging as I have not run into this one 
>> before.
>> 
>> Kurt
>> 
>> On Mon, Mar 1, 2021, at 12:42 PM, Peter Vollan wrote:
>>> yes, it is. I used the deb package installer/
>>> 
>>> 
>>> On Mon, 1 Mar 2021 at 12:40, Kurt McCullum  wrote:
 __
 is the file mcomm.py located in /usr/share/mcomm? The DEB installer will 
 put it there but if you pulled it down manually then you need to make sure 
 the paths are correct or tweak the code to look in the folder you placed 
 the files.
 
 Kurt
 
 On Mon, Mar 1, 2021, at 12:16 PM, Peter Vollan wrote:
> Installing and then running mComm on my linux laptop, I got the following 
> error message:
> 
>   File "/usr/bin/mcomm", line 6
> subprocess.call(["python3", "/usr/share/mcomm/mcomm.py", 
> *sys.argv[1:]])
> ^
> SyntaxError: can use starred expression only as assignment target
 
>> 

Re: [M100] mcomm

[Peter Vollan]

I think it is 2.7


On Mon, 1 Mar 2021 at 12:53, Kurt McCullum  wrote:

> Great. Next check, is python3 installed. The DB installer should require
> it, but I wanted to check.
>
> The error would indicate that its the *sys.argv[1:] which is causing the
> error but I'll have to do some more digging as I have not run into this one
> before.
>
> Kurt
>
> On Mon, Mar 1, 2021, at 12:42 PM, Peter Vollan wrote:
>
> yes, it is. I used the deb package installer/
>
>
> On Mon, 1 Mar 2021 at 12:40, Kurt McCullum  wrote:
>
>
> is the file mcomm.py located in /usr/share/mcomm? The DEB installer will
> put it there but if you pulled it down manually then you need to make sure
> the paths are correct or tweak the code to look in the folder you placed
> the files.
>
> Kurt
>
> On Mon, Mar 1, 2021, at 12:16 PM, Peter Vollan wrote:
>
> Installing and then running mComm on my linux laptop, I got the following
> error message:
>
>   File "/usr/bin/mcomm", line 6
> subprocess.call(["python3", "/usr/share/mcomm/mcomm.py",
> *sys.argv[1:]])
> ^
> SyntaxError: can use starred expression only as assignment target
>
>
>
>

Re: [M100] mcomm

[Kurt McCullum]

Great. Next check, is python3 installed. The DB installer should require it, 
but I wanted to check.

The error would indicate that its the *sys.argv[1:] which is causing the error 
but I'll have to do some more digging as I have not run into this one before.

Kurt

On Mon, Mar 1, 2021, at 12:42 PM, Peter Vollan wrote:
> yes, it is. I used the deb package installer/
> 
> 
> On Mon, 1 Mar 2021 at 12:40, Kurt McCullum  wrote:
>> __
>> is the file mcomm.py located in /usr/share/mcomm? The DEB installer will put 
>> it there but if you pulled it down manually then you need to make sure the 
>> paths are correct or tweak the code to look in the folder you placed the 
>> files.
>> 
>> Kurt
>> 
>> On Mon, Mar 1, 2021, at 12:16 PM, Peter Vollan wrote:
>>> Installing and then running mComm on my linux laptop, I got the following 
>>> error message:
>>> 
>>>   File "/usr/bin/mcomm", line 6
>>> subprocess.call(["python3", "/usr/share/mcomm/mcomm.py", *sys.argv[1:]])
>>> ^
>>> SyntaxError: can use starred expression only as assignment target
>> 

Re: [M100] mcomm

[Peter Vollan]

yes, it is. I used the deb package installer/


On Mon, 1 Mar 2021 at 12:40, Kurt McCullum  wrote:

> is the file mcomm.py located in /usr/share/mcomm? The DEB installer will
> put it there but if you pulled it down manually then you need to make sure
> the paths are correct or tweak the code to look in the folder you placed
> the files.
>
> Kurt
>
> On Mon, Mar 1, 2021, at 12:16 PM, Peter Vollan wrote:
>
> Installing and then running mComm on my linux laptop, I got the following
> error message:
>
>   File "/usr/bin/mcomm", line 6
> subprocess.call(["python3", "/usr/share/mcomm/mcomm.py",
> *sys.argv[1:]])
> ^
> SyntaxError: can use starred expression only as assignment target
>
>
>

Re: [M100] mcomm

[Kurt McCullum]

is the file mcomm.py located in /usr/share/mcomm? The DEB installer will put it 
there but if you pulled it down manually then you need to make sure the paths 
are correct or tweak the code to look in the folder you placed the files.

Kurt

On Mon, Mar 1, 2021, at 12:16 PM, Peter Vollan wrote:
> Installing and then running mComm on my linux laptop, I got the following 
> error message:
> 
>   File "/usr/bin/mcomm", line 6
> subprocess.call(["python3", "/usr/share/mcomm/mcomm.py", *sys.argv[1:]])
> ^
> SyntaxError: can use starred expression only as assignment target

Re: [M100] mcomm

[☼ wil lindsay ☼]

What does it report when you check
python3 --version
on the command?

On Mon, Mar 1, 2021 at 3:17 PM Peter Vollan  wrote:

> Installing and then running mComm on my linux laptop, I got the following
> error message:
>
>   File "/usr/bin/mcomm", line 6
> subprocess.call(["python3", "/usr/share/mcomm/mcomm.py",
> *sys.argv[1:]])
> ^
> SyntaxError: can use starred expression only as assignment target
>

Re: [M100] mcomm android issue

[Joshua O'Keefe]

> On Feb 28, 2021, at 8:57 PM, John R. Hogerhuis  wrote:
> So I'm halfway between you and Ken. We should have a west coast Club100 
> meeting one of these days.

I'm up in the California wine country and love an excuse to get out of the 
house -- once all this is under control, of course -- so count me in favor of a 
West Coast meetup.

Re: [M100] mcomm android issue

[John R. Hogerhuis]

On Mon, Mar 1, 2021 at 8:37 AM Ken Pettit  wrote:

> On 3/1/21 8:20 AM, John R. Hogerhuis wrote:
> >
> > On the plus side our laptop has the advantage of great battery life
> > and a screen readable in bright sunlight.
> >
>
> This is true!  Though at the momemt I'm having a hard time seeing
> anything.  Looking forward to my cataract surgery in April.
>
>
I had to get glasses a few years ago after having excellent vision most of
my life. Age-related myopia. Glasses are a bummer, but it's a 100% fix for
now. Surgery is tempting though.

Is there some equivalent of frequent flier miles for surgery? You seem to
be under the knife a lot ;-)

Best wishes,

--- John.

Re: [M100] mcomm android issue

[Ken Pettit]

On 3/1/21 8:20 AM, John R. Hogerhuis wrote:


On the plus side our laptop has the advantage of great battery life 
and a screen readable in bright sunlight.




This is true!  Though at the momemt I'm having a hard time seeing 
anything.  Looking forward to my cataract surgery in April.


Ken

Re: [M100] mcomm android issue

[John R. Hogerhuis]

On Mon, Mar 1, 2021, 7:59 AM Ken Pettit  wrote:

> Yeah, maybe later this year after everyone has been vaccinated (and we
> actually know the vaccination works :).
>
> Ken
>
>
I'd guess around middle or late summer then based on how availability seems
to be going.


Other way would be to meet outside and physically distanced. On the plus
side our laptop has the advantage of great battery life and a screen
readable in bright sunlight.

-- John.

>
>

Re: [M100] mcomm android issue

[Ken Pettit]

Yeah, maybe later this year after everyone has been vaccinated (and we 
actually know the vaccination works :).


Ken

On 3/1/21 5:55 AM, Kurt McCullum wrote:

I'm up for that.

Kurt

On Sun, Feb 28, 2021, at 8:57 PM, John R. Hogerhuis wrote:



On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum > wrote:



Yes, I am finally settled in my new place in Camarillo. Still
unpacking but life is back to normal.

Kurt


So I'm halfway between you and Ken. We should have a west coast 
Club100 meeting one of these days.


-- John.

Re: [M100] mcomm android issue

[Kurt McCullum]

I'm up for that.

Kurt

On Sun, Feb 28, 2021, at 8:57 PM, John R. Hogerhuis wrote:
> 
> 
> On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:
>> __
>> Yes, I am finally settled in my new place in Camarillo. Still unpacking but 
>> life is back to normal.
>> 
>> Kurt
> 
> So I'm halfway between you and Ken. We should have a west coast Club100 
> meeting one of these days.
> 
> -- John. 

Re: [M100] mcomm android issue

[John R. Hogerhuis]

On Sun, Feb 28, 2021 at 8:51 PM Kurt McCullum  wrote:

> Yes, I am finally settled in my new place in Camarillo. Still unpacking
> but life is back to normal.
>
> Kurt
>

So I'm halfway between you and Ken. We should have a west coast Club100
meeting one of these days.

-- John.

Re: [M100] mcomm android issue

[Kurt McCullum]

Yes, I am finally settled in my new place in Camarillo. Still unpacking but 
life is back to normal.

Kurt

On Fri, Feb 26, 2021, at 3:09 PM, Gregory McGill wrote:
> Is it winter yet? :)did you ever escape?
> 
> Greg
> 
> On Fri, Jul 31, 2020 at 12:30 PM Kurt McCullum  wrote:
>> __
>> :) thanks. A lot more body surfing going on rather than web surfing. It will 
>> definitely be a summer to remember.
>> 
>> On Fri, Jul 31, 2020, at 12:27 PM, John R. Hogerhuis wrote:
>>> Congratulations to Kurt McCullum on the list Quote of the Month
>>> 
>>> "**I'm still stuck in a beach house with only one model-t**"
>>> 
>>> :-)
>>> 
>>> -- John.
>>