Re: [M100] WiModem TPDD

[Tom Wilson]

Yup yup. Just need a male to male adapter.

On Thu, Apr 2, 2020 at 2:47 PM Joshua O'Keefe 
wrote:

>
>
> On Sun, Mar 29, 2020 at 1:21 PM John R. Hogerhuis 
> wrote:
>
>> On Sun, Mar 29, 2020 at 11:36 AM Stephen Adolph 
>> wrote:
>>
>>> 1) in an M100, is a genderchanger all that is needed?  or do you also
>>> need a null modem? any other considerations?
>>>
>>
>> Gender changer and power, that's it.
>>
>
> Just piping in to confirm this along with everyone else who did:  The
> WiModem232 is physically DCE (female connector) and electrically DCE.  With
> my 102 I reused the non-null gender changer from my existing wired setup
> (where the crossover is in the USB device rather than my cabling), and the
> WiModem232 works just fine.
>
-- 
Tom Wilson
wilso...@gmail.com
(619)940-6311
K6ABZ

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

On Sun, Mar 29, 2020 at 1:21 PM John R. Hogerhuis  wrote:

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

Just piping in to confirm this along with everyone else who did:  The
WiModem232 is physically DCE (female connector) and electrically DCE.  With
my 102 I reused the non-null gender changer from my existing wired setup
(where the crossover is in the USB device rather than my cabling), and the
WiModem232 works just fine.

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

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

I think that may be exactly what I'm running into.  I will try sending an 
escape sequence instead of CRs.  I remember the modems of yore required about a 
half second delay after the +++ sequence, I'll experiment with and without 
that.  

Anyone know offhand how many empty FOR loops per second a T gets?  That seems 
like a valuable constant to know.

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

On Thu, Apr 2, 2020 at 11:41 AM Joshua O'Keefe 
wrote:

>
> I've set LaddieAlpha up to re-start after the TCP connection closes by
> adding a simple while loop around invocation.
>

Are you saying that LaddieAlpha is exiting when the connection breaks?

It shouldn't do that. My test version doesn't do that.


>   This worked pretty well.  I also had more consistently positive results
> by modifying the wrapper to send a couple of CRs before dialing, because if
> the connection dropped the modem didn't always notice until there was some
> I/O.
>

Oh... I think I added a feature for Steve at some point, if you send
LaddieAlpha a newline by itself from TELCOM it exits. So maybe you are
making it exit.

Instead of CRs, What you probably want is to send the +++ escape to go back
to command mode so you can redial. I think you can send it even if you're
in command mode already.

Or you could set up Wimodem232 to autodial / maintain a
continuous connection.

But LaddieAlpha should stay open and accept a new connection over and over.
If it doesn't it's a bug.

-- John.

>

Re: [M100] WiModem TPDD

[Stephen Adolph]

regarding delay;

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

I agree that you probably don't need delay tolerance if your ping from
source to destination is ~1-2 of milliseconds.

On Thu, Apr 2, 2020 at 2:41 PM Joshua O'Keefe 
wrote:

> My WiModem232 arrived last night, so I thought I'd provide a bit of a trip
> report:
>
> I'm drawing WiModem power from a pocket size USB battery I had lying
> around unused.  It's a little awkward to splay out on your lap if you're on
> the couch, but it works!  I did have to scrounge around to find a USB Mini
> cable.  Almost everything in my black hole box of unused USB cables was USB
> Micro, of which I have entirely too many.
>
> John's procedure acted as an excellent guide to the basics of setting
> things up.  My peculiar Docker solution on the server side needed a little
> love to do the TCP connection thing, but once set up it worked on the first
> try using the BASIC wrapper to launch NEWDOS (which was left over from my
> experiments with NEWDOS + wired connection).  Interestingly enough, I had
> good success with NEWDOS browsing and loading without even enabling delay.
> My network is not especially low latency -- in fact the TPDD connection
> traverses three bridges across two floors of WiFi to Ethernet to MoCA and
> back to Ethernet -- so this came as something of a surprise.  I eventually
> settled on a delay factor of 1, which seems distinct from delay disabled.
> The only bugbear was the ongoing problem with apparent autobauding, which
> would still crop up every so very often.
>
> Unfortunately, I have had no luck *whatsoever* getting DOS-ON to work with
> NEWDOS -- be it over a wired connection or not.  I can get it to RX/TX a
> little before hanging again by manually opening and closing COM:98n1d
> before issuing commands, but not enough to be able to use a LFILES command
> or to load/save from 0:.  Setting delay factor did not help whatsoever.
> I'm not totally clear if this is an autobauding thing or the connection
> dropping when I MENU out of NEWDOS.  More experimentation needed.
>
> I've yet to try one of the un-delayed ROMs.  I'm not fond of the vanilla
> TS-DOS ROM available since it doesn't have the shift-down fix, but I'll
> give it a whirl to see if I have any success at all.
>
> I've set LaddieAlpha up to re-start after the TCP connection closes by
> adding a simple while loop around invocation.  This worked pretty well.  I
> also had more consistently positive results by modifying the wrapper to
> send a couple of CRs before dialing, because if the connection dropped the
> modem didn't always notice until there was some I/O.  If the connection is
> still up LaddieAlpha doesn't seem to mind the noise and if the connection
> is down, this seems to cause the modem to notice before attempting to dial.
>
> Thanks to everyone for helping get me this far.  It's been a fun project
> so far, and I'm quite interested in doing what I can to help make this a
> reliable solution for everyone.  WiFi TPDD is pretty sweet for those of us
> who like to wander the house with a T in hand.  And in the current world
> situation, I'm doing a lot of wandering around the house!
>
>
> On Tue, Mar 31, 2020 at 5:34 PM John R. Hogerhuis 
> wrote:
>
>> I had similar issues randomly when starting NEWDOS / LaddieAlpha.
>>
>> When it happened, what worked is to break out of NEWDOS (sometimes takes
>> a hitting reset button), go into TELCOM, stat 981ND, term, F8 Bye, CALL
>> NEWDOS again.
>>
>> The BASIC launcher I wrote has a similar effect since it opens the COM
>> port and sends the ATDT command. Since you're not doing that, maybe you
>> could just OPEN the com port at the 98N1D settings and then close it,
>> without having written anything.
>>
>> Ken says he disabled the DTR/DSR checking in NEWDOS which would be my
>> first guess for getting stuck at DISK mode, so my feeling is that the
>> autobauding is involved, and going back into TELCOM resets the port
>> settings.
>>
>> It's weird.
>>
>> If you want a debug version of LaddieAlpha I can share one and we can see
>> all the I/O serial traffic.
>>
>> -- John.
>>
>

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

My WiModem232 arrived last night, so I thought I'd provide a bit of a trip
report:

I'm drawing WiModem power from a pocket size USB battery I had lying around
unused.  It's a little awkward to splay out on your lap if you're on the
couch, but it works!  I did have to scrounge around to find a USB Mini
cable.  Almost everything in my black hole box of unused USB cables was USB
Micro, of which I have entirely too many.

John's procedure acted as an excellent guide to the basics of setting
things up.  My peculiar Docker solution on the server side needed a little
love to do the TCP connection thing, but once set up it worked on the first
try using the BASIC wrapper to launch NEWDOS (which was left over from my
experiments with NEWDOS + wired connection).  Interestingly enough, I had
good success with NEWDOS browsing and loading without even enabling delay.
My network is not especially low latency -- in fact the TPDD connection
traverses three bridges across two floors of WiFi to Ethernet to MoCA and
back to Ethernet -- so this came as something of a surprise.  I eventually
settled on a delay factor of 1, which seems distinct from delay disabled.
The only bugbear was the ongoing problem with apparent autobauding, which
would still crop up every so very often.

Unfortunately, I have had no luck *whatsoever* getting DOS-ON to work with
NEWDOS -- be it over a wired connection or not.  I can get it to RX/TX a
little before hanging again by manually opening and closing COM:98n1d
before issuing commands, but not enough to be able to use a LFILES command
or to load/save from 0:.  Setting delay factor did not help whatsoever.
I'm not totally clear if this is an autobauding thing or the connection
dropping when I MENU out of NEWDOS.  More experimentation needed.

I've yet to try one of the un-delayed ROMs.  I'm not fond of the vanilla
TS-DOS ROM available since it doesn't have the shift-down fix, but I'll
give it a whirl to see if I have any success at all.

I've set LaddieAlpha up to re-start after the TCP connection closes by
adding a simple while loop around invocation.  This worked pretty well.  I
also had more consistently positive results by modifying the wrapper to
send a couple of CRs before dialing, because if the connection dropped the
modem didn't always notice until there was some I/O.  If the connection is
still up LaddieAlpha doesn't seem to mind the noise and if the connection
is down, this seems to cause the modem to notice before attempting to dial.

Thanks to everyone for helping get me this far.  It's been a fun project so
far, and I'm quite interested in doing what I can to help make this a
reliable solution for everyone.  WiFi TPDD is pretty sweet for those of us
who like to wander the house with a T in hand.  And in the current world
situation, I'm doing a lot of wandering around the house!


On Tue, Mar 31, 2020 at 5:34 PM John R. Hogerhuis  wrote:

