Re: [M100] CRC error in 57600 Y

[John R. Hogerhuis]

On Wed, Apr 13, 2022, 6:20 PM Brian K. White  wrote:

>
>
> In another post which possibly hasn't posted yet or possibly went to
> spam, I gave a lot of links and details to garanteed ways to do it,
> which uses a dedicated bootstrapper program to send the initial RX#U1.DO
> and either dlplus or laddiealpha for the tpdd server. These are known to
> work. Anything else is "might work". But the bulletproof simple ways
> currently need windows or linux or mac. There is no bootstrapper for
> ms-dos. (Well, the original dos desklink does supposedly have a
> bootstrapper function by creating a file named loader.ba and then you
> can issue a command from the 100 to trigger it, but I've never got that
> to actually work)
>
> So if you still want to use ms-dos on the host side, you'll have to do
> so trial & error to figure out why you're getting a corrupt transfer of
> the initial RX*.DO file. Doing it manually leaves many opportunities for
> leading junk, trailing junk, bad line-endings, and dropped characters
> from gpoing too fast. You'll have to say *exactly* what you did or else
> there is no way to guess what might have gone wrong.
>


I saw your original post that covered a .PS1 injector and whatnot

Might just open it with a text editor and see if there's anything obviously
misaligned.

The usual corruption of ASCII transfers is because of dropped characters
due to no flow control or flow control that is not working reliably.

-- John.

>

Re: [M100] CRC error in 57600 Y

[Brian K. White]

(re-sending from a different account, I sent this earlier but it never 
showed up)



Desklink is fine, and that checksum message is probably about the 
initial ascii transfer of RX#U1.DO . It's easy to get a corrupt copy 
with a manual ascii transfer, and so it has a self-check that it runs 
before doing anything else, to prevent running a corrupt copy.


Expanding on that,

The old dos desklink works perfectly well, but that doesn't neessarily 
ensure it will work with rex/rex# setup, because rex setup doesn't even 
work with a real tpdd1 or tpdd2.


There is a weakness in the tpdd routines in the rex tools, which makes 
"bad choice?" a complicated question to answer. It's a perfectly fine 
choice for everything else, but may or may not be a good choice for this 
specific task.


Steve has a few times in the past that he only tests against Laddie 
himself. If you use anything else, it may or may not work, but if it 
doesn't he doesn't care.


I use dlplus on linux and it always works also on most machines, but I 
have one old laptop where it doesn't. (works for everything else but 
just not for rex setup) The only thing notable about that laptop is that 
it's an old netbook with an atom cpu, so it's slow. Works fine on every 
other machine I have, and dlplus works fine even on that netbook for 
everything but the rex or rex# setup util. So if you have an ms-dos 
machine, that is probably old and slow also, although that should still 
be fine for doing this because of just running dos with no other 
processes at all stealing cpu and a real com port, vs a full multiuser 
linux os with 500 other processes plus using a usb adapter for the com port.


So, all in all, I'd say desklink on dos should work fine, even with the 
rex utils pickiness.


However I think that is all beside the point. Your problem is probably 
not the tpdd server but the initial ascii transfer of the setup program 
itself. There is an initial self-check that verifies the initial 
transfer of the RX#U1.DO program itself to the 100 in the first place.


If you're using a plain comm program to manually send the program 
instead of using a dedicated bootstrapper program that nails down all 
the variables and details just for exactly this reason, then it's very 
easy to get a corrupt transfer. So Steve has a self-check to catch that.


In another post which possibly hasn't posted yet or possibly went to 
spam, I gave a lot of links and details to garanteed ways to do it, 
which uses a dedicated bootstrapper program to send the initial RX#U1.DO 
and either dlplus or laddiealpha for the tpdd server. These are known to 
work. Anything else is "might work". But the bulletproof simple ways 
currently need windows or linux or mac. There is no bootstrapper for 
ms-dos. (Well, the original dos desklink does supposedly have a 
bootstrapper function by creating a file named loader.ba and then you 
can issue a command from the 100 to trigger it, but I've never got that 
to actually work)


So if you still want to use ms-dos on the host side, you'll have to do 
so trial & error to figure out why you're getting a corrupt transfer of 
the initial RX*.DO file. Doing it manually leaves many opportunities for 
leading junk, trailing junk, bad line-endings, and dropped characters 
from gpoing too fast. You'll have to say *exactly* what you did or else 
there is no way to guess what might have gone wrong.


Also if the host is not really dos but is really windows, then try with 
laddiealpha for the tpdd server and tsend.ps1 for the bootstrapper.

See my other post for all the details on that.

--
bkw


On 4/13/22 18:15, Cedric Amand wrote:

