ContextMenus not in sync with Workbench menu

[JosDuchIt]

My OS4.1 Upd6 partition exists next to the new OS4.1FE partition
So the Icons i used to have on my WB when booting from Upd 6 wers still there when booting from OS4.1FEn, which was a big plus.

I remarked today that a shell icon left out form OS4Upd6:system:Shell and with default tool sys:System/Cli called the new shell indeed, again no poblem, to the contrary
Still before that i noticed this i was under the impression i was calling the olld shell and wanted to put away the icon.
To my surprise with contect menus the "put away" line was ghosted and "leave out" line was active.

Using the iWorkbench/Icons menu, the shell icon being selected, here the lines were as expected: "put away" active, "leave out" ghosted

[Petrol]

Hello,

You should looked at your boot priorities, because it seems you load the wrong kickstart!

regards

[JosDuchIt]

@petrol
i doubt that very much: i regularly change the boot priorities and am quite convinced i know from which partition i booted.
The WB title bar shows clearly when i work with OS4.1 FE or Upd6

[tonyw]

Isn't an icon that is "left out" done so with a soft link?

If so, then it will always point to the original place that you took it from, not the corresponding place on the new System partition.

(Sorry, that doesn't help)

The system may be booted from the highest priority partition, but that's not necessarily where the Kickstart was loaded from. It is always loaded from the first bootable partition on the disk.
To be sure, mark the old partition as "Not Bootable" in MTB.

[broadblues]

Something is indeed a bit inconsistant with the Context Menus leave out and put away menu items.


I dragged an (def)icon from out of the ram: disk onto the workbench.

Workbench offered me both the 'Leave Out' and 'Put Away' options (as it hadn't been left out as yet, just taken out temporarily).

Contextmenus however only offered the 'Put Away' option. (Possibly it can't tell the difference between a 'left out' whioch will persist for more than one session and a simpy teken out til the next reboot).

[broadblues]

It doesn#t appear to be exactly the issue you describe, but I raised a BZ on it anyway

[xenic]

Isn't an icon that is "left out" done so with a soft link?

No. The system creates a file on the current SYS: partition named " .backdrop " containing the path/name of the left out icon.

The system may be booted from the highest priority partition, but that's not necessarily where the Kickstart was loaded from. It is always loaded from the first bootable partition on the disk.

Not true. I have an Update6 partition on partition 8 of my hard disk. If I set the priority of that partition higher than all other bootable partitions (including the first bootable partition) and perform a hard reboot (reset), kickstart is loaded from the Update6 partition. I can confirm that by entering "version exec.library" in a shell. If the system booted from the Update6 partition, the exec version is 53.58 and if it booted from an FE partition the exec version is 53.70.

If you warm reboot (Ctrl-Amiga-Amiga), whatever kickstart was loaded during startup (turning system on) or cold reboot (reset) remains loaded but AmigaOS is loaded from the bootable partition with the highest priority or the partition you select in the AmigaOS early boot screen.

[JosDuchIt]

Anyway here i get
9.OS4.1FE:> echo $kickstart
53.70

and the problem noted is from a shell icon form OS4.1Upd6:System/Shell left out.
I note that it has a type i didn't encounter yet: "SingleIcon"
Maybe the problem has to do only with this typp

[nbache]

If you warm reboot (Ctrl-Amiga-Amiga), whatever kickstart was loaded during startup (turning system on) or cold reboot (reset) remains loaded but AmigaOS is loaded from the bootable partition with the highest priority or the partition you select in the AmigaOS early boot screen.

Or the partition defined in a BootDevice kickstart module for the current kicklayout. Read SYS:Documentation/Kickstart/bootmenu.doc, second section, for an easy way (for all NG AmigaOS platforms) to ensure you always boot the system corresponding to the loaded Kickstart.

Best regards,

Niels