TrueColor and OS 3.5 icons for ClassicWB & Scalos on WB 3.0/3.1

[PeterK]

Hi Bloodwych,
I've just tried out your excellent ADVSP package under WinUAE because mfilos wanted to know if he could use my icon.library together with it. I'm really impressed, ClassicWB seems to have a lot of interesting features which can make life much easier for owners of OS 3.0 systems. Your compilation gets the most out of these older Amigas, that's great.

The ADVSP v27 which I tested is still using the older Scalos 1.2d. On my own WinUAE installation with OS 3.9 I've the latest Scalos beta version which can be launched on a second screen as a possible alternative to the Workbench. Is there a good reason to keep up with this version of Scalos for ClassicWB ?

When I tried to set up my icon.library on ASVSP I had to replace some of the older files with those of a newer Scalos. But finally, there was not so much to change to let it display all types of icons and the best is that it needs no other files from OS 3.5+, just some public libraries and datatypes.

------ OS 3.0 is supported now ! -- Needs less than 512 kB of ChipMem for the icons ! ------

If you would like to try it out, you only have to copy the files in the attached archive into your directory structure. And please tell me if it works. Thanks!

ClassicWB30Icons => all icons for ClassicWB on OS 3.0+ and Scalos 1.2d:
There is a new "information.module" (v3.1b) included, because the older WBInfo v2.9 caused some conflicts with the newicon.library emulation from Stephan Rupprecht . In the new icon information it's possible now to click onto the icon image in order to load the same icon into another tool like Iconian, for example. You also have to use Iconian to change the icon type from "tool" to "project" or else.

Also added are some other patches like PatchRAM which lets the RamDisk display the right amount of used mem instead of always showing "100% full". Other utilities are MemTrailer to avoid some of the memory trashings, MinStack as a replacement for StackAttack, TagLiFE for faster taglist routines and a script called "Enforcer" which can be used for debugging on WinUAE and will be supported by Segtracker, too. Have fun with ClassicWB!

The attachment comes with a new patch called FixScalos to cure all the problems which occured during the screenmode changes before. It should be launched with Run from the end of the startup-sequence. Scalos 1.2d has simply disabled the workbench.library function for updating icons which is called WorkbenchPrivate1(), so I've written an emulation to reactivate it. This should fix problems with IconMaster. Also included is a modified version 37.0 of the excellent AutoUpdateWB utility from Elena Novaretti and Massimo Tantignone

Btw, ClassicWB works pretty well with the 800*600 SuperPlus monitor driver from Ratte, at least on WinUAE.

Important: If you already have installed some iconobject files with v40+ on Scalos 1.2d then please downgrade to the included v39 files, because they cause less conflicts (no graphics corruption while dragging or crashes with icon frames) under Scalos 1.2d. In other words, use the complete package as it is with all files included. Higher version numbers don't mean to get better results here (look into Classes/Datatypes and Libs: for iconobject files). You will NOT lose any features under OS 3.1 !

If your system has only 512 kB ChipMem then it's important to add "ScreenMode" to the "include list" in the FBlit preferences or if you prefer you can run FBlit in exclude mode alternatively (read the docs).

The latest version of the icon.library (now with much faster internal PNG decoding) can be found here:
http://eab.abime.net/showthread.php?t=64079

[mfilos]

PeterK rocked once more

This is a test from my own environment (A600) using 8 colors and the new icon.library + files from PeterK in my custom version of Bloodwych's ClassicWB Full.

[Bloodwych]

Thanks for the info and the files PeterK.

Yes there were a few reasons I found that caused me to revert back from the latest Scalos beta to the older stable non-beta v1.2d. Can't remember all the issues, but it broke a few things and was in general slower on non-accelerated Amiga's.

I will make use of this however since you say it uses free libs and some of the beta Scalos files - probably add it as an install option in the future if it tests out ok. I'd imagine PNG icons are quite slow though on standard Amigas, but it is a nice option to have all icons displaying correctly.

Originally Posted by PeterK

Hi Bloodwych,
If you want to avoid this then please rename or remove the following files:
Sys:System/Copper/Enable/Prefs/Env-Archive/Scalos/Scalos.prefs
Sys:System/Copper/Disable/Prefs/Env-Archive/Scalos/Scalos.prefs

No need to delete.

The Copper enable/disable script actually backs up your current Scalos.prefs file into those drawers, one for Copper enabled and one for Copper disabled. Therefore if you make sure the icons are frameless (Scalos Settings) for both Copper enabled and then disabled first, you won't have any problems with your icon files. Those files above would be replaced by the Copper enable/disable script.