> I had similar issues randomly when starting NEWDOS / LaddieAlpha.
>
> When it happened, what worked is to break out of NEWDOS (sometimes takes a
> hitting reset button), go into TELCOM, stat 981ND, term, F8 Bye, CALL
> NEWDOS again.
>
> The BASIC launcher I wrote has a similar effect since it opens the COM
> port and sends the ATDT command. Since you're not doing that, maybe you
> could just OPEN the com port at the 98N1D settings and then close it,
> without having written anything.
>
> Ken says he disabled the DTR/DSR checking in NEWDOS which would be my
> first guess for getting stuck at DISK mode, so my feeling is that the
> autobauding is involved, and going back into TELCOM resets the port
> settings.
>
> It's weird.
>
> If you want a debug version of LaddieAlpha I can share one and we can see
> all the I/O serial traffic.
>
> -- John.
>

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

I was just thinking if you use the BUILDIT script you just need a framework
4.5 or higher.

On Tue, Mar 31, 2020, 6:00 PM Ken Pettit  wrote:

> Hey John,
>
> I'm trying to compile LaddieAlpha on Ubuntu 14.04 using mono-mcs. Have
> you ever tried this before?  I'm getting a bunch of compile errors, but
> have never programmed in C# before so don't really know if syntax like
> "s?.Close()" is legal or not.
>
> Ken
>
> On 3/31/20 5:34 PM, John R. Hogerhuis wrote:
> > I had similar issues randomly when starting NEWDOS / LaddieAlpha.
> >
> > When it happened, what worked is to break out of NEWDOS (sometimes
> > takes a hitting reset button), go into TELCOM, stat 981ND, term, F8
> > Bye, CALL NEWDOS again.
> >
> > The BASIC launcher I wrote has a similar effect since it opens the COM
> > port and sends the ATDT command. Since you're not doing that, maybe
> > you could just OPEN the com port at the 98N1D settings and then close
> > it, without having written anything.
> >
> > Ken says he disabled the DTR/DSR checking in NEWDOS which would be my
> > first guess for getting stuck at DISK mode, so my feeling is that the
> > autobauding is involved, and going back into TELCOM resets the port
> > settings.
> >
> > It's weird.
> >
> > If you want a debug version of LaddieAlpha I can share one and we can
> > see all the I/O serial traffic.
> >
> > -- John.
>
>

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

On Tue, Mar 31, 2020 at 6:00 PM Ken Pettit  wrote:

> Hey John,
>
> I'm trying to compile LaddieAlpha on Ubuntu 14.04 using mono-mcs. Have
> you ever tried this before?  I'm getting a bunch of compile errors, but
> have never programmed in C# before so don't really know if syntax like
> "s?.Close()" is legal or not.
>
> Ken
>
>
I used to only build with Linux. Lately I've been building with Visual
Studio.

It's legal but those are C# 7'isms. I guess I added those in recently.

You may need Visual Studio at the moment.

Or I can build it for you.

-- John.

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

> John:
> If you want a debug version of LaddieAlpha I can share one and we can see all 
> the I/O serial traffic

Happy to try it with a debug build and produce some logs.

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

On Mar 31, 2020, at 5:22 PM, Ken Pettit  wrote:
> 
> So when you say NEWDOS hangs, is this after hitting F4, for instance, to get 
> a DISK listing?  If the server wasn't responding, then I would expect NEWDOS 
> to simply print the "DRIVE NOT READY" error message.  Makes me think NEWDOS 
> is receiving *something*, but doesn't like what is returned and is getting 
> lost or

The behavior is that F4 clears the screen, prints the reverse text banner, 
doesn't RX or TX anything (or so little my RX/TX LEDs don't catch it), and does 
nothing.

Re: [M100] WiModem TPDD

[Ken Pettit]

Hey John,

I'm trying to compile LaddieAlpha on Ubuntu 14.04 using mono-mcs. Have 
you ever tried this before?  I'm getting a bunch of compile errors, but 
have never programmed in C# before so don't really know if syntax like 
"s?.Close()" is legal or not.


Ken

On 3/31/20 5:34 PM, John R. Hogerhuis wrote:

I had similar issues randomly when starting NEWDOS / LaddieAlpha.

When it happened, what worked is to break out of NEWDOS (sometimes 
takes a hitting reset button), go into TELCOM, stat 981ND, term, F8 
Bye, CALL NEWDOS again.


The BASIC launcher I wrote has a similar effect since it opens the COM 
port and sends the ATDT command. Since you're not doing that, maybe 
you could just OPEN the com port at the 98N1D settings and then close 
it, without having written anything.


Ken says he disabled the DTR/DSR checking in NEWDOS which would be my 
first guess for getting stuck at DISK mode, so my feeling is that the 
autobauding is involved, and going back into TELCOM resets the port 
settings.


It's weird.

If you want a debug version of LaddieAlpha I can share one and we can 
see all the I/O serial traffic.


-- John.

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

I had similar issues randomly when starting NEWDOS / LaddieAlpha.

When it happened, what worked is to break out of NEWDOS (sometimes takes a
hitting reset button), go into TELCOM, stat 981ND, term, F8 Bye, CALL
NEWDOS again.

The BASIC launcher I wrote has a similar effect since it opens the COM port
and sends the ATDT command. Since you're not doing that, maybe you could
just OPEN the com port at the 98N1D settings and then close it, without
having written anything.

Ken says he disabled the DTR/DSR checking in NEWDOS which would be my first
guess for getting stuck at DISK mode, so my feeling is that the autobauding
is involved, and going back into TELCOM resets the port settings.

It's weird.

If you want a debug version of LaddieAlpha I can share one and we can see
all the I/O serial traffic.

-- John.

Re: [M100] WiModem TPDD

[Ken Pettit]

So when you say NEWDOS hangs, is this after hitting F4, for instance, to 
get a DISK listing?  If the server wasn't responding, then I would 
expect NEWDOS to simply print the "DRIVE NOT READY" error message.  
Makes me think NEWDOS is receiving *something*, but doesn't like what is 
returned and is getting lost or something.


On 3/31/20 3:31 PM, Joshua O'Keefe wrote:

Happy to be a part of that effort in any way I can be of service.

I also tried Kurt's SARDOS-D with delay inbuilt, and it complains of disk not 
ready after a short burst of I/O.  Switching to any of the non-delayed ROMs 
restores functionality once LaddieAlpha is bounced.

The WiModem isn't here yet, so I can't tell you if any of this is reproducible 
via network.  I had just been hoping to pick one ROM loadout for both wired and 
wireless usage, so I've been experimenting with NEWDOS and other delay ROMs on 
a wired connection.




On Mar 31, 2020, at 3:04 PM, Ken Pettit  wrote:

Sounds like we (I) need to create a debug version of NEWDOS to figure out 
where it is getting lost or something.

Ken


On 3/31/20 2:56 PM, Joshua O'Keefe wrote:
Great idea!  Let me go try that...

Doing this caused it to work once! I went to go fish some RAM files out of a 
Rex backup and upon returning to NEWDOS: hang again.

Cold resetting and re-re-loading to REX didn't restore the functionality, nor 
did restarting my TPDD emulator.

The fact that it works once suggests there's some kind of state change 
somewhere along the line, but I'm not clear where.  I've tried resetting the 
state of LaddieAlpha (which was the only persistent thing between attempts)  at 
each step, but it doesn't change the story.

If I can get it back into "work once" mode I'll try to see if the causal action 
is invoking rexmgr, which is common to all these tries.


On Mar 31, 2020, at 2:17 PM, Ken Pettit  wrote:

Maybe try re-programming NEWDOS to your REX?

Ken


On 3/31/20 2:03 PM, Joshua O'Keefe wrote:

On Mar 31, 2020, at 1:55 PM, Ken Pettit  wrote:
 Try resetting everything and then running NEWDOS first instead of TS-DOS.

