I was under the impression that using F7 should leave the active Optrom in place. Maybe my memory is failing me.
1. Started with standard menu (no ROM) loaded and no other programs installed. 2. Performed a call 63012 which loads REXMGR. Confirmed that the * is next to UR2100. 3. Performed another call 63012 which loads UR2. (I would not do this step, here) 4. Reopened REXMGR and performed deinstall (F7) and allow machine to reset by pressing a key. 5. Upon restart, the machine is back to the standard menu with no REXMGR or UR2 entries. (yes, all triggers are swept out) 6. Performed call 63012 which reloads REXMGR and not UR2. ( I thought UR2 would be left in place, maybe I am wrong) On Mon, Nov 29, 2021 at 10:39 AM Patrick McDougal <[email protected]> wrote: > Thanks again for the quick response. After your guidance, I performed the > following… > > 1. Started with standard menu (no ROM) loaded and no other programs > installed. > 2. Performed a call 63012 which loads REXMGR. Confirmed that the * is > next to UR2100. > 3. Performed another call 63012 which loads UR2. > 4. Reopened REXMGR and performed deinstall (F7) and allow machine to > reset by pressing a key. > 5. Upon restart, the machine is back to the standard menu with no REXMGR > or UR2 entries. > 6. Performed call 63012 which reloads REXMGR and not UR2. > > It appears that the de-install and reset removes REXMGR and the active > optrom and the call after reset is reloading the REXMGR hooks. Is that the > expected behavior? > > FYI, I have tried the same process using SuperROM as well with the same > results. > > Patrick > > > > On Nov 29, 2021, at 9:15 AM, Stephen Adolph <[email protected]> wrote: > > thats because you are powering off - which resets REX option rom selection > back to "REXMGR" > just use RESET, leaving power on. > This leaves the "active optrom" visible, while removing REXMGR. If you > power off, the option rom selection is reverted to REXMGR. > > Steve > > On Mon, Nov 29, 2021 at 9:08 AM Patrick McDougal <[email protected]> > wrote: > >> I think I may be misunderstanding a step. >> >> I have restarted the machine and then used the call 63012 command. This >> results in the REXMGR appearing in the menu. I then use the call command >> again and UR is now on the menu screen. When I open REXMGR and select f7, >> I received the turn off or press and key to reset. When I turn it off and >> turn in back on again (Thanks Roy and Moss ;)), the REXMGR and UR are now >> absent. A call command from BASIC reloads the REXMGR. >> >> I have also attempted to CLEAR0,MAXRAM commands but have not noticed any >> change. I failed to mentioned previously that after starting View80, I >> will often get a value of 252 under the View80 title. If I understand the >> documentation correctly that it the number of columns selected. >> >> Patrick >> >> >> >> >> >> On Nov 29, 2021, at 8:44 AM, Stephen Adolph <[email protected]> wrote: >> >> OK, good progress. >> I think the next step is to not use CNTL-X but use F7 from REXMGR. >> That will completely remove REXMGR altogether. >> >> you could also try >> CLEAR0,MAXRAM >> >> before you start UR-2 >> >> >> On Mon, Nov 29, 2021 at 8:42 AM Patrick McDougal <[email protected]> >> wrote: >> >>> It is REX#2.1. I performed the following… >>> >>> 1. Removed the batteries and turned off the memory power. >>> 2. Restarted the machine and then performed a call 63012 >>> 3. REXMGR appears in the menu and then CTRL-X and removed the hooks. >>> 4. Opened BASIC, call 63012. >>> 5. Entered UR and selected View80. >>> >>> On the initial try, I received a continuous tone that required the reset >>> button. On the second try, I selected View80 and noticed “Can’t” displayed >>> below the menu. On the 3rd try, I received a “Change HIMEM?” and typed Y >>> and then attempted to enter the edit portion of T-Word and it locked up. >>> >>> Through my testing, I have also had the Telcom prompt pop up below the >>> UR menu when turning on View80. Oddly, I have never seen the option to >>> select the screen width that is mentioned in the UR documentation. >>> >>> I have reloaded the UR bx file in case of an error when transferring. >>> For what its worth, the machine has been very stable with no issues using >>> UR except when attempting to active View80. >>> >>> Any additional recommendations would be much appreciated. >>> >>> Thanks, >>> >>> Patrick >>> >>> On Nov 29, 2021, at 8:12 AM, Stephen Adolph <[email protected]> >>> wrote: >>> >>> I seem to recall fixing this. Can you confirm you are on release 2.1 >>> firmware for REX#? it may well be a conflict. As Ben said using CNTL-X >>> before you start the ROM using Call 63012 (don't start the rom from REX >>> Manager) gives you a REX# free try. >>> >>> >>> On Mon, Nov 29, 2021 at 3:15 AM Ben Wiley Sittler <[email protected]> >>> wrote: >>> >>>> Have you tried removing the REX# hooks before activating 80 column >>>> mode? I believe they are not compatible >>>> >>>> On Sun, Nov 28, 2021, 16:50 Patrick McDougal <[email protected]> >>>> wrote: >>>> >>>>> To the group, >>>>> >>>>> As you may recall, I recently bought a used M100 off of Ebay. I >>>>> cleaned it up and upgrade the RAM to 32k and installed a Rex# (Thank you >>>>> Steve!). I successfully connected in to a Windows 10 machine using Laddie >>>>> Alpha and loaded the UR2100 ROM. I have been trying to use the View 80 >>>>> function which seems to install in high memory when I select it. When I >>>>> attempt to use T-Word, the blank text editing screen appears with a >>>>> smaller >>>>> cursor in the left upper corner and then locks up. This requires a cold >>>>> reboot of the machine (removing the batteries and turning off the memory >>>>> backup power) to restore any function. I can then reload the RexMgr and >>>>> start again. This error does not occur if I do not load the View80 >>>>> component of Ultimate ROM. >>>>> >>>>> Has anyone else experienced this issue or have an idea about >>>>> troubleshooting? >>>>> >>>>> Thanks, >>>>> >>>>> Patrick >>>> >>>> >>> >> >
