Re: [M100] REX question

[Stephen Adolph]

Teeny?

On Thursday, July 8, 2021, Tom Wilson  wrote:

> Right, you don’t need TS-DOS, but you need *something* with the ability
> to load files from a TPDD compatible device. If you have an actual TPDD,
> you can use the bootstrap function, otherwise you have to find a program
> that can be used to bootstrap the necessary files.
>
> That was the challenge - finding a program that could do the job on the
> T200.
>
> On Thu, Jul 8, 2021 at 4:05 PM Josh Malone  wrote:
>
>> I've been informed that you don't actually need TS-DOS loaded to flash
>> a REX -- just something to load the flash utility. Teeny will do.
>>
>> On Thu, Jul 8, 2021 at 6:38 PM Tom Wilson  wrote:
>> >
>> > Yes, I have flashed a Rex Classic to work on a 200. It’s a PITA, mostly
>> to get the DOS boot loader on so I can get the TS-DOS ROM loaded. The
>> problem being that with only 24K of RAM per bank, it’s hard to find a BASIC
>> loader small enough to do the job.
>> >
>> > If you need me to, I can dig through my archive and find the program I
>> used.
>> >
>> > On Thu, Jul 8, 2021 at 1:18 PM Josh Malone 
>> wrote:
>> >>
>> >> REX classic and REX# come in 2 "flavors": 100/102 and 200
>> >>
>> >> The hardware is physically identical, as is the CPLD program. However,
>> >> the FLASH load is different, owing to the different memory
>> >> configurations/maps on the 2 systems. You can "reprogram" a 100/102
>> >> into a 200 and vice-versa by following the initial programming steps
>> >> and doing a "wipe and reload". At least, you can on the REX classic.
>> >> I've never done it on REX# so check the wiki pages.
>> >>
>> >> -Josh
>> >>
>> >> On Thu, Jul 8, 2021 at 2:55 PM Bill Miranda 
>> wrote:
>> >> >
>> >> > Is REX module interchangeable between model 100 and model 102?
>> >> >
>> >> > Thanks!
>> >> >
>> >> > Bill
>> >
>> > --
>> > Tom Wilson
>> > wilso...@gmail.com
>> > (619)940-6311
>> >
>>
> --
> Tom Wilson
> wilso...@gmail.com
> (619)940-6311
>
>

Re: [M100] REX question

[Tom Wilson]

Right, you don’t need TS-DOS, but you need *something* with the ability to
load files from a TPDD compatible device. If you have an actual TPDD, you
can use the bootstrap function, otherwise you have to find a program that
can be used to bootstrap the necessary files.

That was the challenge - finding a program that could do the job on the
T200.

On Thu, Jul 8, 2021 at 4:05 PM Josh Malone  wrote:

> I've been informed that you don't actually need TS-DOS loaded to flash
> a REX -- just something to load the flash utility. Teeny will do.
>
> On Thu, Jul 8, 2021 at 6:38 PM Tom Wilson  wrote:
> >
> > Yes, I have flashed a Rex Classic to work on a 200. It’s a PITA, mostly
> to get the DOS boot loader on so I can get the TS-DOS ROM loaded. The
> problem being that with only 24K of RAM per bank, it’s hard to find a BASIC
> loader small enough to do the job.
> >
> > If you need me to, I can dig through my archive and find the program I
> used.
> >
> > On Thu, Jul 8, 2021 at 1:18 PM Josh Malone 
> wrote:
> >>
> >> REX classic and REX# come in 2 "flavors": 100/102 and 200
> >>
> >> The hardware is physically identical, as is the CPLD program. However,
> >> the FLASH load is different, owing to the different memory
> >> configurations/maps on the 2 systems. You can "reprogram" a 100/102
> >> into a 200 and vice-versa by following the initial programming steps
> >> and doing a "wipe and reload". At least, you can on the REX classic.
> >> I've never done it on REX# so check the wiki pages.
> >>
> >> -Josh
> >>
> >> On Thu, Jul 8, 2021 at 2:55 PM Bill Miranda 
> wrote:
> >> >
> >> > Is REX module interchangeable between model 100 and model 102?
> >> >
> >> > Thanks!
> >> >
> >> > Bill
> >
> > --
> > Tom Wilson
> > wilso...@gmail.com
> > (619)940-6311
> >
>
-- 
Tom Wilson
wilso...@gmail.com
(619)940-6311

