So I was feeling adventurous and after testing the main ROM management feature of REX on an M100 that was apart (using a temporary jumper) I thought I'd go ahead and implement it on my T200 since I only have one of those and wouldn't be moving the REX to other machines.
In the process I came up with an idea for making a plug to allow disconnection of TP1/TP2 so the REX wouldn't be physically tethered to the machine, which worked out beautifully (I should have taken a picture - I'll describe that another time if anybody cares)... So tonight I got adventurous and thought I'd try out what happens if you enable a 'bad' secondary image and need to recover from that (I just enabled the secondary image without uploading anything into it). The info at http://bitchin100.com/wiki/index.php?title=Main_ROM_Management_Feature says: "NOTE - IF YOU PUT A BAD IMAGE IN PRIMARY AND USE IT, REX WILL BE NON FUNCTIONAL. YOU WILL HAVE TO PHYSICALLY REINSTALL YOUR MAIN ROM TO RECOVER. NOTE - IF YOU PUT A BAD IMAGE IN SECONDARY AND SELECT IT, REX WILL BE NON FUNCTIONAL. YOU WILL HAVE TO COLD BOOT YOUR LAPTOP TO RECOVER." And then a little further down... "You can freely update your Secondary ROM as you wish to implement and try out other ROM images. So long as the Primary ROM remains intact you can always recover your REX from a nasty main ROM installation in the Secondary ROM." To me this implies that recovery from a bad secondary ROM image is fairly straightforward. Unfortunately, I'm now stuck. If I pull the batteries for a few seconds REX goes back to the primary image and the machine will boot up fine, but as soon as I try call 61167,2 to re-enable REX it says "REX system installed in bank 1" and then locks up (presumably because it now remembers I wanted to use the secondary image). I have to pull the batteries again before it will boot again. Is there a trick to forcing it to go back to the primary image? jim
