A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Dirty Tricks?



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old November 13th 14, 02:14 PM posted to alt.comp.os.windows-10
Bob Henson[_2_]
external usenet poster
 
Posts: 695
Default Dirty Tricks?

Before anyone upgrades to build 9878, you should know that Microsoft
have fixed it to prevent Classic Shell from working - even in
compatibility mode. If, like me, that is a deal breaker then don't
upgrade. There may yet be a way to run it, but it needs something better
than I've tried so far.


--
If I only had a little humility, I'd be perfect.

Bob
Tetbury, Gloucestershire, UK
Ads
  #2  
Old November 13th 14, 02:42 PM posted to alt.comp.os.windows-10
Joel
external usenet poster
 
Posts: 25
Default Dirty Tricks?

"Bob Henson" escreveu na mensagem ...

Before anyone upgrades to build 9878, you should know that Microsoft
have fixed it to prevent Classic Shell from working - even in
compatibility mode. If, like me, that is a deal breaker then don't
upgrade. There may yet be a way to run it, but it needs something better
than I've tried so far.


If I only had a little humility, I'd be perfect.


Windows TP has its own start menu.

  #3  
Old November 13th 14, 02:56 PM posted to alt.comp.os.windows-10
Bob Henson[_2_]
external usenet poster
 
Posts: 695
Default Dirty Tricks?

On 13/11/2014 1:42 PM, Joel wrote:
"Bob Henson" escreveu na mensagem ...

Before anyone upgrades to build 9878, you should know that Microsoft
have fixed it to prevent Classic Shell from working - even in
compatibility mode. If, like me, that is a deal breaker then don't
upgrade. There may yet be a way to run it, but it needs something better
than I've tried so far.


If I only had a little humility, I'd be perfect.


Windows TP has its own start menu.


Not in any usable form for a desktop user. If there is a way to
configure it so that it only shows real programs rather than hiding them
at the end of the apps, and a way to hide the apps altogether, that fine
- but I haven't found it.

--
Bob
Tetbury, Gloucestershire, UK
If all seems to be going well, you obviously have no idea what is really
happening.
  #4  
Old November 13th 14, 03:35 PM posted to alt.comp.os.windows-10
Joel
external usenet poster
 
Posts: 25
Default Dirty Tricks?


"Bob Henson" escreveu na mensagem ...

Before anyone upgrades to build 9878, you should know that Microsoft
have fixed it to prevent Classic Shell from working - even in
compatibility mode. If, like me, that is a deal breaker then don't
upgrade. There may yet be a way to run it, but it needs something better
than I've tried so far.


If I only had a little humility, I'd be perfect.


On 13/11/2014 1:42 PM, Joel wrote:
Windows TP has its own start menu.

"Bob Henson" wrote in message ...
Not in any usable form for a desktop user. If there is a way to
configure it so that it only shows real programs rather than hiding them
at the end of the apps, and a way to hide the apps altogether, that fine
- but I haven't found it.


If all seems to be going well, you obviously have no idea what is really
happening.


Should be fine if start menu had drag 'n' drop. This is last windows. Then you
have to live real life.

  #5  
Old November 13th 14, 06:05 PM posted to alt.comp.os.windows-10
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default Dirty Tricks?

Bob Henson wrote:

Before anyone upgrades to build 9878, you should know that Microsoft
have fixed it to prevent Classic Shell from working - even in
compatibility mode. If, like me, that is a deal breaker then don't
upgrade. There may yet be a way to run it, but it needs something
better than I've tried so far.


Can you enable/disable the Program Compatibility Assistant (as you
could, say, in Windows 7) using the following instructions?

http://www.sevenforums.com/tutorials...e-disable.html
http://www.howtogeek.com/howto/4161/...s-7-and-vista/

Here's an example of someone that hit the same dialog in Windows 8
regarding Acronis TrueImage (a backup program):

http://superuser.com/questions/49960...t-in-windows-8

