Compute Type-In compilation dsk images

[Compute Type-In compilation dsk images]

I'll add my thanks as well, CaptainBreakout! Great work!

[Corrupted prodos image?]

The file is just dumped in DOS-order, as opposed to ProDOS order. In ProDOS order, the directory block 2 would start at offset 0x400 in the file, but with DOS-order it starts at 0xB00. Basically, within each track, the 256-byte sectors are rearranged as 0, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 15, which means ProDOS blocks 0-7 are composed of sectors:

block 0: 0, 14

block 1: 13, 12

block 2: 11, 10

block 3: 9, 8

block 4: 7, 6

block 5: 5, 4

block 6: 3, 2

block 7: 1, 15

 

I'm surprised Ciderpress doesn't recognize it.

 

Here's the catalog:

/EXAMPLES
*PRODOS SYS $2000 30 14848 1984-Sep-18 00:00
*BASIC.SYSTEM SYS $2000 21 10240 1984-Jun-18 00:00
*STARTUP BAS $0801 7 2794 1984-Jul-26 09:12
*HELP BIN $2000 5 1537 1983-Oct-01 00:00
*HELPSCREENS TXT $0200 60 12358656 1983-Oct-01 00:00
*PRACTICE DIR 1 512 1983-Oct-01 00:00
*PROGRAMS DIR 3 1536 1983-Oct-01 00:00
*DATA DIR 1 512 1987-Oct-16 23:11
*EXTRAS DIR 1 512 1983-Oct-01 00:00
*DIRECTORY DIR 1 512 1983-Oct-01 00:00
Free space: 34 blocks

Yes, HELPSCREENS is a sparse file.