Re: [M100] REX question

[Josh Malone]

I've been informed that you don't actually need TS-DOS loaded to flash
a REX -- just something to load the flash utility. Teeny will do.

On Thu, Jul 8, 2021 at 6:38 PM Tom Wilson  wrote:
>
> Yes, I have flashed a Rex Classic to work on a 200. It’s a PITA, mostly to 
> get the DOS boot loader on so I can get the TS-DOS ROM loaded. The problem 
> being that with only 24K of RAM per bank, it’s hard to find a BASIC loader 
> small enough to do the job.
>
> If you need me to, I can dig through my archive and find the program I used.
>
> On Thu, Jul 8, 2021 at 1:18 PM Josh Malone  wrote:
>>
>> REX classic and REX# come in 2 "flavors": 100/102 and 200
>>
>> The hardware is physically identical, as is the CPLD program. However,
>> the FLASH load is different, owing to the different memory
>> configurations/maps on the 2 systems. You can "reprogram" a 100/102
>> into a 200 and vice-versa by following the initial programming steps
>> and doing a "wipe and reload". At least, you can on the REX classic.
>> I've never done it on REX# so check the wiki pages.
>>
>> -Josh
>>
>> On Thu, Jul 8, 2021 at 2:55 PM Bill Miranda  wrote:
>> >
>> > Is REX module interchangeable between model 100 and model 102?
>> >
>> > Thanks!
>> >
>> > Bill
>
> --
> Tom Wilson
> wilso...@gmail.com
> (619)940-6311
>

Re: [M100] REX question

[Tom Wilson]

Yes, I have flashed a Rex Classic to work on a 200. It’s a PITA, mostly to
get the DOS boot loader on so I can get the TS-DOS ROM loaded. The problem
being that with only 24K of RAM per bank, it’s hard to find a BASIC loader
small enough to do the job.

If you need me to, I can dig through my archive and find the program I
used.

On Thu, Jul 8, 2021 at 1:18 PM Josh Malone  wrote:

> REX classic and REX# come in 2 "flavors": 100/102 and 200
>
> The hardware is physically identical, as is the CPLD program. However,
> the FLASH load is different, owing to the different memory
> configurations/maps on the 2 systems. You can "reprogram" a 100/102
> into a 200 and vice-versa by following the initial programming steps
> and doing a "wipe and reload". At least, you can on the REX classic.
> I've never done it on REX# so check the wiki pages.
>
> -Josh
>
> On Thu, Jul 8, 2021 at 2:55 PM Bill Miranda 
> wrote:
> >
> > Is REX module interchangeable between model 100 and model 102?
> >
> > Thanks!
> >
> > Bill
>
-- 
Tom Wilson
wilso...@gmail.com
(619)940-6311

Re: [M100] REX question

[Bill Miranda]

Thank you Josh and Brian

On Thu, Jul 8, 2021 at 2:25 PM Brian Brindle  wrote:

> Hi Bill,
>
> Yes, you can use the same REX in a model 100 or 102.
>
> If they are mod100/102's have the same amount of memory you will have no
> issues with stored RAM Images, but if they are different you will get a
> memory size mismatch when attempting to load them. Easy to fix using the
> file browse feature and creating a new Image though.
>
> Brian
>
>
> On Thu, Jul 8, 2021 at 2:55 PM Bill Miranda 
> wrote:
>
>> Is REX module interchangeable between model 100 and model 102?
>>
>> Thanks!
>>
>> Bill
>>
>

Re: [M100] REX question

[Brian Brindle]

Hi Bill,

Yes, you can use the same REX in a model 100 or 102.

If they are mod100/102's have the same amount of memory you will have no
issues with stored RAM Images, but if they are different you will get a
memory size mismatch when attempting to load them. Easy to fix using the
file browse feature and creating a new Image though.

Brian


On Thu, Jul 8, 2021 at 2:55 PM Bill Miranda  wrote:

