Bitchin100 DocGarden - User contributions [en]

Main ROM Management Feature

2010-06-14T03:07:07Z

209.195.69.117: New page: Main ROM Management is feature in REX whereby the internal ROMs may be replaced by specific blocks in REX. There are 4 blocks reserved for this - block 2 for the "Primary" Main ROM, and b...

Main ROM Management is feature in REX whereby the internal ROMs may be replaced by specific blocks in REX. There are 4 blocks reserved for this - block 2 for the "Primary" Main ROM, and block 4 for the "Secondary". In the M100/T102, only 32k is required for the Main ROM, but in the T200, 64k is needed (occupying block 3 and 5 also).

The Primary main ROM is the power up default for REX, and should be handled carefully.

However, REX is not able to deduce if the original main ROM is in use, or not. So, we have to help the system out by following a simple rule.

'''Any ROM image that is installed in REX for use in Main ROM Replacement must have a small signature included.'''

This signature is the chaning of the word "MENU" to the word "Menu" at offset 0003h in the standard binary. When REX sees lower case characters, it "deduces" that the original internal ROM is no longer in use, and one of the REX based main ROM images is in use.

REX

2010-06-14T02:57:43Z

209.195.69.117: /* Acknowledgements */

[[Image:Red_logo_small.png||center]]<br/>

== NEWS! ==
* June 13, 2009: Check out the new info on what do to if you delete REXMGR.BA by mistake, posted below.

* Sept. 1, 2009: Seems that Business Analyst option rom does not work in T102 for reasons unknown.

* Aug. 31, 2009: I realize that it may not be clearly stated, but REX is not compatible with any other M100 system that uses LOMEM software. Programs like power dos and PCSG RAM modules that place a basic program in memory typically are in conflict with REX. My apologies if people have had problems.

* Aug. 7, 2009: ROM Replacement feature is being integrated into REX Manager. Specific M100/T102 main rom images will be required, so I have removed M100.bx and T102.bx from the downloadable rom image .zip.

* Aug. 5, 2009: An updated image set is online. I stupidly forgot to make Multiplan and Integrated Solutions ROMs impervious to removal detection by the M100 ROM. These 2 roms have "AB" at locations 0040 and 0041 hex. The patch is to place 00 in locations 0040 and 0041 hex. Corrected binaries are now in the file. This should only affect M100, as T102 OS looks for "TC" rather than "AB".

== For Owners ==

Own REX, need help Getting Started?

<big>[[REX Quickstart guide]]</big>

Keep in mind the following-
* For current release 4.5, do not fill REX beyond 1/2 full (12 remaining blocks must be free).
* make sure you put real data into the default BACKUP entry in RAM group

Click on these links for information on specific software releases - release notes, update proceedure, downloads, new features descriptions etc.

<big>[[soon to be released REX Release 4.6]]</big>

<big>[[Main ROM Management Feature]]</big>

<big>[[REX Release 4.5]]</big>

== 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 gets it's name by being a cross between my other flash memory device, ReMem, and the original OPTION ROM (RAM) memory card, EXTRam.

The primary features of REX are:

* REX allows for quick and easy switching between OPTION ROM images. Once the binary software images are loaded into REX, the user can easily jump back and forth between different applications. 16 OPTION ROMs may be loaded, stored and used.

* REX provides the ability to backup and swap working RAM images. At the press of a key, your current RAM contents are saved in REX. Furthermore, you can reload any saved RAM image for use. This creates a library of RAM images, which has a number of uses. 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 is like having multiple laptops in the same case! 16 RAM images may be stored.

* REX includes an interface to TPDD devices (like TPDD, NADSbox, LaddieCon etc) for loading and saving binary images to external storage.

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.

For advanced users, REX provides some additional features:

* 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 also supports "Main ROM Replacement". This means that, with the addition of a single wire, the main rom on the laptop may be replaced by a version stored in REX. This allows for flash-upgradeable main ROM images, to support patches, custom Menu and character sets, LOMEM patch, Y2K patch etc.

REX may be installed in Model 100 and Tandy 102 currently. Tandy 200 support is not yet available but is in development.

'''REX is available exclusively through Club100.'''

[[Image:REX_installed.jpg]]

[[Media:Rex_OverviewV4.2.pdf|REX Overview PDF]]

[[REX Overview]]

[[REX Hardware Installation]]

[[REX Manager User Guide]]

[[REX Software and Utilities]]

[[Main ROM Replacement]]

[[Media:M100_REX_tested.zip|REX Validated OPTROM Images for M100/T102]]

[[REX2 - custom REX for CP/M support]]

== Software Installation of the REX System- It's Easy ==

In order to initialize the laptop to use REX, you must install the REX system. From a cold restart, power cycle the laptop and then simply type

(for M100/T102)
<code><pre>CALL 63012</pre></code>

(for T200)
<code><pre>CALL 61167,2</pre></code>

to install the REX system, which installs one hook in the timer, includes two short programs.

* first, an invisible file called RXHOOK which contains a special machine language routine that interacts with the timer hook in the laptop, to ensure that REX is properly configured on power up.

* and a visible basic program called REXMGR.BA. This program contains a short embedded machine language routine that starts the REX Manager software on command.

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

After REX Manager is installed, issuing those same commands won't re-install the system, but you will be directed to the Active OPTROM image software instead, just like you would expect if you had a normal option ROM installed.

If the REX system should somehow become de-installed (like on a cold restart) simply re-install it by repeating these instructions.

== Important Note for First Time REX Installation and Use ==

IMPORTANT! For brand new REX installations, where REX has been unused, the user must replace the default "backup" RAM image stored in REX, with a real backup image. Simply start REX Manager, move the cursor over the directory entry for "backup", and press <ENTER>. Select <Y> when prompted to "Refresh backup?". This puts a fresh RAM image for your specific machine into that entry.

== Compatibility between REX and certain other M100 applications ==

REX is NOT COMPATIBLE with certain M100 software and devices, where software conflicts arise with hidden .BA programs in RAM.

Specifically,

POWER-DOS
PCSG RAM MODULES

...and other things as well I am sure, are not compatible with REX.

The incompatibility lies in the software. REX requires that a
specific invisible .BA program called RXHOOK be present as the "first
basic program" at the lowest memory location, making this a form of
"LOWMEM software".

