Arlen,

You have a Subject line which doesn't match the first line of your tutorial.
Why now do I get the feeling that the "Killing users tasks" is something
that was added in a hurry ?

Also, its again not /tutoring/ - no clear reasons given for most steps.
Though you still leave it upto the person to make choices. And as there
are no clear reasons given, on what grounds should he make those ? This
also means that it won't work a "step plan".

[crossposted newsgroups]
The tutorial doesn't work for (MS)DOS, yet you crossposted it into there
too.

Your second paragraph (starting with "Given that, at least on mobile
devices") has nothing to do with Windows (or DOS). It has no place.

1. Create a shortcut named cclip.lnk (i.e., clean clipboard):

/How/ is the reader supposed to create a shortcut ? Or do you presume
he's just born with that knowledge ?

And if you think that he already knows that than what is the chance he also
knows how to select another icon and that he can pin it to the taskbar,
making your steps in that regard superfluous.

IOW, either you write as if he knows nothing, or you assume he already knows
everything. Mixing them is not a good idea (irritating to the guy who
already knows it, confusing the the person who doesn't)

Also, you mention that name as if it /must/ be that one, while both of us
know that any name will do (and its a bad name for something that kills
tasks too).

Use any hierarchy you like; I put mine in my system "Run" directory:

"Use any hierarchy you like" ? What is that supposed to mean ? Yeah, I
know what, in relation to filesystems, a hierarchy is. What makes you
think that a novice knows what you mean there ? What is he supposed to
/do/ ?

"I put mine in my system "Run" directory:" I think the Windows term is
"folder", not "directory". And what should someone do when he doesn't
have that folder ? You make no mention of that.

START IN: C:\Windows\system32

Irrelevant to the "clip" command (or anything in the below) and may be left
blank.

2. If desired, create a "cclip" command using the AppPaths key:

On which grounds should the novice make the "desired" choice ? You only
mention /a/ reason at the end. Actually, the /only/ reason you want/need
this to be done is because you prefer the "run" dialog way of starting
stuff...

3. If desired, set the link icon to something easily distuinguished.

Irrelevant if they use the, by you preferred, "run" dialog (they will never
see the icon anyway). If not that step 2. is irrelevant. No info about
that is provided either.

Worse: if they use the "run" dialog method there is no reason to create a
shortcut to begin with : a simple .BAT file (like the examples you included)
would be enough.

For example, I created this icon in a minute using Irfanview:

That does not belong there, as it only serves to confuse the novice "should
I first go do that" ? At best put it into a "remarks" section after the
tutorial itself has already concluded.

Than again, the whole step 2. belongs there ... Its inconsequential to the
functioning of the shortcut.

4. If desired, pin that icon to the taskbar for quick access.

So, /two/ ways to "quick access" it - with this one being quicker-and-easier
than Win-R ...

And by the way: You pin the /shortcut/, not the icon (doubt that you can do
the latter, but it will confuse the heck outof a novice trying to follow
your directions)

5. If desired, you can combine multiple commands as needed, e.g.,

Should also at best be in the "remarks" section, but preferrably in a
seperate "how to create a shortcut and do interresting stuff with it"
tutorial.

TARGET = %comspec% /c "echo off | clip" & veracrypt /dismount /force /q
& taskkill /f /fi "USERNAME eq %COMPUTERNAME%\%

Bad example, as only one the first of the three command parts has yet been
mentioned, and you spend zero in regard to an explanation to what the other
parts are for.

And yes, /I/ recognise that last part as being the "killing users' tasks"
that you mentioned in your subjectline. I wonder how many novices would be
able to do the same...

And that leaves the middle part, which is irrelevant to anything, and again
only serves to confuse the hapless novice who hasn't got any idea that it
may be removed.

tl;dr:

Your whole tutorial consists outof :

1) Create a shortcut

2) Set the "target:" to %comspec% /c "echo off | clip" & taskkill /f /fi
"USERNAME eq %COMPUTERNAME%\%USERNAME%" /IM *

Than there is a subsection describing ONE way (outof at least three that I
know of) to make the command work from withing the "run" dialog - where that
way is the only one that needs maintenace (the other two need none).

.... which can be fully skipped when the user rather clicks the shortcut (on
the taskbar or elsewhere)

The rest is fluff which has little-or-nothing to do with the subjectline.

And I have to ask : Why create a shortcut /at all/ when all *you* want to do
is to use the "run" dialog ? A simple batchfile would be way easier.

As always, please improve this nascent tutorial with purposefully
helpful suggestions so that everyone benefits from every action you
take on Usenet.

I think you have gotten enough "purposefully helpful suggestions" to be able
to improve upon it. :-) Go git.

Regards,
Rudy Wieser