Alas, no joy on this approach either, with either LaddieAlpha or dlplus running 
at the other end.  Flipping to a vanilla rom (Or one of Kurt's ROMs) after 
resetting (warm or cold) works fine, so whatever's not quite right with my rig 
it's only NEWDOS that doesn't like it, whether NEWDOS goes first or second.  
I'm mystified here.

I've long since lost my RS-232 breakout box (by a good couple of decades), so 
the diagnostic information I can offer is only circumstantial at this point.

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

Happy to do a packet capture once this all moves to IP.  Of course, it may also 
just work.  At this point it's pure wired RS-232 -> USB with the unexpected 
behavior but I can try to do Unix Fanciness to cap what's happening on the tty 
if that helps.  I'd love to be able to just switch to NEWDOS as my daily driver 
and have it handle both wired and my eventual wireless connectivity.

To recap:

Working serial connection works with all un-delayed ROMs just the way you 
expect it to. (Vanilla TSDOS, SARDOS, Ultimate Rom bootstrapping to DOS100.CO)

Same serial connection works once and only once with NEWDOS on first boot; 
merely exiting to menu and coming back is enough to make it stop working, and 
invoking it with no delay solves nothing.

Serial connection works not at all with SARDOS-delayed, first or subsequent 
start, presumably because the delay is hard coded?

I want to try a fresh build of LaddieAlpha, because it does seem to wedge up 
after being used by NEWDOS, but I can't get it to compile.  Something about 
TPDD.cs causes an internal compiler error with the versions of Mono I have on 
hand.

> On Mar 31, 2020, at 3:40 PM, Stephen Adolph  wrote:
> 
> 
> I think what would be good is to get wireshark running somewhere in that IP 
> link.
> Ideally we should see a single packet carrying the request and a single 
> packet carrying the response.
> I don't know that this is necessary for good comms, but I have a feeling it 
> helps.
> 
> Joshua, are you familiar with Wireshark?  you should be able to see packets 
> ingressing and egressing from the USB port IP address.
> ..steve
> 
>> On Tue, Mar 31, 2020 at 6:32 PM Joshua O'Keefe  
>> wrote:
>> Happy to be a part of that effort in any way I can be of service.
>> 

Re: [M100] WiModem TPDD

[Stephen Adolph]

I think what would be good is to get wireshark running somewhere in that IP
link.
Ideally we should see a single packet carrying the request and a single
packet carrying the response.
I don't know that this is necessary for good comms, but I have a feeling it
helps.

Joshua, are you familiar with Wireshark?  you should be able to see packets
ingressing and egressing from the USB port IP address.
..steve

On Tue, Mar 31, 2020 at 6:32 PM Joshua O'Keefe 
wrote:

> Happy to be a part of that effort in any way I can be of service.
>
>

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

Happy to be a part of that effort in any way I can be of service.

I also tried Kurt's SARDOS-D with delay inbuilt, and it complains of disk not 
ready after a short burst of I/O.  Switching to any of the non-delayed ROMs 
restores functionality once LaddieAlpha is bounced.

The WiModem isn't here yet, so I can't tell you if any of this is reproducible 
via network.  I had just been hoping to pick one ROM loadout for both wired and 
wireless usage, so I've been experimenting with NEWDOS and other delay ROMs on 
a wired connection.



> On Mar 31, 2020, at 3:04 PM, Ken Pettit  wrote:
> 
> Sounds like we (I) need to create a debug version of NEWDOS to figure out 
> where it is getting lost or something.
> 
> Ken
> 
>> On 3/31/20 2:56 PM, Joshua O'Keefe wrote:
>> Great idea!  Let me go try that...
>> 
>> Doing this caused it to work once! I went to go fish some RAM files out of a 
>> Rex backup and upon returning to NEWDOS: hang again.
>> 
>> Cold resetting and re-re-loading to REX didn't restore the functionality, 
>> nor did restarting my TPDD emulator.
>> 
>> The fact that it works once suggests there's some kind of state change 
>> somewhere along the line, but I'm not clear where.  I've tried resetting the 
>> state of LaddieAlpha (which was the only persistent thing between attempts)  
>> at each step, but it doesn't change the story.
>> 
>> If I can get it back into "work once" mode I'll try to see if the causal 
>> action is invoking rexmgr, which is common to all these tries.
>> 
 On Mar 31, 2020, at 2:17 PM, Ken Pettit  wrote:
>>> 
>>> Maybe try re-programming NEWDOS to your REX?
>>> 
>>> Ken
>>> 
 On 3/31/20 2:03 PM, Joshua O'Keefe wrote:
> On Mar 31, 2020, at 1:55 PM, Ken Pettit  wrote:
>  Try resetting everything and then running NEWDOS first instead of 
> TS-DOS.
 Alas, no joy on this approach either, with either LaddieAlpha or dlplus 
 running at the other end.  Flipping to a vanilla rom (Or one of Kurt's 
 ROMs) after resetting (warm or cold) works fine, so whatever's not quite 
 right with my rig it's only NEWDOS that doesn't like it, whether NEWDOS 
 goes first or second.  I'm mystified here.
 
 I've long since lost my RS-232 breakout box (by a good couple of decades), 
 so the diagnostic information I can offer is only circumstantial at this 
 point.
> 

Re: [M100] WiModem TPDD

[Ken Pettit]

Sounds like we (I) need to create a debug version of NEWDOS to figure 
out where it is getting lost or something.


Ken

On 3/31/20 2:56 PM, Joshua O'Keefe wrote:

Great idea!  Let me go try that...

Doing this caused it to work once! I went to go fish some RAM files out of a 
Rex backup and upon returning to NEWDOS: hang again.

Cold resetting and re-re-loading to REX didn't restore the functionality, nor 
did restarting my TPDD emulator.

The fact that it works once suggests there's some kind of state change 
somewhere along the line, but I'm not clear where.  I've tried resetting the 
state of LaddieAlpha (which was the only persistent thing between attempts)  at 
each step, but it doesn't change the story.

If I can get it back into "work once" mode I'll try to see if the causal action 
is invoking rexmgr, which is common to all these tries.


On Mar 31, 2020, at 2:17 PM, Ken Pettit  wrote:

Maybe try re-programming NEWDOS to your REX?

Ken


On 3/31/20 2:03 PM, Joshua O'Keefe wrote:

On Mar 31, 2020, at 1:55 PM, Ken Pettit  wrote:
 Try resetting everything and then running NEWDOS first instead of TS-DOS.

Alas, no joy on this approach either, with either LaddieAlpha or dlplus running 
at the other end.  Flipping to a vanilla rom (Or one of Kurt's ROMs) after 
resetting (warm or cold) works fine, so whatever's not quite right with my rig 
it's only NEWDOS that doesn't like it, whether NEWDOS goes first or second.  
I'm mystified here.

I've long since lost my RS-232 breakout box (by a good couple of decades), so 
the diagnostic information I can offer is only circumstantial at this point.

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

Great idea!  Let me go try that...

Doing this caused it to work once! I went to go fish some RAM files out of a 
Rex backup and upon returning to NEWDOS: hang again.

Cold resetting and re-re-loading to REX didn't restore the functionality, nor 
did restarting my TPDD emulator.

The fact that it works once suggests there's some kind of state change 
somewhere along the line, but I'm not clear where.  I've tried resetting the 
state of LaddieAlpha (which was the only persistent thing between attempts)  at 
each step, but it doesn't change the story.

If I can get it back into "work once" mode I'll try to see if the causal action 
is invoking rexmgr, which is common to all these tries.

> On Mar 31, 2020, at 2:17 PM, Ken Pettit  wrote:
> 
> Maybe try re-programming NEWDOS to your REX?
> 
> Ken
> 
>> On 3/31/20 2:03 PM, Joshua O'Keefe wrote:
>>> On Mar 31, 2020, at 1:55 PM, Ken Pettit  wrote:
>>>  Try resetting everything and then running NEWDOS first instead of TS-DOS.
>> Alas, no joy on this approach either, with either LaddieAlpha or dlplus 
>> running at the other end.  Flipping to a vanilla rom (Or one of Kurt's ROMs) 
>> after resetting (warm or cold) works fine, so whatever's not quite right 
>> with my rig it's only NEWDOS that doesn't like it, whether NEWDOS goes first 
>> or second.  I'm mystified here.
>> 
>> I've long since lost my RS-232 breakout box (by a good couple of decades), 
>> so the diagnostic information I can offer is only circumstantial at this 
>> point.
> 

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

On Mar 31, 2020, at 1:55 PM, Ken Pettit  wrote:
> 
>  Try resetting everything and then running NEWDOS first instead of TS-DOS.

Alas, no joy on this approach either, with either LaddieAlpha or dlplus running 
at the other end.  Flipping to a vanilla rom (Or one of Kurt's ROMs) after 
resetting (warm or cold) works fine, so whatever's not quite right with my rig 
it's only NEWDOS that doesn't like it, whether NEWDOS goes first or second.  
I'm mystified here.

I've long since lost my RS-232 breakout box (by a good couple of decades), so 
the diagnostic information I can offer is only circumstantial at this point.

Re: [M100] WiModem TPDD

[Ken Pettit]

Try resetting everything and then running NEWDOS first instead of TS-DOS.

Ken

On 3/31/20 1:52 PM, Joshua O'Keefe wrote:

Thanks Ken!

I've reset everything on the wired end (including replugging the USB 
device to get a nice clean slate) and cold reset again just to see 
where things lie.

Cold reset then:
Plain TSDOS rom: works as expected
Switch to NEWDOS: hang at the DISK banner
CALL63013,1,1: same story
Switch back to vanilla ROM: works as expected

There's definitely something somewhere in my setup that NEWDOS doesn't 
like (although it worked once!) but I'm not clear what it is at this 
point.




On Mar 31, 2020, at 1:39 PM, Ken Pettit  wrote:

 Hi Joshua,

Well, a cold reset will fix any issue with the M100 side of the 
equation.  NEWDOS has no way of saving contextual information through 
a cold boot.  The only information it saves is within the "TS-DOS" 
menu launcher (which is actually a BASIC program with no .BA 
extension).  A cold boot would wipe this out, reseting to ground zero.


This would tend to indicate there is some issue with the "wired" end, 
whatever that is (I believe Steve already asked about that).


I guess you could try calling NEWDOS and specifically telling it not 
to use any delay to see if that makes any difference:


CALL 63012,1,1

Ken

On 3/31/20 1:24 PM, Joshua O'Keefe wrote:

Hi Ken,

In anticipation of my WiModem coming in I've decided to experiment 
with NEWDOS 5.05 while using my wired connection.  I got it to come 
up on the DISK screen both with and without a delay, but the next 
time I went back into TS-DOS all disk operations would hang.  Now 
I've even gone so far as to cold reset, and I still can't get a DISK 
screen to come up past the banner line. It just sits at the banner 
with no I/O attempted (from watching my serial LEDs) no matter what 
delay is set or disabled.


I'm not sure how to troubleshoot this.  As far as I can tell, NEWDOS 
is the only pure TSDOS ROM out there with the shift down fix -- 
although it's also in Kurt's SARDOS, but not his M100 TSDOS+Delay 
ROM -- so it's an obvious choice for me as an end user who does a 
bit of roaming around on the DISK screen.  If I can get it working 
again!


Any pointer where I should be looking to get it making I/O again? 
 This is just a plain old null modem connection that works just 
dandy with other ROMs, so I'm surprised to run into issues with NEWDOS.



On Mar 29, 2020, at 10:52 AM, Ken Pettit  wrote:

 Hey Gang,

It's amazing how much I have forgotten since 2014!

With NEWDOS 5.05, using the F7 Cfg option from within NEWDOS, you 
can enable and set the delay factor using a UI I had added.  This 
will not only change the delay factor for TPDD accesses, but also 
updates the "TS-DOS" MENU item with the selected delay.  So by 
simply choosing TS-DOS from MENU, it will configure for the 
selected delay factor, it it is enabled.


If you want to set IP address in WiModem232, you probably still 
need the shortcut BA that John detailed.


Ken

On 3/29/20 1:19 AM, John R. Hogerhuis wrote:



On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson > wrote:


Is NEWDOS a ROM we can install on Rex, or is it a COM file?


NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).

http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05 



-- John.

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

Thanks Ken!

I've reset everything on the wired end (including replugging the USB device to 
get a nice clean slate) and cold reset again just to see where things lie.  
Cold reset then:
Plain TSDOS rom: works as expected
Switch to NEWDOS: hang at the DISK banner
CALL63013,1,1: same story
Switch back to vanilla ROM: works as expected

There's definitely something somewhere in my setup that NEWDOS doesn't like 
(although it worked once!) but I'm not clear what it is at this point.


> On Mar 31, 2020, at 1:39 PM, Ken Pettit  wrote:
> 
>  Hi Joshua,
> 
> Well, a cold reset will fix any issue with the M100 side of the equation.  
> NEWDOS has no way of saving contextual information through a cold boot.  The 
> only information it saves is within the "TS-DOS" menu launcher (which is 
> actually a BASIC program with no .BA extension).  A cold boot would wipe this 
> out, reseting to ground zero.  
> 
> This would tend to indicate there is some issue with the "wired" end, 
> whatever that is (I believe Steve already asked about that).
> 
> I guess you could try calling NEWDOS and specifically telling it not to use 
> any delay to see if that makes any difference:
> 
> CALL 63012,1,1
> 
> Ken
> 
> On 3/31/20 1:24 PM, Joshua O'Keefe wrote:
>> Hi Ken,
>> 
>> In anticipation of my WiModem coming in I've decided to experiment with 
>> NEWDOS 5.05 while using my wired connection.  I got it to come up on the 
>> DISK screen both with and without a delay, but the next time I went back 
>> into TS-DOS all disk operations would hang.  Now I've even gone so far as to 
>> cold reset, and I still can't get a DISK screen to come up past the banner 
>> line. It just sits at the banner with no I/O attempted (from watching my 
>> serial LEDs) no matter what delay is set or disabled.
>> 
>> I'm not sure how to troubleshoot this.  As far as I can tell, NEWDOS is the 
>> only pure TSDOS ROM out there with the shift down fix -- although it's also 
>> in Kurt's SARDOS, but not his M100 TSDOS+Delay ROM -- so it's an obvious 
>> choice for me as an end user who does a bit of roaming around on the DISK 
>> screen.  If I can get it working again!
>> 
>> Any pointer where I should be looking to get it making I/O again?  This is 
>> just a plain old null modem connection that works just dandy with other 
>> ROMs, so I'm surprised to run into issues with NEWDOS.
>> 
>>> On Mar 29, 2020, at 10:52 AM, Ken Pettit  wrote:
>>> 
>>>  Hey Gang,
>>> 
>>> It's amazing how much I have forgotten since 2014!  
>>> 
>>> With NEWDOS 5.05, using the F7 Cfg option from within NEWDOS, you can 
>>> enable and set the delay factor using a UI I had added.  This will not only 
>>> change the delay factor for TPDD accesses, but also updates the "TS-DOS" 
>>> MENU item with the selected delay.  So by simply choosing TS-DOS from MENU, 
>>> it will configure for the selected delay factor, it it is enabled.
>>> 
>>> If you want to set IP address in WiModem232, you probably still need the 
>>> shortcut BA that John detailed.
>>> 
>>> Ken
>>> 
>>> On 3/29/20 1:19 AM, John R. Hogerhuis wrote:
 
 
 On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson  wrote:
> Is NEWDOS a ROM we can install on Rex, or is it a COM file?
> 
 
 NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).
 
 http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05
   
 
 -- John. 
