SWI Not known errors

It appears that there are three variants on a common system message:

NoSuchSWI1:SWI &%0 not known
NoSuchSWI2:SWI name not known
NoSuchSWI:SWI not known

I would claim that only NoSuchSWI1 is any real use, unless you are the developer who knows which SWI has been requested.

Please could all uses of NoSuchSWI and NoSuchSWI2 be investigated to see if there is any way to include either the name or number of the SWI that cannot be found?

For example, in the SWINumberFromString_Code Entry in Kernel.s.SWINaming it seems to me that when the label this_swi_nexiste_pas (!) is used, although it knows the name in r1 it uses the useless ‘SWI name not known’ message.

I am sure there are other similar examples, eg ‘File not found’ should give the name. I feel that many error messages were as short as possible due to memory constraints in older machinees, particularly when single-tasking meant that the user knew what was being run at the time. With today’s multi-tasking these messages suddenly popping up with no clue where from or why can cause lots of frustration.

G’day Martin,
I’m probably replying in an incorrect manner. Sorry about not replying sooner than this anyhow! I’m going to tinker about your suggestion concerning using *. fat32fs: AND *copy SDFS:$.Documents.Other $.Other AND *sdfs
When I get more familiar with using the human-based protocols, I’ll get back to you(?) or is it the forum? That depends on She-who-Needs-to-be-Obeyed and/or She-who-Must-be-Obeyed.

Richard, I am not sure what you are replying to … but it does not seem to be my post above?!