Sure send the RAM image. I'll check it out in Virtual T (the prototype that I have that supports REX# and REXCPM- hopefully that will get released at some point. As is par for the course with me, I introduced a bug or 2 into the prototype but heck it was my first ever C programming).
On Mon, Dec 21, 2020 at 3:38 AM Jim Anderson <jim.ander...@kpu.ca> wrote: > > -----Original Message----- > > > > Active block is always first, does seem to fit what is happening? I just > > checked on my end and it seems to be working. Active block first, then > > sorted by date/time. > > Yes, it shows the active block first as always, it's the rest of the > entries which aren't sorting. When I applied the 43 update each image had > a bogus date/time (something like 63/12/15, I don't remember exactly) but > I've cycled through each of them and they all now have a date/time stamp > from some time in the last two days, however the sort order remains exactly > the same sequence as always regardless of the date/time attached to each > image. > > If it might be helpful for you to look at, I could make a backup of the > REX area of my REXCPM and send you a link to the backup file to try it on > your system. > > > BTW, I thought I'd mention that after rebuilding and reloading the other > machine with the REX classic, at some point after filling up the OPTROMs > and RAM images I noticed that the SYSTEM# entry has re-appeared in the > OPTROM image list. When I hit B it says it refers to block 0. I recall > now that the # indicates an image which is active in another bank (on my > T200 REX) and I remember you saying you had added bank support (but I > thought that was only in the new REX# release?)... anyhow, maybe this will > help shed an additional clue as to what happened and/or why SYSTEM# is > showing up in the menu now. > > > > > > > > jim > >
