Model T Option ROMs: Difference between revisions
From Bitchin100 DocGarden
Jump to navigationJump to search
(→Notes) |
(→Notes) |
||
Line 39: | Line 39: | ||
Logit100 call 63012 call 61167,2 poke 63911,1:exec 62394 | Logit100 call 63012 call 61167,2 poke 63911,1:exec 62394 | ||
</pre> | </pre> | ||
from Steve A. | |||
De-installation of TS-DOS may require some detailed investigation, since | |||
the full effects of DOS-ON/OFF toggling from the menu are not understood. | |||
TS-DOS injects software into upper memory of the laptop, and modifies hooks. | |||
How this code interacts with M100 is not 100% clear. | |||
For example, do we need to clear all upper ram back to defaults, and restore | |||
the hooks to defaults? What areas of ram are modified? | |||
If the work to de-install was limited to this, then the default upper ram | |||
image would have to be copied from the main rom back into upper RAM. | |||
[[Category:Option ROM]] | [[Category:Option ROM]] |
Revision as of 03:34, 20 March 2009
This page is intended to be a database of all known Option ROMs that were/are commercially available, including version numbers.
Add a new table entry for each unique ROM image. That is, if you have two option ROMS, and they differ by more than one byte value, they should have separate entries. I am assuming ROMs were not "serialized" by embedding a serial number or customer name within each one, though it is conceivable.
Name | Target | Version | Description | Install | Uninstall | Image File |
TS-DOS | Model 100 | 4.0 | TPDD file manipulation BASIC DOS extensions | CALL 63013,0 | DOS-OFF (change BASIC vectors back to RET) Delete trigger file | Not uploaded |
TS-DOS | Model 200 | 4.0 | TPDD file manipulation BASIC DOS extensions | CALL 61167,2 | DOS-OFF (change BASIC vectors back to RET) Delete trigger file | Not uploaded |
Ultimate ROM II | Model 100 | TBD | TBD | CALL 63013,1 | TBD | Not uploaded |
Ultimate ROM II | Model 200 | TBD | TBD | CALL 61167,2 | TBD | Not uploaded |
Use Special:Upload to upload image files (perferably, as a raw 32K .BIN file, not hex, so we get a uniform set.
Notes
From Rick at Club 100:
Traveling Software, offered by Club 100: A Model 100 User Group TS-DOS call 63013,1 call 61167,2 poke 63911,1:exec 62394 CSR (1) call 63013,0 call 921,146 poke 63911,146:exec 1124 UR2 call 63013,1 call 61167,2 poke 63911,1:exec 62394 Sardine call 63013,1 call 61167,2 poke 63911,1:exec 62394 ROM2/Cleuseau call 63012 call 61167,2 poke 63911,1:exec 62394 Card File call 63012 call 61167,2 poke 63911,1:exec 62394 TS-Random call 63013,1 call 61167,2 poke 63911,1:exec 62394 Portable Computer Support Group, offered by Tri-Mike Network East SuperROM call 63012 call 61167,2 poke 63911,1:exec 62394 Lucid call 63012 call 61167,2 poke 63911,1:exec 62394 Bus Analyst call 63012 call 61167,2 poke 63911,1:exec 62394 RAMPlus call 63012 call 61167,2 poke 63911,1:exec 62394 Tandy/Radio Shack, offered by Club 100: A Model 100 User Group Int Solutions call 63012 call 61167,2 poke 63911,1:exec 62394 Multiplan call 63012 call 61167,2 poke 63911,1:exec 62394 Others, where-is, as-is Logit100 call 63012 call 61167,2 poke 63911,1:exec 62394
from Steve A.
De-installation of TS-DOS may require some detailed investigation, since the full effects of DOS-ON/OFF toggling from the menu are not understood. TS-DOS injects software into upper memory of the laptop, and modifies hooks. How this code interacts with M100 is not 100% clear. For example, do we need to clear all upper ram back to defaults, and restore the hooks to defaults? What areas of ram are modified? If the work to de-install was limited to this, then the default upper ram image would have to be copied from the main rom back into upper RAM.