Yes,
Bad choice ?
Le 2022-04-14 00:14, John R. Hogerhuis  a écrit :

" TPDD emulator run on MSDOS"

Desklink?
-- John.




--
bkw

Re: [M100] Update & info on REX#

[Brian K. White]

(re-sending from a different account, I sent this earlier but it never 
showed up, also it's long, sorry)



> What's you're saying is that with the serial link still in place
> (for the initial serial transfer), i can simply switch software in
> my modern pc (on the other end of the serial) instead of going into
> the extra trouble to actually make a real TPDD floppy do the job"


Yes. In fact a real tpdd doesn't even work for this.

It's supposed to in theory even though it's so inconvenient to rig up 
that no one would ever actually do it that way, but I had reason to 
actually try it and the rex setup util doesn't work with either a real 
TPDD1 or TPDD2.


Anyway yes you just get the right kind of serial cable, download the 
rex# setup files and a bootstrapper program and a tpdd server program 
into a temp dir, use the bootstrapper to transfer and run the rex# setup 
utiil, start the tpdd server while the setup util is waiting at it's 
first prompt, and the setup util then fetches a file or two from the 
tpdd server while it's running.


After that, in day to day usage you'll use that same serial cable and 
tpdd server all the time for ordinary file transfer both ways, and in 
rexmgr to install option rom images.



Step by step:

Gather some things:

Serial cable
http://tandy.wiki/Model_T_Serial_Cable

rex# setup files
https://bitchin100.com/wiki/index.php?title=REXsharp

(There is some confusing incorrect terminology there. He says "TPDD 
Client" where he means TPDD Server or TPDD Emulator. I will not use the 
exactly backwards words for things so it may get confusing.)


You want the zip file with the latest version & build#
Currently RX#V21_b19.zip
Just download and unzip into a directory.

bootstrapper and tpdd server:
If you're on Windows I suggest "tsend.ps1" for the bootstrapper and 
LaddieAlpha for the tpdd server.

https://github.com/bkw777/tsend
download the .ps1 file into the same dir and issue the commands in the 
readme to give it permission to run.


http://bitchin100.com/wiki/index.php?title=LaddieCon#LaddieAlpha
Similarly, download laddiealpha.exe into the same dir and likewise you 
may have to right click "run as administrator" on it once, or do all of 
this within an administrator cmd window in the first place.


If you're on linux or mac I suggest dlplus for both:
https://github.com/bkw777/dlplus

Now to use the stuff you just gathered

On the REX# doc page
https://bitchin100.com/wiki/index.php?title=REXsharp
Skip down about 2/3 to "REX# Upgrade Utility" to follow along that short 
list of directions to do the next steps.


1.
Press CTRL+BREAK+RESET to cold-reset the 100. (this will erase all ram 
and files)


2. and 3.
Use the bootstrapper to transfer and run the *.do file.
The zip file contains files for several different machines. For a Model 
100 or 102 you want the one with "1" in it's name.
The directions say RX#Ux.DO, so you want RX#U1.DO, except the file in 
the zip is actually lower case so it's "rx#u1.do"

So in the end you run

.\tsend.ps1 -file rx#u1.do
||
rx#u1.do will transfer to the 100 and then start running. It will prompt 
to proceed. Before answering, start LaddieAlpha on the pc.

.\laddiealpha.exe com1 6

(if your serial port is COM5 or something, use that instead of com1. 6 
is the length of filenames and is always 6 for a 100)


4. - 7.
Now proceed responding to the prompts on the 100 and the setup program 
will fetch a couple more files from the tpdd server behind the scenes 
along the way.


After that in ordinary day to day use you will use the same cable and 
tpdd server frequently to move files back & forth, for example to 
install option rom images into the rex# and to copy ordinary programs & 
docs.


--
bkw

On Wed, Apr 13, 2022, 11:00 AM Cedric Amand  wrote:

   Okay,
   What's you're saying is that with the serial link still in place
   (for the initial serial transfer), i can simply switch software in
   my modern pc (on the other end of the serial) instead of going into
   the extra trouble to actually make a real TPDD floppy do the job :)
   Well actually i'll try both,
   I guess it's a good idea to understand the thing fully (i plan to)
   and running the floppy tpdd is part of the hobby :)
   Le 2022-04-13 16:26, Stephen Adolph  a écrit :

   Hi Cedric,
   To transfer XX.DO programs into the M100 without a DOS on
   the laptop, you can use a serial transfer method by connecting
   the M100 via serial to a PC and using a terminal program to send
   the text.
   When you are actually running the upgrade utility, you need to
   replace the PC-terminal end with a PC-TPDD device end (or any
   form of TPDD device).
   I tend to use Laddie Alpha on the PC to emulate a TPDD drive.
   happy to help ;)
   So, get the Rel 2.1 build 19 bundle RX#V21_b19.ZIP
   
   by any means, transfer RX#U1.DO into the laptop and run it.
   follow the instr

