Clicking on the [Change Icon] button in the Properties for my WiDi App (running Win7 Pro 64), the resulting popup presents a field titled "Look for icons in this file": (%SystemRoot%\Installer\{C1DD4078-51FD-42CC-91DA-AD4369D5F973}\NewShortcut1_0E724E600C084A2682FDFD767068C367.exe (notice: it says "installer" not "installed")
in a directory that contains 4 differently named exe's with hex (Registry-style) components in their names.
Running fc /b (file compare /binary) in the CLI (cmd.exe) shows they are bit-identical!
On my computer their names happen to be "NewShortcut"(sequential eg 1,2,3 etc.)(hex-number).exe.
So, we can't just create shortcuts for our Intel WiDi App the way we can for EVERY other app on our computers???
Why does this operate differently from the conventional manner of showing a program's exe's icon(s) and offering "Look for icons in this file:" as the executable ? They usually show an exe's installed \location\name, which I am calling a "conventional manner" because in decades of playing with Windows and some Linux OSes, I have never before seen this.
Seems like a resource hog to me: 216KB for each" shortcut, and I only installed ONE instance of Intel WiDi (which works beautifully for me). Why four bit-identical216KB exes used apparently just to create "New Shortcuts?"
Does anyone on any forum know how this stuff actually works?
Does anyone know why the departure from conventional programming?
What OTHER programs function similarly?
I can't believe nobody knows or cares.
Message was edited by: Mi St (excess blather trimmed). Renamed Title