Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Why does anyone bother to install Classic Shell on Windows if all they want is the WinXP accordion-style sliding cascade Start Menu?
33 views
Skip to first unread message
Arlen Holder
Oct 27, 2018, 4:08:51 PM10/27/18
to
Why does anyone bother to install Classic Shell on Windows if all they want
is the WinXP accordion-style sliding cascade Start Menu?
According to this link, the Classic Shell (in another name) survives:
<https://www.thewindowsclub.com/get-back-old-classic-start-menu-windows-10-classic-start>
Where I've always been confused why the "Classic Shell" (or now, "Classic
Start" exists, if, if, if, people are using it mainly to get back the WinXP
style cascade menus.
<http://www.bild.me/bild.php?file=2539943taskbar00.jpg>
I've used Classic Shell in the past, where I know it does _more_ than just
give you back your WinXP cascade sliding menu - but this sentence in your
reference is what confuses me:
"This software not only gives you back the old Windows Start menu..."
Huh?
The "old Windows Start Menu" never left Windows 10.
o The old Windows start menu is right there
o In your face
It's _exactly_ the same files!
(only in a different location)
o C:\ProgramData\Microsoft\Windows\Start Menu\Programs
(Mine is called "menu", not "Programs", but it's the exact same thing.)
o C:\ProgramData\Microsoft\Windows\Start Menu\menu
In fact, I literally *copied* my WinXP sliding start menu to the _native_
Windows 10 cascade accordion menu, & it (essentially) worked perfectly!
o Items cascade accordion style _exactly_ as WinXP menus did
o You add a shortcut to it with a simply right click on the shortcut
o You move them around while in the menu itself using the mouse
o Mine is called "menu" but it could as well have been called "Programs"
o It sits there on the task bar (OK, so it's not connected to the flag)
e.g., here is my _native_ WinXP cascade menu on Windows 10:
<http://www.bild.me/bild.php?file=2539943taskbar00.jpg>
Since those are the same folders & shortcuts copied over from WinXP, how is
_that_ Win10 accordion-style cascade menu any different than that of WinXP?
is the WinXP accordion-style sliding cascade Start Menu?
According to this link, the Classic Shell (in another name) survives:
<https://www.thewindowsclub.com/get-back-old-classic-start-menu-windows-10-classic-start>
Where I've always been confused why the "Classic Shell" (or now, "Classic
Start" exists, if, if, if, people are using it mainly to get back the WinXP
style cascade menus.
<http://www.bild.me/bild.php?file=2539943taskbar00.jpg>
I've used Classic Shell in the past, where I know it does _more_ than just
give you back your WinXP cascade sliding menu - but this sentence in your
reference is what confuses me:
"This software not only gives you back the old Windows Start menu..."
Huh?
The "old Windows Start Menu" never left Windows 10.
o The old Windows start menu is right there
o In your face
It's _exactly_ the same files!
(only in a different location)
o C:\ProgramData\Microsoft\Windows\Start Menu\Programs
(Mine is called "menu", not "Programs", but it's the exact same thing.)
o C:\ProgramData\Microsoft\Windows\Start Menu\menu
In fact, I literally *copied* my WinXP sliding start menu to the _native_
Windows 10 cascade accordion menu, & it (essentially) worked perfectly!
o Items cascade accordion style _exactly_ as WinXP menus did
o You add a shortcut to it with a simply right click on the shortcut
o You move them around while in the menu itself using the mouse
o Mine is called "menu" but it could as well have been called "Programs"
o It sits there on the task bar (OK, so it's not connected to the flag)
e.g., here is my _native_ WinXP cascade menu on Windows 10:
<http://www.bild.me/bild.php?file=2539943taskbar00.jpg>
Since those are the same folders & shortcuts copied over from WinXP, how is
_that_ Win10 accordion-style cascade menu any different than that of WinXP?
Arlen Holder
Oct 27, 2018, 4:09:11 PM10/27/18
to
R.Wieser
Oct 27, 2018, 4:25:52 PM10/27/18
to
> Why does anyone bother to install Classic Shell on Windows
> if all they want is the WinXP accordion-style sliding cascade
> Start Menu?
Why does anyone persistently post stuff about Win10 in an XP oriented
> if all they want is the WinXP accordion-style sliding cascade
> Start Menu?
newsgroup ?
Or why the same persistent posting of opinions about what-and-how to use
into a newsgroup related to freeware ?
It doesn't make any sense.
And where the "if all they want is" people may be excused because they
simply do not know any better, the same cannot be said about you ....
Regards,
Rudy Wieser
Jenny Telia
Oct 27, 2018, 7:57:44 PM10/27/18
to
greatly reduced.
😉 Good Guy 😉
Oct 27, 2018, 8:14:08 PM10/27/18
to
On 28/10/2018 00:57, Jenny Telia wrote:
Can I suggest you block poster 'Arlen Holder'? Your annoyance will be greatly reduced.
I have done it many times but that paedophile keeps changing his
identity. The change is subtle but a computer can recognize the
change easily.
You seem to like him. Are you a paid up member of his sex ring?  That weasel chap used to be a member but it seems that he was kicked out from it.
They are running a sex ring which specialises in abusing young boys.
I have removed the Windows 10 newsgroup from this posting because it has nothing to do with Windows 10.
You seem to like him. Are you a paid up member of his sex ring?  That weasel chap used to be a member but it seems that he was kicked out from it.
They are running a sex ring which specialises in abusing young boys.
I have removed the Windows 10 newsgroup from this posting because it has nothing to do with Windows 10.
--
With over 950 million
devices now running Windows 10, customer satisfaction is
higher than any previous version of windows.
Arlen Holder
Oct 27, 2018, 10:42:35 PM10/27/18
to
On Sat, 27 Oct 2018 22:25:43 +0200, R.Wieser wrote:
> Why does anyone persistently post stuff about Win10 in an XP oriented
> newsgroup ?
Hi Rudy Wieser,
> Why does anyone persistently post stuff about Win10 in an XP oriented
> newsgroup ?
One difference between you and me, is that I _add value_ for all.
In fact, I add a _lot_ of unique value to our overall tribal knowledge.
You and I know each other, so please allow me to be blunt with you.
Particularly since you can't add any on-topic value to any conversation.
I don't know if you understand Windows XP cascade menus; but I think I do.
Here is, for example, my Windows XP cascade menu snapped just now for you.
<http://www.bild.me/bild.php?file=8115171winxp_menu_example01.jpg>
That Windows XP menu was made, oh, I don't know, ten years ago (or more)?
Notice anything similar to this Windows 10 cascade menu snapped today?
<http://www.bild.me/bild.php?file=2539943taskbar00.jpg>
(Ignore the other menus - just look at the Win10 cascade accordion menu.)
Notice anything similar?
No?
You don't notice anything similar?
Really?
Nothing?
Well, they're (essentially) the same.
Do you realize WHY WinXP & Win10 menus are essentially the same, Rudy?
No?
Really?
Do you realize, that what you do on WinXP is what you do on Win10, Rudy?
And, do you realize, Rudy, that the cascade menu is just a folder tree?
Do you realize that Rudy? Or not?
If you do realize that, Rudy, then you realize, instantly, what that means.
*What that means is that your WinXP menu will work on Win10.*
*Literally, you can _copy_ WinXP menus to Win10 - and they work just fine!*
Now, I know you're a genius, Rudy, so _you_ (of course) knew all this.
But did _everyone_ on this newsgroup know it was _that_ easy?
I mean, how many people know WinXP menus work out of the box on Win10?
You literally _copy_ the WinXP menu
FROM: WinXP C:\Documents & Settings\All Users\Start Menu\Programs
TO: Win10 C:\ProgramData\Microsoft\Windows\Start Menu\Programs
Notice you literally copy the menu from any one WinXP machine to any other
Win10 machine, and the menus work perfectly! (assuming an intelligent user)
Actually, in my case, since my menu is named "menu", I literally copy
FROM: WinXP C:\Documents & Settings\All Users\Start Menu\menu
TO: Win10 C:\ProgramData\Microsoft\Windows\Start Menu\menu
But, I hope you don't wish to quibble over minor semantic details.
I realize you, Rudy, are a genius so you see the inherent brilliance.
But many people aren't as intelligent as you think you are Rudy.
Those people might not yet see the inherent beuty of these facts.
Those people, Rudy, might even think to use the "Classic Menu".
They do this, it is said, to "get back" the WinXP menus on Win10?
But, those WinXP menus are _already_ there on Win10.
So why do people install the Classic Shell to get WinXP style menus?
Why?
I don't know why.
That's why I asked the question.
Do you know why?
R.Wieser
Oct 28, 2018, 2:48:18 AM10/28/18
to
Jenny,
> Can I suggest you block poster 'Arlen Holder'? Your annoyance will
> be greatly reduced.
I do.
That is, I see his thread-starting post, and than set the whole thing to
ignore. Than I see nothing anymore, unless its a direct reply to one of my
own posts.
Its like ignoring a pickpocket: When you do that newcomers to the "picknic"
(as he likes to call it) won't know who to be weary of. Keeping a bit of a
spotlight on such a person will attent such newcomers that something is off,
and possibly won't be victimized.
And who knows, maybe I'm annoying him enough to see the light and reconsider
his ways. I won't be holding my breath for that though. :-)
Regards,
Rudy Wieser
> Can I suggest you block poster 'Arlen Holder'? Your annoyance will
> be greatly reduced.
That is, I see his thread-starting post, and than set the whole thing to
ignore. Than I see nothing anymore, unless its a direct reply to one of my
own posts.
Its like ignoring a pickpocket: When you do that newcomers to the "picknic"
(as he likes to call it) won't know who to be weary of. Keeping a bit of a
spotlight on such a person will attent such newcomers that something is off,
and possibly won't be victimized.
And who knows, maybe I'm annoying him enough to see the light and reconsider
his ways. I won't be holding my breath for that though. :-)
Regards,
Rudy Wieser
Mayayana
Oct 28, 2018, 8:41:13 AM10/28/18
to
"R.Wieser" <add...@not.available> wrote
| > Can I suggest you block poster 'Arlen Holder'? Your annoyance will
| > be greatly reduced.
|
| I do.
|
Just put him in the blocked senders list. But
you might have to update that occasionally.
He sometimes changes his name and/or email
address.
| And who knows, maybe I'm annoying him
| enough to see the light and reconsider
| his ways.
Not a chance. You can't resist having the last
word. He can't resist holding forth. Anything you
write serves as an excuse for him. It's a deadly
combination. :)
| > Can I suggest you block poster 'Arlen Holder'? Your annoyance will
| > be greatly reduced.
|
| I do.
|
you might have to update that occasionally.
He sometimes changes his name and/or email
address.
| And who knows, maybe I'm annoying him
| enough to see the light and reconsider
| his ways.
word. He can't resist holding forth. Anything you
write serves as an excuse for him. It's a deadly
combination. :)
R.Wieser
Oct 28, 2018, 9:07:54 AM10/28/18
to
Mayayana,
> | And who knows, maybe I'm annoying him
> | enough to see the light and reconsider
> | his ways.
>
> Not a chance.
True. Thats why I won't be holding my breath.
> You can't resist having the last word.
Against him ? Not a chance.
> He can't resist holding forth.
I currently care about as much to what he has to say as he cares about any
other stance than his own. I saw that he responded to my post, but could
not be arsed to read it.
> It's a deadly combination. :)
I became aware of that (reading and responding took a bit too much outof
me), which is why I can't be arsed anymore. :-)
Regards,
Rudy Wieser
> | And who knows, maybe I'm annoying him
> | enough to see the light and reconsider
> | his ways.
>
> Not a chance.
> You can't resist having the last word.
> He can't resist holding forth.
other stance than his own. I saw that he responded to my post, but could
not be arsed to read it.
> It's a deadly combination. :)
me), which is why I can't be arsed anymore. :-)
Regards,
Rudy Wieser
Arlen Holder
Oct 28, 2018, 10:22:57 AM10/28/18
to
On Sun, 28 Oct 2018 08:40:21 -0400, Mayayana wrote:
> Just put him in the blocked senders list.
Mayayana,
> Just put him in the blocked senders list.
The solution I propose is arguably so brilliant, as to be misunderstood.
Hence, this thread is perfectly valid for the newsgroups it's posted in.
Even more so, this thread provides unique technical value.
o The thread asks a valid question of why people use the Classic Shell
o The thread provides a brilliant solution showing it's not needed
Rudy's concern was that he was ignorant of WinXP expertise involved
o The brilliant solution starts with organizing your WinXP menus
o Which then move over perfectly as a _copy_ to Win10
Jenny Telia and you, Mayayana, added _zero_ technical value.
(Likely neither of you even _comprehended_ the brilliant solution.)
The fact is that there is no need for the Classic Shell
(if the person is attempting to gain back the WinXP cascaded menu).
The fact is that the WinXP cascaded menu works _perfectly_ on Win10.
The fact is that you can literally _copy_ the menu from XP to Win10!
And it works!
The fact is that extremely few people know of the brilliant solution.
Apparently you _hate_ that fact.
But that doesn't change that it's a fact nonetheless.
Personally, I'm incredulous when WinXP/WIn10 users are ignorant of this.
To me, it's _obvious_ that Win10 uses the _same_ cascade as does WinXP.
If you're intelligent about it - the menu copies over & just works.
Hence, it's a valid question of why people bother with Classic Shell
(if what they want are their WinXP cascade menus).
Why?
I don't know why?
I assume they're ignorant of the brilliant solution I use & propose.
At least my posts add _value_ (since this solution is brilliant).
--
It may be so brilliant that most people can't seem to understand it.
Arlen Holder
Oct 28, 2018, 1:02:23 PM10/28/18
to
On Sun, 28 Oct 2018 14:22:54 -0000 (UTC), Arlen Holder wrote:
> Rudy's concern was that he was ignorant of WinXP expertise involved
> o The brilliant solution starts with organizing your WinXP menus
> o Which then move over perfectly as a _copy_ to Win10
I realize there are quite a few morons on this newsgroup who won't
> Rudy's concern was that he was ignorant of WinXP expertise involved
> o The brilliant solution starts with organizing your WinXP menus
> o Which then move over perfectly as a _copy_ to Win10
correctly comprehend what I wrote, so I clarify that WinXP is NOT needed
(which is the only part that Rudy Wieser comprehended) for this brilliant
solution to work on Windows 10.
You can just as well _start_ with the WinXP-style classic menus on native
Windows 10 - but my point is that you don't have to start with Win 10.
You can start with the first Windows operating system that had the classic
cascade accordion-style menu.
The brilliant solution is so simple that it "just works" when you port from
Windows XP to Windows 10 - so that's why I mention that it "starts" with
Windows XP.
o My WinXP menus, when copied over to Win10, just work (almost perfectly).
o Your WinXP menus will likely _not_ work (but that's the whole point!).
If you _organized_ your Windows XP well, it _would_ work!
And even if you didn't, it works just fine if you _start_ with Windows 10!
that's the sheer brilliance of this idea.
Alas, brilliance is, I'm sure, not comprehended by most of you.
In fact, the sad fact could be that it could be that not a single person
reading this thread even _comprehends_ the sheer beauty and elegance of the
solution I propose.
I think only 1 out of 1,000 people even comprehended the solution.
Am I correct?
*Did _any_ of you comprehend the solution I proposed?*
HINT: It has pros and cons just like every solution has.
Arlen Holder
Oct 28, 2018, 8:09:56 PM10/28/18
to
On Sun, 28 Oct 2018 15:41:52 -0500, Zaghadka wrote:
> Yes. It's butt-ugly. Some of us have aesthetic preferences.
It seems that you're the first person to post who _comprehended_ what I
wrote, where, I agree with you (if I correctly understood you) that...
o WinXP accordion style menus are "butt ugly" compared to Win10 tiles
While WinXP accordion style menus are butt-ugly compared to Win10 tiled
menus, the fact is that a _lot_ of people add the Classic Shell _just_ to
get those butt-ugly WinXP accordion style menus.
And, they're far easier, in the long run, to manage than the tiles, since
the WinXP-style accordion cascade menu is managed easily in the Windows
file explorer or in the menu itself (just like WinXP managed it).
In addition, _nothing_ in what I wrote precludes the user using also or
either Win10 tile menu (aka the right side or orthodox Win10 menu system),
or the Win10 alphabetical menu (aka the left side or heterodox Win10 menu
system).
All three Win10 menus work well together:
o Win10 tiled menu (right side, aka orthodox menu)
%HOMEPATH%\AppData\Local\TileDataLayer\Database\vedatamodel.edb
o Win10 alphabetical menu (left side, aka heterodox menu)
%programdata%\Microsoft\Windows\Start Menu\Programs\ (global)
%appdata%\Microsoft\Windows\Start Menu\Programs\ (user)
o Win10 cascade menu (accordion style, aka winxp-style menu)
> your start shortcuts. Easy peasy.
Exactly. You're the _first_ person in this thread to acknowledge how easy
it is to add WinXP-style cascade accordion menus to Windows 10, without
adding the Classic Shell.
Hence my question ... why do pepole bother with the Classic Shell if all
they want to gain are WinXP style cascade accordion menus?
> Your solution has nothing to do with XP. You could pin a folder to the
> taskbar back when Windows 98 came out. So basically, every OS since 98
> (original) could do this.
You are correct in that the final solution on Windows 10 doesn't need
Windows XP - but my point with XP is that if you create your Windows XP
menus well, they _exactly_ copy over and work fine on Windows 10!
Everything is exactly the same (if you're intelligent about it).
These are my WinXP menus, for example:
<http://www.bild.me/bild.php?file=8115171winxp_menu_example01.jpg>
The point with XP is that if you are intelligent about it on WinXP, then a
simple copy of those exact same WinXP files works on Windows 10!
For me it worked perfectly since I was intelligent about it on XP.
If you're not intelligent about it on XP, it won't work perfectly on Win10.
That's the reason why it matters, with XP.
You have to think when you're on XP since XP comes first.
> Yes. It's butt-ugly. Some of us have aesthetic preferences.
It seems that you're the first person to post who _comprehended_ what I
wrote, where, I agree with you (if I correctly understood you) that...
o WinXP accordion style menus are "butt ugly" compared to Win10 tiles
While WinXP accordion style menus are butt-ugly compared to Win10 tiled
menus, the fact is that a _lot_ of people add the Classic Shell _just_ to
get those butt-ugly WinXP accordion style menus.
And, they're far easier, in the long run, to manage than the tiles, since
the WinXP-style accordion cascade menu is managed easily in the Windows
file explorer or in the menu itself (just like WinXP managed it).
In addition, _nothing_ in what I wrote precludes the user using also or
either Win10 tile menu (aka the right side or orthodox Win10 menu system),
or the Win10 alphabetical menu (aka the left side or heterodox Win10 menu
system).
All three Win10 menus work well together:
o Win10 tiled menu (right side, aka orthodox menu)
%HOMEPATH%\AppData\Local\TileDataLayer\Database\vedatamodel.edb
o Win10 alphabetical menu (left side, aka heterodox menu)
%programdata%\Microsoft\Windows\Start Menu\Programs\ (global)
%appdata%\Microsoft\Windows\Start Menu\Programs\ (user)
o Win10 cascade menu (accordion style, aka winxp-style menu)
C:\ProgramData\Microsoft\Windows\Start Menu\menu
> But you could always put a folder on the taskbar, and that folder can be
> your start shortcuts. Easy peasy.
Exactly. You're the _first_ person in this thread to acknowledge how easy
it is to add WinXP-style cascade accordion menus to Windows 10, without
adding the Classic Shell.
Hence my question ... why do pepole bother with the Classic Shell if all
they want to gain are WinXP style cascade accordion menus?
> Your solution has nothing to do with XP. You could pin a folder to the
> taskbar back when Windows 98 came out. So basically, every OS since 98
> (original) could do this.
You are correct in that the final solution on Windows 10 doesn't need
Windows XP - but my point with XP is that if you create your Windows XP
menus well, they _exactly_ copy over and work fine on Windows 10!
Everything is exactly the same (if you're intelligent about it).
These are my WinXP menus, for example:
<http://www.bild.me/bild.php?file=8115171winxp_menu_example01.jpg>
The point with XP is that if you are intelligent about it on WinXP, then a
simple copy of those exact same WinXP files works on Windows 10!
For me it worked perfectly since I was intelligent about it on XP.
If you're not intelligent about it on XP, it won't work perfectly on Win10.
That's the reason why it matters, with XP.
You have to think when you're on XP since XP comes first.
Big Bad Bob
Oct 29, 2018, 4:00:05 AM10/29/18
to
On 10/27/18 13:08, Arlen Holder wrote:
> Why does anyone bother to install Classic Shell on Windows if all they want
> is the WinXP accordion-style sliding cascade Start Menu?
Because the *BULLSHIT* Win-10-nic "Start Thing" is SO FUCKED UP!!!
> Why does anyone bother to install Classic Shell on Windows if all they want
> is the WinXP accordion-style sliding cascade Start Menu?
Tiles *FUCKING* *SUCK* and the ALWAYS ALPHABETIZED "slurp-ing" ADWARE
HORSE MANURE 'all CRapps' is FUCKED UP too!!!
> The "old Windows Start Menu" never left Windows 10.
and the 2D FUCKING FLATSO *SUCKS* too!
Roger Blake
Oct 29, 2018, 7:15:05 PM10/29/18
to
On 2018-10-27, Arlen Holder <a%rlenh...@no.spam.net> wrote:
> Why does anyone bother to install Classic Shell on Windows if all they want
> is the WinXP accordion-style sliding cascade Start Menu?
Sheer laziness - it's quick and easy. My use case is typically working
> Why does anyone bother to install Classic Shell on Windows if all they want
> is the WinXP accordion-style sliding cascade Start Menu?
on others' PCs where I just want a sane environment. (The typical user
I work with doesn't even know how to use the start menu. If it's not on
the desktop then as far as they are concerned it doesn't exist.)
Installing Classic Shell when I go to work on a new PC is a quick
download and takes just seconds to install.
--
-----------------------------------------------------------------------------
Roger Blake (Posts from Google Groups killfiled due to excess spam.)
NSA sedition and treason -- http://www.DeathToNSAthugs.com
Don't talk to cops! -- http://www.DontTalkToCops.com
Badges don't grant extra rights -- http://www.CopBlock.org
-----------------------------------------------------------------------------
Arlen Holder
Oct 29, 2018, 8:36:33 PM10/29/18
to
On Mon, 29 Oct 2018 23:15:01 -0000 (UTC), Roger Blake wrote:
> Sheer laziness - it's quick and easy. My use case is typically working
> on others' PCs where I just want a sane environment. (The typical user
> I work with doesn't even know how to use the start menu. If it's not on
> the desktop then as far as they are concerned it doesn't exist.)
>
> Installing Classic Shell when I go to work on a new PC is a quick
> download and takes just seconds to install.
That makes sense that installing Classic Shell is _easier_ than anything
> Sheer laziness - it's quick and easy. My use case is typically working
> on others' PCs where I just want a sane environment. (The typical user
> I work with doesn't even know how to use the start menu. If it's not on
> the desktop then as far as they are concerned it doesn't exist.)
>
> Installing Classic Shell when I go to work on a new PC is a quick
> download and takes just seconds to install.
else. I agree.
Arlen Holder
Oct 29, 2018, 8:37:58 PM10/29/18
to
On Mon, 29 Oct 2018 00:59:58 -0700, Big Bad Bob wrote:
> Because the *BULLSHIT* Win-10-nic "Start Thing" is SO FUCKED UP!!!
> Tiles *FUCKING* *SUCK* and the ALWAYS ALPHABETIZED "slurp-ing" ADWARE
> HORSE MANURE 'all CRapps' is FUCKED UP too!!!
>
>> The "old Windows Start Menu" never left Windows 10.
>
> BULL-FUCKING-SHIT!
>
> and the 2D FUCKING FLATSO *SUCKS* too!
That's what I also had thought, which, I admit, I first added the Classic
> Because the *BULLSHIT* Win-10-nic "Start Thing" is SO FUCKED UP!!!
> Tiles *FUCKING* *SUCK* and the ALWAYS ALPHABETIZED "slurp-ing" ADWARE
> HORSE MANURE 'all CRapps' is FUCKED UP too!!!
>
>> The "old Windows Start Menu" never left Windows 10.
>
> BULL-FUCKING-SHIT!
>
> and the 2D FUCKING FLATSO *SUCKS* too!
Start menu when the eldest grand kid went off to college and we had to buy
our very first Windows laptop as a gift for him.
I started to set it up, where I was *appalled* at the tiled interface.
Since it was brand new, we called up Dell who logged into the laptop and
added the Classic Shell.
At the time, and still now, it was a _shock_ to me that Microsoft would
even think to remove the cascade style accordion start menu.
There was _nothing wrong_ with that cascade style accordion menu!
Sure, it's not easily "touch screened", but it is wonderful to mice!
To this day, I don't understand why they had ditched the cascade menu.
I suspect they wanted to "look" different, without being different.
There's are only about 10 things in Win10 that you can't do in any or all
of the previous releases (e.g., DirectX 11), where none are important to
most people.
The secret on Windows XP still works with Windows 10 though.
1. Organize your shortcuts in the way your mind thinks
2. Create a _separate_ cascade menu from the default "Programs" menu
3. As you add/remove programs, manage that _separate_ cascade menu
That's it.
If you do that, all your cascade menus are _portable_ across machines!
As I've proven, these menus are even portable across operating systems!
Arlen_Holder
Oct 31, 2018, 7:18:11 PM10/31/18
to
On Wed, 31 Oct 2018 01:04:37 -0700, John Corliss wrote:
> I didn't see the OP for whatever reason, but in response I want to say
> that I like Classic Shell in Windows 7 at least because it adds back
> toolbar configurability to Windows Explorer. I also still like the WinXP
> classic style Start Menu and it's easy drag and drop configurability.
> Don't know if CS gets around the newer Windows 10 limitation on the
> number of items you can list in the Start Menu (last I heard it was 512,
> but I could be wrong), but then I don't use W10. If I did, I doubt that
> my >600 Start Menu items (all neatly categorized and organized) would be
> compatible with W10. My Start Menu has evolved over decades of computer
> use and yes, there's nothing there that isn't there for a reason.
>
> Unfortunately, Classic Shell is no longer being developed:
>
> http://www.classicshell.net/forum/viewtopic.php?f=4&t=8147
On Wed, 31 Oct 2018 01:04:37 -0700, John Corliss wrote:
> I also still like the WinXP
> classic style Start Menu and it's easy drag and drop configurability.
So that I always add value, I post this well-researched response, which
_proves_ there never was a need for the Classic Shell ... if ... if WinXP
style accordion cascade menus are what the user wants on Win10.
If _that_ is all one wants, then they _already_ have it on W1in10 native!
<http://www.bild.me/bild.php?file=2796904winxp_menu_on_win10.jpg>
The native Win10 method of gaining the XP-style cascade menu...
o Adds back the "missing" WinXP accordion-style cascade menu
o With the _same_ drag-&-drop configurability
o And with _added_ ease of right-click send-to population
<http://www.bild.me/bild.php?file=2635699winxp_menus_on_win10.jpg>
> Don't know if CS gets around the newer Windows 10 limitation on the
> number of items you can list in the Start Menu (last I heard it was 512,
> but I could be wrong), but then I don't use W10.
Windows 10 has _multiple_ native start menus only 1 of which is so limited:
o There is the left-side (alphabetical, aka heterodox) Start Menu
o There is the right-side (tiled, aka orthodox) Start Menu
o There is the cascade menu (aka WinXP-style) Start Menu
The menu you speak of is actually a binary file, as Paul is aware:
> If I did, I doubt that
> my >600 Start Menu items (all neatly categorized and organized) would be
> compatible with W10. My Start Menu has evolved over decades of computer
> use and yes, there's nothing there that isn't there for a reason.
Based on that statement, I don't think you understand that Windows 10
_already_ has _exactly_ the same menu that you have on XP.
In fact, if you merge user & global, you can literally _copy_ the WinXP
menu hierarchy over to Windows 10 and it will work perfectly.
I've literally copied the WinXP start menu folder hierarchy over to _many_
Windows 10 machines, and it works (almost) perfectly!
The only difference is that, over time, I've honed my hierarchy, from this:
To this:
So minor (easily done with drag and drop) changes were required.
> Unfortunately, Classic Shell is no longer being developed:
> http://www.classicshell.net/forum/viewtopic.php?f=4&t=8147
If all you wanted was WinXP menus on Win10, then Classic Shell was never
needed since WinXP menus work perfectly on Windows 10 (and always did).
These WinXP menus literally copy directly over (and work!) to Win10!
<http://www.bild.me/bild.php?file=5364242winxp_menu_example01.jpg>
Here the WinXP cascade menu is working just fine, on Windows 10!
<http://www.bild.me/bild.php?file=2635699winxp_menus_on_win10.jpg>
> I didn't see the OP for whatever reason, but in response I want to say
> that I like Classic Shell in Windows 7 at least because it adds back
> toolbar configurability to Windows Explorer. I also still like the WinXP
> classic style Start Menu and it's easy drag and drop configurability.
> Don't know if CS gets around the newer Windows 10 limitation on the
> number of items you can list in the Start Menu (last I heard it was 512,
> but I could be wrong), but then I don't use W10. If I did, I doubt that
> my >600 Start Menu items (all neatly categorized and organized) would be
> compatible with W10. My Start Menu has evolved over decades of computer
> use and yes, there's nothing there that isn't there for a reason.
>
> Unfortunately, Classic Shell is no longer being developed:
>
> http://www.classicshell.net/forum/viewtopic.php?f=4&t=8147
On Wed, 31 Oct 2018 01:04:37 -0700, John Corliss wrote:
> I also still like the WinXP
> classic style Start Menu and it's easy drag and drop configurability.
So that I always add value, I post this well-researched response, which
_proves_ there never was a need for the Classic Shell ... if ... if WinXP
style accordion cascade menus are what the user wants on Win10.
If _that_ is all one wants, then they _already_ have it on W1in10 native!
<http://www.bild.me/bild.php?file=2796904winxp_menu_on_win10.jpg>
The native Win10 method of gaining the XP-style cascade menu...
o Adds back the "missing" WinXP accordion-style cascade menu
o With the _same_ drag-&-drop configurability
o And with _added_ ease of right-click send-to population
<http://www.bild.me/bild.php?file=2635699winxp_menus_on_win10.jpg>
> Don't know if CS gets around the newer Windows 10 limitation on the
> number of items you can list in the Start Menu (last I heard it was 512,
> but I could be wrong), but then I don't use W10.
Windows 10 has _multiple_ native start menus only 1 of which is so limited:
o There is the left-side (alphabetical, aka heterodox) Start Menu
o There is the right-side (tiled, aka orthodox) Start Menu
o There is the cascade menu (aka WinXP-style) Start Menu
The menu you speak of is actually a binary file, as Paul is aware:
> If I did, I doubt that
> my >600 Start Menu items (all neatly categorized and organized) would be
> compatible with W10. My Start Menu has evolved over decades of computer
> use and yes, there's nothing there that isn't there for a reason.
Based on that statement, I don't think you understand that Windows 10
_already_ has _exactly_ the same menu that you have on XP.
In fact, if you merge user & global, you can literally _copy_ the WinXP
menu hierarchy over to Windows 10 and it will work perfectly.
I've literally copied the WinXP start menu folder hierarchy over to _many_
Windows 10 machines, and it works (almost) perfectly!
The only difference is that, over time, I've honed my hierarchy, from this:
To this:
So minor (easily done with drag and drop) changes were required.
> Unfortunately, Classic Shell is no longer being developed:
> http://www.classicshell.net/forum/viewtopic.php?f=4&t=8147
If all you wanted was WinXP menus on Win10, then Classic Shell was never
needed since WinXP menus work perfectly on Windows 10 (and always did).
These WinXP menus literally copy directly over (and work!) to Win10!
<http://www.bild.me/bild.php?file=5364242winxp_menu_example01.jpg>
Here the WinXP cascade menu is working just fine, on Windows 10!
<http://www.bild.me/bild.php?file=2635699winxp_menus_on_win10.jpg>
Arlen_Holder
Oct 31, 2018, 8:32:28 PM10/31/18
to
On Wed, 31 Oct 2018 23:18:08 -0000 (UTC), Arlen_Holder wrote:
> The only difference is that, over time, I've honed my hierarchy, from this:
> To this:
Ops. I forgot to include the screenhosts from Win10 and WinXP.
> The only difference is that, over time, I've honed my hierarchy, from this:
> To this:
The WinXP start menu works on Win10 simply by copying it over.
The only difference is that, over time, I've honed my hierarchy, from this:
To this:
<http://www.bild.me/bild.php?file=2635699winxp_menus_on_win10.jpg>
Where even the actual WinXP program shortcuts work perfectly on Win10!
It's so easy, it's no wonder some can't comprehend the sheer brilliance of
such a simple and effective solution.
0 new messages