Re: [M100] CRC error in 57600 Y

[Brian K. White]

Desklink is fine, and that checksum message is probably about the 
initial ascii transfer of RX#U1.DO . It's easy to get a corrupt copy 
with a manual ascii transfer, and so it has a self-check that it runs 
before doing anything else, to prevent running a corrupt copy.


Expanding on that,

The old dos desklink works perfectly well, but that doesn't neessarily 
ensure it will work with rex/rex# setup, because rex setup doesn't even 
work with a real tpdd1 or tpdd2.


There is a weakness in the tpdd routines in the rex tools, which makes 
"bad choice?" a complicated question to answer. It's a perfectly fine 
choice for everything else, but may or may not be a good choice for this 
specific task.


Steve has a few times in the past that he only tests against Laddie 
himself. If you use anything else, it may or may not work, but if it 
doesn't he doesn't care.


I use dlplus on linux and it always works also on most machines, but I 
have one old laptop where it doesn't. (works for everything else but 
just not for rex setup) The only thing notable about that laptop is that 
it's an old netbook with an atom cpu, so it's slow. Works fine on every 
other machine I have, and dlplus works fine even on that netbook for 
everything but the rex or rex# setup util. So if you have an ms-dos 
machine, that is probably old and slow also, although that should still 
be fine for doing this because of just running dos with no other 
processes at all stealing cpu and a real com port, vs a full multiuser 
linux os with 500 other processes plus using a usb adapter for the com port.


So, all in all, I'd say desklink on dos should work fine, even with the 
rex utils pickiness.


However I think that is all beside the point. Your problem is probably 
not the tpdd server but the initial ascii transfer of the setup program 
itself. There is an initial self-check that verifies the initial 
transfer of the RX#U1.DO program itself to the 100 in the first place.


If you're using a plain comm program to manually send the program 
instead of using a dedicated bootstrapper program that nails down all 
the variables and details just for exactly this reason, then it's very 
easy to get a corrupt transfer. So Steve has a self-check to catch that.


In another post which possibly hasn't posted yet or possibly went to 
spam, I gave a lot of links and details to garanteed ways to do it, 
which uses a dedicated bootstrapper program to send the initial RX#U1.DO 
and either dlplus or laddiealpha for the tpdd server. These are known to 
work. Anything else is "might work". But the bulletproof simple ways 
currently need windows or linux or mac. There is no bootstrapper for 
ms-dos. (Well, the original dos desklink does supposedly have a 
bootstrapper function by creating a file named loader.ba and then you 
can issue a command from the 100 to trigger it, but I've never got that 
to actually work)


So if you still want to use ms-dos on the host side, you'll have to do 
so trial & error to figure out why you're getting a corrupt transfer of 
the initial RX*.DO file. Doing it manually leaves many opportunities for 
leading junk, trailing junk, bad line-endings, and dropped characters 
from gpoing too fast. You'll have to say *exactly* what you did or else 
there is no way to guess what might have gone wrong.


Also if the host is not really dos but is really windows, then try with 
laddiealpha for the tpdd server and tsend.ps1 for the bootstrapper.

See my other post for all the details on that.

--
bkw


On 4/13/22 18:15, Cedric Amand wrote:

Yes,
Bad choice ?
Le 2022-04-14 00:14, John R. Hogerhuis  a écrit :

" TPDD emulator run on MSDOS"

Desklink?
-- John.




--
bkw

Re: [M100] CRC error in 57600 Y

[John R. Hogerhuis]

Not many people are using it so with limited test time it gets left out of
the test matrix.

Looks like the client has some dependency on latitude that Laddiealpha and
dlplus give that desklink and a real TPDD do not.

Maybe max request length?

-- John.

On Wed, Apr 13, 2022, 3:15 PM Cedric Amand  wrote:

> Yes,
> Bad choice ?
>
>
>
> Le 2022-04-14 00:14, John R. Hogerhuis  a écrit :
>
> " TPDD emulator run on MSDOS"
>
> Desklink?
>
> -- John.
>
>
>

[M100] NEC 8201 LCD

[Robert J. Hutchins]

Question: 

My NEC 8201 has a defect, one half column is always lit up. 

I disassembled it, cleaned the strips but no change.

Is this usually a screen memory defect?

 

If anyone has a Model 100 LCD, in good shape I would like to purchase it.

 

Thank you

Robert J. Hutchins

 

 

Re: [M100] CRC error in 57600 Y

[Stephen Adolph]