Great work and thanks for your efforts!

[PeterK]

New icon.library 46.4.227. More chipmem remains free when FBlit is dected.
Added a modified version of Stephan Rupprecht's CopyIcon to the programs. This makes it possible under WB 3.1 to copy only the images from any type of source icon (old, new, glow, png or os4) to one or more destinations without changing the tooltypes. Please, report any problems with CopyIcon here and send no emails to Stephan, because I am responsible for this WB 3.1 hack.

I'd imagine PNG icons are quite slow though on standard Amigas, but it is a nice option to have all icons displaying correctly.

Indeed, PNG icons are still very slow because atm they are decoded twice for each image by the png.datatype. Maybe, one day I will write a faster internal png decoder like that one which comes with the PowerIcons program from Elena Novaretti, but I can't say when this could happen.

Anyhow, you can gain much more speed from png icons by simply converting them into the OS 3.5 format with snapshot. That's all you need to do. Btw, don't use any filters for scaling with WinUAE if you want speed, just set the filter to "none".

[mfilos]

Outstanding work as always Peter!!!
Going to give it a test today and report back

[PeterK]

Hey, you're funny mfilos
First saying "outstanding work" and then admitting that you didn't test it yet

Never mind, but do you know an IconEdit replacement or an Icon-Information tool for WB 3.1 that can display OS 3.5 icons or does anybody else have something like this in his tool collection ??

@moderator
A thread title like this would fit a little better:
"TrueColor and OS 3.5 icons for ClassicWB & Scalos on WB 3.1"
Thank you !

Attached is an alternative package with Scalos 40.23 files.
.... deleted ....

Thanks a lot to the mod !

Removed: The alternative package is outdated now! Take the attachment from the first posting instead. The included v39 iconobject files are working better together with ClassicWB.

[Bloodwych]

Not sure about the IconEdit replacement or an Icon-Information tool.

Thanks for putting this up, much appreciated. I'll have a play around next time I'm working on the ClassicWB packs, but for those who want to add support themselves then this thread is a great place to start.

[PeterK]

Updated the CopyIcon tool from Stephan Rupprecht in both packages above.

Since the workbench.library v40 has no WorbenchControl() function as it is supported by OS 3.5+ I've set the default stacksize to a value of 8192 bytes. This change to the program should avoid random memory trashes under WB 3.1 caused by calling the missing function in workbench.library v40.

[mfilos]

LOL Peter, I said outstanding based on what you wrote

Anywayz... I tested tonight on my WinUAE clone environment the new Scalos files and I have 3 comments.

1. System is working just fine but some startup delay occur with some setup messages from new Scalos version like the one below...




2. After Scalos last message, but I get a window declaring that 4 pens missing. I switched back to 8color screenmode and the 8color palette in Scalos but I still get this message.




3. What on earth is that status bar in the lower part of every window? I think it showed some stuff (like total files etc) but when I changed the font it stopped displaying the info. Is there a possibility to remove this or it's in the options of the Prefs file that you couldn't find Peter?


4. Some changes on right clicking occur (like selecting a rectangle area) and change of Title on the right click menu but I guess these are based on the new version features.




Overall it seems really nice, but I don't think I'll put it in the real Amiga for now.

The new icon.library works just fine thought mate. It seem that the Chip RAM is staying put for long LOL.

[PeterK]

Hi mfilos,

regarding 1, 2 and 3, yes confirmed, but as I already said before...

... I cannot set up all the new features in the preferences because I don't have the Scalos.prefs programs ...

Concerning 2, with 16 colors I can just ignore this message about the missing pens, it works despite of this warning, but maybe not with 8 colors ? I didn't try that. I'm using 256 colors on WinUAE, of course.

Concerning the ChipMem, it seems to be sufficient for millions of icons with Scalos 40.23, much better than with Scalos v39.

[mfilos]

Sadly the last full version I can find from that era is 1.4 (40.31).
You can check it out to see if it reacts the same way as 40.23 (but with the prefs).
I uploaded it on my Dropbox so you can download it here mate: http://dl.dropbox.com/u/939939/Scalo...2840.31%29.lha

[PeterK]

Thank you mfilos,
but I've already tested with Scalos 1.4b v40.29. It could even work if you move completely to the 1.4 release, but then it won't have anything to do with Bloodwych's ClassicWB anymore. My hope is that there might be an older release between 1.2d and 1.3w v40.23 which comes with the main Scalos preferences program.

@Bloodwych
Do you have these files ?

[Bloodwych]