These incompatible applications also use LOWMEM software, and as such
they overlap and will cause problems. So, you cannot use REX today with those applications.

I will look into changes I can make to allow these things to coexist,
but I don't have all variants of what is possible, so it is hard for
me to ensure it works with everything.

If you own a REX and you are using it with some other piece of
internal memory system, in general I would say it is not compatible -
it is one or the other.

If this incompatibility is causing you problems, I apologize for the lack of clarity.

== Starting REX Manager if REXMGR.BA is accidentially deleted... ==

What to do? You accidentally delete REXMGR.BA from the menu, and now you can't start REX Manager because the active ROM is always accessed.

In Release 4.5, the best course of action is to delete the timer hook, which de-activates the auto configuration of REX. In BASIC, type the following commands:

POKE62975,201

Now, power cycle the laptop, enter BASIC and type
CALL63012
and you will start REX Manager again, which will reinstall the software.

== Acknowledgements ==

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

'''John Hogerhuis''' - for all his technical support

'''Philip Avery''' - for his assistance in coding the MENU functions

'''Wilson Van Alst''' - for providing the base TPDD routines

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

'''Club 100 and Rick Hanson''' - for helping to get this gadget out there

and others for their helpful comments and support.

[[Category:Model T Hardware]]

REX

2010-06-14T02:57:07Z

209.195.69.117:

[[Image:Red_logo_small.png||center]]<br/>

== NEWS! ==
* June 13, 2009: Check out the new info on what do to if you delete REXMGR.BA by mistake, posted below.

* Sept. 1, 2009: Seems that Business Analyst option rom does not work in T102 for reasons unknown.

* Aug. 31, 2009: I realize that it may not be clearly stated, but REX is not compatible with any other M100 system that uses LOMEM software. Programs like power dos and PCSG RAM modules that place a basic program in memory typically are in conflict with REX. My apologies if people have had problems.

* Aug. 7, 2009: ROM Replacement feature is being integrated into REX Manager. Specific M100/T102 main rom images will be required, so I have removed M100.bx and T102.bx from the downloadable rom image .zip.

* Aug. 5, 2009: An updated image set is online. I stupidly forgot to make Multiplan and Integrated Solutions ROMs impervious to removal detection by the M100 ROM. These 2 roms have "AB" at locations 0040 and 0041 hex. The patch is to place 00 in locations 0040 and 0041 hex. Corrected binaries are now in the file. This should only affect M100, as T102 OS looks for "TC" rather than "AB".

== For Owners ==

Own REX, need help Getting Started?

<big>[[REX Quickstart guide]]</big>

Keep in mind the following-
* For current release 4.5, do not fill REX beyond 1/2 full (12 remaining blocks must be free).
* make sure you put real data into the default BACKUP entry in RAM group

Click on these links for information on specific software releases - release notes, update proceedure, downloads, new features descriptions etc.

<big>[[soon to be released REX Release 4.6]]</big>

<big>[[Main ROM Management Feature]]</big>

<big>[[REX Release 4.5]]</big>

== 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 gets it's name by being a cross between my other flash memory device, ReMem, and the original OPTION ROM (RAM) memory card, EXTRam.

The primary features of REX are:

* REX allows for quick and easy switching between OPTION ROM images. Once the binary software images are loaded into REX, the user can easily jump back and forth between different applications. 16 OPTION ROMs may be loaded, stored and used.

* REX provides the ability to backup and swap working RAM images. At the press of a key, your current RAM contents are saved in REX. Furthermore, you can reload any saved RAM image for use. This creates a library of RAM images, which has a number of uses. 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 is like having multiple laptops in the same case! 16 RAM images may be stored.

* REX includes an interface to TPDD devices (like TPDD, NADSbox, LaddieCon etc) for loading and saving binary images to external storage.

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.

For advanced users, REX provides some additional features:

* 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 also supports "Main ROM Replacement". This means that, with the addition of a single wire, the main rom on the laptop may be replaced by a version stored in REX. This allows for flash-upgradeable main ROM images, to support patches, custom Menu and character sets, LOMEM patch, Y2K patch etc.

REX may be installed in Model 100 and Tandy 102 currently. Tandy 200 support is not yet available but is in development.

'''REX is available exclusively through Club100.'''

[[Image:REX_installed.jpg]]

[[Media:Rex_OverviewV4.2.pdf|REX Overview PDF]]

[[REX Overview]]

[[REX Hardware Installation]]

[[REX Manager User Guide]]

[[REX Software and Utilities]]

[[Main ROM Replacement]]

[[Media:M100_REX_tested.zip|REX Validated OPTROM Images for M100/T102]]

[[REX2 - custom REX for CP/M support]]

== Software Installation of the REX System- It's Easy ==

In order to initialize the laptop to use REX, you must install the REX system. From a cold restart, power cycle the laptop and then simply type

(for M100/T102)
<code><pre>CALL 63012</pre></code>

(for T200)
<code><pre>CALL 61167,2</pre></code>

to install the REX system, which installs one hook in the timer, includes two short programs.

* first, an invisible file called RXHOOK which contains a special machine language routine that interacts with the timer hook in the laptop, to ensure that REX is properly configured on power up.

* and a visible basic program called REXMGR.BA. This program contains a short embedded machine language routine that starts the REX Manager software on command.

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

After REX Manager is installed, issuing those same commands won't re-install the system, but you will be directed to the Active OPTROM image software instead, just like you would expect if you had a normal option ROM installed.

If the REX system should somehow become de-installed (like on a cold restart) simply re-install it by repeating these instructions.

== Important Note for First Time REX Installation and Use ==

IMPORTANT! For brand new REX installations, where REX has been unused, the user must replace the default "backup" RAM image stored in REX, with a real backup image. Simply start REX Manager, move the cursor over the directory entry for "backup", and press <ENTER>. Select <Y> when prompted to "Refresh backup?". This puts a fresh RAM image for your specific machine into that entry.

== Compatibility between REX and certain other M100 applications ==

REX is NOT COMPATIBLE with certain M100 software and devices, where software conflicts arise with hidden .BA programs in RAM.

Specifically,

POWER-DOS
PCSG RAM MODULES

...and other things as well I am sure, are not compatible with REX.