I never test with that.  Only LaddieAlpha.   would be better to cover every
possible TPDD, but... I don't have that kind of time!


On Wed, Apr 13, 2022 at 6:15 PM Cedric Amand  wrote:

> Yes,
> Bad choice ?
>
>
>
> Le 2022-04-14 00:14, John R. Hogerhuis  a écrit :
>
> " TPDD emulator run on MSDOS"
>
> Desklink?
>
> -- John.
>
>
>

Re: [M100] CRC error in 57600 Y

[Cedric Amand]

Yes, Bad choice ? Le 2022-04-14 00:14, John R. Hogerhuis  a 
écrit : > > > " TPDD emulator run on MSDOS" > > Desklink? > > > > -- John. > > 
> > >

Re: [M100] CRC error in 57600 Y

[John R. Hogerhuis]

" TPDD emulator run on MSDOS"

Desklink?

-- John.

>

[M100] CRC error in 57600 Y

[Cedric Amand]

Hey everyone, Trying to make use of my second hand REX, I've managed to have a 
TPDD emulator run on MSDOS and was able to load a couple of ROMs (mforth & 
MP100 )/ This is REX#2.0 Each loading ends up with the message CRC error in 
57600 Y which is overwritten by an "Ok" which actually gives OkC error in 57600 
Y If I load the same ROM again, it starts. The programs seem to work as far as 
I can see. I'm pretty sure it didn't do that the first time I loaded a ROM, but 
now it does it all the time. TSDOS101 - which was already in my REX# , does not 
make this error message. Only the roms I uploaded. I'm sure I did something 
wrong, and hopefully this is not a FAQ, but any help appreciated :)

Re: [M100] Update & info on REX#

[Cedric Amand]

Hello Brian, First of all, again thanks for taking the time to answer me in so 
much detail. You're right about the confusion about TPDD client and emulators, 
I actually just did the mistake, installing on my msdos computer what is 
clearly an tpdd client, not an emulator. By the way here's my setup :) 
https://ibb.co/ccMR2Gw I have the files from the latest REX"2.1 ZIP file, a 
working serial link obviously I'm planning to use an MSDOS computer (here a 
libretto out of my collection) as with a recent Maxbook pro M1 everything 
becomes more complicated. What you you recommend for bootstrapping from MSDOS 
(6.22) (Alternatively the libretto has Win98 if needed.) Same question for the 
TPDD emulator ? The rest of your instructions are super clear, and I'll try 
that right away, maybe making a summary post myself thanks! Le 2022-04-13 
22:30, Brian K. White  a écrit : > > Yes. In fact a real 
tpdd doesn't even work for this. > > It's supposed to in theory even though 
it's so inconvenient to rig up > that no one would ever actually do it that 
way, but I had reason to > actually try it and the rex setup util doesn't work 
with either a real > TPDD1 or TPDD2. > > Anyway yes you just get the right kind 
of serial cable, download the > rex# setup files and a bootstrapper program and 
a tpdd server program > into a temp dir, use the bootstrapper to transfer and 
run the rex# setup > utiil, start the tpdd server while the setup util is 
waiting at it's > first prompt, and the setup util then fetches a file or two 
from the > tpdd server while it's running. > > After that, in day to day usage 
you'll use that same serial cable and > tpdd server all the time for ordinary 
file transfer both ways, and in > rexmgr to install option rom images. >

Re: [M100] Update & info on REX#

[Brian K. White]

Yes. In fact a real tpdd doesn't even work for this.

It's supposed to in theory even though it's so inconvenient to rig up 
that no one would ever actually do it that way, but I had reason to 
actually try it and the rex setup util doesn't work with either a real 
TPDD1 or TPDD2.


Anyway yes you just get the right kind of serial cable, download the 
rex# setup files and a bootstrapper program and a tpdd server program 
into a temp dir, use the bootstrapper to transfer and run the rex# setup 
utiil, start the tpdd server while the setup util is waiting at it's 
first prompt, and the setup util then fetches a file or two from the 
tpdd server while it's running.


After that, in day to day usage you'll use that same serial cable and 
tpdd server all the time for ordinary file transfer both ways, and in 
rexmgr to install option rom images.



Step by step:

Gather some things:

Serial cable
http://tandy.wiki/Model_T_Serial_Cable

rex# setup files
https://bitchin100.com/wiki/index.php?title=REXsharp

(There is some confusing incorrect terminology there. He says "TPDD 
Client" where he means TPDD Server or TPDD Emulator. I will not use the 
exactly backwards words for things so it may get confusing.)


You want the zip file with the latest version & build#
Currently RX#V21_b19.zip
Just download and unzip into a directory.

