Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: blakespot on November 05, 2019, 03:57:43 AM
-
I seem to recall the ALIAS command in AmigaDOS 1.3 and I see docs that reference it, yet it’s not in my 1.3 HD install on the A1000 or on any of the 1.3 Workbench disks I have. Did it not exist in 1.3??
bp
-
Just checked my nearest reference guide at hand. According to Sheldon Leemon's AmigaDOS Reference Guide 4th Edition, ALIAS is an internal shell command, so there won't be a disk-based file for it.
Tested it quickly in a 1.3 environment in FS-UAE and it works.
So go nuts setting up aliases on your 1.3 system! :)
-
I type ALIAS and get a Command Not Found. I put it in s/S-S and it errors out... Workbench 1.3 here. What gives?
Amiga 1000 w/ KS 1.3.
bp
-
I type ALIAS and get a Command Not Found. I put it in s/S-S and it errors out... Workbench 1.3 here. What gives?
The shell in 1.3 was disk-based, otherwise you just get the ROM-Shell which does not have alias. If I recall correctly:
resident CLI L:Shell-Seg System pure
should be part of the startup-sequence.
-
Right, but nowhere on any of my WB 1.3 disks do I see ALIAS in c/. So...what am I missing?
bp
-
It’s an internal command that’s part of L:shell-seg. If you’re in a shell after it’s been made resident as Thomas described, then ALIAS will be available.
I think it’s the same way CD, If, Else, etc. are internal in Kickstart 2+. Those commands aren’t stored directly in the ROM; they’re part of shell-seg, which itself is part of the ROM. The difference in 1.3 is that shell-seg is loaded into memory from disk instead of being automatically/instantly available from ROM.
-
Ok, well I have a s-s that boots off of floppy and then hands things off (assigns SYS: etc.) to the SCSI HD and loads from there (can eject the boot WB disk) on my Amiga 1000. I've noticed nothing else amiss, but I definitely don't have ALIAS working. So what am I missing from s-s to make the shell-seg resident? Thanks.
Odd.
bp
-
You have the command that Thomas posted in your startup-sequence?
-
You have the command that Thomas posted in your startup-sequence?
I might have missed the "Replace" option of the "resident" command.
-
Checked my 1.3 disk. It's
resident CLI L:Shell-Seg SYSTEM pure add(Thomas's line was missing the "add" argument)
Is the p (pure) bit set on your L:Shell-Seg file? I don't really understand how the pure bit works in relation to the Resident command, but I know there's some sort of relationship between the two. If you lost the pure bit, I wonder if the resident command would quietly fail. Thomas, I'm sure you could answer this ;)
-
Is the p (pure) bit set on your L:Shell-Seg file? I don't really understand how the pure bit works in relation to the Resident command, but I know there's some sort of relationship between the two. If you lost the pure bit, I wonder if the resident command would quietly fail. Thomas, I'm sure you could answer this ;)
The p bit: Well, it is a "sort of" security feature: If the bit is not set, "resident" will complain that the command (and this is what you typically make resident) is not pure. You can override this decision "yes, I really mean it" by the "pure" keyword.
-
I spent some time looking into this further. Basically, under 1.3, Alias works in a *shell* but not in a *cli*
In other words, launch a command line from the Shell icon in the root of the Workbench disk or from the newshell command and you'll have a functional Alias.
Launch a command line from the CLI icon in the System drawer or the newcli command and you won't.