salfter/fluxengine
1
0
Fork 0
mirror of https://github.com/davidgiven/fluxengine.git synced 2025-10-31 11:17:01 -07:00
Code Issues Packages Projects Releases Wiki Activity

Prefer IMG for Micropolis, and use a vgi profile to swap format

Browse Source
This commit is contained in:
Eric Anderson
2022-01-29 10:05:54 -07:00
parent bd854d29a4
commit bc9b761903
8 changed files with 68 additions and 103 deletions
Download Patch File Download Diff File Expand all files Collapse all files

43
doc/disk-micropolis.md
View File

@@ -29,24 +29,10 @@ fluxengine read micropolis315 # single-sided Mod II
fluxengine read micropolis630 # double-sided Mod II
```
You should end up with a `micropolis.vgi` which is 198000, 396000, 338800, or
677600 bytes. Each sector in VGI consumes 275 bytes, to retain the full
information stored on disk.
It's also possible to output to IMG, which is more suitable for generic tooling
than emulation or preservation:
```
fluxengine read micropolis -c 0-34 --image_writer.img.tracks=35 -h 0 --image_writer.img.sides=1 # single-sided Mod I
fluxengine read micropolis -c 0-34 --image_writer.img.tracks=35 # double-sided Mod I
fluxengine read micropolis -h 0 --image_writer.img.sides=1 # single-sided Mod II
fluxengine read micropolis # double-sided Mod II
```
You should end up with a `micropolis.img` which is 143360, 286720, 315392, or
630784 bytes long. The image is written in CHS order, but HCS is generally used
by CP/M tools so double-sided disk images may need to be post-processed.
Half-full double-sided disks can be read as single-sided disks to work around
the problem.
You should end up with a `micropolis.img` of the corresponding size. The image
is written in CHS order, but HCS is generally used by CP/M tools so
double-sided disk images may need to be post-processed. Half-full double-sided
disks can be read as single-sided disks to work around the problem.
The [CP/M BIOS](https://www.seasip.info/Cpm/bios.html) defined SELDSK, SETTRK,
and SETSEC, but no function to select the head/side. Double-sided floppies
@@ -55,6 +41,19 @@ twice the number of tracks, HCS; the second side's tracks in opposite order
logically followed the first side (e.g., tracks 77-153). Micropolis disks
tended to be the latter.
It's also possible to output to VGI, which retains OS-specific "user data" and
machine-specific ECC. Add "vgi" to the command line after the chosen Micropolis
profile:
```
fluxengine read micropolis143 vgi # single-sided Mod I
fluxengine read micropolis287 vgi # double-sided Mod I
fluxengine read micropolis315 vgi # single-sided Mod II
fluxengine read micropolis630 vgi # double-sided Mod II
```
You should end up with a `micropolis.vgi` instead. The format is well-defined
for double-sided disks so post-processing is not necessary.
Writing disks
-------------
@@ -66,10 +65,10 @@ fluxengine write micropolis287 # double-sided Mod I
fluxengine write micropolis315 # single-sided Mod II
fluxengine write micropolis630 # double-sided Mod II
fluxengine write micropolis -c 0-34 --image_reader.img.tracks=35 -h 0 --image_reader.img.sides=1 # single-sided Mod I
fluxengine write micropolis -c 0-34 --image_reader.img.tracks=35 # double-sided Mod I
fluxengine write micropolis -h 0 --image_reader.img.sides=1 # single-sided Mod II
fluxengine write micropolis # double-sided Mod II using IMG
fluxengine write micropolis143 vgi # single-sided Mod I
fluxengine write micropolis287 vgi # double-sided Mod I
fluxengine write micropolis315 vgi # single-sided Mod II
fluxengine write micropolis630 vgi # double-sided Mod II
```
Useful references