The incompatibility lies in the software. REX requires that a
specific invisible .BA program called RXHOOK be present as the "first
basic program" at the lowest memory location, making this a form of
"LOWMEM software".

These incompatible applications also use LOWMEM software, and as such
they overlap and will cause problems. So, you cannot use REX today with those applications.

I will look into changes I can make to allow these things to coexist,
but I don't have all variants of what is possible, so it is hard for
me to ensure it works with everything.

If you own a REX and you are using it with some other piece of
internal memory system, in general I would say it is not compatible -
it is one or the other.

If this incompatibility is causing you problems, I apologize for the lack of clarity.

== Starting REX Manager if REXMGR.BA is accidentially deleted... ==

What to do? You accidentally delete REXMGR.BA from the menu, and now you can't start REX Manager because the active ROM is always accessed.

In Release 4.5, the best course of action is to delete the timer hook, which de-activates the auto configuration of REX. In BASIC, type the following commands:

POKE62975,201

Now, power cycle the laptop, enter BASIC and type
CALL63012
and you will start REX Manager again, which will reinstall the software.

== Acknowledgements ==

I would like to thank those that have contributed to the project:
'''John Hogerhuis''' - for all his technical support
'''Philip Avery''' - for his assistance in coding the MENU functions
'''Wilson Van Alst''' - for providing the base TPDD routines
'''Kenneth Pettit''' - for VirtualT as this project would not have happened without it
'''Club 100 and Rick Hanson''' - for helping to get this gadget out there
and others for their helpful comments and support.

[[Category:Model T Hardware]]

Soon to be released REX Release 4.6

2010-06-14T02:48:53Z

209.195.69.117: /* REX Operation Overview */

== Supported Models ==
M100 and T102, with either REX or REX2.

== New Features ==
* Main ROM Replacement feature, allowing users to load and update the main system ROM
* ROM2/Cleuseau is now supported
* REX system information and acknowledgements display added
* Checksum added into TPDD routines
* Improved bank switching
* Stronger directory structure testing
* Minor changes to MENU controls
* More descriptive Help files

== Bug Fixes ==
* the 12 block limitation in Release 4.5 is resolved

== REX Operation Overview ==

'''RAM/ROM/OS Menu'''

REX is an option ROM switcher that also includes RAM backup and switching functions. REX manages RAM or ROM data in 32k blocks, refered to as images. Option ROMs may be loaded into REX images and selected for use, and your system RAM may be copied to or restored from REX images. Images are grouped by type (RAM/ROM/OS). SYS images are reserved for system use. Images may be 'Load'ed or 'Save'd to/from TPDD.

Filename extensions are
.BX is used for Option ROM images
.BY is used for RAM images
.BZ is used for OS images
.BR is used for REX system images

Images may be 'Name'd, 'Copy'd or 'Kill'ed. Up to 16 images of any one type are allowed, with 24 images in total. An Image is 'ACTIVE' when in use by REX, and is marked with a *. There must always be one active RAM and one active ROM or OS image. You cannot kill an active image. Active status is changed by selection of a new image using the <ent> key. OS images are option ROMs that act as independant operating systems.

Keyboard Commands

b Block number information
e Hints on <ENTER> key functions
i Information on REX system
c Checksum of menu entry image
s Toggle directory sort order
ent Take action for selection
tab Show directory for next image type
esc return to menu

Function Keys
F1 Display help screens
F2 Load/Save image from/to TPDD
F3 Copy image to REX
F4 Delete image from REX
F5 Rename the image
F6 Reserved for future function
F7 Deinstall REX software from laptop
F8 Exit REX Manager

'''SYS Menu'''

This menu is used to manage system related tasks, primarily management of the loaded main ROM images used when REX is replacing the internal ROMs. See the Wiki to learn the steps required to configure your laptop for ROM Replacement, and how to create ROM images that are compatible with REX. (ROMs require a small change so that REX can detect the hardware configuration.) REX Manager screens now indicate the status of the ROM Replacement function. In the top left corner there is a single highlighted character, one of (M, P, S). This character indicates which system ROM is in use - internal or REX based.

M - standard internal ROMs in use
P - Primary ROM (block 2)in use
S - Secondary ROM (block 4) in use

When the internal ROM is in use, REX cannot provide ROM Replacement. Primary or Secondary ROM images may be 'Load'ed via selection from menu. When the laptop is configured to provide the system ROM, the power-up default is to use the Primary ROM in block 2. It is a good idea to leave this block configured with the standard image. 'Use' command allows the user to select either Primary or Secondary ROMs for use. This selection is tracked in the active block directory, so that system state is always restored on power up. Timestamps are recorded also. Messages are shown above the entries to give some information about the block under the cursor.

Keyboard Commands
b Block number information
i Information on REX system
c Checksum of menu entry image
tab Show directory for next image type
esc return to menu
Function Keys
F1 Display help screens
F2 Load image from TPDD
F3 Select ROM image for use
F7 Deinstall REX software from laptop
F8 Exit REX Manager

== Upgrade Procedure ==
The upgrade procedure is quite simple. The upgrade package contains a program called REXU1.CO (the upgrader tool) and a 16k binary image of the new REX software load called REX146.BR.

The upgrade assumes you have a working REX or REX2 running software release 4.5. This is a mostly safe assumption, since all REX and REX2 to date have been only got Release 4.5.

The upgrade tool REXU1 runs in RAM and relies on a connected TPDD device to make the software upgrade image available.

'''Steps'''

1. Download the upgrade package, and place the 2 files in your favorite TPDD device or emulator so they are accessible. Upload the program REXU1.CO to the laptop.

2. Power up the laptop, start REX Manager, and de-install the REX software by pressing F7. Return to MENU.

3. Make sure that you CLEAR memory for REXU1.CO. From BASIC issue the command CLEAR0,60460. Return to MENU and run REXU1.CO.

4. The upgrade tool first allows the user to make a full system backup by indicating Y or N at the prompt. In REX, the system is a 32k binary image that includes your current software load, and your current directory. It is recommended that you save your existing image just to be safe. Keeping the system image allows you to revert to that if something unforseen happens during the upgrade. Provide a unique filename to safely identify the system image backup.

