What Windows "magic" invokes a command window as an Administrator window simply by using Control+Shift+Enter versus Enter?

[groups trimmed]
"Arlen George Holder" wrote:

But even so, I couldn't find out where this "Run.lnk" shortcut goes.

It goes to the registry:
HKEY_CLASSES_ROOT\CLSID\{2559a1f3-21d7-11d4-bdaf-00c04f60b9f0}

That's where the magic begins for that particular lnk shortcut.
Applies to XP and Win7, no idea about 10.

It's interesting to note that the WinKey+R was disabled when "explorer.exe"
wasn't running.

There appears to be some dependency on explorer for the lnk, so maybe
also for the hotkey.

Is there another way of bringing up the Run box when explorer.exe is dead?

On XP the Run dialog box is in shell32.dll, on 7 and 10 - don't know.
shell32.dll (XP & 7) contains a typlib (type library for COM
automation) which has the "FileRun" method declared in the registry
entry. So there probably is a way to invoke the dialog using that as a
starting point for research! It may be possible in script or may need
a program to be written.

Otherwise use a command prompt and type the program name or "Start"
followed by similar.

On 2019-08-18 1:49 a.m., J. P. Gilliver (John) wrote:
In message , Jonathan N. Little
writes:
Arlen George Holder wrote:
Hi Jonathan,

It's _embarrassing_ that none of us know how Windows works, least of all
me.

While it's a truism that none of us knows how _all_ of Windows works,
there _are_ people who know how sections of it do - and taken as a
whole, we _do_. And by now, there are probably enough who are now
outside Microsoft that we - _as a whole_ - do know how it works, with
the exception of those bits that are to do with licencing/activation
etcetera.

I don't think it's _embarrassing_ as such, that no single individual
knows how all of it works: it's no different to any other complex
entity, such as a power station or even, these days, a car.

I commend you for mentioning power stations in this context. I'm sure
that Anatoly Dyatlov, in Chernobyl, was quite knowledgeable about how
the power station worked back on the 26th of April, 1986.

That's the nature of proprietary software. The alternative is open
source. This is why this is my only and last Winbox. All others I have a
Linux.

I'm curious: given that Windows has now been around significantly longer
than the average or even extended life of a machine, as has Linux: if
"this" is your current machine, given your stated view of proprietary
software, why did you buy it when you did (alternatives would have been
available)?

The problem with any machine purchased today is that open-source
software won't properly support it until three or four years from now.
Unless you purchase a machine which was explicitly built with hardware
that already has good driver support in Linux, it's not likely that your
experience will be any good. My laptop only recently got properly
supported by Ubuntu 19.04 and even then, the ACPI functionality is a
complete mess.

On Sun, 18 Aug 2019 10:56:27 -0400, Rabid Robot wrote:

The problem with any machine purchased today is that open-source
software won't properly support it until three or four years from now.

I wonder why people pay showroom price for brand new. Like cars, in a
few years they lose most of their value. Rich people aren't rich because
they spend a lot of money.

J. P. Gilliver (John) wrote:

I'm curious: given that Windows has now been around significantly longer
than the average or even extended life of a machine, as has Linux: if
"this" is your current machine, given your stated view of proprietary
software, why did you buy it when you did (alternatives would have been
available)?

1) I build it, as nearly all my computers for over 20 years.
2) Started with Windows.
3) For business used CorelDraw back then. Only pro graphics software for
Windows. [could not do #1 with a Mac]
4) Been using Linux for servers @ 18 years ago
5) Been using Linux on all other systems for 12 years
6) Still need CorelDraw for business and no Linux port
7) Inkscape is good, but missing essential features that CD has, but do
use Inkscape to fix CD's bad SVG export.
8) When Windows becomes subscription only I'll have to find a way to
make Inkscape work for everything, or find some better alternative.


--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

Rabid Robot wrote:
The problem with any machine purchased today is that open-source
software won't properly support it until three or four years from now.
Unless you purchase a machine which was explicitly built with hardware
that already has good driver support in Linux, it's not likely that your
experience will be any good. My laptop only recently got properly
supported by Ubuntu 19.04 and even then, the ACPI functionality is a
complete mess.

Not been my experience. Been installing Ubuntu 16.04 on brand-spank'n
new systems with 8 generation Intel CPUs where the CPU predates the OS
release by 2 years and no problem. Haven't encountered a 9th gen yet.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On Fri, 16 Aug 2019 21:43:18 -0000 (UTC), Arlen George Holder wrote:

Does anyone know what "magic" enables this wonderful feature?
I read that process doc but I still don't understand how it works.

It's just an added feature to use the shell's "RunAs" verb to open the given
command line, instead of the default "Open" verb.

Below VBScript demonstrate this.

set sa = createobject("shell.application")

'run Notepad normally
msgbox "About to run Notepad normally..."
sa.shellexecute "notepad"

'run Wordpad elevated
msgbox "About to run Wordpad Elevated..."
sa.shellexecute "wordpad", "", "", "runas"

UPDATE:

Windows 10:
o Win+R cmd {Enter} == this opens a "user" command window
o Win+R cmd {Ctrl+Shift+Enter} == this opens an "admin" command window

And, not surprisingly...
o Win+R wsl {Enter} == pwd shows the cwd is /mnt/c/Users/{user}/
o Win+R wsl {Ctrl+Shift+Enter} == cwd is set to /mnt/c/WINDOWS/system32/

Yet... paradoxically...
o Win+R wsl {Enter} == a "whoami" shows this to be a "user" window
o Win+R wsl {Ctrl+Shift+Enter} == this is _still_ a "user" window

Go figure.
--
The reason this is important is when you're entering telnet commands, the
Linux telnet has options not necessarily in the Windows telnet, and, more
importantly, the shell in Linux also has nice options (e.g., bang bang).

On Tue, 4 Aug 2020 21:49:02 -0000 (UTC), Arlen Holder wrote:

o Win+R wsl {Enter} == a "whoami" shows this to be a "user" window
o Win+R wsl {Ctrl+Shift+Enter} == this is _still_ a "user" window

Oooooops.

I forgot to mention that you won't have wsl unless you do this:
o Tutorial for setting up Ubuntu as a Windows Subsystem for Linux WSL in Windows 10
https://groups.google.com/forum/#!topic/alt.comp.freeware/rOT8xBWo9dk

Note: You won't have telnet in Windows either, unless you do this:
o Tutorial: How to enable the Telnet Client in Windows 10
https://groups.google.com/forum/#!topic/alt.comp.freeware/pEhuvzzFBTU

For example:
{me} Win+R cmd {ctrl+shift+enter} == optional, admin cmd window
{it} C:\WINDOWS\system32 == this is the admin $p$g prompt apparently
{me} C:\WINDOWS\system32 telnet
{it} 'telnet' is not recognized as an internal or external command,
{it} operable program or batch file. == I could "enable" it but screw that
{me} exit

Start over directly with Ubuntu running inside of Windows:
{me} Win+R wsl == to get into the Windows subsystem for Linux
{me} $ telnet nntp.aioe.org 119
{me} post
{it} 340 Ok, recommended message-ID
{me} from: Arlen Holder
{me} newsgroups: comp.mobile.android
{me} subject: Do you use FreedomPop in the USA? If so, what are the details?
{me} message-id:
{me} references:
{me} blank line
control+v doesn't work, but sometimes control+q works here
{me} .
{me} quit == exit out of telnet
{me} exit == exit out of wsl

This is what it looks like, in the flesh (with inevitable gotchas):
o https://i.postimg.cc/kGG8W31b/telnetnntp01.jpg
--
Two kinds of people frequent Usenet: those who add value & those who chat.