BlizKick with OS3.9

[motorollin]

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

[x56h34]

Make sure that your maprom jumper from the B1260 card is removed (open). IIRC from your previous posts, you have a B1260.

If you are trying to create a single-reboot system, make sure that the extracted modules are from BB2 rom update. You only said "rom update" so you could be talking about BB1... I don't know, only speculating. :-)

Finally, here's an example of a BlizKick line designed for a single reboot and all or most of the relevant modules active:

Blizkick * EXTRESBUF=150000 HOGWAITBLIT SpeedROM MODULE Bblank NewAlert ROMFIXES Noclick MoveVBR FixMath404 MuMove4k scsi.device FastFileSystem Filesystem.Resource console.device Ram-Handler romupdate.idtag shell Bootmenu QUIET

SetPatch NOROMUPDATE QUIET

[motorollin]

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

[x56h34]

These modules should come out from the rom update and be placed into the DEVS:Modules directory, together with the rest of the regular BlizKick modules:

scsi.device
FastFileSystem
Filesystem.Resource
console.device
Ram-Handler
romupdate.idtag
shell
Bootmenu

Assuming that you've installed the Rom Update from BB2, when the installer asked you to during BB2 installation, all you need to type from shell is the following:

romupdatesplit "devs:AmigaOS ROM Update" to devs:modules

...and the above-mentioned modules will be extracted from the BB2 Rom Update straight into the BlizKick's default modules dir.

[amigagr]

i don't remember for sure anymore but with the romupdatesplit command it may need to specify your exact amiga model just to be sure that you get from it the correct rom modules. read the blizkick.guide fearther.

[humppa]

Remove the QUIET option to see where/why it hangs.

[motorollin]

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

[Framiga]

"When I split the file, I got some "unknown" modules. What are they? Do I have to include them in BlizKick?"

about this particular issue (unknown) you have to use the very latest romupdatesplit tool, in the latest BK archive (BB2 compliant). Otherwise, you'll get those "unknown" entries.

[Piru]

@amije

with the romupdatesplit command it may need to specify your exact amiga model just to be sure that you get from it the correct rom modules.

By default romupdatesplit extracts the modules for the computer it is run on. Only if you run the command on some other system you need to specify the model.

[Piru]

@motorollin

When I split the file, I got some "unknown" modules. What are they? Do I have to include them in BlizKick?

Like Framiga already pointed out, you need the latest romupdatesplit (updated was for 3.9BB2). Grab it from BlizKick.lha.

This suggests to me that setpatch left the BlizKick-ed image resident and patched it. I thought Setpatch would wipe out the BlizKicked image?

From SetPatch point of view the p5 maprom looks 100% identical to real ROM, thus it won't remove anything. SetPatch will just install the regular patches and/or 3.9 modules like with any other ROM.

Unless if you power off or use BlizKick to remove the mapping (start BlizKick without ROM file) the new "rom" will stay. This is why the p5 maprom is superior to any pure software rekicking.