On Sunday, 8 May 2022 at 02:37:50 UTC+1, Nathanael wrote:
> Good detective work:)
>
> V59 is done. Only four more files to go. Thanks.
> On Sunday, May 8, 2022 at 1:56:30 AM UTC+8, Martin wrote:
> > Am 05/07/2022 07:18 PM, Martin schrieb:
> > > Am 05/07/2022 02:25 PM, Nathanael schrieb:
> > >> But I’m still not following your discussion on vol 59’s READ.ME.
> > >>
> > >>> padding with a single CTRL-Z and the rest of the block from 1024 Bytes above
> > >>
> > >> The READ.ME from vol 59 of CPMDOSGG already ends with 40 bytes of 1AH, so did you mean adding a Ctrl-Z to a different file?
> > >>
> > >> I also don’t know what “the rest of the block from 1024” means.
> > >>
> > >> —nathanael
> > >>
> > >
> > Forget it :-)
> >
> > Found the missing READ.ME in DOSGG CPM06/627, but named #HISTORY.018.
> >
> > This file *IS* the missing READ.ME.
> >
> > Copy, rename, done!
Nathanael
Which files remain unresolved?
It would also be good if you could create an ISO file of the cleaned-up archive.
regards
Mark

I’ve only got one file left to resolve: Vol 54 TTBOOT.ASM.

After that, I’m going to focus a bit more on volume content. For example, there are numerous instances where a volume contains a file, like CRC.COM or USQ.COM, which isn’t listed in -CATALOG.xxx. How strictly should I adhere to the -CATALOG file listings?

Yes, when I’m satisfied, I’ll create an ISO image for download.

On Monday, May 9, 2022 at 11:19:34 PM UTC+8, Mark Ogden wrote:
> On Sunday, 8 May 2022 at 02:37:50 UTC+1, Nathanael wrote:
> > Good detective work:)
> >
> > V59 is done. Only four more files to go. Thanks.
> > On Sunday, May 8, 2022 at 1:56:30 AM UTC+8, Martin wrote:
> > > Am 05/07/2022 07:18 PM, Martin schrieb:
> > > > Am 05/07/2022 02:25 PM, Nathanael schrieb:
> > > >> But I’m still not following your discussion on vol 59’s READ.ME.
> > > >>
> > > >>> padding with a single CTRL-Z and the rest of the block from 1024 Bytes above
> > > >>
> > > >> The READ.ME from vol 59 of CPMDOSGG already ends with 40 bytes of 1AH, so did you mean adding a Ctrl-Z to a different file?
> > > >>
> > > >> I also don’t know what “the rest of the block from 1024” means.
> > > >>
> > > >> —nathanael
> > > >>
> > > >
> > > Forget it :-)
> > >
> > > Found the missing READ.ME in DOSGG CPM06/627, but named #HISTORY.018.
> > >
> > > This file *IS* the missing READ.ME.
> > >
> > > Copy, rename, done!
> Nathanael
> Which files remain unresolved?
> It would also be good if you could create an ISO file of the cleaned-up archive.
> regards
> Mark

Oh, and I’m keeping the build script updated on GitHub just in case anyone can’t wait for the ISO :) and wants to build it themselves. Currently the script still flags around 20 CRC mismatches, but except for TTBOOT.ASM, they’re all false flags due to bugs in the code I haven’t bothered to fix.

https://github.com/CPMArchives/SIGM

On Tuesday, May 10, 2022 at 10:43:47 AM UTC+8, Nathanael wrote:
> I’ve only got one file left to resolve: Vol 54 TTBOOT.ASM.
>
> After that, I’m going to focus a bit more on volume content. For example, there are numerous instances where a volume contains a file, like CRC.COM or USQ.COM, which isn’t listed in -CATALOG.xxx. How strictly should I adhere to the -CATALOG file listings?
>
> Yes, when I’m satisfied, I’ll create an ISO image for download.
> On Monday, May 9, 2022 at 11:19:34 PM UTC+8, Mark Ogden wrote:
> > On Sunday, 8 May 2022 at 02:37:50 UTC+1, Nathanael wrote:
> > > Good detective work:)
> > >
> > > V59 is done. Only four more files to go. Thanks.
> > > On Sunday, May 8, 2022 at 1:56:30 AM UTC+8, Martin wrote:
> > > > Am 05/07/2022 07:18 PM, Martin schrieb:
> > > > > Am 05/07/2022 02:25 PM, Nathanael schrieb:
> > > > >> But I’m still not following your discussion on vol 59’s READ.ME.
> > > > >>
> > > > >>> padding with a single CTRL-Z and the rest of the block from 1024 Bytes above
> > > > >>
> > > > >> The READ.ME from vol 59 of CPMDOSGG already ends with 40 bytes of 1AH, so did you mean adding a Ctrl-Z to a different file?
> > > > >>
> > > > >> I also don’t know what “the rest of the block from 1024” means.
> > > > >>
> > > > >> —nathanael
> > > > >>
> > > > >
> > > > Forget it :-)
> > > >
> > > > Found the missing READ.ME in DOSGG CPM06/627, but named #HISTORY.018.
> > > >
> > > > This file *IS* the missing READ.ME.
> > > >
> > > > Copy, rename, done!
> > Nathanael
> > Which files remain unresolved?
> > It would also be good if you could create an ISO file of the cleaned-up archive.
> > regards
> > Mark

On Tuesday, 10 May 2022 at 03:59:30 UTC+1, Nathanael wrote:
> Oh, and I’m keeping the build script updated on GitHub just in case anyone can’t wait for the ISO :) and wants to build it themselves. Currently the script still flags around 20 CRC mismatches, but except for TTBOOT.ASM, they’re all false flags due to bugs in the code I haven’t bothered to fix.
>
> https://github.com/CPMArchives/SIGM
> On Tuesday, May 10, 2022 at 10:43:47 AM UTC+8, Nathanael wrote:
> > I’ve only got one file left to resolve: Vol 54 TTBOOT.ASM.
> >
> > After that, I’m going to focus a bit more on volume content. For example, there are numerous instances where a volume contains a file, like CRC.COM or USQ.COM, which isn’t listed in -CATALOG.xxx. How strictly should I adhere to the -CATALOG file listings?
> >
> > Yes, when I’m satisfied, I’ll create an ISO image for download.
> > On Monday, May 9, 2022 at 11:19:34 PM UTC+8, Mark Ogden wrote:
> > > On Sunday, 8 May 2022 at 02:37:50 UTC+1, Nathanael wrote:
> > > > Good detective work:)
> > > >
> > > > V59 is done. Only four more files to go. Thanks.
> > > > On Sunday, May 8, 2022 at 1:56:30 AM UTC+8, Martin wrote:
> > > > > Am 05/07/2022 07:18 PM, Martin schrieb:
> > > > > > Am 05/07/2022 02:25 PM, Nathanael schrieb:
> > > > > >> But I’m still not following your discussion on vol 59’s READ.ME.
> > > > > >>
> > > > > >>> padding with a single CTRL-Z and the rest of the block from 1024 Bytes above
> > > > > >>
> > > > > >> The READ.ME from vol 59 of CPMDOSGG already ends with 40 bytes of 1AH, so did you mean adding a Ctrl-Z to a different file?
> > > > > >>
> > > > > >> I also don’t know what “the rest of the block from 1024” means.
> > > > > >>
> > > > > >> —nathanael
> > > > > >>
> > > > > >
> > > > > Forget it :-)
> > > > >
> > > > > Found the missing READ.ME in DOSGG CPM06/627, but named #HISTORY.018.
> > > > >
> > > > > This file *IS* the missing READ.ME.
> > > > >
> > > > > Copy, rename, done!
> > > Nathanael
> > > Which files remain unresolved?
> > > It would also be good if you could create an ISO file of the cleaned-up archive.
> > > regards
> > > Mark
Nathanael
Looks like the first sector of TTBOOT.ASM is corrupted, although I suspect all/most was comments
Mark

