Thanks, Steve.
Running “rx#t2.do” failed at “Test write ROM data to flash”.
I used “rx#u2.do” to update to RX#_22 and it succeeded with no error.
However, when I returned to the main T200 menu, it was strangely garbled
(“Microsoft” got replaced by “2ha oft”). REXMGR did show up in the options,
but trying to save the current state said that memory was write protected!
All the slots were taken up with “🮕🮕🮕🮕🮕” dated “:⯆┴ 31,2063 63:63”
Re-running “rx#t2.do” again failed at the same place:
Initializing laptop
OK! Check ready
OK! Test sector register
OK! Erase flash, test RY/BY
OK! Checking FF
OK! Write ROM data to flash
FAILED! Test write ROM data to flash
Do I need to buy another T200 REX#? Maybe I should get two, just in case.
—b9
On Tue, Aug 6, 2024 at 5:13 AM Stephen Adolph <[email protected]> wrote:
> Hard to say what exactly is corrupt; could be the REX# software or it
> could be the directory.
> I'd suggest first installing a new REX# software image while leaving the
> directory intact. "upgrade"
> If that doesn't work, you need to rebuild it. "test"
>
>
> https://bitchin100.com/wiki/index.php?title=REXsharp#REX.23_Manager_Software
>
> I suggest using the newest software version.
>
> In general I have found it very challenging to make REX# completely
> bulletproof. It is hard to anticipate every possible failure mode.
>
> cheers,
> Steve
>
>
> On Tue, Aug 6, 2024 at 6:26 AM B 9 <[email protected]> wrote:
>
>> I've been happily using a REX# Option ROM in my Tandy 200 for a while now
>> but today it gave me some weird message about rebuilding the ROM directory.
>> The progress bar was frozen at about 80%. I had to do a full reset (holding
>> SHIFT+Break+Reset) and and now my REX# doesn't respond. Running `CALL
>> 61167,2` locks up the screen and I have to press the reset button to do a
>> soft reset. I tried the REX# in my spare Tandy 200 and failed in the same
>> way.
>>
>> Any ideas for how I might revive my REX#?
>>
>> —b9
>>
>>
>>
>>
