RLV12 V2.0 Create SD-Card
SD-Card
Before you can use an SD-Card you need to format it. In this description I will be using macOS. Be warned this will delete all files on the SD-Card. Always make sure that you check the device id or disk number of the SD-Card you want to format.
In my example the SD-Card is in /dev/disk3
Format the SD-Card
When you have inserted the SD-Card you must first unmount all volumes that are mounted on this SD-Card. Then you partition the SD-Card using a MBR partitioning scheme. In the example I will have a total of 9 partitions.
The first 8 partitions will be created with a size of a RL02 which is exactly 20480 blocks. I will format each of the partition as a “FAT12” volume and give them volume names DL0, DL1, etc., the names are not important, but help to identify the partitions.
For a partition to be usable as disk image by the RLV12 emulator it has to be of type “Linux” and it has to have the exact size of a RL01 or RL02 volume. However many operating system are not able to create a partitions of type “Linux”. Therefore I have taken “FAT12” as the starting type. You will see later how we can change the partition type using the user interface of the RLV12 emulator.
The 9th partition I create is of type “MS-DOS” which is equivalent to the standard used by Windows for the remaining partition size. Here you can later place disk images that you can individually attach to one of the 4 units. Typically this will be a FAT-32 partition. Make sure it will not be exFAT as this is not supported by the RLV12 emulator.
The use of partitions to store the disk immages for RL01 or RL02 drive is optional. The advantage of parititions is that they will be automatially mapped to the units. The Emulator supports a maximum of 8 disk image partitions. Of course only the first for partitiosn of type Linux will be mapped to units, the RLV12 controller only supports 4 disk drives. Also if you create less than 4 disk image partitions only as many units will be mapped to parition and the other units will be marked offline by the controller. You can however map manually disk images to the additional units via the command line interfaces and the units will then be put online.
If there is a FAT-16 or FAT-32 partition on the SD-Card this partition will be recognized as storage for disk images. Disk images are just files that are copie of RL01 or RL02 disk images and are of course required to be the exact size of the disk to be emulated. A small set of commands allows the user to display the files and directories on the FAT partition and to map disk image files to units.
Previously the disk image partitions was the only way to have units mapped
automatically at startup, therefore partitions where required when you wanted
your system to be automatically read for use without using the command line
interface to map disk image files to units. In the meantime there is an
automount feature where the RLV12 Emulator tries to find and read a file named
RLV12.INI
in the root directory and will execute each line as a command as if
it was entered using the serial interface. Most notably the attach command can
be used to automatically map disk image files to units. Note that when the
RLV12 Emulator finds a RVL12.INI
file it will not automatically map disk
image partitions to disk units. Of course you can still attach a disk image
partition to a unit using the appropriate command in the RLV12.INI
file.
The following shows how to prepare an SD-Card with the maximum number
of disk image partitions and an additional FAT partition.
Note the very long command line using diskutil
to partition the disk.
diskutil partitionDisk /dev/disk3 9 MBR "MS-DOS FAT12" DL0 20480S "MS-DOS FAT12" DL1 20480S "MS-DOS FAT12" DL2 20480S "MS-DOS FAT12" DL3 20480S "MS-DOS FAT12" DL4 20480S "MS-DOS FAT12" DL5 20480S "MS-DOS FAT12" DL6 20480S "MS-DOS FAT12" DL7 20480S "MS-DOS" FILES R
Peters-Mini:v2 peter$ diskutil unmountdisk /dev/disk3
Unmount of all volumes on disk3 was successful
Peters-Mini:v2 peter$ diskutil partitionDisk /dev/disk3 9 MBR "MS-DOS FAT12" DL0 20480S "MS-DOS FAT12" DL1 20480S "MS-DOS FAT12" DL2 20480S "MS-DOS FAT12" DL3 20480S "MS-DOS FAT12" DL4 20480S "MS-DOS FAT12" DL5 20480S "MS-DOS FAT12" DL6 20480S "MS-DOS FAT12" DL7 20480S "MS-DOS" FILES R
Started partitioning on disk3
$<3>Unmounting disk
$<3>Creating the partition map
$<3>Waiting for partitions to activate
$<3>Formatting disk3s1 as MS-DOS (FAT12) with name DL0
$<3>512 bytes per physical sector
/dev/rdisk3s1: 20424 sectors in 2553 FAT12 clusters (4096 bytes/cluster)
bps=512 spc=8 res=1 nft=2 rde=512 sec=20480 mid=0xf8 spf=8 spt=32 hds=16 hid=63 drv=0x80
$<3>Mounting disk
$<3>Formatting disk3s2 as MS-DOS (FAT12) with name DL1
$<3>512 bytes per physical sector
/dev/rdisk3s2: 20424 sectors in 2553 FAT12 clusters (4096 bytes/cluster)
bps=512 spc=8 res=1 nft=2 rde=512 sec=20480 mid=0xf8 spf=8 spt=32 hds=16 hid=20601 drv=0x80
$<3>Mounting disk
$<3>Formatting disk3s3 as MS-DOS (FAT12) with name DL2
$<3>512 bytes per physical sector
/dev/rdisk3s3: 20424 sectors in 2553 FAT12 clusters (4096 bytes/cluster)
bps=512 spc=8 res=1 nft=2 rde=512 sec=20480 mid=0xf8 spf=8 spt=32 hds=16 hid=41139 drv=0x80
$<3>Mounting disk
$<3>Formatting disk3s5 as MS-DOS (FAT12) with name DL3
$<3>512 bytes per physical sector
/dev/rdisk3s5: 20424 sectors in 2553 FAT12 clusters (4096 bytes/cluster)
bps=512 spc=8 res=1 nft=2 rde=512 sec=20480 mid=0xf8 spf=8 spt=32 hds=16 hid=61677 drv=0x80
$<3>Mounting disk
$<3>Formatting disk3s6 as MS-DOS (FAT12) with name DL4
$<3>512 bytes per physical sector
/dev/rdisk3s6: 20424 sectors in 2553 FAT12 clusters (4096 bytes/cluster)
bps=512 spc=8 res=1 nft=2 rde=512 sec=20480 mid=0xf8 spf=8 spt=32 hds=16 hid=82215 drv=0x80
$<3>Mounting disk
$<3>Formatting disk3s7 as MS-DOS (FAT12) with name DL5
$<3>512 bytes per physical sector
/dev/rdisk3s7: 20424 sectors in 2553 FAT12 clusters (4096 bytes/cluster)
bps=512 spc=8 res=1 nft=2 rde=512 sec=20480 mid=0xf8 spf=8 spt=32 hds=16 hid=102753 drv=0x80
$<3>Mounting disk
$<3>Formatting disk3s8 as MS-DOS (FAT12) with name DL6
$<3>512 bytes per physical sector
/dev/rdisk3s8: 20424 sectors in 2553 FAT12 clusters (4096 bytes/cluster)
bps=512 spc=8 res=1 nft=2 rde=512 sec=20480 mid=0xf8 spf=8 spt=32 hds=16 hid=123291 drv=0x80
$<3>Mounting disk
$<3>Formatting disk3s9 as MS-DOS (FAT12) with name DL7
$<3>512 bytes per physical sector
/dev/rdisk3s9: 20424 sectors in 2553 FAT12 clusters (4096 bytes/cluster)
bps=512 spc=8 res=1 nft=2 rde=512 sec=20480 mid=0xf8 spf=8 spt=32 hds=16 hid=143829 drv=0x80
$<3>Mounting disk
$<3>Formatting disk3s10 as MS-DOS (FAT) with name FILES
$<3>512 bytes per physical sector
/dev/rdisk3s10: 826112 sectors in 51632 FAT16 clusters (8192 bytes/cluster)
bps=512 spc=16 res=1 nft=2 rde=512 mid=0xf8 spf=202 spt=32 hds=54 hid=164367 drv=0x80 bsec=826560
$<3>Mounting disk
$<3>Finished partitioning on disk3
/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *507.4 MB disk3
1: DOS_FAT_12 DL0 10.5 MB disk3s1
2: DOS_FAT_12 DL1 10.5 MB disk3s2
3: DOS_FAT_12 DL2 10.5 MB disk3s3
4: DOS_FAT_12 DL3 10.5 MB disk3s5
5: DOS_FAT_12 DL4 10.5 MB disk3s6
6: DOS_FAT_12 DL5 10.5 MB disk3s7
7: DOS_FAT_12 DL6 10.5 MB disk3s8
8: DOS_FAT_12 DL7 10.5 MB disk3s9
9: DOS_FAT_32 FILES 423.2 MB disk3s10
Peters-Mini:v2 peter$
For your reference you should list the partition table information using fdisk
before you eject the SD-Card from the computer.
Peters-Mini:v2 peter$ sudo fdisk /dev/disk3
Password:
Disk: /dev/disk3 geometry: 983/16/63 [990976 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 01 0 1 1 - 1023 254 63 [ 63 - 20480] DOS FAT-12
2: 01 1023 254 63 - 1023 254 63 [ 20601 - 20480] DOS FAT-12
3: 01 1023 254 63 - 1023 254 63 [ 41139 - 20480] DOS FAT-12
4: 05 1023 254 63 - 1023 254 63 [ 61619 - 929308] Extended DOS
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 01 1023 254 63 - 1023 254 63 [ 61677 - 20480] DOS FAT-12
2: 05 1023 254 63 - 1023 254 63 [ 82157 - 908770] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 01 1023 254 63 - 1023 254 63 [ 82215 - 20480] DOS FAT-12
2: 05 1023 254 63 - 1023 254 63 [ 102695 - 888232] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 01 1023 254 63 - 1023 254 63 [ 102753 - 20480] DOS FAT-12
2: 05 1023 254 63 - 1023 254 63 [ 123233 - 867694] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 01 1023 254 63 - 1023 254 63 [ 123291 - 20480] DOS FAT-12
2: 05 1023 254 63 - 1023 254 63 [ 143771 - 847156] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 01 1023 254 63 - 1023 254 63 [ 143829 - 20480] DOS FAT-12
2: 05 1023 254 63 - 1023 254 63 [ 164309 - 826618] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 0B 1023 254 63 - 1023 254 63 [ 164367 - 826560] Win95 FAT-32
2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Peters-Mini:v2 peter$ diskutil eject /dev/disk3
Disk /dev/disk3 ejected
Peters-Mini:v2 peter$
Next you insert the newly formatted SD-Card into the RLV12 Emulator. You need
to connect via a terminal emulation to the RLV12 Emulator using a USB to TTL-Serial
adapter. The default settings for the serial port are 115200baud, 8 bits per character
no parity and one stop-bit. Make sure you get a proper >
prompt.
>
SD Card inserted
-> automount
Set SPI Mode:01 Counts:01
Interface Condition Read:0x0580FF8000
Initialise Card RC:0x00, # of tries:0x37
Operation Condition Reg.:0x0580FF8000FF SD_Status:0x05
Set Block Length RC:00
Primary Extended Partition............:0000F0B3
Next Extended Partition Startsector...:0000F0B3
Next Extended Partition Startsector...:000140ED
Next Extended Partition Startsector...:00019127
Next Extended Partition Startsector...:0001E161
Next Extended Partition Startsector...:0002319B
Next Extended Partition Startsector...:000281D5
Status................................:03
Partition start.......................:0002820F
Sectors before this partition.........:0002820F
Number of FATs........................:02
Sectors per FAT.......................:000000CA
Sectors per cluster...................:10
Bytes per sector......................:0200
Reserved sectors......................:0001
1st FAT starts at sector..............:00028210
Data starts at sector.................:000283C4
FAT16 Volume with root dir sectors....:20
The root dir starts at sector.........:000283A4
Success!
The RLV12 Emulator will list the partitions found. You can verify that you
can read the SD-Card by using the DIR
command. This should display the root
directory of the first MS-DOS partition.
>dir
Show Dir:0x00000000
A C:0000 <Volume> FILES
H C:0002 <DIR> SPOTLI~1 .Spotlight-V100
H C:000B <DIR> FSEVEN~1 .fseventsd
>
Starting with Version 2.2 of the firmware, partitions can be changed individually
using a new command in the CLI. This firmware will also list partitions of type
MS-DOS FAT12 as a valid parition if it is of the exact size of a RL01/02 disk
cartridge. It will however be marked as idle. A new command activate
has
been added that will change the partition type of MS-DOS FAT 12 to Linux.
Note in the example above the first 5 partitions have already been activated and
are attached to the first 4 units. The 5th partition is not attached and the
next three partitions are marked as idle.
>show part
Partition 01 (pcb:0x2FF2) starting at sector 0x0000003F MBR at 0x00000000 is attached
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 02 (pcb:0x2FE2) starting at sector 0x0000285C MBR at 0x00000000 is attached
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 03 (pcb:0x2FD2) starting at sector 0x00005079 MBR at 0x00000000 is attached
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 04 (pcb:0x2FC2) starting at sector 0x00007896 MBR at 0x00007879 is attached
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 05 (pcb:0x2FB2) starting at sector 0x0000A0B3 MBR at 0x0000A096 is not attached
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 06 (pcb:0x2FA2) starting at sector 0x0000C8D0 MBR at 0x0000C8B3 is idle offset 0x01BE
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 07 (pcb:0x2F92) starting at sector 0x0000F0ED MBR at 0x0000F0D0 is idle offset 0x01BE
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 08 (pcb:0x2F82) starting at sector 0x0001190A MBR at 0x000118ED is idle offset 0x01BE
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 43 (pcb:0x2F72) starting at sector 0x00014127 MBR at 0x0001410A is volume C:
Label:"FILES "
>activate part8
>show parti
Partition 01 (pcb:0x2FF2) starting at sector 0x0000003F MBR at 0x00000000 is attached
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 02 (pcb:0x2FE2) starting at sector 0x0000285C MBR at 0x00000000 is attached
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 03 (pcb:0x2FD2) starting at sector 0x00005079 MBR at 0x00000000 is attached
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 04 (pcb:0x2FC2) starting at sector 0x00007896 MBR at 0x00007879 is attached
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 05 (pcb:0x2FB2) starting at sector 0x0000A0B3 MBR at 0x0000A096 is not attached
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 06 (pcb:0x2FA2) starting at sector 0x0000C8D0 MBR at 0x0000C8B3 is idle offset 0x01BE
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 07 (pcb:0x2F92) starting at sector 0x0000F0ED MBR at 0x0000F0D0 is idle offset 0x01BE
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 08 (pcb:0x2F82) starting at sector 0x0001190A MBR at 0x000118ED is not attached
Drive has 0x00002800 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0100 cylinders
Drive type/flags and name 0x00/0x00 RL01
Partition 43 (pcb:0x2F72) starting at sector 0x00014127 MBR at 0x0001410A is volume C:
Label:"FILES "
>activate part6
>activate part7
When you have activated all partitions you want you can re-insert the SD-Card into the computer, in my case all partitions have been activated now.
Peters-Mini:v2 peter$ diskutil list /dev/disk3
/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *507.4 MB disk3
1: Linux 10.5 MB disk3s1
2: Linux 10.5 MB disk3s2
3: Linux 10.5 MB disk3s3
4: Linux 10.5 MB disk3s5
5: Linux 10.5 MB disk3s6
6: Linux 10.5 MB disk3s7
7: Linux 10.5 MB disk3s8
8: Linux 10.5 MB disk3s9
9: DOS_FAT_32 FILES 423.2 MB disk3s10
Peters-Mini:v2 peter$
Now you can copy your RL02 diskimages to the respective partition.
Peters-Mini:~ peter$ cd disksrsx/
Peters-Mini:disksrsx peter$ ls
NETGEN.dsk rsx11m46 simh-rm05.ini
dlrt11v57.dsk rsx11m46.tpc sysgen42.dsk
du057.dsk rsx11mbl26_3_2.rl01 sysgenrsx11m
rd52_0-rt11v57.dsk rsx11mbl26_3_2.rl01.bz2 usedrsx11mp.dsk
rd52new.dsk rsx11mp46-blank.dsk v57bld.dsk
rl0.dsk rsx11mp46-rl02pg.README v57bldboot.dsk
rl02.dsk rsx11mp46-rl02pg.dsk
rl057.dsk rsx11mp46-rl02pg.zip
rl0hack11v2-20180417.dsk rsx11mp46-rm05.dsk
rl0hack11v2.dsk rsx11mp46toy.dsk
rl0null.dsk rsx11mplus_4_6_bl87.dsk
rl1.dsk rsx11mplus_4_6_bl87_dsk.zip
rm rsx11mplus_4_6_hack11.dsk
rm05.log rt1153distr.dsk
rm05b.log rt11v57.rd
rm05c.log rt11v57dl4.dsk
rm05d.log rt56.dsk
rp0.dsk rt56b.dsk
Peters-Mini:disksrsx peter$ sudo dd if=rsx11mplus_4_6_hack11.dsk of=/dev/disk3s1
Password:
dd: /dev/disk3s1: end of device
20481+0 records in
20480+0 records out
10485760 bytes transferred in 8.403989 secs (1247712 bytes/sec)
Peters-Mini:disksrsx peter$ sudo dd if=rt11v57dl4.dsk of=/dev/disk3s2
20480+0 records in
20480+0 records out
10485760 bytes transferred in 9.016126 secs (1163001 bytes/sec)
Peters-Mini:disksrsx peter$ diskutil eject /dev/disk3
Disk /dev/disk3 ejected
Peters-Mini:disksrsx peter$
Remove the SD-Card from your computer and insert it into the RLV12 Emulator
>
SD Card inserted
-> automount
Set SPI Mode:01 Counts:01
Interface Condition Read:0x0580FF8000
Initialise Card RC:0x00, # of tries:0x2A
Operation Condition Reg.:0x0580FF8000FF SD_Status:0x05
Set Block Length RC:00
New RL02 Volume Startsector...........:0000003F Unit:01
New RL02 Volume Startsector...........:00005079 Unit:02
New RL02 Volume Startsector...........:0000A0B3 Unit:03
Primary Extended Partition............:0000F0B3
Next Extended Partition Startsector...:0000F0B3
New RL02 Volume Startsector...........:0000F0ED Unit:04
Next Extended Partition Startsector...:000140ED
New RL02 Volume Startsector...........:00014127 Unit:05
Next Extended Partition Startsector...:00019127
New RL02 Volume Startsector...........:00019161 Unit:06
Next Extended Partition Startsector...:0001E161
New RL02 Volume Startsector...........:0001E19B Unit:07
Next Extended Partition Startsector...:0002319B
New RL02 Volume Startsector...........:000231D5 Unit:08
Next Extended Partition Startsector...:000281D5
Volume address 0x0160, PCB address 0x2FF6, Type 0x01, Status 0x03, Start Sector 0x0000003F
Volume address 0x0170, PCB address 0x2FEA, Type 0x01, Status 0x03, Start Sector 0x00005079
Volume address 0x0180, PCB address 0x2FDE, Type 0x01, Status 0x03, Start Sector 0x0000A0B3
Volume address 0x0190, PCB address 0x2FD2, Type 0x01, Status 0x03, Start Sector 0x0000F0ED
Status................................:03
Partition start.......................:0002820F
Sectors before this partition.........:0002820F
Number of FATs........................:02
Sectors per FAT.......................:000000CA
Sectors per cluster...................:10
Bytes per sector......................:0200
Reserved sectors......................:0001
1st FAT starts at sector..............:00028210
Data starts at sector.................:000283C4
FAT16 Volume with root dir sectors....:20
The root dir starts at sector.........:000283A4
Success!
>
You can now display the partition and unit status and rearrange the partitions to unit mapping.
>show part
Partition 01 (pcb:0x2FF6) starting at sector 0x0000003F is attached
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 02 (pcb:0x2FEA) starting at sector 0x00005079 is attached
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 03 (pcb:0x2FDE) starting at sector 0x0000A0B3 is attached
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 04 (pcb:0x2FD2) starting at sector 0x0000F0ED is attached
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 05 (pcb:0x2FC6) starting at sector 0x00014127 is not attached
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 06 (pcb:0x2FBA) starting at sector 0x00019161 is not attached
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 07 (pcb:0x2FAE) starting at sector 0x0001E19B is not attached
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 08 (pcb:0x2FA2) starting at sector 0x000231D5 is not attached
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
>show unit
Unit 0 (0x0160) is attached to partition 01 (0x2FF6) starting at sector 0x0000003F
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Unit 1 (0x0170) is attached to partition 02 (0x2FEA) starting at sector 0x00005079
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Unit 2 (0x0180) is attached to partition 03 (0x2FDE) starting at sector 0x0000A0B3
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Unit 3 (0x0190) is attached to partition 04 (0x2FD2) starting at sector 0x0000F0ED
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
>
Now you can attach a unit to any of the available partitions. Make sure you first detach an attached unit.
>det rl3
>attach rl3 part6
>
>
>show unit
Unit 0 (0x0160) is attached to partition 01 (0x2FF6) starting at sector 0x0000003F
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Unit 1 (0x0170) is attached to partition 02 (0x2FEA) starting at sector 0x00005079
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Unit 2 (0x0180) is attached to partition 03 (0x2FDE) starting at sector 0x0000A0B3
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Unit 3 (0x0190) is attached to partition 06 (0x2FBA) starting at sector 0x00019161
Drive has 0x00005000 blocks has 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
>
Here you can see another session where a unit is mapped to a disk image and a partition is remapped
>det rl3
>det rl0
>att rl0 /diskimages/rt11v57dl4.dsk
/diskimages/rt11v57dl4.dsk
Fragments of file
Size:00005000 Start:000640F0
>att rl3 par1
>show un
Unit 0 (0x0E60) is attached to file (0x2F54) /diskimages/rt11v57dl4.dsk
Fragments of file
Size:00005000 Start:000640F0
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Unit 1 (0x0E70) is attached to partition 02 (0x2FE2) starting at sector 0x00005003
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Unit 2 (0x0E80) is attached to partition 03 (0x2FD2) starting at sector 0x0000A004
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Unit 3 (0x0E90) is attached to partition 01 (0x2FF2) starting at sector 0x00000002
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
>
Another new command is initialize
this command is not currently fully implemented but
it’s intention is to write a standard bad sector file to the last track of the volume
in order to support operating system that expect an existing bad sector file like RT-11.
For the time being this command is only supported on partitions not on disk image
files.
FDISK
As a reference I have also implemented a simple version of the fdisk
command
on the RLV12 emulator
>fdisk
Sector: 0x00000000, Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 83 1023 254 63 - 1023 254 63 [0x00000002 - 0x00005000] Linux files
2: 83 1023 254 63 - 1023 254 63 [0x00005003 - 0x00005000] Linux files
3: 83 1023 254 63 - 1023 254 63 [0x0000A004 - 0x00005000] Linux files
4: 05 1023 254 63 - 1023 254 63 [0x0000F004 - 0x00EBEFFC] Extended DOS
Sector: 0x0000F004, Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 83 1023 254 63 - 1023 254 63 [0x0000F005 - 0x00005000] Linux files
2: 05 1023 254 63 - 1023 254 63 [0x00014005 - 0x00EB9FFB] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Sector: 0x00014005, Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 83 1023 254 63 - 1023 254 63 [0x00014006 - 0x00005000] Linux files
2: 05 1023 254 63 - 1023 254 63 [0x00019006 - 0x00EB4FFA] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Sector: 0x00019006, Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 83 1023 254 63 - 1023 254 63 [0x00019007 - 0x00005000] Linux files
2: 05 1023 254 63 - 1023 254 63 [0x0001E007 - 0x00EAFFF9] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Sector: 0x0001E007, Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 83 1023 254 63 - 1023 254 63 [0x0001E008 - 0x00005000] Linux files
2: 05 1023 254 63 - 1023 254 63 [0x00023008 - 0x00EAAFF8] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Sector: 0x00023008, Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 83 1023 254 63 - 1023 254 63 [0x00023009 - 0x00005000] Linux files
2: 05 1023 254 63 - 1023 254 63 [0x00028009 - 0x00EA5FF7] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Sector: 0x00028009, Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 0B 1023 254 63 - 1023 254 63 [0x0002800A - 0x00EA5FF6] Win95 FAT-32
2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
>