>>> 
> 

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

The wired system is what I've been using all along: 
102 - gender - 25-9 - StarTech USB (with internal null) - /dev/ttyUSB0 - 
LaddieAlpha (or dlplus)

I can switch ROMs back to any other, and the connection lights right back up 
again, but something I'm doing isn't quite right for NEWDOS.  It works great 
with everything except NEWDOS, which hangs on DISK no matter the state.  In 
fact, the hang occurs even if I leave the cable off entirely, as though it's 
maybe a DTR/DSR thing?  Neither RX or TX LEDs flicker at all, so it doesn't 
seem to get even that far.

Resident commands hang similarly.



> On Mar 31, 2020, at 1:29 PM, Stephen Adolph  wrote:
> 
> 
> Can you describe the wired system?  M100 -RS232-??
> 
> 
>> On Tue, Mar 31, 2020 at 4:25 PM Joshua O'Keefe  
>> wrote:
>> Hi Ken,
>> 
>> In anticipation of my WiModem coming in I've decided to experiment with 
>> NEWDOS 5.05 while using my wired connection.  I got it to come up on the 
>> DISK screen both with and without a delay, but the next time I went back 
>> into TS-DOS all disk operations would hang.  Now I've even gone so far as to 
>> cold reset, and I still can't get a DISK screen to come up past the banner 
>> line. It just sits at the banner with no I/O attempted (from watching my 
>> serial LEDs) no matter what delay is set or disabled.
>> 
>> I'm not sure how to troubleshoot this.  As far as I can tell, NEWDOS is the 
>> only pure TSDOS ROM out there with the shift down fix -- although it's also 
>> in Kurt's SARDOS, but not his M100 TSDOS+Delay ROM -- so it's an obvious 
>> choice for me as an end user who does a bit of roaming around on the DISK 
>> screen.  If I can get it working again!
>> 
>> Any pointer where I should be looking to get it making I/O again?  This is 
>> just a plain old null modem connection that works just dandy with other 
>> ROMs, so I'm surprised to run into issues with NEWDOS.
>> 
 On Mar 29, 2020, at 10:52 AM, Ken Pettit  wrote:
 
>>>  Hey Gang,
>>> 
>>> It's amazing how much I have forgotten since 2014!  
>>> 
>>> With NEWDOS 5.05, using the F7 Cfg option from within NEWDOS, you can 
>>> enable and set the delay factor using a UI I had added.  This will not only 
>>> change the delay factor for TPDD accesses, but also updates the "TS-DOS" 
>>> MENU item with the selected delay.  So by simply choosing TS-DOS from MENU, 
>>> it will configure for the selected delay factor, it it is enabled.
>>> 
>>> If you want to set IP address in WiModem232, you probably still need the 
>>> shortcut BA that John detailed.
>>> 
>>> Ken
>>> 
>>> On 3/29/20 1:19 AM, John R. Hogerhuis wrote:
 
 
 On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson  wrote:
> Is NEWDOS a ROM we can install on Rex, or is it a COM file?
> 
 
 NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).
 
 http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05
   
 
 -- John. 
>>> 

Re: [M100] WiModem TPDD

[Ken Pettit]

Hi Joshua,

Well, a cold reset will fix any issue with the M100 side of the 
equation.  NEWDOS has no way of saving contextual information through a 
cold boot.  The only information it saves is within the "TS-DOS" menu 
launcher (which is actually a BASIC program with no .BA extension).  A 
cold boot would wipe this out, reseting to ground zero.


This would tend to indicate there is some issue with the "wired" end, 
whatever that is (I believe Steve already asked about that).


I guess you could try calling NEWDOS and specifically telling it not to 
use any delay to see if that makes any difference:


CALL 63012,1,1

Ken

On 3/31/20 1:24 PM, Joshua O'Keefe wrote:

Hi Ken,

In anticipation of my WiModem coming in I've decided to experiment 
with NEWDOS 5.05 while using my wired connection.  I got it to come up 
on the DISK screen both with and without a delay, but the next time I 
went back into TS-DOS all disk operations would hang.  Now I've even 
gone so far as to cold reset, and I still can't get a DISK screen to 
come up past the banner line. It just sits at the banner with no I/O 
attempted (from watching my serial LEDs) no matter what delay is set 
or disabled.


