The scenario is this:
I am writing a script to update software on thousands of Windows95 machines,
and I need to find and delete any and all shortcuts that were used/created
by the user. Of course, the "default" shortcuts that were originally
installed will be easy to identify and remove, but the custom shortcuts made
by the users still need to be identified and removed.
My idea was to parse all ".LNK" files and identify which ones point to a the
executable I am removing. The problem is...how do I collect the 'command
line' information from the LNK files to identify the ones I want?
Anybody?
Please email or post anything you can help with!
joel...@home.com
Use the (not part of the installation) shortcut.exe utility supplied with W95
to get target information from a .lnk. Then you only have to work out how to
enumerate the .lnk on the disk...
--
Dirk Fieldhouse Logica UK Limited
field...@logica.com 75 Hampstead Road
c=gb;a=attmail;p=logica; London NW1 2PL
o=LOGICA;ou1=UK;s=fieldhouse UK
+44 (171) 637 9111
On 27 Aug 1999 13:17:16 GMT, field...@logica.com (Dirk Fieldhouse)
wrote:
>Use the (not part of the installation) shortcut.exe utility supplied with W95
>to get target information from a .lnk. Then you only have to work out how to
>enumerate the .lnk on the disk...
Hmmm... sounds useful, but, uh, er, um... I searched all the Win95 CAB
files and didn't find "shortcut.exe" in any of them. Where might it
lie?
--
darren!voi...@hotmail.com (remove the ! for a reply)
=========================================
John Gianni wrote in message <37ca61a8.38981247@news>...
Good luck,
Bill
joel <joel...@home.com> wrote in message
news:rg%w3.9378$Hu6....@news.rdc1.wa.home.com...
> Does anyone know if it is possible to search a hard drive for any
shortcuts
> that point to a particular executable?
>
> The scenario is this:
> I am writing a script to update software on thousands of Windows95
machines,
> and I need to find and delete any and all shortcuts that were used/created
> by the user. Of course, the "default" shortcuts that were originally
> installed will be easy to identify and remove, but the custom shortcuts
made
> by the users still need to be identified and removed.
>
> My idea was to parse all ".LNK" files and identify which ones point to a
the
> executable I am removing. The problem is...how do I collect the 'command
> line' information from the LNK files to identify the ones I want?
>