Hi Peter , Setting aside why it failed for the moment,
If all you did was hit the reset button then REX manager would not start up on CALL63012. I suggest that you 1) power cycle + cold restart in one move. Or cold reset, power cycle, cold reset. This will reset REX. 2) then call 63012..rex mgr should start up. Not saying rex software doe not have issues .. just that a reset does nothing to rex. It is normal that rex presents an option rom to the t102 after cold reset. If an option rom was configured before the reset it will remain configured after reset. Only a power cycle resets REX. There is no reset signal on the option to socket. Was Rom2 configured to be present on REX at the ti e? Why do you think it needs to be reflashed? Btw what load is installed? Checksum = ? Do you have the latest? You can certainly do that it you want to but normally the only reason to reflash rex is when the directory is corrupted. Not sure this is that... Prior to the incident, what option rom was rex configured to set? Debugging a failure on a system that is not in ones hands and does not repeat, is challenging. Thx Steve On Sunday, August 25, 2019, Peter Noeth <[email protected]> wrote: > I was doing some BASIC programming on my T102 using the Text editor. I > put it down to attend to the laundry, and came back 15 or 20 minutes later > to continue on with the T102, where I found that typing on the computer > produced garbage characters on the screen and then the computer locked up. > REX was enabled at the time. > > I pressed the Reset button and the computer restarted like doing a cold > boot (date back to 1900). Going into BASIC and typing 'CALL 63012' did not > re-initialize REX, but instead initialized "Cleuseau", which is the Option > ROM image I had loaded into REX. > > I believe there is a problem in REX when using the TEXT program (at > least while editing a BASIC program) and the computer's 'Power Down Timer' > triggers. > > Had anyone else experience this? > > Fortunately, all my files (except the one I was editing) are backed up > on my desktop computer, but it looks like the REX may need to be > re-flashed. I don't have the equipment to re-flash it (nor do I want to buy > yet another programming interface to do so), so will probably send it to > Josh Malone (I bought it from him at Tandy Assembly) for checkout. > > The point here is that the REX firmware needs to be debugged for these > conditions, and hopefully fixed. > > Regards, > > Peter >
