thanatoid wrote in
:

Just to be clear, I'm only talking about the Start Menu
shortcuts that one uses to access the program, and NOT
where the program itself is actually installed (i.e. in
Program Files - and some also use the user
nameApplications subdirectory, too).

It was clear. I have the program files, "utils", and a few
things in SYS and REF(erence). I have been toying with the idea
of putting sys, ref and utils on another partition since they
really do not need to be in the Acronis images, and DO take up
space in them. I already have several virtual (reference and
Doonesbury) CD's on other partitions.


Organising stuff is awkward no matter hopw we do it. I didn't have trouble
with the main menu, so long as I keep it small. Currently three main
branches, all with few entries, Editors, Key-Switch, and Storage. Editors for
those I reach for a lot, KEy-Switch for the few things that also have
dedicated global shortcuts for, like a task manager to reach for in
emergencies. The menu entries are in case I forget the shortcut, and to
rememind me where to look for any possible shortcut conflicts. Storage is
WInRAR, WinImage and UltraISO and such.

A lot of the time I don't use shortcuts at all! I just use file associations
and if I don't like icons or think they're unclear of ambigous, I make my own
and hack them into a program if needed. (That's more reliable than externals
with registry DefaultIcon links and avoids having loose icon files, but those
are great for anyone who prefers not to change a program file).

I organise the same way I do for electronic and mechanical parts. There's no
perfect pattern so ANY fairly consistent pattern is enough. I like to reach
things directly, symbols that point to stuff aren't stuff, so I try to avoid
them except where they have large and simple effects. One I found useful at
times was directories in one location, named Active, Dormant, Incoming,
Outgoing. Maybe a fifth, EMERGENCY, which alphabetically places itself
centred dividing the other four into useful pairings. They'd always be in
same order, and so long as no other directories were there, this is a great
fast way to get at stuff, but it's limited, it only works in situations where
a person MUST always be on top of what stuff is active, dormant, etc.. In the
line of constant work this stays good, but otherwise it can get messy.

So mostly I use file associations. I don't need to know where the program is
then, or have menu entries for it. I just need to know where my work is, go
there, open the file...

Small partitions for work data are vital, I find. That way the OS search
function can immediately find data or program files if my mind is fogged and
memory and habit won't quit fumbling and satisfy my impatience. This search
is more than a free ride for when I get tired in a long session, it's always
faster to have the computer find stuff unless we already know (in both mind
and motor memory) exactly where it is. For this reason a big menu is
pointless, it can often be worse than going to the actual directory the stuff
is in, so all my methods handle it on that basis.