Boingbag 3/4 problems

*Sigh*, you know, I was told not to install Boingbags 3 and 4 as they are buggy garbage (apparently)... but I did anywayz. :(

When installing BB3 it opens your SS and tells to install a couple of lines early on to load the new modules. Strangely, BB4 didnt require this.

I did this. But upon first boot it failed with the error message that version such and such of (I cant remember the library or device) was already resident. So I deleted this device/lib from the loadmodules line and rebooted. Happened again with the next new module trying to load, so I removed it.

This time it booted (must not have had the other devs/libs in memory) once at wb I think to myself "Well, these custom KS 3.9 roms must have BB3 and BB4 built in" so I deleted the entire loadmodules line.

System booted fine and wb version is still 45.5 and ks is still 45.59.

So all must be well. But.... since then I have discovered two small problems and I am starting to think they have something to do with the resident icon.library or such.

1 - When I right click on a volume and try and format the system simply locks, not crashes. Yet, running format from the icon is fine.

2 - When I right click on an icon and select Information, then drag and drop another icon on top of the icon image to replace it... it will only work if the new icon image is only 32 colours or less. If I drag and drop a 256 colour icon I ge the message "not of required type"

If I run IconEdit and load the images, they come up as blank - sort of like if you try and view a new icon without the newicon patch (on older systems).

Neither of these problems existed before installing BB3/BB4.

Perhaps I should not have deleted that line from te startup sequence?

Oh, and Im running PowerIcons patch too. I am only using standard 256 colour icons, but the colours are not correct unless I use the PowerIcon patch.

The PowerIcons patch slows down the system though, is there any other way of correctly displaying 256 colours icons? Surely WB should be able to do this itself?

ANY help would be appreciated.

Format the hard drive and install AOS3.9 from scratch without these "garbage".

BB3 and BB4 are definitely not garbage!!! That statement is really shity towards all the devs and people working for extra patches for all of us! It Just needs some caution when installing. Especially BB4 is work in development!
It's not strange that BB4 haven't told ya to alter your S-S since it doesn't have any module that needs to be loaded prior SetPatch.
Apart from that, BB3 is a well made installation script that works just fine. BB4 is still on development (I dunno what version of it you have. For example I have 3 different versions of BoingBang4.lha on my hard disk) so it depends on what version you installed anyway.
You clearly don't state what real Kickstart you have (do you have a custom Kick 3.9 - since from your sentence: "Well, these custom KS 3.9 roms must have BB3 and BB4 built in" so I deleted the entire loadmodules line", it seems that you do) so unless you just state exactly what your system is I don't know how we can gief more help :)
I haven't yet installed BB4 since it's in development, but never had issues with BB3 in the past either on A600 or A1200.

Gulliver may know a bit more though.

stachu100 - I have spent over 15 hours setting this up - formatting and starting again is simply a stupid suggestion, no offence. :)

Im afraid I cant tell you much about the custom KS roms - I didnt make them, I merely purchased them as A4000 KS 3.9 roms.

Thats why I was surprised that they appeared to have BB3 (at least) in them.

As a starting point, can you please post that loadmodule line from your SS (since you have boingbag 3 installed) and I will see if that fixes the problem.

@mfilos my friend,

As far as I know @abraXXious is using custom ROM. And in my opinion this is an issue.

EDIT:
Just saw post above, but anyhow custom ROM is an issue in my opinion. Please use standard KS33.1 and you can install AOS3.9+BB1+BB2+BB3+BB4.
BB3 and BB4 are not official - so you might have a problem, it's normal.

@abraXXious
Since you have custom kickstart ROMS, then the "AmigaOS ROM Update" is probably on them too so it's safe for:
- Renaming "Devs:AmigaOS ROM Update" to something else
- commenting your SetPatch line and instead...
- Using the following line: " C:SetPatch NOROMUPDATE QUIET

Using the LoadModule command with the new Modules will only bring errors in case the speciffic module you're trying to load is already burned into the Eprom.
As Stanislaw correctly said:
- Either you will use a standard 3.1 ROM and load whatever the hell you want via LoadModule/BlizKick/Deneb's Flash/ACA's maprom etc, or...
- Use your custom kick 3.9 without loading the extra modules.

I can't give you my own 3.9 Module declaration cause in my A1200 my own burned 3.9 ROM so no LoadModule, and in my A600 i have my own custom 3.9 ROM loaded as a file via MapRom so again... no LoadModule in there as well

Mfilos is right,

If your loading the modules into ram, then you need to alter setpatch to NOROMUPDATE.

Also, I thought you had a deneb?
If so, then why mess with startup, just throw the modules into the deneb.

I have no problems with BB3 or BB4.
I have been running them for atleast 8 months now fine.

Im even using the so called buggy graphics.library without issue.
Both my A1200 and A600 and loving it.

I did have an issue with BB2 ROM Update on A4000 though, but thats a documented problem.

Hi guys, thanks for the help.

I am running Setpatch NOROMUPDATE QUIET - have been from the word go.

BUT, I then have Blizkick kicking the ks rom image into fast ram - C:Blizkick KICKFILE * MODULE MoveVBR RamLibStack CPUCARD QUIET

This loads the kickstart from Rom into ram with the two modules - MoveVBR and RamLibStack. But I had this in place before installing boingbag 3/4 so this cannot be the problem.

Running SysInfo, I can see that my resident libs/devs are:

Kickstart 45.59
Graphics.library 40.24
Intuition 40.85
68040.library 44.2
Icon.library 46.4
Datatypes.library 44.47
Cybergraphx.libarry 41.4 - which is odd as Im using P96, must be an emulation layer

scsi.device 43.43

These all appear to the the up to date libs/devices.

Oh, and I fixed the RawBInfo problem... I can now drag and drop and save all icons.... you will laugh when I tell you what it was. I had lowered the priority to -1 so it didnt steal cpu time from more important task..... such as DoomAttack. :) Apparently it idoes not like having it priority changed.

So, the only problem I have left with this entire system is when I right click on a volume and choose format - I get an intuition lock up.

Everything else - rename, delete, information, copy etc etc all function fine.

Strange though that the format command works fine from the icon.
Any ideas?

---------- Post added at 21:54 ---------- Previous post was at 21:47 ----------

I just commented out Blizkick and cold rebooted. I can tell NO difference in speed.... is there actually any difference to having the rom image in ram? And if so, how can you actually tell?!

If there is no point I will save myself a second boot my ditching Blizkick. Also, are there any worthwhile Blizkick modules (I have yet to find one)?

More than that, is there any decent Deneb modules? And can you load ks to fast using the Deneb? Is a second boot required?

Since you have a Deneb I'd say... use that instead! Everything in Deneb doesn't require a reboot since it's loading them too early :)
You can use almost every BlizKick Module into Deneb's flash and will use them like you were using BlizKick.

Cooliez, so you are saying there is no point kicking the rom image to ram? I cannot see any difference in speed... but everywhere it says it is supposed to be faster... even running the intuition test in AmiGod there appears to be no difference!