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

[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.  

[Oldsmobile_Mike]

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

[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.

[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.

[Oldsmobile_Mike]

Or you can copy a disk.info file from some other location into RAM:, prior to the LoadWB command. Also you can use the new icon library to automatically load an image (without the soft link), but that's probably just going to confuse things more.

Kolla's answer is the most "technically correct" if you want to do it the way the OS designers intended.