On 10/16/22 14:17, Stephen Adolph wrote:
Hi Robert, couple of comments.
1) test your REXCPM. you can always test it yourself and see if you
have a hardware problem
https://bitchin100.com/wiki/index.php?title=REXCPM
<https://bitchin100.com/wiki/index.php?title=REXCPM>
read up on how to load and run REXCPM.
I would not do this if you are happy with the REX# part of the install.
In fact if that is working, likely no hardware problem.
There is only one memory chip and it is used for both REX# and CPM.
2) Philip's routines more or less rely on LaddieAlpha to operate. I
would recommend you use LaddieAlpha as the TPDD client.
Laddie is a server not a client. You confuse things by insisting on
using the wrong terminology in what are supposed to be reference documents.
I routinely use dlplus to reload rexcpm. But that's only available from
linux or mac. In fact thanks to the fact that you have packaged up
rxcini as a loader.do it makes it super convenient to use the
bootstrapper to directly run rxcini in one shot. Same for REX#. Thanks
much for that.
You can get that same convenience from Windows with a combination of
tsend.ps1 and laddie. Basically:
tsend.ps1 rxcini.DO ;laddiealpha.exe laddie-options-I-don't-remember
all one commandline.
github.com/bkw777/tsend.ps1
For Robert, I would make sure you're following the points about clearing
ram before trying to run cpmupd, and definitely use tpdd to copy cpmupd
to the machine in case you're not.
I think you'll have to list out all the actual steps you're performing
when you say doesn't work because "it works for me". But it doesn't
always work the first time just from memory.
The directions are somehow confusing to read and get the bullet points
that matter. Even though I've done it several times and have tried to
write down my own more direct version, I still end up having to pull up
the bitchin100 pages and refer to some points after it doesn't work the
first time just from memory. Usually I forget one of the two times you
should issue a clear statement.
This is because the files are binary files with a .BK extension.
Also, make sure you load and run CPMUPD.CO <http://CPMUPD.CO> after you
power off, power on. This is to ensure you are in the default RAM config.
There you go, exactly the kind of step I skip or forget the importance of.
But when I go back to the wiki page and don't skip anything, it always
works.
--
bkw
