SYS:C/Make Link: function not implemented?

[matthey]

Another thought - perhaps the icon def_RAM.info somehow got changed to an icon of a different type?  For example a Project or a Tool icon, instead of a Disk icon?

If you are using MakeLink because Peter K's icon.library ghosts the Ram Disk icon when the icon is in ENVARC:sys/def_ram.info, it is now possible to add "NoGhost" to the icon tooltype of the icon which you do not want ghosted. It is not possible to add the "NoGhost" tooltype to a disk icon but Peter claims "WB can handle that [icon] if it's a drawer, tool or project icon." The icon type can be changed with Sys:Tools/IconEdit of course.

http://eab.abime.net/showpost.php?p=1028014&postcount=1375

Another tip for keeping the S:Startup-Sequence minimal when there is adequate memory is to set the P (Pure) and H (Hold) file protection bits of C:Assign and C:Execute which allows removing the 4 resident commands pertaining to them. Other common candidates for this technique which provides a small speedup and reduces memory fragmentation include C:Execute, C:List and C:Mount if they are used from scripts or the shell often.

[matthey]

@OP - since we're on the subject, you might also want to make sure you have the latest version of the Peter K. icon.library.  It's not on Aminet, I had to hunt through a ridiculously long thread on EAB to find it.  @Matthey - do you have a link handy?

The newest version of Peter's icon.library (version 46.4.412 currently) is always on the first page of the thread. I'll link to that page since it sometimes has important information.

http://eab.abime.net/showpost.php?p=814987&postcount=1

I am using PeteK's icon.library but I don't have any ghosting on the RAM Icon? However I am getting ghosting on .lha files if that makes a difference.

The idea with the icon.library was to make generic default icons (no icon) ghosted which is logical and sometimes helpful to have this visual indicator. The Ram Disk icon would not be ghosted if it was copied to the ram disk (and you had the newest icon.library) but that would require copying it at bootup every time or using MakeLink.

[matthey]

Which library files should I delete?

I recommend keeping icon.library 45.4 (01/24/06) as a backup with a different name. I believe this is the newest official icon.library which came with AmigaOS 3.9. You may have icon.library 40.1 (02/15/93) or similar if you have AmigaOS 3.1 installed. This version is the one in most 3.1 kickstart ROMs.

[matthey]

This is what I am getting.

My AmigaOS 3.9 Amiga gives:

> version ram-handler full
ram-handler 44.24 (12/01/04)
> version c:makelink full
makelink 45.0 (12/24/00)

Hmm.

[matthey]

Where would I get a newer version from?

A recent ram-handler 44.23 is in the AmigaOS 3.9 official BB2 "DEVS:AmigaOS ROM Update". The ram-handler 44.24 should be in the "unofficial" Boing Bag updates as well as elsewhere but this is a kickstart module. There are several ways to patch it in after kickstart is loaded which should have been done in your S:Startup-Sequence if you are using the unofficial Boing Bags. I use Blizkick and my own custom kickstart so I don't need it and can't say specifically what is need.

[matthey]

I wouldn't have a clue how to do that

If you have the "official" BB2 installed, then this should be done for you by the installation. Check that:

1)  you have a file in DEVS: called "AmigaOS ROM Update" which is 321768 bytes
2)  there is a SetPatch line in your S:Startup-Sequence and that it is not commented out with a ";"
3) that the Workbench "About..." menu shows Kickstart 45.57

If you are using the "unofficial" Boing Bag updates then everything also should have been installed for you and you need to refer to the documentation for it or have someone who has it installed correctly tell you what files and changes to the S:Startup-Sequence are necessary.

This page says ram-handler 44.24 is bugged:

It would probably be better to stick with ram-handler 44.23 if there is a bug. I didn't notice since the bug is not listed under the "AmigaOS 3.9 bugs" link not that I have had major problems. I'll have to ask Gulliver what the bugs are.

[matthey]

Do I want to know what a "nuke" is?  It sounds terrible.  On the other hand, ask me what a "soggy buffalo" is.  

Maybe some kind of shot? A quick search gives a Nuke Waste, Nuke Rainbow, Jager Nuke, Nuclear Waste, Russian Nuke and Nuke bomb. I've never heard of any of them but I'm a beer drinker too. They probably have completely different liquor nomenclature across the pond. Hmm, we better be careful or the NSA may classify Amiga.org as a terrorist site .

P.S. Nice work on getting carvedeye straightened out.

[matthey]

@paul1981
Mmm, NewCastle. Good beer. I understand the picture but what did that have to do with a nuke?

[matthey]

Must be British slang.  "Newcastle" - "Newc" - "Nuke".  At least that's what I'm assuming!

Makes sense now. I would have caught it if he had spelled it "Newc".

At least it's not this!  

Is the pic from Persion Gulf Inferno? Fun memories of that game, explosive chages and all .