What is the best icon set to use on A2000 with 3.1

[Oldsmobile_Mike]

Mike, what settings are you using on VisualPrefs to get that 4.1 look?  I'd be interested in trying that out without too much fuss

Also, for anyone... is it me or does the version information for icon.library for PeterK's respond differently once it's in the LIBS: folder and made resident?  Like check it out in the install folder and you get

icon.library 46.4.409
(68020)

vs.

icon.library 46.4
(68020)

I typically use "VersionWB" now, instead of just "version" or "version xxx.library full".

With VisualPrefs, I started with a template, then I basically deleted every bit of it except for the Boing Ball logo.  Then made a bunch of changes in the GUI settings.  Then added Birdie (with mostly default settings).  It was an iterative process over a period of time.  Someone here from AmigaKit actually has a much better (as in, it looks more like 4.1) setup, I asked them once what they ran but never implemented it all, myself.  It's somewhere here in a thread though, if you want to dig it up.

Anyhow, some screenshots.  Don't be all "copying me" though.  Go make up your own stuff!  

[tonyvdb]

3.0/3.1 isn't that smart, so you need to force it to use the updated version on your disk by putting either the LoadModule or LoadResident command before SetPatch in your Startup-Sequence:

Code: [Select]


LoadResident >NIL: LIBS:icon.library REBOOT


Or the more full example, given in the docs:

Code: [Select]


Version >NIL: icon.library 46
If WARN
   If EXISTS LIBS:workbench.library
      LoadResident >NIL: LIBS:workbench.library
   EndIf
   LoadResident >NIL: LIBS:icon.library REBOOT
EndIf

SetPatch QUIET


You'd need to use Ed to edit one or the other of the above statements into your S:Startup-Sequence.

Ok, so backing this up just a little bit, I put the LoadResident >NIL: LIBS:icon.library REBOOT before set patch and now It does not load workbench and I get "LoadResident: unknown command"

[zipper]

Of course, because that command is not a part of OS 3.1. It's in that iconlib archive.

[tonyvdb]

Ok, so where do I find and place the LoadResident too?
I guess my bigger question is where should the iconLib_46.4 folder be placed as nowhere in the documentation does it say where in the system folder this stuff should be installed.

[Oldsmobile_Mike]

Ok, so where do I find and place the LoadResident too?
I guess my bigger question is where should the iconLib_46.4 folder be placed as nowhere in the documentation does it say where in the system folder this stuff should be installed.

• LoadResident is a command. It goes in C:. (should probably also stick LoadModule in there, too).  These are not unique to icon.library, lots of programs use these commands.
• Icon.library goes in Libs:
• The other stuff in the C directory of the archive is optional, it's simple command line utilities to do things like add outline, shadows, etc., to the icon text. They're described in the manual.

The program author included a lot of optional stuff: config files for FBlit, benchmark tools, palette prefs settings, source code, etc.  Basically everything in the "bonus", "source", and "ThirdParty" drawers is optional, with the exception of "ThirdParty/Loadmodule" and "ThirdParty/LoadResident".  ;)

[tonyvdb]

Ok, got that right now and it's boots into workbench however there is no change at all in the icons? Maybe I should have just done the simple line
"LoadResident >NIL: LIBS:icon.library REBOOT"
Load time is longer so it must be doing the reboot as requested. I did the full version that's shown in the startup sequence.
I'm sorry for all the questions....

[Oldsmobile_Mike]

Ok, got that right now and it's boots into workbench however there is no change at all in the icons? Maybe I should have just done the simple line
"LoadResident >NIL: LIBS:icon.library REBOOT"
Load time is longer so it must be doing the reboot as requested. I did the full version that's shown in the startup sequence.
I'm sorry for all the questions....

To confirm if it's running, drop down to the command line and do a "version icon.library full", or try enabling one of the C: options, like "OutlineIconText".

Remember, this isn't what makes the icons "look different".  But it greatly improves performance when using more advanced icon sets like GlowIcons or Ken's Icons, for example.    Are you still running stock 3.1 icons?

[tonyvdb]

 Are you still running stock 3.1 icons?

I'm feeling dumb here, yes stock 3.1 icons. That's what I want to change. I hate the default disk icon it uses and my RAM disk also just looks like a disk not the chip I see on my a4000

