How a TRS-80 Disk Boots: Regular and Dual Boot

Introduction

Every TRS-80 disk system starts the same way: the ROM reads one sector from drive 0 and runs it. Everything after that, the DOS, a game's own loader, or a program that starts on more than one model, is up to the 256 bytes in that sector. This page follows the boot from the moment RESET is pressed to the moment a DOS or program is running, for the Model I, Model III, Model 4 and Model 4P.

The first part covers the ordinary boot: what each ROM does, what it checks and what it ignores, what the boot sector of each major DOS does next, and what the messages and silences of a failed boot mean. The second part covers dual-boot disks, which start and run on both a Model I and a Model III even though the two machines look for different sectors in different recording densities. It explains why such a disk is possible at all, and then takes the dual-boot families one at a time: how each tells the two machines apart, how it gets from its boot sectors to the program, and how it keeps the parts that must differ between the machines, system files included, from getting in each other's way.

Everything on this page was taken from the code itself: the Level II, Model III and Model 4 ROMs, the Model 4P boot ROM, and the boot sectors of eleven DOS builds, all disassembled on this site and linked below, checked against the disk images in the trs-80.com archive. H. C. Pennington's TRS-80 Disk & Other Mysteries (IJG, November 1979) was used as a starting point. It was the first book to describe the TRS-80's disks in detail and much of it still holds, but it was written before almost every DOS on this page existed; The 1979 View sets out what it says about booting and where later systems differ.

Addresses and bytes are in hexadecimal. "Sector 0" and "sector 1" are the numbers in the sector's ID field, which is what the controller looks for, not positions around the track.

The Boot at a Glance

The single most important fact about booting a TRS-80 is that the Model I and the Model III do not look for the same thing:

Model IModel III and Model 4Model 4P
What starts the bootPower on (0000h), or RESET, which is wired to the NMI (0066h) and cold-starts the ROM when a disk controller answersPower on or RESET (both reach 3015h)Power on or RESET: the 4K boot ROM, which replaces the Model III ROM
How to skip the diskHold BREAK: Level II BASIC starts as on a cassette machineHold BREAK: the Cass? prompt, then ROM BASICNot by BREAK (it is only noted at 405Bh for the booted program); the ROM image can be loaded with F3 or 3
ControllerWD1771 in the Expansion Interface, at memory addresses 37E0h-37EFhWD1793 at ports F0h-F4h (Model 4 gate array: WD1773)WD1793 at ports F0h-F4h (gate array: WD1773)
Density readSingle density (FM) onlyDouble density (MFM) onlyDouble density (MFM)
Sector readCylinder 0, sector 0, drive 0Cylinder 0, sector 1, drive 0Cylinder 0, sector 1, hard disk first, then floppy drive 0
Loaded at4200h-42FFh, then JP 4200h4300h on, then JP 4300h4300h on; run there, or the Model III ROM image is started instead
Errors checkedNone, and no time-out: if the sector cannot be read, the machine waits for everRecord not found, CRC error, lost data; the read is tried again with no limitEvery error is shown as a message (in English, German and French) and the CPU halts
Data address markNot checkedNot checkedRead, and used to tell a TRSDOS 1.x disk (F8) from an LDOS-style disk when the ROM image is loaded from it

Three differences, the sector number, the density and the load address, are what make a disk belong to one machine. They are also what lets a single disk belong to both (see How Dual Boot Works).

The Model I: Level II BASIC's Bootstrap

The Model I has no separate boot ROM: the disk bootstrap is a few dozen bytes inside the Level II BASIC ROM's power-up code. The steps, with the ROM addresses (they are the same in every Level II ROM version; see the Model I, III and 4 ROM disassembly):

AddressCodeWhat happens
0000HDI / XOR A / JP 0674hPower on. Interrupts off, then the initialization routine.
0066HLD SP,0600hRESET. On the Model I the RESET button drives the Z80's NMI line, not its reset pin, so pressing it lands here.
0069HLD A,(37ECH) / INC A / CP 02h / JP NC,0000HRead the disk controller's status. With no Expansion Interface the address reads FFh; with a controller it reads something else, and RESET becomes a full cold start. That is why RESET on a disk system reboots the DOS. Without a controller: JP 06CCh, back to BASIC.
0674H-0689HLDIR ...Copy the RST vectors and device control blocks (06D2h-0707h) to 4000h-4035h and clear the next 39 bytes.
068BHLD A,(3840H) / AND 04h / JP NZ,0075hIs BREAK held down? Then skip the disk and start Level II BASIC.
0693HLD SP,407DH / LD A,(37ECH) / INC A / CP 02h / JP C,0075hIs there a controller? If not, Level II BASIC.
069FHLD A,01h / LD (37E1H),ASelect drive 0 (bit 0 of the drive select latch), which also starts its motor. 000Dh, the ROM's $BOOT entry, jumps here: a program can reboot the disk with JP 000Dh.
06AAHLD (HL),03hRESTORE: step the head out to track 0, at the slowest stepping rate.
06ACHLD BC,0000H / CALL 0060HDelay. The loop at 0060H takes about 14.65 µs a count, and BC = 0000h counts 65,536 times: about one second for the motor to come up to speed.
06B2HBIT 0,(HL) / JR NZ,06B2HWait until the controller is no longer busy.
06B7HXOR A / LD (37EEh),ASector register = 0. The track register is already 0 from the RESTORE.
06BDHLD A,8CH / LD (HL),AREAD SECTOR (8Ch: one sector, IBM sector lengths, head load delay).
06C0H-06C7hBIT 1,(HL) / JR Z / LD A,(DE) / LD (BC),A / INC C / JR NZTake each byte from the data register (37EFh) when the status shows DATA REQUEST, into 4200h on. Only Register C is counted, so exactly 256 bytes are taken: 4200h-42FFh.
06C9HJP 4200HRun the boot sector.

What the Model I's bootstrap does not do matters as much as what it does:

  • It never looks at the result of the read. No error bit is tested, the data address mark is not tested, and there is no second try. If 256 bytes arrive, they are run.
  • It has no time-out. The byte loop waits for DATA REQUEST and nothing else. When the controller gives up (a disk with no single-density sector 0, such as a Model III disk, an unformatted disk, or a damaged track 0), no data request ever comes and the computer simply waits. Only RESET gets it out, and holding BREAK during RESET is the way to get to BASIC.
  • It reads single density only. The WD1771 cannot read double density at all. A Model I with a doubler still boots its first sector in single density, because the doubler starts in single density (see Model I Double Density).
  • It needs a 256-byte sector 0. With IBM sector lengths, a 128-byte sector 0 delivers only 128 bytes, and the loop waits for the 129th for ever.

The Model III and the Model 4: the ROM's Bootstrap

The Model III's ROM was largely rewritten, and its bootstrap is more careful than the Model I's. The Model 4's ROM keeps the same bootstrap. The steps, with the addresses of the revised Model III 3.0 ROM (the other versions are shifted a few bytes; see the ROM disassembly):

