🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: borland.public.cppbuilder.nativeapi
Article #12293

Re: Failed to resolve explorer lnk from the taskbar

#12293
From: Angus
Date: Mon, 15 Dec 2003 03:10
42 lines
2779 bytes
I'm with you Remy, and now fully understand, and this helps me a great deal.
Once again thanks for  your excellent help.
Angus.


"Remy Lebeau (TeamB)" <gambit47.no.spam@no.spam.yahoo.com> wrote in message
news:3fd6321e$1@newsgroups.borland.com...
>
> "Angus" <aguspickton@yahoo.com> wrote in message
> news:3fd58940@newsgroups.borland.com...
> > I right click Internet Explorer from the desktop. Create a shortcut
> > which windows puts on the desktop. I drag the shortcut onto the
> > taskbar. That's it.
>
> The original Internet Explorer icon that is placed on the Desktop is not a
> standard shortcut, there is no filename associated with it.  That is why
you
> cannot resolve it correctly.  I told you earlier that not all items would
be
> standard shortcuts to begin with.
>
> If you right-click on the original Desktop link for IE and go to
Properties,
> you will see that it brings up the IE Configuration dialog, not the
standard
> shortcut Properties dialog.  That is your first clue that the original
link
> is not a standard shortcut.  It is actually a Shell Extension that IE
> installed for itself.
>
> Second, following the steps you describe, if you were to create such a
> shortcut from the original link, and then look at the Properties, you
would
> see that the Target field for the shortcut is set to simply "Internet
> Explorer" and is also greyed out.  That is your second clue that the
> shortcut does not point to an actual filename at all, thus IShellLink will
> not resolve a filename from it.
>
>
> Gambit
>
>
Technical Details
Message-ID: <3fdd2619@newsgroups.borland.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.media.kyoto-u.ac.jp!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail
References: <3fd298ae@newsgroups.borland.com> <3fd2f996@newsgroups.borland.com> <3fd3e61d@newsgroups.borland.com> <3fd3f278$1@newsgroups.borland.com> <3fd53140@newsgroups.borland.com> <3fd534f0$1@newsgroups.borland.com> <3fd58940@newsgroups.borland.com> <3fd6321e$1@newsgroups.borland.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10cc67,ebe7a1f15ea83f48
X-Google-Attributes: gid10cc67,public
X-Google-ArrivalTime: 2003-12-14 19:22:10 PST
Reply-To: "Angus" <anguspickton@yahoo.com>
From: "Angus" <aguspickton@yahoo.com>
Newsgroups: borland.public.cppbuilder.nativeapi
References: <3fd298ae@newsgroups.borland.com> <3fd2f996@newsgroups.borland.com> <3fd3e61d@newsgroups.borland.com> <3fd3f278$1@newsgroups.borland.com> <3fd53140@newsgroups.borland.com> <3fd534f0$1@newsgroups.borland.com> <3fd58940@newsgroups.borland.com> <3fd6321e$1@newsgroups.borland.com>
Subject: Re: Failed to resolve explorer lnk from the taskbar
Date: Mon, 15 Dec 2003 16:10:37 +1300
Lines: 44
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
NNTP-Posting-Host: 203.173.198.8
Message-ID: <3fdd2619@newsgroups.borland.com>
X-Trace: newsgroups.borland.com 1071457817 203.173.198.8 (14 Dec 2003 19:10:17 -0700)
Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.media.kyoto-u.ac.jp!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail