OS 3.9 romupdate causes autoconfig data to dissapear, how to resolve that?

[keropi]

I use os3.9 on my a1200, and all was fine with my hardware. Until I bought a PicassoII card. The amiga recognises it OK on the early startup menu, along with my 1260... but on the 1st time the romupdate is applied, only the 1260 is recognised. I have to reboot the amiga (with the keyboard) in order to make the picassoII appear again... what else can I do? is there an alternative to setpatch, or can I completely disable the romupdate? any help?
The full specs of my miggy are on my signature, thanx!

[keropi]

hey cass!

where should I put that? first thing on the startup seq? and what about later setpatch commands on the ss? should I remark them?
If I used blizkick or similar to load the os3.9 romupdate?

[keropi]

how can I replace setpatch with blizkick? I mean what changes must I make in startup-sequence ?

[keropi]

ah, I tried cass's way, and it works like a charm!  :-D
even though there is NOROMUPDATES , still setpatch does some stuff, because when I run it on a cli window on 3.9 it says it has been run and displays a list of the patches... finally I can enjoy my picassoII  :-D  :-D  :-D
thanx guys!

[keropi]

OK, I tried blizkick... extracted the AMIGAOS ROM UPDATE to modules, moved the modules to DEVS:MODULES and I used this command:

c:blizkick extresbuf=48000 MODULE console.device FastFileSystem ram-handler followed by all the modules names...

prob is that I get: cannot kick FastfileSystem, errorcode 10 ...
anyone used blizkick like that? :-?

[keropi]

@ stormlord: you just add this line: WAIT 2 before the setpatch command?

@doctorq: What I did is this:
I used the extract prog on the DEVS:AmigaOS Rom Update , and put the files it produced in DEVS:MODULES
the files I got from extract are:
console.device
FastFileSystem
FileSystem.resource
ram-handler
scsi.device
unknown
unknown.1
unknown.2
unknown.3

and I put this line after the powerflyer's ATA3.driver :
c:blizkick extresbuf:48000 MODULE console.device FastFileSystem .... all the modules except the scsi.device, because ata3.driver installs its own...
And I get error 10 and that it cannot load FastFileSystem...
I tried removing it, and I get error10 on the next entry...
Is what I have done correct???

[keropi]

Yes, I have installed both BB for OS3.9... I will use the new Blizkick (thanx Framiga!) but one last thing:
Am I using it OK ? I mean, is the command I put on the SS correct? I only need it to inject the patches, not kickstart+patches... should I use a KS also?

[keropi]

There is a newest release on BlizKick homepage, which has full support for os3.5 and 3.9  :-D  Also there was a bug that prevents modules after console.device to load (like in my case) I'll try that later at home, I am sure I'll get it running now  :-D  
Here is the BlizKick homepage:
BlizKick homepage

[keropi]

a friend suggested I should try running "prepareemul a1200" (from shapeshifter package) after setpatch on my SS, because it does another reboot, so there will be no need to manually do a reboot. I have read that all prepareemul does is that it leaves the first 8kb of chipram free, so shapeshifter can use them...
What do you think of that idea?

[keropi]

I just tried what the BLIZKICK 1.24rc5 says in the help file... I extracted the romupdate (DEVS:MODULES) and put this line on the SS after ata3.driver:
c:blizkick extresbuf=80000 MODULE FileSystem.resource FastFileSystem ram-handler console.device

BUT

on boot I get:
Couldn't kick file "DEVS:MODULES/FileSystem.resource" !
c:BlizKick failed returncode 10

why? :-?  :-?  :-?

[keropi]

OK, I'll re-install BB2...

[keropi]

damn, re-installed bb2, extracted agin the modules, but only the first one can load... I get an error 10 and a message saying that it cannot find the module... in whatever order I put the modules, only the fisrt one works... wtf?  :pissed: I even tried using full paths in modules, and changed the default module path using the info on the guide... but still only the 1st one loads!   :pissed: