Author |
Message |
Global announcement Topic: Classic Shell no longer in development. Source code released |
freezer |
Posted: Tue Dec 05, 2017 12:02 pm
|
|
Replies: 133 Views: 356436
|
Classic Shell is, for me, an essential piece of software. I install it on every computer I use! Even virtual machine's I only need for an hour, Classic Shell is the first thing I install. I'm so sad to see this WONDERFUL product coming to an end. But I do feel your pain. I am sad to see Windows movi... |
|
|
Forum: Bug Reports Topic: The new run/search box cannot be used to access UNC paths |
freezer |
Posted: Wed Sep 10, 2014 2:01 pm
|
|
Replies: 5 Views: 3816
|
What if a new file is found while you press Enter? Then it will open that file instead of the path you typed. You have no way of knowing if new results will show up until the search is finished. If your intent is to just open a folder, you can use the Win+R box, or even Win+E to open Explorer and t... |
|
|
Forum: Bug Reports Topic: The new run/search box cannot be used to access UNC paths |
freezer |
Posted: Thu Sep 04, 2014 9:44 am
|
|
Replies: 5 Views: 3816
|
I know it's taken me a while to get back on this thread. Whereas the newer versions of Classic Shell works much better with UNC paths, it's still not perfect. The problem now is one of timing. When you first type a UNC path in the Classic Shell search/run box, it displays a window to the side with t... |
|
|
Forum: Bug Reports Topic: The new run/search box cannot be used to access UNC paths |
freezer |
Posted: Mon Oct 14, 2013 9:31 am
|
|
Replies: 5 Views: 3816
|
The new run/search box in 4.0 has serious flaws and cannot be used to access network resources via UNC path. If you type in a machine name using UNC syntax and hit enter, instead of locating the machine on the network and browsing to it, it will search the local machine for that string. So if you ty... |
|
|
Forum: Bug Reports Topic: No indication when accessing network resources |
freezer |
Posted: Fri Feb 01, 2013 3:52 pm
|
|
Replies: 0 Views: 5229
|
If you click the Start button, then in the run/search box type a UNC path (e.g. \\foobar). When you press enter ClassicShell attempts to access this network resource, but there is no visual feedback to the user that it's doing anything. If the network resource is inaccessible then ClassicShell sits ... |
|
|
Sort by: |