I'm not sure how to troubleshoot this.  As far as I can tell, NEWDOS 
is the only pure TSDOS ROM out there with the shift down fix -- 
although it's also in Kurt's SARDOS, but not his M100 TSDOS+Delay ROM 
-- so it's an obvious choice for me as an end user who does a bit of 
roaming around on the DISK screen.  If I can get it working again!


Any pointer where I should be looking to get it making I/O again? 
 This is just a plain old null modem connection that works just dandy 
with other ROMs, so I'm surprised to run into issues with NEWDOS.



On Mar 29, 2020, at 10:52 AM, Ken Pettit  wrote:

 Hey Gang,

It's amazing how much I have forgotten since 2014!

With NEWDOS 5.05, using the F7 Cfg option from within NEWDOS, you can 
enable and set the delay factor using a UI I had added.  This will 
not only change the delay factor for TPDD accesses, but also updates 
the "TS-DOS" MENU item with the selected delay.  So by simply 
choosing TS-DOS from MENU, it will configure for the selected delay 
factor, it it is enabled.


If you want to set IP address in WiModem232, you probably still need 
the shortcut BA that John detailed.


Ken

On 3/29/20 1:19 AM, John R. Hogerhuis wrote:



On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson > wrote:


Is NEWDOS a ROM we can install on Rex, or is it a COM file?


NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).

http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05 



-- John.

Re: [M100] WiModem TPDD

[Stephen Adolph]

Can you describe the wired system?  M100 -RS232-??


On Tue, Mar 31, 2020 at 4:25 PM Joshua O'Keefe 
wrote:

> Hi Ken,
>
> In anticipation of my WiModem coming in I've decided to experiment with
> NEWDOS 5.05 while using my wired connection.  I got it to come up on the
> DISK screen both with and without a delay, but the next time I went back
> into TS-DOS all disk operations would hang.  Now I've even gone so far as
> to cold reset, and I still can't get a DISK screen to come up past the
> banner line. It just sits at the banner with no I/O attempted (from
> watching my serial LEDs) no matter what delay is set or disabled.
>
> I'm not sure how to troubleshoot this.  As far as I can tell, NEWDOS is
> the only pure TSDOS ROM out there with the shift down fix -- although it's
> also in Kurt's SARDOS, but not his M100 TSDOS+Delay ROM -- so it's an
> obvious choice for me as an end user who does a bit of roaming around on
> the DISK screen.  If I can get it working again!
>
> Any pointer where I should be looking to get it making I/O again?  This is
> just a plain old null modem connection that works just dandy with other
> ROMs, so I'm surprised to run into issues with NEWDOS.
>
> On Mar 29, 2020, at 10:52 AM, Ken Pettit  wrote:
>
>  Hey Gang,
>
> It's amazing how much I have forgotten since 2014!
>
> With NEWDOS 5.05, using the F7 Cfg option from within NEWDOS, you can
> enable and set the delay factor using a UI I had added.  This will not only
> change the delay factor for TPDD accesses, but also updates the "TS-DOS"
> MENU item with the selected delay.  So by simply choosing TS-DOS from MENU,
> it will configure for the selected delay factor, it it is enabled.
>
> If you want to set IP address in WiModem232, you probably still need the
> shortcut BA that John detailed.
>
> Ken
>
> On 3/29/20 1:19 AM, John R. Hogerhuis wrote:
>
>
>
> On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson  wrote:
>
>> Is NEWDOS a ROM we can install on Rex, or is it a COM file?
>>
>>
> NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).
>
>
> http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05
>
>
> -- John.
>
>
>

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

Hi Ken,

In anticipation of my WiModem coming in I've decided to experiment with NEWDOS 
5.05 while using my wired connection.  I got it to come up on the DISK screen 
both with and without a delay, but the next time I went back into TS-DOS all 
disk operations would hang.  Now I've even gone so far as to cold reset, and I 
still can't get a DISK screen to come up past the banner line. It just sits at 
the banner with no I/O attempted (from watching my serial LEDs) no matter what 
delay is set or disabled.

I'm not sure how to troubleshoot this.  As far as I can tell, NEWDOS is the 
only pure TSDOS ROM out there with the shift down fix -- although it's also in 
Kurt's SARDOS, but not his M100 TSDOS+Delay ROM -- so it's an obvious choice 
for me as an end user who does a bit of roaming around on the DISK screen.  If 
I can get it working again!

Any pointer where I should be looking to get it making I/O again?  This is just 
a plain old null modem connection that works just dandy with other ROMs, so I'm 
surprised to run into issues with NEWDOS.

> On Mar 29, 2020, at 10:52 AM, Ken Pettit  wrote:
> 
>  Hey Gang,
> 
> It's amazing how much I have forgotten since 2014!  
> 
> With NEWDOS 5.05, using the F7 Cfg option from within NEWDOS, you can enable 
> and set the delay factor using a UI I had added.  This will not only change 
> the delay factor for TPDD accesses, but also updates the "TS-DOS" MENU item 
> with the selected delay.  So by simply choosing TS-DOS from MENU, it will 
> configure for the selected delay factor, it it is enabled.
> 
> If you want to set IP address in WiModem232, you probably still need the 
> shortcut BA that John detailed.
> 
> Ken
> 
> On 3/29/20 1:19 AM, John R. Hogerhuis wrote:
>> 
>> 
>> On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson  wrote:
>>> Is NEWDOS a ROM we can install on Rex, or is it a COM file?
>>> 
>> 
>> NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).
>> 
>> http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05
>>   
>> 
>> -- John. 
> 

Re: [M100] WiModem TPDD

[Josh Malone]

On Sun, Mar 29, 2020 at 2:36 PM Stephen Adolph  wrote:

> So a few questions abouit WiModem232:
>
> 1) in an M100, is a genderchanger all that is needed?  or do you also need
> a null modem? any other considerations?
>

Only gender changer required. The device is DCE.

2) has anyone measured the power supply current?  any chance it is <50mA?
>

I don't know specifically, but I *have* run mine off the 5vdc available at
the BCR port. The batteries have to be alkaline for that -- the NiMH
voltage is not sufficient. I would *guess* that transmit current is over
50mA though.

-Josh

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

On Sun, Mar 29, 2020 at 11:36 AM Stephen Adolph 
wrote:

> So a few questions abouit WiModem232:
>
> 1) in an M100, is a genderchanger all that is needed?  or do you also need
> a null modem? any other considerations?
>
> 2) has anyone measured the power supply current?  any chance it is <50mA?
>
>
Gender changer and power, that's it.

Manual says:

" How much power does the WiModem232 use? A: The WiModem232 uses an average
of ~80mA while transmitting and ~25mA while receiving. OLED option uses
~10mA more current."

Note that there are two different versions, one with a display and one
without. I guess if you're minimizing current draw you would want the one
without. It has a AT command style interface so a display isn't really
necessary. The LED is sufficient to indicate general status.

The only feature I wish this thing had was autobauding for command mode.
It's a pretty well thought out device.

-- John.

Re: [M100] WiModem TPDD

[Fred Whitaker]

The original instructions called for a Null Modem.
Fred Whitaker

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10


From: M100  on behalf of Stephen Adolph 

Sent: Sunday, March 29, 2020 2:35:46 PM
To: m...@bitchin100.com 
Subject: Re: [M100] WiModem TPDD

So a few questions abouit WiModem232:

1) in an M100, is a genderchanger all that is needed?  or do you also need a 
null modem? any other considerations?

2) has anyone measured the power supply current?  any chance it is <50mA?

thx


On Sat, Mar 28, 2020 at 12:54 PM Joshua O'Keefe 
mailto:maj...@nachomountain.com>> wrote:
Has anyone tried to wire up one of the TPDD emulators with socat or something 
to make it network accessible, and then tried reaching it from a WiModem type 
device?  Having wireless storage seems like it would be a great boon, but most 
of the remnants I see in the Club100 library seem to be about some kind of 
mysterious Bluetooth rig.  It seems like it'd be simpler to just hook an 
emulator to a pty, wire up the other end to a TCP listen socket with socat, 
then just dial up the TPDD with a WiModem.

Has this been tried?  Am I insane?  This seems like it would be straightforward 
to set up with off the shelf parts and commonly available glue software.

As if I needed yet another excuse to spring for a WiModem.

Re: [M100] WiModem TPDD

[Stephen Adolph]

So a few questions abouit WiModem232:

1) in an M100, is a genderchanger all that is needed?  or do you also need
a null modem? any other considerations?

2) has anyone measured the power supply current?  any chance it is <50mA?

thx


On Sat, Mar 28, 2020 at 12:54 PM Joshua O'Keefe 
wrote:

> Has anyone tried to wire up one of the TPDD emulators with socat or
> something to make it network accessible, and then tried reaching it from a
> WiModem type device?  Having wireless storage seems like it would be a
> great boon, but most of the remnants I see in the Club100 library seem to
> be about some kind of mysterious Bluetooth rig.  It seems like it'd be
> simpler to just hook an emulator to a pty, wire up the other end to a TCP
> listen socket with socat, then just dial up the TPDD with a WiModem.
>
> Has this been tried?  Am I insane?  This seems like it would be
> straightforward to set up with off the shelf parts and commonly available
> glue software.
>
> As if I needed yet another excuse to spring for a WiModem.

