REXsharp: Difference between revisions

From Bitchin100 DocGarden
Jump to navigationJump to search
No edit summary
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Image:REXsharp.PNG]]
[[Image:REXsharp.PNG]]


== Overview ==
'''under development! stay tuned!'''
 
= Overview =


<big>'''What is REX#?'''</big>
<big>'''What is REX#?'''</big>
Line 12: Line 14:




<big>'''Main Benefits of REX#'''</big>
<big>'''Main Features and Functions of REX#'''</big>


REX# (via REXMGR software) enables several key capabilities for the Model T user.   
REX# (via REXMGR software) enables several key capabilities for the Model T user.   
Line 18: Line 20:
* Option ROMs: Applications for Model T laptops were originally distributed as Option ROMs.  These ROM images may be loaded into flash blocks, and then quickly switched/activated for use by REX Manager.
* Option ROMs: Applications for Model T laptops were originally distributed as Option ROMs.  These ROM images may be loaded into flash blocks, and then quickly switched/activated for use by REX Manager.
* RAM Images:  Users can quickly backup or restore the current working RAM of the laptop into one of the 32k flash blocks.  This provides a great way to store data, programs, or quickly recover from a cold boot situation.
* RAM Images:  Users can quickly backup or restore the current working RAM of the laptop into one of the 32k flash blocks.  This provides a great way to store data, programs, or quickly recover from a cold boot situation.
* Quick Menu:  the laptop main menu now has some custom keystrokes that speed up REX# usage.
* Active Optrom display:  the main menu also shows the name of the installed option ROM.
* Additional nice things:  REX Manager fixes the Y2K date display problem
* Additional nice things:  REX Manager fixes the Y2K date display problem


 
= Model T variants supported by REX# =
<big>'''Model T variants supported by REX#'''</big>


* TRS-80 Model 100
* TRS-80 Model 100
Line 31: Line 34:




=== M100 note ===
=== Notes ===
 
Model 100:
* 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.
* REX# does not function correctly in these models, due to the significantly different main ROM.


  In Europe and UK, and probably elsewhere, there are newer versions of M100 that have different boards.
Olivetti M10 note:
  Model numbers are 26-3801B and 26-3802B.
* In order to use REX#, the Olivetti M10 must have it's main ROM updated to be "like the M100".
  REX# does not function correctly in these models, due to the significantly different main ROM.
* The M10 is compatible with standard 27C256 eproms, so it is a matter of obtaining the replacement main ROM image, burning the image and mounting the chip in the main ROM socket.
 
* the link to the M10 ROM page --> [[Olivetti M10 ROM patch|Olivetti M10 ROM patch]]


=== Links ===
= Links =
[[M100 CP/M|Philip Avery's M100 CP/M Page]]


[[REX|REX Products home page]]
[[REX|REX Products home page]]


[[Ordering_Information|REX Products ordering information]]
[[Ordering_Information|REX Products ordering information]]


= Status =
= Status =
Line 54: Line 61:
= Quick Start =
= Quick Start =


So, you have just received your REXCPM and want to get going.   
So, you have just received your REX# and want to get going.   


AS SHIPPED REXCPM CONTAINS NO SOFTWARE!!!! You must INITIALIZE your REXCPM to get started!
1) Power down the laptop. Follow the hardware installation steps.


'''IMPORTANT''': CALL 63012 <u>will not work</u> prior to REXCPM being initialized with RXCINI!
2)  Power on your laptop, enter BASIC, and type


M100/T102/M10:
  CALL63012


T200 (Bank 1 only):
  CALL61167,2


Here's what you need to do:
NEC (Bank 1 only):
  EXEC62394


  0.  Read this entire page!  There is information further in the page that you need to know to be able to
      initialize the device, and get started
  00. '''AFTER''' going through the initialization procedure outlined below and the main REX software is loaded
      onto your REXCPM, it will be able to be used just like REX. You can review the information at the REX Wiki
      page for general information about REX use. But don't jump ahead just yet!


  1.  Install your REXCPM.  Links to information about installation in M100 and T102 is at this page, below.
REX Manager will check for and install the REXMGR menu entry, and REX Manager will start.
  2.  Initialize your REXCPM by running RXCINI.DO.  This lets you load the RXCMGR application and initialize the directory.
