»

[keropi]

I thought I did that right but no....

Here is what I do:

1. Format the FLASH
2. Add a firmware, v.1.6 it writes it OK, select NO on the question and then BlizzPPC card.
but on diagnostics it says v.1.5 :-? :-?
3. Add a 3.1 ROM for a1200 , I add the whdload rom image I use
4. Add the 3.9-bb2 romupdate, all expect scsi.device (since I have a fastata and its ata3.driver installs scsi.device v.50.00)
5. then I save on the Flash, it says ~380kb free
6. power off
7. remove kickflash jumper
8. reboot
9. nothing, the hd led stays on for 20-30sec, and then the power led blinks (it always has light, just dimms a little and then it goes to full bright...)

any ideas?

[alexh]

It's not an encrypted AmigaForever ROM is it? Since 16.5 WHDLoad can use these images.

Check and see if you have "rom.key" in DEVS:Kickstarts

Blinking LED is an indication of a 680x0 crash. If it is repetitive, i.e. with no GURU Meditation, it means the crash occured when executing the Kickstart ROM.

Does it work if you load JUST the kickstart image to FlashKick?

[keropi]

hmm just to be sure I grabbed Kickstart v3.1 rev 40.68 (1993)(Commodore)(A1200).rom TOSEC 0.04 ... I'll try it now...

[Doobrey]

I had a quick look at the 1.6 firmware last night, and from what I could make out it won't remap a kickstart image if the first 16 bytes of the image match those of the 'physical'/real kickstart (basically if you've got 40.68 ROMs you can't remap a 40.68 image from KickFlash)...although it should carry on loading the other modules in the KickFlash so I doubt that's your problem.

Does the kickstart image work OK with Blizkick?

[keropi]

yeah it works fine with bkick... gonna recheck though...
with or without the 3.1 rom, it makes no difference...
but why the firmware is only identified as 1.5??? I flashed the 1.52 from the coyoteflash archive and in diagnostics it was ??.?? lol
I also changed the setpatch command in SS to look like what the manual says, SETPATCH NOROMUPDATES QUIET ...

damn...

[alexh]

Perhaps you could try a "home made" 3.9 Kickstart using Romulus and Remus tools?

[keropi]

yeah, am gonna do that next...
just what I was thinking Alexh..
are those available in aminet?

[Chain]

http://www.doobreynet.co.uk/beta/index.html

[Doobrey]

alexh wrote:
Perhaps you could try a "home made" 3.9 Kickstart using Romulus and Remus tools?

IMHO, it'd be better to get the KickFlash working 'normally' before trying this, the last thing keropi needs is to find an unknown bug or side effect of Remus to add to the confusion.

It's gotta be some stupid..one of those head slapping 'DOH!' moments.
Maybe Blizkick is still run from the startup sequence(could be a problem if the Kickflash already remapped the ROM??)
or maybe he added the 1.6 firmware to the mirror file but forgot to actually write it to the KickFlash?

One way to test if it updated OK would be to make a clean mirror file (ie nothing but the latest firmware) and write it, reboot then get CoyoteFlash to read the entire contents to disk and manually check that 1.6 is inside it (just look for "CoyoteFlash 1.6" somewhere in the first 16kb with a hex editor/viewer) and also check the machine can boot, then starting adding things one at a time

[keropi]

I try kickflash on a clean os3.9 installation... so the bkick running is out of the question...

I have formatted the flash (not mirror) and then added ONLY the v1.6 firmware, write it and reboot... bust still on format->diagnostics menu it appears as 1.5... although the actual firmware on the coyoteflash package is version 1.6... dunno...

there is something fishy... lol