AmigaOS 3.9 Boing Bag #3

[dannyp1]

Did you read the post that you quoted?  That answers your question.  

[TheGoose]

@Gulliver

Hey, I looked over a number of the patches; I'm not going to apply a bunch of spatch files on my system. If what can be complied, is complied and then tested some more, I'd love to get my hands on BB3. So, there is some installation packaging planned? Sounds like yes from the discussion...?

I guess that go back into the license stuff again, hmm? But maybe not, these patched ones would be new not the originals...

Nice effort and work.

[Gulliver]

Thanks to everyone for their kind words. Anyway, keep in mind i am just one of many working on this project, and they all truly diserve the credits.

@TheGoose

You can get the beta version of the installation  package at:

http://amigan.1emu.net/releases/BoingBag3.lha

Please remember to report any bugs if you find them!

[amigadave]

We are not trying to sent people from this site, but protect it. If there are original copyrighted (even patched version of the originals) in the file linked and the owner finds out, then they can have this site shut down. It's happened before. We were down for three or four days a few years ago over someone posting another person's (owner of Amiga Web Directory) event pictures.
If the Boing Bag just has the patch files and installs by patching the original files, then that would be fine.
Sucks, but this is what keeps us running. One DCMA violations letter to our ISP and we go offline.

If BoingBag3 had a simple check that required the OS3.9 CD to be in an attached CDROM drive, it would prove that the installer of BoingBag3 has a license to use the files being patched, that are from the OS3.9 CD anyway.

As for containing other copyrighted files that are obtained elsewhere, that is another matter that would have to be resolved.

[Minuous]

If BoingBag3 had a simple check that required the OS3.9 CD to be in an attached CDROM drive, it would prove that the installer of BoingBag3 has a license to use the files being patched, that are from the OS3.9 CD anyway.

That would be redundant since BB2 already does such a check before installing itself, and BB3 checks that BB2 is already installed before installing itself.

[amigadave]

That would be redundant since BB2 already does such a check before installing itself, and BB3 checks that BB2 is already installed before installing itself.

Good point!  I did not know that since I have not used your BoingBag3 installer yet (but hope to in a few minutes).

Edit:  Well, the install script for BoingBag3 went smoothly and looked good too. Everything seemed to be okay until I altered the Startup-Sequence as directed in the install process.  Now I get an error message during the boot process which tell me that RAM-Handler version 40 (I think this is the version it is reporting) is already resident and LoadModule reports a failure to load object, or something like that.  These are the exact lines I added to my Startup-Sequence immediately above the existing SetPatch line.

;BEGIN BoingBag3
SYS:C/LoadModule L:RAM-Handler L:Shell-Seg, Devs:scsi.device NOREBOOT
SYS:C/SetPatch SKIPROMMODULES filesystem,RAM-Handler,scsi,shell QUIET
;END BoingBag3

I then commented out the existing C:SetPatch QUIET line just below what I added by adding a semi-colon in front of it.  There is no mention of what to do with the existing SetPatch line in your original Startup-Sequence file in the BoingBag3 install instructions, or the install script, so you might want to add something about that.  

After it gave me the error message and would not complete booting again, I then booted from my other original boot partition and also commented out the IDE-Fix IF-THEN statement lines as I do not have IDE-Fix, but that should not make any difference, should it?  Do I need the IDE-Fix IF-THEN lines for the A1200's internal IDE controller?  If I do I will remove the semi-colons from those lines to activate them again.  Commenting out the IDE-Fix lines had no effect on the problem, but I saw no reason to have those lines working if I don't have IDE-Fix installed on my A1200 (unless it is going to get installed in the process of BoingBag3).

I will work on it more tomorrow (actually later today as it is after 3am).  Let me know what you think about the error I am getting from the startup-sequence after adding the lines above that were in the BoingBag3 Installation script.

[Minuous]

>Now I get an error message during the boot process which tell me that RAM-Handler version 40 (I think this is the version it is reporting) is already resident and LoadModule reports a failure to load object, or something like that.

Odd...I'm not having much luck reproducing this one...

>There is no mention of what to do with the existing SetPatch line in your original Startup-Sequence file in the BoingBag3 install instructions, or the install script, so you might want to add something about that.

OK, done.

>After it gave me the error message and would not complete booting again, I then booted from my other original boot partition and also commented out the IDE-Fix IF-THEN statement lines as I do not have IDE-Fix, but that should not make any difference, should it? Do I need the IDE-Fix IF-THEN lines for the A1200's internal IDE controller? If I do I will remove the semi-colons from those lines to activate them again. Commenting out the IDE-Fix lines had no effect on the problem, but I saw no reason to have those lines working if I don't have IDE-Fix installed on my A1200 (unless it is going to get installed in the process of BoingBag3).

It doesn't do anything to IDE-Fix.

[Gulliver]

AmigaOS 3.9 Boing Bag #3 LEGAL

1.Usage
You are entitled to use BoingBag3, only if you got a legitimate AmigaOS 3.9 licence.

2.Distribution and Costs
You can distribute the BoingBag 3 using any media only if you keep all the files in it intact, and provided you do it free of any charge at all.
You are not allowed to distribute this BoingBag with other products and charge money for the entire package or bundle. It cannot be given away free as an extra for the purchase of another product. No media, handling, packing and/or shipping charges are allowed for the distribution of this software product.

3.Copyrights
All trademarks and software products are copyrights of their respective owners.