REX# ships with TS-DOS pre-loaded, so you can get started with that application immediately.
      Unlike REX, REXCPM is based on RAM and cannot be shipped pre-programmed.
      The user must install the RXCMGR application, which is a binary file which must be loaded into a
      specific memory block in the SRAM.
      Additionally, the RXCMGR application needs a directory, to track what ROM images are stored in REX.
      Please scroll down and read about how to use RXCINI.DO.  Software is available below.
  3.  Now you are ready to use REXCPM and RXCMGR.  You can use it just like a REX.  Create ram backups, load option ROMs etc.


In the main Menu of the laptop, you will see a program called REXMGR is now installed.  You can run that program any time to enter REX Manager, to load and run all the different ROMs you wish, and to allow you to manage your RAM backups.


Once initialization is complete, you can access RXCMGR.
To load files to/from REX, you MUST have a way of hosting files REX can access over the serial (RS232) port.
 
To host files for transfer to REX via REX Manager alternatives include
* [[NADSBox]], [[LaddieCon]] for Windows XP, 2000, Vista, Windows 7,
* [[DLPlus]] for Linux/OSX/BSD, [[Desklink]] for Win98 or DOS or
* [[DLPilot]] for PalmOS 3.x era devices (UNVERIFIED, but should work)
as the best [[TPDD]] devices for use with REX Manager.


  Power cycle the laptop to ensure that REXCPM hardware is in the default state.
  In BASIC, type
      CALL 63012
  This should start RXCMGR, and should install RXCMGR in the laptop directory.


= Hardware Installation =
= Hardware Installation =