5. Proceed to upgrade the software image by indicating Y or N, or quit the application using Q or ESC. (N, Q and ESC are equivalent). Confirm your intention to upgrade the system by confirming with Y at the next prompt, or abandon using N. If you confirm the upgrade, the upgrade process will proceed by erasing the first 16k of the system image, containing the system software, and replacing it with the binary image REX146.BR stored on TPDD.

'''Be careful to keep the laptop powered up during the flash process!'''

6. Power cycle the laptop, and from BASIC issue the command CALL63012. This should start REX Manager again, and you should now be using release 4.6. You will observe that REX will notice the system upgrade, and will back up the software image to the backup block. This is normal and will happen only once.

'''DONE!'''

== REX Release 4.6 Upgrade Package ==

REX SYSTEM images contain the REX Manager software package, including the default directories, and are 32kbyte binary files. For M100/T102, images have filenames of REX1XX.BR, and T200 images have filenames of REX2XX.BR, where XX is the release number.

In the upgrade package, 16k system images with only the software are provided, because you will want to keep your directory data.

<table border="1">
<tr><td>Status</td><td>Release</td><td>Model</td><td>Description</td><td>File</td><td>Submitter / Date</td></tr>
<tr><td>GA</td><td>1.0</td><td>M100/T102</td><td>REX Upgrade Package</td><td>[[Media:REX_4.6_Upgrade.zip|REX_4.6_Upgrade.zip]]</td><td>[[User:Sadolph|Sadolph]] 13:06, 13 June 2010 (PDT)</td></tr>
</table>

== 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.

== Rel. 4.6 Known Issues ==
* Startup of REX Manager is slow. I will be making improvements in the next release.
* No ability to transfer files from stored RAM images is a pain. Look to the next release.

== Rel. 4.6 bug reports/work arounds ==

None yet!

== Enhancement Requests ==

<table border="1">
<tr><td>Status</td><td>Description</td><td>Requester / Date</td></tr>
<tr><td>Unknown</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>Unknown</td><td>Support import of file from frozen RAM image to the thawed RAM image. RAM images can be used in a way similar to subdirectories. Therefore it is useful to be able to retrieve files from frozen RAM images</td><td>[[User:Jhoger|Jhoger]] 08:16, 16 April 2009 (PDT)</td></tr>
<tr><td>unknown</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>
</table>

nb: to put a username+datestamp just type 4 tildes <nowiki>~~~~</nowiki>

Soon to be released REX Release 4.6

2010-06-14T02:47:49Z

209.195.69.117:

== Supported Models ==
M100 and T102, with either REX or REX2.

== New Features ==
* Main ROM Replacement feature, allowing users to load and update the main system ROM
* ROM2/Cleuseau is now supported
* REX system information and acknowledgements display added
* Checksum added into TPDD routines
* Improved bank switching
* Stronger directory structure testing
* Minor changes to MENU controls
* More descriptive Help files

== Bug Fixes ==
* the 12 block limitation in Release 4.5 is resolved

== REX Operation Overview ==

'''RAM/ROM/OS Menu'''

REX is an option ROM switcher that also includes RAM backup and switching functions. REX manages RAM or ROM data in 32k blocks, refered to as images. Option ROMs may be loaded into REX images and selected for use, and your system RAM may be copied to or restored from REX images. Images are grouped by type (RAM/ROM/OS). SYS images are reserved for system use. Images may be 'Load'ed or 'Save'd to/from TPDD.
Filename extensions are
.BX is used for Option ROM images
.BY is used for RAM images
.BZ is used for OS images
.BR is used for REX system images

Images may be 'Name'd, 'Copy'd or 'Kill'ed. Up to 16 images of any one type are allowed, with 24 images in total. An Image is 'ACTIVE' when in use by REX, and is marked with a *. There must always be one active RAM and one active ROM or OS image. You cannot kill an active image. Active status is changed by selection of a new image using the <ent> key. OS images are option ROMs that act as independant operating systems.

Keyboard Commands

b Block number information
e Hints on <ENTER> key functions
i Information on REX system
c Checksum of menu entry image
s Toggle directory sort order
ent Take action for selection
tab Show directory for next image type
esc return to menu

Function Keys
F1 Display help screens
F2 Load/Save image from/to TPDD
F3 Copy image to REX
F4 Delete image from REX
F5 Rename the image
F6 Reserved for future function
F7 Deinstall REX software from laptop
F8 Exit REX Manager

'''SYS Menu'''

This menu is used to manage system related tasks, primarily management of the loaded main ROM images used when REX is replacing the internal ROMs. See the Wiki to learn the steps required to configure your laptop for ROM Replacement, and how to create ROM images that are compatible with REX. (ROMs require a small change so that REX can detect the hardware configuration.) REX Manager screens now indicate the status of the ROM Replacement function. In the top left corner there is a single highlighted character, one of (M, P, S). This character indicates which system ROM is in use - internal or REX based.

M - standard internal ROMs in use
P - Primary ROM (block 2)in use
S - Secondary ROM (block 4) in use

When the internal ROM is in use, REX cannot provide ROM Replacement. Primary or Secondary ROM images may be 'Load'ed via selection from menu. When the laptop is configured to provide the system ROM, the power-up default is to use the Primary ROM in block 2. It is a good idea to leave this block configured with the standard image. 'Use' command allows the user to select either Primary or Secondary ROMs for use. This selection is tracked in the active block directory, so that system state is always restored on power up. Timestamps are recorded also. Messages are shown above the entries to give some information about the block under the cursor.

Keyboard Commands
b Block number information
i Information on REX system
c Checksum of menu entry image
tab Show directory for next image type
esc return to menu
Function Keys
F1 Display help screens
F2 Load image from TPDD
F3 Select ROM image for use
F7 Deinstall REX software from laptop
F8 Exit REX Manager

== Upgrade Procedure ==
The upgrade procedure is quite simple. The upgrade package contains a program called REXU1.CO (the upgrader tool) and a 16k binary image of the new REX software load called REX146.BR.

The upgrade assumes you have a working REX or REX2 running software release 4.5. This is a mostly safe assumption, since all REX and REX2 to date have been only got Release 4.5.

The upgrade tool REXU1 runs in RAM and relies on a connected TPDD device to make the software upgrade image available.

'''Steps'''

