|
|
| (2 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| | | dead page |
| = Upgrading your REXCPM from Version 1 to Version 2 =
| |
| | |
| If you are here, you are looking for instructions on how to upgrade your REXCPM from Version 1 to Version 2.
| |
| | |
| The process to do this upgrade is only slightly different from simply the normal upgrade process.
| |
| | |
| The reason for the change, is that the internal image directory for REXCPM has been moved to a new location in the SRAM chip. While a little annoying to need an extra step, the change aligns REX# and REXCPM so they can use the same subroutines, which is helpful for product support.
| |
| | |
| Thanks for your understanding.
| |
| | |
| | |
| = Special Upgrade Process =
| |
| | |
| The upgrade process consists of two steps.
| |
| | |
| <big>'''Step 1:'''</big> Run the utility one-time to copy your directory contents to the new location.
| |
| | |
| <big>'''Step 2:'''</big> Use RXCINI.DO to load the new RXCMGR application.
| |
| | |
| | |
| | |
| ==Step 1 - Copy the Directory==
| |
| | |
| As mentioned, the first step is to run a utility that copies the current directory to the new location. The utility is DIRCPY.DO
| |
| | |
| What is important here, is that the directory needs to be accurate when copied, and after you copy it, don't use RXCMGR to alter the Image directory. You want to immediately complete the upgrade so that Version 2 starts up with the correct directory.
| |
| | |
| Running DIRCPY.DO does not impair RXCMGR version 1 in any way. So, if you run the utility and decide not to do the upgrade, no problem.
| |
| | |
| You can also revert to version one if you wish.
| |
| | |
| The key thing is - the directory contents need to be accurate for either Version 1 or Version 2 of RXCMGR to work correctly.
| |
| | |
| Notes:
| |
| ======
| |
| * DIRCPY.DO replicates the directory, and leaves the current one intact.
| |
| * So, RXCMGR (version 1) can continue to be used even after you run DIRCPY.DO
| |
| | |
| | |
| When you are ready to do the upgrade to Version 2, then start by running DIRCPY.DO. Here is the utility.
| |
| | |
| Here's the software:
| |
| {| class="wikitable"
| |
| |'''Utility'''||'''Version'''||'''File'''
| |
| |-
| |
| |DIRCPY||1||[[Media:DIRCPY.ZIP|DIRCPY.DO]]
| |
| |-
| |
| |}
| |
| | |
| | |
| Step 1 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 DIRCPY.DO via serial transfer, or TPDD transfer. It is now 7 bit ASCII.
| |
| DIRCPY.DO contains HEX ASCII encoded machine language, for more reliable transfer.
| |
| 3. RUN DIRCPY.DO in BASIC.
| |
| DIRCPY.DO will make a copy of the current image directory at the new location.
| |
| 4. Let the program run
| |
| When complete, your directory will have been prepared for Version 2.
| |
| | |
| | |
| Again, DIRCPY is non destructive and at this point you can continue to use REXCPM if you wish.
| |
| If you alter the directory however, you will need to run DIRCPY.DO again when you want to upgrade to Version 2.
| |
| | |
| | |
| | |
| ==Step 2 - Upgrade the software==
| |
| | |
| Use RXCINI.DO to load the Version 2 RXCMGR application into REXCPM.
| |
| | |
| Only indicate yes to "Load REX code:".
| |
| | |
| Indicate no to "Init REX dir :". You have a valid directory!
| |
| | |
| Notes:
| |
| ======
| |
| * RXCINI Version 2 has been modified to improve ease-of-use
| |
| * The embedded machine code is now encoded as ASCII characters
| |
| * 7 bit transfer should work
| |
| * It also loads much more quickly, and includes checksum verification
| |
| * If you get the message "CAN'T RUN"
| |
| ---> please remove the REX hook (CNTL-X or F7)
| |
| ---> power cycle
| |
| ---> and try again
| |
| | |
| | |
| Here's the software:
| |
| {| class="wikitable"
| |
| |'''Utility'''||'''Version'''||'''File'''
| |
| |-
| |
| |RXCINI||2||[[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 now 7 bit ASCII.
| |
| RXCINI.DO contains HEX ASCII encoded machine language, for more reliable transfer.
| |
| 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 NO 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.
| |
| | |
| To install RXCMGR:
| |
| --->Power off.
| |
| --->Power on.
| |
| --->From BASIC,
| |
| ---> CALL 63012
| |
|
| |
| You should see RXCMGR as a MENU entry. Selecting that will start RXCMGR software.
| |
| | |
| Note:
| |
| =====
| |
| If you see an error message - "CAN'T RUN", this means that REXCPM is not in the default state.
| |
| See instruction #1 above!
| |
| | |
| [[Category:Model T Hardware]]
| |
