a bit scared of boingbags 3 & 4

[honx]

i discovered something weird in locale prefs, see attachment, yellow marker.

[Minuous]

Looks like some of the filenames have become mangled on my system at some point. Issue has been fixed for the forthcoming V1.3, however this is the only change so far; waiting to make some other changes before releasing.

[honx]

please tell me which files/folders i'll have to delete when it comes to the point.
so that there only stays the correct espana thingamajigs.

[honx]

are you also able to fix the unarc tool from os 3.9? it replaces spaces in filenames by underlines.
i noticed this problem while unpacking eagleplayer - you can see second page of this topic.
example: "14 Bit Amplifier" (real filename) -> "14_Bit_Amplifier" (after unarc) --> a HUGE problem!

[Minuous]

Originally Posted by honx

please tell me which files/folders i'll have to delete when it comes to the point.
so that there only stays the correct espana thingamajigs.

Files2/Locale/Countries/+sterreich.country (and, correspondingly, SYS:Locale/Countries/+sterreich.country )
Files2/Locale/Countries/espaªa.country (and, correspondingly, SYS:Locale/Countries/espaªa.country )

are you also able to fix the unarc tool from os 3.9? it replaces spaces in filenames by underlines.

Well, not easily, as there is no source code available for it.

[honx]

for future updates: how can i prevent boingbag4 from overwriting icons in prefs: folder (.info)?
changed most icons in prefs: to icons with blue question mark instead of default black/white one.
so next time i install a newer version of boingbag4, i don't want these icons to be overwritten.
how can i prevent that from happening? and another question: did classactprefs also come with boingbag?
does such a blue question mark icon also exist for classactionprefs? it's the only one i couldn't find.
it's the only icon in prefs folder which still has got this (in my opinion) ugly black/white question mark.

[idrougge]

Before installation:

Protect SYS:Prefs/#?.info -W

To make icons writable again:

Protect SYS:Prefs/#?.info +W

If the installation script fails because your icons are write protected, you can just copy the icons to a safe place and copy them back later on:

Copy SYS:Prefs/#?.info SafePlace:

[Minuous]

did classactprefs also come with boingbag?

No, neither ClassAct Prefs nor ReAction Prefs (nor icons for those) are in BB4, the old ReAction Prefs is left intact as there has not been an update since. There is no reason for anyone running OS3.5 or later to have ClassAct Prefs, it is rendered obsolete by ReAction and thus should be deleted if present.

does such a blue question mark icon also exist for classactionprefs? it's the only one i couldn't find.

I don't know, as I haven't looked. But such a change is easily made; just doing a flood fill in the icon editor should be all that is necessary.

[honx]

Originally Posted by Minuous

I don't know, as I haven't looked. But such a change is easily made; just doing a flood fill in the icon editor should be all that is necessary.

unfortunately not really. the old black/white question marks are flat with white border.
while the new blew ones use a colour gradient which gives them some kind of 3d look.
i could fill in the black with any other colour but it would still remain flat with white border.
in attached screenshot of prefs folder you can see the difference, old icon is far right one.

[Nibbler]

Never had any issue with Boing Bag 3&4.
I use it on my Amiga CD32 Pro.

Hmmmm....wait, i had one issue with boing 3&4 .
If Setpatch was set to ROMUPDATE the "new Romfile from that 3/4 boing pack always crashed my system. ( i heard many people had that problem)

So i just use the Romfile from 3.9 and everything is hunky dory.
Or Setpatch "NoRomupdate" , because i dont see the point on an AmigaCd32 Pro with 8MB fastram to add all this extra crap that i dont need.

( yeah i know, you could say: "for what 3.9 on a AmigaCd32 anyway? " ; but my Amiga CD32 Pro came with it ( years ago ) .. thats why

; besides, some features are quiet nice

[honx]

protecting icons did not do anything. and i moron did not save .info files, now i have to search icons again...

[idrougge]

Sorry, that's my fault. They should have been delete protected as well, with

Protect SYS:Prefs/#?.info -WD

[honx]

this didn't help either. nevermind, today i made backup of all prefs icons...

[idrougge]

That really didn't help?

[honx]

no, i used "Protect SYS:Prefs/#?.info -WD" in shell before installing new version 1.31 of boingbag 4.
afterwards icons were overwritten again. fortunately this time a made a backup prior to update.

[Minuous]

Some OS3.9 CDs had all the protection bits set, thus the BB3&4 installer will force an overwrite of protected files if necessary.

[honx]

latest boingbag #3/4 v1.39 my broke aweb. browser startup help page not displayed anymore (attatchment #1).
if i try opening any .html file by doubleclick, some apl is missing (attachment #2). path is set in user-startup (#3)

so how do i fix that? (and why did i have to update boingbag anyway?) -> #nevertoucharunningsystem

and openurl prefs won't let me edit browsers in browsers tab. i can add, clone and delete but i can't edit entries.
nothing happens if i click on edit button, so i am unable to change any paths...

[Minuous]

I'm not getting any of these errors.

>openurl prefs won't let me edit browsers in browsers tab

OpenURL is not part of BB3&4. There have been no changes to system components that might cause this.

>so how do i fix that?

Have you installed it on a clean OS3.9+BB2 system?

>why did i have to update boingbag anyway?

Various components eg. icon.library etc. continue to be updated, so it needs to be kept in sync. Also an AWeb bug was worked around and all duplicate files were removed.

[honx]

i'm using the same system that i used a year ago as i installed bb3/4 for the first time...
no clean install anymore, just updating bb3/4 from 1.38 (no problems with that) to 1.39.
only for aweb i won't do fresh install with all config involved, i'd rather go without aweb.
besides aweb everything else is still working without any problems i'm aware of...

anyway, as workaround for second error i assigned "aweb_apl:" leading to aweb directory.
about first problem: filename got an underline (AWeb Manual became AWeb_Manual.html).
but aweb browser still was looking for the manual without underline, so i renamed the file.

about openurl: i'm curious where i did get this openurl thingy. i did not intall it actively...

[honx]

btw. what duplicate files have been removed? i have to check my system for these files to delete them.
as far i know an install script doesn't delete anything, so i assume these duplicates are still in my system...