REX Release 4.9: Difference between revisions

From Bitchin100 DocGarden
Jump to navigationJump to search
 
(63 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Supported Models ==
== Supported Models ==
*  Model 100 and Tandy 102 with either REX or REX2
*  Model 100 and Tandy 102 with either REX or REX2
*  Tandy 200 with REX.
*  Tandy 200 with REX
*  NEC PC-8201 and NEC PC-8300 with REX3
*  NEC PC-8201 with REX3
 
 
 
=== M100 note ===
 
  In Europe and UK, and probably elsewhere, there are newer versions of M100 that have different boards.
  Model numbers are 26-3801B and 26-3802B.
  It isn't clear if REX works in those systems; until I can verify, assume REX does not work in anything
  but a USA/Canada equivalent M100 (meaning it has a Modem, and the custom ROM pinout).
  ***UPDATE*** confirmed that UK M100s need to use a US main ROM image.  Options include getting a
  new main ROM burned using a known good binary image, or wiring your computer up using Main ROM Management feature.


== New Features ==
== New Features ==
*  QUAD support - has been removed from release 4.9 as of revision 254.
*  Y2K Fix - REX now automatically fixes the year displayed in MENU.
*  Y2K Fix - REX now automatically fixes the year displayed in MENU.
*  PC-8201 support (including TAB key in addition to SHIFT-F5 to bank-switch, like T200)
*  PC-8201 support (including TAB key in addition to SHIFT-F5 to bank-switch, like T200)
Line 10: Line 24:
*  Quick Menu features - see description below
*  Quick Menu features - see description below
*  REX status indicator in MENU - the active Option ROM (for each bank) is indicated in the display
*  REX status indicator in MENU - the active Option ROM (for each bank) is indicated in the display


== REX Functionality Overview ==
== REX Functionality Overview ==
Line 23: Line 36:
*  <CNTL-B>: Back up RAM - REX will prompt the user to confirm, and if confirmed will copy RAM to the active RAM image, performing a backup.
*  <CNTL-B>: Back up RAM - REX will prompt the user to confirm, and if confirmed will copy RAM to the active RAM image, performing a backup.
*  <CNTL-R>: Restore RAM - REX will prompt the user to confirm, and if confirmed will copy the active RAM image to RAM, performing a restore.
*  <CNTL-R>: Restore RAM - REX will prompt the user to confirm, and if confirmed will copy the active RAM image to RAM, performing a restore.
*  <CNTL-H>: Hooks removal - REX will prompt the user to confirm, and if confirmed will remove all hooks relating to REXMGR from the laptop operating system, effectively disabling REX.  REXMGR remains in the MENU, so REX can be easily reinstalled.  Also, the Active Option ROM is accessible using the usual ROM start procedures.  This feature is useful when it is desired to run the Option ROM without REX active.
*  <CNTL-X>: Hooks removal - REX will prompt the user to confirm, and if confirmed will remove all hooks relating to REXMGR from the laptop operating system, effectively disabling REX.  REXMGR remains in the MENU, so REX can be easily reinstalled.  Also, the Active Option ROM is accessible using the usual ROM start procedures.  This feature is useful when it is desired to run the Option ROM without REX active.


'''Multi-Bank Operation'''
'''Multi-Bank Operation'''


Unlike Model 100 and Tandy 102, multi-bank machines (PC-8201, PC-8300, T200) have an advantage in that the user has 3 distinct memory spaces to work with.  Prior to release 4.9, all of those banks would have the same Option ROM active.  In Release 4.9, multi-bank machines now may access unique active RAM images and active OPTION ROM images on a per-bank basis.  For example, TS-DOS, UR-2 and R2C can be assigned to each bank, and each bank can have an associated RAM image.  This means the user can simply TAB between spaces and quickly use different Option ROMs, and each RAM space can be backed up separately.
Unlike Model 100 and Tandy 102, multi-bank machines PC-8201, T200 have an advantage in that the user has up to 3 distinct memory spaces to work with.  Prior to release 4.9, all of those banks would have the same Option ROM active.  In Release 4.9, multi-bank machines now may access unique active RAM images and active OPTION ROM images on a per-bank basis.  For example, TS-DOS, UR-2 and R2C can be assigned to each bank, and each bank can have an associated RAM image.  This means the user can simply TAB between spaces and quickly use different Option ROMs, and each RAM space can be backed up separately.


In REX Manager, images are marked with '*' next to the name when that image is ACTIVE in the current BANK.  Images that are ACTIVE in OTHER BANKS are marked with '#'.  Pressing B or b in REX Manager will indicate the BANK associated with an image, as well as the block number the image occupies in REX flash memory.
In REX Manager, images are marked with '*' next to the name when that image is ACTIVE in the current BANK.  Images that are ACTIVE in OTHER BANKS are marked with '#'.  Pressing B or b in REX Manager will indicate the BANK associated with an image, as well as the block number the image occupies in REX flash memory.


REX Release 4.9 supports the M100 4-bank 128kByte RAM Module, but only the first 3 RAM banks are supported.


'''Y2K Fix'''
'''Y2K Fix'''
Line 37: Line 49:
Prior to Release 4.9, users wanting a fix for Y2K would have needed to make use of Main ROM Replacement via REX.  This requires a hardware modification.  Now, a Y2K patch is automatically applied when in MENU.
Prior to Release 4.9, users wanting a fix for Y2K would have needed to make use of Main ROM Replacement via REX.  This requires a hardware modification.  Now, a Y2K patch is automatically applied when in MENU.


== Upgrading REX from a Release 4.8 or Earlier ==
== Rebuilding REX ==


If you are the owner of a REX which is operating with software of Release 4.8 vintage or earlier, then it is not possible to upgrade to Release 4.9 <B> while maintaining the contents of the FLASH and the image NAME DIRECTORY. </B>  Upgrading this vintage or REX requires the removal of any backed up RAM images to a TPDD device for storage and for later re-loading into REX.  The FLASH memory in REX is completely wiped when upgrading from R4.8 or earlier.
  In order to use revision 254, users must do a complete rebuild of their REX.


'''Please see the section below for specific software release bundles for upgrading from R4.8 or prior.'''
All rebuilds to REX are `clean sweep` upgrades, meaning <B> you must save off all important stored RAM images to a TPDD device.</B>  After the upgrade, you can re-load your important RAM and OPTROM images into REX.  The FLASH memory in REX is completely wiped.
 
'''Please see the section below for specific software release bundles.'''


'''What you need'''
'''What you need'''
*  for M100 or T102: RF149.CO, RXF149.BR, TSD100.BX
*  for M100 or T102: RF149.CO, RXF149.BR, TSD100.BX
*  for T200: RF249.CO, RXF249.BR, TSD200.BX
*  for T200: RF249.CO, RXF249.BR, TSD200.BX
*  for PC-8201 or PC-8300: NOTHING!  It is new in R4.9!
*  for PC-8201: RFN49.CO, RXFN49.BR, TSDNEC.BX
*  your favorite TPDD device connected to the laptop
*  your favorite TPDD device connected to the laptop


Place the files in the root directory of your TPDD device for loading.
Place the files in the root directory of your TPDD device for loading.
These instructions are meant to cover the procedure to install release 4.9 software for the FIRST TIME.  All previous releases of REX have used addresses 04000h to 0FFFh as the REX directory in block 0 of the flash.  Release 4.9 changes that - the new directory location is 6000h-7FFFh.


In order to make a "clean sweep" and make sure that no issues with older software, for the initial installation of 4.9 we take the approach of wiping the old directory, and all the flash contents (from block 6-31; the user space) and initialize things to default.
In order to make a "clean sweep" and make sure that no issues with older software, for the initial installation of 4.9 we take the approach of wiping the old directory, and all the flash contents (from block 6-31; the user space) and initialize things to default.
Line 68: Line 80:


'''Step 2'''
'''Step 2'''
  Load the upgrader tool:  Load into RAM the RFx49.CO file using the TPDD device.   
  Load the rebuild tool:  Load into RAM the RFx49.CO file using the TPDD device.   
  You will need to CLEAR0,55000 to run the program.  But, don't run it yet.
  You will need to CLEAR0,55000 to run the program.  But, don't run it yet.


Line 87: Line 99:
  CALL63012 (M100/T102)
  CALL63012 (M100/T102)
  CALL61167,2 (T200)
  CALL61167,2 (T200)
  EXEC62394 (PC-8201/8300)
  EXEC62394 (PC-8201)


Voila!  You should see REXMGR in the MENU, and you should see the fancy new OPTROM indicator in the top right corner.  You are now running release 4.9!!!!
Voila!  You should see REXMGR in the MENU, and you should see the fancy new OPTROM indicator in the top right corner.  You are now running release 4.9!!!!


== REX Release 4.9 Upgrade Package (for upgrades from Release 4.8 or older) ==
== REX Release 4.9 Upgrade Packages ==
 
The following files may be downloaded and used to upgrade your REX from an older release to R4.9 revision 134.


  Revision 134 makes only minor changes to 117. Minor improvement to bank switching in T200.
The following files may be downloaded and used to upgrade your REX from an older release to R4.9 revision 260.  Because the directory structure is new in release 4.9, users must do a full rebuild when on 4.8 or older. Remember a full rebuild will completely wipe and rebuild your REX so save important data to a TPDD device!


<table border="1">
These are the checksums for revision 260:
<tr><td>Status</td><td>Release</td><td>Model</td><td>Description</td><td>File</td><td>Revision</td><td>Submitter / Date</td></tr>
<tr><td>Beta</td><td>4.9</td><td>M100/T102</td><td>REX Release 4.9 Upgrade Package for R4.8 and prior</td><td>[[Media:R49_M100T102_134_upgrade48.zip|R49_M100T102_134_upgrade48]]</td><td>134</td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 08:03, 25 January 2015 (PST)</td></tr>
<tr><td>Beta</td><td>4.9</td><td>T200</td><td>REX Release 4.9 Upgrade Package for R4.8 and prior</td><td>[[Media:R49_T200_134_upgrade48.zip|R49_T200_134_upgrade48]]</td><td>134</td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 08:03, 25 January 2015 (PST)</td></tr>
</table>


  M100 = DF79
  T200 = 18BA
  NEC = 3B3E


 
If your checksum (by pressing I) is not this, then you should upgrade.
The following files may be downloaded and used to upgrade your REX from an older release to R4.9 revision 117.
 




<table border="1">
<table border="1">
<tr><td>Status</td><td>Release</td><td>Model</td><td>Description</td><td>File</td><td>Revision</td><td>Submitter / Date</td></tr>
<tr><td>Status</td><td>Release</td><td>Model</td><td>Description</td><td>File</td><td>Revision</td></tr>
<tr><td>Beta</td><td>4.9</td><td>M100/T102</td><td>REX Release 4.9 Upgrade Package for R4.8 and prior</td><td>[[Media:R49_M100T102_117_upgrade48.zip|R49_M100T102_117_upgrade48]]</td><td>117</td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 20:02, 11 January 2015 (PST)</td></tr>
<tr><td>Beta</td><td>4.9</td><td>T200</td><td>REX Release 4.9 Upgrade Package for R4.8 and prior</td><td>[[Media:R49_T200_117_upgrade48.zip|R49_T200_117_upgrade48]]</td><td>117</td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 20:02, 11 January 2015 (PST)</td></tr>
</table>


== Upgrading REX from Release 4.9 to a newer revision of Release 4.9==
<tr><td>Beta</td><td>4.9</td><td>M100/T102</td><td>REX Release 4.9 Rebuild Package</td><td>[[Media:R49_M100T102_260_rebuild.zip|R49_M100T102_260_rebuild]]</td><td>260</td></tr>


If you are the owner of a REX which is operating with software of Release 4.9 vintage, then the upgrade is a simpler process. Upgrading this version of REX simply involves over-writing the first 24k of the first block of the REX FLASH with a newer revision.  The directories remain, as do all the stored images.
<tr><td>Beta</td><td>4.9</td><td>T200</td><td>REX Release 4.9 Rebuild Package</td>
<td>[[Media:R49_T200_260_rebuild.zip|R49_T200_260_rebuild]]</td><td>260</td></tr>


'''Please see the section below for specific software release bundles for upgrading from R4.9.'''
<tr><td>Beta</td><td>4.9</td><td>NEC</td><td>REX Release 4.9 Rebuild Package</td>
 
<td>[[Media:R49_NEC_260_rebuild.zip|R49_NEC_260_rebuild]]</td><td>260</td></tr>
'''What you need'''
*  for M100 or T102: RU149.CO, REX149.BR
*  for T200: RU249.CO, REX249.BR
*  for PC-8201 or PC-8300: RUN49.CO, REXN49.BR
*  your favorite TPDD device connected to the laptop
 
 
These instructions are meant to cover the procedure to install a newer release 4.9.  Don't do this if you are currently running R4.8 or earlier!
 
Place the files in the root directory of your TPDD device for loading.
 
'''Step 1'''
Load the upgrader tool:  Load into RAM the RUx49.CO file using the TPDD device.
You will need to CLEAR0,55000 to run the program.  But, don't run it yet.
 
'''Step 2'''
Remove REX software from the laptop.  This is an easy step - just go into REXMGR and press F7
(or SHIFT-F4 in PC-8201/8300)to DEINstall REX software.  You should find yourself at MENU with
RUx49.CO in the directory of the laptop.
 
'''Step 3'''
Issue the BASIC command CLEAR0,55000.  Exit BASIC and run RUx49.CO from Menu.
RUx49.CO will do the necessary steps of erasing blocks, loading the REX software,
and copying it to backup block 1.
 
'''Step 4'''
Once RUx49.CO completes, you should be able to start REXMGR.  Power cycle the laptop.
Cold restart the machine to clean out any funny memory stuff.  Enter BASIC and type either
CALL63012 (M100/T102)
CALL61167,2 (T200)
EXEC62394 (PC-8201/8300)
 
Voila!  You have upgraded your REX!!!!
 
== REX Release 4.9 Upgrade Package (for upgrades from Release 4.9) ==
 
The following files may be downloaded and used to upgrade your REX from an older release to R4.9 revision 134.
 
  Revision 134 makes only minor changes to 117. Minor improvement to bank switching in T200.
 
<table border="1">
<tr><td>Status</td><td>Release</td><td>Model</td><td>Description</td><td>File</td><td>Revision</td><td>Submitter / Date</td></tr>
<tr><td>Beta</td><td>4.9</td><td>M100/T102</td><td>REX Release 4.9 Upgrade Package for R4.9</td><td>[[Media:R49_M100T102_134_upgrade49.zip|R49_M100T102_134_upgrade49]]</td><td>134</td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 07:57, 25 January 2015 (PST)</td></tr>
<tr><td>Beta</td><td>4.9</td><td>T200</td><td>REX Release 4.9 Upgrade Package for R4.9</td><td>[[Media:R49_T200_134_upgrade49.zip|R49_T200_134_upgrade49]]</td><td>134</td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 07:57, 25 January 2015 (PST)</td></tr>
<tr><td>Beta</td><td>4.9</td><td>PC-8201 or PC-8300</td><td>REX Release 4.9 Upgrade Package for R4.9</td><td>[[Media:R49_NEC_134_upgrade49.zip|R49_NEC_134_upgrade49]]</td><td>134</td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 07:57, 25 January 2015 (PST)</td></tr>
</table>
</table>




The following files may be downloaded and used to upgrade your REX from an earlier R4.9 to revision 260.
These files are update only; directory and flash contents should stay the same after the update to REXROM.


The following files may be downloaded and used to upgrade your REX from an older release to R4.9 revision 117.


<table border="1">
<table border="1">
<tr><td>Status</td><td>Release</td><td>Model</td><td>Description</td><td>File</td><td>Revision</td><td>Submitter / Date</td></tr>
<tr><td>Status</td><td>Release</td><td>Model</td><td>Description</td><td>File</td><td>Revision</td></tr>
<tr><td>Beta</td><td>4.9</td><td>M100/T102</td><td>REX Release 4.9 Upgrade Package for R4.9</td><td>[[Media:R49_M100T102_117_upgrade49.zip|R49_M100T102_117_upgrade49]]</td><td>117</td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 20:09, 11 January 2015 (PST)</td></tr>
<tr><td>Beta</td><td>4.9</td><td>T200</td><td>REX Release 4.9 Upgrade Package for R4.9</td><td>[[Media:R49_T200_117_upgrade49.zip|R49_T200_117_upgrade49]]</td><td>117</td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 20:09, 11 January 2015 (PST)</td></tr>
<tr><td>Beta</td><td>4.9</td><td>PC-8201 or PC-8300</td><td>REX Release 4.9 Upgrade Package for R4.9</td><td>[[Media:R49_NEC_117_upgrade49.zip|R49_NEC_117_upgrade49]]</td><td>117</td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 20:09, 11 January 2015 (PST)</td></tr>
</table>


== REX Release 4.9 Source Code ==
<tr><td>Beta</td><td>4.9</td><td>M100/T102</td><td>REX Release 4.9 Update Package</td><td>[[Media:R49_M100T102_260_update.zip|R49_M100T102_260_update]]</td><td>260</td></tr>


The following files are ZIP files containing the source code for REX Release 4.9 by Revision.
<tr><td>Beta</td><td>4.9</td><td>T200</td><td>REX Release 4.9 Update Package</td>
<td>[[Media:R49_T200_260_update.zip|R49_T200_260_update]]</td><td>260</td></tr>


<table border="1">
<tr><td>Beta</td><td>4.9</td><td>NEC</td><td>REX Release 4.9 Update Package</td>
<tr><td>Status</td><td>Source Files</td><td>Revision</td><td>Submitter / Date</td></tr>
<td>[[Media:R49_NEC_260_update.zip|R49_NEC_260_update]]</td><td>260</td></tr>
<tr><td>Beta</td><td>[[Media:REX_source_117.zip|REX source code Revision 117]]</td><td>117</td><td> [[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 20:14, 11 January 2015 (PST)</td></tr>
</table>
</table>


== About Main ROM Management  ==
== About Main ROM Management  ==
Please see the main REX wiki page for a description of this feature - how to prepare a ROM image, how to modify the hardware, and how to load REX with images.
Please see the main REX wiki page for a description of this feature - how to prepare a ROM image, how to modify the hardware, and how to load REX with images.
== Rel. 4.9 Trouble Reports==
<table border="1">
<tr><td>Status</td><td>Model(s)</td><td>Description</td><td>Impact</td><td>Work Around</td><td>User/ Date</td></tr>
<tr><td>resolved</td><td>M102</td><td>a problem occured upgrading from 4.8 to 4.9.  unknown fault at this time.--- problem found. TSDOS was corrupted.</td><td> Medium</td><td> resolved - user reloaded TS-DOS using REXMGR. </td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 12:30, 1 February 2015 (PST)</td></tr>
<tr><td>resolved in rev 119</td><td>T200</td><td>there was a minor issue in revision 117 relating to F1 BANK switching.  Using F1 rather than TAB effectively uninstalled REXMGR. </td><td> Low </td><td> Restart REXMGR by power cycling and CALL61167,2. This is resolved in the next revision.  </td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 06:23, 24 January 2015 (PST)</td></tr>
<tr><td>believed resolved in 134</td><td>T200/PC-8201/PC-8300</td><td>periodically, REX software is not removed/reinstalled on bank switch.  This disables REX in the new bank.</td><td> Low </td><td> Bank switch back to original bank and run REXMGR to reinstall. </td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 08:02, 25 January 2015 (PST)</td></tr>
<tr><td>investigation</td><td>PC-8300</td><td>An early PC-8300 install was defective for unknown reasons.</td><td> High </td><td> None at this time. </td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 06:23, 24 January 2015 (PST)</td></tr>
</table>
== Enhancement Requests ==
<table border="1">
<tr><td>Status</td><td>Description</td><td>Requester / Date</td></tr>
<tr><td>under consideration</td><td> is there some way to modify all the bank settings within REXMGR without having to exit, change bank, and re-enter REXMGR?  Cool idea, hmmm.</td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 15:56, 1 February 2015 (PST)</td></tr>
<tr><td>under consideration</td><td>Support for so called Paired Switching, where a RAM image is swapped and an OPTROM image is switched in the same step. </td><td>[[User:Sadolph|Sadolph]] 05:17, 15 August 2009 (PDT)</td></tr>
<tr><td>unlikely</td><td>Support for TPDD-2, for drive 1: (0: is supported).</td><td>[[User:Sadolph|Sadolph]] 04:36, 19 April 2009 (PDT)</td></tr>
<tr><td>in planning</td><td>Flash disk for file storage</td><td>[[User:Sadolph|Sadolph]] ([[User talk:Sadolph|talk]]) 05:09, 12 January 2015 (PST)</td></tr>
</table>
nb: to put a username+datestamp just type 4 tildes <nowiki>~~~~</nowiki>

Latest revision as of 16:19, 6 January 2023


Supported Models

  • Model 100 and Tandy 102 with either REX or REX2
  • Tandy 200 with REX
  • NEC PC-8201 with REX3


M100 note

 In Europe and UK, and probably elsewhere, there are newer versions of M100 that have different boards.
 Model numbers are 26-3801B and 26-3802B.
 It isn't clear if REX works in those systems; until I can verify, assume REX does not work in anything
 but a USA/Canada equivalent M100 (meaning it has a Modem, and the custom ROM pinout).
 ***UPDATE*** confirmed that UK M100s need to use a US main ROM image.  Options include getting a 
 new main ROM burned using a known good binary image, or wiring your computer up using Main ROM Management feature.

New Features

  • QUAD support - has been removed from release 4.9 as of revision 254.
  • Y2K Fix - REX now automatically fixes the year displayed in MENU.
  • PC-8201 support (including TAB key in addition to SHIFT-F5 to bank-switch, like T200)
  • Multi-bank support - see description below
  • Quick Menu features - see description below
  • REX status indicator in MENU - the active Option ROM (for each bank) is indicated in the display

REX Functionality Overview

REX remains similar to release 4.8, but several major new capabilities have been added. The differences are outlined below.

Quick Menu Features

For commonly used functions, now some shortcut keys are available in MENU. This avoids the need to start REXMGR to perform simple operations like ROM switching and backing up your RAM.

Summary of commands:

  • <CNTL-O>: Switch Option ROM - REX will display available Option ROMs, and the user can use arrow keys to move the cursor to the desired selection. <ENTER> to activate the new selection and start that ROM. <ESC> to exit. The Active Option ROM is indicated with a *.
  • <CNTL-B>: Back up RAM - REX will prompt the user to confirm, and if confirmed will copy RAM to the active RAM image, performing a backup.
  • <CNTL-R>: Restore RAM - REX will prompt the user to confirm, and if confirmed will copy the active RAM image to RAM, performing a restore.
  • <CNTL-X>: Hooks removal - REX will prompt the user to confirm, and if confirmed will remove all hooks relating to REXMGR from the laptop operating system, effectively disabling REX. REXMGR remains in the MENU, so REX can be easily reinstalled. Also, the Active Option ROM is accessible using the usual ROM start procedures. This feature is useful when it is desired to run the Option ROM without REX active.

Multi-Bank Operation

Unlike Model 100 and Tandy 102, multi-bank machines PC-8201, T200 have an advantage in that the user has up to 3 distinct memory spaces to work with. Prior to release 4.9, all of those banks would have the same Option ROM active. In Release 4.9, multi-bank machines now may access unique active RAM images and active OPTION ROM images on a per-bank basis. For example, TS-DOS, UR-2 and R2C can be assigned to each bank, and each bank can have an associated RAM image. This means the user can simply TAB between spaces and quickly use different Option ROMs, and each RAM space can be backed up separately.

In REX Manager, images are marked with '*' next to the name when that image is ACTIVE in the current BANK. Images that are ACTIVE in OTHER BANKS are marked with '#'. Pressing B or b in REX Manager will indicate the BANK associated with an image, as well as the block number the image occupies in REX flash memory.


Y2K Fix

Prior to Release 4.9, users wanting a fix for Y2K would have needed to make use of Main ROM Replacement via REX. This requires a hardware modification. Now, a Y2K patch is automatically applied when in MENU.

Rebuilding REX

 In order to use revision 254, users must do a complete rebuild of their REX.

All rebuilds to REX are `clean sweep` upgrades, meaning you must save off all important stored RAM images to a TPDD device. After the upgrade, you can re-load your important RAM and OPTROM images into REX. The FLASH memory in REX is completely wiped.

Please see the section below for specific software release bundles.

What you need

  • for M100 or T102: RF149.CO, RXF149.BR, TSD100.BX
  • for T200: RF249.CO, RXF249.BR, TSD200.BX
  • for PC-8201: RFN49.CO, RXFN49.BR, TSDNEC.BX
  • your favorite TPDD device connected to the laptop

Place the files in the root directory of your TPDD device for loading.

In order to make a "clean sweep" and make sure that no issues with older software, for the initial installation of 4.9 we take the approach of wiping the old directory, and all the flash contents (from block 6-31; the user space) and initialize things to default.

A note about Rom Replacement - if you are using this feature then you know that your main OS roms are stored in block 2-5. Those blocks are not erased, and they stay in place and operational the whole time. My three test machines are all running with REX based main roms.


Step 1

So then, the first thing to do is for you to 'Save' all your existing RAM and OPTROM images 
(the ones that you both want to keep and are not already stored on a PC somewhere) out of REX 
and onto your favorite TPDD device.  Please go through your saved images, decide what you want 
to save and use again, and get them out of REX.  After we install R4.9, all those images will 
be wiped.  You will have to reload anything you need.


Step 2

Load the rebuild tool:  Load into RAM the RFx49.CO file using the TPDD device.  
You will need to CLEAR0,55000 to run the program.  But, don't run it yet.

Step 3

Remove REX software from the laptop.   This is an easy step - just go into REXMGR and press F7 
(or SHIFT-F4 in PC-8201/8300)to DEINstall REX software.  
You should find yourself at MENU with RFx49.CO in the directory of the laptop.

Step 4

Issue the BASIC command CLEAR0,55000.  Exit BASIC and run RFx49.CO from Menu.  
RFx49.CO will do the necessary steps of erasing blocks, loading the REX software, 
copying it to backup block 1, and then loading TS-DOS into block 8.

Step 5

Once RFx49.CO completes, you should be able to start REXMGR.  Power cycle the laptop.  
Cold restart the machine to clean out any funny memory stuff.  Enter BASIC and type either

CALL63012 (M100/T102)
CALL61167,2 (T200)
EXEC62394 (PC-8201)

Voila! You should see REXMGR in the MENU, and you should see the fancy new OPTROM indicator in the top right corner. You are now running release 4.9!!!!

REX Release 4.9 Upgrade Packages

The following files may be downloaded and used to upgrade your REX from an older release to R4.9 revision 260. Because the directory structure is new in release 4.9, users must do a full rebuild when on 4.8 or older. Remember a full rebuild will completely wipe and rebuild your REX so save important data to a TPDD device!

These are the checksums for revision 260:

  M100 = DF79
  T200 = 18BA
  NEC = 3B3E

If your checksum (by pressing I) is not this, then you should upgrade.


StatusReleaseModelDescriptionFileRevision
Beta4.9M100/T102REX Release 4.9 Rebuild PackageR49_M100T102_260_rebuild260
Beta4.9T200REX Release 4.9 Rebuild Package R49_T200_260_rebuild260
Beta4.9NECREX Release 4.9 Rebuild Package R49_NEC_260_rebuild260


The following files may be downloaded and used to upgrade your REX from an earlier R4.9 to revision 260. These files are update only; directory and flash contents should stay the same after the update to REXROM.


StatusReleaseModelDescriptionFileRevision
Beta4.9M100/T102REX Release 4.9 Update PackageR49_M100T102_260_update260
Beta4.9T200REX Release 4.9 Update Package R49_T200_260_update260
Beta4.9NECREX Release 4.9 Update Package R49_NEC_260_update260

About Main ROM Management

Please see the main REX wiki page for a description of this feature - how to prepare a ROM image, how to modify the hardware, and how to load REX with images.