1. Download the upgrade package, and place the 2 files in your favorite TPDD device or emulator so they are accessible. Upload the program REXU1.CO to the laptop.

2. Power up the laptop, start REX Manager, and de-install the REX software by pressing F7. Return to MENU.

3. Make sure that you CLEAR memory for REXU1.CO. From BASIC issue the command CLEAR0,60460. Return to MENU and run REXU1.CO.

4. The upgrade tool first allows the user to make a full system backup by indicating Y or N at the prompt. In REX, the system is a 32k binary image that includes your current software load, and your current directory. It is recommended that you save your existing image just to be safe. Keeping the system image allows you to revert to that if something unforseen happens during the upgrade. Provide a unique filename to safely identify the system image backup.

5. Proceed to upgrade the software image by indicating Y or N, or quit the application using Q or ESC. (N, Q and ESC are equivalent). Confirm your intention to upgrade the system by confirming with Y at the next prompt, or abandon using N. If you confirm the upgrade, the upgrade process will proceed by erasing the first 16k of the system image, containing the system software, and replacing it with the binary image REX146.BR stored on TPDD.

'''Be careful to keep the laptop powered up during the flash process!'''

6. Power cycle the laptop, and from BASIC issue the command CALL63012. This should start REX Manager again, and you should now be using release 4.6. You will observe that REX will notice the system upgrade, and will back up the software image to the backup block. This is normal and will happen only once.

'''DONE!'''

== REX Release 4.6 Upgrade Package ==

REX SYSTEM images contain the REX Manager software package, including the default directories, and are 32kbyte binary files. For M100/T102, images have filenames of REX1XX.BR, and T200 images have filenames of REX2XX.BR, where XX is the release number.

In the upgrade package, 16k system images with only the software are provided, because you will want to keep your directory data.

<table border="1">
<tr><td>Status</td><td>Release</td><td>Model</td><td>Description</td><td>File</td><td>Submitter / Date</td></tr>
<tr><td>GA</td><td>1.0</td><td>M100/T102</td><td>REX Upgrade Package</td><td>[[Media:REX_4.6_Upgrade.zip|REX_4.6_Upgrade.zip]]</td><td>[[User:Sadolph|Sadolph]] 13:06, 13 June 2010 (PDT)</td></tr>
</table>

== 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.

== Rel. 4.6 Known Issues ==
* Startup of REX Manager is slow. I will be making improvements in the next release.
* No ability to transfer files from stored RAM images is a pain. Look to the next release.

== Rel. 4.6 bug reports/work arounds ==

None yet!

== Enhancement Requests ==

<table border="1">
<tr><td>Status</td><td>Description</td><td>Requester / Date</td></tr>
<tr><td>Unknown</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>Unknown</td><td>Support import of file from frozen RAM image to the thawed RAM image. RAM images can be used in a way similar to subdirectories. Therefore it is useful to be able to retrieve files from frozen RAM images</td><td>[[User:Jhoger|Jhoger]] 08:16, 16 April 2009 (PDT)</td></tr>
<tr><td>unknown</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>
</table>

nb: to put a username+datestamp just type 4 tildes <nowiki>~~~~</nowiki>

Soon to be released REX Release 4.6

2010-06-14T02:39:40Z

209.195.69.117:

== Supported Models ==
M100 and T102, with either REX or REX2.

== New Features ==
* Main ROM Replacement feature, allowing users to load and update the main system ROM
* ROM2/Cleuseau is now supported
* REX system information and acknowledgements display added
* Checksum added into TPDD routines
* Improved bank switching
* Stronger directory structure testing
* Minor changes to MENU controls
* More descriptive Help files

== Bug Fixes ==
* the 12 block limitation in Release 4.5 is resolved

== REX Operation Overview ==

REX is an option ROM switcher that also includes RAM backup and switching functions. REX manages RAM or ROM data in 32k blocks, refered to as images. Option ROMs may be loaded into REX images and selected for use, and your system RAM may be copied to or restored from REX images. Images are grouped by type (RAM/ROM/OS). SYS images are reserved for system use. Images may be 'Load'ed or 'Save'd to/from TPDD.
Filename extensions are
.BX is used for Option ROM images
.BY is used for RAM images
.BZ is used for OS images
.BR is used for REX system images

Images may be 'Name'd, 'Copy'd or 'Kill'ed. Up to 16 images of any one type are allowed, with 24 images in total. An Image is 'ACTIVE' when in use by REX, and is marked with a *. There must always be one active RAM and one active ROM or OS image. You cannot kill an active image. Active status is changed by selection of a new image using the <ent> key. OS images are option ROMs that act as independant operating systems.

Keyboard Commands
<b> Block number information
<e> Hints on <ENTER> key functions
<i> Information on REX system
<c> Checksum of menu entry image
<s> Toggle directory sort order
<ent> Take action for selection
<tab> Show directory for next image type
<esc> return to menu

Function Keys
<F1> Display help screens
<F2> Load/Save image from/to TPDD
<F3> Copy image to REX
<F4> Delete image from REX
<F5> Rename the image
<F6> Reserved for future function
<F7> Deinstall REX software from laptop
<F8> Exit REX Manager

This menu is used to manage system related tasks, primarily management of the loaded main ROM images used when REX is replacing the internal ROMs. See the Wiki to learn the steps required to configure your laptop for ROM Replacement, and how to create ROM images that are compatible with REX. (ROMs require a small change so that REX can detect the hardware configuration.) REX Manager screens now indicate the status of the ROM Replacement function. In the top left corner there is a single highlighted character, one of (M, P, S). This character indicates which system ROM is in use - internal or REX based.

M - standard internal ROMs in use
P - Primary ROM (block 2)in use
S - Secondary ROM (block 4) in use

When the internal ROM is in use, REX cannot provide ROM Replacement. Primary or Secondary ROM images may be 'Load'ed via selection from menu. When the laptop is configured to provide the system ROM, the power-up default is to use the Primary ROM in block 2. It is a good idea to leave this block configured with the standard image. 'Use' command allows the user to select either Primary or Secondary ROMs for use. This selection is tracked in the active block directory, so that system state is always restored on power up. Timestamps are recorded also. Messages are shown above the entries to give some information about the block under the cursor.

