Welcome, Guest. Please login or register.

Author Topic: BlizKick with OS3.9  (Read 3023 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline motorollinTopic starter

  • Hero Member
  • *****
  • Join Date: Nov 2005
  • Posts: 8669
    • Show all replies
BlizKick with OS3.9
« on: May 30, 2006, 07:18:47 PM »
Can anyone let me know the correct syntax for using BlizKick with OS3.9? I have tried following the manual, but it doesn't seem to be working. I read my 3.1 ROM to a file, used the splitting command to extract the modules from the 3.9 romupdate, and tried entering the name of each module as an argument in the BlizKick command line, but my kickstart version is still 3.1 after BlizKick-ing.

--
moto
Code: [Select]
10  IT\'S THE FINAL COUNTDOWN
20  FOR C = 1 TO 2
30     DA-NA-NAAAA-NAAAA DA-NA-NA-NA-NAAAA
40     DA-NA-NAAAA-NAAAA DA-NA-NA-NA-NA-NA-NAAAAA
50  NEXT C
60  NA-NA-NAAAA
70  NA-NA NA-NA-NA-NA-NAAAA NAAA-NAAAAAAAAAAA
80  GOTO 10
 

Offline motorollinTopic starter

  • Hero Member
  • *****
  • Join Date: Nov 2005
  • Posts: 8669
    • Show all replies
Re: BlizKick with OS3.9
« Reply #1 on: May 30, 2006, 07:48:27 PM »
Cool... I'll check the jumper.

When you say split the BB2 romupdate too, is that "DEVS:AmigaOS ROM Update.BB2"? I have to split both? When I split the file, I got some "unknown" modules. What are they? Do I have to include them in BlizKick?

--
moto
Code: [Select]
10  IT\'S THE FINAL COUNTDOWN
20  FOR C = 1 TO 2
30     DA-NA-NAAAA-NAAAA DA-NA-NA-NA-NAAAA
40     DA-NA-NAAAA-NAAAA DA-NA-NA-NA-NA-NA-NAAAAA
50  NEXT C
60  NA-NA-NAAAA
70  NA-NA NA-NA-NA-NA-NAAAA NAAA-NAAAAAAAAAAA
80  GOTO 10
 

Offline motorollinTopic starter

  • Hero Member
  • *****
  • Join Date: Nov 2005
  • Posts: 8669
    • Show all replies
Re: BlizKick with OS3.9
« Reply #2 on: May 31, 2006, 08:18:52 AM »
Well here's something weird. I used Remus to create a new 3.1 ROM image sans scsi.device (I don't need it and it just increases boot time). I booted with no SS, then BlizKicked the image. Sure enough, 'version scsi.device' resulted in an 'Object not found' error, and 'version' returned kickstart 40.68. I then ran setpatch and the system rebooted. No SS again, and typed version, and got 44.x (whatever the 3.9 version is). But when I typed 'version scsi.device', I got 'object not found' again. This suggests to me that setpatch left the BlizKick-ed image resident and patched it. I thought Setpatch would wipe out the BlizKicked image?

Anyway, I'm working on using Remus to insert the 3.9 ROMUpdate files in to a 3.1 ROM image which I can BlizKick, and one day burn to EPROMs  :-D

--
moto
Code: [Select]
10  IT\'S THE FINAL COUNTDOWN
20  FOR C = 1 TO 2
30     DA-NA-NAAAA-NAAAA DA-NA-NA-NA-NAAAA
40     DA-NA-NAAAA-NAAAA DA-NA-NA-NA-NA-NA-NAAAAA
50  NEXT C
60  NA-NA-NAAAA
70  NA-NA NA-NA-NA-NA-NAAAA NAAA-NAAAAAAAAAAA
80  GOTO 10