bootstrapper and tpdd server:
If you're on Windows I suggest "tsend.ps1" for the bootstrapper and 
LaddieAlpha for the tpdd server.

https://github.com/bkw777/tsend
download the .ps1 file into the same dir and issue the commands in the 
readme to give it permission to run.


http://bitchin100.com/wiki/index.php?title=LaddieCon#LaddieAlpha
Similarly, download laddiealpha.exe into the same dir and likewise you 
may have to right click "run as administrator" on it once, or do all of 
this within an administrator cmd window in the first place.


If you're on linux or mac I suggest dlplus for both:
https://github.com/bkw777/dlplus

Now to use the stuff you just gathered

On the REX# doc page
https://bitchin100.com/wiki/index.php?title=REXsharp
Skip down about 2/3 to "REX# Upgrade Utility" to follow along that short 
list of directions to do the next steps.


1.
Press CTRL+BREAK+RESET to cold-reset the 100. (this will erase all ram 
and files)


2. and 3.
Use the bootstrapper to transfer and run the *.do file.
The zip file contains files for several different machines. For a Model 
100 or 102 you want the one with "1" in it's name.
The directions say RX#Ux.DO, so you want RX#U1.DO, except the file in 
the zip is actually lower case so it's "rx#u1.do"

So in the end you run

.\tsend.ps1 -file rx#u1.do
||
rx#u1.do will transfer to the 100 and then start running. It will prompt 
to proceed. Before answering, start LaddieAlpha on the pc.

.\laddiealpha.exe com1 6

(if your serial port is COM5 or something, use that instead of com1. 6 
is the length of filenames and is always 6 for a 100)


4. - 7.
Now proceed responding to the prompts on the 100 and the setup program 
will fetch a couple more files from the tpdd server behind the scenes 
along the way.


After that in ordinary day to day use you will use the same cable and 
tpdd server frequently to move files back & forth, for example to 
install option rom images into the rex# and to copy ordinary programs & 
docs.


--
bkw

On Wed, Apr 13, 2022, 11:00 AM Cedric Amand  wrote:

   Okay,
   What's you're saying is that with the serial link still in place
   (for the initial serial transfer), i can simply switch software in
   my modern pc (on the other end of the serial) instead of going into
   the extra trouble to actually make a real TPDD floppy do the job :)
   Well actually i'll try both,
   I guess it's a good idea to understand the thing fully (i plan to)
   and running the floppy tpdd is part of the hobby :)
   Le 2022-04-13 16:26, Stephen Adolph  a écrit :

   Hi Cedric,
   To transfer XX.DO programs into the M100 without a DOS on
   the laptop, you can use a serial transfer method by connecting
   the M100 via serial to a PC and using a terminal program to send
   the text.
   When you are actually running the upgrade utility, you need to
   replace the PC-terminal end with a PC-TPDD device end (or any
   form of TPDD device).
   I tend to use Laddie Alpha on the PC to emulate a TPDD drive.
   happy to help ;)
   So, get the Rel 2.1 build 19 bundle RX#V21_b19.ZIP
   
   by any means, transfer RX#U1.DO into the laptop and run it.
   follow the instructions at the REX# wiki.
   
https://bitchin100.com/wiki/index.php?title=REXsharp#REX.23_Upgrade_Utility
   good luck.
   Steve

   On Wed, Apr 13, 2022 at 10:16 AM Cedric Amand
wrote:

   Thanks a lot Stephen;
   This is all probably easier for the original owner, having
   to "onboard" not knowing the history of the device is diffi

Re: [M100] Update & info on REX#

[Cedric Amand]

Okay, What's you're saying is that with the serial link still in place (for the 
initial serial transfer), i can simply switch software in my modern pc (on the 
other end of the serial) instead of going into the extra trouble to actually 
make a real TPDD floppy do the job :) Well actually i'll try both, I guess it's 
a good idea to understand the thing fully (i plan to) and running the floppy 
tpdd is part of the hobby :) Le 2022-04-13 16:26, Stephen Adolph 
 a écrit : > > Hi Cedric, > > > To transfer XX.DO 