On Tuesday, May 10, 2022 at 4:09:08 PM UTC+8, Mark Ogden wrote:
> On Tuesday, 10 May 2022 at 03:59:30 UTC+1, Nathanael wrote:
> > Oh, and I’m keeping the build script updated on GitHub just in case anyone can’t wait for the ISO :) and wants to build it themselves. Currently the script still flags around 20 CRC mismatches, but except for TTBOOT.ASM, they’re all false flags due to bugs in the code I haven’t bothered to fix.
> >
> > https://github.com/CPMArchives/SIGM
> > On Tuesday, May 10, 2022 at 10:43:47 AM UTC+8, Nathanael wrote:
> > > I’ve only got one file left to resolve: Vol 54 TTBOOT.ASM.
> > >
> > > After that, I’m going to focus a bit more on volume content. For example, there are numerous instances where a volume contains a file, like CRC.COM or USQ.COM, which isn’t listed in -CATALOG.xxx. How strictly should I adhere to the -CATALOG file listings?
> > >
> > > Yes, when I’m satisfied, I’ll create an ISO image for download.
> > > On Monday, May 9, 2022 at 11:19:34 PM UTC+8, Mark Ogden wrote:
> > > > On Sunday, 8 May 2022 at 02:37:50 UTC+1, Nathanael wrote:
> > > > > Good detective work:)
> > > > >
> > > > > V59 is done. Only four more files to go. Thanks.
> > > > > On Sunday, May 8, 2022 at 1:56:30 AM UTC+8, Martin wrote:
> > > > > > Am 05/07/2022 07:18 PM, Martin schrieb:
> > > > > > > Am 05/07/2022 02:25 PM, Nathanael schrieb:
> > > > > > >> But I’m still not following your discussion on vol 59’s READ.ME.
> > > > > > >>
> > > > > > >>> padding with a single CTRL-Z and the rest of the block from 1024 Bytes above
> > > > > > >>
> > > > > > >> The READ.ME from vol 59 of CPMDOSGG already ends with 40 bytes of 1AH, so did you mean adding a Ctrl-Z to a different file?
> > > > > > >>
> > > > > > >> I also don’t know what “the rest of the block from 1024” means.
> > > > > > >>
> > > > > > >> —nathanael
> > > > > > >>
> > > > > > >
> > > > > > Forget it :-)
> > > > > >
> > > > > > Found the missing READ.ME in DOSGG CPM06/627, but named #HISTORY.018.
> > > > > >
> > > > > > This file *IS* the missing READ.ME.
> > > > > >
> > > > > > Copy, rename, done!
> > > > Nathanael
> > > > Which files remain unresolved?
> > > > It would also be good if you could create an ISO file of the cleaned-up archive.
> > > > regards
> > > > Mark
> Nathanael
> Looks like the first sector of TTBOOT.ASM is corrupted, although I suspect all/most was comments
> Mark

Oddly, it appears zero.ASM is similarly corrupted, yet its CRC matches that in -CATALOG.054. So the corruption appears to go all the way back to the original.

Hey, Steven — when you’ve got the time, if you’ve got a copy of vol 54, could you take a look at the files to see if your copies are corrupted?

On Tuesday, May 10, 2022 at 9:25:08 PM UTC+8, Nathanael wrote:
> On Tuesday, May 10, 2022 at 4:09:08 PM UTC+8, Mark Ogden wrote:
> > On Tuesday, 10 May 2022 at 03:59:30 UTC+1, Nathanael wrote:
> > > Oh, and I’m keeping the build script updated on GitHub just in case anyone can’t wait for the ISO :) and wants to build it themselves. Currently the script still flags around 20 CRC mismatches, but except for TTBOOT.ASM, they’re all false flags due to bugs in the code I haven’t bothered to fix.
> > >
> > > https://github.com/CPMArchives/SIGM
> > > On Tuesday, May 10, 2022 at 10:43:47 AM UTC+8, Nathanael wrote:
> > > > I’ve only got one file left to resolve: Vol 54 TTBOOT.ASM.
> > > >
> > > > After that, I’m going to focus a bit more on volume content.. For example, there are numerous instances where a volume contains a file, like CRC.COM or USQ.COM, which isn’t listed in -CATALOG.xxx. How strictly should I adhere to the -CATALOG file listings?
> > > >
> > > > Yes, when I’m satisfied, I’ll create an ISO image for download.
> > > > On Monday, May 9, 2022 at 11:19:34 PM UTC+8, Mark Ogden wrote:
> > > > > On Sunday, 8 May 2022 at 02:37:50 UTC+1, Nathanael wrote:
> > > > > > Good detective work:)
> > > > > >
> > > > > > V59 is done. Only four more files to go. Thanks.
> > > > > > On Sunday, May 8, 2022 at 1:56:30 AM UTC+8, Martin wrote:
> > > > > > > Am 05/07/2022 07:18 PM, Martin schrieb:
> > > > > > > > Am 05/07/2022 02:25 PM, Nathanael schrieb:
> > > > > > > >> But I’m still not following your discussion on vol 59’s READ.ME.
> > > > > > > >>
> > > > > > > >>> padding with a single CTRL-Z and the rest of the block from 1024 Bytes above
> > > > > > > >>
> > > > > > > >> The READ.ME from vol 59 of CPMDOSGG already ends with 40 bytes of 1AH, so did you mean adding a Ctrl-Z to a different file?
> > > > > > > >>
> > > > > > > >> I also don’t know what “the rest of the block from 1024” means.
> > > > > > > >>
> > > > > > > >> —nathanael
> > > > > > > >>
> > > > > > > >
> > > > > > > Forget it :-)
> > > > > > >
> > > > > > > Found the missing READ.ME in DOSGG CPM06/627, but named #HISTORY.018.
> > > > > > >
> > > > > > > This file *IS* the missing READ.ME.
> > > > > > >
> > > > > > > Copy, rename, done!
> > > > > Nathanael
> > > > > Which files remain unresolved?
> > > > > It would also be good if you could create an ISO file of the cleaned-up archive.
> > > > > regards
> > > > > Mark
> > Nathanael
> > Looks like the first sector of TTBOOT.ASM is corrupted, although I suspect all/most was comments
> > Mark
> Oddly, it appears zero.ASM is similarly corrupted, yet its CRC matches that in -CATALOG.054. So the corruption appears to go all the way back to the original.
>
> Hey, Steven — when you’ve got the time, if you’ve got a copy of vol 54, could you take a look at the files to see if your copies are corrupted?
..
ZCPR.ASM. Stupid spellchecker.