4.Limitations of Liability
In no event shall any contributors, developers or copyright holders be liable
for any damages whatsoever, including - but not restricted to - lost
revenue or profits or other direct, indirect, special, incidental or
consequential damages, even if they have been advised of the possibility
of such damages, except to the extent invariable law, if any, provides
otherwise.

5.No Warranty
The Software and this license document are provided AS IS with NO WARRANTY
OF ANY KIND, INCLUDING THE WARRANTY OF DESIGN, MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE.

6.Copyrights Acknowledgements of individual BoingBag 3 components:
AmigaOS 3.9 is copyrighted by Amiga Inc.
AHI is copyrighted by Martin Blom
AWeb is copyrighted by AWeb APL Development Team
MooVid is copyrighted by László Török
AWNpipe is copyrighted by William H. M. Parker
XADMaster is copyrighted by Dirk Stoecker
PlayCDkludge is copyrighted by Ralph Babel
Appp.device is copyrighted by Thomas Bickel
Asyncio.library is copyrighted by Achim Stegemann
Workbench.guide is copyrighted by Matt Hey
Reqtools.library is copyrighted by Nico François and Magnus Holmgren
HighGFX is copyrighted by André Pfeiffer
Mpega.library is copyrighted by Stephane Tavenard
Say is copyrighted by Peter Kaltstein
Translator.library is copyrighted by M. Barlow and Francesco Devitt
Amplifier is copyrighted by Thorsten Hansen

PS: Constructive criticism is welcomed! By the way, there is a dedicated Amiga user trying to contact these Amiga developers in order to get their full blessing the way we intend to. If someone wants to help, you are welcome to do so, as many developers are extremely difficult to track down and reach.

[matthey]

Edit:  Well, the install script for BoingBag3 went smoothly and looked good too. Everything seemed to be okay until I altered the Startup-Sequence as directed in the install process.  Now I get an error message during the boot process which tell me that RAM-Handler version 40 (I think this is the version it is reporting) is already resident and LoadModule reports a failure to load object, or something like that.

I got this error message after a reboot too. The solution is to turn the Amiga off. The problem is gone after turning the Amiga back on.

Other installation problems...

Libs:xadmaster.library is improperly named Libs:xadmaster.device for the 68020 version at least.

I had the same problem with the incorrect (cycling) text colors on Workbench with the newest workbench.library on my stock 3000. I couldn't get it to go away by saving the pallet prefs like last time. The 2 configurations that have exhibited this problem...

3000T CSMK3 68060 with Mediator Voodoo4 Picasso96
3000 68030 with CyberVision64 Picasso96

Problem happens on both RTG and non-RTG screens and with latest P96 software as well as P96 v1.43b.

[dannyp1]

I think I got it to go away by saving the fonts in prefs.

[AmiKit]

@Gulliver

First of all, many thanks for your effort!

AmigaOS 3.9 Boing Bag #3 LEGAL

1.Usage
You are entitled to use BoingBag3, only if you got a legitimate AmigaOS 3.9 licence.

You simply cannot re-distribute original or patched AmigaOS files, no matter what you write into your readme. Sorry, that's a fact. In addition I doubt you can use the name "Boing Bag" and pretend it's official one (according to the archive's readme). It's not.
(Btw. the previous official Boing Bags contain full patched system files just because they were created and distributed by the original Amiga OS license owner - which you are not.)

The only legal solution for this unofficial Boing Bag, besides renaming the package, is to include patch data (.pch files) instead of full and patched AmigaOS files. The full files can be created on user's computer - by an installer. It should be easy to write one.

[Minuous]

I got this error message after a reboot too. The solution is to turn the Amiga off. The problem is gone after turning the Amiga back on.

Will change the instructions accordingly. Thanks.

Other installation problems...

Libs:xadmaster.library is improperly named Libs:xadmaster.device for the 68020 version at least.

Oops, will fix.

pretend it's official one.

No one is pretending it's official, what are you going on about?

[arnljot]

You simply cannot re-distribute original or patched AmigaOS files, no matter what you write into your readme. Sorry, that's a fact.

I think we should discuss how much work it is to have the patch contain patches and have the installer do the patching, or have Hyperion sanction this effort.

In addition I doubt you can use the name "Boing Bag" and pretend it's official one. It's not.

You mention renaming it. I agree.

Two naming suggestions for your[ie everyone] consideration:

1) Community BB3.
2) Boing Ball 3 (start numbering at 3...)

[Gulliver]

@arnljot

Isn´t Amiga Inc. still the copyright holder of AmigaOS 3.9? There is already a helpfull user trying with no success to contact them reagarding this project, so that we may achieve official status. If anyone has or knows another way to contact Amiga Inc.  please drop me a line.

About naming, well it is called "Unofficial BoingBag 3", so the name says it all. So just for simplicity sake it is named in several places BoingBag 3, but then that is informally.
And this Unofficial adjective has been in its name since the beginning. If unsure check http://lilliput.host-cafe.com
However if you would like a name change, make a poll and if you get the majority of votes from all the choices presented here, or even some new ones. Then we can change it, it is really not an issue.

@AmiKit
Thanks for your recommendations and kind comments, but as said before, I am one of many which are involved in this project, and they all trully diserve the merit and the corresponding credit!

[matthey]

I think I got it to go away by saving the fonts in prefs.

That fixed it. Thanks. I guess I remembered wrong. It would be good to update the BB3 web site that saving SYS:Prefs/Font settings will fix strange colored Workbench text from workbench.library. Maybe put the info in the readme with installer too.

[Gulliver]

Give me 10 minutes and consider it done!