Re: [M100] WiModem TPDD

[Ken Pettit]

Hey Gang,

It's amazing how much I have forgotten since 2014!

With NEWDOS 5.05, using the F7 Cfg option from within NEWDOS, you can 
enable and set the delay factor using a UI I had added.  This will not 
only change the delay factor for TPDD accesses, but also updates the 
"TS-DOS" MENU item with the selected delay.  So by simply choosing 
TS-DOS from MENU, it will configure for the selected delay factor, it it 
is enabled.


If you want to set IP address in WiModem232, you probably still need the 
shortcut BA that John detailed.


Ken

On 3/29/20 1:19 AM, John R. Hogerhuis wrote:



On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson > wrote:


Is NEWDOS a ROM we can install on Rex, or is it a COM file?


NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).

http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05 



-- John.

Re: [M100] WiModem TPDD

[Ken Pettit]

On 3/29/20 1:19 AM, John R. Hogerhuis wrote:



On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson > wrote:


Is NEWDOS a ROM we can install on Rex, or is it a COM file?


NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).

http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05 



I guess to be accurate, NEWDOS is actually not just a patched verion of 
TS-DOS.  It is actually a re-assembly of it.  I had fully disassembled 
TS-DOS into a file that can be re-assemled by VirtualT.  I then added 
features to it, including detection of running on VirtualT, fixing the 
DISK scroll bug, adding programmable delay, and ignoring DSR.


Reviewing the code and reminding myself what I did in 2014, I had 
actually added an F7 key hander (non-DISK mode) to provide a UI 
interface for setting the delay factor directly within NEWDOS.  But it 
has no place to save this delay factor ... just useful for easily 
dialing in a delay factor that can be used in a BASIC call.


Ken

Re: [M100] WiModem TPDD

[Ken Pettit]

Hey Guys,

I just realized that I never published the source assembly for NEWDOS.  
I will get that added to my Personal Libraries, along with the VirtualT 
IDE project files for building it.


Ken

On 3/29/20 1:19 AM, John R. Hogerhuis wrote:



On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson > wrote:


Is NEWDOS a ROM we can install on Rex, or is it a COM file?


NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).

http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05 



-- John.

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

On Sat, Mar 28, 2020 at 11:08 PM Tom Wilson  wrote:

> Is NEWDOS a ROM we can install on Rex, or is it a COM file?
>
>
NEWDOS is a patched version of TS-DOS to install in REX (or a OptROM).

http://www.club100.org/memfiles/index.php?=0==Ken%20Pettit/NewDos/VER5.05


-- John.

Re: [M100] WiModem TPDD

[Tom Wilson]

Is NEWDOS a ROM we can install on Rex, or is it a COM file?


Tom Wilson
wilso...@gmail.com
(619)940-6311
K6ABZ


On Sat, Mar 28, 2020 at 10:56 PM John R. Hogerhuis  wrote:

> I wrote a small program to dial the TCP connection and launch NEWDOS with
> the delay. Seems to work reliably.
>
> 10 OPEN"COM:98N1E"FOROUTPUTAS1:?#1,"ATDT 192.168.1.85:8085
> ":CLOSE1:CALL63013,2,2:MENU
>
> SAVE"DIAL
>
> Replace the IP and port with your TCP listener.
>
> -- John.
>

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

I wrote a small program to dial the TCP connection and launch NEWDOS with
the delay. Seems to work reliably.

10 OPEN"COM:98N1E"FOROUTPUTAS1:?#1,"ATDT 192.168.1.85:8085
":CLOSE1:CALL63013,2,2:MENU

SAVE"DIAL

Replace the IP and port with your TCP listener.

-- John.

Re: [M100] WiModem TPDD

[Kurt McCullum]

No plans yet. I suppose I could add it at some point but I need to make sure 
all the TPDD stuff is solid. It's looking good so far but lots of testing 
needed. The reason for going to Python was two create a version of mComm that 
people could tweak to their liking on various platforms. I'm in the process of 
downsizing for a move. I've already let go of my T200 and the TPDD2 and 
possibly the T102 will eventually go. I use my NEC units daily so those stay. 
I'd like to leave some clean code for the M100 community to work with and 
Python seemed to be a good way to do that. The Sardine stuff needs to be 
documented so others can fiddle with it. I'll continue to develop mComm but 
having an open source version will benefit everyone.

The TS-DOS delay issue is a problem. If it doesn't get a response fast enough 
it switches to 9600 baud and then it fails. There are a few options to get 
around this. NEWDOS has a delay you can adjust. In my user folder on Club100 
there are versions of TS-DOS and SARDOS that have delays built in. Those were 
developed when I created the Bluetooth capability in the Android version of 
mComm. 

Between John's Laddie Alpha and the Windows version of mComm you should find a 
solution that will work with your WiModem232

Kurt

On Sat, Mar 28, 2020, at 6:56 PM, Joshua O'Keefe wrote:
>> On Mar 28, 2020, at 6:01 PM, Kurt McCullum  wrote:
>> Gary Weber (Of Web8201.net fame) had me modify the windows version of mComm 
>> to work with WiModem232.
> 
> Kurt, were you planning to bring the TCP functionality forward into your new 
> (Python, I think you said?) version of mComm? The potential for Sardine 
> compatibility from the living room sounds mighty tempting once I can try it 
> on my storage system.
> 
>> John said:
>> Here is my write-up regarding using Wimodem232 + NewDOS + LaddieAlpha
>> http://bitchin100.com/wiki/index.php?title=Connecting_NEWDOS_to_Wimodem232 
> 
> Thanks John, this looks like fun. I'll try it when my WiModem gets here -- 
> the possibility of having LAN and WAN access to storage opens up a few more 
> daily driver use cases for me.
> 
> You said you ran into DTR issues, I wonder if the DTR checks can just be 
> NOPped out. I guess it's time for me to go learn to read 8085 while I wait 
> for my modem to get here.

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

On Sat, Mar 28, 2020 at 6:57 PM Joshua O'Keefe 
wrote:

>
> You said you ran into DTR issues, I wonder if the DTR checks can just be
> NOPped out.  I guess it's time for me to go learn to read 8085 while I wait
> for my modem to get here.
>

yeah I have a question out to Ken.

If it's DTR/DSR issue it could be resolve on the Wimodem232. By
default though it is supposed to loop back DTR-DSR which is all we're
supposed to need.

The other possibility is that the autobauding is still being triggered
sometimes. TS-DOS attempts to switch baud rates if it encounters
difficulty. Generally TPDD drives ran at two speeds, 19200bps or 9600bps.
TS-DOS it starts at 19200bps, and if there are communication problems it
switches down to 9600bps (and for a TPDD emulator, generally make
everything worse).

-- John.

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

> On Mar 28, 2020, at 6:01 PM, Kurt McCullum  wrote:
> Gary Weber (Of Web8201.net fame) had me modify the windows version of mComm 
> to work with WiModem232.

Kurt, were you planning to bring the TCP functionality forward into your new 
(Python, I think you said?)  version of mComm?  The potential for Sardine 
compatibility from the living room sounds mighty tempting once I can try it on 
my storage system.

> John said:
> Here is my write-up regarding using Wimodem232 + NewDOS + LaddieAlpha
> http://bitchin100.com/wiki/index.php?title=Connecting_NEWDOS_to_Wimodem232  

Thanks John, this looks like fun.  I'll try it when my WiModem gets here -- the 
possibility of having LAN and WAN access to storage opens up a few more daily 
driver use cases for me.

You said you ran into DTR issues, I wonder if the DTR checks can just be NOPped 
out.  I guess it's time for me to go learn to read 8085 while I wait for my 
modem to get here.

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

Here is my write-up regarding using Wimodem232 + NewDOS + LaddieAlpha

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

-- John.

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

On Sat, Mar 28, 2020 at 6:01 PM Kurt McCullum  wrote:

> Gary Weber (Of Web8201.net fame) had me modify the windows version of
> mComm to work with WiModem232. I don't think I ever released it as an
> install but it does exist. Basically, the WiModem connects on IP port 1983
> (The year the model-t was released) instead of a com port. He had to use
> the version of SARDOS that has built in delays because there is a little
> lag but the last I heard from him it was working well. He may chime in with
> his experience.
>
> Kurt
>
>
I have the same feature in LaddieAlpha. I talked to Ken and now I'm having
success with it too.

Mainly it's just an issue of using NEWDOS 5.05 (See Ken Pettit's Personal
Directory at Club100), launching it with a sufficient delay/timeout factor.

To listen:
.\LaddieAlpha.EXE tcp://*:8085

To dial from Wimodem:
AT*B19200
ATDT 192.168.1.85:8085

Start NEWDOS 5.05 in delay mode:
CALL 63013,2,2

Enter Disk mode
F4 (Disk)

