
Signature
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)
[]
> It makes sense to group them. The Start Menu
> gets too long if you just let it grow with every new
[quoted text clipped - 5 lines]
> parent folders generated at installation for every
> separate app.
[]
Agreed - though doing it that way means the uninstall routine, should you
come to try to use it, doesn't know where they are, and leaves them (but
Start Menu Cleaner - or other app.s, but I like SMC as it's simple - will
find and prompt for their removal).
An alternative, provided the install routine allows (most, though not all,
do), is: do as Don suggests and make some generic ones (I have things like
netstuff, hardware, text.etc, images, ... - IIRR I also put a # or two
before them, which [a] shows they're mine [b] makes them come at the top, at
least in the shell I use), then when a new app. asks where to put its
shortcuts, suggesting something like
newapp
, I just stick my one before it, thus
netstuff\newapp
, which then puts it as a submenu under netstuff, and uninstall knows where
to find it. (If your generic names are too long to type easily, _copy_ [e.
g. Ctrl-C] the suggested new name, select your generic from the list shown,
type \ at its end, and paste [Ctrl-V] the new one.)
If you know the new app. is only going to make one shortcut, then I'd say
just override the suggested folder name with one of your existing ones - I
find single-entry submenus to the start menu somewhat irritating - but YMMV!