Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: Oldsmobile_Mike on June 19, 2013, 07:53:19 AM
-
I've seen a few references to this online for a while and would like to test it on my system, however the thread over on EAB is 29 pages long, and the download doesn't include any instructions on how to install it under 3.1 besides saying "check the thread". :insane: :eyeroll:
Any tips besides just dumping the lib file in LIBS: ? Is there something about a "LoadResident" command I need?
Thanks!
-
I think for 3.1 you just dump it in LIBS: (I would rename your old one just in case something goes wrong). I think you only have to do the LoadResident or LoadModule lines if you have 3.9.
I'm using it on my 3.9 install of ClassicWB and it rocks!
slaapliedje
-
Does it come built in to AmikitOS yet?
-
From the readme of the latest version on aminet:
http://aminet.net/package/util/libs/IconLib_46.4
"Added direct support for workbench.library version 39 and 40.
Of course, it's required to load the icon.library resident if
you want to use it with AmigaOS 3.0 or 3.1. This can be done
either with LoadModule, LoadResident or by using a custom ROM. "
-
Never mind, figured it out! Copied the icon.library from the Aminet archive and the LoadResident command from the author's demo ADF that I found a link to on EAB, and then added these lines to the very beginning of my Startup-Sequence:
Version >NIL: icon.library 46 REVISION 4
IF WARN
IF EXISTS LIBS:workbench.library
LoadResident >NIL: LIBS:workbench.library
EndIf
LoadResident >NIL: LIBS:icon.library REBOOT
EndIf
...I'm guessing the workbench.library lines are for people who actually have a workbench.library (4000T owners? Or maybe if they're using some modified version that I think the author is also working on?), dunno but I left them in there. And the rest did the trick! And yes, definitely an improvement on speed, and nice to be able to see NewIcons images now instead of just the little square without having to install NewIcons or a bunch of other cr@p. Just wish I hadn't had to beat my head against a wall for two hours to figure it out. ;)
Ah, Amiga programmers. Making you have to actually work to get anything installed, since 1985. ;)
-
It not that hard tbh.
Just copy icon.library to libs: and then add a LoadModule or LoadResident declaration as first line in S-S to load the library.
I'd suggest to also use the Workbench.library 45.132 which also works for WB3.0 as it has many improvements from the stock one.
Also it's not only the speed and the ability to be able to SEE (and not the dot) EVERY icon available without having to install anything.
It also has the ability to remap colors being able to see even OS4.x and DualPNG icons in OCS systems (without RTG). On Snapshot... you get a popup windows asking if you want to convert the icon to 3.5 format in order to gain size and speed more!
It has embedded support for PNG decoding (which zlib.library done externally) and also it has RTG support for displaying FULLY OS4.x and DualPNG icons without the need of using AfAOS or PowerIcons patch. Everything is built inside the library!
Also there is support for grayscale color remapping and other stuff that I can't remember by heart.
Peter Keunecke's work is just unbelievable and a great asset for every Amiga that uses Workbench frequently.
-
Is there any benefit to loading it from your start-up sequence?
I've just got it in my LIBS folder and everything seems nice and fast on my system.
-
Simply copying it in Libs doesn't work on it's own (unless you have OS3.9). You need a declaration for loading it.
-
Simply copying it in Libs doesn't work on it's own (unless you have OS3.9). You need a declaration for loading it.
Yes I do have 3.9 :)
What is the difference then, is 3.9 loading the library into my FASTRAM automatically with SetPatch or something?
-
I believe so yeah. Either that or the new workbench.library (although I kinda doubt it).
I tried both using icon.library in a custom ROM or leaving it on the disk (libs) and haven't saw any different both in speed and memory conservation.
I'm pretty sure in both situations icon.library is loaded into FastRAM so no harm done to have it on HD.
Will have to ask PeterK just to be sure I guess
-
So in 3.1 this does a double boot?
-
Correct.
Booting till LoadModule/LoadResident declaration, then a reboot and continuing booting.
-
So in 3.1 this does a double boot?
Yes but you can avoid the double boot by burning yourself a custom ROM.
(And put all the double boot stuff in the custom ROM while u r at it, not just icon.library)
My Amiga double boots because of something the accellerator software does, I think. I wish I could get rid of that...
-
I got a reply from PeterK concerning these questions and this was his reply:
...Indeed you don't need LoadResident or LoadModule on systems with SetPatch v44. SetPatch will automatically look into the LIBS: drawer and checks it for iconlib and wblib.
If they are in LIBS: then SetPatch will unload the already resident icon and wb libraries and replaces them with those from LIBS:.
There is no advantage to load them with LoadResident or LoadModule if you have SetPatch v44, except for the copyright.
Loading these libs from a ROM is of course faster than loading them from a harddisk and you can also start the system without a reboot if everything comes from the ROM.
In case that SetPatch or LoasdModule or LoadResident are doing the job you will always need one reboot to make these libs resiident.
Btw, if you load them twice, first with LoadModule or LoadResident and then with SetPatch again without DISABLEROMMODULES "" then you are really loosing 200 kByte of FastMem.
LoadModule or LoadResident are required for OS 3.0/3.1.systems.
-
It double boots on mine (OS 3.1), but since I'm running from CF and my screen stays black during the boot process I don't even notice except for a quick flicker of the power LED. No big deal.
And thanks for the comments @mfilos! I just discovered your blog somewhat recently and have really been enjoying reading about your projects!
Last, any tips where to get the author's updated workbench.library? Obviously going to Aminet and just typing "workbench.library" into the search would be too easy. ;) Is this something I would need to compile myself, somehow?
-
It double boots on mine (OS 3.1), but since I'm running from CF and my screen stays black during the boot process I don't even notice except for a quick flicker of the power LED. No big deal.
And thanks for the comments @mfilos! I just discovered your blog somewhat recently and have really been enjoying reading about your projects!
Last, any tips where to get the author's updated workbench.library? Obviously going to Aminet and just typing "workbench.library" into the search would be too easy. ;) Is this something I would need to compile myself, somehow?
It's in the extras folder when you extract the icon library archive.
You have to manually patch workbench library using spatch IIRC.
-
...And thanks for the comments @mfilos! I just discovered your blog somewhat recently and have really been enjoying reading about your projects!
Last, any tips where to get the author's updated workbench.library? Obviously going to Aminet and just typing "workbench.library" into the search would be too easy. ;) Is this something I would need to compile myself, somehow?
Thanks for the good words mate.
I just made an archive for you including Workbench.library 45.132 plus the ReadMe file which you can get from my Dropbox here:
https://dl.dropboxusercontent.com/u/939939/wblib_45.132.lha
-
I just made an archive for you including Workbench.library 45.132
Awesome!!! Works great! Today was my first chance to mess around with it again so of course I stayed up till 7am in the morning patching & updating libraries/etc. all over the place, made my little 'ole A500 so fast that I had to put Workbench back into 16 color mode just so it would be slow enough to be usuable! No joke! ;) Thanks!