Installation information for Model 100 here ----> [[REXCPM Installation in M100|M100 install]]
Installation information for Model 100 here ----> [[REXsharp Installation in M100|REX# M100 install]]


Installation information for Tandy 102 here ----> [[REXCPM Installation in T102|T102 install]]
Installation information for Tandy 102 here ----> [[REXsharp Installation in T102|REX# T102 install]]


= Use with M100CP/M =
Installation information for Tandy 200 here ----> [[REXsharp Installation in T200|REX# T200 install]]


REX operation and CP/M operation are independent.  To install CP/M, follow the instructions on the M100CP/M page.
Installation information for NEC here ----> [[REXsharp Installation in NEC|REX# NEC install]]
The link to Philip's M100CP/M page is near the top of this page.
Once CP/M is running, REX provides a quick mechanism to "jump" into it.


  REX Quick Menu function has been expanded to include a new command.
Installation information for M10 here ----> [[REXsharp Installation in M10|REX# M10 install]]
  CNTL-C from MENU immediately transfers control to CP/M.
 
= Use with MVT100 external Video =
 
Currently the REXCPM "ROM" software is not compatible with the VT100 driver for M100.  I am working on integrating this function, but for now they conflict because they both try to use the CHGET hook.
 
It is possible to use use MVT100 with REXCPM by un-installing the REX hook (CNTL-X at MENU).  After REX is inoperative, the VT100 driver can be loaded.  But since there is no way to remove the VT100 software once installed, I would suggest caution.
 
As soon as I have integrated the VT100 driver into REXCPM, I will post an update.


= Documentation =
= Documentation =


  Stay tuned!
[[REX Manager User Guide for REXsharp]]


= Software =  
= Technical Information =


==="The ROM"===


As shipped, REXCPM is a blank piece of SRAM.  In order to get rolling you need to load in the REXCPM "ROM" application.
= Use with MVT100 external Video =
Use RXCINI to load the following software.


Here's the software:
Currently the REX Manbager software is not compatible with the VT100 driver for M100I am working on integrating this function, but for now they conflict because they both try to use the CHGET hook.
{| class="wikitable"
|'''REXCPM "ROM"'''||'''Build'''||'''Status'''||'''File'''
|-
|RXC_11||39|| BetaStill testing! ||[[Media:RXC_11_b39.ZIP|RXC_11_b39.ZIP]]
|-
|}


  Note:  REXCPM "ROM" software is based on classic REX with several differences.
It is possible to use use MVT100 with REXCPM by un-installing the REX hook (CNTL-X at MENU).  After REX is inoperative, the VT100 driver can be loaded.  But since there is no way to remove the VT100 software once installed, I would suggest caution.
          - 16 32k Blocks are available for use by the REXCPM "ROM"
          - the remaining SRAM is dedicated to CP/M use
          - the software has some simplifications
          - SRAM based operation means some low level changes to how REX works
          Please communicate any bug reports.


===Initialization===
As soon as I have integrated the VT100 driver into REXCPM, I will post an update.


A tool is available for initializing a fresh REXCPM, or if you want to rebuild it you can use this tool also.
Since REXCPM is based on SRAM, and there is no on-board battery (only a large 1000uF capacitor), by the time you receive your REX the memory contents will be blank.  So, you have to load REXCPM with the REXCPM application and any option ROMs you want to use.
Here's the software:
{| class="wikitable"
|'''Utility'''||'''Version'''||'''File'''
|-
|RXCINI||1||[[Media:RXCINI.ZIP|RXCINI.DO]]
|-
|}
  Instructions
  ============
  1.  Make sure REXCPM is in default state, meaning
      a. RXCMGR is not running (use CNTL-X to remove hooks, or F7 from RXCMGR)
      b. Power cycle once, to ensure the default memory blocks are selected
      c. Optionally, cold-rebooting the laptop after a power cycle ensures a clean state.
  2.  Load RXCINI.DO via serial transfer, or TPDD transfer.  It is 8 bit ASCII.
      If transferring via serial, use 8 bit mode, not 7 bit.  RXCINI.DO contains encoded machine language. 
  3.  RUN RXCINI.DO in BASIC.
      RXCINI.DO allows you to do either or both of two processes:
      a.  You can choose to LOAD a REXCPM application (28kB file)
      b.  You can choose to INITIALIZE (reset to blank) the REX directory, which stores ROM image names. 
      You can guess that initializing the directory removes any existing directory entries.
      The REXCPM application EXCLUDES the directory, so you must initialize the directory if you are
      starting from scratch and there is no existing directory (or stored images!).
  4.  Configure RXCINI.DO to do the following:
      a.  indicate YES to "Load REX code:"
      b.  indicate YES to "Init REX dir :"
      c.  execute these choices
  5.  The loader will load up the machine language routine, and begin to execute
  6.  To LOAD a fresh REXCPM application, RXCINI.DO accesses a remote TPDD device to get the binary 28k file.
      RXCINI.DO contains it's own TPDD access routines, and does not need a DOS.
      a. Ensure a TPDD device is ready to go with the source file as needed.
      b. Supply the correct file name (6 characters, no extension, case sensitive)
      File extension is automatically set to .BR
  7.  Let the program run
      When complete, REXCPM should have a fresh "ROM" load for REXCPM, and a freshly initialized directory.
  From BASIC,
  CALL 63012
  to start/install RXCMGR.


= Software =


  Note:
===REXMGR ROM Image===
  If you see an error message - "Can't run!", this means that REXCPM is not in the default state.


===Backup and Restore===
As shipped, REX# contains the currently supported REX Manager ROM image.  It also includes TS-DOS.
Upgrades to REX Manager ROM will be provided over time to address bugs or possibly add features.


A tool is available for backing up or restoring REXCPM memory contents to TPDD.
'''this will be updated when there is an upgrade available'''
Some of the REXCPM SRAM is dedicated to CP/M while other memory is dedicated to REX functionality.
This tool allows you to select:


  * Either a Backup or Restore process
  * REXCPM or CP/M memory regions
    REXCPM memory includes REXCPM ROM image + directory + 16 blocks
    Total of 17 32kB blocks.
    CP/M memory includes all of the CP/M disk space, including directory (but excluding CP/M OS)
    For 2MB, 40 32kB blocks.  For 4MB, 104 32kB blocks.
  * Serial port speed - 19200 8N1 or 76800 8N1 "Large Packet"


===Upgrade Utility for REX#===


The tool uses the standard RS-232 port on the M100.  Standard TPDD clients can operate at 19200 baud, but LaddieAlpha is capable of operation at 76800 baud, and also able to support large packet sizes, both of which help to speed up the process.


  NOTE:  LaddieAlpha with 76800 Large Block support is not generally available yet.  Stay tuned.
A tool is available for upgrading REX# to a newer build.


Backup/Restore processes can take some time; use this table for guidance.
'''this will be updated when there is an upgrade available'''


{| class="wikitable"
|'''Process'''||'''Memory size'''||'''Duration'''||'''Duration'''
|-
|REXCPM||either||19200||5:20 min
|-
|CP/M||2MB||19200||13 min
|-
|CP/M||4MB||19200||33 min
|-
|REXCPM||either||76800||2:10 min
|-
|CP/M||2MB||76800||5 min
|-
|CP/M||4MB||76800||13:15 min
|-
|}


Here's the software:
= Option ROM Images for Download =
{| class="wikitable"
|'''Utility'''||'''Version'''||'''File'''
|-
|RXCUTL||1||[[Media:RXCUTL.ZIP|RXCUTL.DO]]
|-
|}


  Instructions
[[Media:M100_OPTION_ROMS.zip|Validated OPTROM Images for M100/T102]]
  ============
  1. Make sure REXCPM is in default state, meaning
      a. RXCMGR is not running (use CNTL-X to remove hooks, or F7 from RXCMGR)
      b. Power cycle once, to ensure the default memory blocks are selected
      c. Optionally, cold-rebooting the laptop after a power cycle ensures a clean state.
  2.  load RXCUTL.DO into the M100 using a terminal program on PC (lots of ways to do this)
      It is 8 bit ASCII.
      If transferring via serial, use 8 bit mode, not 7 bit.  RXCINI.DO contains encoded machine language.
  3.  Enter BASIC and type RUN"RXCUTL.DO"
  4.  Select Process, REX or CP/M, and speed
  5.  The loader will load up the machine language routine, and begin to execute
  6.  Ensure that a TPDD client is attached to the serial port
  7.  For either process, supply 6 character case-sensitive name for the file.
      File extension is set to .BB
  8.  Once executed, RXCUTL will attempt to either write or read all required data to/from REXCPM SRAM.


[[Media:T200_OPTION_ROMS.zip|Validated OPTROM Images for T200]]


  Note:
[[Media:NEC__OPTION_ROMS.zip|Validated OPTROM Images for NEC]]
  If you see an error message - "Can't run!", this means that REXCPM is not in the default state.


= Acknowledgements =
= Acknowledgements =


I would like to thank those that have contributed to the project:
I would like to thank those that have contributed to the project:
'''Philip Avery''' - for his commitment to this project and for the port of CP/M to the M100


'''John Hogerhuis''' - for all his technical support, and for this Wiki resource
'''John Hogerhuis''' - for all his technical support, and for this Wiki resource
Line 268: Line 158:
= FAQ =
= FAQ =


'''Q. I am having trouble loading RXC***.DO using serial transfer.  It keeps crashing!'''
A. Please ensure you are transferring the file to the laptop in 8 bit mode.  While the file is ASCII, it contains 8 bit ASCII because there is embedded machine language.
'''Q. Why do I need an adapter?'''
A. The adapter does 3 things:  it disables the internal RAM, it sends 'RAM active' signal to REXCPM, and it provides battery power to REXCPM to keep the SRAM "alive".
'''Q. Is Tandy 102 a plug and play installation?'''
A. No. Model 100 is plug and play, but T102 requires soldering of a single wire.
Details are available on this site for how to install on T102.
'''Q. Will REXCPM come out for T200?'''
A.  There are currently no plans to support REXCPM in the T200 platform.
'''Q. Will REXCPM come out for NEC PC-8201?'''
A.  This is being investigated. 
'''Q. Are the REX memory images which REXCPM saves and restores to TPDD compatible with the images (.BY files) saved and restored by REX classic?  Ie. will I be able to take a .BY file I saved from my REX classic, load it into REXCPM, switch to it, and have everything work properly?  Or is this going to blow up in my face?  :)
A.  There were no changes in this functionality, so it should work.  I have not tested this though.  REXCPM is always 32k images, so your REXclassic image would also need to be 32k.
'''Q. Can I access the banking functionality of REXCPM via BASIC?
A.  Yes.  There are 3 banks:  Option ROM 0000-7FFF, low RAM 8000-BFFF and high RAM C000-FFFF.  All 3 are accessible but the only practical use case is for Option ROM since BASIC uses both RAM banks.  The BASIC program would need to make use of a machine language routine to set the register value in REXCPM to the specific memory bank of interest.  Then, to access the RAM you would need another machine language routine.  Examples of such code can be made available at this wiki.




[[Category:Model T Hardware]]
[[Category:Model T Hardware]]

Revision as of 07:00, 26 September 2020

REXsharp.PNG

under development! stay tuned!

Overview

What is REX#?

REX# is an add-on memory card that plugs into the Option ROM socket in a supported laptop, augmenting significantly the amount of memory in the laptop as well as what that memory can be used for.

  • REX# provides 1MB of flash memory for the laptop.
  • REX# puts bank switched flash memory into the OPTION ROM memory bank (1x32k bank)
  • The 1MB flash (32 blocks of 32kB) may then be accessed, one 32k block at a time.
  • REXMGR (aka REX Manager) software, loaded into the first 32k block, makes all this memory useful!


Main Features and Functions of REX#

REX# (via REXMGR software) enables several key capabilities for the Model T user.

  • Option ROMs: Applications for Model T laptops were originally distributed as Option ROMs. These ROM images may be loaded into flash blocks, and then quickly switched/activated for use by REX Manager.
  • RAM Images: Users can quickly backup or restore the current working RAM of the laptop into one of the 32k flash blocks. This provides a great way to store data, programs, or quickly recover from a cold boot situation.
  • Quick Menu: the laptop main menu now has some custom keystrokes that speed up REX# usage.
  • Active Optrom display: the main menu also shows the name of the installed option ROM.
  • Additional nice things: REX Manager fixes the Y2K date display problem

Model T variants supported by REX#

  • TRS-80 Model 100
  • Tandy 102
  • Tandy 200
  • NEC PC-8201, 8201A, 8300
  • Olivetti M10
  • KC-85 (well I don't have one but I'm sure it would work!)


Notes

Model 100:

  • 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.
  • REX# does not function correctly in these models, due to the significantly different main ROM.


Olivetti M10 note:

  • In order to use REX#, the Olivetti M10 must have it's main ROM updated to be "like the M100".
  • The M10 is compatible with standard 27C256 eproms, so it is a matter of obtaining the replacement main ROM image, burning the image and mounting the chip in the main ROM socket.
  • the link to the M10 ROM page --> Olivetti M10 ROM patch

Links

REX Products home page

REX Products ordering information

Status

  * REX# is now generally available, and can be ordered subject to availability.
  * Inventory status will be kept up to date at the Ordering page.


Quick Start

So, you have just received your REX# and want to get going.

1) Power down the laptop. Follow the hardware installation steps.

2) Power on your laptop, enter BASIC, and type

M100/T102/M10:

 CALL63012

T200 (Bank 1 only):

  CALL61167,2 

NEC (Bank 1 only):

  EXEC62394 


REX Manager will check for and install the REXMGR menu entry, and REX Manager will start. REX# ships with TS-DOS pre-loaded, so you can get started with that application immediately.

In the main Menu of the laptop, you will see a program called REXMGR is now installed. You can run that program any time to enter REX Manager, to load and run all the different ROMs you wish, and to allow you to manage your RAM backups.

To load files to/from REX, you MUST have a way of hosting files REX can access over the serial (RS232) port.

To host files for transfer to REX via REX Manager alternatives include

as the best TPDD devices for use with REX Manager.


Hardware Installation

Installation information for Model 100 here ----> REX# M100 install

Installation information for Tandy 102 here ----> REX# T102 install

Installation information for Tandy 200 here ----> REX# T200 install

Installation information for NEC here ----> REX# NEC install

Installation information for M10 here ----> REX# M10 install

Documentation

REX Manager User Guide for REXsharp

Technical Information

Use with MVT100 external Video

Currently the REX Manbager software is not compatible with the VT100 driver for M100. I am working on integrating this function, but for now they conflict because they both try to use the CHGET hook.

It is possible to use use MVT100 with REXCPM by un-installing the REX hook (CNTL-X at MENU). After REX is inoperative, the VT100 driver can be loaded. But since there is no way to remove the VT100 software once installed, I would suggest caution.

As soon as I have integrated the VT100 driver into REXCPM, I will post an update.


Software

REXMGR ROM Image

As shipped, REX# contains the currently supported REX Manager ROM image. It also includes TS-DOS. Upgrades to REX Manager ROM will be provided over time to address bugs or possibly add features.

this will be updated when there is an upgrade available


Upgrade Utility for REX#

A tool is available for upgrading REX# to a newer build.

this will be updated when there is an upgrade available


Option ROM Images for Download

Validated OPTROM Images for M100/T102

Validated OPTROM Images for T200

Validated OPTROM Images for NEC

Acknowledgements

I would like to thank those that have contributed to the project:

John Hogerhuis - for all his technical support, and for this Wiki resource

Kenneth Pettit - for VirtualT as this project would not have happened without it

Brian White - for his innovative PCB2MOLEX carrier design


FAQ