seems to work. Mostly. I think I'm seeing the DTR/DSR handshake issue
sometimes when first entering Disk mode. Seems to resolve by resetting,
popping in an out of TELCOM Term with stat 98N1D

I'm writing up some more detailed instructions.

-- John.

Re: [M100] WiModem TPDD

[Kurt McCullum]

Gary Weber (Of Web8201.net fame) had me modify the windows version of mComm to 
work with WiModem232. I don't think I ever released it as an install but it 
does exist. Basically, the WiModem connects on IP port 1983 (The year the 
model-t was released) instead of a com port. He had to use the version of 
SARDOS that has built in delays because there is a little lag but the last I 
heard from him it was working well. He may chime in with his experience.

Kurt

On Sat, Mar 28, 2020, at 9:38 AM, Joshua O'Keefe wrote:
> Has anyone tried to wire up one of the TPDD emulators with socat or something 
> to make it network accessible, and then tried reaching it from a WiModem type 
> device? Having wireless storage seems like it would be a great boon, but most 
> of the remnants I see in the Club100 library seem to be about some kind of 
> mysterious Bluetooth rig. It seems like it'd be simpler to just hook an 
> emulator to a pty, wire up the other end to a TCP listen socket with socat, 
> then just dial up the TPDD with a WiModem.
> 
> Has this been tried? Am I insane? This seems like it would be straightforward 
> to set up with off the shelf parts and commonly available glue software.
> 
> As if I needed yet another excuse to spring for a WiModem.

[M100] WiModem TPDD

[Stephen Adolph]

It would be great to get a reference solution that can be shown to work
reliably.

I was never really happy with bluetooth as an intermediate translation
layer to TCP ip.

However I do think with the right attention it should be workable.
Especially If the translation layer knows TPDD speak.  Then you'd never end
up with fragmented exchanges.

For example.  How does adaptation to tcp decide when is end of packet?



On Saturday, March 28, 2020, Joshua O'Keefe 
wrote:

> On Mar 28, 2020, at 4:40 PM, Stephen Adolph  wrote:
> >
> > Give it a whirl!
>
> Steve, you are doing a terrible job dissuading me from trying to score a
> WiModem.  Of course, I could also hang it off the back of the Amiga, and I
> can't reuse the one on the C64 as it's wired for a Commodore User Port
> instead of RS232, so I have another excuse for needing a second Wi-Fi modem.
>
> Between this and John's offhanded mention of LaddieAlpha TCP mode (which I
> was not aware of previously) I guess it's time to go do my bit for the
> retro computer economy!

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

On Mar 28, 2020, at 4:40 PM, Stephen Adolph  wrote:
> 
> Give it a whirl!  

Steve, you are doing a terrible job dissuading me from trying to score a 
WiModem.  Of course, I could also hang it off the back of the Amiga, and I 
can't reuse the one on the C64 as it's wired for a Commodore User Port instead 
of RS232, so I have another excuse for needing a second Wi-Fi modem.

Between this and John's offhanded mention of LaddieAlpha TCP mode (which I was 
not aware of previously) I guess it's time to go do my bit for the retro 
computer economy!

Re: [M100] WiModem TPDD

[Stephen Adolph]

Give it a whirl!
Iirc, you have to have enough delay to let TCP do its thing.
Also, a complication is when the TPDD packet is split across two or more ip
packets.



On Saturday, March 28, 2020, Joshua O'Keefe 
wrote:

> On Mar 28, 2020, at 4:20 PM, Stephen Adolph  wrote:
>
>
> Ken made a version of newdos that had no timeout I believe, and that is
> what used in my experiment.
> Dont know if I could find it again...  would have to take a look
>
>>
> How high did you crank the newdos delay value?  It looks like it can allow
> really long delays: http://www.club100.org/memfiles/index.php?action=
> view=NEWDOS.DO=Ken%20Pettit/NewDos/VER5.05&
>
> Sorry for all the questions about this, but I am trying to determine how
> badly I want that WiModem as they seem to have become scarce since I last
> looked.
>

Re: [M100] WiModem TPDD