You guys are running into issues I've seen in the past. I did attempt a full upgrade to the latest Scalos to see how it ran, replacing all files with the beta ones, but ran into issues as I'd mentioned earlier and reduced performance on standard Amiga's. After weighing up the options, I decided to stick with 1.2d.

I will revisit this however next time I play with the ClassicWB, as it would a nice upgrade.

I don't have those files PeterK.

[mfilos]

Bloodwych my friend, noone said you don't know your shiz :P
Apparently your packs are made for a variety of systems so you certainly made the right choice sticking with the 1.2 Scalos that is rock stable

We're just trying to check out if we can buff a bit our Scalos environment. You know how much I like tinkering systems anywayz.

Btw I emailed Scalos dev team and a friendly guy (Jürgen) replied me with the following:

Hallo Marios,

sorry, but I failed to find a 40.23 archive here. The oldest available archive in your requested range is 40.28.
Due to several CVS/SVN moves I'm also not able to rebuild such an old version from the sources.

This is the oldest version we can use 40.28 which I uploaded on my Dropbox.
PeterK do your magic lol

http://dl.dropbox.com/u/939939/ScalosBeta_40.28.lha

[Bloodwych]

...and I'm really pleased guys such as yourself tinker!

Anything that can add to improving peoples Workbenches is good news.

[PeterK]

The attachment in the first posting of this thread has been updated again. See above...

[Bloodwych]

Wow, pretty awesome work PeterK!!!

I can see another enable/disable/install option being added to the ClassicWB packs very soon!

[PeterK]

Update 5 can be downloaded from the first posting now.

[PeterK]

Update 6 with a new FixScalos can be downloaded from the first posting now. The screenmode changes seem to work correctly now. No wrong colors anymore

If nobody reports any problems here then my job is finished, now. Have fun with ClassicWB.

[mfilos]

Will give it a spin the following days Peter mate! Thanks for your fast response

[PeterK]

Sorry, but I've just realized that I made a mistake in my last versions of FixScalos. I will remove the archives temporarily and do some more checks first.

[PeterK]

Finally, update 7 and FixScalos 0.4 can be downloaded from the first posting, now.

I have to apologize for all the confusion which I may have caused with update 6 and FixScalos 0.2 and 0.3. Sorry for that, but I made a nice mistake which let me believe that I already found the perfect solution for FixScalos at that time. Unfortunately, I used the wrong byte for checking the type of the colormap in the ReleasePen() function and therefore it was disabled permanently. In the new version of FixScalos the ReleasePen() function, which was responsible for all the crashes, is disabled only as long as the Workbench screen is closed. I really hope that this is the end of the story....

Btw, the overscan and screenmode preferences are working great with FixScalos. Now, I can use the EURO36 monitor with a 720*600 resolution on WinUAE (not on a real Amiga). This needs a few tweaks in the startup-sequence instead of the normal monitor crap.

IF EXISTS DEVS:monitors/EURO36
   DEVS:monitors/EURO36 MINROW=0x10 TOTROWS=0x140
   C:PatchOverscan ID=79000 O=N   0 0 639 199
   C:PatchOverscan ID=79000 O=M -40 0 679 299
   C:SetDefMon EURO36
EndIF

[cosmicfrog]

thanks for all ya efforts it really helps our little machine shine

[mfilos]

Peter mate sorry for the late reply but I needed quite some time to test this thoroughly before implementing it into my uber custom ClassicWB setup

So the verdict is...

IT WORKS LIKE A CHARM!!!

I made some minor alterations:
- I commented PatchRAM from the patches since I already have an "Ram-Handler 42.24" inside my Custom ROM.
- I commented the LoadModule declarations for both Icon.library and SCSI.device as I have them in my Custom ROM.
- I removed the PatchWB from my WBStartup folder since now it's in C and run from Startup-Sequence

Other than that, it works very well as you can see from the following screnshots

Just a stock boot Screenshot with nothing but ToolManager visible



Some screenshots from AllIconsOnWB3.1 archive by PeterK showing OS4 icons and DualPNG Ken's Icons.



...and the new Icon information module from Scalos! How awesome is that!



Thanks for the CopyIcon patch as well Peter! It sure rocks a lot more than IconInstaller.

[PeterK]

FixScalos 0.5 now takes a possible failure of OpenWB() or CloseWB() into account.

@cosmicfrog and mfilos
Thank you for your feedback! Good to know, that at least some people have use for my small extensions for ClassicWB and Scalos.

