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
You will not be able to post if you are still using Microsoft email addresses such as Hotmail etc
See here for more information viewtopic.php?f=20&t=7296
See here for more information viewtopic.php?f=20&t=7296
DO NOT USE DEVICES WHERE THE IP CHANGES CONSTANTLY!
At this time it is unfortunately not possible to white list users when your IP changes constantly.
You may inadvertently get banned because a previous attack may have used the IP you are now on.
So I suggest people only use fixed IP address devices until I can think of a solution for this problem!
At this time it is unfortunately not possible to white list users when your IP changes constantly.
You may inadvertently get banned because a previous attack may have used the IP you are now on.
So I suggest people only use fixed IP address devices until I can think of a solution for this problem!
TOS 4.92 source code
Re: TOS 4.92 source code
DFB1 Open source 50MHz 030 and TT-RAM accelerator for the Falcon
Smalliermouse ST-optimised USB mouse adapter based on SmallyMouse2
FrontBench The Frontier: Elite 2 intro as a benchmark
Smalliermouse ST-optimised USB mouse adapter based on SmallyMouse2
FrontBench The Frontier: Elite 2 intro as a benchmark
Re: TOS 4.92 source code
Also there's the Atari HQ archive. As I said, the puzzle has multiple pieces.
Re: TOS 4.92 source code
Ah, yes, great. I don't know how I missed that one. Thanks a lot.Badwolf wrote: Mon Sep 29, 2025 11:07 am 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!
I checked that archive earlier. But I can't see any BIOS source files there unless they are very well hidden somewhere.mikro wrote: Mon Sep 29, 2025 12:38 pm Also there's the Atari HQ archive. As I said, the puzzle has multiple pieces.
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?
http://github.com/ijor/fx68k 68000 cycle exact FPGA core
FX CAST Cycle Accurate Atari ST core
http://pasti.fxatari.com
FX CAST Cycle Accurate Atari ST core
http://pasti.fxatari.com
Re: TOS 4.92 source code
@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.
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.
Re: TOS 4.92 source code
I see. And there is no old tool to browse the RCS archive natively?mikro wrote: Mon Sep 29, 2025 2:55 pm @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".
http://github.com/ijor/fx68k 68000 cycle exact FPGA core
FX CAST Cycle Accurate Atari ST core
http://pasti.fxatari.com
FX CAST Cycle Accurate Atari ST core
http://pasti.fxatari.com
Re: TOS 4.92 source code
The simplest way is to rename "RCS" folders to "CVS" and use standard cvs toolset but it's still painful.ijor wrote: Wed Oct 01, 2025 3:49 amI see. And there is no old tool to browse the RCS archive natively?
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.