On Tuesday, 10 May 2022 at 14:27:42 UTC+1, Nathanael wrote:
> On Tuesday, May 10, 2022 at 9:25:08 PM UTC+8, Nathanael wrote:
> > On Tuesday, May 10, 2022 at 4:09:08 PM UTC+8, Mark Ogden wrote:
> > > On Tuesday, 10 May 2022 at 03:59:30 UTC+1, Nathanael wrote:
> > > > Oh, and I’m keeping the build script updated on GitHub just in case anyone can’t wait for the ISO :) and wants to build it themselves. Currently the script still flags around 20 CRC mismatches, but except for TTBOOT.ASM, they’re all false flags due to bugs in the code I haven’t bothered to fix.
> > > >
> > > > https://github.com/CPMArchives/SIGM
> > > > On Tuesday, May 10, 2022 at 10:43:47 AM UTC+8, Nathanael wrote:
> > > > > I’ve only got one file left to resolve: Vol 54 TTBOOT.ASM..
> > > > >
> > > > > After that, I’m going to focus a bit more on volume content. For example, there are numerous instances where a volume contains a file, like CRC.COM or USQ.COM, which isn’t listed in -CATALOG.xxx. How strictly should I adhere to the -CATALOG file listings?
> > > > >
> > > > > Yes, when I’m satisfied, I’ll create an ISO image for download.
> > > > > On Monday, May 9, 2022 at 11:19:34 PM UTC+8, Mark Ogden wrote:
> > > > > > On Sunday, 8 May 2022 at 02:37:50 UTC+1, Nathanael wrote:
> > > > > > > Good detective work:)
> > > > > > >
> > > > > > > V59 is done. Only four more files to go. Thanks.
> > > > > > > On Sunday, May 8, 2022 at 1:56:30 AM UTC+8, Martin wrote:
> > > > > > > > Am 05/07/2022 07:18 PM, Martin schrieb:
> > > > > > > > > Am 05/07/2022 02:25 PM, Nathanael schrieb:
> > > > > > > > >> But I’m still not following your discussion on vol 59’s READ.ME.
> > > > > > > > >>
> > > > > > > > >>> padding with a single CTRL-Z and the rest of the block from 1024 Bytes above
> > > > > > > > >>
> > > > > > > > >> The READ.ME from vol 59 of CPMDOSGG already ends with 40 bytes of 1AH, so did you mean adding a Ctrl-Z to a different file?
> > > > > > > > >>
> > > > > > > > >> I also don’t know what “the rest of the block from 1024” means.
> > > > > > > > >>
> > > > > > > > >> —nathanael
> > > > > > > > >>
> > > > > > > > >
> > > > > > > > Forget it :-)
> > > > > > > >
> > > > > > > > Found the missing READ.ME in DOSGG CPM06/627, but named #HISTORY.018.
> > > > > > > >
> > > > > > > > This file *IS* the missing READ.ME.
> > > > > > > >
> > > > > > > > Copy, rename, done!
> > > > > > Nathanael
> > > > > > Which files remain unresolved?
> > > > > > It would also be good if you could create an ISO file of the cleaned-up archive.
> > > > > > regards
> > > > > > Mark
> > > Nathanael
> > > Looks like the first sector of TTBOOT.ASM is corrupted, although I suspect all/most was comments
> > > Mark
> > Oddly, it appears zero.ASM is similarly corrupted, yet its CRC matches that in -CATALOG.054. So the corruption appears to go all the way back to the original.
> >
> > Hey, Steven — when you’ve got the time, if you’ve got a copy of vol 54, could you take a look at the files to see if your copies are corrupted?
> .
> ZCPR.ASM. Stupid spellchecker.
Nathanael
The ZCPR.ASM in cpmdosgg/CPM10/1054 is fine
Mark

On Tuesday, May 10, 2022 at 10:19:28 PM UTC+8, Mark Ogden wrote:
> On Tuesday, 10 May 2022 at 14:27:42 UTC+1, Nathanael wrote:
> > On Tuesday, May 10, 2022 at 9:25:08 PM UTC+8, Nathanael wrote:
> > > On Tuesday, May 10, 2022 at 4:09:08 PM UTC+8, Mark Ogden wrote:
> > > > On Tuesday, 10 May 2022 at 03:59:30 UTC+1, Nathanael wrote:
> > > > > Oh, and I’m keeping the build script updated on GitHub just in case anyone can’t wait for the ISO :) and wants to build it themselves. Currently the script still flags around 20 CRC mismatches, but except for TTBOOT.ASM, they’re all false flags due to bugs in the code I haven’t bothered to fix.
> > > > >
> > > > > https://github.com/CPMArchives/SIGM
> > > > > On Tuesday, May 10, 2022 at 10:43:47 AM UTC+8, Nathanael wrote:
> > > > > > I’ve only got one file left to resolve: Vol 54 TTBOOT.ASM.
> > > > > >
> > > > > > After that, I’m going to focus a bit more on volume content. For example, there are numerous instances where a volume contains a file, like CRC.COM or USQ.COM, which isn’t listed in -CATALOG.xxx. How strictly should I adhere to the -CATALOG file listings?
> > > > > >
> > > > > > Yes, when I’m satisfied, I’ll create an ISO image for download.
> > > > > > On Monday, May 9, 2022 at 11:19:34 PM UTC+8, Mark Ogden wrote:
> > > > > > > On Sunday, 8 May 2022 at 02:37:50 UTC+1, Nathanael wrote:
> > > > > > > > Good detective work:)
> > > > > > > >
> > > > > > > > V59 is done. Only four more files to go. Thanks.
> > > > > > > > On Sunday, May 8, 2022 at 1:56:30 AM UTC+8, Martin wrote:
> > > > > > > > > Am 05/07/2022 07:18 PM, Martin schrieb:
> > > > > > > > > > Am 05/07/2022 02:25 PM, Nathanael schrieb:
> > > > > > > > > >> But I’m still not following your discussion on vol 59’s READ.ME.
> > > > > > > > > >>
> > > > > > > > > >>> padding with a single CTRL-Z and the rest of the block from 1024 Bytes above
> > > > > > > > > >>
> > > > > > > > > >> The READ.ME from vol 59 of CPMDOSGG already ends with 40 bytes of 1AH, so did you mean adding a Ctrl-Z to a different file?
> > > > > > > > > >>
> > > > > > > > > >> I also don’t know what “the rest of the block from 1024” means.
> > > > > > > > > >>
> > > > > > > > > >> —nathanael
> > > > > > > > > >>
> > > > > > > > > >
> > > > > > > > > Forget it :-)
> > > > > > > > >
> > > > > > > > > Found the missing READ.ME in DOSGG CPM06/627, but named #HISTORY.018.
> > > > > > > > >
> > > > > > > > > This file *IS* the missing READ.ME.
> > > > > > > > >
> > > > > > > > > Copy, rename, done!
> > > > > > > Nathanael
> > > > > > > Which files remain unresolved?
> > > > > > > It would also be good if you could create an ISO file of the cleaned-up archive.
> > > > > > > regards
> > > > > > > Mark
> > > > Nathanael
> > > > Looks like the first sector of TTBOOT.ASM is corrupted, although I suspect all/most was comments
> > > > Mark
> > > Oddly, it appears zero.ASM is similarly corrupted, yet its CRC matches that in -CATALOG.054. So the corruption appears to go all the way back to the original.
> > >
> > > Hey, Steven — when you’ve got the time, if you’ve got a copy of vol 54, could you take a look at the files to see if your copies are corrupted?
> > .
> > ZCPR.ASM. Stupid spellchecker.
> Nathanael
> The ZCPR.ASM in cpmdosgg/CPM10/1054 is fine
> Mark