Keyboard Commands
<b> Block number information",0
<i> Information on REX system",0
<c> Checksum of menu entry image",0
<tab> Show directory for next image type",0
<esc> return to menu",0
Function Keys
<F1> Display help screens
<F2> Load image from TPDD
<F3> Select ROM image for use
<F7> Deinstall REX software from laptop
<F8> Exit REX Manager

== Upgrade Procedure ==
The upgrade procedure is quite simple. The upgrade package contains a program called REXU1.CO (the upgrader tool) and a 16k binary image of the new REX software load called REX146.BR.

The upgrade assumes you have a working REX or REX2 running software release 4.5. This is a mostly safe assumption, since all REX and REX2 to date have been only got Release 4.5.

The upgrade tool REXU1 runs in RAM and relies on a connected TPDD device to make the software upgrade image available.

'''Steps'''

1. Download the upgrade package, and place the 2 files in your favorite TPDD device or emulator so they are accessible. Upload the program REXU1.CO to the laptop.

2. Power up the laptop, start REX Manager, and de-install the REX software by pressing F7. Return to MENU.

3. Make sure that you CLEAR memory for REXU1.CO. From BASIC issue the command CLEAR0,60460. Return to MENU and run REXU1.CO.

4. The upgrade tool first allows the user to make a full system backup by indicating Y or N at the prompt. In REX, the system is a 32k binary image that includes your current software load, and your current directory. It is recommended that you save your existing image just to be safe. Keeping the system image allows you to revert to that if something unforseen happens during the upgrade. Provide a unique filename to safely identify the system image backup.

5. Proceed to upgrade the software image by indicating Y or N, or quit the application using Q or ESC. (N, Q and ESC are equivalent). Confirm your intention to upgrade the system by confirming with Y at the next prompt, or abandon using N. If you confirm the upgrade, the upgrade process will proceed by erasing the first 16k of the system image, containing the system software, and replacing it with the binary image REX146.BR stored on TPDD.

'''Be careful to keep the laptop powered up during the flash process!'''

6. Power cycle the laptop, and from BASIC issue the command CALL63012. This should start REX Manager again, and you should now be using release 4.6. You will observe that REX will notice the system upgrade, and will back up the software image to the backup block. This is normal and will happen only once.

'''DONE!'''

== REX Release 4.6 Upgrade Package ==

REX SYSTEM images contain the REX Manager software package, including the default directories, and are 32kbyte binary files. For M100/T102, images have filenames of REX1XX.BR, and T200 images have filenames of REX2XX.BR, where XX is the release number.

In the upgrade package, 16k system images with only the software are provided, because you will want to keep your directory data.

<table border="1">
<tr><td>Status</td><td>Release</td><td>Model</td><td>Description</td><td>File</td><td>Submitter / Date</td></tr>
<tr><td>GA</td><td>1.0</td><td>M100/T102</td><td>REX Upgrade Package</td><td>[[Media:REX_4.6_Upgrade.zip|REX_4.6_Upgrade.zip]]</td><td>[[User:Sadolph|Sadolph]] 13:06, 13 June 2010 (PDT)</td></tr>
</table>

== 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.

== Rel. 4.6 Known Issues ==
* Startup of REX Manager is slow. I will be making improvements in the next release.
* No ability to transfer files from stored RAM images is a pain. Look to the next release.

== Rel. 4.6 bug reports/work arounds ==

None yet!

== Enhancement Requests ==

<table border="1">
<tr><td>Status</td><td>Description</td><td>Requester / Date</td></tr>
<tr><td>Unknown</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>Unknown</td><td>Support import of file from frozen RAM image to the thawed RAM image. RAM images can be used in a way similar to subdirectories. Therefore it is useful to be able to retrieve files from frozen RAM images</td><td>[[User:Jhoger|Jhoger]] 08:16, 16 April 2009 (PDT)</td></tr>
<tr><td>unknown</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>
</table>

nb: to put a username+datestamp just type 4 tildes <nowiki>~~~~</nowiki>

REX

2010-06-14T02:02:44Z

209.195.69.117: /* For Owners */

Soon to be released REX Release 4.6

2010-06-14T01:58:57Z

209.195.69.117:

OPTROM Switching

2010-05-27T17:11:30Z

209.195.69.117:

Some time was spent in developing an improved method to call main ROM from option ROM, and to handle interrupts from within the optrom.

The goal was to
* use only the stack
* minimize code size
* reduce execution time

<code><pre>

OPON: .EQU 0FAA4H

;-----------------------------------------------------------------------
; ROM start
;-----------------------------------------------------------------------
.org 0000h

RST0: di
JMP program ; standard entry
.DB 0,0,0,0
RST1: RET
.DB 0,0,0,0,0,0,0
RST2: RET ;Not used
.DB 0,0,0,0,0,0,0
RST3: RET ;Not Used
.DB 0,0,0,0,0,0,0
RST4: RET ;Not Used
.DB 0,0,0
TRAP: DI
CALL INTCALL
RST5: RET ;Not Used
.DB 0,0,0
RST55: DI
CALL INTCALL
RST6: JMP STDCALL ;RST 6 used as short call to a Standard ROM routine.
.DB 0
RST65: DI ;Replaces the 6.5 interrupt and sets up a call to 6.5 in Standard ROM
CALL INTCALL
RST7: RET ;Not Used
.DB 0,0,0
RST75: DI ;Replaces the 7.5 interrupt and sets up a call to 7.5 in Standard ROM
CALL INTCALL

.org 0040h

OPON_img: ; auto copied on power up
; 8 bytes
PUSH PSW ; temp store psw
mvi a,01h
OUT 0E8H
pop psw
ret

.db 00h

.org 0048h

;---------------------------------------------------------
;The STDCALL routine allows a program running in the
;the Option ROM to call and return to an address in the
;Option ROM.
;Syntax is to use a RST 6 plus the address to be called.
;
; RST 6
; rvect--> DW 04B44H (cvect)
; pvect-->
;
;---------------------------------------------------------

STDCALL: ; 23 bytes
; stack = rvect
xthl
inx h
inx h
xthl ; fix up first stack entry
; stack = pvect
; hl=hl'

push h
lxi h, OPON
xthl ; stack = pvect, OPON
; hl=hl'

push h
push d ; stack = pvect, OPON, hl', de'