programs into the M100 without a DOS on the laptop, you can use a serial 
transfer method by connecting the M100 via serial to a PC and using a terminal 
program to send the text. > > > > When you are actually running the upgrade 
utility, you need to replace the PC-terminal end with a PC-TPDD device end (or 
any form of TPDD device). > > I tend to use Laddie Alpha on the PC to emulate a 
TPDD drive. > > > > happy to help ;) > > > > So, get the Rel 2.1 build 19 
bundle RX#V21_b19.ZIP (https://bitchin100.com/wiki/images/e/ea/RXSV21_b19.ZIP) 
> > > > by any means, transfer RX#U1.DO into the laptop and run it. > > follow 
the instructions at the REX# wiki. > > > > 
https://bitchin100.com/wiki/index.php?title=REXsharp#REX.23_Upgrade_Utility > > 
> > good luck. > > Steve > > > > > On Wed, Apr 13, 2022 at 10:16 AM Cedric 
Amand mailto:ced...@cedric.net)> wrote: > > > > > > Thanks 
a lot Stephen; > > > > > > > > This is all probably easier for the original 
owner, having to "onboard" not knowing the history of the device is difficult. 
> > > > > > > > What was troubling to me is the releases notes that made me 
believe a version I did not have (4.x) solved the Y2K problem, or a rom patch. 
> > > > Given the fact I know for sure my ROM is stock US, I was wondering how 
the hell the Y2K worked as expected > > I understand now that's because 
REX#v2.0 is more recent than those v4.x release notes, thanks for the 
clarification ! > > > > > > the "blank" thing was also a source of concern (bug 
? old ram from the old owner ?) when you don't know, well you don't know :) > > 
> > > > > > One thing that is yet a bit unclear to me is the loading of an 
updated REX software : the manual says to load the basic probram with a serial 
link, but if I get this right, the loading of the rex software image itself can 
ONLY be done with a TPDD device right (not a serial link), am I correct ? > > > 
> I have access to a TPDD floppy, but just want to be sure I got this part 
right. > > > > > > > > > > > > thanks again for taking care of your users and 
customers Stephen, that is much appreciated, > > > > > > > > > > > > > > Le 
2022-04-13 14:32, Stephen Adolph mailto:twospru...@gmail.com)> a écrit : > > > > > > > > > > > Cedric, > > > > 
> > > > > see comments below. cheers Steve > > > > > > > > > > > > On Wed, Apr 
13, 2022 at 8:12 AM Cedric Amand mailto:ced...@cedric.net)> 
wrote: > > > > > > > > > > > > > > Hi everyone, > > > > > > > > > > > > > > > > 
As Stephen already knows, I bought a M100 from someone would did put a REX# in 
it, and i'm trying to get a complete understanding of it. > > > > > > > > > > > 
> > > > > I have many questions but let's start with a few > > > > > > > > I 
see versions of the rex from 4.5 to 4.9, and other versions saying V2.0 or v2.1 
> > > > > > > > Do some numbers refer to hardware ? > > > > > > > > > > > > > > 
> > > > > REX# hardware is different from REX hardware. The software is not 
interchangeable. > > > > > > REX# software is on the REX# page at bitchin100, 
currently 2.1. > > > > > > REX software is the old 4.x stream. > > > > > > > > 
> > > > > > > > > > > > > > If I use the REXMGR program; the thing says REX#2.0 
> > > > > > > > Where do I get that" woftare" info ( 4.5 ? 4.9 ?) i think I 
sasw it once but can't reproduce > > > > > > > > > > > > > > > > > > > > > 
press I. > > > > > > you don't want the old software, it won't work on REX#. > 
> > > > > > > > > > > > > > > > > > > I have a RAM image called "blank". I 
can't load it, it says "error ram sze mismatch" > > > > > > > > > > > > > > > > 
> > > that is because the image is blank, and you have not actually saved a ram 
image to it. > > > > > > > > > > > > > > > > > > > > Again not sure what's the 
history of my M100. Is that a RAM image I shoudl get rid of ? > > > > > > > > > 
> > > > > > > > > > > > it is the default, unsaved, ram image. > > > > > > > > 
> > > > > > > > > > > > It's likely my REX needs an upgrade. I have 
difficulties finding info about how to do that precisely. > > > > > > > > > > > 
> > > > > > > > you have a REX#. > > > > > > The instructions are on the REX# 
page at bitchin100. > > > > > > I try my best to document what you need to do. 
> > > > > > > > > > > > https://bitchin100.com/wiki/index.php?title=REXsharp > 
> > > > > > > > > > > > > > > > > > > > > > > > > > > Final question ; my M100 
display Y2K correctly, and I'm pretty sure ot's NOT running a rex# version with 
the software fix. How could 

Re: [M100] Update & info on REX#

[Stephen Adolph]

Hi Cedric,

To transfer XX.DO programs into the M100 without a DOS on the laptop,
you can use a serial transfer method by connecting the M100 via serial to a
PC and using a terminal program to send the text.

When you are actually running the upgrade utility, you need to replace the
PC-terminal end with a PC-TPDD device end (or any form of TPDD device).
I tend to use Laddie Alpha on the PC to emulate a TPDD drive.

happy to help ;)

So, get the Rel 2.1 build 19 bundle  RX#V21_b19.ZIP


by any means, transfer RX#U1.DO into the laptop and run it.
follow the instructions at the REX# wiki.

