Re: [M100] RexCPM install

[Brian K. White]

I recently got dlplus working under cygwin and msys2, but I had to make 
changes to support it, it didn't work out of the box.
Were you using github.com/bkw777/dlplus or the zip file on bitchin100? 
It just worked or did you have to do anything to make it work?


I need to change the name of my fork. "dlplus" really still refers to 
John's version from the zip file on bitchin100.
And mine has deviated so far by now that it's no longer even very 
similar either inside or out.
And, I never liked that it was called dl-anything in the first place. 
DeskLink is Travelling Software's name, and so the original "dl for 
unix" and John's continuation "dlplus" should just not have been 
dl-anything in the first place, just like I should not call it 
LaddiePlus now.

But I don't know what.

dl2 makes the most sense if I didn't care about the "dl" part. It says 
what it is and what to expect correctly and succinctly.


vpdd ? virtual pdd,   meh
ndl ? new desklink or not desklink as you prefer,  meh
pddserver - just to needle Steve ;)
tpddd - tandy portable disk drive daemon , even I don't hate people that 
much

pdde ? maybe
fb100ulator - nailed it

--
bkw

On 10/16/22 17:33, Ben Wiley Sittler wrote:
I regularly use dlplus from a Cygwin command-line shell interface in 
Windows too, but I realize that's not everyone's cup of tea


On Sun, Oct 16, 2022, 14:29 Brian K. White  wrote:

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

Re: [M100] RexCPM install

[Ben Wiley Sittler]

Unlike wsl, cygwin has access to hardware (at least when run with suitable
permissions)

On Sun, Oct 16, 2022, 18:11 Brian White  wrote:

> It actually works from cygwin? I've actually never even tried it. (dlplus
> I mean, I used to use cygwin all the time but not in the last several
> years). I figured if WSL doesn't work then not even worth trying cygwin.
>
> I will try it and update the readme because this would be great.
>
>
> bkw
>
> On Sun, Oct 16, 2022, 5:33 PM Ben Wiley Sittler 
> wrote:
>
>> I regularly use dlplus from a Cygwin command-line shell interface in
>> Windows too, but I realize that's not everyone's cup of tea
>>
>> On Sun, Oct 16, 2022, 14:29 Brian K. White  wrote:
>>
>>> 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
>>> > 
>>> > 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  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
>>>
>>>

Re: [M100] RexCPM install

[Brian White]

It actually works from cygwin? I've actually never even tried it. (dlplus I
mean, I used to use cygwin all the time but not in the last several years).
I figured if WSL doesn't work then not even worth trying cygwin.

I will try it and update the readme because this would be great.


bkw

On Sun, Oct 16, 2022, 5:33 PM Ben Wiley Sittler  wrote:

> I regularly use dlplus from a Cygwin command-line shell interface in
> Windows too, but I realize that's not everyone's cup of tea
>
> On Sun, Oct 16, 2022, 14:29 Brian K. White  wrote:
>
>> 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
>> > 
>> > 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  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
>>
>>

Re: [M100] RexCPM install

[Ben Wiley Sittler]

I regularly use dlplus from a Cygwin command-line shell interface in
Windows too, but I realize that's not everyone's cup of tea

On Sun, Oct 16, 2022, 14:29 Brian K. White  wrote:

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

Re: [M100] RexCPM install

[Brian K. White]

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 


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

Re: [M100] RexCPM install

[Philip Avery]

Robert

Are you sure you're using the same TPDD emulator & any usb-serial cable 
as previously? LaddieAlpha is rock solid in my experience and CPMUPD 
will work, presuming REXCPM is operating normally.


Philip

On 17/10/2022 7:17 am, 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
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.

This is because the files are binary files with a .BK extension.
Also, make sure you load and run CPMUPD.CO  after 
you power off, power on.  This is to ensure you are in the default RAM 
config.



cheers
Steve



On Sat, Oct 15, 2022 at 5:24 PM Robert Hutchins 
 wrote:


Hi all,

Having trouble installing CPM into my Model 100 with the RexCPM
ROM kit.

I get the REX part installed, but am unable to get CPMUPD to do
its job…

It either just hangs, doing nothing or sometimes it will work, but
then, when it

prompts for the CPM file (CPM210.bk) it refuses to load this. Just
sits there hung…

Any ideas would be welcome.

At one point in the past,  I did have it working, but it expired
(batteries all died) .

Is there any chance the memory in the RexCPM device is failing…

Thank you

Robert J. Hutchins

Re: [M100] RexCPM install

[Stephen Adolph]

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
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.
This is because the files are binary files with a .BK extension.
Also, make sure you load and run CPMUPD.CO after you power off, power on.
This is to ensure you are in the default RAM config.


cheers
Steve



On Sat, Oct 15, 2022 at 5:24 PM Robert Hutchins 
wrote:

>
>
> Hi all,
>
>
>
> Having trouble installing CPM into my Model 100 with the RexCPM ROM kit.
>
> I get the REX part installed, but am unable to get CPMUPD to do its job…
>
>
>
> It either just hangs, doing nothing or sometimes it will work, but then,
> when it
>
> prompts for the CPM file (CPM210.bk) it refuses to load this. Just sits
> there hung…
>
>
>
> Any ideas would be welcome.
>
> At one point in the past,  I did have it working, but it expired
> (batteries all died) .
>
> Is there any chance the memory in the RexCPM device is failing…
>
>
>
> Thank you
>
> Robert J. Hutchins
>
>
>

[M100] RexCPM install

[Robert Hutchins]

 

Hi all,

 

Having trouble installing CPM into my Model 100 with the RexCPM ROM kit.

I get the REX part installed, but am unable to get CPMUPD to do its job.

 

It either just hangs, doing nothing or sometimes it will work, but then,
when it

prompts for the CPM file (CPM210.bk) it refuses to load this. Just sits
there hung.

 

Any ideas would be welcome.

At one point in the past,  I did have it working, but it expired (batteries
all died) .

Is there any chance the memory in the RexCPM device is failing.

 

Thank you

Robert J. Hutchins