Yeah, it is. I was looking at the wrong one. So it’s just TTBOOT.ASM. I’ve so far been unable to locate a replacement.

I have a copy of SIGM in /home/larry/jonv/repositories/Walnut_Creek_CPM/WalnutCreek/SIMTEL/SIGM/VOLS000/VOL054/
February 2 1982 hat has the following crc:

Sig/M Volume 54 Z80 Command Processor Replacement
Capture CONIN and CONOUT Onto Disk
2.2 Bios For Thinker Toys

-CATALOG.054 contents of Sig/M volume 54
released February 2, 1982

index name size crc description

54.01 BDOSLOC .ASM 2K EB D4 Z80 Command Processor
54.02 DISK .DIR 1K 5C CE CCP 2.2 Replacement
54.03 READ .ME 6K D7 AB /
54.04 SIG/M .SUB 4K 15 86 /
54.05 ZCPR .ASM 51K 7A 46 /
54.06 ZCPR .DOC 45K 94 B7 /
54.07 ZCPR .HLP 15K 26 9D /
54.08 ZCPR .WS 40K A2 C2 /
54.09 I/O-CAP .ADD 1K 74 31 Capture CONIN and CONOUT
54.10 I/O-CAP .ASM 19K A2 1A onto a disk file
54.11 TTBOOT .ASM 3K C9 01 2.2 Bios for Thinker Toys
54.12 TTCBIOS .ASM 7K B5 80 /
54.13 TTSDDJ .HLP 4K 93 E8 /

Copyright (c) 1982 by Sig/M-Amateur Computer Group
of New Jersey Inc., Box 97, Iselin NJ, 08830-0097

Larry

On Wednesday, May 11, 2022 at 3:57:58 AM UTC+8, ldkr...@gmail.com wrote:
> I have a copy of SIGM in /home/larry/jonv/repositories/Walnut_Creek_CPM/WalnutCreek/SIMTEL/SIGM/VOLS000/VOL054/
> February 2 1982 hat has the following crc:
>
> Sig/M Volume 54 Z80 Command Processor Replacement
> Capture CONIN and CONOUT Onto Disk
> 2.2 Bios For Thinker Toys
>
> -CATALOG.054 contents of Sig/M volume 54
> released February 2, 1982
>
> index name size crc description
>
> 54.01 BDOSLOC .ASM 2K EB D4 Z80 Command Processor
> 54.02 DISK .DIR 1K 5C CE CCP 2.2 Replacement
> 54.03 READ .ME 6K D7 AB /
> 54.04 SIG/M .SUB 4K 15 86 /
> 54.05 ZCPR .ASM 51K 7A 46 /
> 54.06 ZCPR .DOC 45K 94 B7 /
> 54.07 ZCPR .HLP 15K 26 9D /
> 54.08 ZCPR .WS 40K A2 C2 /
> 54.09 I/O-CAP .ADD 1K 74 31 Capture CONIN and CONOUT
> 54.10 I/O-CAP .ASM 19K A2 1A onto a disk file
> 54.11 TTBOOT .ASM 3K C9 01 2.2 Bios for Thinker Toys
> 54.12 TTCBIOS .ASM 7K B5 80 /
> 54.13 TTSDDJ .HLP 4K 93 E8 /
>
> Copyright (c) 1982 by Sig/M-Amateur Computer Group
> of New Jersey Inc., Box 97, Iselin NJ, 08830-0097
>
>
> Larry
Yes, 0catalog..054 records C901 as the CRC, but unfortunately the actual file on the image has a CRC of 7A37 and exhibits the same corruption.

I have a local copy of the SIGM archive. I've zipped it up and put it here: https://vintagecomputer.ca/files/SIGM/

You can find TTBOOT.ASM in there if you still need it. I assume it is complete.

Hope this helps,
Santo

> Yes, 0catalog..054 records C901 as the CRC, but unfortunately the actual file on the image has a CRC of 7A37 and exhibits the same corruption.

Thank you for the effort. What you have appears to be a duplicate of the SIGM content from the Walnut Creek CD. Unfortunately, TTBOOT.ASM exhibits the same corruption.

On Wednesday, May 11, 2022 at 10:26:10 AM UTC+8, santo.n...@gmail.com wrote:
> I have a local copy of the SIGM archive. I've zipped it up and put it here: https://vintagecomputer.ca/files/SIGM/
>
> You can find TTBOOT.ASM in there if you still need it. I assume it is complete.
>
> Hope this helps,
> Santo
> > Yes, 0catalog..054 records C901 as the CRC, but unfortunately the actual file on the image has a CRC of 7A37 and exhibits the same corruption.

I’m in the process of manually verifying that only files that appear in -CATALOG and/or CRCKFILE listings are included in the rebuilt volumes. After that, I think I’m going to call this done.

As to file dates, where the -CATALOG.xxx lists a release date, I’ve used that. Some volumes specify only the month; others give no date at all.. Often it seems as if the volume release dates corresponded with the ACGNJ monthly meeting. Does anyone have info available on what those dates were?

That is unfortunate. Worst case scenario, I have the "SIG/M Volume 54" 8" disk from 02/19/81, if needed. I would just have to re-create my 8" disk archiving set up (which is a bit painful to set up) and figure out how to configure ImageDisk properly for this disk type. Picture of disk label here: https://vintagecomputer.ca/files/SIGM/IMG-3638.jpeg

Santo