AddressCodeWhat happens
0000h, 3015hJP 3015h / JP 3455hPower on. RESET on the Model III also arrives through the NMI; the ROM's handler tells it from a disk interrupt by port E4h and restarts here.
3455hIM 1 / LD SP,407Dh / OUT (E4h),AInterrupt mode 1, a stack, the NMI latch cleared.
345Eh-3466hOUT (ECh) / OUT (F4h),81h / OUT (F0h),D0hVideo wait states on; drive 0 selected in double density (bit 7 of port F4h); the controller stopped with Force Interrupt.
346FhLD A,0Bh / OUT (F0h),ARESTORE: head to track 0.
3473h-3487hLDIR / LDIRCopy the RAM vectors and device control blocks (36AAh-36F5h to 4000h, 36F9h-3738h to 41E5h).
3489h-348FhCALL 01C9h / CALL 028Dh / JP NZ,37AFhClear the screen. BREAK held: Cass? and BASIC without disk.
3492h-3495hIN A,(F0h) / INC A / JP Z,37AFhA status of FFh means no controller: Cass?.
3498h-34A9hBIT 2,AWait, with a time-out, for the Track 0 bit. A drive 0 that never reaches track 0: Cass?.
34ABh-34C8hBIT 1,AWait for the index pulse (bit 1 of the status after a RESTORE): five readings of it. If it does not come before a time-out, no diskette is turning in drive 0: the ROM shows Diskette? (0277h) and waits again, for as long as it takes.
34CAh-34E9hLD HL,3502h / LD (404Ah),HL ... OUT (F0h),80hPoint the NMI vector (4049h) at 3502h, let the controller's interrupt through as an NMI (port E4h = 80h), sector register = 1, buffer 4300h, READ SECTOR (80h).
34EEh-34FFhINI / OUT (F4h),C1h / INI / JP 34F7hThe first byte is polled; every byte after it is taken with INI while bit 6 of port F4h holds the CPU in wait states until the next byte is ready. The loop does not count: it ends only when the controller's interrupt arrives as an NMI.
3502h-3516hAND 1Ch / JP Z,4300h / JR 34CAhThe NMI: NMI off, the vector at 4049h set to a RETN, the status masked with 1Ch (record not found, CRC error, lost data). Clean: JP 4300h. Otherwise read the sector again.