Obviously ClassicShell is not yet advertising they are compatible with a
tech preview (pre-release) of Windows. Most software vendors long ago
gave up trying to guess where Microsoft would go in a new version. They
were told things would be one way by Microsoft but found out after the
release that wasn't so. Software authors prefer the expense of just one
development cycle for a release of Windows. If you want compatibility
as designed by the developers then wait until Windows 10 is actually
released and until ClassicShell eventually announces compatibility with
Windows 10 released version.
  #6  
Old November 13th 14, 06:28 PM posted to alt.comp.os.windows-10
Bob Henson[_2_]
external usenet poster
 
Posts: 695
Default Dirty Tricks?

On 13/11/2014 5:05 PM, VanguardLH wrote:
Bob Henson wrote:

Before anyone upgrades to build 9878, you should know that Microsoft
have fixed it to prevent Classic Shell from working - even in
compatibility mode. If, like me, that is a deal breaker then don't
upgrade. There may yet be a way to run it, but it needs something
better than I've tried so far.


Can you enable/disable the Program Compatibility Assistant (as you
could, say, in Windows 7) using the following instructions?

http://www.sevenforums.com/tutorials...e-disable.html
http://www.howtogeek.com/howto/4161/...s-7-and-vista/

Here's an example of someone that hit the same dialog in Windows 8
regarding Acronis TrueImage (a backup program):

http://superuser.com/questions/49960...t-in-windows-8

Obviously ClassicShell is not yet advertising they are compatible with a
tech preview (pre-release) of Windows. Most software vendors long ago
gave up trying to guess where Microsoft would go in a new version. They
were told things would be one way by Microsoft but found out after the
release that wasn't so. Software authors prefer the expense of just one
development cycle for a release of Windows. If you want compatibility
as designed by the developers then wait until Windows 10 is actually
released and until ClassicShell eventually announces compatibility with
Windows 10 released version.


I realise the author of Classic Shell is not going to be writing for
Windows 10 for a long time yet. However, it worked perfectly all the way
through the change from Windows 7 to Windows 8 and Windows 8.1 and the
first two builds of Windows 10 - so I'm thinking that it has been
deliberately blocked by Microsoft if Windows 8 compatibility mode won't
work - which is doesn't. I'll have a look at the suggestions you posted,
but if that doesn't work I'll happily delete Windows 10. I don't think
Microsoft will be too concerned if yours truly is not giving them the
benefit of my wisdom any more :-) I'm never going to use it, I'm just
learning because folk will ask me questions about it in my volunteer
job. Thanks for the tips.

--
Bob
Tetbury, Gloucestershire, UK
Naturist - a person who prefers to go about naked, thus reminding others
why they prefer wearing clothes.
  #7  
Old November 13th 14, 06:51 PM posted to alt.comp.os.windows-10
Rene Lamontagne
external usenet poster
 
Posts: 2,549
Default Dirty Tricks?

On 11/13/2014 11:28 AM, Bob Henson wrote:
On 13/11/2014 5:05 PM, VanguardLH wrote:
Bob Henson wrote:

Before anyone upgrades to build 9878, you should know that Microsoft
have fixed it to prevent Classic Shell from working - even in
compatibility mode. If, like me, that is a deal breaker then don't
upgrade. There may yet be a way to run it, but it needs something
better than I've tried so far.


Can you enable/disable the Program Compatibility Assistant (as you
could, say, in Windows 7) using the following instructions?

http://www.sevenforums.com/tutorials...e-disable.html
http://www.howtogeek.com/howto/4161/...s-7-and-vista/

Here's an example of someone that hit the same dialog in Windows 8
regarding Acronis TrueImage (a backup program):

http://superuser.com/questions/49960...t-in-windows-8

