os3.9 NOROMUPDATE?

[Dr.Bongo]

Upgraded the memory in my A4k (the one in my sig) to 128mb. After which it refused to boot only giving a software failure. WB 3.1 and classic WB are fine with it though, both show 128mb fast mem.
 The only way I can seem to get 3.9 to work is to Add NOROMUPDATE to the startup-sequence.

 Everything seems fine and speedy like that but my question is - Will having that in my startup-sequence make a negative difference?

[mfilos]

NOROMUPDATE option only tells SetPatch not to load the extra BB2 modules found within the file "AmigaOS ROM Update" that resides under DEVS folder.
The file contains the following modules:



Apparently one or more modules is messing with your system.
If you don't mind having the newer versions of these modules you're gonna be fine with NOROMUPDATE option.
If you want to check though which module is giving you a hard time you can use the option SKIPROMMODULES with the module (or modules seperated with a comma) that you want to exclude loading.

For example:

Code: [Select]

SetPatch SKIPROMMODULES "scsi.device" QUIET...will load all the BB2 modules but exclude scsi.device.

[Dr.Bongo]

Cheers for that. I kind of knew most of it, but your reply was quite in-depth.

I can't seem to notice a difference in performance or features, I just wondered If anyone has been through similar and can say if it really matters or makes a difference to add NOROMUPDATE?

[cha05e90]

I can't seem to notice a difference in performance or features, I just wondered If anyone has been through similar and can say if it really matters or makes a difference to add NOROMUPDATE?

Bugfixes? NOROMUPDATE, no bugfixes. There was a list of fixes for each module, but I don't know whether they were on the AmigaOS 3.9 CD or part of the NDK archive.