> Is REX module interchangeable between model 100 and model 102?
>
> Thanks!
>
> Bill
>

Re: [M100] REX question

[Stephen Adolph]

Bill,
REX# and it's predecessor REX can be installed in either M100 or T102.
Meaning you buy an M100 version, you can use it in T102 also, and move it
between the 2 if you want.
I don't make REX anymore.  I have switched to the new design REX#.   If you
really want the old version others will make it for you, or you can roll
your own too.
cheers
Steve


On Thu, Jul 8, 2021 at 2:55 PM Bill Miranda  wrote:

> Is REX module interchangeable between model 100 and model 102?
>
> Thanks!
>
> Bill
>

Re: [M100] REX question

[Josh Malone]

REX classic and REX# come in 2 "flavors": 100/102 and 200

The hardware is physically identical, as is the CPLD program. However,
the FLASH load is different, owing to the different memory
configurations/maps on the 2 systems. You can "reprogram" a 100/102
into a 200 and vice-versa by following the initial programming steps
and doing a "wipe and reload". At least, you can on the REX classic.
I've never done it on REX# so check the wiki pages.

-Josh

On Thu, Jul 8, 2021 at 2:55 PM Bill Miranda  wrote:
>
> Is REX module interchangeable between model 100 and model 102?
>
> Thanks!
>
> Bill

[M100] REX question

[Bill Miranda]

Is REX module interchangeable between model 100 and model 102?

Thanks!

Bill

Re: [M100] REX Question: Flash Wear Leveling

[Stephen Adolph]

Hi Peter,
Wear leveling isn't really implemented properly.  As you add to the rex
directory it fills up. And that induces flatter use.
The datasheet for am29F800 suggests 10 write cycles before wear out.  I
reasoned that was a tremendous amount of rex image writes...
Hope that helps.
Steve


On Tuesday, December 17, 2019, Peter Noeth  wrote:

>   I have been developing a number of programs lately on my T102 w/REX,
> backing up frequently, and was wondering if the REX control software was
> doing any "wear leveling" of the Flash sectors. Having worked with Flash
> memory in my previous job (Point of Sale Credit Card machines) I know that
> it is an important process, due the limited write cycles per cell that NAND
> flash have.
>
> Regards,
>
> Peter
>

[M100] REX Question: Flash Wear Leveling

[Peter Noeth]

  I have been developing a number of programs lately on my T102 w/REX,
backing up frequently, and was wondering if the REX control software was
doing any "wear leveling" of the Flash sectors. Having worked with Flash
memory in my previous job (Point of Sale Credit Card machines) I know that
it is an important process, due the limited write cycles per cell that NAND
flash have.

Regards,

Peter

Re: [M100] REX Question

[Stephen Adolph]

That's a good point.  I needed that message for debug.  I guess it could be
removed.

On Friday, September 27, 2019, Peter Noeth  wrote:

> Steve,
>
>   Thanks for the clarification.
>
>   That was my other thought, but since I had never seen a similar message
> in the TRS-DOS days of "Floppy Disk Only Storage" on the Model 1 or 4P
> where one could fill the directory table easily too, I didn't expect the
> REX would notify the user ether, as long as there was no "Unrecoverable"
> error.
>
>   I will add that bit of info to my REX notes.
>
> Peter
>
> 
>
>
> >On Friday, September 27, 2019, Steven Adolf  > wrote:
>
> >There is a finite length of the directory in flash.  Old directory entries
> >are not erased ..they are marked as old.
> >When you hit the last table entry, the table gets rebuilt to reflect the
> >current entries only, erasing the old entries.
>
> >Steve
>
>
> >On Friday, September 27, 2019, Peter Noeth  wrote:
>
> >   I was doing some fine tuning on a BASIC program, and when I used the
> > System Menu command key "CTRL-B" to refresh the backup image of RAM, I
> got
> > the message "Rebuilding Directories" (or some such, I didn't write it
> down)
> > after the RAM image was updated.
> >
> >   Is this message due to "wear leveling" of the REX FLASH memory?
> >
> >   REX seems to be still working.
> >
> > Regards,
> >
> > Peter
> >
>
>  
>
>

