|
On May 10, 2018, at 1:24 PM, John Yeung <gallium.arsenide@xxxxxxxxx<mailto:gallium.arsenide@xxxxxxxxx>> wrote:
On Thu, May 10, 2018 at 12:59 PM, Charles Wilt <charles.wilt@xxxxxxxxx<mailto:charles.wilt@xxxxxxxxx>> wrote:
It is that simple...
Windows 3.0 - Windows 10 all have a "change icon" button on the properties
pop-up for a shortcut.
Yeah, it defaults to the looking at the icons in the target .EXE but you
can change that to any file.
Ah, but then that is NOT as simple as just changing the "link behind
the icon" as Jon suggested.
I read Jon's suggestion *as he expressed it* as opening the properties
of the link ("shortcut" in Windows parlance) that the end user clicks
on to launch the old client, and changing the target executable for
that shortcut to the new client, thereby hopefully preserving the
appearance of the old shortcut, yet executing the new client.
This would be a completely reasonable intuition of what should happen,
and since Jon hasn't been primarily a Windows user for quite some time
now, I would not fault him for believing this would work.
As it happens, he, you, and I all know better. But maybe not all
readers do, so I was merely pointing out that it is not as simple as
that (understandable but mistaken) intuition. And even if you do know
how it works, I still disagree with the characterization that it's
"that simple" because as Dan pointed out, if you don't have the
executable for the old client on the machine you are setting up, you
have to extract the desired icon into a separate .ico file (or
replicate it some other way), which is a whole other thing.
John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.
Help support midrange.com<http://midrange.com> by shopping at amazon.com<http://amazon.com> with our affiliate link: http://amzn.to/2dEadiD<http://amzn.to/2dEadiD>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
