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!

[Cass]

Try
c:SetPatch NOROMUPDATE QUIET


________
FFM COMPILATION

[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?

[AmiGR]

The problem is the reboot that it causes, not the contents of the ROMUpdate. I suggest Blizkick, it might have a fix or two.

[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?

This is the first (or one of the first) line in SS. Just edit the existant C:SetPatch, and add the NOROMUPDATE parameter.
There shouldn`t be/following any other C:SetPatch lines afterwards.
________
GRAPE APE MARIJUANA STRAIN

[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!

[Matt_H]

You do lose considerable functionality by completely disabling the ROM Update (31KHz bootmenu, scsi/ide upgrades, FFS upgrades, etc). If you're willing to do more testing, you could try disabling individual modules from the update until you find the one responsible.

My first guess would be exec.library, so try using

C:SetPatch SKIPROMUPDATES "exec.library"

Or you can deal with the extra reboot by not disabling anything. It's not too bad, and you get used to it ;-)

[AmiGR]

[Matt_H]

The problem is not caused by any module, it's caused by the reboot itself. Blizkick might help, it uses a less hack-ish way to install the modules.

Really? Huh. That's interesting. I never would have guessed that myself.

Keropi, you should probably ignore my previous post, then :-)

I will also suggest trying BlizKick.

[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? :-?

[doctorq]

Have you used all the modules that came with BlizKick or all the modules you extracted from the ROM Update? I use BlizKick with BoingBag2 for OS3.9 and no errors here...

[StormLord]

I had a similar problem when I had a working amiga that after the reset of setpatch the disk become invalidated or at least that what the message said after the boot proccess started again. I solved it through with a WAIT 2 just before setpatch and worked from then normaly until I had this crazy idea of adding a grex...

[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???

[Doobrey]

AmiGR wrote:
The problem is not caused by any module, it's caused by the reboot itself.

The "earlyupdate" & "veryearly update"  messes about with expansion.libraries config list , and also fiddles with the list of available card slots.