SYS:C/Make Link: function not implemented?

[Oldsmobile_Mike]

Have you examined your startup-sequence for that command somewhere in it?

Did you do a fresh install (onto a clean partition) of 3.9 + BB1-4, or install on top of an existing partition/OS install?

[Oldsmobile_Mike]

Haha.  I love when Amiga users get into arguments.  

I just checked mine and for what it's worth, the "SOFT" option does work.  I changed mine because I wanted to use a custom icon that's stored in a different place (and commented out the original line), I'll include a screenshot in case this is any help to OP.  But I do crazy stuff so maybe it's better to "fix it right" and not follow my example.  

OP - try dropping down to a command prompt and checking your version of ram-handler?  Should be 44.23, I think there's also a buggy 44.24 floating around out there somewhere.

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?

You can also do "version c:makelink full" from a command prompt, mine is v45.0 (12/24/2000).  Perhaps somehow you have an older version of the command?

[Oldsmobile_Mike]

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

Haha.  You guessed it, that is exactly why I moved my def_RAM.info to a different location.  To avoid that ghosting.  I saw that he did add those "NoGhost" features recently, but I haven't bothered to change my S-S back.  

[Oldsmobile_Mike]

@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?

[Oldsmobile_Mike]

I have checked my Libs Folder and I have 5 different icon.library files which are icon.library, icon.library.45.1, icon.library.45.4, icon.library_68000 and icon.library_69020, could this be the problem?

Hahaha.  While I don't think this is the cause of you're problem, you're going to want to get rid of those.  :lol:

What I do with mine is rename them with a ".old" extension during testing, then once I'm sure the new replacement is working I move them into an archive partition.  Keep that main LIBS: folder clean!  

[Oldsmobile_Mike]

The newest version of Peter's icon.library 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

AAAAHHHHHH.  FML.  You know, I'd always look for it on the LAST PAGE.  Thinking "last is most recent is newest".  I guess my logic just totally fails, in this case.  

[Oldsmobile_Mike]

Which library files should I delete? Do I rename the file I'm keeping as just plain icon.library?

Correct.  You want the correct one for your processor from @Matthey's link (IconLib_46.4.412.lha), rename it to just "icon.library", and stick it in LIBS:.  

Edit: you should also get the C: tools from the Aminet version ( Aminet - util/libs/IconLib_46.4.lha ), as well, and stick those in your C:.  You may want to play around with them, they let you do things like make outlined text, or you may not.  But doesn't hurt to have them.  

[Oldsmobile_Mike]

There are 3 library files which one will I use? There is icon.lbrary_Lined, icon.library_68000 and icon.library_68020. Will it be the 68020 as I am using an 030 accelerator?

Ding-ding-ding!  :lol:

[Oldsmobile_Mike]

After you get that installed, reboot and drop down to a command prompt and give us the output of :

version ram-handler full
version c:makelink full

[Oldsmobile_Mike]

This is what I am getting.

Good sir, you need to update your ram-handler.  You're using an old version from 1992, that is no bueno!  

[Oldsmobile_Mike]

Where would I get a newer version from?

It should have been installed as part of your BB updates, however since it sounds like you installed 3.9 on top of 3.1 (rather than a fresh 3.9 install), who knows what old junk you have left in there.  One sec, let me see what I can do.  Unless @Matthey beats me to it.  

[Oldsmobile_Mike]

This page says ram-handler 44.24 is bugged:

http://lilliput.amiga-projects.net/TechDetails.htm

I've always used 44.23 (which is included in the 3.9 ROM updates), but what the heck, I'll try 44.24, and now you can, too.  File attached, stick it in your L: and reboot.  Save any old versions as ".old", or a backup method of your choice, first!  

(We may have to revisit your Startup-Sequence again, but try the above, first.)

[Oldsmobile_Mike]

Here is another tip.  I'm copying this from someone else's thread and just going to boldface the parts that you need to look at now:

C:LoadModule L:FastFileSystem L:Ram-Handler L:Shell-Seg DEVS:scsi.device LIBS:icon.library L:workbench.library NOREBOOT
C:SetPatch SKIPROMMODULES filesystem,ram-handler,shell,scsi.device,icon.library,workbench.library QUIET

In other words, somewhere in your first couple lines you should have the "LoadModule" command.  After that somewhere should be "L:Ram-Handler".  Likewise, your SetPatch SKIPROMMODULES should be set to skip the version of ram-handler that's in there.

Basically what you're telling your system is to ignore the old version on the ROM and load the new version from L:.  Kapish?  

[Oldsmobile_Mike]

Here is what my s-sequence looks like.

Delete the linefeed after SKIPROMUPDATES.  Open the file in Ed or some other text editor, and put that whole command all on one line.  You'll have to scroll to the right to see the whole thing, but I think you have a linefeed stuck in there that's breaking the command.

Edit: do the same for the other lines (LoadResident & LoadModule) as well.  No linefeeds.  

Edit 2:  added picture.

[Oldsmobile_Mike]

What are linefeeds? mike I am hopeless at this kind of stuff What if you copied and pasted the s-sequence to this thread with the correct stuff on and I can copy and paste it to my Amiga would you be able to do that, that's if you don't mind I would really appreciate it.

Linefeeds man, carriage returns, don't you remember from using the old typewriters?  I'm mixing my terminology a bit, but what you get when you press the enter key.  Make your text be all on one line (like in my screenshot) instead of on two lines.  I think you've got a break in the command because of that that's causing it to not run correctly.

I could copy & paste but my S-S is going to be different because I use a bunch of Cosmos's libraries, a bunch of extra stuff for my '040, etc.  Think of a Startup-Sequence like a finely tuned machine.  You wouldn't pull your 302 from your Ford Mustang and stick it in your Chevy Camero, would you?  Each needs to be tuned for the specific system it's installed on.  And I'll shut up with my car and typewriter analogies now!