https://bitchin100.com/wiki/index.php?title=REXsharp#REX.23_Upgrade_Utility

good luck.
Steve

On Wed, Apr 13, 2022 at 10:16 AM Cedric Amand  wrote:

> Thanks a lot Stephen;
>
> This is all probably easier for the original owner, having to "onboard"
> not knowing the history of the device is difficult.
>
> What was troubling to me is the releases notes that made me believe a
> version I did not have (4.x) solved the Y2K problem, or a rom patch.
> Given the fact I know for sure my ROM is stock US, I was wondering how the
> hell the Y2K worked as expected
> I understand now that's because REX#v2.0 is more recent than those v4.x
> release notes, thanks for the clarification !
>
> the "blank" thing was also a source of concern (bug ? old ram from the old
> owner ?) when you don't know, well you don't know :)
>
> One thing that is yet a bit unclear to me is the loading of an updated REX
> software : the manual says to load the basic probram with a serial link,
> but if I get this right, the loading of the rex software image itself can
> ONLY be done with a TPDD device right (not a serial link), am I correct ?
> I have access to a TPDD floppy, but just want to be sure I got this part
> right.
>
>
> thanks again for taking care of your users and customers Stephen, that is
> much appreciated,
>
>
> Le 2022-04-13 14:32, Stephen Adolph  a écrit :
>
> Cedric,
>
> see comments below.  cheers Steve
>
> On Wed, Apr 13, 2022 at 8:12 AM Cedric Amand  wrote:
>
>> Hi everyone,
>>
>> As Stephen already knows, I bought a M100 from someone would did put a
>> REX# in it, and i'm trying to get a complete understanding of it.
>>
>> I have many questions but let's start with a few
>> I see versions of the rex from 4.5 to 4.9, and other versions saying V2.0
>> or v2.1
>> Do some numbers refer to hardware ?
>>
>
> REX# hardware is different from REX hardware.  The software is not
> interchangeable.
> REX# software is on the REX# page at bitchin100, currently 2.1.
> REX software is the old 4.x stream.
>
>>
>> If I use the REXMGR program; the thing says REX#2.0
>> Where do I get that" woftare" info ( 4.5 ? 4.9 ?) i think I sasw it once
>> but can't reproduce
>>
>>
> press I.
> you don't want the old software, it won't work on REX#.
>
>
>> I have a RAM image called "blank". I can't load it, it says "error ram
>> sze mismatch"
>>
>
> that is because the image is blank, and you have not actually saved a ram
> image to it.
>
>
>> Again not sure what's the history of my M100. Is that a RAM image I
>> shoudl get rid of ?
>>
>>
> it is the default, unsaved, ram image.
>
>
>> It's likely my REX needs an upgrade. I have difficulties finding info
>> about how to do that precisely.
>>
>
> you have a REX#.
> The instructions are on the REX# page at bitchin100.
> I try my best to document what you need to do.
>
>  https://bitchin100.com/wiki/index.php?title=REXsharp
>
>
>>
>> Final question ; my M100 display Y2K correctly, and I'm pretty sure ot's
>> NOT running a rex# version with the software fix. How could I know what the
>> previous owner did to an Y2K working like it should ?
>>
>>
> All REX# software fixes Y2K without needing to patch your main ROM.
>
>
>>
>> thanks !
>>
>

Re: [M100] Update & info on REX#

[Cedric Amand]

Thanks a lot Stephen; This is all probably easier for the original owner, 
having to "onboard" not knowing the history of the device is difficult. What 
was troubling to me is the releases notes that made me believe a version I did 
not have (4.x) solved the Y2K problem, or a rom patch. Given the fact I know 
for sure my ROM is stock US, I was wondering how the hell the Y2K worked as 
expected I understand now that's because REX#v2.0 is more recent than those 
v4.x release notes, thanks for the clarification ! the "blank" thing was also a 
source of concern (bug ? old ram from the old owner ?) when you don't know, 
well you don't know :) One thing that is yet a bit unclear to me is the loading 
of an updated REX software : the manual says to load the basic probram with a 
serial link, but if I get this right, the loading of the rex software image 
itself can ONLY be done with a TPDD device right (not a serial link), am I 
correct ? I have access to a TPDD floppy, but just want to be sure I got this 
part right. thanks again for taking care of your users and customers Stephen, 
that is much appreciated, Le 2022-04-13 14:32, Stephen Adolph 
 a écrit : > > > Cedric, > > > see comments below. cheers 