On Wednesday, May 11, 2022 at 7:29:46 PM UTC+8, santo.n...@gmail.com wrote:
> That is unfortunate. Worst case scenario, I have the "SIG/M Volume 54" 8" disk from 02/19/81, if needed. I would just have to re-create my 8" disk archiving set up (which is a bit painful to set up) and figure out how to configure ImageDisk properly for this disk type. Picture of disk label here: https://vintagecomputer.ca/files/SIGM/IMG-3638.jpeg
>
> Santo

OK, now that just brings up too many questions. To begin with, the date. According to -CATALOG.054, volume 54 was released to February 1982, yet your disk label is dated a year earlier. Why? By my info, in February ‘81 ACGNJ was releasing volume 10.

What’s the provenance of your disk set ? Are they originals? How many volumes do you have?

It’s a big ask, I know, but if there’s anyway you could image what you’ve got as time permits, IMD images of original discs would be the Holy Grail of what I’m trying to do here.

Thanks for posting that image. I am tantalized. :-)

On Wednesday, May 11, 2022 at 9:02:57 PM UTC+8, Nathanael wrote:
> On Wednesday, May 11, 2022 at 7:29:46 PM UTC+8, santo.n...@gmail.com wrote:
> > That is unfortunate. Worst case scenario, I have the "SIG/M Volume 54" 8" disk from 02/19/81, if needed. I would just have to re-create my 8" disk archiving set up (which is a bit painful to set up) and figure out how to configure ImageDisk properly for this disk type. Picture of disk label here: https://vintagecomputer.ca/files/SIGM/IMG-3638.jpeg
> >
> > Santo
> OK, now that just brings up too many questions. To begin with, the date. According to -CATALOG.054, volume 54 was released to February 1982, yet your disk label is dated a year earlier. Why? By my info, in February ‘81 ACGNJ was releasing volume 10.
>
> What’s the provenance of your disk set ? Are they originals? How many volumes do you have?
>
> It’s a big ask, I know, but if there’s anyway you could image what you’ve got as time permits, IMD images of original discs would be the Holy Grail of what I’m trying to do here.
>
> Thanks for posting that image. I am tantalized. :-)

One more question. Is that a TRS-80 Model IV I see in the background?

I had to sort through the disks but unfortunately, I only have 227 8" disks with a small number missing and some duplicates. They are a backup with various labels and of disks have two disk archives on them. I should set up a CP/M system to check these disks. These disks must have been reused at some point. Here is what that looks like: https://vintagecomputer.ca/files/SIGM/IMG-3639.jpeg

These disks came from Canada Remote Systems who was originally Toronto RCP/M. They ran a large BBS and had their own CP/M archive that I have posted here: https://vintagecomputer.ca/files/Canada%20Remote%20Systems%20CPM%20Archive/. I have a couple of backups of this; one on CD and one on ZIP disk. You can see the SIG/M backup was dated July 4, 1983 if the first disk is accurate. Unfortunately, there must have been another box of disks that I didn't get.

Yes, that is a TRS-80 Model 4 next to the box. I also have a NEC APC with 8" drives and I think I have CP/M 86 for it but that computer needs work :(.. I wonder if I could have used that to browse these disks?

I will look into my 8" archiving system. If I recall, my Adaptec SCSI controller (with the better floppy controller) died so I may have some issues setting it up. It might take me a bit to get that going.

Santo

On Wednesday, May 11, 2022 at 10:29:28 PM UTC+8, santo.n...@gmail.com wrote:
> I had to sort through the disks but unfortunately, I only have 227 8" disks with a small number missing and some duplicates. They are a backup with various labels and of disks have two disk archives on them. I should set up a CP/M system to check these disks. These disks must have been reused at some point. Here is what that looks like: https://vintagecomputer.ca/files/SIGM/IMG-3639.jpeg
>
> These disks came from Canada Remote Systems who was originally Toronto RCP/M. They ran a large BBS and had their own CP/M archive that I have posted here: https://vintagecomputer.ca/files/Canada%20Remote%20Systems%20CPM%20Archive/. I have a couple of backups of this; one on CD and one on ZIP disk. You can see the SIG/M backup was dated July 4, 1983 if the first disk is accurate. Unfortunately, there must have been another box of disks that I didn't get.
>
> Yes, that is a TRS-80 Model 4 next to the box. I also have a NEC APC with 8" drives and I think I have CP/M 86 for it but that computer needs work :(. I wonder if I could have used that to browse these disks?
>
> I will look into my 8" archiving system. If I recall, my Adaptec SCSI controller (with the better floppy controller) died so I may have some issues setting it up. It might take me a bit to get that going.
>
> Santo
>Toronto RCP/M

I seem to have the same collection at *HUMONGOUS* CP/M here:

http://cpmarchives.classiccmp.org/ftp.php?b=cpm/Software/TorontoRCPM/CDR

Before you put a lot of work into this, let’s see if it’ll be worth the effort.

There are currently six sources that I’m aware of for the SIG/M. The best known is the Walnut Creek CD. Unfortunately, it’s also by far the most corrupt — filenames have beeen altered, passage through UNIX at some point has left file names altered, many text files converted to UNIX format, and weird stuff with / in the file name, and a whole bunch of files that don’t match original CRCs.

CPMDOSgg seems to be the cleanest collection — CRCs mostly match, e..g. — suggesting its source (whatever it is) is older than the other collections.

I’d ideally like to get my hands on IMD disk images of original copies of the SIG/M disks, or disks that were duped from them. From your description it sounds like what you have isn’t anything like that — just archive disks made by someone at Toronto RCP/M. So getting IMDs may not be necessary. But if there’s a chance the source of your images is older than CPMDOSgg, copies of the files (zipped up, perhaps) could still prove useful. Case in point is vol 54’s TTBOOT.ASM.

My first machine was a Model IV. I stilll miss it.