The consequences:

  • The ROM tries again for ever. A disk whose double-density sector 1 cannot be read, a Model I disk for example, leaves the drive running and the screen blank while the ROM retries.
  • The data address mark is not checked. Mask 1Ch leaves out the record-type bit, so a boot sector written with F8 (as TRSDOS 1.3's is) or FB boots the same.
  • The length is the sector's. Because the transfer runs until the controller's interrupt, a boot sector longer than 256 bytes is loaded beyond 43FFh.
  • The reads are interrupt-ended and wait-stated. Every Model III boot sector on this page reads its sectors the same way as the ROM: INI with wait states for the bytes, and its own NMI routine at 4049h for the end of the read.

The Model 4

The Model 4 boots through the same code (in the Model 4 ROM the wait for the diskette counts five full index pulses, each one set and then clear), so a Model 4 boots Model III disks as a Model III. Which mode it then runs in is decided by the boot sector: the boot sectors of the 201 TRSDOS 6 and LS-DOS system disks checked all start 00 FE nn F3 3E 86 D3 84 (nn the directory cylinder), that is NOP / CP nn / DI / LD A,86h / OUT (84h),A. Its first act is to write port 84h, the Model 4's memory map and video control port, which a Model III does not have. That is why a Model 4-mode disk cannot run on a Model III, though the Model III ROM will load and start its boot sector.

The Model 4P: a Boot ROM and a ROM Image

The Model 4P has no Model III ROM at all. In its place is a 4K boot ROM (see the Model 4P boot ROM disassembly), and Model III software is run by loading an image of the Model III ROM, the file MODELA/III (or MODELB/III to MODELG/III), into RAM at 0000h-37FFh. The boot ROM:

  1. Sets up the machine, scans the keyboard for the keys held at reset (F1 or 1 hard disk, F2 or 2 floppy, F3 or 3 the ROM image, Right SHIFT RS-232, V the version, N, L and P as below), and restores the floppy drives.
  2. Tries the hard disk; if that fails, floppy drive 0. A drive boot reads cylinder 0, sector 1 into 4300h, as a Model III does.
  3. Decides whether the sector needs the Model III ROM. A 256-byte boot sector is scanned for a CALL to an address 0000h-00FFh (the bytes CD xx 00, executable or not). If there is none, the sector is a Model 4 boot: the ROM sets memory map mode 0 and the 2 MHz clock, switches itself out through its exit routine at 4020h, and jumps to 4300h. A sector with such a call, or any 512-byte boot sector, needs the Model III ROM.
  4. Gets the ROM image. If a ROM image is still in RAM from an earlier boot (its jump table at 3000h and the word at 000Bh are intact), it is used; otherwise MODEL%/III is read from floppy drive 0 through that disk's directory. The image is started at 3015h, the Model III's own start, and from there the boot is a Model III boot, ROM bootstrap and all.

Two consequences matter for old disks. First, the image is read from the disk in the drive, so a self-booting Model III game disk, which has no directory and no MODELA/III, cannot supply it; the ROM stops with The ROM Image Was Not Found On Drive 0. The cure is the P key: hold P at reset with a disk that has the image, and the ROM loads it, shows The ROM Image Has Been Loaded and waits, so the disk can be changed before ENTER. (L forces the image to be loaded from disk even when one is in RAM; N runs a boot sector without the image even when it calls into the ROM area.) Second, when the image is loaded from a disk, the boot ROM reads that disk's layout from the data address mark of its boot sector: F8 means the TRSDOS 1.x layout (directory cylinder in byte 1, sectors from 1), anything else the LDOS-style layout (byte 2, sectors from 0). A TRSDOS 1.3 disk whose boot sector has been rewritten with an FB mark loads the image and then fails with a seek error, as boot tests in an emulator confirmed.

The Model I in Double Density

A Model I with a double-density adapter (Percom's Doubler, Radio Shack's doubler and others) still boots exactly as above: the adapter starts up in single density and the ROM knows nothing about it. So every Model I double-density system disk has to keep at least its boot sector in single density on cylinder 0, and the boot sector, once running, switches the adapter over. The DOSes did this in different ways:

  • DOSPLUS 3.5: the boot sector reads the disk's settings (sector 2 of cylinder 0) first and switches the adapter to double density only when they say so (DOSPLUS 3.5 Model I boot sector).
  • LDOS: SOLE/CMD keeps cylinder 0 single density on a double-density system disk and writes a double-density boot module into its sectors 5 and 6 (LDOS 5.3.1 Model I boot sector).
  • NEWDOS/80 describes such a disk in its PDRIVE table with the letter K: track 0 in the opposite density to the rest.
  • Percom DoubleDOS: cylinder 0 is single density, and sector 0 is the only sector on it with data. The boot sector writes FFh to the controller's command address (37ECh), the Doubler's command for double density, and loads SYS0/SYS from cylinder 1, sector 0 on (DoubleDOS boot sector). NEWDOS/80's Model I boot sector writes FEh to the same address first, which on a Percom Doubler selects single density.
  • TRSDOS 2.7DD: cylinder 0 single density with ten sectors numbered 0-9; every other cylinder double density with eighteen sectors numbered 1-18, as on a Model III.

The mixed-density cylinder 0 of these disks is a Model I matter only. A Model III cannot boot any of them, since its ROM reads cylinder 0 in double density.

What a Boot Sector Does

Once the ROM has jumped to it, the boot sector is on its own: 256 bytes, no DOS, only the ROM's display and keyboard routines to call. Almost every DOS's boot sector follows the same plan.

The first bytes are code and data at once

TRSDOS 2.3's boot sector starts 00 FE 11 F3 31 FC 41. Run from 4200h, that is NOP, then CP 11h, a compare whose result nothing tests, then DI and LD SP,41FCh. The compare is there only so that its operand, byte 2 of the sector, can hold the directory cylinder (11h, cylinder 17) and still be executed harmlessly. The DOS reads that byte later to find the directory of any disk put in a drive. The same trick runs through the whole TRSDOS 2.3 family, LDOS, NEWDOS/80 and DOSPLUS; TRSDOS 1.3 starts FE 11, so its directory cylinder is byte 1. MicroDOS uses byte 0 as a length byte instead: FE 00 is CP 00h to the CPU and "254 bytes follow" to MicroDOS. Byte 0 is free on the 2.3 family: while a single-drive BACKUP runs, TRSDOS 2.3 keeps a HALT (76h) there on the copy and puts the real byte back at the end.

It loads SYS0/SYS and jumps to it

  • Finding SYS0/SYS. TRSDOS 2.3, LDOS, VTOS 4 and DOSPLUS read sector 4 of the directory cylinder, whose first entry is SYS0/SYS's, check that the entry is in use, and load from the start of its first extent. NEWDOS/80 carries SYS0/SYS's track and sector in the boot sector itself (track 0, sector 5). TRSDOS 1.3 always starts at track 0, sector 2. DoubleDOS always starts at cylinder 1, sector 0.
  • Loading it. SYS0/SYS is read one sector at a time into a buffer (4D00h, 5100h or 5300h) and taken as a load module: a record of type 01h is a block of bytes with its load address, type 02h the transfer address, and other types are skipped. The boot sectors that read the directory follow only the first extent, so SYS0/SYS must lie in consecutive sectors from its first granule.
  • Running it. The transfer record ends the load with a jump, usually to 4E00h. NEWDOS/80 adds a check: the byte at the transfer address must be A5h, and the jump goes to the byte after it.
  • Failing. A sector that cannot be read after a few tries gives an error message; a missing SYS0/SYS gives a "no system" message. Then the boot sector waits for ENTER or stops until RESET.

The rest of BOOT/SYS

The directory names the boot area BOOT/SYS: the first granule of cylinder 0, five sectors on a single-density disk. The ROM reads only one of them. What the others hold depends on the DOS: nothing on TRSDOS 2.3; a copy of the boot sector and the PDRIVE table on NEWDOS/80; a second boot sector for booting through a disk driver, the system information sector and a copy of the allocation table on LDOS and VTOS 4; the drive settings and boot options on DOSPLUS. On Model III DOSes that number sectors from 0, sector 1 is the boot sector and sector 0 is either a copy of it (LDOS, NEWDOS/80) or only the directory cylinder byte (DOSPLUS), because the DOS reads byte 2 of sector 0 when it looks for a disk's directory.

The Boot Sectors of the Major DOSes

Each row links to the full disassembly of that boot sector.

DOSSector the ROM runsHow it finds what it loadsBufferTriesJumps toMessages
DOSPLUS 3.5 (Model I)0, at 4200h (sector 1 is a copy)Settings sector 2 first, then directory sector 4, entry 05300h24E00hERROR!
DOSPLUS 3.5 (Model III)1, at 4300h (sector 0 holds only byte 2)Settings sector 2 first, then directory sector 4, entry 05300h24E00hDISK ERROR!
DoubleDOS 4.24 (Model I)0 (single density), at 4200hFixed: cylinder 1, sector 0 on, in double density4D00h24E00hDISK ERROR
LDOS 5.3.1 (Model I)0, at 4200hDirectory sector 4, entry 0, first extent5100h24E00hNo System, Disk Error
LDOS 5.3.1 (Model III)1, at 4300h (sector 0 is a copy)Directory sector 4, entry 0, first extent5100h54E00hNo system, Disk error
MicroDOS 2.20 (Model I)0, at 4200hFixed: track 0 sector 1 to track 1 sector 9, after checking for the word MICRODOS4300h14400hNO MICRODOS, DISK ERROR
NEWDOS/80 2.0 (Model I)0, at 4200h (sector 1 is a copy)Fixed: track 0, sector 5 on5100h104D01h, after checking A5h at 4D00hNO SYS, ERROR
NEWDOS/80 2.0 (Model III)1, at 4300h (sector 0 is a copy)Fixed: track 0, sector 5 on5100h104D01h, after checking A5h at 4D00hNO SYS, ERROR
TRSDOS 1.3 (Model III)1, at 4300h (sectors are numbered 1-18)Fixed: track 0, sector 2 on4D00h94E00hERROR
TRSDOS 2.3 (Model I)0, at 4200hDirectory sector 4, entry 0 (SYS0/SYS), first extent4D00h2SYS0/SYS's transfer addressNO SYSTEM, DISK ERROR
VTOS 4.0.2 (Model I)0, at 4200hDirectory sector 4, entry 0, first extent5100h24E00hNO SYSTEM, DISK ERROR

Some details that set one DOS apart:

  • TRSDOS 1.3 keeps its limited-backup counter at byte 22h of the boot sector, the disk's serial number at F4h-FBh, its version at FEh and its track count at FFh. FORMAT writes the boot sector to every disk it formats (see TRSDOS 1.3: the limited-backup counter).
  • NEWDOS/80's FORMAT fills the boot sector with the geometry of the drive being formatted (sectors per track, the first sector number, the select byte, three PDRIVE bytes at FDh-FFh), so even a disk with no usable PDRIVE table still says how it was laid out.
  • LDOS and VTOS 4 carry the bootstrap stepping rate in the operand of the boot sector's seek command; FORMAT sets it and SYS0/SYS copies it into the drive's table.
  • The data address mark matters to some Model I boot sectors. TRSDOS 2.3's boot sector, which NEWDOS 2.1 shares, tests the read status with mask 5Ch, which includes bit 6 of the WD1771's record-type field. A directory sector written with an F8 or F9 mark therefore stops the boot with DISK ERROR, while FA, the mark TRSDOS 2.3 writes on its directory, passes. A disk whose directory marks were converted to F8 loads the boot sector and then fails, as boot tests in an emulator confirmed. LDOS's Model I boot sector masks with 1Ch and does not care.

Data Disks and Other Disks That Do Not Boot

Every formatted disk has a boot sector, because the DOS reads its directory cylinder byte. What a data disk's boot sector does when it is booted depends on the DOS that formatted it:

  • TRSDOS 2.3 writes its full boot sector on every disk. On a data disk the directory has no SYS0/SYS entry, so the boot stops at NO SYSTEM.
  • NEWDOS/80 stops at NO SYS when what it reads is not a load module.
  • TRSDOS 6 and LS-DOS write a short stub into both sector 0 and sector 1 of a data disk, with the message Cannot boot, DATA DISK!, so either machine's ROM finds a sector that says so.
  • Percom DoubleDOS's FORMAT writes a stub that displays NO SYSTEM.

A boot sector that only reports that the disk is for another model, or is a data disk, is not a boot in the sense of this page: the disk does not start a DOS or a program on that machine.

When a Disk Will Not Boot

MachineWhat you seeWhat it means
Model INothing happens; drive 0 may run and stop; RESET does the sameThe ROM's read of single-density sector 0 never finished: no disk, a Model III or double-density disk, an unformatted or damaged track 0, or a 128-byte sector 0. The ROM has no time-out. Hold BREAK and press RESET for BASIC.
Model INO SYSTEM, NO SYS, No SystemThe boot sector ran but the disk has no SYS0/SYS: a data disk.
Model IDISK ERROR, ERROR, ERROR!The boot sector ran but could not read the directory or a sector of SYS0/SYS. On TRSDOS 2.3 and NEWDOS 2.1, also a directory sector with an F8 or F9 data mark.
Model III, 4Cass?BREAK was held, there is no disk controller, or drive 0 never reached track 0.
Model III, 4Diskette?, again and againNo diskette is turning in drive 0 (no index pulses): no disk, or the door is open.
Model III, 4Drive 0 runs, the screen stays blankDouble-density sector 1 cannot be read and the ROM is retrying without end: a Model I or single-density disk, an unformatted disk, or a damaged sector 1.
Model III, 4ERROR, Disk error, DISK ERROR!, No system, NO SYSAs on the Model I: the boot sector ran and the DOS's own load failed.
Model 4PAn error message with a code, and a haltFrom the boot ROM: for example The ROM Image Was Not Found On Drive 0 (a Model III disk without MODELA/III: use the P key), The Floppy Disk Drive Is Not Ready, or CRC Error, Try Again Or Use Another Disk.

How One Disk Boots on Two Machines

A disk tagged [Dual Boot] in the archive boots and runs on a Model I and on a Model III (such disks are listed as Model 13). A Model 4 boots it as a Model III, and a 4P does once it has the Model III ROM image, so the Model III is the second machine that counts. A disk that only tells the second machine it is the wrong disk is not dual boot. No disk is known that boots both a Model I and a Model 4 in Model 4 mode.

Every dual-boot disk has to answer three questions, and the families below answer them in different ways: how the program knows which computer it is on, how it gets from the boot sector to the program, and what it does about the parts that must differ between the two machines (the disk routines, sometimes the whole program, and on transfer disks the files themselves).

Two boot sectors on one cylinder 0

The Model I's ROM reads single-density sector 0; the Model III's reads double-density sector 1. The two never see each other's sector: the WD1771 cannot read double density at all, and the Model III's ROM reads only in double density. So a cylinder 0 that holds a single-density sector 0 and a double-density sector 1 can hold one boot sector for each machine, each read only by the ROM it was written for. The load addresses differ too (4200h and 4300h), so each sector is written to run where its own machine puts it.

The difficulty is making such a track. A formatter writes a whole track in one density, and no DOS FORMAT writes a mixed one. Vernon Hester, the author of MultiDOS, has described how his dual-boot diskettes were made: cylinder 0 is formatted in double density, and then a single-density sector 0 alone is formatted over the start of it. A single-density sector takes nearly twice the room of a double-density one, so it overwrites the double-density sector that follows sector 0 around the track, which in MultiDOS's 3:1 interleave is sector 6. On these disks a missing double-density sector 6 on cylinder 0 is how the disk was made, not damage.

Other dual-boot disks hold only the two boot sectors on cylinder 0 (SuperMOVE, the Duo-Loader, Arranger, Cornsoft), and some hold more: Super Utility v2 puts six single-density and six double-density sectors on the track, numbered even and odd; SofTrends adds four more single-density sectors of 256, 512 and 1024 bytes beside its boot sector; FunSoft adds a second single-density sector for the Model III's use; Cogito adds five single-density sectors numbered 100-104; and Big Five's BFLOADER fills the single-density part with nine 128-byte sectors so that three double-density sectors still fit.

Where the program lives

The Model I's controller reads only single density (unless a doubler is fitted), while the Model III's reads both. Within that limit the disks in the archive keep their programs in five ways:

  • One copy, in single density, read by both. The Model III's boot code switches its controller to single density (bit 7 of port F4h clear, for example OUT (F4h),01h) and reads the same sectors as the Model I: the Duo-Loader games, Cogito, FunSoft's games, MultiDOS and the Computer Shack games, SofTrends, and the files a SuperMOVE disk carries (its two transfer programs are separate).
  • Two copies on different single-density tracks. Each loader reads its own cylinders: Big Five's MINI DOS games keep a Model I build on cylinders 7-18 and a Model III build on 19-30.
  • Two copies in different densities on different cylinders. The Model I build is single density and the Model III build double density: Big Five's BFLOADER games, Cornsoft's games, and Kim Watt's FILE TRANSFER UTILITY disks.
  • Two copies on the same tracks, one in each density. Every data track holds single-density sectors for the Model I and double-density sectors for the Model III side by side: Super Utility, PowerTool and HyperZap. No formatter of a DOS can write such a track, which is part of their copy protection.
  • One copy, in double density. Dan Foy's Arranger is double density from cylinder 1 on, and its Model I boot sector switches a double-density adapter on before reading it, so the Model I needs a doubler.

Telling the machines apart

The two machines differ in more than the disk controller: the Model III's controller is at ports F0h-F4h and ends its reads with an NMI, and some ROM entry points and RAM areas moved. The disks deal with that in three ways:

  • The boot path is the test. Each boot sector loads its own disk routines or its own copy of the program, so nothing needs to ask which machine it is. Most families work this way.
  • A table filled in by the loader. The shared program calls the disk through fixed addresses, and each machine's loader puts its own routines there: the Duo-Loader's jump table at 4400h, SofTrends' driver sector at 5400h, FunSoft's one machine-specific sector on cylinder 3, and Cogito's jumps patched over the Model I boot sector's routines at 4248h-42B6h.
  • A ROM byte. Two tests were found. ROM address 0125h holds 49h (I, the last letter of Model III in Radio Shack Model III Basic) on the Model III and 4; on the Model I it holds 20h (the space after LEVEL II in RADIO SHACK LEVEL II BASIC) on the early ROMs and A3h on the 1.3 ROM, so LD A,(0125h) / CP 49h means Model III. Cogito uses it. ROM address 0054h holds 01h on the Model I (the BREAK entry of the keyboard table at 0050h) and BEh on the Model III (inside the RS-232 entry points that replaced the table), so LD A,(0054h) / DEC A giving zero means Model I. Arranger uses it.

System files on a dual-boot disk

Most dual-boot disks are self-booting programs with no directory, and so have no system files to clash. Where a directory or system files are needed, the disks show five answers:

  • No files at all. The loaders read fixed tracks and sectors (Big Five's MINI DOS, the Duo-Loader, Cogito, FunSoft, Cornsoft, Super Utility).
  • One file holding both machines' code. MultiDOS's RESIDENT/SYS covers the boot track, a Model I body and a Model III body; every other system file appears once and serves both.
  • Two system files with different names in one directory. SuperMOVE disks carry PMOVE1/SYS and PMOVE3/SYS (SMOVE1/SYS and SMOVE3/SYS on CLOAD, XFER1/SYS and XFER3/SYS on LDOS Utility Disk 2) in one single-density directory; the boot sectors reach them by position, not by name. A product with model-specific files names them apart (PowerScript's SCRPMOD1/OVR, SCRPMOD3/OVR and SCRPMOD4/OVR).
  • Two directories, one in each density. Kim Watt's FILE TRANSFER UTILITY disks have a single-density Model I directory on cylinder 5 and a double-density Model III directory on cylinder 6, and Big Five's BFLOADER disks have both on cylinder 17. Each machine, and each machine's DOS, sees only its own directory, so the same file name can stand for a different file on each.
  • Leave it to the user's DOS. SofTrends' File Transfer System keeps the product's files in one directory and moves them to the user's own DOS disk.

Cautions

  • Two boot paths in the bytes do not prove a dual boot. Of 19 archive images whose bytes showed both paths, 17 booted and ran on both models when tested; two did not. Dual boot is proved by tracing both paths to the program, or by booting the disk on both.
  • Keep dual-boot disks as DMK. A JV1 image is single density only and cannot hold the Model III's boot sector at all; a JV3 keeps the sectors of a mixed-density cylinder 0 but not their order or the layout of the track. A DMK (or a flux image) keeps the track as it is.
  • Never "repair" the missing sector 6 of a MultiDOS-style cylinder 0: there is no room for it on the track, and an image with it added would, written to a real disk, run past the index and overwrite the Model I's boot sector.

↑ Back to the page index

The Dual-Boot Disks

The families below were traced from the boot sectors of the dual-boot images in the trs-80.com archive (550 DMK images, grouped by the bytes of their two boot sectors), following each path to the program it starts. The count is the number of DMK images carrying that family's pair of boot sectors. Several families are also copy protected; their protection is described on the copy protection page and is mentioned here only where it shapes the boot.

FamilyImagesTells the machines apart byMachine-specific code and files
Kim Watt: Super Utility, PowerTool, HyperZap46 (HyperZap 6)The boot pathTwo complete builds on the same tracks, one in each density
Big Five: MINI DOS14The boot pathTwo builds of the game on different single-density cylinders
Big Five: BFLOADER7The boot pathTwo builds in two densities, and two directories on cylinder 17
Yves Lempereur / FunSoft, and publishers using his loader7 and 31The boot pathTwo versions of the first-stage loader; one machine-specific sector each on cylinder 3; one game
Kim Watt's FILE TRANSFER UTILITY22 (and 5 Power-Copy)The boot pathTwo transfer programs, two sets of files, two directories
SuperMOVE (Breeze/QSD, PowerSOFT)243The boot pathTwo transfer programs (PMOVE1/SYS, PMOVE3/SYS) in one directory; one set of files
SofTrends File Transfer System24The boot pathOne transfer program with a driver sector for each machine
Cogito: Frogger, Zaxxon, Game Packs38ROM byte 0125hOne module; on a Model III it patches jumps over the Model I boot sector's routines
MultiDOS II / ZEUS and the Computer Shack games2 and 13The boot pathOne file, RESIDENT/SYS, holding both machines' code; everything else shared
Wayne Westmoreland's games and the Duo-Loader33The boot pathTwo loaders with the same jump table at 4400h; one game
Cornsoft15The boot pathTwo builds, single density for the Model I and double density for the Model III
Dan Foy's Arranger23ROM byte 0054hOne double-density program; the Model I needs a doubler
Soft Sector Marketing / Factory Programming, Acorn, and single titles15The boot pathTwo modules, or one game with two loaders

The other six images in the set (the PowerTool Copy Utility and Verify Utility disks, the Super Utility+ 3.1a Creator disk and three AFM disks) have only a Model III boot sector.

↑ Back to the page index

Kim Watt: Super Utility, PowerTool and HyperZap

Kim Watt's disks, published by Breeze Computing, QSD, Breeze/QSD and PowerSOFT (and PowerTool by Tandy), boot in two quite different ways. His utilities, Super Utility and PowerTool, carry two complete programs on the same tracks, one in each density. His file transfer disks, the FILE TRANSFER UTILITY and SuperMOVE, are described under file transfer disks below. His SuperBOOT loader (on the Adams adventures, MAKE-80 and the Simutek disks) is a Model I boot only.

Super Utility v2.1 and Super Utility+ v2.x (1981-82)

Cylinder 0 holds single-density sectors 0, 2, 4, 6, 8 and 10 and double-density sectors 1, 3, 5, 7, 9 and 11, on one track. So does every cylinder from 3 on, except cylinders 1 and 2 (ordinary single density, ten sectors) and the protection cylinders 4 and 5. The single-density half of each track is the Model I's and the double-density half the Model III's.

  • Telling the machines apart: nothing is tested. Each ROM reads its own boot sector, and each boot sector reads only its own half of the tracks: the Model I's single-density sector 0 counts sectors 0, 2, 4 ... 10 through the controller at 37ECh, and the Model III's double-density sector 1 counts sectors 1, 3, 5 ... 11 through ports F0h-F4h in double density (OUT (F4h),81h).
  • The boot: both boot sectors are the same /CMD-format record reader (type 01h records are loaded, type 02h gives the entry, other types are skipped), fed from cylinder 3. Each loads a title screen to 3E40h and a first stage at 5200h-533Fh and enters it at 5208h. The first stage tests memory (4000h-51FFh and 5300h-FEFFh), checks the protection cylinders 4 and 5 (S-024), sets the RST vectors and hands back to its boot sector's reader, which loads the rest of its program from cylinder 6 on.
  • Two programs: the two halves hold two builds of Super Utility. Their title screens already differ (SUPER UTILITY + ... (C)(P) 1981 BY BREEZE/QSD, INC. on the Model I, mixed case on the Model III). No file system is involved: there is no directory and nothing to conflict.

Super Utility+ v3.x and PowerTool (1982-84)

The second generation keeps the idea with a different layout: cylinder 0 holds single-density sectors 0 and 2-9 (only sector 0 is the boot) and double-density sector 1; cylinder 1 holds single-density 512-byte sectors 32, 48 and 37 and double-density 512-byte sectors 64, 80 and 69; and every data track holds single-density sectors 64, 72, 80, 88, 96 and 104 and double-density sectors 64, 72, 80, 88, 96 and 104 (PowerTool v0.3: five of each, 80-112).

  • Telling the machines apart: again the boot path. The Model I's boot sector reads only the single-density sectors and the Model III's only the double-density ones, and the same sector number in the other density is invisible to it. The Model III path selects double density and its own NMI routine; the Model I path uses 37ECh.
  • The boot: each boot sector reads its three cylinder-1 sectors (nibble-encoded, stored backwards) into 4400h-46FFh and returns into 4400h; that second stage checks the protection cylinders and then reads the encoded record stream from the data tracks, six sectors a track (S-024 has the details). On a failed check the Model I halts and the Model III reboots.
  • Two programs: the sectors with the same number in the two densities hold different data on 158 of 174 pairs on PowerTool v1.00.00 (150 of 160 on PowerTool v0.3): two builds, one for each machine. No directory.
  • Not dual boot: Super Utility 4/4P's single-density sector 0 only prints This disk is for the TRS-80 Model 4/4P ONLY!; and the PowerTool Copy Utility and Verify Utility disks and the Super Utility+ 3.1a Creator disk have only a double-density boot sector, for the Model III.

HyperZap (M J Gingell - Hypersoft, 1983-85)

HyperZap is not Kim Watt's, but it is built the same way: single-density sector 0 (18 06 00 55 ...) for the Model I and double-density sector 1 (18 06 00 56 ...) for the Model III, then cylinders 1-12 each carrying single-density sectors 1-6 and double-density sectors 1-6 on the same track (S-034). Each ROM's boot reads its own density. v3.0c, v3.2c and v3.2g boot on both models; every v3.2e image lacks a single-density sector the Model I path needs, so v3.2e fails on the Model I.

Power-Copy and the transfer disks

Power-Copy I-III and Power-Copy III (Breeze Computing, 1982) boot through the same pair of loaders as the FILE TRANSFER UTILITY, and Kim Watt's LDOS Utility Disk 2 through SuperMOVE's; both are described below.

↑ Back to the page index

Big Five Software

Big Five (Bill Hogue and Jeff Konyu) used two loaders: MINI DOS on the 1980-81 games, which has no directory, and BFLOADER on the 1982 games, which has two.

MINI DOS VER 1.2 (Robot Attack, Cosmic Fighter, Galaxy Invasion, Meteor Mission II, Super Nova, Attack Force)

Cylinder 0 holds only the two boot sectors; the rest of the disk is single density, five 512-byte sectors a track (cylinder 4 and the duplicated cylinder IDs belong to the copy protection, S-003).

  • Telling the machines apart: the boot path only. The Model I's sector 0 (MINI DOS VER 1.2 BY BIG 5) seeks to cylinder 2; the Model III's sector 1 selects single density (OUT (F4h),01h) and seeks to cylinder 6.
  • The boot: each reads five 512-byte sectors (nine tries each, DISK ERROR! on failure) into 4400h-4DFFh and jumps to 4400h. That is a loader built for its own machine: cylinder 2's drives the controller at 37ECh, cylinder 6's the ports. Each puts up the title, loads twelve cylinders of game (30K) to 4800h and jumps there; if CLEAR is held it first asks Erase High Scores ? and, on Y, writes a cleared high-score sector.
  • Two games: the Model I's loader reads cylinders 7-18 and the Model III's cylinders 19-30. They are two builds of the game, 95-97% the same bytes: on Robot Attack, cylinders 9-18 and 21-30 are identical and only the first two cylinders of each build differ. Both loaders clear the same high-score sector, cylinder 31 sector 0. No directory.

BFLOADER (Defense Command, Stellar Escort, Weerd, 1982)

Here cylinder 0 holds single-density sector 0, nine 128-byte single-density sectors (E5 filler), and double-density sectors 1, 2 and 3. Cylinders 1-16 are single density, cylinder 17 is mixed again, and cylinders 18-26 are double density.

  • Telling the machines apart: the boot path only. Both boot sectors also find out what kind of drive they are in: each steps in twice and issues Read Address; an ID naming cylinder 2 means a 40-track drive, cylinder 1 an 80-track drive reading a 40-track disk, and the boot sector then doubles its steps.
  • The boot: each boot sector reads a /CMD-format file in its own density. The Model I's sector 0 starts at cylinder 1 sector 5 (single density, through 37ECh); the Model III's sector 1 starts at cylinder 18 sector 1 (double density, 18 sectors a track, through the ports). Each puts a DI (F3h) at the transfer address and jumps there.
  • Two directories on one track: cylinder 17 holds a Model I directory in single density (sectors 0-2, the 2.3 layout: GAT BFLOADER01/25/82, HIT, and entries for DIR/SYS, BOOTER/SYS, the game and HISCORES) and a Model III directory in double density (sectors 1-3, the TRSDOS 1.3 layout: GAT, HIT, one entry sector). Both list the game by the same name, DEFENSE/CMD (STELLAR/CMD, WEERD/CMD), but the Model I's entry points at the single-density build on cylinders 1-16 and the Model III's at the double-density build from cylinder 18. A DOS on either machine reading the disk sees only the directory in its own density, and so only its own build. The 128-byte single-density sectors are there to leave room on the track for the three double-density ones.

↑ Back to the page index

Yves Lempereur / FunSoft, and the Publishers Who Used His Loader

Yves Lempereur's FunSoft games (Babel Terror, Apple Panic, Black Hole, Mad Mines, Time Runner, Space Invaders, BRCDE) and the titles of Fantastic Software, Med Systems, Melbourne House, Beam Software, Software Guild, Gessler, Focus Media, McGraw-Hill and Odesta that use a loader of the same design (Penetrator, Odin, Asylum, Spox, Panik, Strike Force, Institute Adventure, Forbidden Planet and others; some say Loader by Paul Brandon) are all single density after cylinder 0, with sector numbers that change from track to track (S-008). Cylinder 0 holds single-density sectors 0 and 2 and double-density sector 1.

  • Telling the machines apart: the boot path only, carried two stages deep.
  • The Model I: single-density sector 0 steps in twice and issues Read Address to learn whether the drive has 40 or 80 tracks, then reads the ten sectors of cylinder 1 (numbered from the table 7Ch 5Fh 4Fh 27h 17h 7Bh 53h 64h 24h 41h plus the cylinder number) into 4400h and jumps there.
  • The Model III: double-density sector 1 copies itself out of the way (to 4400h on the FunSoft disks and some others, to B700h on most of the other publishers'), selects single density (OUT (F4h),01h) and reads single-density sector 2 of cylinder 0 into 4300h, by polling rather than with an NMI, and runs it. Sector 2 is a port version of the Model I's sector 0, and it reads cylinder 2 by the same table.
  • The second stage: cylinder 1 is the Model I's code (it drives 37ECh) and cylinder 2 the Model III's (it drives the ports); on Babel Terror the two are 86% the same bytes. Both go on to cylinder 3, which holds the title and the shared LOADER at 8000h, and each takes its Read Track routine from its own sector of cylinder 3 (sector 103 for the Model I, sector 39 for the Model III). The game itself is on tracks both machines read the same way (on the FunSoft disks, Read Track nibble tracks).
  • System files: none. Some disks (Apple Panic, Mad Mines) carry on their later cylinders a TRSDOS-layout directory listing only BOOT/SYS and DIR/SYS, which nothing reads.

↑ Back to the page index

File Transfer Disks: Kim Watt's FILE TRANSFER UTILITY, SuperMOVE, and SofTrends

A file transfer disk carries a product's files and a program that copies them onto the buyer's own DOS disk, so one diskette can be sold for both machines without carrying a DOS. Booting it runs the transfer program; the files themselves are ordinary files in a directory. These are the dual-boot disks on which the question of conflicting system files really arises, and the three systems in the archive answer it three ways.

Kim Watt's FILE TRANSFER UTILITY (Breeze, 1981-82): two of everything

Used on Kim Watt's own disks (PowerDRAW v1.0, the Read Protect Fix, Power-Copy) and licensed to The Alternate Source and others (Modem-80, Cribbage, Variable Finder, Faster, Orchestra-85 and -90, Piano-85, Pandemonium, SuperVaders); the directories are dated December 1981 to May 1982 (GAT name FileXfer on most). The disk is a 40-cylinder disk in two halves:

CylindersDensityContents
0BothSingle-density sector 0 (Model I boot, 00 FE 05: directory on cylinder 5) and double-density sector 1 (Model III boot, FE 06: directory on cylinder 6, in byte 1 as on TRSDOS 1.3)
1‑2SingleFILE TRANSFER UTILITY I, the Model I transfer program
3‑4DoubleFILE TRANSFER UTILITY III, the Model III transfer program
5SingleThe Model I directory, TRSDOS 2.3 layout
6DoubleThe Model III directory, TRSDOS 1.3 layout (sectors 1-18)
7‑27SingleThe Model I files
28‑39DoubleThe Model III files
  • Telling the machines apart: the boot path only. The Model I's sector 0 reads cylinder 1 in single density through 37ECh; the Model III's sector 1 reads cylinder 3 from sector 1 in double density through the ports.
  • The boot: both boot sectors are the /CMD-format record reader also used by SuperMOVE (below), with ten tries a sector. Each loads its transfer program, which says it will copy the files onto another TRSDOS I formatted disk (TRSDOS III on the Model III) on any drive, asks for the destination drive and the source and destination disks, copies, and offers to reboot.
  • Conflicting files: the two directories never meet. On Modem-80 v3.0 both list the same ten names (MODEM80/CMD, MODEM48/CMD, XMODEM/CMD, LDOSIII/FIX and others), but every one of them is a different file in the two halves: the Model I's on single-density cylinders 7-24 and the Model III's on double-density cylinders 28-35. On PowerDRAW v1.0 the program files differ and the data file DEMO/DRW is the same 93 sectors in both. Because each boot sector names its own directory cylinder, a DOS reading the disk sees only one directory too: a Model I DOS reads byte 2 of sector 0 and finds cylinder 5, TRSDOS 1.3 reads byte 1 of sector 1 and finds cylinder 6. A Model III directory can be empty (Orchestra-85, whose files are all in the Model I half), and the masters of the utility ship with both directories empty.

SuperMOVE (Breeze/QSD and PowerSOFT, 1982-88): one directory, two programs

SuperMOVE is the later design, and the archive's most common dual boot: 243 images, among them the LOAD-80 and CLOAD magazine disks, Dot Writer and its font disks, PowerScript, PowerDRAW 1.5 and 1.6, PowerDot, Electric Webster, Le Script, Scriplus, AFM, Kim's and Lance's Early Games, The ToolBox, the LDOS utility disks, and Cornsoft and Molimerx titles. The same layout is already on Kim Watt's LDOS Utility Disk 2 (March 1982), whose LDOS file transfer programs are XFER1/SYS and XFER3/SYS.

  • The disk: single density throughout but for the Model III boot sector, ten sectors a track, with an ordinary TRSDOS 2.3-layout directory on cylinder 17 (GAT names such as SUPRMOVE07/13/84, POWRSOFT07/04/84, CLOAD -FEB 1983). The directory lists BOOT/SYS, DIR/SYS, the product's files and two system files: PMOVE1/SYS on cylinder 1 and PMOVE3/SYS on cylinder 3 (SMOVE1/SYS and SMOVE3/SYS on CLOAD). The directory is the ordinary 2.3-family one, which is what makes the disk readable by a Model I DOS.
  • Telling the machines apart: the boot path only. The Model I's single-density sector 0 (00 FE 11, then CALL 01C9h) reads from cylinder 1 sector 0 through 37ECh into a buffer at 4400h; the Model III's double-density sector 1 (00 FE 11 too) sets the NMI jump at 4049h, selects single density and reads from cylinder 3 sector 0 through the ports into a buffer at 4D00h. They read the two programs by position, not through the directory.
  • The boot: both boot sectors are the same record reader in two versions: a type 01h record is loaded (and each byte checked after it is stored), type 02h is the entry, other types up to 1Dh are skipped, anything higher stops with DATA ERR (Data Error on the Model III), as a failed read does with DSK ERR or Disk Error. The program loaded is SuperMOVE - Mod I Transfer Utility or SuperMOVE - Mod III Transfer Utility, both by Kim Watt.
  • Conflicting files: both machines copy the same files, from the one single-density directory, onto another TRSDOS I formatted disk or another TRSDOS III formatted disk. A file that must differ between the machines therefore has to have its own name, and the products name them apart: PowerScript v4.2 carries SCRPMOD1/OVR, SCRPMOD3/OVR and SCRPMOD4/OVR. The program copies every file unless the destination is short of space, in which case it asks file by file (<< Copy it ?), and it asks before overwriting a file of the same name on the destination (<< EXISTS, Replace it ?). The two transfer programs are the only machine-specific files on the disk, and the boot sectors find them by position.

SofTrends' File Transfer System (Glynn Owen, 1982-85)

The AIDS-III, AIDS Plus and AIDS Plus-II disks and their companions (FileAid, LabelAid, Re-Vise, Auto-Mate, VisaPlus+) use SofTrends' own system. Cylinder 0 holds single-density sectors 0 (256 bytes), 1 (512), 2 (1024), 3 (256) and 4 (256), and double-density sector 1; the files are in a NEWDOS/80-format directory on cylinder 1.

  • Telling the machines apart: the boot path, through a driver sector. The Model I's sector 0 reads sector 4 into 5400h, sector 1 into 5500h and sector 2 into 5700h, and jumps to 560Eh; the Model III's sector 1 selects single density and reads sector 3 into 5400h, then the same sectors 1 and 2, and jumps to 54ABh. Sectors 1 and 2 are one transfer program (SOFTRENDS, INC. FILE TRANSFER SYSTEM) for both machines, and the page at 5400h is the disk driver: sector 4 for the Model I's controller, sector 3 for the Model III's ports.
  • Conflicting files: one set of files. The program's messages show it moving the product's files into memory and then onto the user's own DOS disk (PUT THE COPY OF YOUR DOS INTO DRIVE 0), with the user's DOS booted in between; how it writes them was not traced.

↑ Back to the page index

Cogito: Frogger, Zaxxon and the Game Packs (1983-85)

Cogito's loader is on Frogger (Sega, Radio Shack 26-1959), Zaxxon (26-1956), Game Pack Two (Defense Command and Stellar Escort, 26-1926) and Game Pack Three (Meteor Mission 2 and Cosmic Fighter, 26-1923). Cylinder 0 holds single-density sectors 0 and 100-104 and double-density sector 1; the game is on single-density cylinders numbered 100-109 (S-018). It is the one family that loads a single module for both machines and has that module ask which machine it is on.

  • The boot: the Model I's sector 0 (through 37ECh) and the Model III's sector 1 (through the ports, after selecting single density) do the same thing: read cylinder 0 sectors 100-104 into EC00h-F0FFh, seek to cylinder 2, read sectors 100-109 into E200h-EBFFh, and jump to E200h.
  • Telling the machines apart: the module tests ROM address 0125h (LD A,(0125h) / CP 49h, at E8AAh). Its first call (E906h) returns at once on a Model I, where the Model I boot sector's disk routines are still in memory at 4200h. On a Model III it writes jumps over the same addresses (4248h, 4269h, 4273h, 429Eh and 42B6h) to its own port routines, so the rest of the game calls 4248h-42B6h on either machine and reaches the right controller. The routine that reads the controller's status (E8B0h) makes the same test and reads 37ECh or port F0h; the drive is selected by writing 01h both to 37E1h and to port F4h, which is harmless on either machine.
  • System files: none. Once the one permitted backup (the menu's B) has been made, sector 105 of cylinders 1 and 2 holds C9h and the menu refuses another.

↑ Back to the page index

MultiDOS II / ZEUS and the Computer Shack Games

Vernon Hester's dual-boot diskettes, the "kernel" editions of MultiDOS that he sold to publishers from late 1982, let a product boot on a Model I, a Model III or a Model 4 in Model III mode. The ZEUS Editor Assembler distribution disk (Cosmopolitan Electronics, 1983) and the MultiDOS II beta diskette are in the archive; so are the Computer Shack games (Clash, Cyborg, Convoy, Moon Rover, Digout, Assault!, Fury, Gauntlet, Jovian, Liberator, Stronghold, Time Bandit), whose masters Computer Shack made itself on a Model I with a doubler. Cylinder 0 is the double-density track with single-density sector 0 written over its start (see above), and the rest of the disk is single density. ZEUS and MultiDOS II have an ordinary 2.3-family directory on cylinder 17.

ZEUS and MultiDOS II

  • Telling the machines apart: the boot path only. Each boot sector first checks a byte of itself where it expects to have been loaded (4200h must hold 00h, 4301h must hold FEh) and restarts the machine if it does not find it.
  • The Model I: single-density sector 0 reads cylinder 1 sector 0, the Model I sign-on screen in capitals, onto the screen, then cylinder 1 sector 1 to cylinder 2 sector 3 into 4300h-4FFFh, and jumps to 4319h with 4D00h on the stack.
  • The Model III: double-density sector 1 selects single density, reads cylinder 2 sector 4, the Model III sign-on screen in mixed case, onto the screen, then cylinder 2 sector 5 on into 4E00h down to 4400h, passes on the directory cylinder (byte 2 of its own sector) and a byte from the end of the sector, finds the top of memory (stored at 4411h), and jumps to 4D3Ch.
  • System files: one file, RESIDENT/SYS, is the boot track plus both bodies: in Vernon Hester's words it has both the Model I and Model III code. Its directory entry runs from cylinder 0 for 40 records: record 0 is the Model I boot sector, records 10-23 the Model I screen and code, records 24-36 the Model III screen and code. Every other system file (Doserror/ovl, Allocate/ovl, Command/ovl, Opener/ovl, Closer/ovl, Library1/ext, Library2/ext) appears once in the one directory, so both machines use the same copies; only the resident part differs. Because RESIDENT/SYS starts on the mixed-density cylinder 0, it cannot be copied as a file, by design.

The Computer Shack games

The games use the same cylinder 0 with their own loaders (on Clash: Model I sector 0 reads cylinder 1 sector 0 into 4300h and loads on from its first bytes; Model III sector 1 reads the same sector into 4400h and jumps to 447Eh). Both read a parameter block in cylinder 1 sector 0. The Model I's path then loads cylinder 1 sectors 1-9 and cylinder 2 sectors 0-3 into 4300h-4FFFh, the Model III's cylinders 3 and 4 into 4400h-4FFFh: a disk driver for each machine with the same jump table at 44E1h (read and write a sector by track, sector and drive). Both then load the same game from cylinder 5 on into 5300h-CAFFh. Their message Press ENTER when a MULTIDOS system diskette is in drive zero shows where the code came from. No directory is needed.

↑ Back to the page index

Wayne Westmoreland's Games and Russ Wetmore's Duo-Loader

Wayne Westmoreland's Adventure International games (Armored Patrol, 1981; Eliminator, Rear Guard and Sea Dragon, 1982; all with Terry Gilman on the credit screen) boot through the Duo-Loader, whose boot sector reads This boot and accompanying loader (c)1981 Russ Wetmore Casselberry,FL. Adventure International used it on other self-booting games too: Arex, Stratos, Laser Ball, Search for Elsoliado, Toxic Dumpsite and the Graphic Ventures (Spook House, The Sledge of Rahmul). The disk is single density from cylinder 1 on, ten 256-byte sectors a track; the tracks past the game are often unformatted.

  • Telling the machines apart: the boot path only, with a jump table to hide the difference from the game.
  • The boot: the Model I's sector 0 reads cylinder 1 sectors 0-3 into 4400h-47FFh through 37ECh; the Model III's sector 1 selects single density and reads cylinder 1 sectors 4-7 into the same 4400h-47FFh through the ports. Both jump to 4416h. Each loader prints the game's name and its authors, puts the Adventure International banner (cylinder 1 sectors 8 and 9) on the screen, waits for Press <ENTER> to load program., loads the game from cylinder 2 sector 0 (cylinder 3 on the Graphic Ventures) and jumps to it: on Sea Dragon, 61 sectors to 74EAh; on Armored Patrol, 78 sectors to 70E8h; on Rear Guard, 61 sectors to 77A5h; on Eliminator, 54 sectors to 83ECh.
  • One game, two drivers: both loaders begin with the same table of six jumps at 4400h-4411h, each to that loader's own routines, and the game calls the disk only through it: Sea Dragon reads and writes its high-score sector (cylinder 10 sector 0) through 4403h (read) and 4406h (write), with the sector count in 4414h. Byte 4415h is 01h in the Model I's loader and 03h in the Model III's; Sea Dragon's game does not read it.
  • System files: none.

↑ Back to the page index

Other Dual-Boot Families

Cornsoft (Scarfman, Frogger, Crazy Painter, 1981-82)

Two builds in two densities. Each boot sector begins with the same three-entry table (a jump over it, a byte reader and a sector reader) and its second stage calls its own boot sector's routines through it. The Model I's single-density sector 0 reads ten sectors of single-density cylinder 1 into 4600h; the Model III's double-density sector 1 reads eighteen sectors of double-density cylinder 2 into 4600h. On Scarfman the rest of the disk is single-density cylinders 5 and 6 and double-density cylinders 7 and 8, which only the Model III can read; the cylinders between are unformatted. No directory.

Dan Foy's Arranger (1983)

One program, in double density. The Model I's sector 0 writes FFh, the doubler's double-density command, to 37ECh and reads 88 double-density sectors from cylinder 1 sector 0 (18 a track, numbered 0-17) and six from cylinder 6 into 4400h; the Model III's sector 1 reads the same sectors through the ports and jumps to the same 4400h. The program then tests ROM address 0054h (LD A,(0054h) / DEC A: zero on a Model I) and sets a flag for the Model III. A Model I without a double-density adapter cannot run it.

Soft Sector Marketing and Factory Programming (John Weaver Jr's AUTODOS, 1981-83)

Caterpillar, Chicken, Rally, Outhouse, Sneak Thief and Alien Defense with Talking. The Model I's sector 0 (00 FE 11 31 F6 41 CD C9 01) takes a starting track and sector from the end of the sector (42FEh) and loads a /CMD module through 37ECh; the Model III's sector 1 does the same through the ports from 43FEh. The two modules are separate builds (on Chicken the Model I's on cylinder 7 and the Model III's on cylinder 2). On some copies of Caterpillar the modules are ordinary files in a directory (CATER1/CMD, CATER3/CMD): two names for the two builds.

Acorn Software (Pigskin, Space Rocks) and Liberty Software (Alien Armada)

The Model I's sector 0 times the drive with a Read Track command; the Model III's sector 1 is a port version of it; the game is on single-density tracks with F8 data marks. No directory.

Jonathan Yarden's 3-D Tic-Tac-Toe (The Alternate Source, 1983)

Cylinder 0 holds single-density sectors 1 and 0 and double-density sector 1. The Model III's sector 1 copies a 38-byte stub to 4140h, selects single density and reads sector 1 again, now the single-density sector 1, into 4300h: the sector register still holds the 1 the ROM put there. That sector is the port version of the Model I's sector 0, and both then load one module from cylinder 2 sector 0.

Single titles

Adventure International's SC-78503 Starfighter (1981) pairs a single-density sector 0 (SHUTTLE NOW ARRIVING...) with a port version in double-density sector 1, with no directory. Yield and Pulsar (James Weaver Jr, 1983), whose cylinder 0 holds 512-byte sectors in both densities, has not been traced.

↑ Back to the page index