Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Gulliver on May 30, 2008, 01:36:57 AM
-
AmigaOS 3.9 Boing Bag #3 - UPDATED 03-DIC-2009
====================
NO WARRANTIES: USE AT YOUR OWN RISK!
Well, it seems pretty clear nowadays (may 29th 2008), Amiga Inc is going nowhere, and there is not even a clear path of upgrade for Classic Amiga 68k users. So I decided to recreate an Amiga Boing Bag list that could include nearly all current semi-official patches for 3.9. Caution has been taken to avoid the use of patches that may cause problems, but then i can guarantee nothing.
This Boing Bag has been tested on both an A1200 and UAE with different configurations, and it works beatifully!
A word of warning: This list was created in an attempt to create a post AmigaOS 3.9 boing
bag #2 update, its proper installation requires of a skilled Amiga user!
For futher details keep on reading this document.
__________________________________________________________________________________________
To get the latest updates, downloads and information, visit: http://lilliput.host-cafe.com
__________________________________________________________________________________________
AMIGAOS 3.9 BOING BAGS I & II
AMIGAOS 3.9 PROGRAM UPDATES
AHI 6.7
AMPlifier 2.35
somehow download and install the AmiKit package, its in there, just take the time to etxract & replace your AMPlifier files from over there.
XADmaster V12.1a + XADmaster.key.
AWeb APL Lite 3.5 (version 3.5.09)
Action (MooVId) 1.6
Added support for: INTEL INDEO 3.1 & 3.2 (IV31/IV32), JPEG/JFIF (MOV) 8/24bit, QT3/QT4/QT5 streaming MOV files, 3IVX Delta 1/2 (3iv1), QT 64bit filesupport, OpenDivx/DIVX4/DIVX5.xx (DIVX/DX50), MPEG4/MPEG4 V1 (DIV1/MPG4/MP41), MPEG4 V2 (MP42), MPEG4 V2 (MP43), MPEGI/Layer2 audio (mp2), MPEGI/Layer3 audio (mp3), Sorenson Codecs (QT/SVQ1), MPEG4/QT6, and lots of bugs got fixed & few new features.
A file named "3ivx1d3_codec_68k Moovid.lha" that is the 3iv1 Delta 3 codec distribution for 68k Amigas and works with MooVid
AMIGAOS 3.9 REPLACEMENTS:
Serial.device v43.7 is buggy and is causing modem connection problems. Use previous serial.device v43.4, which allows you to connect fine.
There are two sets of printer drivers on the 3.9 CD:
The drivers in: AmigaOS3.9:Emergency-Boot/Devs/Printers/ are the original drivers from the OS 3.5 CD, and should work fine.
The drivers in: AmigaOS3.9:OS-Version3.9/Workbench3.9/Storage/Printers/ are from Boing Bag 1, and are known to be buggy.
For omniscsi.device users (GVP scsi boards & adapters), there is a bug in PlayCD, and a workaround called "playcdkludge"
There is a new appp.device v3.4 which has a new function that lets you use long usernames and activates a DSL-mode that negotiates the necessary options for a DSL line with the dialup computer.
AMIGAOS 3.9 UPDATE PATCHES
Amigaguide.datatype 45.6 - Fixes race condition with amigaguide.datatype V45.5: some guide
documents are not displayed properly if their size is odd.
Genesis has packet fragmentation issues. There is a fix for that
Icon.library 46.4a - Icon/Copy takes ICONCTRLA_SetGlobalMaxNameLength into account now, plus many fixes, no more memory leaks using Deficons tool etc. IconBeFast like functionality. it is optimized for 68020+ and is romable
MultiView 45.10 - Many fixes
Rexxsyslib.library 44.2 - fixes longword write into unallocated memory
Workbench.library 45.131 - Too many fixes
The CacheCDFS shipped in OS 3.9 always mounts a CD as "Unnamed" if its
name consists of identical characters (e.g. "Q", "GG", "WWW", ...).
Asyncio.library 40.6 - few bug fixes
Awn-pipe 2.54 – Adds new features to this pipe and GUI generator
Say – Boingbag3 marks the return of the popular speech program, that now supports different accents.
Workbench.guide – A general help guide for BoingBag3 users, should be placed into SYS:Locale/Help/english/Sys/. So from now on, pressing the Amiga keyboard ¨Help¨ key, will make this workbench.guide, to automatically be displayed.
KICKSTART ROM UPDATES
Scsci.device 44.2- Adds proper LBA48 IDE support, so disks upto 144 petabytes (144,000,000 gigabytes)can be used. NOTE:HDToolbox works fine (at least up to 160GB) Some version create stupid default partitions but just manually delete them before creating "real" partitions. It also fixes a bug that overwrites memory past the allocated bytes. Adds speedyIDE optimizations
Shell 45.27 - Too many bugfixes to list
RAM-Handler 44.24 - Fixes the RAM disk to show the real size occupied - its no longer
100% full.
Console.device 44.10 - Fixed bug with rp_Font usage; console caches rp_Font of last opener's window in its own device base and could make use of it even after that window was closed. This could lead to race conditions such as accessing unallocated memory. For safety, this cached rp_Font copy is reset to gb_DefaultFont on each CloseDevice() now. It also fixes an ancient bug of console.device which doesn't reset text styles on CSI0m if aSDSS command was used.
FastFileSystem 45.15 - fixes mismatched memory deallocations and disk validation bug of FastFileSystem V45.13.
FUTURE
I hope someday someone can actually create an automated install script that installs all of this stuff!
If you happen to develop or meet by chance a cool and friendly AmigaOS 3.9 patch, then dont hesitate to add it to this list.
Hopefully i might release an AmigaOS 3.9 Boing Bag 3 contribution software list (Some usefull 3rd party software for 3.9).
CREDITS FOR THEIR PROGRAMS & PATCHES (Thanks to all of them)
Doobrey
Peter Keunecke
Toni Wilen
Chris Hodges
Thomas Richter
Ralph Babel
AWeb APL Development Team
Thorsten Hansen
Dirk Stoecker
László Török
Mikolaj Calusinski
Oliver Roberts
Christian Sauer
Thomas Bickel
Ratte
The AHI Team
MM
THE AUTHOR
I wish to remain anonymous, i am doing this as a contribution to our small Amiga
community. I hope someone finds it usefull.
-
Thanks for all the work you did on this.
Would be nice if this could be on a web page somewhere.
ManRaven
-
There's also this (http://www.monkeyhouse.eclipse.co.uk/amiga/boingbag/). A little out of date now, but still useful.
Thanks for finding out the changes for the AmiKit patches. I'd been looking at them but there was no indication of what they did. I might actually install them now. ;-)
-
user Nlandas said on another thread, he might build a web site with this info, i already sent him a private message regarding the availability of this data.
I am glad you found it usefull! :)
-
Thank you Gulliver!
I hope Nlandas does create a site for this information, I am surprised that no one has done so in the past. It will be great to have such a resource and hopefully support for this effort will grow.
Any chance you will begin work on an automated install script for all these updates and patches?
-
ManRaven wrote:
Would be nice if this could be on a web page somewhere.
See here (http://www.amiga.org/forums/showthread.php?t=36609).
-
weirdami wrote:
See here (http://www.amiga.org/forums/showthread.php?t=36609).
:-D
-
@amigadave
I will try to make a script, but it will be painfull as hell for me as i dont know how to, but anyway, i will give it a try (but expect nothing as outcome).
It would be a hell of a lot easier if someone actually had the knowledge to make the install script/program and gives it a try.
-
Gulliver wrote:
user Nlandas said on another thread, he might build a web site with this info, i already sent him a private message regarding the availability of this data.
I am glad you found it usefull! :)
Message received - I didn't see this second updated thread. I've created a quick site basically just your message for now. I'll move all files internally if allowed to keep broken links from occuring and see what else could be updated based on future information.
Hopefully, Gulliver or someone can make a script to add to it.
-Nyle
Very rough Amiga web page. (BE KIND) (http://landas.com/Amiga.html)
-
Thanks, although I remember the site mentioned above, but I will give it a try. I don't like installers though. :-)
-
Phantom wrote:
Thanks, although I remember the site mentioned above, but I will give it a try. I don't like installers though. :-)
Wow, you must be psychic phantom because I just created the site today. :-)
I can understand the dislike for installers but the plan would be to offer both the manual install files and the installer script for non-Amiga Gurus. :-D
-Nyle
-
Wow, you must be psychic phantom because I just created the site today.
Maybe... :crazy:
-
Ive always wanted off screen window dragging - Are there any tools that allow this on OS3.9?
-
PowerWindows (http://aminet.net/package/util/misc/PowerWindows) allows you to drag windows off to the right and bottom of the screen only, (not off the left edge or top edge).
An updated version PowerWindowsNG (http://aminet.net/package/util/misc/PowerWindowsNG) will allow you to use any direction, but you need to patch the ROM to handle it.
-
BooBoo1200 wrote:
Ive always wanted off screen window dragging - Are there any tools that allow this on OS3.9?
SYS:Prefs/ScreenMode ?
-
ffs 45.14
icon 45.5
...
-
_Steve_ wrote:
PowerWindows (http://aminet.net/package/util/misc/PowerWindows) allows you to drag windows off to the right and bottom of the screen only, (not off the left edge or top edge).
An updated version PowerWindowsNG (http://aminet.net/package/util/misc/PowerWindowsNG) will allow you to use any direction, but you need to patch the ROM to handle it.
Thanks :-D
Thats excellent finaly - I realy did search
I havent realy tried PowerWindowsNG yet hopefuly works with SKick.
Sorry for going off topic!
-
@Ratte,
Do you have links to those files or any info on them?
-
@Gulliver,
Thanks for putting the links to all the upates in one place!
-
I have seen FFS 45.15. Is this the newest? I have not seen the patch for icon.library 45.5. Where can it be found?
Dan
-
Just in case if you havent noticed, the information of the first post has been updated!
Good luck!
-
Gulliver wrote:
AmigaOS 3.9 Boing Bag #3 (edited 23 sept 2008)
========================
...
XADmaster V12.1a + XADmaster.key
http://www.dstoecker.de/
...
Thanks for the effort designing this list!
I just wanted to mention that all the links to download the XAD components at the link you gave above do not work.
They all result in
"FTP Error
pub/aminet/util/arc/xad[insert component name here].lha: No such file or directory
ftp.protocol 24.43 © Copyright 1996 Jason Gouger, 1997-2005 Stefan Burstroem"
Do others have the same problems?
-
Quick remedy - change ftp to http.
-
Lots of new updates & new web links. See first post of this thread for this changes!
-
Lots of new updates & new web links. See first post of this thread for this changes!
Most of the links are broken...
-
I have offered Gulliver free webspace where he could upload the files and perhaps create a website. Hope this helps.
-
Lots of new updates & new web links. See first post of this thread for this changes!
The web links are not working.
-
I guess nobody liked to have direct links to the files they hosted. Will have to create a website, a torrent, a rapidshare file or something like that. Just be patient and you will see this in some form.
PS: I am really sorry for those webmasters/site owners who didnt like i linked their files. My sincere appologies!
-
Icon.library 46.4a - Icon/Copy takes ICONCTRLA_SetGlobalMaxNameLength into account now, plus many fixes, no more memory leaks using Deficons tool etc. IconBeFast functionality.
A fix for this is in http://eab.abime.net/attachment.php?...6&d=1250041669 it is optimized for 68020+
I am interested to know about the differences between this library and the one from http://aminet.net/util/sys/OS39_update_patches.lha
Both versions are 68020 optimized, ICONCTRLA_SetGlobalMaxNameLength is implemented and the memory leaks have been fixed.
Also, the RemApollo.lha archive contains many fixes for OS components. I haven't check if all of them are included in this thread. They are probably.
-
the icon.library 46.4a has as an addition to those features you mentioned:
-IconBeFast functionality built in (see iconbefast readme in aminet for more details)
-It is romable
-It is smaller
Please do check to see if you find something else, it will be apreciated :)
-
the icon.library 46.4a has as an addition to those features you mentioned:
-IconBeFast functionality built in (see iconbefast readme in aminet for more details)
-It is romable
-It is smaller
Please do check to see if you find something else, it will be apreciated :)
Ok. I will.
-
Action (MooVId) 1.6 download link doesn't work
-
Gulliver your webspace is set :)
See /pm for further details.
-
Thanks, i will read my PM
-
Website is ready
Visit Unofficial AmigaOS 3.9 BoingBag 3 at
http://lilliput.host-cafe.com
Still, i encourage discussion and debate of this subject on this thread!
Thank you Nostromo!
-
No problem Gulliver =^-^=
I would want to install that soon :)
-
Minor website update:
added asyncio.library 40.6
-
Good news! More AmigaOS 3.9 BoingBag3 updates:
Awn-pipe 2.54 – Adds new features to this pipe and GUI generator
Say – Boingbag3 marks the return of the popular speech program, that now supports different accents.
Workbench.guide – A general help guide for BoingBag3 users, should be placed into SYS:Locale/Help/english/Sys/. So from now on, pressing the Amiga keyboard ¨Help¨ key, will make this workbench.guide, to automatically be displayed.
Plus more speed optimizations tips
for all this, and more visit http://lilliput.host-cafe.com
-
Hey, thanks for hosting the files at sharebee. :)
Is there a changelog somewhere for the BB #4 updates like the Xadmaster.library?
Regarding GigaMem, i have read that VMM is better, but i have never compared them.
-
No problem, I tested shrarebee and it is actually better than mediafire in all senses.
XADmaster.library on BB4 had no changelog when i found it! you can try to figure what modifications were applyed by inspecting http://sourceforge.net/projects/libxad/
I tryed VMM before and it was not as compatible as Gigamem with all apps!
-
Sharebee is really messed up on my computer. It won't let me download any of the files. It is loaded with pop-ups that are trying to load and wants me to take tests and fill out forms asking for my email, name, etc. before I can download a file. Media fire always worked great but this Sharebee is worthless. What's going on?
-
@dannyp1
I doesnt happen on my 3 setups. You do not need to put your email or fill forms anywhere, just follow one of the links that you see below the name of the file you are requesting at sharebee like zshare, megaupload, ect.
Sharebee is like a central download hub, where you choose your desired download service to download just the same file.
If you still have problems, please give me the name & version of your browser to test it myself!
-
Well, I got it working. I used ZShare and it made me sit and wait 50 seconds before I could continue to the download. I am still getting pop-ups. I'm just not seeing where you think this is better in all ways to the previous method. Thank-you for your help. The bottom line is I now have the files downloaded. :)
Dan
-
Dan, maybe you dont see the good side of it. Sharebee is more Amiga browser friendly (Have you tryed mediafire on AWeb or Ibrowse? It sucks big time!), and it gives you plenty of choices from where to download stuff, plus, if for example ZShare is down or gets a disk failure, you still got all the other online storage sites which will serve as a backup.
-
Why can't the files also be hosted on lilliput.host-cafe.com?
-
@kolla
I havent tryed yet. Will do it when i have a bit more time.
-
OK, preliminary installer for OS3.9 Boing Bag #3 is ready.
http://amigan.1emu.net/releases/BoingBag3.lha
http://amigan.1emu.net/releases/BoingBag3.readme
Enjoy...
-
Excellent work Minuoius!
I will test it and then get back to you for further comments :)
-
This is a long-needed update and its great that you can now install it without having to find and install all the individual updates and patches. Would it be possibel though to provide an option to install CPU specific versions? For eample I have 060 board and the XAD version intalled by BB3 is for a 020. So I reinstalled the 060 version after I had run the BB3 update.
Weed
-
its also trashed my png support through uodating icon library, reverting back to icon.library v53.4 (patched) fixed it.
Weed
-
Excellent, thank you very much, will give it a try :)
-
@Minuous
First check done, found the following issues:
1)LoadModule is 40.11 should be latest from aminet (version 40.12)
2)
BoingBag3.readme QUOTE
These components are new:
PlayCDKludge 1.2
Say 43.0
translator.library 43.1
BoingBag3.readme END OF QUOTE
List is missing narrator.device 37.7
3) Missing update:
Ram-handler is 44.23, should be 44.24
Thats it for now ;)
-
Would it be possibel though to provide an option to install CPU specific versions? For eample I have 060 board and the XAD version intalled by BB3 is for a 020. So I reinstalled the 060 version after I had run the BB3 update.
Actually it is supposed to automatically check the CPU you have and copy the correct version, must be a bug in the script.
Thanks all for the feedback, I will make a V0.2 within the next few days.
-
Keep up the good work
-
OK, preliminary installer for OS3.9 Boing Bag #3 is ready.
http://amigan.1emu.net/releases/BoingBag3.lha
http://amigan.1emu.net/releases/BoingBag3.readme
Enjoy...
That's awesome, well done :)
-
There is newer...
narrator.device 37.8
reqtools.library 39.3
http://www.heywheel.com/matthey/Amiga/BB3libsnew.lha
and a better workbench.guide here...
http://www.heywheel.com/matthey/Amiga/WBguide.lha
It would be nice to include these newer P96 libs also...
http://www.heywheel.com/matthey/Amiga/P96new.lha
Looking good though :).
-
There is newer...
narrator.device 37.8
reqtools.library 39.3
http://www.heywheel.com/matthey/Amiga/BB3libsnew.lha
There's also reqtools.library 39.3 Rev2. Optimized for 68060, but works for all 68020+ CPUs:
http://www.ziosante.it/downloads/ReqToolsLib.lha
Where did you find this version of narrator.device? :)
-
@Mathey
Thanks for finding that library and that narrator.device. I will soon fix BoingBag3 website accordingly!
I have seen your workbench.guide, which is certainly very good. In fact it has a lot of information on how to handle workbench using Arexx. But i must say that i disagree that it suits better for BB3, as it lacks all the general help information regarding for example: Workbench drawers, a general help FAQ with usual problems and their solutions, a brief description of what each command and tool does, etc. Anyway, i invite you to rip the information fom both, and attempt to merge them. That could be really usefull!
The Picasso96 stuff, in my humble point of view, should be added to a BoingBag3 Contribution software list, as such was the way Picasso96 was intended to be on AmigaOS3.9. As soon as i have a little more time i will attempt to generate that list and put it online including your Picasso96 findings.
-
Where did you find this version of narrator.device? :)
It was the Mu/Thor/Thomas Richter's patch. It just bumps the stack a little. Nothing major.
Thanks for the ReqTools link.
-
@Matthey
I have seen your workbench.guide, which is certainly very good. In fact it has a lot of information on how to handle workbench using Arexx. But i must say that i disagree that it suits better for BB3, as it lacks all the general help information regarding for example: Workbench drawers, a general help FAQ with usual problems and their solutions, a brief description of what each command and tool does, etc. Anyway, i invite you to rip the information fom both, and attempt to merge them. That could be really usefull!
My workbench.guide has very specific info on the operation of Workbench, is formatted better with more buttons/links, and supports requester specific and menu help. Your workbench.guide has a lot of additional info, much of it useful but some not so much related to Workbench. I think it would be best to make separate guides for BB3, Workbench, Arexx and AmigaDOS and link between them. Ernest Unrau has an excellent ARexx guide already that could probably be used (update recently added to Aminet). My Workbench guide could be used with your additional Workbench related info added. I couldn't find an AmigaDOS guide as good as Ernest's Arexx guide but parts could be borrowed from other places including the work you have done already. English isn't my strong point and I am currently developing a better disassembler to modify programs so my time is limited. It would be better if someone else made the simple tedious modifications if possible. Otherwise, I may eventually get to it ;).
The Picasso96 stuff, in my humble point of view, should be added to a BoingBag3 Contribution software list, as such was the way Picasso96 was intended to be on AmigaOS3.9. As soon as i have a little more time i will attempt to generate that list and put it online including your Picasso96 findings.
That's fine with me. I'm happy that someone is taking the time to finally put this all together. Thanks.
-
@Matthey
I cant agree more! :)
I wish i had the time to edit them myself, but i am too busy at the moment to make that happen. So if someone wants to help on this, it could be nice!
-
AmigaOs BoingBag 3 website updated again:
-Due to popular demand, files are no longer on sharebee, they are hosted at the website
-Updated narrator.device (it is inside the Say archive)
-Added reqtools.library 39.3 (updates the one present in MooVid)
-Added two 3.9 bug entries
-Updated the credits section a bit
Of course you are encouraged to visit the AmigaOS BoingBag 3 website at http://lilliput.host-cafe.com
-
Many people has said that DON'T use latest AHI with real 68k amigas, it has made for morph os/amiga os4 and requires more cpu power than 4.7 wich is last only 68k AHI
???
-
@utri007
Well those claims are not based on facts. AHI 6 has been made for various different platforms, including 68k and it works as intended. The only fact is that if you got a 68000 cpu you should use AHI 4.x because since AHI 5 onwards, you are required to have at least a 68020 cpu or better.
-
OK all, V0.2 has been uploaded, URL is still http://amigan.1emu.net/releases/BoingBag3.lha.
It incorporates the upgrades that have been mentioned, some fixes to the script, etc.
-
Excellent!
Will get back at you with some comments after i play with it a bit.
-
@Minuous
You are missing:
DEVS: scsi.deviceA4000T v43.45 (there is no 44.2 for this model)
DEVS: scsi.deviceA3000 v43.45 (same here)
They are both generated with the following patch http://aminet.net/driver/media/SCSI4345p.lha (you should use the IDE patch version for the A4000T)
There is an update to icon.library 46.4alpha11 -> 46.4.128 released today:
http://eab.abime.net/attachment.php?attachmentid=23628&d=1260984338
My 2 cents
-
I don't suppose a GlowIcon for the Translator prefs has ever been done? The current icon is really ugly :(
-
OK, 0.4 is done, it is the release candidate. Enjoy.
-
@Minuous
Excellent work! We are so near... :)
Details left:
Ratte allowed us to include Highgfx and HD270 drivers which should be located at /sotrage/monitors/. They are both excellent monitor drivers for workbench. Download them at http://aminet.net/driver/moni/HighGFX40_6.lha
The installer should check wich mpega.library to install, so that it installs the one that suits better the cpu. Get mpega.library at http://aminet.net/util/libs/mpega_library.lha
That should be enough!
-
OK, 1.0 beta is released.
-
Quick question....is anything in that archive pirated? I will wait (for a short while) for a reply before I delete stuff.
-
pirated? you mean boingbag3? as far as i know it is a set of patches that a user has to apply to the original files via spatch. so it is completely legal.
-
Why would you want to delete things if you don't know if they are pirated or not? Here we go with the old "Guilty until proven innocent" crap. As far as I can see all of the updates in the BB3 are public domain, freeware, etc. If you go do a search in aminet you will find just about everything. Where did the complaint come from that would inspire you to leave that post?
-
Amiga OS files cannot be freely redistributed without permission (not even in patched form because the new files still contain copyrighted data). That's why various unofficial patch archives (eg. see Aminet) contain only patch data (.pch files) and not the full patched files. If there is any other non-AmigaOS copyrighted files in the "BB3" archive being redistributed without permission, then that's not right either.
-
Why would you want to delete things if you don't know if they are pirated or not? Here we go with the old "Guilty until proven innocent" crap. As far as I can see all of the updates in the BB3 are public domain, freeware, etc. If you go do a search in aminet you will find just about everything. Where did the complaint come from that would inspire you to leave that post?
Read slvrdrgn's post and you'll see why. As far as who complained, I did.
-
I guess my question then is, if you were the one who complained, what were you complaining about when you said yourself that you didn't know if the files were legal or not. I can perfectly understand your questioning if they were legal (We all need to get our jollies somehow). I do not understand the threat to start erasing things. If these are pch patches and things released as freeware such as xad and AHI then you have no complaint. There are enough people spending their time on the English Board already. Are you trying to chase more people there?
-
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.
-
Thank you Argo for being polite and not having an attitude. The guys doing the BB3 have been trying real hard to get it right and it just kind of bothers me when someone jumps in with a chip on their shoulder and starts threatning to erase things.
-
I guess my question then is, if you were the one who complained, what were you complaining about when you said yourself that you didn't know if the files were legal or not. I can perfectly understand your questioning if they were legal (We all need to get our jollies somehow). I do not understand the threat to start erasing things. If these are pch patches and things released as freeware such as xad and AHI then you have no complaint. There are enough people spending their time on the English Board already. Are you trying to chase more people there?
maybe you read between the lines and tried to find a reason to argue? My question was without attitude. If you know me, you'll know I dont usually ask, I just delete stuff thats questionable. Thats what I do. My job isnt to hold your hand and tuck you in at night, its to make sure the owners site doesnt get taken down because of questionable material, among other things.
As far as "If you go do a search in aminet you will find just about everything". Thats Aminet, not Amiga.org.
-Alex
-
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.
You need a better ISP, then. Frankly, ISPs who respond immediately and with prejudice to any supposed DMCA notice are pansies.
There are strict requirements to DMCA notices, and 90% of a random sampling from last year (no cite because I am hazy today) were incomplete or otherwise invalid. In addition, all it takes is a response to the DMCA notice from the supposed offender to get the content back on-line. At that point, the ISP has fulfilled the safe-harbor provision and all interaction is from then on between the alleged offender and the complainant.
None the less, many ISPs just piss themselves when they get a DMCA and take down the site, anyway. As a hosting provider myself, I put the onus on the complainant to prove the validity of the notice, not one of which has been proper, and give the alleged offender and opportunity to respond before acting. Never has one been followed up on.
Of course, I have only dealt with the carpet-bombed MPAA and RIAA types, and even a law firm which took it upon itself to enforce copyrights which it didn't even represent. So I cannot account for the individual copyright owner who retains legal representation for such a matter.
I have my own reservations on the whole copyright issue, but I stay within the law. Unfortunately, it is becoming common for operators of sites which just link to offending material to be held accountable (and I mean just a link to a page, not even directly to the material.) This means that I could potentially bomb a site by putting a link to my own, and then within my site have all sorts of copyright violations.
PCI (Payment Card Industry) regulations are just about the same, but that is a discussion for another topic and time
-
Discussions are allways healthy. This site does not host any files at all, but allways allowed freedom of speech. So wether we like or not the subject in discussion, it is allways a good exercise to be open minded and tolerant.
By the way, the use and installation of BoingBag3 has allways been at your own risk, and implies you have a legit copy of the AmigaOS 3.9 cdrom.
This BoingBag was never official, it is a community effort. That is the reason why it is called "Unofficial BoingBag 3". So if you are looking for Amiga inc. or Haage & Partner endorsement on the project you are looking in the wrong basket.
The entire project was based on my own prerrogatives.I mean that after being an AmigaOS 3.9 user, i thought what if all those upgrades, bugfixes and enhancements around the web for AmigaOS 3.9 could be assembled in a list in an informative way so that everyone that had AmigaOS 3.9 could take the time and effort if they wished, to upgrade their OS.
The project is really cool, from a 68k Amiga user point of view, and many people started to send their own suggestions, and their own software for it.
It grew in a way that i was offered webhosting to put all that information over there. At first i received so many emails and enquiries for particular items, and it took too much time to answer them all, that i had to directly link the files that were required for such BoingBag. A really good guy, with his clear intentions to help our little Amiga community, tryed to create an installer including everything that would make BoingBag 3 something usefull for everyone out there that did not have the skills or time to gather and assemble the BoingBag 3 for themselves.
So in the end if you are still wondering if this is right or wrong, if it is legal or illegal, you should contract a lawyer and speak with a priest of your particular religion, and i am not one or the other. I mean you are allways on your own to find subjective answers to questions i really dont know, how they are or should be answered. Some things are legal in some countries, in others not. Some things are good for some people others see it as terribly wrong. You should decide.
-
Quick question....is anything in that archive pirated? I will wait (for a short while) for a reply before I delete stuff.
No, I have just asked for and received confirmation that the MooVid version in question has been released to the community by the developer Lazlo Torok.
Re. patches: The other four Boing Bags are not distributed as patches. If someone wants to waste their time turning hundreds of useful files back into patch files and then rewriting the installer script and retesting everything, to produce a less useful archive, they can do so. I certainly have no intention of wasting my time doing such a thing.
-
Is there license and legal documentation included on each and every component in the BB3 archive? If not, there should be, I think.
Distributing 3rd party files (even if freeware) can be a tricky business. For example: What if some distributor suddenly would start to sell BB3 on a CD? Would all (possibly unwilling) contributors be happy with that?
For example aminet files have "Distribution (http://wiki.aminet.net/The_Readme_file#Distribution:)" field in their readme, with possibility to specify NoCD if you didn't like aminet guys selling your stuff.
-
Is there license and legal documentation included on each and every component in the BB3 archive?
- Yes, I think that's essential.
- Second: Someone shouldn't put original, copyrighted files in whatever "Community-BoingBag" - even a "patched" version still has the copyright (someone mentioned this before AFAIRC...).
- It must have been a huge and btw very welcome work to search all these files and make a package - so spending some more time to make it "perfect" (i.e. using original distributions, like CD-ROMS, as a patch base) should be possible.
-
I agree on what Piru said! I am going to try to take care of that.
Most likely it will say something like that you are entitled to use it, if only you got the legitimate AmigaOS 3.9 cdrom. 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 software 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 and shipping charges are allowed for distribution.
And will add the usual disclaimer that we are not liable for damages of the use or missuse of the product.
All trademarks and software products are copyrights of their respective owners.
Plus a list of credits & contributors & acknowledgements
PS: I know it is not well written, but then that is the concept. If someone wants to help, you are welcome!
PS 2: So yes NOCD, so that they dont add it to an Aminet CD and sell it!
-
@Gulliver
I really appreciate your efforts with this project.. Cheers
-
@Gulliver
I really appreciate your efforts with this project.. Cheers
I have to second and third this, as well. And the comments by Piru.
Full steam ahead, fellas. Your efforts are certainly appreciated.
-
No, I have just asked for and received confirmation that the MooVid version in question has been released to the community by the developer Lazlo Torok.
Interesting that it is still available here: http://www.reg.net/authors.asp?AuthorID=3759
So? Free or not free?
-
Did you read the post that you quoted? That answers your question. ;)
-
@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.
-
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!
-
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.
-
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.
-
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.
-
>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.
-
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.
-
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.
-
I think I got it to go away by saving the fonts in prefs.
-
@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.
-
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?
-
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...)
-
@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!
-
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.
-
Give me 10 minutes and consider it done!
-
@Gulliver
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. 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.)
Well, they did the impossible then ;). Oh, Did you mean legally? Yea, It would probably be better to use the .pch method for OS modules. An early disassembled exec is on Aminet and Piru's exec.library contains the actual exec.librarys but that's all grey area. There is actually little chance of pirating here as the updates in BB3 are not very useful without AmigaOS 3.9. I would think that would be good enough but it would be better to get permission from Hyperion or Amiga Inc to distribute this way. Maybe permission could be obtained to release other semi-official updates as well. Thomas Richter has some updates ready to go if he had permission...
http://www.natami.net/knowledge.php?b=6¬e=13805&x=1
Maybe we could start an e-mail petition. People who want to see an update would send Gulliver an e-mail with their name and e-mail address and those would be collected and sent to Hyperion and Amiga Inc. with a request.
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.
One advantage to the .pch method is a much smaller BB3. The installation would become slower with more problems though.
-
OK, I have released a 2nd beta, which fixes some bugs that have been reported here and at EAB. Now in expert mode it also gives you more control over which keymaps, etc. to update.
-
Would WBCtrl (http://stephan-rupprecht.de/downloads/WBCtrl.lha) be a nice addition? Though it says "controls undocumentated wb3.5 features" but does wb3.9 cover these undocumented features already?
-
@Gulliver
First of all, many thanks for your effort!
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. 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.
@AmiKit, You know how much I appreciate your work, have supported it in the past and idolize what you have been able to create and the fact that you still give it away free, but I would have to disagree with you on the use of the words "Boing Bag", unless the previous or current Amiga IP owners have also copyrighted those words (which maybe they did and I just was too lazy to go look before writing this message). The other parts of your message must be considered by everyone working on the project.
It really would be a shame if ANYONE were to object to this effort and try to stop it. If Hyperion has the rights to AmigaOS, all versions of it, then I think it would be terribly wrong and stupid of them to try to stop the community from putting together an effort like this one as it really does not hurt anyone. To my knowledge, the authors of this effort are not promoting any kind of piracy, they have put checks in place so it cannot be installed without BoingBag2 being installed first, which requires the installer to have a (hopefully legal) copy of the OS3.9 CD.
I think every effort to keep this work on the "Unofficial Boing Bag 3" legal and out of trouble with any of the authors of the separate files needed is being made.
My question is why has something like this not been done before now? It was greatly needed and certainly very appreciated. There are far too many returning Amiga users that do not know this information, and some Amiga users that never left, but did not keep up with updating their Amigas for one reason or another that can now update them to a more modern state with the help of this initiative. I hope this work expands even further with many people helping their fellow Amiga users to fine tune their Amigas to their fullest potential. This has always been one of the strengths of the Amiga community.
Edit: My problem with the RAM-Handler error did disappear after a cold boot, so if you haven't already added a note to include a cold boot after using the Unofficial Boing Bag 3 install script, you might want to add such a note. Now I am off to the other thread that describes which files to add/alter/or patch to create the fastest and most stable of AGA OS3.9 Amigas. Thanks again for this thread and all the work done to create the "Unofficial Boing Bag 3" project.
-
Indeed we must keep this effort going. The 68k Amiga stuff isn't worth a damn to anyone anymore but the few that have the Amiga hobby. If there is anyone that is so petty that he or she has to try to stop this effort I would like them to go away from the Amiga scene and never come back( softly put because what I actually want to say is much much harsher).
I really can't help but feel that our small user base is still overrun with absolute morrons when it comes to the worth of the 68k stuff. There isn't any. From the ROM's to the OS to the software. There is nothing of value in it anymore.
If we can have a third Boing Bag that gathers all the patches and updates and can roll them out in one go then that is good news for everyone that installs Amiga OS 3.9.
-
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
It's matter of few more lines in installer that would do all the patching on user's computer. Like I said, it's easy and worth to write such an installer and make the package 100% legal and bulletproof (providing all the software in the package is included properly - according to each program's readme and license OR with specific permission for this purpose).
This way the Unofficial Boing Bag can be promoted everywhere, on OSNews and other servers, distributed on Amiga Future CD, etc. Wouldn't it be great?
-
I really can't help but feel that our small user base is still overrun with absolute morrons when it comes to the worth of the 68k stuff. There isn't any. From the ROM's to the OS to the software. There is nothing of value in it anymore.
Nobody wants to stop the really appreciated effort to build a nice installing "BoingBag3", BUT - to use your own words - the community is still overrun by morons who consider everything 68k related is worthless which leads to their conclusion that everything should be for free and copyright is only a word. It is still possible to make a "bulletproof" update of OS3.9 - see AmiKit's post #111.
-
It's matter of few more lines in installer that would do all the patching on user's computer. Like I said, it's easy and worth to write such an installer and make the package 100% legal and bulletproof (providing all the software in the package is included properly - according to each program's readme and license OR with specific permission for this purpose).
This way the Unofficial Boing Bag can be promoted everywhere, on OSNews and other servers, distributed on Amiga Future CD, etc. Wouldn't it be great?
One vote for this - hopefully Thomas Richter can publish his patches & updates this way too, instead of waiting.. ;-)
Of course full files would be nice, but I don't think that is absolutely necessary. Infact I don't want to see possible negative attitude from copyright owners to let down those creating this excellent package. This has happened way too often. So if there is already legal way, and all it takes is somewhat more complex installer-script, I'd say it's easy choice.
-
With the entire legal status of OS 3.9 up in the blue, releasing this BoingBag 3 with full binaries and all is a nice experiment. Who, if any, will have legal grounds to complain? :-)
-
I keep hearing how easy it is to do this installer. If this is so easy why hasn't it already been done? Amikit has been saying on here for years that he would do it and never has. Now that someone else is trying he's back with how easy it is. If this is so easy, go make a "bullet proof" BB3 yourself and I'm sure Gulliver will gladly make this one dissapear. Gulliver isn't doing this for glory or fame. He's doing it because of his love of the Amiga. Which brings up one of the biggest problems with the Amiga scene these days. There are too many people calling the shots who haven't even turned on an Amiga in years.
-
One vote for this - hopefully Thomas Richter can publish his patches & updates this way too, instead of waiting.. ;-)
Of course full files would be nice, but I don't think that is absolutely necessary. Infact I don't want to see possible negative attitude from copyright owners to let down those creating this excellent package. This has happened way too often. So if there is already legal way, and all it takes is somewhat more complex installer-script, I'd say it's easy choice.
+1
-
Okay add my vote too - hopefully Thomas Richter can publish his patches & updates this way too, instead of waiting.. ;-)
@kolla
I agree with you. As said before there is a user trying to contact Amiga Inc. regarding OS 3.9, but should he try to contact Hyperion too? And what about Haage & Partner?
By the way Amiga Inc. is still unreachable by email. Can anyone help?
Has anyone got Thomas Richter email?
-
I keep hearing how easy it is to do this installer. If this is so easy why hasn't it already been done? Amikit has been saying on here for years that he would do it and never has. Now that someone else is trying he's back with how easy it is. If this is so easy, go make a "bullet proof" BB3 yourself and I'm sure Gulliver will gladly make this one dissapear. Gulliver isn't doing this for glory or fame. He's doing it because of his love of the Amiga. Which brings up one of the biggest problems with the Amiga scene these days. There are too many people calling the shots who haven't even turned on an Amiga in years.
dannyp, please, I've done it already. Look at the "Install Patches" inside AmiKit package (also attached here). If you want it for real Amiga too, you can modify it yourself as well, the working example is there (just ignore the "second run", "third run" etc. parts. They are there to install new patches if the script was already used before).
With regards to BB3 legal status, I am just pointing out the objective facts. If you have problem with that, don't blame me. In addition I am showing a real solution how to make the package legal and thus worldwide available. What more do you want me to do and why?
As said before there is a user trying to contact Amiga Inc. regarding OS 3.9, but should he try to contact Hyperion too? And what about Haage & Partner?
By the way Amiga Inc. is still unreachable by email. Can anyone help?
Don't waste your time contacting AInc or Haage.. I know what I am talking about. Anyway, if .pch solution is used, contacting them is not necessary at all.
-
Don't waste your time contacting AInc or Haage.. I know what I am talking about. Anyway, if .pch solution is used, contacting them is not necessary at all.
I think that is *exactly* why one should do it the "illegal" way, in an attempt to provoke a reaction. And if there is no reaction, that's good too :)
If the copyright holders dont care, there's really no reason others must care either.
-
I will just repeat what I already said. If making a BB3 is so easy, why is this the first real effort that has been made to do it. People have been pleading for years to get this done and now that someone is actually making it happen, all the naysayers are coming out of the woodwork. This doesn't need to be "bullet proof". It Needs to get into the hands of Amiga users who actually still use their Amiga's. Please don't tell me how easy this is to do, show me.
-
I will just repeat what I already said. If making a BB3 is so easy, why is this the first real effort that has been made to do it. People have been pleading for years to get this done and now that someone is actually making it happen, all the naysayers are coming out of the woodwork. This doesn't need to be "bullet proof". It Needs to get into the hands of Amiga users who actually still use their Amiga's. Please don't tell me how easy this is to do, show me.
At first you were talking about installer, now you are talking about easyness of creating the whole package. Make up your mind. Btw. I've already created both so I see no reason why should I show anything more to you. I will just repeat what I already said. Feel free to modify the already existing script. Merry Christmas.
-
Has anyone got Thomas Richter email?
Thomas Righter's e-mail is the same as it's always been. Look in the Mu/mmu.library package on Aminet. The problem is that he has seen the source code and would not be able to release his updates without "official" permission. It's a little different when someone signs a NDA. Getting official permission would open doors.
Another product I would like to see included to complement MooVid is Riva. It's a MPEG player written entirely in assembler so it's very fast. Stephen (Cobra on AmigaWorld.net) went on to write DvPlayer for AmigaOS 4. Maybe you could get him to release the full version of Riva on Aminet with source code too, preferably?
-
Amikit said: "At first you were talking about installer, now you are talking about easyness of creating the whole package. Make up your mind. Btw. I've already created both so I see no reason why should I show anything more to you."
We must be missing something in the translation between native languages here. If you have allready done all of this why are Gulliver and his crew wasting their time doing what you have already done?
I know you have an installer for installing patches on your emulation. This is for real Amiga's.
You are taking what I am saying personally and it is not meant to be that way. You have a wonderful web site that I have visited many times and donated money to more than once. It is a great resource for the community. I just don't consider the BB3 project to be easy or it would have been done long before now. I know that I couldn't do what they are doing or I would have already done it myself.
-
@matthey
I was thinking the exact same things! i am going to try to contact Stephen Fellner first!
-
Amikit said: "At first you were talking about installer, now you are talking about easyness of creating the whole package. Make up your mind. Btw. I've already created both so I see no reason why should I show anything more to you."
We must be missing something in the translation between native languages here. If you have allready done all of this why are Gulliver and his crew wasting their time doing what you have already done?
I know you have an installer for installing patches on your emulation. This is for real Amiga's.
You are taking what I am saying personally and it is not meant to be that way. You have a wonderful web site that I have visited many times and donated money to more than once. It is a great resource for the community. I just don't consider the BB3 project to be easy or it would have been done long before now. I know that I couldn't do what they are doing or I would have already done it myself.
dannyp1, all what I am saying is that I've done SIMILAR package+installer for AmiKit.
Now when BB3 package is ready for real Amiga (thanks to Gulliver and others), there's only one more step to make it legal and thus promotable worldwide: the proper .pch installer. And that's easy according to my experience. I've also published my installer script as an example for anyone who wants to try it. That's all.
-
>This way the Unofficial Boing Bag can be promoted everywhere, on OSNews and other servers
There is nothing stopping it being promoted as is.
>distributed on Amiga Future CD, etc.
This would not meet condition #2 of the licence. Maybe we should have an exemption for magazine coverdisks.
-
>This way the Unofficial Boing Bag can be promoted everywhere, on OSNews and other servers
There is nothing stopping it being promoted as is.
Wrong. See SilvrDrgn's post #75 (http://www.amiga.org/forums/showpost.php?p=534475&postcount=75)
-
Wrong. See SilvrDrgn's post #75 (http://www.amiga.org/forums/showpost.php?p=534475&postcount=75)
That doesn't stop them from mentioning it. No one is proposing that OSNews should be distributing the package, they are a news site not a download site.
-
That doesn't stop them from mentioning it. No one is proposing that OSNews should be distributing the package, they are a news site not a download site.
Wrong. See Yo's post (http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=30280&forum=16#526318).
-
We're talking about OSNews not amigaworld. I don't see how amigaworld moderators can call the shots about what is covered at an unaffiliated site. If amigaworld - or amiga-news.com for that matter - want their users to be left in the dark about new Amiga releases, and using obsolete software with known bugs in it for which fixes are available, that's up to them I guess.
-
We're talking about OSNews not amigaworld.
And what is the difference?? :) Btw. I haven't noticed any real arguments against SilvrDrgn's and Yo's claims. I won't participate in this discussion with you until I see some. Sorry.
-
I think the point has been made about the legality. again and again. I suggest ignoring the community police and carry on. good job :-)
-
Well, I don't know how many other users/members here are trying to use this "Unofficial Boing Bag 3" lha file/installer script and if they are having no problems getting it to work, but I am about to start my 4th attempt from a clean OS3.9 plus BoingBag1 & 2 on an empty partition as the first three attempts have failed.
I am back to having an error message which prevents Workbench from loading that states that RAM-Handler version 44 is already loaded and gives a LoadModule error.
On this last attempt, I also got the error that Devs/scsi.device could not be found, or did not exist, which when I booted from another partition, or my backup ZIP100: drive and checked, I confirmed that there is no scsi.device to be found in the Devs directory, or anywhere else on my CF card (which is attached to the internal IDE controller via a IDE to CF card adapter.
I am getting lost now, as I don't fully understand how the internal controller is working with the OS3.9 install process without any scsi.device present for the internal IDE controller on the A1200.
Also, my monitor appears to become more and more unstable after I install the Unofficial BoingBag3 script. It might be the age of the CRT, or a less than perfect connection of my IndivisionAGA to the Lisa chip, I cannot tell what is causing the tearing and artifacts on my 19" monitor, but I was using a 16" CRT earlier in this process and it exhibited the same tearing and artifacts, so I am not too fast to blame the monitors. I guess it could be a faulty IndivisionAGA, but until I get a stable OS running on it again, I can't say for sure what the problem is, as the display was not 100% prior to my attempts to install BoingBag3, but I thought that I might have had a loose connection to the Lisa chip then, and/or heat problem from the hard drive sitting on top of the IndivisionAGA. Now with the CF card adapter, heat above the IndivisionAGA should not be an issue.
I am going to download the latest version of the Unofficial BoingBag3 file again, as I think one or two adjustments have been made since the version I have been trying.
I am not sure what else to try differently, except to not use the installer script at all and do all of the file installations and patches manually myself.
Any ideas for me? I would also like to hear from others that have used the installer script successfully to know if there was anything they had to do to get it to work properly.
-
Good job :-)
Thanks :-)
I've done SIMILAR package+installer for AmiKit.
BB3 is a superset of this, ie. it contains all those upgraded components plus many more.
-
>Devs/scsi.device could not be found
That's strange, could you please send me your install_log_file?
>Also, my monitor appears to become more and more unstable after I install the Unofficial BoingBag3 script. It might be the age of the CRT, or a less than perfect connection of my IndivisionAGA to the Lisa
It doesn't upgrade any monitor drivers (although it does add some new ones).
-
>Devs/scsi.device could not be found
That's strange, could you please send me your install_log_file?
>Also, my monitor appears to become more and more unstable after I install the Unofficial BoingBag3 script. It might be the age of the CRT, or a less than perfect connection of my IndivisionAGA to the Lisa
It doesn't upgrade any monitor drivers (although it does add some new ones).
Still working on it, but I am saving logfiles this time. I think the scsi.device is in the A1200 KickstartROM, that is why it does not show up in Devs:
-
RiVA author was contacted, what follows is the email exchange:
Hello!
I have planned on releasing RiVA as freeware at some stage, but have
not done so due to lack of interest at the time. I suppose it wouldn't
hurt to get it released as freeware even though I don't think many
people are serious about playing videos on classic Amigas these days,
some people may find it useful. However give me some time to get it
sorted out as I don't get as much time for Amiga things lately as I
would like to.
Best Regards and a Happy Holiday Season,
Stephen Fellner
On Wed, Dec 23, 2009 at 10:08 PM wrote:
> Dear Stephen Fellner,
> I am writting to ask if you could release as
> freeware your copyrighted files corresponding to your RiVA mpeg
> player software product free for non commercial purposes. I hope you can see
> this as a good endeavour and support us with your fully working program as a
> contribution to our small Amiga comunity.
>
> I hope we can count with your blessing, looking forward for an answer,
>
> Thank you for your time,
> Regards,
-
@Gulliver
Great news! Why didn't you do all this a long time ago :).
-
I think the scsi.device is in the A1200 KickstartROM, that is why it does not show up in Devs:
Confirmed!
-
After installation there should be a requester telling user to do a power off to get rid off old loaded modules, that would avoid many scsi.device problems and whatnot.
Btw. there's a KingCon 1.8 on AmiKit, among various fixes it also allows KingCon to be loaded as a kickstart module so CON: is replaced with kingcon even when booting without startup-sequence. I really wish we had the sources for it, I'd love to see 1.8 for 68000 as well, and not just 020+ (that goes for alot of stuff btw).
-
Is the installer the latest version? Are you doing updates for the installer?
-
Is this link the latest version? If AmiKit would hurry up and finally finish delivering my Lyra I can test this out. It's been weeks now so it *should* be here soon and I am dying to be able to use my keyboard to give this a go. Let me know
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!
-
We're talking about OSNews not amigaworld. I don't see how amigaworld moderators can call the shots about what is covered at an unaffiliated site. If amigaworld - or amiga-news.com for that matter - want their users to be left in the dark about new Amiga releases, and using obsolete software with known bugs in it for which fixes are available, that's up to them I guess.
Imho every site decides for themselves.
Regarding aw.net not publishing the news item, it is due to doubts of the legality, I did email around, and got some clear answers from one of the license/copyright/owners saying BB3 is not legal, you can PM me on aw.net, and I can give a bit more details.
-
And I mailed Jesus and he said it was all right.
Really - if they have complaints, then they should speak up loud and clear and state the legal status of the code in question - right now, anything that is copyrighted "Amiga Inc" is up in the blue legally.
-
What's the big secret? If you know of somebody who feels they are being hurt by the BB3 project, you or the person with the "clear answers" should speak up and not play games. For it to be illegal somebody would have to care that their code that was written for the Amiga was being used on Amiga's. There is nobody connected with this project who is making a single penny from somebody elses work. There is nobody on the project who is trying to take credit for somebody elses work.
-
@ kolla & dannyp1
Well IMHO the situation is clear: The BB3 compilers didn't clear the copyright issues. The BB3 limbo is direct result from this.
This is exactly the reason why you should always clear these issues beforehand.
The current situation might seem unfair, considering no money making is involved. However, copyright is the "copy" "right", and it applies regardless of the payment (even if none).
-
If somebody is a copyright holder why don't they step forward and identify themselves and present the proof that they have a legal right to stop the BB3. There are being efforts made and emails sent daily trying to clear up any problems. (I might add that nobody who has been contacted and has replied has had a problem with the project yet). I find it strange that somebody on another board can send out a couple of emails and instantly get replys that contain "clear answers" but it is a big secret as to who the mystery copyright holder is and why he would give a hoot that somebody is trying to keep a dying platform alive with no hurt being done to him. Am I the only one who is curious who this "license/copyright/owner" is.
-
i didn't follow the thread carfully BUT i just downloaded the archive ... guys, you'r really looking for troubles here!
-
>After installation there should be a requester telling user to do a power off to get rid off old loaded modules, that would avoid many scsi.device problems and whatnot.
Already implemented in beta 2.
>Btw. there's a KingCon 1.8 on AmiKit, among various fixes it also allows KingCon to be loaded as a kickstart module so CON: is replaced with kingcon even when booting without startup-sequence. I really wish we had the sources for it, I'd love to see 1.8 for 68000 as well, and not just 020+ (that goes for alot of stuff btw).
BB3 is primarily upgrades of existing apps, whereas KingCon and AnimIcon are complete replacements for existing apps, which explains their omission from the core BB3 package. (Although they may be suitable candidates for a BB3 Contributions package.)
-
The onus is not upon the copyright holder to monitor every project out there, but on the project producers to ensure they are not violating copyright.
None the less, I would suggest keeping a running score board of products for which you have received the okay to proceed with BB3, along with the official notice from the original author. Then only include those in the archive as testing progresses.
If no one has objected so far when contacted, then kudos to you and keep moving forward with attempts at contact, but certainly do not assume cooperation. Bear in mind that some people may be a little miffed or offended by inclusion of their work in a project, even if not-for-profit, without having been contacted first; they might not even make first contact with you.
I think the BB3 project is a great idea and would be a benefit to us all, but only if done correctly.
-
sometimes rules must be bended. It's the one way to move on and the only "human" way.
-
@ kolla & dannyp1
Well IMHO the situation is clear: The BB3 compilers didn't clear the copyright issues. The BB3 limbo is direct result from this.
It would be no matter how much work you'd put in it.
This is exactly the reason why you should always clear these issues beforehand.
This is exactly why on should avoid closed source proprietary systems at all, amigaos (and morphos for that matter) is a relic of the past in this regard. That the ...ahm.. "owners" havent bothered to go for a more open development path after fall of CBM has been a real PITA.
The current situation might seem unfair, considering no money making is involved. However, copyright is the "copy" "right", and it applies regardless of the payment (even if none).
How do one know who has the copyright of a given component of AmigaOS3.9? There are copyright stamps east and west there, and as you have pointed out earlier, also stolen components etc - to breach some more copyrights owned by ignorant copyright holder is just keeping up a long and strong tradition of 3.5+, nothing new, same old, same old.
If tomazkid and amigaworld.net have any balls (heh) they should also ban any discussion of OS3.9, or linking to Amiga dealers who still sell OS3.9 - this a much much worse breach of copyrights than this BB3 will ever be. I'm quite sure you agree.
-
comparing the Moana files with BB3, is unfair.
I didn't have the time to reply to tomazkid at aw.net but once for all ... the Moana files were STOLEN along the laptop that stored them. This is ALL another matter.
-
This is exactly why on should avoid closed source proprietary systems at all, amigaos (and morphos for that matter) is a relic of the past in this regard.
This cannot be a serious interpretation. Open source non-proprietary systems have licensing problems as well. In short, this is absolutely NOT a closed-source issue.
-
This cannot be a serious interpretation. Open source non-proprietary systems have licensing problems as well. In short, this is absolutely NOT a closed-source issue.
Copyright is there also without a license, it is not the same.
Opensource licenses ensures that you as a user is free to fiddle with the sources and compile as much as you like. The license might prohibit you from distributing binaries, but that is not much of an issue when there are sources that can be distributed.
-
Copyright is there also without a license, it is not the same.
Opensource licenses ensures that you as a user is free to fiddle with the sources and compile as much as you like. The license might prohibit you from distributing binaries, but that is not much of an issue when there are sources that can be distributed.
But is that not ultimately the problem here? The distribution of someone else's work without permission, whether modified or not? Technically, the inclusion in a package modifies the program, its distribution package, and/or its intended method of installation.
Irrespective of the nit-picking, I still stand on my previous statements. I am all for the BB3 project, provided everyone who has "contributed" gets their proper due.
-
But is that not ultimately the problem here? The distribution of someone else's work without permission, whether modified or not? Technically, the inclusion in a package modifies the program, its distribution package, and/or its intended method of installation.
Irrespective of the nit-picking, I still stand on my previous statements. I am all for the BB3 project, provided everyone who has "contributed" gets their proper due.
Omg, if people are going to keep bickering about the copyright issues let's just do the following:
a) For any files that exist on AmigaOS disks (or compact discs) simply create patch files for them from the original to the final state. Determine which OS the user is providing and apply the appropriate patch. This appears to be OS3.9 for the most part.
b) For any files that cannot be included in another package but that are free for download from a site such as Aminet, write a simple downloader with a modifiable file/url list that connects to the net OR uses previously downloaded files of the same name and/or version in a locally cached directory. It would be nice if each file had a handler script so that only that script could be updated when software was updated elsewhere, but this is not necessary.
c) For the rest of the files that are free to distribute put them all with the final installer alongside any patches made in step a. Do this as much as possible because having to download files from mirrors that seem to constantly break for Amiga software is a big pita.
Finally no matter how it is finally distributed, somebody (preferably several somebodies) should keep a copy of each file needed to make this Boing Bag complete. And for those people who are complaining about the name, just call it the Unofficial Boing Bag #3. That way the title is different and other people can't complain about it any more. For Christ's sake there are tons of businesses across the world that have the same name as well other products that have the same name. This is a non-issue.
I don't have a lot of Amiga specific C programming but I can write something in Python for the Amiga (I noticed there is a 68k distribution albeit older) if it would help.
-
"a) For any files that exist on AmigaOS disks (or compact discs) simply create patch files for them from the original to the final state. Determine which OS the user is providing and apply the appropriate patch. This appears to be OS3.9 for the most part."
this solution would be perfect and legal IMHO
-
a) For any files that exist on AmigaOS disks (or compact discs) simply create patch files for them from the original to the final state. Determine which OS the user is providing and apply the appropriate patch. This appears to be OS3.9 for the most part.
That only solves the issue if the patches themselves don't contain any 3rd party copyrighted material.
If they do, then this method solves nothing.
-
Seems only pedants stuck with an Amiga whilst everyone else got a PC ! :)
-
Seems only pedants stuck with an Amiga whilst everyone else got a PC ! :)
Wat?
-
I think the meaning of my message was quite clear! :)
-
Huh?
-
OK, V1.0 is released.
-
OK, V1.0 is released.
Is this the installer? Where is the link?
-
Yes.
-
..
-
comparing the Moana files with BB3, is unfair.
I didn't have the time to reply to tomazkid at aw.net but once for all ... the Moana files were STOLEN along the laptop that stored them. This is ALL another matter.
well, ianal but this is how the EU laws look at this.
You have the right to modify files and programs for your own use, but you don't have the right to distribute the modified files. (unless the license says otherwise.)
So let's say I modify my own OS4 cd to run on a Macmini, legal as long as I don't distribute it.
That was where the Moana comparison comes in.
What Piru has written in this thread is worth a reading as well.
No fun to read, but that is how the laws look like at the moment, laws written for analog technology does not work too well with the digital world, but as long the laws are not changed, this is what the situation looks like.
-
So will amigaworld.net also block any discussion on OS3.9 and remove links to anyone selling OS3.9 that comes with pirated AmiTCP (aka Genesis)?
Btw... would it make sense to have some sort of bugtracker/improvement wishes for Classic 68k AmigaOS? I have a few wishes myself, but no idea where to address them.
One quite recent example is ForceNewLook that I had to dig out from some old MagicMenu-1.x archive, it enforces newlook menus (black on white) in for example console.device. First of all it would be nice if console.device could finally at last switch to newlook menus as default itself, and secondly it would be nice with romable ForceNewLook.
-
So will amigaworld.net also block any discussion on OS3.9 and remove links to anyone selling OS3.9 that comes with pirated AmiTCP (aka Genesis)?
Btw... would it make sense to have some sort of bugtracker/improvement wishes for Classic 68k AmigaOS? I have a few wishes myself, but no idea where to address them.
One quite recent example is ForceNewLook that I had to dig out from some old MagicMenu-1.x archive, it enforces newlook menus (black on white) in for example console.device. First of all it would be nice if console.device could finally at last switch to newlook menus as default itself, and secondly it would be nice with romable ForceNewLook.
No, general discussion of BB3 is still allowed, direct links are not.
Regarding OS 3.9 cd, well, we deal with that if necessary, until then it will pass.
Is the Genesis that comes with OS 3.9 really pirated btw?
links please, I am not too familiar with that myself.
You need to bear in mind that aw.net server is located in France, and we need to respect the French laws in particular, and EU laws in general, not an easy task always, but we need to do it.
-
No, general discussion of BB3 is still allowed, direct links are not.
Regarding OS 3.9 cd, well, we deal with that if necessary, until then it will pass.
Is the Genesis that comes with OS 3.9 really pirated btw?
links please, I am not too familiar with that myself.
Sure, http://www.amigau.com/aig/amigaos39.html under "critisism".
You need to bear in mind that aw.net server is located in France, and we need to respect the French laws in particular, and EU laws in general, not an easy task always, but we need to do it.
From my understanding and experience, the French has a very pragmatic attitude towards laws, also historically, so this statement is sort of funny. No offence :)
-
Sure, http://www.amigau.com/aig/amigaos39.html under "critisism".
From my understanding and experience, the French has a very pragmatic attitude towards laws, also historically, so this statement is sort of funny. No offence :)
Thanks for the link. :-)
No offence taken, this might illustrate our view perhaps :-D
http://i.imgur.com/XJthe.jpg (http://i.imgur.com/XJthe.jpg)
We just don't want any Hadopi effect on our server. ;-)
-
Well, as you all probably know by now that BoingBag 3 project has been finalized. As someone suggested, it could not transform itself into a moving target any longer, and thus a never ending project goal. So we had put some sense on it and declare it finished.
But this doesnt mean that the idea of enhancing, updating and bugfixing AmigaOS 3.9 has ended. In fact it means we have to start again, with a new BoingBag, now named unofficial BoingBag 4. I believe there is still many things to improve on AmigaOS 3.9, and by the way we already have the first entry, a bugfix for icon.library.
Of course, as usual, you can get the latest updates and information on BoingBag 4
Happy New Year!
-
Here we go again. And Argo, just where was it you got your law degree to be such an expert on what is legal. You had better also ban everyone from going on EBay because I see illegal roms for sale on there every day (but gee, they never seem to get shut down. What do they know that you don't). And there's that Amiga hardware site with all the installation disks. They are all legal? They also never get shut down. Why is it that Amiga.org is the only place the web police are lying in wait to do away with?
-
Okay, the Unofficial Boing Bag 4 got an update:
MooVid 1.7 beta
This is the last version of the popular 68k video player available. It contains, even more bugfixes and supported codecs.
For this and BoingBag 3 information and downloads go to:
http://lilliput.host-cafe.com
-
BoingBag 4 got new updates:
Canon BJC6000 (and possibly other Canon 720x720) printer drivers. Written for OS3.5/3.9
Includes limited support for photo printhead, and text mode printing.
Epson_Colour_45.lha is a colour printer driver for the Epson Stylus Colour printers.
It should work with the Stylus S20, D120 or Cx0 series which also supports 1440 dpi.
For more information, patches and updates, visit http://lilliput.host-cafe.com
-
Right, i set out to install this thing. I found that using InstallerNG was the only working installer , the original wouldnt have it, InstallerNG gave a few errors, then stalled completely at 96%?
-
How odd! I have just installed it withouth any problems at all.
I am using the 3.9 installer.
Maybe you have an older version. type on a cli window "version sys:utilities/installer", it should be version 44.10
Hope it helps
-
Indeed the installer in sys:utilities is 44.10 , however the one i have marked as original in sys:c is 39.something. No complaints using 44.10, but is choosing "other" correct when running on an 060?
-
Make sure you are using 44.10, as it will be more compatible. It should work without issues on a 060. So delete the old one you have in C:
-
Make sure you are using 44.10, as it will be more compatible. It should work without issues on a 060. So delete the old one you have in C:
Dont worry about it. But how about adding
http://aminet.net/package/util/boot/CopyMem , http://aminet.net/package/util/boot/UtilPatch and http://aminet.net/package/util/misc/gfxroute?
-
Make sure you are using 44.10, as it will be more compatible. It should work without issues on a 060. So delete the old one you have in C:
Boing Bag #3 was great, but hozed my AFA_OS install...can it be fixed for BoingBag #3? Eg. can you make a new archive,
OR, make it so boing bag #3 can be avoided. So you go 1,2, then 4. ?
The other thing is that boing bag #3 installs many AHI sound drivers, many of which (or most of which) users will NOT have that hardware, and some programs complain about opening those drivers (or trying to open) if the actual hardware does not exist on your system.
-
I use AFA_OS with no problem together with BB3. You need to use the last version of its components which are not yet on the AFA_OS website. They are over here:
http://eab.abime.net/showpost.php?p=643280&postcount=227
The AHI trouble you encounter is made to ensure every soundcard gets supported by default. Just use the AHI preferences editor, select YOUR driver exclusively for each AHI option and save your preferences. Then you can if you want to, erase all the drivers you are not going to use. You shouldnt have any more issues from now on.
Good luck!
-
Keeps nagging about me missing the openpci.library the maestix.library and the toccata.library by the way.
Also the http://aminet.net/package/util/boot/MuFastChip might be worth looking into adding. It detects if the patch is already applied and does nothing then naturally.
-
I use AFA_OS with no problem together with BB3. You need to use the last version of its components which are not yet on the AFA_OS website. They are over here:
http://eab.abime.net/showpost.php?p=643280&postcount=227
The AHI trouble you encounter is made to ensure every soundcard gets supported by default. Just use the AHI preferences editor, select YOUR driver exclusively for each AHI option and save your preferences. Then you can if you want to, erase all the drivers you are not going to use. You shouldnt have any more issues from now on.
Good luck!
Yes, I know you need the latest components. But its kind of a pain in the butt. Because out-of-the-box BB3 hozes AFA_OS. Maybe it's AFA_OS that needs to be updated to new archive, then.
-
From the forthcoming version of AFA_OS 4.7, BB3 will be totally supported.
The problem was that AFA_OS only wanted to work with icon.library 45.1.
Authors of both the updated icon.library and AFA_OS have agreed to work together to solve compatibilty issues. So they released that version that fixed incompatibilties, whilst AFA_OS 4.7 is being developed.
-
The missing libraries then, openpci is open source, that could be stuck in the bag.
Someone seems to have had and solved the problem on eab. http://eab.abime.net/showpost.php?p=637218&postcount=15 But i dont get why those are required on an a1200 without a mediator or anything.
from eab:
OpenPCI unified library and drivers for Amiga PCI/AGP Bus Project Page:
http://bvernoux.free.fr/DevPCI.php
OpenPCI library v2.1 (68k and PPC/MorphOS)
OpenPCI library v2.0 (68k and PPC/MorphOS)
MaestroPro driver V41.40 + AHI driver V2.2:
http://aminet.net/package/util/libs/Maestix
(includes maestix.library v41.40)
Toccata.library V12.0:
http://aminet.net/package/util/libs/toclib12
-
The problem is that openpci is not 100% compatible with Mediators. It is an open source replacement (and that is really good), but it may generate some conflicts.
But most importantly, let me tell you that BB3 is an Operating System update, not a driver update, that is why it requires from the user to ensure the installation of their particular hardware drivers, in a proper manner. Of course there are few concesions made, but they are allowed only in the case they dont generate any incompatibility with other systems (which is not the case of openpci).
Thank you for your ideas and support. Let me try to explain you that the idea behind BB3 is to follow the concepts drawn by AmigaOs 3.9 and attempt to remain as faithfull as possible to the original AmigaOS 3.9 design goal/concept. This means we are rather conservative when it comes to adding system patches, that may eventually create a conflict.
Of course, if you like certain particular set of apps and patches, you are welcomed to create your own AmigaOS distribution/enviroment much like Amikit, AmigaSYS, ClassicWB and AIAB do. But it is not our goal. The objective we target, as said before is to update, enhance and bugfix AmigaOS 3.9 as much as possible, but leaving the user the freedom to choose between any of these emulation/distribution enviroments. We are more focused on the core of the OS, not on the enviroment aspects of it.
I hope you find sense out of my poor and damaged brain ;)
Thanks again, and your suggestions are allways welcomed, as much as you are welcomed to disagree with me and find a safe way to create those patches as rom updates yourself and prove me that I am wrong. :)
After all I am just one of many involved in this project, and I am not allways right! :)
-
@Gulliver
Understood, but surely people with mmu´s could get some love from mmulib?
http://aminet.net/package/util/libs/MMULib
What about a patch selecting dialog? That way people can mess up their Amigas on their own.
Stuff like this is infinitely interesting. http://aminet.net/package/driver/video/gfxlib_4025b4
Patch controlling installing conflict detecting wonderbra might be the way to go then?
-
@mike-
I'm the author of CopyMem and UtilPatch. You no longer need to use UtilPatch if you are using Thomas Richter's 68060.library. It's now incorporated with small changes into the 68060.library as a patch for the utility.library. One less patch is needed :). I should update the aminet readme to reflect this though.
CopyMem is still quite useful. I plan on trying to make a new exec.library which incorporates this, TLSFmem and some optimizations. That would be a better BB inclusion than a patch I think.
-
@mike-
I plan on trying to make a new exec.library which incorporates this, TLSFmem and some optimizations. That would be a better BB inclusion than a patch I think.
Cool!!! Just let us know when you are done, so we give it a try, and of course, include it in BB4 :)
-
>From the forthcoming version of AFA_OS 4.7, BB3 will be totally supported.
Yes.
AFA 4.7 is near ready, only installer script change so it can install in amikit must done.
I think it can release in 1-2 weeks.
currently this is working
+when use 8 bit screen Icon display use now old Iconlib.AFA work also with PeterK iconlib and BB3.
+ wawa add code for Window gadgets in 8 bit screen look, and AFA look now nicer even on 640*256*4 AGA screens.
known Problem: On some Programs the size gadget placing is not correct center in 4-256 color screens.
+ All Programs (kingcon) that use builtin Icons can work now without extern Icon.(thanks PeterK for help at this)
+ with Lib Revision 88 the Frameiclass support with the zune Skin System the render of
FRAME_PROPBORDER (compatible with OS4 API)
FRAME_PROPKNOB (compatible with OS4 API)
FRAME_DISPLAYBOX (compatible with OS4 API)
FRAME_WINDOW
FRAME_PAGE
FRAME_GROUP
FRAME_REQUESTER
IA_Orientation (compatible with OS4 API) is used to rotate the slider shading horizontal/vertical
+ fix redraw Problem that happen with Final Data
-
After installing BB3 on AmiKit MagicMenu is no longer transparent.
How can I fix this?
-
Sorry, @bernd_afa just said what i wanted to explain. And he is the authority on the subject
-
>From the forthcoming version of AFA_OS 4.7, BB3 will be totally supported.
Yes.
AFA 4.7 is near ready, only installer script change so it can install in amikit must done.
I think it can release in 1-2 weeks.
currently this is working
+when use 8 bit screen Icon display use now old Iconlib.AFA work also with PeterK iconlib and BB3.
+ wawa add code for Window gadgets in 8 bit screen look, and AFA look now nicer even on 640*256*4 AGA screens.
known Problem: On some Programs the size gadget placing is not correct center in 4-256 color screens.
+ All Programs (kingcon) that use builtin Icons can work now without extern Icon.(thanks PeterK for help at this)
+ with Lib Revision 88 the Frameiclass support with the zune Skin System the render of
FRAME_PROPBORDER (compatible with OS4 API)
FRAME_PROPKNOB (compatible with OS4 API)
FRAME_DISPLAYBOX (compatible with OS4 API)
FRAME_WINDOW
FRAME_PAGE
FRAME_GROUP
FRAME_REQUESTER
IA_Orientation (compatible with OS4 API) is used to rotate the slider shading horizontal/vertical
+ fix redraw Problem that happen with Final Data
I am looking forward to the update. It seems a lot of work has been done. Thanks!
-
thanks for the hard work, it is appreciated.. it is great to know that the Amiga Continues to have dedicated users to advance the existing tech. dispite the pc trend.:laughing:
-
From the forthcoming version of AFA_OS 4.7, BB3 will be totally supported.
The problem was that AFA_OS only wanted to work with icon.library 45.1.
Authors of both the updated icon.library and AFA_OS have agreed to work together to solve compatibilty issues. So they released that version that fixed incompatibilties, whilst AFA_OS 4.7 is being developed.
Excellent, thanks :)
-
Anyway, I recomend you get the latest BB4, which is a work in progress, and install those updates yourself so that you get a system much more updated and bugfixed.