Great to hear! Comments: 1) to run the backup utility, RXCMGR must be disabled. CNTL-X. think I stated this at the wiki? 2) And yes, I've dropped some features that either added little value or added greatly to the testing burden. Date and sort were on the chopping block. bad call?
Steve On Wed, Jun 24, 2020 at 6:51 PM Jim Anderson <jim.ander...@kpu.ca> wrote: > Got mine today! Loaded in some OPTROMS and one of my old RAM backup > images from my REX Classic, and they work great! (Not sure if you want to > test that yourself before updating the wiki, Stephen.) Only hitch (mostly > cosmetic) is that there is still a REXMGR entry on the menu screen left > over from the saved image, which REXMGR would normally clean up and replace > but now it just adds RXCMGR. At least both of those entries will launch > RXCMGR for you, and if it bothers you (like it does me) you can use a DOS > or just KILL "REXMGR" from BASIC to get rid of it. > > Also loaded the current CP/M disk image and played around a bit with > that. I'm very pleased and I can't wait until the MVT100 is available. > > I ran into one problem so far, and I also have a question: > > > Problem: I can't run a backup using RXCUTL - I am prompted for what to > back up (I tried both, same results), then Backup or Restore (I tried both, > same results), then 19200 or 76800_LB (I only tried 19200). RXCUTL > proceeds to load the machine language code and then gets to this (and yes, > LaddieAlpha is running before I reach this point): > > Loading at: 61000 <....(didn't type out all the dots)....> 62356 > > Params=REXCPM,Backup,19200 > > Can't run!! > Press space bar for MENU > > > Question: I notice that OPTROM and RAM images in RXCMGR no longer show a > modification date/time stamp and therefore hitting 's' to change the > directory sort order doesn't do anything. Was this an > intentionally-dropped feature? > > > > > > > > jim >