It says "icon.library 46.4"
(68000)

[Oldsmobile_Mike]

I'm feeling dumb here, yes stock 3.1 icons. That's what I want to change. I hate the default disk icon it uses and my RAM disk also just looks like a disk not the chip I see on my a4000

It says "icon.library 46.4"
(68000)

Sounds right.  Well, what do you want to change the icons *to*?  Plenty of options already listed in this thread, my recommendation for a low-spec system is still as follows:

3.1 + BetterWB:  http://lilliput.amiga-projects.net/BetterWB.htm
The full set of MagicWB icons:  http://aminet.net/package/pix/mwb/StandardMagicWB16

All the other things we keep talking about here (NewIcons, GlowIcons, Ken's Icons, etc.) would work, but they're going to be slow on a stock 68000, and require higher color modes than a low-spec system can "comfortably display".  

Anyhow, you could start with the above and then build on it, maybe by adding MagicMenus, or a  multi-commodity like MultiCX or MCP.  There's no real "standard" as far  as customizing an Amiga goes, just look at other people's screenshots  and ask what they're running, if you're curious.  

[blakespot]

No no no.  Icon.library is built into ROM.  With 3.5 and 3.9 they "look on the disk" to see if there's a newer version first, as opposed to automatically using the version that's on the ROM.

3.0/3.1 isn't that smart, so you need to force it to use the updated version on your disk by putting either the LoadModule or LoadResident command before SetPatch in your Startup-Sequence:

Code: [Select]


LoadResident >NIL: LIBS:icon.library REBOOT


I did this and the command fails, indicating (when I remove NIL) that icon.library object already exists. I have A2000 w/ 68020 (using 68020 icon.library, or trying) and 3.1 ROM and WB 3.1.

I renamed old icon.library and put the 020 icon.library in LIBS: as the orig name (icon.library).

Ideas? Tnx.

[Oldsmobile_Mike]

LoadResident has to be the first line in your startup-sequence. Before SetPatch. Did you put it there?

[blakespot]

Setpatch is not the first line in my s-s. But I put this line just before setpatch.

So this needs to be the first line? It can't be really, as I have logic checking to see if Rom is 1.3 or 3.1 and then redirection to scripts to load appropriate Workbench.

bp

[Oldsmobile_Mike]

Huh. Okay, that's probably going to cause problems, since the LoadResident command triggers a reboot. I guess it needs to be something like this:

- if 1.3, skip LoadResident
- if 3.1, run LoadResident, reboot, skip 1.3 stuff, run 3.1 stuff

Honestly not sure. You're going to have to figure out how to get the LoadResident reboot to 'play nice'  with your 1.3/3.1 selector logic.

Or just dump 1.3, lol.

[Oldsmobile_Mike]

Funny story, when I was running 3.1 on my A500 it actually had to do two reboots to boot up. One to add the VXL*30 32-bit RAM, one to load all the stuff I had crammed into LoadResident and LoadModule commands, and then it could boot. Sucker took forever and was a careful balancing act of scripting, since I wanted all the stuff those commands were loading loaded into the 32-bit space instead of 16-bit space, etc. Upgrading it to 3.9 made that process a lot less painful.

Always figured one of these days I'll get around to learning how to burn my own custom 3.9 ROM's.

[blakespot]

Huh. If I told you that I was putting load resident before setpatch but halfway through the startup sequence script, would you anticipate that I would get a object already present error like I'm getting? It is before set patch as I have it now.

I guess load resident after a reboot doesn't do it's thing again after checking to see if what it loaded is already loaded.

 If I comment out the load resident line in the startup sequence and boot the system, I get no error. This is after having replaced the 3K icon.library file with the 38K or so modified icon.library file. Would you expect a smooth boot? Is there anyway it's actually loaded on it's own under 3.1?

 Thanks for the help, by the way.


bp

[Oldsmobile_Mike]

I think you'd have to do a check:

If icon.library = version "anything other than the version you've installed" then run the LoadResident command
Else skip running the command

Or "if version icon.library = version you've installed, skip running the load command"
Else "run the load command"

That's just offhand, obviously.  I'm not near a computer right now.  But it sounds like part of the problem is that it's being loaded twice.