shoggoth wrote:deeez wrote:Dal wrote:Correct - and unless something changed, the CT60 soft-firmware actually copies in TOS from the physical rom and patches it.
I dont quite get it, I guess things perhaps wouldnt work if I had tos 4.02 or similar?
Motherboard TOS rev shouldn't mattet. CT TOS replaces TOS completely during boot.
Are you 100% sure on this? Here is a quote from Rodolphe Czuba in an admittedly very old interview about CT60 (source: http://www.myatari.co.uk/issues/mar2001/centurbo.htm)
Rodolphe Czuba wrote:stc: A tough subject is the operating system. Milan and Medusa put some hard work into a stable TOS on their 060 machines and prototypes. Which version of TOS will you use for the CT60 and how is compatibility realised?
Rodolphe: We will use the TOS of the Falcon. We have coded a boot for the flash memory. The software initialises the CT60 registers (the SDRAM for example), and this one copies the ROM into the 1 MB flash by patching some things like the PMMU tree. The 060 FPU library is also in the flash.
Also, in Didier's release post on DHS for TOS 2.01, he states:
Didier wrote:I updated archives, it's a Firebee release, but there are some features for the CT60:
- Retry loop for read the flash and copy the TOS until the CRC is correct.
So, from this, I have always had the impression that for ct60, the original (licensed) TOS is copied in from the Falcon to the 1mb flash and then patched to work for the ct60 before execution at boot time.
This has always been ambiguous, and until now, not really seen anything definitive around the boot process for the ct60. However, for legal/licensing reasons, it would make sense to use the original TOS, right?
So, assuming the above is true (I may have misunderstood), then what happens when TOS <4.04 is used?