On Wednesday, May 11, 2022 at 11:51:02 AM UTC-4, Nathanael wrote:
> On Wednesday, May 11, 2022 at 10:29:28 PM UTC+8, santo.n... @ g***l.com wrote:
> > I had to sort through the disks but unfortunately, I only have 227 8" disks with a small number missing and some duplicates. They are a backup with various labels and of disks have two disk archives on them. I should set up a CP/M system to check these disks. These disks must have been reused at some point. Here is what that looks like: https://vintagecomputer.ca/files/SIGM/IMG-3639.jpeg
> >
> > These disks came from Canada Remote Systems who was originally Toronto RCP/M. They ran a large BBS and had their own CP/M archive that I have posted here: https://vintagecomputer.ca/files/Canada%20Remote%20Systems%20CPM%20Archive/. I have a couple of backups of this; one on CD and one on ZIP disk. You can see the SIG/M backup was dated July 4, 1983 if the first disk is accurate. Unfortunately, there must have been another box of disks that I didn't get.
> >
> > Yes, that is a TRS-80 Model 4 next to the box. I also have a NEC APC with 8" drives and I think I have CP/M 86 for it but that computer needs work :(. I wonder if I could have used that to browse these disks?
> >
> > I will look into my 8" archiving system. If I recall, my Adaptec SCSI controller (with the better floppy controller) died so I may have some issues setting it up. It might take me a bit to get that going.
> >
> > Santo
> >Toronto RCP/M
>
> I seem to have the same collection at *HUMONGOUS* CP/M here:
>
> http://cpmarchives.classiccmp.org/ftp.php?b=cpm/Software/TorontoRCPM/CDR
>
> Before you put a lot of work into this, let’s see if it’ll be worth the effort.
>
> There are currently six sources that I’m aware of for the SIG/M. The best known is the Walnut Creek CD. Unfortunately, it’s also by far the most corrupt — filenames have beeen altered, passage through UNIX at some point has left file names altered, many text files converted to UNIX format, and weird stuff with / in the file name, and a whole bunch of files that don’t match original CRCs.
>
> CPMDOSgg seems to be the cleanest collection — CRCs mostly match, e.g. — suggesting its source (whatever it is) is older than the other collections.
>
> I’d ideally like to get my hands on IMD disk images of original copies of the SIG/M disks, or disks that were duped from them. From your description it sounds like what you have isn’t anything like that — just archive disks made by someone at Toronto RCP/M. So getting IMDs may not be necessary. But if there’s a chance the source of your images is older than CPMDOSgg, copies of the files (zipped up, perhaps) could still prove useful. Case in point is vol 54’s TTBOOT.ASM.
>
> My first machine was a Model IV. I stilll miss it.

Is it possible that TTBOOT.ASM was never copied to the SIG/M vol 54 disk correctly? If the corrupt/missing first sector is purely comments it may have been just not noticed and/or disregarded until recently. Have you considered going back to even older sources like the Thinker Toys printed documentation? Boards of that era often included source listings in their manuals and it may have not been transcribed properly into the SIG/M collection ever. Possibly that might give clues as what is missing. Kudos for the great project BTW. Great historical value and importance

> Is it possible that TTBOOT.ASM was never copied to the SIG/M vol 54 disk correctly?

Except that TTBOOT.ASM’s CRC (6E2F) doesn’t match the value in -CATALOG.054 (C901), indicating that what we have isn’t what the original CRC was generated against.

> Have you considered going back to even older sources like the Thinker Toys printed documentation?

Is that available somewhere? I haven’t been able to find it.

> Kudos for the great project BTW

Thanks. It began a couple of years ago when I was trying to chase down Vols 184-192, which were missing from every source I had at the time.

On Friday, May 13, 2022 at 9:17:43 PM UTC+8, xagdin-...@yahoo.com wrote:
> On Wednesday, May 11, 2022 at 11:51:02 AM UTC-4, Nathanael wrote:
> > On Wednesday, May 11, 2022 at 10:29:28 PM UTC+8, santo.n... @ g***l.com wrote:
> > > I had to sort through the disks but unfortunately, I only have 227 8" disks with a small number missing and some duplicates. They are a backup with various labels and of disks have two disk archives on them. I should set up a CP/M system to check these disks. These disks must have been reused at some point. Here is what that looks like: https://vintagecomputer.ca/files/SIGM/IMG-3639.jpeg
> > >
> > > These disks came from Canada Remote Systems who was originally Toronto RCP/M. They ran a large BBS and had their own CP/M archive that I have posted here: https://vintagecomputer.ca/files/Canada%20Remote%20Systems%20CPM%20Archive/. I have a couple of backups of this; one on CD and one on ZIP disk. You can see the SIG/M backup was dated July 4, 1983 if the first disk is accurate. Unfortunately, there must have been another box of disks that I didn't get.
> > >
> > > Yes, that is a TRS-80 Model 4 next to the box. I also have a NEC APC with 8" drives and I think I have CP/M 86 for it but that computer needs work :(. I wonder if I could have used that to browse these disks?
> > >
> > > I will look into my 8" archiving system. If I recall, my Adaptec SCSI controller (with the better floppy controller) died so I may have some issues setting it up. It might take me a bit to get that going.
> > >
> > > Santo
> > >Toronto RCP/M
> >
> > I seem to have the same collection at *HUMONGOUS* CP/M here:
> >
> > http://cpmarchives.classiccmp.org/ftp.php?b=cpm/Software/TorontoRCPM/CDR
> >
> > Before you put a lot of work into this, let’s see if it’ll be worth the effort.
> >
> > There are currently six sources that I’m aware of for the SIG/M.. The best known is the Walnut Creek CD. Unfortunately, it’s also by far the most corrupt — filenames have beeen altered, passage through UNIX at some point has left file names altered, many text files converted to UNIX format, and weird stuff with / in the file name, and a whole bunch of files that don’t match original CRCs.
> >
> > CPMDOSgg seems to be the cleanest collection — CRCs mostly match, e.g. — suggesting its source (whatever it is) is older than the other collections.
> >
> > I’d ideally like to get my hands on IMD disk images of original copies of the SIG/M disks, or disks that were duped from them. From your description it sounds like what you have isn’t anything like that — just archive disks made by someone at Toronto RCP/M. So getting IMDs may not be necessary. But if there’s a chance the source of your images is older than CPMDOSgg, copies of the files (zipped up, perhaps) could still prove useful. Case in point is vol 54’s TTBOOT.ASM.
> >
> > My first machine was a Model IV. I stilll miss it.
> Is it possible that TTBOOT.ASM was never copied to the SIG/M vol 54 disk correctly? If the corrupt/missing first sector is purely comments it may have been just not noticed and/or disregarded until recently. Have you considered going back to even older sources like the Thinker Toys printed documentation? Boards of that era often included source listings in their manuals and it may have not been transcribed properly into the SIG/M collection ever. Possibly that might give clues as what is missing. Kudos for the great project BTW. Great historical value and importance

