Did you try mComm for Windows?
http://www.club100.org/memfiles/index.php?&direction=0&order=&directory=Kurt%20McCullum
(Setup250.EXE)
The key points to that are, it's a windows executable that is not only a
TPDD emulator but also includes a bootstrapper to install TS-DOS or
TEENY onto the M100, and the serial port access is all coded into the
binary where there is no chance to get anything wrong, no question about
if the app or the serial port is configured right or anything. That
eliminates some possible question marks.
I would try using mComm to bootstrap TS-DOS or TEENY (either one is
fine) and then use TS-DOS or TEENY to copy whatever REXCPM setup files
are needed over to the M100.
Then if that doesn't work I'd double-check the serial port cabling.
http://tandy.wiki/Model_T_Serial_Cable
Even if your cable seems to work ok in telcom, just check every wire
against that table anyway, or just buy the PCCables 00103 or Cables2Go
03019 just to remove all doubt.
And definitely try some other host machine like you just said, some
other laptop, or an Android phone or tablet with the Android version of
mComm. Even if you don't want to use any other machine normally, it's
still a required diagnostic step just to dispose of another variable.
Actually using the Android mComm would also require getting a usb-serial
adapter, which you could use right on your win10 desktop instead of the
built in com port. A built-in com port should be the gold standard and
work better than any usb adapter, but you still just have to try
something else, anything else, as a diagnostic test.
----
I think I may try to make a tpdd2-style bootstrapper written in cmd or
powershell for windows, and bash for everything else, that can bootstrap
arbitrary things like the REX bootstrap utils.
dlplus can already bootstrap arbitrary files like that, it doesn't have
to be one of the bundled dos installers, but I don't have a Windows
build of dlplus. Maybe I'll just do that instead.
The bootstrapper code in dlplus or mComm works very reliably, and is
about as convenient as possible for the user, and is simple enough that
I think it can be written in powershell and bash. I could probably make
a Windows executable from the existing plain c version, but the routine
is simple enough that I don't think it needs to be a compiled binary,
and all else being equal, a readable/editable script is better than an
inscrutable binary, even if the source for the binary is available.
There is a python version of mComm already, which is a readable/editable
script, but on Windows that would mean you have to install some version
of python which is annoying on Windows. There are several different ways
to get python on Windows and no real standard, and no guarantee that one
install doesn't conflict with or perturb some other possible install,
because they each want to put themselves into the system PATH variable etc.
You shouldn't need to bootstrap TS-DOS or TEENY just to use it one time
to transfer one file*. The same process could just as well bootstrap
that file directly.
*(You never use it again, because once REX is bootstrapped, you have
TS-DOS in rom instead.)
We probably don't even need Steve to change RXCINI.DO to work from a RUN
COM:... command. If it doesn't already work naturally, we can probably
just use LOAD COM:... followed by save or run.
And if mComm can bootstrap arbitrary files besides the bundled dos
installers, then there you go, may already be a more robust REX
bootstrap recipe already available, just needs to be tried.
--
bkw
On 11/15/20 12:52 PM, [email protected] wrote:
Steve,
I was not successful trying to get Teeny into my M100. Same for
LaddieAlpha.
I think that my 64-bit Win10 laptop is not capable of sending just text
as a file transfer. I tried TeraTerm, and Putty with no luck (although
TeraTerm was the most helpful via configuration options).
I will fire up my old Win7 laptop (32-bit) and start over. At least I
will have HyperTerm there.
More later,
Bob
*From:* M100 <[email protected]> *On Behalf Of
*[email protected]
*Sent:* Sunday, November 15, 2020 11:21 AM
*To:* [email protected]
*Subject:* Re: [M100] STRUGGLING to get REXCPM loaded
Steve,
I thought about this a lot. I suspect that my method of getting
RXCINI.DO into the M100 is the key flaw, not your work at all.
I will next:
1. Check the REXCPM physical installation
2. Try Teeny
More later. All this just reminds me of how computers were back when
they were in their adolescence.
And we still call it “fun” don’t we? <smile> Actually, it is truly
fun in a problem-solving = satisfaction way. I guess that is the
engineer in me coming out. And this is a lot more fun than having a
boss looking over my shoulder as I tried to get a manufacturing plant up
and running properly (I was an automatic controls – process
instrumentation – engineer for DuPont for 34 years).
Have a good day!
Bob
*From:* M100 <[email protected]
<mailto:[email protected]>> *On Behalf Of *Stephen Adolph
*Sent:* Saturday, November 14, 2020 8:36 PM
*To:* [email protected] <mailto:[email protected]>
*Subject:* Re: [M100] STRUGGLING to get REXCPM loaded
I had an experience where the file simply wasn't transferred correctly
(7 bit), and it crashed. Not sure what to say Bob. Did you try
checking that all springs are making good contact?
I test every REXCPM with each mated adapter and cable before I send it out.
Try loading Teeny.do, create teeny.co <http://teeny.co> and use that to
load rxcini.do.
On Saturday, November 14, 2020, <[email protected]
<mailto:[email protected]>> wrote:
Steve,
I successfully transferred the RXCTST.DO file and ran it.
Same kind of a message as before, but it gets to 4 dots on the
second line before the machine turns off. Turning the power on
shows the results of a cold start. Same kind of failure as with RXCINI.
Before each try, I cold started the machine and cycled the power.
Still stuck.
Sorry,
Bob
*From:* M100 <[email protected]
<mailto:[email protected]>> *On Behalf Of *Stephen
Adolph
*Sent:* Saturday, November 14, 2020 7:37 PM
*To:* [email protected] <mailto:[email protected]>
*Subject:* Re: [M100] STRUGGLING to get REXCPM loaded
If you continue to struggle, try this:
http://bitchin100.com/wiki/index.php?title=REXCPM#Test_your_REXCPM_Installation
<http://bitchin100.com/wiki/index.php?title=REXCPM#Test_your_REXCPM_Installation>
On Sat, Nov 14, 2020 at 7:35 PM Stephen Adolph <[email protected]
<mailto:[email protected]>> wrote:
Hi Bob,
my guess is that there are one of 2 things wrong.
1) the socket has some loose connections or
2) the 8 bit transfer didn't go as planned and there is
something amiss with RXCINI.DO
I must say, I need to make my utilities more bulletproof. I
think I will adopt the Ron Weisen encoding...7 bit.
Steve
On Sat, Nov 14, 2020 at 4:06 PM <[email protected]
<mailto:[email protected]>> wrote:
Hello all!
Today I finally tried to install REXCPM in my M100. I have
not yet succeeded. Any suggestions would sure be
appreciated. Here is the scenario:
Using a Null Modem cable, I transferred the RXCINI.DO file
carefully to the M100. I used 1200baud with TeraTerm on my
Dell Win10 laptop, 8 bits, etc. My Dell Win10 machine came
with a Dell external device that provides supports legacy
ports via USB cable to an external box with physical serial,
parallel, Ethernet, and USB connections.
The transfer was successful and I looked at the lines of
code in the .DO file and compared to a screen listing of
RXCINI (used Notepad). All good.
I connect my NADSbox with RXC_11.BR <http://RXC_11.BR> AND
RXCINI.DO In the root directory and using the cable that I
have always used with my NADSbox. Then I start through the
steps found onthe Bitchin100 page:
http://bitchin100.com/wiki/index.php?title=REXCPM
<http://bitchin100.com/wiki/index.php?title=REXCPM>
I at step 4, I select Yes to both options, and Y to proceed.
I see a line on my screen that shows dots appearing:
Loading at: 62000 <…………………….
..
Note that I see only two dots on the last line then the
screen goes off with the M100 powered off. When I turn it
back on, it is apparent that a cold start has occurred.
I have repeated all the steps carefully at least 4 times
(Cold started M100, transfer RXCINI.DO, RUN”RXCINI”. I
never get to step 6. The result is always the same.
I am pretty sure that my transfer of RXCINI.DO is not corrupted.
Any suggestions?
Thanks in advance,
Bob
--
bkw