Obviously ClassicShell is not yet advertising they are compatible with a
tech preview (pre-release) of Windows. Most software vendors long ago
gave up trying to guess where Microsoft would go in a new version. They
were told things would be one way by Microsoft but found out after the
release that wasn't so. Software authors prefer the expense of just one
development cycle for a release of Windows. If you want compatibility
as designed by the developers then wait until Windows 10 is actually
released and until ClassicShell eventually announces compatibility with
Windows 10 released version.


I realise the author of Classic Shell is not going to be writing for
Windows 10 for a long time yet. However, it worked perfectly all the way
through the change from Windows 7 to Windows 8 and Windows 8.1 and the
first two builds of Windows 10 - so I'm thinking that it has been
deliberately blocked by Microsoft if Windows 8 compatibility mode won't
work - which is doesn't. I'll have a look at the suggestions you posted,
but if that doesn't work I'll happily delete Windows 10. I don't think
Microsoft will be too concerned if yours truly is not giving them the
benefit of my wisdom any more :-) I'm never going to use it, I'm just
learning because folk will ask me questions about it in my volunteer
job. Thanks for the tips.



Yup, More conspiracies.

Rene



  #8  
Old November 13th 14, 07:06 PM posted to alt.comp.os.windows-10
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default Dirty Tricks?

Bob Henson wrote:

On 13/11/2014 5:05 PM, VanguardLH wrote:
Bob Henson wrote:

Before anyone upgrades to build 9878, you should know that Microsoft
have fixed it to prevent Classic Shell from working - even in
compatibility mode. If, like me, that is a deal breaker then don't
upgrade. There may yet be a way to run it, but it needs something
better than I've tried so far.


Can you enable/disable the Program Compatibility Assistant (as you
could, say, in Windows 7) using the following instructions?

http://www.sevenforums.com/tutorials...e-disable.html
http://www.howtogeek.com/howto/4161/...s-7-and-vista/

Here's an example of someone that hit the same dialog in Windows 8
regarding Acronis TrueImage (a backup program):

http://superuser.com/questions/49960...t-in-windows-8

Obviously ClassicShell is not yet advertising they are compatible with a
tech preview (pre-release) of Windows. Most software vendors long ago
gave up trying to guess where Microsoft would go in a new version. They
were told things would be one way by Microsoft but found out after the
release that wasn't so. Software authors prefer the expense of just one
development cycle for a release of Windows. If you want compatibility
as designed by the developers then wait until Windows 10 is actually
released and until ClassicShell eventually announces compatibility with
Windows 10 released version.


I realise the author of Classic Shell is not going to be writing for
Windows 10 for a long time yet. However, it worked perfectly all the way
through the change from Windows 7 to Windows 8 and Windows 8.1 and the
first two builds of Windows 10 - so I'm thinking that it has been
deliberately blocked by Microsoft if Windows 8 compatibility mode won't
work - which is doesn't. I'll have a look at the suggestions you posted,
but if that doesn't work I'll happily delete Windows 10. I don't think
Microsoft will be too concerned if yours truly is not giving them the
benefit of my wisdom any more :-) I'm never going to use it, I'm just
learning because folk will ask me questions about it in my volunteer
job. Thanks for the tips.


I believe Windows comes with an included list in the registry of
programs that require compability mode or checking, like under
HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags. So
the update probably also included changing the compability list.
Microsoft may have found something really nasty happens in Windows if
ClassicShell attempt to usurp the desktop manager or file explorer.

I suppose you could delete the appcomp flag entry in the registry that
lists ClassicShell but I'd go with disabling the Compability Assistant's
checking. After, if you're going to override the compatibility check
and protection for one program then you'll do it for another and another
and another. However, disabling the compatibility assistant also means
it won't amend the environ for a program that requires compatibility
settings, so [old] programs that ran before may cease to function or
start misbehaving.