Re: [M100] REX Question

[Peter Noeth]

Steve,

  Thanks for the clarification.

  That was my other thought, but since I had never seen a similar message
in the TRS-DOS days of "Floppy Disk Only Storage" on the Model 1 or 4P
where one could fill the directory table easily too, I didn't expect the
REX would notify the user ether, as long as there was no "Unrecoverable"
error.

  I will add that bit of info to my REX notes.

Peter




>On Friday, September 27, 2019, Steven Adolf http://.com>> wrote:

>There is a finite length of the directory in flash.  Old directory entries
>are not erased ..they are marked as old.
>When you hit the last table entry, the table gets rebuilt to reflect the
>current entries only, erasing the old entries.

>Steve


>On Friday, September 27, 2019, Peter Noeth  wrote:

>   I was doing some fine tuning on a BASIC program, and when I used the
> System Menu command key "CTRL-B" to refresh the backup image of RAM, I got
> the message "Rebuilding Directories" (or some such, I didn't write it
down)
> after the RAM image was updated.
>
>   Is this message due to "wear leveling" of the REX FLASH memory?
>
>   REX seems to be still working.
>
> Regards,
>
> Peter
>

 

Re: [M100] REX Question

[Stephen Adolph]

There is a finite length of the directory in flash.  Old directory entries
are not erased ..they are marked as old.
When you hit the last table entry, the table gets rebuilt to reflect the
current entries only, erasing the old entries.

Steve


On Friday, September 27, 2019, Peter Noeth  wrote:

>   I was doing some fine tuning on a BASIC program, and when I used the
> System Menu command key "CTRL-B" to refresh the backup image of RAM, I got
> the message "Rebuilding Directories" (or some such, I didn't write it down)
> after the RAM image was updated.
>
>   Is this message due to "wear leveling" of the REX FLASH memory?
>
>   REX seems to be still working.
>
> Regards,
>
> Peter
>

[M100] REX Question

[Peter Noeth]

  I was doing some fine tuning on a BASIC program, and when I used the
System Menu command key "CTRL-B" to refresh the backup image of RAM, I got
the message "Rebuilding Directories" (or some such, I didn't write it down)
after the RAM image was updated.

  Is this message due to "wear leveling" of the REX FLASH memory?

  REX seems to be still working.

Regards,

Peter

[M100] REX question

[Peter Noeth]

  In the REX Manager (looking at the RAM group for example), the [s] key is
supposed to toggle the sort order. This seems to alternate between "first
to last" or "last to first", with the active image (the starred one)
always first (top left display position). The displayed list is not sorted
alphabetically, but instead seems to be somewhat in the order that the
images were created.

  Is this correct?  It seems to me that unless the list is alpha sorted
(A-Z or Z-A) this function is not really very useful, especially if there
are enough images to need to use the arrow keys to scroll the displayed
list.

  I am just trying to understand the operation to complete my "Quick
Reference" documentation.

Regards,

Peter

Re: [M100] REX: Question about REXMGR

[Stephen Adolph]

It is an indicator that lets you know how REX views the main rom.
M = standard main rom detected
P = REX is providing main rom out of the primary reserved block
S = REX is providing main rom out of the secondary reserved block


On Tue, Mar 26, 2019 at 1:24 AM Peter Noeth  wrote:

>   I was just reading the REX Manager User Guide (
> http://bitchin100.com/wiki/index.php?title=REX_Manager_User_Guide) and
> found that the screen shot seems quite out of date (v4.5). Although the
> operation described seemed to match the current version (v4.9), it does not
> explain what the "reverse video" 'M' on the first line just to the right of
> the version number means on v4.9.
>
>   I found nothing about this in the built in "Help" [F1] either.
>
>   I am making additions to my "Quick Reference" card on REX, so was
> wondering what the "M" means.
>
> Regards,
>
> Peter
>

[M100] REX: Question about REXMGR

[Peter Noeth]

  I was just reading the REX Manager User Guide (
http://bitchin100.com/wiki/index.php?title=REX_Manager_User_Guide) and
found that the screen shot seems quite out of date (v4.5). Although the
operation described seemed to match the current version (v4.9), it does not
explain what the "reverse video" 'M' on the first line just to the right of
the version number means on v4.9.

  I found nothing about this in the built in "Help" [F1] either.

  I am making additions to my "Quick Reference" card on REX, so was
wondering what the "M" means.

Regards,

Peter

Re: [M100] REX question

[David Laffineuse]

Reloading the TSDOS ROM twice in a row seems to fix the issue.  Is that the 
correct workaround?  Also is there a way to update REX to a later code version? 

Sent from my iPhone

> On May 10, 2018, at 11:01 PM, Stephen Adolph  wrote:
> 
> Yah it is a bugfix fixed in a later release however that good code is mixed 
> with subsequent bad code.  tsdos is displacing rexmgr as lowest . Ba file.
> 
>> On Thursday, May 10, 2018, John R. Hogerhuis  wrote:
>> Sounds like a bug in rexmgr. 
>> 
>> Might depend on which two roms you are switching between. 
>> 
>> You may want to run the redo the install CALL  manually when you 
>> switch the ROMs but I think you’re not supposed to have to do that.  
>> 
>> Maybe Steve can weigh in on how REXMGR is supposed to do this. 
>> 
>> — John. 

Re: [M100] REX question

[Stephen Adolph]

Yah it is a bugfix fixed in a later release however that good code is mixed
with subsequent bad code.  tsdos is displacing rexmgr as lowest . Ba file.

On Thursday, May 10, 2018, John R. Hogerhuis  wrote:

> Sounds like a bug in rexmgr.
>
> Might depend on which two roms you are switching between.
>
> You may want to run the redo the install CALL  manually when you
> switch the ROMs but I think you’re not supposed to have to do that.
>
> Maybe Steve can weigh in on how REXMGR is supposed to do this.
>
> — John.
>

Re: [M100] REX question

[John R. Hogerhuis]

Sounds like a bug in rexmgr.

Might depend on which two roms you are switching between.

You may want to run the redo the install CALL  manually when you
switch the ROMs but I think you’re not supposed to have to do that.

Maybe Steve can weigh in on how REXMGR is supposed to do this.

— John.

Re: [M100] REX question

[David Laffineuse]

In this example I am only switching ROM images, not RAM images.  Rexmanager 
returns version 4.9, checksum 6e83, model Rex, firmware 6(1).  I think that the 
problem is due to the fact that, when i get back to the ts-dos rom, it doesn’t 
put the trigger file back in the menu right away, causing some offset in RAM 
locations.  If i then go back to rexmanager and reselect ts-dos rom a second 
time, the ts-dos trigger file reappears which solves the offset issue and i can 
run the correct program by selecting it in the menu.  

Sent from my iPhone

> On May 10, 2018, at 10:10 PM, Josh Malone  wrote:
> 
> Are you changing ROMs or RAM images? Clearly something is messed up in your 
> memory file system. I'd say it's time for a cold-start.
> 
> Just to be sure which rexmgr version you're running go into rexmgr and press 
> the I key and see what the checksum is.
> 
>> On Thu, May 10, 2018, 9:50 PM David Laffineuse  
>> wrote:
>> So I switch between different roms and then come back to the menu.   From 
>> the menu, i position my cursor on anthem.ba but it runs froger.ba.  If i 
>> position myself on froger.ba and press return, it runs shootr.ba, etc.
>> 
>> Sent from my iPhone
>> 
>>> On May 10, 2018, at 9:42 PM, John R. Hogerhuis  wrote:
>>> 
>>> 
 On Thu, May 10, 2018 at 6:28 PM David Laffineuse  
 wrote:
 So I have been playing with REX a bit.  However when I switch between 
 different ROMs, it seems to confuse the M100 a bit.  Indeed, after 
 changing ROM, when I select a program in RAM, it runs another.  How can I 
 fix that?
 
 Sent from my iPhone
>>> 
>>> Can you give some more detail? If it runs a program from a different rom 
>>> than you’re switched to, something is very wrong.  That’s basically 
>>> impossible unless rexmgr or the Rex is malfunctioning. 
>>> 
>>> Maybe I don’t know what you mean. 
>>> 
>>> Obviously the trigger file left by a given ROM is only appropriate to run 
>>> when the proper rom is installed. 
>>> 
>>> Rexmgr should work though. If you switch roms you might need to call 63012 
>>> or whatever is recommended for that rom/ laptop if you don’t have a trigger 
>>> file.  

Re: [M100] REX question

[Josh Malone]

Are you changing ROMs or RAM images? Clearly something is messed up in your
memory file system. I'd say it's time for a cold-start.

Just to be sure which rexmgr version you're running go into rexmgr and
press the I key and see what the checksum is.

On Thu, May 10, 2018, 9:50 PM David Laffineuse 
wrote:

> So I switch between different roms and then come back to the menu.   From
> the menu, i position my cursor on anthem.ba but it runs froger.ba.  If i
> position myself on froger.ba and press return, it runs shootr.ba, etc.
>
> Sent from my iPhone
>
> On May 10, 2018, at 9:42 PM, John R. Hogerhuis  wrote:
>
>
> On Thu, May 10, 2018 at 6:28 PM David Laffineuse 
> wrote:
>
>> So I have been playing with REX a bit.  However when I switch between
>> different ROMs, it seems to confuse the M100 a bit.  Indeed, after changing
>> ROM, when I select a program in RAM, it runs another.  How can I fix that?
>>
>> Sent from my iPhone
>
> Can you give some more detail? If it runs a program from a different rom
> than you’re switched to, something is very wrong.  That’s basically
> impossible unless rexmgr or the Rex is malfunctioning.
>
> Maybe I don’t know what you mean.
>
> Obviously the trigger file left by a given ROM is only appropriate to run
> when the proper rom is installed.
>
> Rexmgr should work though. If you switch roms you might need to call 63012
> or whatever is recommended for that rom/ laptop if you don’t have a trigger
> file.
>
>

Re: [M100] REX question

[David Laffineuse]

So I switch between different roms and then come back to the menu.   From the 
menu, i position my cursor on anthem.ba but it runs froger.ba.  If i position 
myself on froger.ba and press return, it runs shootr.ba, etc.

Sent from my iPhone

> On May 10, 2018, at 9:42 PM, John R. Hogerhuis  wrote:
> 
> 
>> On Thu, May 10, 2018 at 6:28 PM David Laffineuse  
>> wrote:
>> So I have been playing with REX a bit.  However when I switch between 
>> different ROMs, it seems to confuse the M100 a bit.  Indeed, after changing 
>> ROM, when I select a program in RAM, it runs another.  How can I fix that?
>> 
>> Sent from my iPhone
> 
> Can you give some more detail? If it runs a program from a different rom than 
> you’re switched to, something is very wrong.  That’s basically impossible 
> unless rexmgr or the Rex is malfunctioning. 
> 
> Maybe I don’t know what you mean. 
> 
> Obviously the trigger file left by a given ROM is only appropriate to run 
> when the proper rom is installed. 
> 
> Rexmgr should work though. If you switch roms you might need to call 63012 or 
> whatever is recommended for that rom/ laptop if you don’t have a trigger 
> file.  

Re: [M100] REX question

[John R. Hogerhuis]

On Thu, May 10, 2018 at 6:28 PM David Laffineuse 
wrote:

> So I have been playing with REX a bit.  However when I switch between
> different ROMs, it seems to confuse the M100 a bit.  Indeed, after changing
> ROM, when I select a program in RAM, it runs another.  How can I fix that?
>
> Sent from my iPhone

Can you give some more detail? If it runs a program from a different rom
than you’re switched to, something is very wrong.  That’s basically
impossible unless rexmgr or the Rex is malfunctioning.

Maybe I don’t know what you mean.

Obviously the trigger file left by a given ROM is only appropriate to run
when the proper rom is installed.

Rexmgr should work though. If you switch roms you might need to call 63012
or whatever is recommended for that rom/ laptop if you don’t have a trigger
file.

[M100] REX question

[David Laffineuse]

So I have been playing with REX a bit.  However when I switch between different 
ROMs, it seems to confuse the M100 a bit.  Indeed, after changing ROM, when I 
select a program in RAM, it runs another.  How can I fix that?

Sent from my iPhone