Concerning IconMaster (IconInstaller): you can still use it if the newicon.library emulation from Stephan Rupprecht is also installed. Depends on what you like or prefer, CopyIcon and IconInstaller have different features.

Mfilos, the link from your blog to this thread seems to be broken. And where is your video?

[mfilos]

@PeterK
The link from my blog to this thread works fine for me!
My video which I took some weeks ago was in the previous article but for not searching for it you can see it here: http://www.youtube.com/watch?v=kPMu1H3zeig

[PeterK]

Fantastic video, mfilos
Unbelievable, what's all possible with an A600. Excellent work, thank you.
The link on your new, updated A600 page works correctly. It's the page from March 5'th where it doesn't work and where I could not find the video.

[mfilos]

Thanks for the good words my friend and thanks for pointing the broken link! I fixed it already

[PeterK]

FixScalos 0.6 should solve problems with refreshing icons. The UpdateWorkbench() function was disabled in Scalos 1.2d and is emulated now.

[mfilos]

Yep it sure does
Icon refresh works without issues now \o/

FixScalos ftw!

[PeterK]

Added a modified version 37.0 of the excellent AutoUpdateWB tool.

[mfilos]

I love AutoUpdateWB!
It rox so much that it can run now even in WB3.1!!! Just tested it and it works as good as my OS3.9 installation \o/

Thanks a lot for your continuous work Peter mate

[Bloodwych]

This work is awesome. Can't wait to get around to the next ClassicWB update and slip it in if that's ok with you PeterK.

I will of course give full credits during the Install routine and on the webpage.

[PeterK]

Yes, of course, it's ok to use these add-ons in your next ClassicWB release. But the credits should go to the original authors like Stephan Rupprecht for his CopyIcon tool and the newicon.library emulation and to Elena Novaretti and Massimo Tantignone for their AutoUpdateWB.

[Bloodwych]

Thanks a lot PeterK, much appreciated. I'll make sure I mention them too.

[PeterK]

ClassicWB30Icons => all icons for ClassicWB on OS 3.0+ and Scalos 1.2d:

See above, please !

[mfilos]

Wow that is awesome man and a great addition to Bloodwych's packs since now they can work even without Kickstart 3.1!!!
Lotsa kudos!

Comparing it to the former installation I spotted the following changes:
- Classes/Datatypes/amigaiconobj35.datatype (39.30 instead of 40.18)
- Libs/icon.library (46.4.228 instead of 46.4.227)
- Libs/iconobject.library (39.10 instead of 40.6)

Is it safe for us that used your previous version successfully to our 3.1 environment to use these older versions (not your icon.library ofc) of files (iconobject datatype and library)?

I'll report back with a screenshot later on

Peter you rock man \o/

[PeterK]

ClassicWB30Icons => all icons for ClassicWB on OS 3.0+ and Scalos 1.2d:

The iconobject.library and the relating datatypes didn't change since "update5", I would say. Maybe, you didn't replace these files before, because they are older, but the v39 versions are much more compatible to Scalos 1.2d than the v40 iconobject files. So, please downgrade ! They don't cause graphic corruptions while icons are dragged around and they don't crash with frames or borders!

The icon.library 46.4.228, the CopyIcon tool and the newicon.library 44.4 are just downgraded to OS 3.0 now without losing any possible features in OS 3.1+, as I hope. But if somebody discovers any drawbacks, then please don't hesitate to report them here, since I have only limited time to test each and every configuration which could be installed in reality.

And another request to the moderator:
Could you please change the thread title again and give WB 3.0 more attention now? Thank you !!

[Bloodwych]

Brilliant work - love the screenshots, very impressive! Also thread title changed.

A big thanks for supporting Scalos 1.2d - I think it's the one most people use on Classic Amigas. Once I get some free time, I will thoroughly test in the ClassicWB Scalos packs. As I said above, I hope to add an option so the user can choose to add your icon support upon installation. Perhaps I'll also add it to the enable/disable components menu too just in case people need to disable it for a compatibility issue.

[PeterK]

Thank you, Bloodwych, I didn't notice that you are the moderator too (OOPS, I'm soo blind), but of course, why not ?? ClassicWB is your great project and I still discover more and more nice features every day when I play with it.

Installation as an option is relatively easy, but it could be very hairy and weird to write a safe script to disable and re-enable all my add-ons on the fly. The icon.library, for example, is loaded resident with LoadModule and many other things won't work anymore if you only remove my library. There are a lot of dependencies. Nevertheless, you already have lots of experience in writing these scripts and may find it easy to solve or avoid these conflicts. If I can help you in any way then please just ask me. I would like to do that, for sure.