Geneve drive remapping
REMAP
REMAP allows a disk I/O device to be mapped to any DSK1...DSK9 device number. Usage is as follows either in an AUTOEXEC file or at the GeneveOS Command Line prompt.
REMAP <number><DRIVE>
| A | Floppy #1 | Any floppy-only controller |
| B | Floppy #2 | Any floppy-only controller |
| C | Floppy #3 | Any floppy-only controller |
| D | Floppy #4 | Any floppy-only controller that supports 4 floppies |
| E | Internal Geneve Ramdisk | |
| F | Internal Horizon Ramdisk | 8 bit CRU >1400 256K |
| G | Internal Horizon Ramdisk | 8 bit CRU >1600 256K |
| H | Internal Rave Ramdisk | |
| I | HFDC Emulate File | |
| J | HFDC Floppy #1 | |
| K | HFDC Floppy #2 | |
| L | HFDC Floppy #3 | |
| M | HFDC Floppy #4 | |
| N | Internal Horizon Ramdisk | 16 bit CRU >1400 |
| O | Internal Horizon Ramdisk | 16 bit CRU >1600 |
| P | Internal Horizon Ramdisk | 16 bit CRU >1000 |
| Q | Internal Horizon Ramdisk | 16 bit CRU >1700 |
| R | Internal Horizon Ramdisk | 16 bit CRU >1800 |
| S | Internal Horizon Ramdisk | 16 bit CRU >1900 |
| T | PFM FlashDisk #1 | |
| U | Reserved for PFM #2 | |
| V | Reserved for Future Expansion | |
| W | TIPI DSK1 | TIPI CRU >1800 |
| X | TIPI DSK2 | TIPI CRU >1800 |
| Y | TIPI DSK3 | TIPI CRU >1800 |
| Z | TIPI DSK4 | TIPI CRU >1800 |
Examples
REMAP 1W Maps DSK1 to TIPI DSK1 (assumes PI.CONFIG has entry) REMAP 4Q Maps DSK4 to a 16 bit HRD at CRU >1700
(taken from the GeneveOS 7.30 manual)
SCSMAP
The SCSMAP command allows the use of SCS1 through SCS6 for devices.
SCSMAP also allows mapping the IDE drives to a SCS device name as
SCSMAP <x><y>
where x=1 to 6 for SCS1 to SCS6, and y=1 to 9 for SCSI connected devices 1 through 9.
To separate the IDE class of drives, the IDE drives have been set as
y=A to H where A=IDE1, B=IDE2, C=IDE3, D=IDE4, E=IDE5, F=IDE6, G=IDE7, and H=IDE8.
Please note that if you have partitioned your IDE drive to 8 partitions, our testing has indicated the 8th partition is presently not useable. We suspect this is a eprom programming issue that needs to be resolved. The IDE card needs to be running the DSR from Fred Kaal at www.ti99-geek.nl, Version 14.
The SCSMAP also allows mapping 16-bit Horizon Ramdisks into the SCSx "RamHardDrive" addressing. See identifiers below.
Please note, SCSI and IDE have more devices than the SCSMAP will presently allow. Plan drive size and mapping accordingly to maximize your equipment configuration.
Here are the default drive mappings:
| SCSMAP 11 | SCSI Device #1 to SCS1. |
| SCSMAP 22 | SCSI Device #2 to SCS2. |
| SCSMAP 33 | SCSI Device #3 to SCS3. |
| SCSMAP 48 | HRD Ramdrive CRU >1400 to SCS4. |
| SCSMAP 59 | HRD Ramdrive CRU >1600 to SCS5. |
| SCSMAP 6A | IDE 1st Drive, 1st Partition to SCS6 |
As an example, SCSx. may be reconfigured as follows:
| SCSMAP 12 | SCSI Device #2 to SCS1. |
| SCSMAP 26 | SCSI Device #6 to SCS2. |
In addition, IDE drives and the Horizon Ramdisk when configured as a RAM Harddrive are also mapped as a SCSI device as follows:
| SCSMAP 48 | Maps a Horizon Ramdisk at CRU >1400 to SCS4. |
| SCSMAP 39 | Maps a Horizon Ramdisk at CRU >1600 to SCS3. |
| SCSMAP 37 | Maps IDE Device #1 to SCS3 (special case mapping) |
| SCSMAP 1A | Maps IDE Device #1 to SCS1. |
| SCSMAP 6H | Maps IDE Device #8 (H) to SCS6. |
| Drive assignment | Device |
|---|---|
| 1 | SCSI Device #1 |
| 2 | SCSI Device #2 |
| 3 | SCSI Device #3 |
| 4 | SCSI Device #4 |
| 5 | SCSI Device #5 |
| 6 | SCSI Device #6 |
| 7 | IDE Device #1 |
| 8 | HRD CRU >1400 ramdisk |
| 9 | HRD CRU >1600 ramdisk |
| A | IDE Device #1 |
| B | IDE Device #2 |
| C | IDE Device #3 |
| D | IDE Device #4 |
| E | IDE Device #5 |
| F | IDE Device #6 |
| G | IDE Device #7 |
| H | IDE Device #8 |
It should be noted that Drive Assignment Device "7" is also duplicated as Drive Assignement Device "A".
As of 3 April 2021, testing of the IDE support in MAME has shown a potential issue of being unable to use IDE Device #8 if a user has partitioned both drives into 4 partitions each. This is unrelated to GeneveOS as it has been confirmed in the TI-99/4A emulation as well within MAME. The developer of the DSR has been contacted for investigation.