Note that registry entries for some programs include their own AppCompat
subkey. Not all compatibility settings are listed by Microsoft all
together under one registry key, Microsoft may not know all apps that
require a compatibility environ, and apps that come out later may
realize they need to use a compatibility setup for them to work (i.e.,
these are apps after the release of Windows that add their own
compatibility settings and are listed as a subkey under that program's
registry entry). A program that requires a compatibility environ is not
saying it will run in one of the compatibility modes (Windows 9x, XP,
Vista, etc) which makes a whole slew of changes to the environ for a
process, including those that are not necessary for that program to
behave. I'm talking about shims the program needs to use under a
version of Windows so that program works okay there; see
http://technet.microsoft.com/en-us/l...(v=WS.10).aspx.
However, I don't know if the Compatibility Assistent is required to
implement the shim (I'm not that deep into Windows programming). The
shim may be the only code needed by a program for it to work in a later
version of Windows than it was original coded for.
  #9  
Old November 13th 14, 08:20 PM posted to alt.comp.os.windows-10
Bob Henson[_2_]
external usenet poster
 
Posts: 695
Default Dirty Tricks?

On 13/11/2014 5:51 PM, Rene Lamontagne wrote:
On 11/13/2014 11:28 AM, Bob Henson wrote:
On 13/11/2014 5:05 PM, VanguardLH wrote:
Bob Henson wrote:

Before anyone upgrades to build 9878, you should know that Microsoft
have fixed it to prevent Classic Shell from working - even in
compatibility mode. If, like me, that is a deal breaker then don't
upgrade. There may yet be a way to run it, but it needs something
better than I've tried so far.

Can you enable/disable the Program Compatibility Assistant (as you
could, say, in Windows 7) using the following instructions?

http://www.sevenforums.com/tutorials...e-disable.html
http://www.howtogeek.com/howto/4161/...s-7-and-vista/

Here's an example of someone that hit the same dialog in Windows 8
regarding Acronis TrueImage (a backup program):

http://superuser.com/questions/49960...t-in-windows-8

Obviously ClassicShell is not yet advertising they are compatible with a
tech preview (pre-release) of Windows. Most software vendors long ago
gave up trying to guess where Microsoft would go in a new version. They
were told things would be one way by Microsoft but found out after the
release that wasn't so. Software authors prefer the expense of just one
development cycle for a release of Windows. If you want compatibility
as designed by the developers then wait until Windows 10 is actually
released and until ClassicShell eventually announces compatibility with
Windows 10 released version.


I realise the author of Classic Shell is not going to be writing for
Windows 10 for a long time yet. However, it worked perfectly all the way
through the change from Windows 7 to Windows 8 and Windows 8.1 and the
first two builds of Windows 10 - so I'm thinking that it has been
deliberately blocked by Microsoft if Windows 8 compatibility mode won't
work - which is doesn't. I'll have a look at the suggestions you posted,
but if that doesn't work I'll happily delete Windows 10. I don't think
Microsoft will be too concerned if yours truly is not giving them the
benefit of my wisdom any more :-) I'm never going to use it, I'm just
learning because folk will ask me questions about it in my volunteer
job. Thanks for the tips.



Yup, More conspiracies.


Well, just because I'm paranoid, doesn't mean they aren't after me.

P.S. I just looked at the random tag-line below. If you think maybe I'm
having a bad day, you're not wrong :-)))

--
Bob
Tetbury, Gloucestershire, UK

No, I haven't got a personality disorder - all three of us are just fine!
  #10  
Old November 13th 14, 08:27 PM posted to alt.comp.os.windows-10
Rene Lamontagne
external usenet poster
 
Posts: 2,549
Default Dirty Tricks?

On 11/13/2014 1:20 PM, Bob Henson wrote:
On 13/11/2014 5:51 PM, Rene Lamontagne wrote:
On 11/13/2014 11:28 AM, Bob Henson wrote:
On 13/11/2014 5:05 PM, VanguardLH wrote:
Bob Henson wrote:

