I was looking back, some of the quote tags didn't get posted correctly. That why I either use the name or nickname of the poster. This way they know who I am talking to. If I am talking to everyone I will say "All" or "Others" unless I post a new thread. I goof up some of the time by not saying who I am replying too.
As to the "we", for those pretending not to understand, the disparaging post I quoted was directed at those folks who rejected the start screen, and have retained their opinion that the start menu was, in fact, far far better, and that includes me, and many others. Chiming in that you did not understand that, is disingenuous at best.
Now I am . Are you saying you like the Window 10 start menu or don't like it? If, you like the start menu that fine with me, but there is a lot of people that don't which includes me. (For clarification, I don't like the windows 10 start menu). I admit there are a couple of nice features about the start menu that I do like, live titles and resizing titles. Actually as a disabled individual I do have trouble understanding really hard tech stuff.
Please read all of the thread. Some stated they changed the name, were able to get it to install, but then ran into problems with it. Here’s one. There’s another in some other thread....And indeed, once the program is installed by changing the name of the executable in Win10TP it runs without a problem.
Microsoft Blocks Classic Shell in Windows 10 Build 9879
Again > Where do you come up with this stuff?You'd think Microsoft would at least *test* a program before declaring that it is "incompatible," wouldn't you...?
LOL! You just posted this yesterday:
And even then you can't expect all legitimate programs to works with a preview version. The TP build is how they discover incompatibilities to be fixed, after all.
As for Classic Shell, there are 2 outstanding issues that caused it to be blocked:
1) The start menu messes with the taskbar and causes the new taskbar buttons to overlap with the programs. This is because the start menu relies on undocumented internal structure of the taskbar, which was changed between 8.1 and 10.
2) Upgrading from one version of Windows to 10TP breaks the start menu. There are multiple technical issues here that I don't want to get into.
I am working on a fix for both. There should be a new beta version of Classic Shell by Thanksgiving.
Folks when someone finds a program that doesn't at this time work with W-10 there are three things to do.
1. Post your problem here.
2. Post your problem in Windows 10 Feedback.
3. If you can inform the owners of the program.
That is the big three.
I'm not here to design W-10 or 3rd party programs. I'm here to give input so W-10 will hopefully be a great operating system.
I will let the owners of the 3rd party programs and Microsoft work out the problems between them.
I'm as sure as one can be their will be things about W-10 that I would like different. That to me doesn't make W-10 is a no go.
I will have to decide whether watching my favorite game of puppies dancing in the bathtub is more important than W-10 to me.
In the end that is a decision we will all make.
Microsoft is trying to make a operating system that the masses will like and buy.
If third party programs don't work with W-10 the owners will just have to adjust their program so it does.
Thanks for expounding on that, Ivo and Layback Bear.
I spent a mere $110 on a copy of 8, then 8.1 was a free upgrade. This was all on a six-year-old tower at the time which continues to purr along yet another two years later. MS saved me money by keeping the OS footprint small enough and backward compatible enough to use on older hardware. Saved me money. And yet 10 runs pretty well on it along with Office 2013 Pro.
To some > Compare that to a Mac with the latest OS X or even a new WinTel. Let me know how that goes.