Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Gulliver on May 13, 2010, 12:16:55 AM
-
AmigaOS 3.9 BoingBag #4 version 0.2b
=======================
NO WARRANTIES: USE AT YOUR OWN RISK!
The unofficial BoingBag 4 project is a community effort that is pursuing the considerable
task of upgrading, enhancing and bugfixing AmigaOS 3.9.
This is a preliminary release. It is anticipated that further updates
will be developed and incorporated before the final release. Please
report any bugs immediately.
To get the latest updates and information, visit http://lilliput.amiga-projects.net/bbag4.htm
You will need to install Boing Bags #1, #2 and #3 before installing BoingBag 4.
BoingBag 1 and 2 are available from http://os.amigaworld.de/index.php?lang=en&page=12
BoingBag 3 is available from http://lilliput.amiga-projects.net/bbag3isdone.htm
BoingBag 4 is available from http://lilliput.amiga-projects.net/bbag4.htm
__________________________________________________________________________________________
These components are updated:
BB3 BB4
graphics.library 40.24 -> 40.25b8
icon.ibrary 46.4.129 -> 46.4.159
SetPatch 44.38 -> 44.39
version.library 45.4 -> 45.5
wizard.library 42.100 -> 45.1
These components are new:
Canon BJC6000 printer driver 44.7
Epson Stylus Colour printer driver 45.0
SuperPlus monitor driver 40.2
Also, various components are replaced with their 68020-optimized
equivalents (generated with the PatchFor020 utility).
Thanks to all the developers who made this upgrade possible by their
continued support for OS3.9, and to all the beta testers of this package.
Changelog
---------
Canon BJC6000
Includes limited support for photo printhead, and text mode printing.
Epson Stylus Colour
It should work with the Stylus S20, D120 or Cx0 series which also
support 1440 dpi.
icon.library 46.4.154
The ProcessIcon bug and an enforcer zeropage read hit are fixed now.
The following functions in the icon.library were broken:
OptimizeImageSpace(), DropChunkyIconImage(), DropNewIconToolTypes(),
OnlyUpdatePosition(), PreserveOldIconImages(). In some cases the
planar images of non-V44 icons couldn't be displayed. This version
works without conflicts under AfA_OS if the version of the
AFA_OS_LIBS:Icon_Lib.exe is from 2010 or newer. More fixes and tweaks.
graphics.library 40.25b8
Lots of fixes, optimizations and enhancements. You are now able to
remove forever these patches:
* AmyWarp
* BlazeWCP
* CPUBlit
* FBlit
* FText
* IconBeFast
* SetPatch 44.38 (R_WriteChunkyPixel and R_WritePixelLine8
patches).
They are now built in.
SetPatch 44.39
Disabled R_WriteChunkyPixel and R_WritePixelLine8.
SuperPlus monitor driver 40.2
An ECS/AGA driver with 800x600 70ns mode, about 70% faster than
Super72 in 256 colours. It can provide support for ECS at 800x600 in
16 colors out of 4096, and is also interesting for the AGA chipset,
because it uses the "HiRes" mode with 70ns instead "SuperHiRes" with
35ns pixel clock. The display DMA is not as heavily loaded as it is
with Super72 and display operations are faster.
wizard.library 45.1
Provides a nicer MUI/Zune look and is optimized for 68020 and up.
-
I like the new graphics.library, good work.
-
Hiya,
Is all of these updates considered stable 'enough' for a release?
Good work BTW :)
-
Oh great thanks!!!
-
Hats off to Cosmos especially for his work on graphics.library (since its importance).
Of course many thanks even to all the others who contribute! :)
-
ohhh...nice! and with install script
*thumbs up!*
-
Downloaded,thanks for your work.
-
Under winuae, loadmodule11 doesn't load the graphics.library if the 'fast' option is set. Without this (and check) option, graphics.library is loaded.
:afro:
-
Also, various components are replaced with their 68020-optimized
equivalents (generated with the PatchFor020 utility).
Really? I mean, all I see are files that are exactly as they were before, now only with filenames in uppercase. Seems quite pointless.
-
Another thing... even with the new graphics.library I save ~160k of chipram by using fblit on my A1200.
-
Another thing... even with the new graphics.library I save ~160k of chipram by using fblit on my A1200.
The goal for graphics.library 40.25 was to be better than 40.24. If you find room for further improvements, why dont you drop your comments on the corresponding thread, so that the guy which is actually enhancing this library, Cosmos, improves it further? He is still looking for suggestions. Maybe in that way you can tell him with greater detail what doesnt seem to work as good as you expect to.
And I am sorry that uppercase filenames bother you.
I will see that at some point we convert them back to lowercase.
Thank you for your feedback.
-
Another thing... even with the new graphics.library I save ~160k of chipram by using fblit on my A1200.
Now that you mentioned it, I took a closer look at my (fairly) vanilla 3.9/CGX install, which you can see a shot of here (http://www.amiga.org/gallery/index.php?n=3232).
I didn't think about it before, but looking at that, the largest free block of chip ram I have is 2,036,624 bytes. That means I'm only using about 60K of chip ram to start with.
RTG FTW :)
-
The goal for graphics.library 40.25 was to be better than 40.24. If you find room for further improvements, why dont you drop your comments on the corresponding thread, so that the guy which is actually enhancing this library, Cosmos, improves it further? He is still looking for suggestions. Maybe in that way you can tell him with greater detail what doesnt seem to work as good as you expect to.
Hm, OK. I haven't really been paying much attention to what graphics.library 40.25 is meant to do, I'm just commenting on the "you can now forever remove" list. Appearantly FBlit still makes a rather big difference on AGA at least.
And I am sorry that uppercase filenames bother you.
I will see that at some point we convert them back to lowercase.
Great. I'm still pussled about the optimization though, the new files are exactly same size, but different md5sums. I would have expected small differences in filesize as well.
-
Great. I'm still pussled about the optimization though, the new files are exactly same size, but different md5sums. I would have expected small differences in filesize as well.
Doesn't take much really. After all, even if there is one byte of data in the file that is different, the size isn't going to change but the md5 hash will.
-
Doesn't take much really. After all, even if there is one byte of data in the file that is different, the size isn't going to change but the md5 hash will.
Yes, Piru just explained it for me.
I must say though, I dont really like it, would be so much better if the version string could also be patched to reflect the changes done. Now we end up with lots of binaries that at first glance are the same, but yet are not. And god forbid you try to use one of those files from a BB4 system on a 68000 system. And for what gain, really? Optimized MEmacs? WTF? :laughing:
-
Those optimizations are basicly C division and multiplication compiler dependent optimizations for 020 and up, which have been around for quite a while.
I know that you dislike the fact that they are optimized for 020+ because they cannot work on the Minimig.
But then, I invite you to share your knowledge on the modded AmigaOS 3.9 you made for your Minimig (68000) so that you share it with others. I can create a section on my website if you wish, with your help, of course. And then we can help Amigaos 3.9 on 68000 move forward. This would be particularly interesting for both the Minimig and the soon to be released fpgaarcade (which IMHO makes it even more interesting).
-
In my case, the new graphics.library makes the palette preference of AmigaOS 3.9 to crash at the moment where the colorwheel gadget is about to render inside the window. I own a BPPC, so i suppose this is a conflict between the library and the PPC code of the gadget.
-
Thanks for your report!
-
>In my case, the new graphics.library makes the palette preference of AmigaOS 3.9 to crash at the moment where the colorwheel gadget is about to render inside the window.
Ok, thanks for reporting : I'll fix that !
>even with the new graphics.library I save ~160k of chipram by using fblit on my A1200.
I think it's because of F_AddBob/F_RemIBob who are not in the v40.25 library for some reasons...
-
fixed !
Remember that the v40.25 is a WIP and I can't test the whole WB by myself !
So, when you find an issue, please, email me as soon as possible...
-
Thanks Cosmos!
-
fixed !
Remember that the v40.25 is a WIP and I can't test the whole WB by myself !
So, when you find an issue, please, email me as soon as possible...
Cool. I will test it as soon as you upload it on Aminet and report any possible problems.
-
>I save ~160k of chipram by using fblit on my A1200
Maybe I found a solution for enable F_AddBob/F_RemIBob again... These
two functions speedup a lot icons rendering, I know... And save chipmem too...
-
I know that you dislike the fact that they are optimized for 020+ because they cannot work on the Minimig.
Well, that's not really the issue I see here. what I dislike is that there is no way to tell apart original CBM binaries and these 020 binaries unless you have checksums around to compare with. My suggestion is ofcourse to alter the version strings inside the binaries as well - bump minor with 1 and set a current date, it's should be easy enough.
But then, I invite you to share your knowledge on the modded AmigaOS 3.9 you made for your Minimig (68000) so that you share it with others.
It isn't modified, the updated kickstart uses the regular ROM updates, I just put together a kickstart of my own to save RAM.
The only bits that dont work on 68000 are apps that use resource.library, and some ReAction classes (and they typically exist as 68000 compatible versions in ClassAct), some datatypes (but 3.1 works, and on such a system, how many datatypes do one need anyways?). The 3.9 Workbench works just fine, up to 45.129, where it was "optimized" for 020 (I use quotes since I _really_ cannot see _any_ speed difference whatsoever on my other systems). Oh, and C:MakeDir - appearantly someone thought the creation of directories went too slow at some point.
I can create a section on my website if you wish, with your help, of course. And then we can help Amigaos 3.9 on 68000 move forward. This would be particularly interesting for both the Minimig and the soon to be released fpgaarcade (which IMHO makes it even more interesting).
I can upload a list of files, versions and md5sums for example. I will update my kick39.rom with BB4 stuff as well (if possible), and can give you that as well. I don't see much future for it though, since all bug fixes and feature additions only happens (mostly silently) with 020+ in mind. FPGAArcade will hopefull have the option of having a CPU board with a real 68k on it, as freely available 020+ softcores have yet to appear. My A500 will have a 020 quite soon, and making it even less of an issue for me.
-
Well, I have been torturing AmigaOS 3.9 to work with a 68000. So far so good, I did some regression tests to find out what is compatible, and whats not.
The good part is that it works on any Amiga with 3MB of any ram (you need 512KB more if you havent got a real kickstart 3.1 and want to softkick).
Featurewise with my tweaked setup:
-Glowicons work
-large HDD support works
-wb disk fuel gauge works
-cdrom support works
-Aweb works
-IOmegaTools works
-Vinced (shell with history, etc.) works
-Search function, even with integrated pull down menu works
-WBclock works
-Icon information works much like rawbinfo (but not exactly the same way)
-I have a working mp3 player (not Amplifier 2.3x though)
-Animatedicon seems to work, until it fails due to a problem with datatypes
-wbrun works
-xadmaster works
-HDToolbox with large drives works (did a simple trick)
As I said, I am having problems with datatypes, but I hope to fix that soon. The same goes with the TCP-IP stack, and deficons (which hopefully will work).
@kolla
It could be great if you could help me a bit. I am so near of having most of 3.9 components working.
-
@kolla: tobiflex core that is the base of yaqubes softcore for fpgaarcade already got 68010 compatibility in meantime. he is heading further for 68020.
-
cosmos: i see you ve released w3d library patch. join forces with matthey, he has also patched the same library in asm but he is mostly working on w3d hardware drivers at the moment. it makes no sence to work in parallel. anyway it is a good oportunity if you joined us, if you have bvision setup, to test w3d patches and also the new storm mesa. head over to utilitybase and search for the w3d/mesa thread.
-
Excellent work as always, thanks!
Btw., what are the recommendations BB3-wise or BB4-wise: which 68060.library and exec (Piru or BB2-one) to use?
-
Excellent work as always, thanks!
Btw., what are the recommendations BB3-wise or BB4-wise: which 68060.library and exec (Piru or BB2-one) to use?
The recommendations for what you are asking are the same as with any sub-version of AmigaOS 3.9.
-
-Search function, even with integrated pull down menu works
Are you here talking about the "Find" from the "Window" menu, or something else? I replaced SYS:System/Find with one of the many similar programs on aminet.
-Icon information works much like rawbinfo (but not exactly the same way)
Well, that's just the original info window from workbench.library, with its missing "pure" and "hold" ticks, insanely large window etc. Would love to see it updated, file flags added, display version, md5sum, resizable window...
-HDToolbox with large drives works (did a simple trick)
Which HDToolbox? I ask since the OS3.9 one uses Reaction, so I've only used 40.4 from OS3.1.
As I said, I am having problems with datatypes, but I hope to fix that soon.
Which datatypes? I use datatype.library 44.47 and picture.datatype 42.1 from aminet, and 3.1 datatypes or whatever I find on aminet that works. amigaguide.library 45.5 works, 45.6 doesnt.
The same goes with the TCP-IP stack, and deficons (which hopefully will work).
I have Miami myself, and never really thought of deficons :)
@kolla
It could be great if you could help me a bit. I am so near of having most of 3.9 components working.
I'm not sure what you need help with :)
-
@kolla
Regarding the Find command on the system drawer and menu, I did the same as you have done. RAWBInfo was replaced by wbinfo29 (on Aminet), which works similarly (it requires mui though). HDtoolbox is better replaced with HDInst 6.9 (on Aminet), which works great (hdwrench.library is not needed anymore, you can delete it).
Thanks for your tip on datatypes, I will follow what you did.
DefIcons, hopefully can be tweaked to work with GlowIcons (I really dont know), but without the prefs GUI (get it from newicons46 on Aminet).
In relation to the TCP-IP stack, Genesis wont work as it requires the dreaded 020+ resource.library. But, the mui genesis demo (on Aminet) should work. Anyway AmiTCP is always a good backup option.
So, I hope I get a couple of issues solved by now. I will get back later with hopefully less issues and more solutions. :)
-
BoingBag 4 got updated (version 0.2c):
-Updated icon.library to 46.4.163 (New optimized DrawIconStateA() function and some small tweaks)
-Filenames are now in proper lowercase
If you already have another BB4 version installed, simply install this one over the old one.
For downloads and information visit: http://lilliput.amiga-projects.net
-
>Another thing... even with the new graphics.library I save ~160k of chipram by using fblit on my A1200.
Please, Kolla, try FBlit with F_AbbBob & R_RemIBob disable and watch if you save ~160k of chipram again ?!
I wanna be sure...
-
BoingBag 4 has been updated to 0.7d
http://lilliput.amiga-projects.net/bbag4.htm
-
BoingBag 4 has been updated to 0.7d
http://lilliput.amiga-projects.net/bbag4.htm
Very nice! thank you very much! What is new specifically? I looked at the list of updated components for BB4, but didn't see a changelog.
-
It seems that BB4 has two versions of datatypes.library, both 44.47 (in files3/libs) and 44.48 (in files1/libs) - files3 is the dir with 020+ optimized binaries, right?
@Cosmos
I'm sorry - I never got around to test it out, I'll try again :)
-
Thank you, because for me update the icon.ibrary lastly with the new updates is impossible although I have the library version for it.
-
Hi:
Only one question: Which chip ram do you get with BB4 in an A1200 and if possible compared to chip ram with BB2?
-
Very nice! thank you very much! What is new specifically? I looked at the list of updated components for BB4, but didn't see a changelog.
from 0.7c to 0.7d, just the inclusion of FastFilesystem 45.16 (read the changelog in the included readme).
-
@kolla
You are right, not only datatypes.library, but also diskfont.library. Now it is fixed. Thank you!
@Templario
If you need any help just PM in spanish. ;)
-
Hi again:
This are the results in an A1200 upgrading from BB2 to BB4 (I've just done it):
BB2 Chip Ram: 1.416Kb (69%)
BB3 Chip Ram: 1.135 (55%)
BB4 Chip Ram: 1.170 (57%)
Ok, you get 2% more from BB3 to BB4, but tell me, Why must I loose 12% from BB2 to BB4? Where's my benefit?
Ok, I'm only looking one thing, but, do I gain or loose?
-
Slight OT: May I ask how one can build his own "AmigaOS ROM Update" file which combines a multitude of resident modules in just one file? I would like to built my own version instead of using the LoadModule command for all the replacement files. Is there a tool for it?
-
Slight OT: May I ask how one can build his own "AmigaOS ROM Update" file which combines a multitude of resident modules in just one file? I would like to built my own version instead of using the LoadModule command for all the replacement files. Is there a tool for it?
You should contact Doobrey and ask him to support that build option inside his Remus program.
http://www.doobreynet.co.uk/
-
Hi again:
This are the results in an A1200 upgrading from BB2 to BB4 (I've just done it):
BB2 Chip Ram: 1.416Kb (69%)
BB3 Chip Ram: 1.135 (55%)
BB4 Chip Ram: 1.170 (57%)
Ok, you get 2% more from BB3 to BB4, but tell me, Why must I loose 12% from BB2 to BB4? Where's my benefit?
Ok, I'm only looking one thing, but, do I gain or loose?
What matters, probably in your config, regarding chipmem usage, is your updated rom modules. They give you lots of benefits, including very large harddisk support, fixed ram disk space, faster and better behaved scsi.device, etc.
I know chipram is precious, but fastmem is way better ;)
BTW: Have you tried using env-handler to reduce your chipmem usage?
-
Well, I've just tried env-handler, installed it on C and disabled the commands it says and the chip ram is the same (in fact, I loose some kbs).
" They give you lots of benefits, including very large harddisk support, fixed ram disk space, faster and better behaved scsi.device, etc."
In fact, I'm upgrading with a Transcend 32Gb CF and an internal Cd that I had working flawlessly using Smart File System and a cracked Idefix under BB2. I don't wanna be the pessimist here, it must be the benefits are in things I've never had problems before, like that ram disk space... But where I can start to have problems is in any Game or program needing enough chip ram.
-
That's impressive and a much need solution - thank you.
Hope to see more of these smart "all in one" problem solvers.
:hammer:
"graphics.library 40.25b8
Lots of fixes, optimizations and enhancements. You are now able to
remove forever these patches:
* AmyWarp
* BlazeWCP
* CPUBlit
* FBlit
* FText
* IconBeFast
* SetPatch 44.38 (R_WriteChunkyPixel and R_WritePixelLine8
patches).
They are now built in."
-
That's impressive and a much need solution - thank you.
Hope to see more of these smart "all in one" problem solvers.
:hammer:
"graphics.library 40.25b8
Lots of fixes, optimizations and enhancements. You are now able to
remove forever these patches:
* AmyWarp
* BlazeWCP
* CPUBlit
* FBlit
* FText
* IconBeFast
* SetPatch 44.38 (R_WriteChunkyPixel and R_WritePixelLine8
patches).
They are now built in."
Ah, I understand... I've already installed Fblit, Ftext, IconBeFast, SetPatch, and I believe that BlazeWCP too, plus anothers, and perhaps that's why I only loose instead of gain Chip ram? But where I loose it is in BB3, that's why I didn't update. However I will keep this BB4 to try it...
-
Just to let the interested ones know that icon.library has been updated to 46.4.175, and of course, it fixes between other things that infamous iconification bug.
It is available on Aminet, and it is of course part of the updated BoingBag 4 version 0.7e, which is available at the usual places.
-
And for all of you that don't want to loose chipram, this are my new results:
I've just installed CyberbugFixAGA and my chip ram with 64 colors and BB4 now is: 1443 Kb (71%).
What's that?:
http://eab.abime.net/showpost.php?p=175372&postcount=24
So... my chipram is better than ever:roflmao:
-
With this update now I have could updateing the IconLib with the new version IconLib46-4-175, downloaded from Aminet, because before as I said it was impossible, thank you for this boing bag 4.
-
BoingBag 4 version 0.8m
=======================
Icon library updated to 46.4.195 Which now features better support for PNG icons.
New components:
-XAD client for 7-Zip archives that enables UnArc to extract 7-Zip archives.
-XAD client for compressed executables like powerpacker, imploder, etc., and enables Unarc to decrunch them.
-Xfdmaster library and decrunchers that support the xad_xfd client.
-LZMA xfdmaster slave/pluggin for better xad_xfd client support.
You can download it from:
http://lilliput.amiga-projects.net/bbag4.htm
and very soon also on:
http://amigan.emu.net/releases/
-
BoingBag 4 version 0.8m
=======================
Icon library updated to 46.4.195 Which now features better support for PNG icons.
New components:
-XAD client for 7-Zip archives that enables UnArc to extract 7-Zip archives.
-XAD client for compressed executables like powerpacker, imploder, etc., and enables Unarc to decrunch them.
-Xfdmaster library and decrunchers that support the xad_xfd client.
-LZMA xfdmaster slave/pluggin for better xad_xfd client support.
You can download it from:
http://lilliput.amiga-projects.net/bbag4.htm
and very soon also on:
http://amigan.emu.net/releases/
Nice, does the new icon.library properly display OS 4.x icons? I say this because of dual boot users on classic amigas that have OS 4.0 (and soon 4.1) and OS 3.9 on the same machine.
-
Nice, does the new icon.library properly display OS 4.x icons? I say this because of dual boot users on classic amigas that have OS 4.0 (and soon 4.1) and OS 3.9 on the same machine.
Yes, OS4 icons look great. Of course, dont pretend them to be gorgeous with just 16 colors!
-
OK, I must be doing something terribly wrong, but for each install of BB3 and BB4 the text it asks me to add to the beginning of startup-sequence botches everything.
I fixed the botch in BB3 (had to add execute bits to LoadModule)
Now with this one it is telling me that there is no SYS:C/FailAt which is true.
If I comment out all of the stuff asked for in the BB4 script I get a proper boot.
Can someone show what exactly is supposed to be at the beginning of the startup-sequence? Also, if FailAt and LoadResident are missing, where should I grab them?
-
Yes, OS4 icons look great. Of course, dont pretend them to be gorgeous with just 16 colors!
Hmmm....well since I'm using a graphics card with 16-bit or 24-bit depth cannot the OS4 icons be displayed with more colours? Or would this require more than just an icon.library update?
-
The lines of contention are (currently I have them commented out):
SYS:C/ FailAt 21
SYS:C/LoadResident >NIL DEVS:card.resource
SYS:C/LoadResident >NIL DEVS:misc.resource
SYS:C/LoadResident >NIL DEVS:trackdisk.device
SYS:C/LoadResident >NIL L:ramlib
SYS:C/FailAt 20
If I boot with these uncommented the error reads "FailAt: unknown command"
If I comment that line out it says "LoadResident: unknown command"
-
Try just "FailAt 21" without the quotes.
-
Try just "FailAt 21" without the quotes.
will do. not too sure what to do about the lack of LoadResident tho...
-
Hmmm....well since I'm using a graphics card with 16-bit or 24-bit depth cannot the OS4 icons be displayed with more colours? Or would this require more than just an icon.library update?
Yes, of course, you will have more colours. It requires icon.library 46.4.204 and two other libraries (zlib.library and pngalpha.library), all present in the new BB4 0.8n.
-
Gulliver - Haalp! :)
-
The lines of contention are (currently I have them commented out):
SYS:C/ FailAt 21
SYS:C/LoadResident >NIL DEVS:card.resource
SYS:C/LoadResident >NIL DEVS:misc.resource
SYS:C/LoadResident >NIL DEVS:trackdisk.device
SYS:C/LoadResident >NIL L:ramlib
SYS:C/FailAt 20
If I boot with these uncommented the error reads "FailAt: unknown command"
If I comment that line out it says "LoadResident: unknown command"
Have you check that you actually have LoadResident in C: ?
Most of the time these kind of issues come up, it is always related to some human error while adding those text lines, and omitting a space, or wrongly spelling something.
Please check your BBag installation again, I am not home right now, but will try to help you when I get there (I have my Amiga setups at home).
-
Have you check that you actually have LoadResident in C: ?
Most of the time these kind of issues come up, it is always related to some human error while adding those text lines, and omitting a space, or wrongly spelling something.
Please check your BBag installation again, I am not home right now, but will try to help you when I get there (I have my Amiga setups at home).
That's the deal - no LoadResident in C: .
oh and fer sure its def human error :) most likely mine :D
-
This is off topic, so I apologise in advance....but I notice one of the patches that this new graphics library replaces was called "AmyWarp". I'm unable to find this on aminet. Can anyone tell me what this patch is or where to get it from?
Thanks a lot.
-
I found a copy of LoadResident in RemAPollo on aminet. Yanked just it out and will put it in C and see where I am from there.
EDIT: Seemed to work a treat! I guess I am good to go.
no SYS:C/FailAt X, just FailAt x
-
I found a copy of LoadResident in RemAPollo on aminet. Yanked just it out and will put it in C and see where I am from there.
EDIT: Seemed to work a treat! I guess I am good to go.
no SYS:C/FailAt X, just FailAt x
I am glad it is working.
Now enjoy it :)
-
Yes, of course, you will have more colours. It requires icon.library 46.4.204 and two other libraries (zlib.library and pngalpha.library), all present in the new BB4 0.8n.
Thanks, I installed BB4 from your website and the icons are displaying properly, however there is still a large amount of banding - indicating they are not using alot of colours. I'm using a mediator 4000di and Radeon 9250 at 16-bit, 1024x768 resolution.
Any prefs or setting I have to adjust?
BTW, thanks for BB3/4 and all your work :-)
Too bad we couldn't have a full new ISO made for OS 3.9.
-
Thanks, I installed BB4 from your website and the icons are displaying properly, however there is still a large amount of banding - indicating they are not using alot of colours. I'm using a mediator 4000di and Radeon 9250 at 16-bit, 1024x768 resolution.
Any prefs or setting I have to adjust?
BTW, thanks for BB3/4 and all your work :-)
Too bad we couldn't have a full new ISO made for OS 3.9.
At this point, icon.library is still being finetuned by Peter Kneucke, so if you see too much banding, you should post a screengrab and post it over here (http://eab.abime.net/showthread.php?t=57885&page=3) so that PeterK solves any issues.
I am glad you are happy with BB3 and 4 :)
I also wish we could build an updated ISO, but then the copyright status of AmigaOS 3.9 is really complicated (Amiga Inc (?) + Haage&Partner + AmiTCP/Genesis piracy claims). :(
-
I'm not too sure what the banding means or is, but I do notice some corruption occasionally when moving Icons around or upon closing programs. There will be a rainbow colored blotch or a line across the screen. Cleaning up resolves it.
-
I'm not too sure what the banding means or is, but I do notice some corruption occasionally when moving Icons around or upon closing programs. There will be a rainbow colored blotch or a line across the screen. Cleaning up resolves it.
For what its worth, I only experience that same gfx corruption under WinUAE, not on my real A1200.
-
For what its worth, I only experience that same gfx corruption under WinUAE, not on my real A1200.
Weird - this is on a real life A4000...
-
At this point, icon.library is still being finetuned by Peter Kneucke, so if you see too much banding, you should post a screengrab and post it over here (http://eab.abime.net/showthread.php?t=57885&page=3) so that PeterK solves any issues.
I am glad you are happy with BB3 and 4 :)
I also wish we could build an updated ISO, but then the copyright status of AmigaOS 3.9 is really complicated (Amiga Inc (?) + Haage&Partner + AmiTCP/Genesis piracy claims). :(
Thanks I posted with a screenshot to the thread on the English Amiga Board.
Darren
-
Thanks I posted with a screenshot to the thread on the English Amiga Board.
Darren
You forgot to mention on your post over EAB that you are running workbench in 16bits :)
Otherwise on low colour workbenches that banding would probably seem normal.
-
You forgot to mention on your post over EAB that you are running workbench in 16bits :)
Otherwise on low colour workbenches that banding would probably seem normal.
Oops, right. I updated the post :) Thnx.
-
BoingBag #4 v0.9m - Minor update
Changes between V0.9k and V0.9m:
* Adjusted startup-sequence modification instructions.
* Upgraded icon.library from 46.4.228 to 46.4.251.
* Upgraded dos.library to latest version.
* Fixed Genesis icons.
Available at:
http://amigan.1emu.net/releases/
http://lilliput.amiga-projects.net/bbag4.htm
-
@Gulliver
Thanks for the update. Good to see you are still going :).
-
:bump:
Hi Gulliver,
Are you still working on BB4?
Cheers!
-
Boing Bag 4 v0.9s - http://amigan.1emu.net/releases/BoingBag4.lha
Don't let it "automatically update" your s:startup-sequence as it will TRASH IT!
Choose 'no' when it asks, and it gives you the commands to enter manually.
-
Can anyone tell me what the "FAST" in the LoadModule line does except making LoadModule ignore the whole command-line?
I've modded the add to the s-s like this:
;BEGIN BB4s MOD
Version >NIL: exec.library 45 REVISION 20
If WARN
SYS:C/LoadResident >NIL: DEVS:card.resource DEVS:trackdisk.device L:KingCON-Handler
EndIf
SYS:C/LoadModule >NIL: L:RAM-Handler DEVS:battmem.resource DEVS:FileSystem.resource DEVS:misc.resource DEVS:potgo.resource DEVS:scsi.device L:FastFileSystem L:Shell-Seg LIBS:dos.library REVERSE NOREBOOT
SYS:C/SetPatch SKIPROMUPDATES console.device,ram-handler,FileSystem.resource,filesystem,scsi.device,shell QUIET
;END BB4s MODI've added L:RAM-Handler and removed LIBS:icon.library and LIBS:workbench.library (as these two are loaded anyway from disk by SetPatch when not using "DISABLEROMMODULES """). The following needs to be named like this to be recognized by SetPatch:
console -> console.device
filesysres -> FileSystem.resource
fs -> filesystem
scsi -> scsi.device (unsure about this one)
And off course I've removed the FAST from LoadModule.
Wouldn't it be better to stick with either LoadModule OR LoadResident? I've experimented a bit with both but the results are inconclusive but I've found it best to let it remain as is.
EDIT: My LoadModule is version 40.12 (3.10.2009), is there e newer one?
-
@nicholas:
>Don't let it "automatically update" your s:startup-sequence as it will TRASH IT!
What are you talking about!? Can you attach a copy of your supposedly "trashed" startup-sequence for verification?
-
@nicholas:
>Don't let it "automatically update" your s:startup-sequence as it will TRASH IT!
What are you talking about!? Can you attach a copy of your supposedly "trashed" startup-sequence for verification?
No because it was three weeks ago and i didn't backup the trashed copy.
By "trashed" I meant that it removed lines i'd added to my startup-sequence, can't remember off the top of my head what was removed now but it definately removed a few things.
Luckily I took a backup prior to installing it.
-
i'd added to my startup-sequence
There's the problem. User hacking of startup-sequence has been unsupported since OS2.0 came out c. 1990, user-startup is intended for that purpose. Plus the readme explicitly notes that it is intended for a fresh install.
-
This is off topic, so I apologise in advance....but I notice one of the patches that this new graphics library replaces was called "AmyWarp". I'm unable to find this on aminet. Can anyone tell me what this patch is or where to get it from?
Thanks a lot.
http://ftp://anonymous:lowsite@ftp.low-level.com/demo/system/AmyWarp.lha