I see you understand "S" not "O".  I've checked it out on my end and it was
working.  If the date/time stamps are the same, sort order won't change.

Anyhow, I will check it again.
steve

On Sun, Dec 20, 2020 at 4:25 PM Stephen Adolph <[email protected]> wrote:

> re REXCPM  - S changes the sort order!
>
> Re REXclassic: sounds like your directory is corrupted at first glance.  I
> would do a full rebuild, not just the software.
> Let me know if you cannot find the tools you need.
> cheers, steve
>
>
>
> On Sun, Dec 20, 2020 at 3:05 PM Jim Anderson <[email protected]> wrote:
>
>> I recently applied the 260 update to two of my REX classics and the 43
>> update to my REXCPM.  Two questions:
>>
>> REXCPM - I see a date and time stamp on the images now, awesome!
>> However, for me the images are still being sorted by their original order
>> (I think it's the order in which the images were created) even though I've
>> cycled through all of them and they all now have an valid date/time stamp
>> (they started with garbage date/time data after the update, of course).
>> Press O to change sort order only reverses the original sort order back and
>> forth.  Is there a trick to it?  Do I have to offload, delete, and re-load
>> them?
>>
>> REX classic - I was using my T102 this morning and hit Ctrl-O from the
>> main screen to change option ROM images.  I noticed the last image in the
>> list was something I hadn't seen before, named SYSTEM#, and out of
>> curiosity I selected it.  Well, you know what they say about curiosity and
>> cats... my T102 locked up solid and the Reset button wouldn't recover it.
>> Ctrl-Break-Reset will do a cold reset, but as soon as I CALL 63012 it locks
>> up solid again.  Powering off and on doesn't help, removing and
>> reinstalling the REX doesn't help.  I guess I'll have to try doing the 260
>> update again (and if that doesn't help, the full 260 reinstall...) but I
>> wanted to find out what SYSTEM# is and why it locked REX up tight.
>> (Perhaps it's not meant to show in the list?)
>>
>>
>>
>>
>>
>>
>>
>>         jim
>>
>>

Reply via email to