ldsi 06h ; point de to stack location of return vector

lhlx ; hl=pvect
dcx h
dcx h ; point hl=pvect-2
xchg ; de=pvect-2
lhlx ; hl=cvect

pop d ; de=de'
xthl ; hl=hl', stack= pvect, OPON, cvect

jmp STDON

;---------------------------------------------------------
;Routine for the hardware traps.
;return address on entry is related to which interrupt occured.
;
; after interrupt occurs
; ivect DI
; call INTCALL
; rvect -->
; so stack = pvect, rvect
;---------------------------------------------------------

INTCALL: ; final stack must be opon, introutine
; interrupts are off
; enter with return location on stack, indicating int routine
; stack = pvect, rvect
; 20 bytes
push h
push d ; stack = pvect, rvect, hl', de'

ldsi 04h

lhlx ; hl= rvect

dcx h
dcx h
dcx h
dcx h ; hl = ivect

push h ; stack = pvect, rvect, hl', de', ivect

lxi h,OPON
shlx ; stack = pvect, OPON, hl', de', ivect

pop h ; hl=ivect
pop d ; de=de'

xthl ; stack = pvect, OPON, ivect
; hl=hl', de=de'

jmp STDON

;---------------------------------------------------------
;OPEXIT/STDON: Turns off the Option ROM (or turns on Standard ROM)
;---------------------------------------------------------
.org 0085h

STDON:
PUSH PSW
PUSH H ; 26C8, F1 C9 POP PSW, RET
LXI H,26C8H ; it returns to this location --> pop psw; ret
XTHL

OPEXIT: ; return to location pushed on stack
xra a
OUT 0E8H
RET ; RET can be found at 008EH in stdrom
; in both M100 and T200

EXIT:
.org 00094H
pop h
lxi h,0000h
xthl ; restart

jmp OPEXIT

</pre></code>

[[Media:demo.zip|Demo program for an option rom]]

Note that in some instances one might need to use the data stored in FF45 to preseve the state of thinks like the cassette relay. In that case, it is relatively simple to extend this to cover FF45 support properly.

OPTROM Switching

2010-05-27T17:07:50Z

209.195.69.117:

Some time was spent in developing an improved method to call main ROM from option ROM, and to handle interrupts from within the optrom.

The goal was to
* use only the stack
* minimize code size
* reduce execution time

OPON: .EQU 0FAA4H

;-----------------------------------------------------------------------
; ROM start
;-----------------------------------------------------------------------
.org 0000h

RST0: di
JMP program ; standard entry
.DB 0,0,0,0
RST1: RET
.DB 0,0,0,0,0,0,0
RST2: RET ;Not used
.DB 0,0,0,0,0,0,0
RST3: RET ;Not Used
.DB 0,0,0,0,0,0,0
RST4: RET ;Not Used
.DB 0,0,0
TRAP: DI
CALL INTCALL
RST5: RET ;Not Used
.DB 0,0,0
RST55: DI
CALL INTCALL
RST6: JMP STDCALL ;RST 6 used as short call to a Standard ROM routine.
.DB 0
RST65: DI ;Replaces the 6.5 interrupt and sets up a call to 6.5 in Standard ROM
CALL INTCALL
RST7: RET ;Not Used
.DB 0,0,0
RST75: DI ;Replaces the 7.5 interrupt and sets up a call to 7.5 in Standard ROM
CALL INTCALL

.org 0040h

OPON_img: ; auto copied on power up
; 8 bytes
PUSH PSW ; temp store psw
mvi a,01h
OUT 0E8H
pop psw
ret

.db 00h

.org 0048h

;---------------------------------------------------------
;The STDCALL routine allows a program running in the
;the Option ROM to call and return to an address in the
;Option ROM.
;Syntax is to use a RST 6 plus the address to be called.
;
; RST 6
; rvect--> DW 04B44H (cvect)
; pvect-->
;
;---------------------------------------------------------

STDCALL: ; 23 bytes
; stack = rvect
xthl
inx h
inx h
xthl ; fix up first stack entry
; stack = pvect
; hl=hl'

push h
lxi h, OPON
xthl ; stack = pvect, OPON
; hl=hl'

push h
push d ; stack = pvect, OPON, hl', de'

ldsi 06h ; point de to stack location of return vector

lhlx ; hl=pvect
dcx h
dcx h ; point hl=pvect-2
xchg ; de=pvect-2
lhlx ; hl=cvect

pop d ; de=de'
xthl ; hl=hl', stack= pvect, OPON, cvect

jmp STDON

;---------------------------------------------------------
;Routine for the hardware traps.
;return address on entry is related to which interrupt occured.
;
; after interrupt occurs
; ivect DI
; call INTCALL
; rvect -->
; so stack = pvect, rvect
;---------------------------------------------------------

INTCALL: ; final stack must be opon, introutine
; interrupts are off
; enter with return location on stack, indicating int routine
; stack = pvect, rvect
; 20 bytes
push h
push d ; stack = pvect, rvect, hl', de'

ldsi 04h

lhlx ; hl= rvect

dcx h
dcx h
dcx h
dcx h ; hl = ivect

push h ; stack = pvect, rvect, hl', de', ivect

lxi h,OPON
shlx ; stack = pvect, OPON, hl', de', ivect

pop h ; hl=ivect
pop d ; de=de'

xthl ; stack = pvect, OPON, ivect
; hl=hl', de=de'

jmp STDON

;---------------------------------------------------------
;OPEXIT/STDON: Turns off the Option ROM (or turns on Standard ROM)
;---------------------------------------------------------
.org 0085h

STDON:
PUSH PSW
PUSH H ; 26C8, F1 C9 POP PSW, RET
LXI H,26C8H ; it returns to this location --> pop psw; ret
XTHL

OPEXIT: ; return to location pushed on stack
xra a
OUT 0E8H
RET ; RET can be found at 008EH in stdrom
; in both M100 and T200

EXIT:
.org 00094H
pop h
lxi h,0000h
xthl ; restart

jmp OPEXIT

OPTROM Switching

2010-05-27T17:07:16Z

209.195.69.117: New page: Some time was spent in developing an improved method to call main ROM from option ROM, and to handle interrupts from within the optrom. The goal was to * use only the stack * minimize co...