On Friday, May 13, 2022 at 7:42:49 PM UTC-4, Nathanael wrote:
> > Is it possible that TTBOOT.ASM was never copied to the SIG/M vol 54 disk correctly?
> Except that TTBOOT.ASM’s CRC (6E2F) doesn’t match the value in -CATALOG.054 (C901), indicating that what we have isn’t what the original CRC was generated against.
> > Have you considered going back to even older sources like the Thinker Toys printed documentation?
> Is that available somewhere? I haven’t been able to find it.
> > Kudos for the great project BTW
> Thanks. It began a couple of years ago when I was trying to chase down Vols 184-192, which were missing from every source I had at the time.
> On Friday, May 13, 2022 at 9:17:43 PM UTC+8, * wrote:
> > On Wednesday, May 11, 2022 at 11:51:02 AM UTC-4, Nathanael wrote:
> > > On Wednesday, May 11, 2022 at 10:29:28 PM UTC+8, santo.n... @ g***l.com wrote:
> > > > I had to sort through the disks but unfortunately, I only have 227 8" disks with a small number missing and some duplicates. They are a backup with various labels and of disks have two disk archives on them. I should set up a CP/M system to check these disks. These disks must have been reused at some point. Here is what that looks like: https://vintagecomputer.ca/files/SIGM/IMG-3639.jpeg
> > > >
> > > > These disks came from Canada Remote Systems who was originally Toronto RCP/M. They ran a large BBS and had their own CP/M archive that I have posted here: https://vintagecomputer.ca/files/Canada%20Remote%20Systems%20CPM%20Archive/. I have a couple of backups of this; one on CD and one on ZIP disk. You can see the SIG/M backup was dated July 4, 1983 if the first disk is accurate. Unfortunately, there must have been another box of disks that I didn't get.
> > > >
> > > > Yes, that is a TRS-80 Model 4 next to the box. I also have a NEC APC with 8" drives and I think I have CP/M 86 for it but that computer needs work :(. I wonder if I could have used that to browse these disks?
> > > >
> > > > I will look into my 8" archiving system. If I recall, my Adaptec SCSI controller (with the better floppy controller) died so I may have some issues setting it up. It might take me a bit to get that going.
> > > >
> > > > Santo
> > > >Toronto RCP/M
> > >
> > > I seem to have the same collection at *HUMONGOUS* CP/M here:
> > >
> > > http://cpmarchives.classiccmp.org/ftp.php?b=cpm/Software/TorontoRCPM/CDR
> > >
> > > Before you put a lot of work into this, let’s see if it’ll be worth the effort.
> > >
> > > There are currently six sources that I’m aware of for the SIG/M. The best known is the Walnut Creek CD. Unfortunately, it’s also by far the most corrupt — filenames have beeen altered, passage through UNIX at some point has left file names altered, many text files converted to UNIX format, and weird stuff with / in the file name, and a whole bunch of files that don’t match original CRCs.
> > >
> > > CPMDOSgg seems to be the cleanest collection — CRCs mostly match, e.g. — suggesting its source (whatever it is) is older than the other collections.
> > >
> > > I’d ideally like to get my hands on IMD disk images of original copies of the SIG/M disks, or disks that were duped from them. From your description it sounds like what you have isn’t anything like that — just archive disks made by someone at Toronto RCP/M. So getting IMDs may not be necessary. But if there’s a chance the source of your images is older than CPMDOSgg, copies of the files (zipped up, perhaps) could still prove useful. Case in point is vol 54’s TTBOOT.ASM.
> > >
> > > My first machine was a Model IV. I stilll miss it.
> > Is it possible that TTBOOT.ASM was never copied to the SIG/M vol 54 disk correctly? If the corrupt/missing first sector is purely comments it may have been just not noticed and/or disregarded until recently. Have you considered going back to even older sources like the Thinker Toys printed documentation? Boards of that era often included source listings in their manuals and it may have not been transcribed properly into the SIG/M collection ever. Possibly that might give clues as what is missing. Kudos for the great project BTW. Great historical value and importance

As I recall, Thinker Toys was an early form of the George Morrow company's S-100 board so it might be found buried in the documentation on S100Computers.com

http://www.s100computers.com/Hardware%20Folder/Morrow/History/History.htm

I was digging around and noticed there was a code listing in the Disk Jockey S-100 FDC board which looked kind of similar. If there are clues in TTBOOT.ASM as to what hardware it is specifically meant for that might provide help on what documents are relevant. There are are several on the S100Computers.com site but others as well.

It might be worth posting on the S100Computers.com Google Group to see if someone has it in their collection.

On closer inspection, vol 54’s TTBOOT.ASM and TTCBIOS.ASM are not Thinker Toy software, but independent patches by Jack Burge; so I don’t think tracking down Thinker Toy documentation is going to turn anything up.

It’s pretty clear what’s missing is just a few lines of comment at the top of the file, so the actually utility of the file isn’t impacted. But it’d be nice to get it cleaned up anyway.

Putting out a call on th S100 forum sounds like a good idea, though.

On Saturday, May 14, 2022 at 8:25:56 AM UTC+8, xagdin-...@yahoo.com wrote:
> On Friday, May 13, 2022 at 7:42:49 PM UTC-4, Nathanael wrote:
> > > Is it possible that TTBOOT.ASM was never copied to the SIG/M vol 54 disk correctly?
> > Except that TTBOOT.ASM’s CRC (6E2F) doesn’t match the value in -CATALOG.054 (C901), indicating that what we have isn’t what the original CRC was generated against.
> > > Have you considered going back to even older sources like the Thinker Toys printed documentation?
> > Is that available somewhere? I haven’t been able to find it.
> > > Kudos for the great project BTW
> > Thanks. It began a couple of years ago when I was trying to chase down Vols 184-192, which were missing from every source I had at the time.
> > On Friday, May 13, 2022 at 9:17:43 PM UTC+8, * wrote:
> > > On Wednesday, May 11, 2022 at 11:51:02 AM UTC-4, Nathanael wrote:
> > > > On Wednesday, May 11, 2022 at 10:29:28 PM UTC+8, santo.n... @ g***l..com wrote:
> > > > > I had to sort through the disks but unfortunately, I only have 227 8" disks with a small number missing and some duplicates. They are a backup with various labels and of disks have two disk archives on them. I should set up a CP/M system to check these disks. These disks must have been reused at some point. Here is what that looks like: https://vintagecomputer.ca/files/SIGM/IMG-3639.jpeg
> > > > >
> > > > > These disks came from Canada Remote Systems who was originally Toronto RCP/M. They ran a large BBS and had their own CP/M archive that I have posted here: https://vintagecomputer.ca/files/Canada%20Remote%20Systems%20CPM%20Archive/. I have a couple of backups of this; one on CD and one on ZIP disk. You can see the SIG/M backup was dated July 4, 1983 if the first disk is accurate. Unfortunately, there must have been another box of disks that I didn't get.
> > > > >
> > > > > Yes, that is a TRS-80 Model 4 next to the box. I also have a NEC APC with 8" drives and I think I have CP/M 86 for it but that computer needs work :(. I wonder if I could have used that to browse these disks?
> > > > >
> > > > > I will look into my 8" archiving system. If I recall, my Adaptec SCSI controller (with the better floppy controller) died so I may have some issues setting it up. It might take me a bit to get that going.
> > > > >
> > > > > Santo
> > > > >Toronto RCP/M
> > > >
> > > > I seem to have the same collection at *HUMONGOUS* CP/M here:
> > > >
> > > > http://cpmarchives.classiccmp.org/ftp.php?b=cpm/Software/TorontoRCPM/CDR
> > > >
> > > > Before you put a lot of work into this, let’s see if it’ll be worth the effort.
> > > >
> > > > There are currently six sources that I’m aware of for the SIG/M. The best known is the Walnut Creek CD. Unfortunately, it’s also by far the most corrupt — filenames have beeen altered, passage through UNIX at some point has left file names altered, many text files converted to UNIX format, and weird stuff with / in the file name, and a whole bunch of files that don’t match original CRCs.
> > > >
> > > > CPMDOSgg seems to be the cleanest collection — CRCs mostly match, e.g. — suggesting its source (whatever it is) is older than the other collections.
> > > >
> > > > I’d ideally like to get my hands on IMD disk images of original copies of the SIG/M disks, or disks that were duped from them. From your description it sounds like what you have isn’t anything like that — just archive disks made by someone at Toronto RCP/M. So getting IMDs may not be necessary. But if there’s a chance the source of your images is older than CPMDOSgg, copies of the files (zipped up, perhaps) could still prove useful. Case in point is vol 54’s TTBOOT.ASM.
> > > >
> > > > My first machine was a Model IV. I stilll miss it.
> > > Is it possible that TTBOOT.ASM was never copied to the SIG/M vol 54 disk correctly? If the corrupt/missing first sector is purely comments it may have been just not noticed and/or disregarded until recently. Have you considered going back to even older sources like the Thinker Toys printed documentation? Boards of that era often included source listings in their manuals and it may have not been transcribed properly into the SIG/M collection ever. Possibly that might give clues as what is missing. Kudos for the great project BTW. Great historical value and importance
> As I recall, Thinker Toys was an early form of the George Morrow company's S-100 board so it might be found buried in the documentation on S100Computers.com
>
> http://www.s100computers.com/Hardware%20Folder/Morrow/History/History.htm
>
> I was digging around and noticed there was a code listing in the Disk Jockey S-100 FDC board which looked kind of similar. If there are clues in TTBOOT.ASM as to what hardware it is specifically meant for that might provide help on what documents are relevant. There are are several on the S100Computers.com site but others as well.
>
> It might be worth posting on the S100Computers.com Google Group to see if someone has it in their collection.