Before anyone upgrades to build 9878, you should know that Microsoft
have fixed it to prevent Classic Shell from working - even in
compatibility mode. If, like me, that is a deal breaker then don't
upgrade. There may yet be a way to run it, but it needs something
better than I've tried so far.

Can you enable/disable the Program Compatibility Assistant (as you
could, say, in Windows 7) using the following instructions?

http://www.sevenforums.com/tutorials...e-disable.html
http://www.howtogeek.com/howto/4161/...s-7-and-vista/

Here's an example of someone that hit the same dialog in Windows 8
regarding Acronis TrueImage (a backup program):

http://superuser.com/questions/49960...t-in-windows-8

Obviously ClassicShell is not yet advertising they are compatible with a
tech preview (pre-release) of Windows. Most software vendors long ago
gave up trying to guess where Microsoft would go in a new version. They
were told things would be one way by Microsoft but found out after the
release that wasn't so. Software authors prefer the expense of just one
development cycle for a release of Windows. If you want compatibility
as designed by the developers then wait until Windows 10 is actually
released and until ClassicShell eventually announces compatibility with
Windows 10 released version.


I realise the author of Classic Shell is not going to be writing for
Windows 10 for a long time yet. However, it worked perfectly all the way
through the change from Windows 7 to Windows 8 and Windows 8.1 and the
first two builds of Windows 10 - so I'm thinking that it has been
deliberately blocked by Microsoft if Windows 8 compatibility mode won't
work - which is doesn't. I'll have a look at the suggestions you posted,
but if that doesn't work I'll happily delete Windows 10. I don't think
Microsoft will be too concerned if yours truly is not giving them the
benefit of my wisdom any more :-) I'm never going to use it, I'm just
learning because folk will ask me questions about it in my volunteer
job. Thanks for the tips.



Yup, More conspiracies.


Well, just because I'm paranoid, doesn't mean they aren't after me.

P.S. I just looked at the random tag-line below. If you think maybe I'm
having a bad day, you're not wrong :-)))



Some days just aren't worth having. :-)

Better one tomorrow, Regards, Rene



  #11  
Old November 13th 14, 08:49 PM posted to alt.comp.os.windows-10
Bob Henson[_2_]
external usenet poster
 
Posts: 695
Default Dirty Tricks?

On 13/11/2014 18:06, VanguardLH wrote:
Bob Henson wrote:

On 13/11/2014 5:05 PM, VanguardLH wrote:
Bob Henson wrote:

Before anyone upgrades to build 9878, you should know that Microsoft
have fixed it to prevent Classic Shell from working - even in
compatibility mode. If, like me, that is a deal breaker then don't
upgrade. There may yet be a way to run it, but it needs something
better than I've tried so far.

Can you enable/disable the Program Compatibility Assistant (as you
could, say, in Windows 7) using the following instructions?

http://www.sevenforums.com/tutorials...e-disable.html
http://www.howtogeek.com/howto/4161/...s-7-and-vista/

Here's an example of someone that hit the same dialog in Windows 8
regarding Acronis TrueImage (a backup program):

http://superuser.com/questions/49960...t-in-windows-8

Obviously ClassicShell is not yet advertising they are compatible with a
tech preview (pre-release) of Windows. Most software vendors long ago
gave up trying to guess where Microsoft would go in a new version. They
were told things would be one way by Microsoft but found out after the
release that wasn't so. Software authors prefer the expense of just one
development cycle for a release of Windows. If you want compatibility
as designed by the developers then wait until Windows 10 is actually
released and until ClassicShell eventually announces compatibility with
Windows 10 released version.


I realise the author of Classic Shell is not going to be writing for
Windows 10 for a long time yet. However, it worked perfectly all the way
through the change from Windows 7 to Windows 8 and Windows 8.1 and the
first two builds of Windows 10 - so I'm thinking that it has been
deliberately blocked by Microsoft if Windows 8 compatibility mode won't
work - which is doesn't. I'll have a look at the suggestions you posted,
but if that doesn't work I'll happily delete Windows 10. I don't think
Microsoft will be too concerned if yours truly is not giving them the
benefit of my wisdom any more :-) I'm never going to use it, I'm just
learning because folk will ask me questions about it in my volunteer
job. Thanks for the tips.