Some time was spent in developing an improved method to call main ROM from option ROM, and to handle interrupts from within the optrom.

The goal was to
* use only the stack
* minimize code size
* reduce execution time

<nowiki>

OPON: .EQU 0FAA4H

;-----------------------------------------------------------------------
; ROM start
;-----------------------------------------------------------------------
.org 0000h

RST0: di
JMP program ; standard entry
.DB 0,0,0,0
RST1: RET
.DB 0,0,0,0,0,0,0
RST2: RET ;Not used
.DB 0,0,0,0,0,0,0
RST3: RET ;Not Used
.DB 0,0,0,0,0,0,0
RST4: RET ;Not Used
.DB 0,0,0
TRAP: DI
CALL INTCALL
RST5: RET ;Not Used
.DB 0,0,0
RST55: DI
CALL INTCALL
RST6: JMP STDCALL ;RST 6 used as short call to a Standard ROM routine.
.DB 0
RST65: DI ;Replaces the 6.5 interrupt and sets up a call to 6.5 in Standard ROM
CALL INTCALL
RST7: RET ;Not Used
.DB 0,0,0
RST75: DI ;Replaces the 7.5 interrupt and sets up a call to 7.5 in Standard ROM
CALL INTCALL

.org 0040h

OPON_img: ; auto copied on power up
; 8 bytes
PUSH PSW ; temp store psw
mvi a,01h
OUT 0E8H
pop psw
ret

.db 00h

.org 0048h

;---------------------------------------------------------
;The STDCALL routine allows a program running in the
;the Option ROM to call and return to an address in the
;Option ROM.
;Syntax is to use a RST 6 plus the address to be called.
;
; RST 6
; rvect--> DW 04B44H (cvect)
; pvect-->
;
;---------------------------------------------------------

STDCALL: ; 23 bytes
; stack = rvect
xthl
inx h
inx h
xthl ; fix up first stack entry
; stack = pvect
; hl=hl'

push h
lxi h, OPON
xthl ; stack = pvect, OPON
; hl=hl'

push h
push d ; stack = pvect, OPON, hl', de'

ldsi 06h ; point de to stack location of return vector

lhlx ; hl=pvect
dcx h
dcx h ; point hl=pvect-2
xchg ; de=pvect-2
lhlx ; hl=cvect

pop d ; de=de'
xthl ; hl=hl', stack= pvect, OPON, cvect

jmp STDON

;---------------------------------------------------------
;Routine for the hardware traps.
;return address on entry is related to which interrupt occured.
;
; after interrupt occurs
; ivect DI
; call INTCALL
; rvect -->
; so stack = pvect, rvect
;---------------------------------------------------------

INTCALL: ; final stack must be opon, introutine
; interrupts are off
; enter with return location on stack, indicating int routine
; stack = pvect, rvect
; 20 bytes
push h
push d ; stack = pvect, rvect, hl', de'

ldsi 04h

lhlx ; hl= rvect

dcx h
dcx h
dcx h
dcx h ; hl = ivect

push h ; stack = pvect, rvect, hl', de', ivect

lxi h,OPON
shlx ; stack = pvect, OPON, hl', de', ivect

pop h ; hl=ivect
pop d ; de=de'

xthl ; stack = pvect, OPON, ivect
; hl=hl', de=de'

jmp STDON

;---------------------------------------------------------
;OPEXIT/STDON: Turns off the Option ROM (or turns on Standard ROM)
;---------------------------------------------------------
.org 0085h

STDON:
PUSH PSW
PUSH H ; 26C8, F1 C9 POP PSW, RET
LXI H,26C8H ; it returns to this location --> pop psw; ret
XTHL

OPEXIT: ; return to location pushed on stack
xra a
OUT 0E8H
RET ; RET can be found at 008EH in stdrom
; in both M100 and T200

EXIT:
.org 00094H
pop h
lxi h,0000h
xthl ; restart

jmp OPEXIT

</nowiki>

Model T DocGarden

2010-05-27T16:59:51Z

209.195.69.117:

These pages are devoted to the Model T:

TRS-80 Model 100, Tandy Model 102, KC-85, NEC 8201A, NEC 8300, Olivetti M10, Tandy Model 200, and the WP-2

== Community ==

The community gathers at [[Club 100|Club100.org]]

== Classic Article Repubs ==

We hope to republish one or more articles from the Golden Era of the Model T every month:

<DPL>
category=Model 100 Classics
</DPL>

== One-Liners ==

This is a collection of Microsoft BASIC programs that
* Do something interesting or useful
* With only a single line of code

One-liners are bite-sized computer programs on a human scale. You are encouraged to type them in manually (by hand) and study their operation.

[[Model 100/102 Compatible One-Liners]]

== File-Transfer and Storage ==

We still use Model Ts today, so file transfer to/from desktop and modern laptops is an important issue. There are multiple alternatives, from simple text file transfers using TEXT, TELCOM, or BASIC, up to dedicated file transfer protocol client and servers.

[[Model T File Transfer]]

== Model T Developer Reference ==

Articles on Model T programming topics

<DPL>
category=Model T Developer Reference
columns=3
</DPL>

== Model T Software ==

<DPL>
category=Model T Software
</DPL>

== Model T Hardware Hacks and Troubleshooting ==
<DPL>
category=Model T Hardware Hacking
</DPL>

== Model T Hardware Projects ==

<DPL>
category=Model T Hardware
columns=3
</DPL>

[[Remem]] is the ultimate Model T memory upgrade

[[REX]] is a flash OptROM emulator/switcher

[[NADSBox]] is a stand-alone TPDD emulation device that uses SD cards

[[Mikrokolor]] Is a Color Graphics interface for the Model 100. Allows for 40x80 character graphics/text

[[MTHD]] Is a how to add a Harddrive to your Model T

== Other Topics ==

[[OPTROM Switching]] discussion on code used to bank switch main ROM and option ROM

== Model T Links ==

[http://club100.org Rick Hanson's Club 100]

[http://www.istop.com/%7Esadolph/remem_home.html Steve Adolph's Remem Site]

[http://sliderule.mraiow.com/wiki/Portable_Computer_Index#T Chris Osburn's Calculating Instruments]

[http://kenpettit.com/projects.html Ken Pettit's Model T Projects]