[Joshua O'Keefe]

On Mar 28, 2020, at 4:20 PM, Stephen Adolph  wrote:
> 
> Ken made a version of newdos that had no timeout I believe, and that is what 
> used in my experiment.
> Dont know if I could find it again...  would have to take a look

How high did you crank the newdos delay value?  It looks like it can allow 
really long delays: 
http://www.club100.org/memfiles/index.php?action=view=NEWDOS.DO=Ken%20Pettit/NewDos/VER5.05;

Sorry for all the questions about this, but I am trying to determine how badly 
I want that WiModem as they seem to have become scarce since I last looked.

Re: [M100] WiModem TPDD

[Stephen Adolph]

Ken made a version of newdos that had no timeout I believe, and that is
what used in my experiment.
Dont know if I could find it again...  would have to take a look.


On Saturday, March 28, 2020, John R. Hogerhuis  wrote:

> OK, so... yes  I see the same problems with TS-DOS and tcp mode that
> everyone else does.
>
> I tried TS-DOS and NEWDOS that were loaded into my Rex... no difference.
> They hang timing out on the many little directory extension messages.
>
> One thing about the WiModem232 generally, is that you need to be in 600
> baud mode (48N1D) while configuring it, transferring plain text files via
> TELCOM, etc. because the Model 100 screen is so slow.
>
> But once you want to use TPDD mode you need to switch the wimodem baud to
> 19200 and your TELCOM stat to 98N1D. Just realize that if you do any AT
> commands on the wimodem you'll lose everything after the first 64
> characters because of overrun.
>
> I did transfer TEENYX.DO to my laptop and that works fine with tcp mode.
>
> So TS-DOS basically not working over Wifi. TEENY works over wifi.
>
> I think the problem is the directory extensions.
>
> What is needed is a TS-DOS version with much longer timeouts or not
> timeouts.
>
> -- John.
>
>>

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

OK, so... yes  I see the same problems with TS-DOS and tcp mode that
everyone else does.

I tried TS-DOS and NEWDOS that were loaded into my Rex... no difference.
They hang timing out on the many little directory extension messages.

One thing about the WiModem232 generally, is that you need to be in 600
baud mode (48N1D) while configuring it, transferring plain text files via
TELCOM, etc. because the Model 100 screen is so slow.

But once you want to use TPDD mode you need to switch the wimodem baud to
19200 and your TELCOM stat to 98N1D. Just realize that if you do any AT
commands on the wimodem you'll lose everything after the first 64
characters because of overrun.

I did transfer TEENYX.DO to my laptop and that works fine with tcp mode.

So TS-DOS basically not working over Wifi. TEENY works over wifi.

I think the problem is the directory extensions.

What is needed is a TS-DOS version with much longer timeouts or not
timeouts.

-- John.

>

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

The "delay loops" or timeouts are not part of the tpdd protocol. They're
just a feature of tsdos. Using another Tpdd client, like teeny tells the
tale.

But only if you've also addressed the cable check dtr/DSR issue. I think
this is a setting or jumper on most of these devices to assert DSR. There
are also patched versions of teeny that do no cable check. You can create a
DSR asserting patched version of teeny when you inload using TEENY.EXE.

I will try my wimodem thingy again and update the group.

-- John.

Re: [M100] WiModem TPDD

[Josh Malone]

>
> Ah - okay cool. Didn't realize that.
>
>

Re: [M100] WiModem TPDD

[B4 Me100]

I don¹t think TPDD uses hardware handshaking it relies on delay loops.  The
TPDD drive generates DSR to indicate there is something present which is
required by the ROM drivers.

When I tried it via an ESP12 to LaddieAlpha the big issue was the variable
delay even with a modified TPDD I could not get it to work satisfactorily.
It would work briefly then the WiFi would stall and that would be game over.
I did try to buffer the TPDD file in the ESP (32K is not a lot of data) and
then write it to LaddieAlpha but could not get it to work reliably. I gave
up and just used the ESP as a TPDD drive and then FTP¹d files to and from a
server via the ESP12.

From:  M100  on behalf of Josh Malone

Reply-To:  
Date:  Saturday, March 28, 2020 at 11:10 AM
To:  
Subject:  Re: [M100] WiModem TPDD

> I don't think the WiModem does the hardware flow control needed by tpdd
> protocol. I might try this with my Rickards modem though.
> 
> On Sat, Mar 28, 2020, 2:02 PM Tom Wilson  wrote:
>> I tried it with a CBMStuff Wimodem 232 talking to LaddieAlpha running in TCP
>> mode. No joy. 
>> 
>> I didn¹t try very hard, so there may be a combination of settings that does
>> work, but I was never able to get it to work.
>> 
>> On Sat, Mar 28, 2020 at 10:39 AM Gregory McGill 
>> wrote:
>>> most wimodems are locked to a baud rate and don't support hardware
>>> handshaking.. may make it tough to set up also they only support 8bits no
>>> parity.. with the exception of the gurumodem which does 7 bits and even/odd
>>> parity as well
>>> 
>>> 
>>> On Sat, Mar 28, 2020 at 9:38 AM Joshua O'Keefe 
>>> wrote:
>>>> Has anyone tried to wire up one of the TPDD emulators with socat or
>>>> something to make it network accessible, and then tried reaching it from a
>>>> WiModem type device?  Having wireless storage seems like it would be a
>>>> great boon, but most of the remnants I see in the Club100 library seem to
>>>> be about some kind of mysterious Bluetooth rig.  It seems like it'd be
>>>> simpler to just hook an emulator to a pty, wire up the other end to a TCP
>>>> listen socket with socat, then just dial up the TPDD with a WiModem.
>>>> 
>>>> Has this been tried?  Am I insane?  This seems like it would be
>>>> straightforward to set up with off the shelf parts and commonly available
>>>> glue software.
>>>> 
>>>> As if I needed yet another excuse to spring for a WiModem.
>> -- 
>> Tom Wilson
>> wilso...@gmail.com
>> (619)940-6311 
>> K6ABZ

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

Tpdd protocol doesn't do any flow control. It's purely request/response.

It does do a cable check dtr/dsr.

TSDOS itself has cable check, and timeout issues in some cases.

I recommend to loop back dtr/DSR if your device cannot assert DSR and use
teeny. It has no timeout issues. Also there are versions of tsdos to work
around timeout issues.

I just suggest to try with TEENY as a diagnostic.

-- John.

On Sat, Mar 28, 2020, 11:10 AM Josh Malone  wrote:

> I don't think the WiModem does the hardware flow control needed by tpdd
> protocol. I might try this with my Rickards modem though.
>
> On Sat, Mar 28, 2020, 2:02 PM Tom Wilson  wrote:
>
>> I tried it with a CBMStuff Wimodem 232 talking to LaddieAlpha running in
>> TCP mode. No joy.
>>
>> I didn’t try very hard, so there may be a combination of settings that
>> does work, but I was never able to get it to work.
>>
>> On Sat, Mar 28, 2020 at 10:39 AM Gregory McGill 
>> wrote:
>>
>>> most wimodems are locked to a baud rate and don't support hardware
>>> handshaking.. may make it tough to set up also they only support 8bits no
>>> parity.. with the exception of the gurumodem which does 7 bits and even/odd
>>> parity as well
>>>
>>>
>>> On Sat, Mar 28, 2020 at 9:38 AM Joshua O'Keefe 
>>> wrote:
>>>
 Has anyone tried to wire up one of the TPDD emulators with socat or
 something to make it network accessible, and then tried reaching it from a
 WiModem type device?  Having wireless storage seems like it would be a
 great boon, but most of the remnants I see in the Club100 library seem to
 be about some kind of mysterious Bluetooth rig.  It seems like it'd be
 simpler to just hook an emulator to a pty, wire up the other end to a TCP
 listen socket with socat, then just dial up the TPDD with a WiModem.

 Has this been tried?  Am I insane?  This seems like it would be
 straightforward to set up with off the shelf parts and commonly available
 glue software.

 As if I needed yet another excuse to spring for a WiModem.
>>>
>>> --
>> Tom Wilson
>> wilso...@gmail.com
>> (619)940-6311
>> K6ABZ
>>
>

Re: [M100] WiModem TPDD

[John R. Hogerhuis]

That's what the feature is there for and it worked when I last tested it.

You might want to try with TEENY instead since it has no timeouts like
tsdos does.

Also you might be having cable handshake (dtr/dsr) issues. Model t' require
DSR.

-- John.

Re: [M100] WiModem TPDD

[Josh Malone]

I don't think the WiModem does the hardware flow control needed by tpdd
protocol. I might try this with my Rickards modem though.

On Sat, Mar 28, 2020, 2:02 PM Tom Wilson  wrote:

> I tried it with a CBMStuff Wimodem 232 talking to LaddieAlpha running in
> TCP mode. No joy.
>
> I didn’t try very hard, so there may be a combination of settings that
> does work, but I was never able to get it to work.
>
> On Sat, Mar 28, 2020 at 10:39 AM Gregory McGill 
> wrote:
>
>> most wimodems are locked to a baud rate and don't support hardware
>> handshaking.. may make it tough to set up also they only support 8bits no
>> parity.. with the exception of the gurumodem which does 7 bits and even/odd
>> parity as well
>>
>>
>> On Sat, Mar 28, 2020 at 9:38 AM Joshua O'Keefe 
>> wrote:
>>
>>> Has anyone tried to wire up one of the TPDD emulators with socat or
>>> something to make it network accessible, and then tried reaching it from a
>>> WiModem type device?  Having wireless storage seems like it would be a
>>> great boon, but most of the remnants I see in the Club100 library seem to
>>> be about some kind of mysterious Bluetooth rig.  It seems like it'd be
>>> simpler to just hook an emulator to a pty, wire up the other end to a TCP
>>> listen socket with socat, then just dial up the TPDD with a WiModem.
>>>
>>> Has this been tried?  Am I insane?  This seems like it would be
>>> straightforward to set up with off the shelf parts and commonly available
>>> glue software.
>>>
>>> As if I needed yet another excuse to spring for a WiModem.
>>
>> --
> Tom Wilson
> wilso...@gmail.com
> (619)940-6311
> K6ABZ
>

Re: [M100] WiModem TPDD

[Tom Wilson]

I tried it with a CBMStuff Wimodem 232 talking to LaddieAlpha running in
TCP mode. No joy.

I didn’t try very hard, so there may be a combination of settings that does
work, but I was never able to get it to work.

On Sat, Mar 28, 2020 at 10:39 AM Gregory McGill 
wrote:

> most wimodems are locked to a baud rate and don't support hardware
> handshaking.. may make it tough to set up also they only support 8bits no
> parity.. with the exception of the gurumodem which does 7 bits and even/odd
> parity as well
>
>
> On Sat, Mar 28, 2020 at 9:38 AM Joshua O'Keefe 
> wrote:
>
>> Has anyone tried to wire up one of the TPDD emulators with socat or
>> something to make it network accessible, and then tried reaching it from a
>> WiModem type device?  Having wireless storage seems like it would be a
>> great boon, but most of the remnants I see in the Club100 library seem to
>> be about some kind of mysterious Bluetooth rig.  It seems like it'd be
>> simpler to just hook an emulator to a pty, wire up the other end to a TCP
>> listen socket with socat, then just dial up the TPDD with a WiModem.
>>
>> Has this been tried?  Am I insane?  This seems like it would be
>> straightforward to set up with off the shelf parts and commonly available
>> glue software.
>>
>> As if I needed yet another excuse to spring for a WiModem.
>
> --
Tom Wilson
wilso...@gmail.com
(619)940-6311
K6ABZ

Re: [M100] WiModem TPDD

[Gregory McGill]

most wimodems are locked to a baud rate and don't support hardware
handshaking.. may make it tough to set up also they only support 8bits no
parity.. with the exception of the gurumodem which does 7 bits and even/odd
parity as well


On Sat, Mar 28, 2020 at 9:38 AM Joshua O'Keefe 
wrote:

> Has anyone tried to wire up one of the TPDD emulators with socat or
> something to make it network accessible, and then tried reaching it from a
> WiModem type device?  Having wireless storage seems like it would be a
> great boon, but most of the remnants I see in the Club100 library seem to
> be about some kind of mysterious Bluetooth rig.  It seems like it'd be
> simpler to just hook an emulator to a pty, wire up the other end to a TCP
> listen socket with socat, then just dial up the TPDD with a WiModem.
>
> Has this been tried?  Am I insane?  This seems like it would be
> straightforward to set up with off the shelf parts and commonly available
> glue software.
>
> As if I needed yet another excuse to spring for a WiModem.

Re: [M100] WiModem TPDD

[Stephen Adolph]

I once was running LaddieAlpha over TCP/IP through my firewall so that I
could access the TPDD while connecting over serial bluetooth to Wifi.

M100 -->  bluetooth --> (android phone as a bridge) {cloud} {house}
-- firewall --- server(LaddieAlpha)

was fun to accomplish.


On Sat, Mar 28, 2020 at 12:54 PM Joshua O'Keefe 
wrote:

> Has anyone tried to wire up one of the TPDD emulators with socat or
> something to make it network accessible, and then tried reaching it from a
> WiModem type device?  Having wireless storage seems like it would be a
> great boon, but most of the remnants I see in the Club100 library seem to
> be about some kind of mysterious Bluetooth rig.  It seems like it'd be
> simpler to just hook an emulator to a pty, wire up the other end to a TCP
> listen socket with socat, then just dial up the TPDD with a WiModem.
>
> Has this been tried?  Am I insane?  This seems like it would be
> straightforward to set up with off the shelf parts and commonly available
> glue software.
>
> As if I needed yet another excuse to spring for a WiModem.

[M100] WiModem TPDD

[Joshua O'Keefe]

Has anyone tried to wire up one of the TPDD emulators with socat or something 
to make it network accessible, and then tried reaching it from a WiModem type 
device?  Having wireless storage seems like it would be a great boon, but most 
of the remnants I see in the Club100 library seem to be about some kind of 
mysterious Bluetooth rig.  It seems like it'd be simpler to just hook an 
emulator to a pty, wire up the other end to a TCP listen socket with socat, 
then just dial up the TPDD with a WiModem.

Has this been tried?  Am I insane?  This seems like it would be straightforward 
to set up with off the shelf parts and commonly available glue software.

As if I needed yet another excuse to spring for a WiModem.