I believe Windows comes with an included list in the registry of
programs that require compability mode or checking, like under
HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags. So
the update probably also included changing the compability list.
Microsoft may have found something really nasty happens in Windows if
ClassicShell attempt to usurp the desktop manager or file explorer.


It has certainly been made a special exception in this new build 9879.
I've tried disabling the compatibility checking with gpedit, and I've
tried the registry hack that was suggested from howtogeek, and neither
have any effect - Windows 10 still immediately picks it out as
incompatible - so your list idea is no doubt correct. As it worked fine
in the first two builds, and nothing nasty happened to Windows 10 - I'm
still with the conspiracy theory. It would be typical of Microsoft to
try to force users to use a GUI they don't want to (and to bully the
writer of Classic Shell - they already made him ditch his shell logo on
the start button in an earlier version).

Anyway, as I said before, even if they knew of me, I doubt Microsoft
would give a toss about my participation and my amateur attempts to help
them, so I shall delete the whole thing. At my age, Windows 7 will see
me out. Maybe I'll try again when they produce a consumer trial version
and/or when there's a known good version of Classic Shell that works
with Windows 10.


--
Assumption - an error of which you are as yet unaware.

Bob
Tetbury, Gloucestershire, UK
  #12  
Old November 13th 14, 09:22 PM posted to alt.comp.os.windows-10
Bob Henson[_2_]
external usenet poster
 
Posts: 695
Default Dirty Tricks?

On 13/11/2014 19:49, Bob Henson wrote:
On 13/11/2014 18:06, VanguardLH wrote:
Bob Henson wrote:

On 13/11/2014 5:05 PM, VanguardLH wrote:
Bob Henson wrote:

Before anyone upgrades to build 9878, you should know that Microsoft
have fixed it to prevent Classic Shell from working - even in
compatibility mode. If, like me, that is a deal breaker then don't
upgrade. There may yet be a way to run it, but it needs something
better than I've tried so far.

Can you enable/disable the Program Compatibility Assistant (as you
could, say, in Windows 7) using the following instructions?

http://www.sevenforums.com/tutorials...e-disable.html
http://www.howtogeek.com/howto/4161/...s-7-and-vista/

Here's an example of someone that hit the same dialog in Windows 8
regarding Acronis TrueImage (a backup program):

http://superuser.com/questions/49960...t-in-windows-8

Obviously ClassicShell is not yet advertising they are compatible with a
tech preview (pre-release) of Windows. Most software vendors long ago
gave up trying to guess where Microsoft would go in a new version. They
were told things would be one way by Microsoft but found out after the
release that wasn't so. Software authors prefer the expense of just one
development cycle for a release of Windows. If you want compatibility
as designed by the developers then wait until Windows 10 is actually
released and until ClassicShell eventually announces compatibility with
Windows 10 released version.


I realise the author of Classic Shell is not going to be writing for
Windows 10 for a long time yet. However, it worked perfectly all the way
through the change from Windows 7 to Windows 8 and Windows 8.1 and the
first two builds of Windows 10 - so I'm thinking that it has been
deliberately blocked by Microsoft if Windows 8 compatibility mode won't
work - which is doesn't. I'll have a look at the suggestions you posted,
but if that doesn't work I'll happily delete Windows 10. I don't think
Microsoft will be too concerned if yours truly is not giving them the
benefit of my wisdom any more :-) I'm never going to use it, I'm just
learning because folk will ask me questions about it in my volunteer
job. Thanks for the tips.


