TOS 4.92 source code

[Badwolf]

There's a file titled "Atari BIOS/XBIOS source code" which has a 1992 date stamp and refernce to Sparrows and DSPs, so I think this must be it!

BW

[mikro]

Also there's the Atari HQ archive. As I said, the puzzle has multiple pieces.

[ijor]

There's a file titled "Atari BIOS/XBIOS source code" which has a 1992 date stamp and refernce to Sparrows and DSPs, so I think this must be it!

Ah, yes, great. I don't know how I missed that one. Thanks a lot.

Also there's the Atari HQ archive. As I said, the puzzle has multiple pieces.

I checked that archive earlier. But I can't see any BIOS source files there unless they are very well hidden somewhere.

Btw, Mikro, you mentioned you converted from RCS to git. The BIOS archive that Badwolf found, does include some RCS files. How you perform that conversion? Or otherwise, how you access the RCS archive?

[mikro]

@ijor that took weeks of coding custom tools, scripts and in general, understanding how RCS works. Definitely not a "downloaded a script and have a git repo as outcome".

I still need to clean it up (mostly merge everything together) but it was a true detective work.

And on top of that ... many RCS files are corrupted, i.e. they hold the latest version but the deeper into history you go the more corrupted results you get. So there are many blank spots.

[ijor]

@ijor that took weeks of coding custom tools, scripts and in general, understanding how RCS works. Definitely not a "downloaded a script and have a git repo as outcome".

I see. And there is no old tool to browse the RCS archive natively?

[mikro]

I see. And there is no old tool to browse the RCS archive natively?

The simplest way is to rename "RCS" folders to "CVS" and use standard cvs toolset but it's still painful.

The easiest way to look into history is to actually just view the ",v" files, those contains changes over history (you can easily see the commit title and diff from recent revision). But sometimes the diff from "now" to "one revision earlier" is just "remove all lines" (corrupted file) so you can't easily reconstruct the complete history. I had to use a couple of tricks but the end result is of course far from perfect.