Difference between revisions of "REX"

From Bitchin100 DocGarden
Jump to: navigation, search
(Additional Utilities)
Line 65: Line 65:
  
 
== Future Roadmap ==
 
== Future Roadmap ==
 +
 +
REX2 will be available in the near future.  It provides additional blocks of SRAM, allowing an all RAM mode of operation, for CP/M support.
 +
 +
 +
== Rel. 4.2 Beta testing: bug reports/fixes ==
 +
 +
1)  Year bug - the year data is not correctly preserved by REX when RAM images are saved and loaded.  Solution - implement a mechanism that maintains the year data properly.  TBD
 +
 +
2)  directory bug with entry for block 31 - it appears that the name entry for block 31 is not displayed correctly, investigation continuing.
 +
 +
3)  sounds - currently REX uses audible clicks to indicate progress, which can be annoying.  Solution - disable audio, replace with some other mechanism.  TBD
 +
 +
4)  directory order - current directory entries are displayed in order of block number, which is problematic since this causes reordering whenever REX garbage collection forces an image to be moved from one block to another.  Solution - replace this with a listing based on chronological order in the directory.  TBD
 +
 +
5)  Overall stability - there may be some bugs lurking still regarding ram image swapping and stability.  Still under investigation.
 +
 +
6)  Robustness for TPDD routines - under investigation
 +
 +
7)  Restore from current ram image - there is no easy way to restore from the current backup image.  Solution TBD. work around is to copy the backup image to a new block, and then install that image.
 +
 +
8)  non-blank block recovery - it is possible that REX attempts to copy an image to a non blank block.  This situation is indicitive of a problem with the system since this should never happen.  If it does occur, the system gets in a deadlock condition.  Solution - make sure REX has no bugs in this functionality first, but an option to "name" or "delete" the offending block would be a nice safety system.  TBD.
 +
  
  
  
 
[[Category:Model T Hardware]]
 
[[Category:Model T Hardware]]

Revision as of 05:45, 16 April 2009

Red logo small.png

What Is REX

REX is completely plug and play flash memory upgrade. REX plugs into the Option ROM slot, with no soldering or necessity to open the laptop case.

REX provides support for up to 16 in-circuit selectable option roms. That means, you can have 16 different software packages on one Option ROM, and select between them without physically unplugging anything.

In addition, REX is in-circuit, software reprogrammable. That means you can change, patch, or replace an Option ROM image without any special hardware or physically unplugging REX.

An additional feature is a facility for freezing/thawing up to 16 RAM images to/from flash. This offers an easy way to quickly backup all RAM to flash, or switch between multiple snapshots of RAM. This is similar to the "fast switch environments" on Remem: it would be like having multiple laptops in the same case!

For advanced users, REX distinguishes between traditional option rom software, and alternative OS software which runs from the option rom memory location. This allows for some interesting future capabilities like CP/M or a FORTH based system.

REX Overview PDF

REX Manager

REX comes pre-programmed with REX Manager software. REX Manager allows you to pick which of the ROM or OS images is the one currently in use, and also supports management of RAM images.

REX Manager operates "behind the scenes" to make sure the currently selected Option ROM image is automatically enabled on every power cycle. This is an impressive trick since REX does not receive power while the laptop is off (unlike the RAM memory circuit).

REX Manager is started by running the program REXMGR.BA from Menu.

Advanced BASIC ROM Replacement Mode (OPTIONAL)

For users with the do-it-yourself spirit, an optional feature of REX can be enabled.

With a single wire soldered in place, REX permits BASIC ROM replacement!

This means that you can disable the built-in BASIC/TEXT/TELCOM ROM on your motherboard and replace it with a specific block of REX flash memory. Typically, this will be the same BASIC/TEXT/TELCOM ROM image we know and love, with a few changes. So, you can upgrade your Model T with little tweaks like Y2K, the lomem patch, new character sets, put your name on the main menu, etc.

Installing REX Manager - It's Easy

From a cold restart, power cycle the laptop and the simply type

CALL 63012

will install the REX system.

You should see a program in the Menu called REXMGR.BA. Running this program will always start the REX Manager software.

Additional Utilities

REXUPG.CO is a utility that allows the user to upgrade the internal REX Manager software.

REXMR.CO is a utility that allows the user to program upgraded main rom images into REX for use in "ROM Replacement" installations.

Future Roadmap

REX2 will be available in the near future. It provides additional blocks of SRAM, allowing an all RAM mode of operation, for CP/M support.


Rel. 4.2 Beta testing: bug reports/fixes

1) Year bug - the year data is not correctly preserved by REX when RAM images are saved and loaded. Solution - implement a mechanism that maintains the year data properly. TBD

2) directory bug with entry for block 31 - it appears that the name entry for block 31 is not displayed correctly, investigation continuing.

3) sounds - currently REX uses audible clicks to indicate progress, which can be annoying. Solution - disable audio, replace with some other mechanism. TBD

4) directory order - current directory entries are displayed in order of block number, which is problematic since this causes reordering whenever REX garbage collection forces an image to be moved from one block to another. Solution - replace this with a listing based on chronological order in the directory. TBD

5) Overall stability - there may be some bugs lurking still regarding ram image swapping and stability. Still under investigation.

6) Robustness for TPDD routines - under investigation

7) Restore from current ram image - there is no easy way to restore from the current backup image. Solution TBD. work around is to copy the backup image to a new block, and then install that image.

8) non-blank block recovery - it is possible that REX attempts to copy an image to a non blank block. This situation is indicitive of a problem with the system since this should never happen. If it does occur, the system gets in a deadlock condition. Solution - make sure REX has no bugs in this functionality first, but an option to "name" or "delete" the offending block would be a nice safety system. TBD.