Welcome, Guest. Please login or register.

Author Topic: 3.1 Kickstart 40.70 vs 40.68?  (Read 15240 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show all replies
    • http://www.iki.fi/sintonen/
Re: 3.1 Kickstart 40.70 vs 40.68?
« on: September 26, 2010, 09:57:39 PM »
Quote from: Matt_H;581410
Grab the ROM to a file and do a byte comparison against 40.68 or 4000T 40.70 :)

Such comparison is unlikely to give any meaningful result, other than "the files are the same" or "the files are different".

Unless of course if you mean binary diff of some kind?
 

Offline Piru

  • \' union select name,pwd--
  • Hero Member
  • *****
  • Join Date: Aug 2002
  • Posts: 6946
    • Show all replies
    • http://www.iki.fi/sintonen/
Re: 3.1 Kickstart 40.70 vs 40.68?
« Reply #1 on: September 27, 2010, 09:18:55 AM »
Quote from: olsen;581472
What broke the V40 scsi.device for the A600/A500/A2000 was that the driver initialization code passed an uninitialized register, which would have contained a Task pointer in the SCSI variant, to the respective setup code.
Ouch.

Still, not as bad as breaking the whole AUTOCONFIG(TM) in KS 1.2 and later selling KS 1.3 separately as an upgrade to allow booting off HDD. This problem was trivial to fix as well (make sure that correct a6 is used for AllocMem call), and it made KS 1.2 support AUTOCONFIG(TM) just fine.
« Last Edit: September 27, 2010, 09:22:09 AM by Piru »