SYS:C/Make Link: function not implemented?

[carvedeye]

Hi all every time I boot up my Amiga 1200T I get this message before workbench loads up
it is starting to annoy me now do any of you have any ideas? It all started when I installed boing bags 1-4?

TIA Ray

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

[guest11527]

Which file system is on the boot disk? Is this FFS formatted or something else?

[carvedeye]

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?

I think it was a fresh install (haven't been on the miggy for a few month) I have copy and pasted the start up sequence.



; $VER: Startup-Sequence_HardDrive 45.7 (8.11.2014) for BB4
; Startup-Sequence for hard drive systems

If Exists C:IDEFix
  C:IDEFix
EndIf

FailAt 21
SYS:C/LoadResident >NIL: DEVS:card.resource DEVS:trackdisk.device L:KingCON-Handler
FailAt 20
SYS:C/LoadModule >NIL: DEVS:battmem.resource DEVS:console.device DEVS:FileSystem.resource DEVS:misc.resource DEVS:potgo.resource DEVS:scsi.device L:FastFileSystem L:Ram-Handler L:Shell-Seg LIBS:dos.library LIBS:layers.library REVERSE NOREBOOT
SYS:C/SetPatch SKIPROMUPDATES console.device,dos,filesystem,FileSystem.resource,ram-handler,scsi.device,shell QUIET

C:Version >NIL:
C:AddBuffers >NIL: DF0: 15
FailAt 21

C:MakeDir RAM:T RAM:Clipboards RAM:ENV RAM:ENV/Sys
C:Copy >NIL: ENVARC: RAM:ENV ALL NOREQ

Resident >NIL: C:Assign PURE
Resident >NIL: C:Execute PURE

Assign >NIL: ENV: RAM:ENV
Assign >NIL: T: RAM:T
Assign >NIL: CLIPS: RAM:Clipboards
Assign >NIL: REXX: S:
Assign >NIL: PRINTERS: DEVS:Printers
Assign >NIL: KEYMAPS: DEVS:Keymaps
Assign >NIL: LOCALE: SYS:Locale
Assign >NIL: LIBS: SYS:Classes ADD
Assign >NIL: HELP: LOCALE:Help DEFER

BindDrivers
C:Mount >NIL: DEVS:DOSDrivers/~(#?.info)

C:LoadMonDrvs

;IF EXISTS DEVS:Monitors
;  IF EXISTS DEVS:Monitors/VGAOnly
;    DEVS:Monitors/VGAOnly
;  EndIF

;  C:List >NIL: DEVS:Monitors/~(#?.info|VGAOnly) TO T:M LFORMAT "DEVS:Monitors/%s"
;  Execute T:M
;  C:Delete >NIL: T:M
;EndIF

SetEnv Language "english"
SetEnv Workbench $Workbench
SetEnv Kickstart $Kickstart
UnSet Workbench
UnSet Kickstart

C:AddDataTypes REFRESH QUIET
C:IPrefs
C:ConClip

Path >NIL: RAM: C: SYS:Utilities SYS:Rexxc SYS:System S: SYS:Prefs SYS:WBStartup SYS:Tools SYS:Tools/Commodities

SYS:System/REXXMast >NIL:

SYS:C/MakeLink RAM:disk.info ENVARC:SYS/def_RAM.info SOFT

IF EXISTS S:User-Startup
  Execute S:User-Startup
EndIF

Resident Execute REMOVE
Resident Assign REMOVE

C:LoadWB
EndCLI >NIL:

[pVC]

SYS:C/MakeLink RAM:disk.info ENVARC:SYS/def_RAM.info SOFT

MakeLink command doesn't have SOFT option. (Edit: it does after the latest updates to 3.9, sorry)

Other more commonly used method is to copy the .info file instead of linking it:
Copy ENVARC:SYS/def_RAM.info RAM:disk.info

[Thomas]

MakeLink command doesn't have SOFT option.

Why do you say so? This is plain wrong. You *require* the SOFT option to make a link from one device to another. Hard links are only possible within one device.

The "not implemented" message obviously comes from RAM disk. Most likely the updated ram-handler was not installed or disabled. The older ram-handler indeed did not support links.

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

[carvedeye]

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?

That is what it says on mine? I'm have also tried it without SOFT and it still doesn't solve my problem? Its says I need the soft for it to work?

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

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

[carvedeye]

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.

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

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

[carvedeye]

@Matthey - do you have a link handy?

A link would be great. 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?

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