I believe Windows comes with an included list in the registry of
programs that require compability mode or checking, like under
HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags. So
the update probably also included changing the compability list.
Microsoft may have found something really nasty happens in Windows if
ClassicShell attempt to usurp the desktop manager or file explorer.


It has certainly been made a special exception in this new build 9879.
I've tried disabling the compatibility checking with gpedit, and I've
tried the registry hack that was suggested from howtogeek, and neither
have any effect - Windows 10 still immediately picks it out as
incompatible - so your list idea is no doubt correct. As it worked fine
in the first two builds, and nothing nasty happened to Windows 10 - I'm
still with the conspiracy theory. It would be typical of Microsoft to
try to force users to use a GUI they don't want to (and to bully the
writer of Classic Shell - they already made him ditch his shell logo on
the start button in an earlier version).

Anyway, as I said before, even if they knew of me, I doubt Microsoft
would give a toss about my participation and my amateur attempts to help
them, so I shall delete the whole thing. At my age, Windows 7 will see
me out. Maybe I'll try again when they produce a consumer trial version
and/or when there's a known good version of Classic Shell that works
with Windows 10.



P.S. to the last message. As I was about to delete the whole shooting
match, I remembered Start 8 - a very similar program to Classic Shell
and also written only for Windows 8. It works just fine, almost as good
as Classic Shell. I will still be deleting the whole thing in 30 days
time (Start 8 is only free for 30 days) but it looks as though the
conspiracy theory is true!

--
Treat each day like it's your last - one day you'll be right.

Bob
Tetbury, Gloucestershire, UK
  #13  
Old November 14th 14, 12:18 AM posted to alt.comp.os.windows-10
Joel
external usenet poster
 
Posts: 25
Default Dirty Tricks?

"Bob Henson" escreveu na mensagem ...

P.S. to the last message. As I was about to delete the whole shooting
match, I remembered Start 8 - a very similar program to Classic Shell
and also written only for Windows 8. It works just fine, almost as good
as Classic Shell. I will still be deleting the whole thing in 30 days
time (Start 8 is only free for 30 days) but it looks as though the
conspiracy theory is true!
--
Treat each day like it's your last - one day you'll be right.


Try Start Menu X
http://www.startmenux.com/index.html

  #14  
Old November 14th 14, 10:06 AM posted to alt.comp.os.windows-10
Bob Henson[_2_]
external usenet poster
 
Posts: 695
Default Dirty Tricks?

On 13/11/2014 11:18 PM, Joel wrote:
"Bob Henson" escreveu na mensagem ...

P.S. to the last message. As I was about to delete the whole shooting
match, I remembered Start 8 - a very similar program to Classic Shell
and also written only for Windows 8. It works just fine, almost as good
as Classic Shell. I will still be deleting the whole thing in 30 days
time (Start 8 is only free for 30 days) but it looks as though the
conspiracy theory is true!
--
Treat each day like it's your last - one day you'll be right.


Try Start Menu X
http://www.startmenux.com/index.html


I'll have a look at that too - I've never seen that one before. All
these programs interest me, I'm often asked how to make Windows 8
usable, and the same will happen with Windows 10 (if I'm still around
when it is released :-) )

--
Bob
Tetbury, Gloucestershire, UK
Change is inevitable, except from a vending machine.
  #15  
Old November 14th 14, 12:57 PM posted to alt.comp.os.windows-10
Joel
external usenet poster
 
Posts: 25
Default Dirty Tricks?



On 13/11/2014 11:18 PM, Joel wrote:

Try Start Menu X
http://www.startmenux.com/index.html

"Bob Henson" escreveu na mensagem ...
I'll have a look at that too - I've never seen that one before. All
these programs interest me, I'm often asked how to make Windows 8
usable, and the same will happen with Windows 10 (if I'm still around
when it is released :-) )
--
Change is inevitable, except from a vending machine.


Here's my forecast: in 2015 you'll be in Gloucestershire trying the new
Windows 10 Final.

Have a nice day.

 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 10:41 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.