Steve > > > > On Wed, Apr 13, 2022 at 8:12 AM Cedric Amand mailto:ced...@cedric.net)> wrote: > > > > > > Hi everyone, > > > > > > > > As 
Stephen already knows, I bought a M100 from someone would did put a REX# in it, 
and i'm trying to get a complete understanding of it. > > > > > > > > I have 
many questions but let's start with a few > > > > I see versions of the rex 
from 4.5 to 4.9, and other versions saying V2.0 or v2.1 > > > > Do some numbers 
refer to hardware ? > > > > > > > REX# hardware is different from REX hardware. 
The software is not interchangeable. > > REX# software is on the REX# page at 
bitchin100, currently 2.1. > > REX software is the old 4.x stream. > > > > > > 
> > > > If I use the REXMGR program; the thing says REX#2.0 > > > > Where do I 
get that" woftare" info ( 4.5 ? 4.9 ?) i think I sasw it once but can't 
reproduce > > > > > > > > > press I. > > you don't want the old software, it 
won't work on REX#. > > > > > > > > I have a RAM image called "blank". I can't 
load it, it says "error ram sze mismatch" > > > > > > > that is because the 
image is blank, and you have not actually saved a ram image to it. > > > > > > 
> > Again not sure what's the history of my M100. Is that a RAM image I shoudl 
get rid of ? > > > > > > > > > it is the default, unsaved, ram image. > > > > > 
> > > It's likely my REX needs an upgrade. I have difficulties finding info 
about how to do that precisely. > > > > > > > you have a REX#. > > The 
instructions are on the REX# page at bitchin100. > > I try my best to document 
what you need to do. > > > > 
https://bitchin100.com/wiki/index.php?title=REXsharp > > > > > > > > > > > > 
Final question ; my M100 display Y2K correctly, and I'm pretty sure ot's NOT 
running a rex# version with the software fix. How could I know what the 
previous owner did to an Y2K working like it should ? > > > > > > > > > All 
REX# software fixes Y2K without needing to patch your main ROM. > > > > > > > > 
> > > > thanks ! > > > > > > >

Re: [M100] Update & info on REX#

[Stephen Adolph]

Cedric,

see comments below.  cheers Steve

On Wed, Apr 13, 2022 at 8:12 AM Cedric Amand  wrote:

> Hi everyone,
>
> As Stephen already knows, I bought a M100 from someone would did put a
> REX# in it, and i'm trying to get a complete understanding of it.
>
> I have many questions but let's start with a few
> I see versions of the rex from 4.5 to 4.9, and other versions saying V2.0
> or v2.1
> Do some numbers refer to hardware ?
>

REX# hardware is different from REX hardware.  The software is not
interchangeable.
REX# software is on the REX# page at bitchin100, currently 2.1.
REX software is the old 4.x stream.

>
> If I use the REXMGR program; the thing says REX#2.0
> Where do I get that" woftare" info ( 4.5 ? 4.9 ?) i think I sasw it once
> but can't reproduce
>
>
press I.
you don't want the old software, it won't work on REX#.


> I have a RAM image called "blank". I can't load it, it says "error ram sze
> mismatch"
>

that is because the image is blank, and you have not actually saved a ram
image to it.


> Again not sure what's the history of my M100. Is that a RAM image I shoudl
> get rid of ?
>
>
it is the default, unsaved, ram image.


> It's likely my REX needs an upgrade. I have difficulties finding info
> about how to do that precisely.
>

you have a REX#.
The instructions are on the REX# page at bitchin100.
I try my best to document what you need to do.

 https://bitchin100.com/wiki/index.php?title=REXsharp


> Final question ; my M100 display Y2K correctly, and I'm pretty sure ot's
> NOT running a rex# version with the software fix. How could I know what the
> previous owner did to an Y2K working like it should ?
>
>
All REX# software fixes Y2K without needing to patch your main ROM.


>
> thanks !
>

[M100] Update & info on REX#

[Cedric Amand]

Hi everyone, As Stephen already knows, I bought a M100 from someone would did 
put a REX# in it, and i'm trying to get a complete understanding of it. I have 
many questions but let's start with a few I see versions of the rex from 4.5 to 
4.9, and other versions saying V2.0 or v2.1 Do some numbers refer to hardware ? 
If I use the REXMGR program; the thing says REX#2.0 Where do I get that" 
woftare" info ( 4.5 ? 4.9 ?) i think I sasw it once but can't reproduce I have 
a RAM image called "blank". I can't load it, it says "error ram sze mismatch" 
Again not sure what's the history of my M100. Is that a RAM image I shoudl get 
rid of ? It's likely my REX needs an upgrade. I have difficulties finding info 
about how to do that precisely. Final question ; my M100 display Y2K correctly, 
and I'm pretty sure ot's NOT running a rex# version with the software fix. How 
could I know what the previous owner did to an Y2K working like it should ? 
thanks !