Nathaneal,
Try this archive. I don't know how to work with extracting files from IMD archives but I hope this has the file you are looking for.

https://vintagecomputer.ca/files/SIGM/SIGM54.IMD

Santo

On Saturday, May 14, 2022 at 12:24:42 AM UTC-4, Nathanael wrote:
> On closer inspection, vol 54’s TTBOOT.ASM and TTCBIOS.ASM are not Thinker Toy software, but independent patches by Jack Burge; so I don’t think tracking down Thinker Toy documentation is going to turn anything up.
>
> It’s pretty clear what’s missing is just a few lines of comment at the top of the file, so the actually utility of the file isn’t impacted. But it’d be nice to get it cleaned up anyway.
>
> Putting out a call on th S100 forum sounds like a good idea, though.

Thanks for the attempt. Unfortunately, it has the same corruption.

FYI, for IMDU files, I use Dave Dunfield’s IMDU, then cpmtools to extract the files:

imdu SIGM54.IMD SIGM54.RAW -b -e -d
cpmcp -f IBM-3740 SIGM54.RAW 0:*.* ./

On Sunday, May 15, 2022 at 12:10:12 AM UTC+8, santo.n...@gmail.com wrote:
> Nathaneal,
> Try this archive. I don't know how to work with extracting files from IMD archives but I hope this has the file you are looking for.
>
> https://vintagecomputer.ca/files/SIGM/SIGM54.IMD
>
> Santo
> On Saturday, May 14, 2022 at 12:24:42 AM UTC-4, Nathanael wrote:
> > On closer inspection, vol 54’s TTBOOT.ASM and TTCBIOS.ASM are not Thinker Toy software, but independent patches by Jack Burge; so I don’t think tracking down Thinker Toy documentation is going to turn anything up.
> >
> > It’s pretty clear what’s missing is just a few lines of comment at the top of the file, so the actually utility of the file isn’t impacted. But it’d be nice to get it cleaned up anyway.
> >
> > Putting out a call on th S100 forum sounds like a good idea, though.

Am 05/15/2022 02:47 AM, Nathanael schrieb:
> Thanks for the attempt. Unfortunately, it has the same corruption.
>
> FYI, for IMDU files, I use Dave Dunfield’s IMDU, then cpmtools to extract the files:
>
> imdu SIGM54.IMD SIGM54.RAW -b -e -d
> cpmcp -f IBM-3740 SIGM54.RAW 0:*.* ./
>
>
> On Sunday, May 15, 2022 at 12:10:12 AM UTC+8, santo.n...@gmail.com wrote:
>> Nathaneal,
>> Try this archive. I don't know how to work with extracting files from IMD archives but I hope this has the file you are looking for.
>>
>> https://vintagecomputer.ca/files/SIGM/SIGM54.IMD
>>
>> Santo
>> On Saturday, May 14, 2022 at 12:24:42 AM UTC-4, Nathanael wrote:
>>> On closer inspection, vol 54’s TTBOOT.ASM and TTCBIOS.ASM are not Thinker Toy software, but independent patches by Jack Burge; so I don’t think tracking down Thinker Toy documentation is going to turn anything up.
>>>
>>> It’s pretty clear what’s missing is just a few lines of comment at the top of the file, so the actually utility of the file isn’t impacted. But it’d be nice to get it cleaned up anyway.
>>>
>>> Putting out a call on th S100 forum sounds like a good idea, though.

Hi Nathanael, what about this?

We create a preliminary fix until the original finally appears.

The beginnings of TTCBIOS and TTBOOT are very similar.

The content of TTCBIOS.ASM from line 2 to the end of the corruption
fits perfectly into most of the first sector of TTBOOT.ASM.

Now, we only need to find a nice replacement for the (I assume) single
line before containing the filename.

We have 21 Bytes available...

What about this:
1) We replace the TAB before the filename with SPACEs
2) We put the remaining byte as a SPACE after the filename

The idea for this came from real life situations.
It often happens that a TAB gets replaced by SPACEs,
also a trailing SPACEs could remain after changing
the filename from TTCBIOS.ASM to TTBOOT.ASM :-)

0000: 3B 20 20 20 20 20 20 20 54 54 42 4F 4F 54 2E 41
0010: 53 4D 20 0D 0A

Putting everything together, the first sector looks like this:

0000: 3b 20 20 20 20 20 20 20 54 54 42 4f 4f 54 2e 41 ; TTBOOT.A
0010: 53 4d 20 0d 0a 3b 0d 0a 3b 0d 0a 3b 0d 0a 3b 20 SM ..;..;..;..;
0020: 20 20 20 20 20 4f 72 69 67 69 6e 61 6c 20 63 6f Original co
0030: 64 69 6e 67 20 62 79 3a 20 20 54 68 69 6e 6b 65 ding by: Thinke
0040: 72 20 54 6f 79 73 0d 0a 3b 09 09 09 20 20 20 20 r Toys..;...
0050: 52 69 63 68 6d 6f 6e 64 2c 20 43 41 0d 0a 3b 0d Richmond, CA..;.
0060: 0a 3b 0d 0a 3b 20 20 20 20 20 20 20 50 61 74 63 .;..; Patc
0070: 68 69 6e 67 20 74 6f 20 6d 69 6e 69 6d 69 7a 65 hing to minimize

Hth
Martin