Check out these MSKB articles. They describe how shortcuts are resolved. In particular, the last one describes the process required to "fix" this behaviour. I had a LOT of trouble when I first set up my LAN because people had a nasty habit of sharing drive C (even I used to do this until I discovered that this is a Bad Idea). The main problem is that the shortcut includes the UNC path to the application and will attempt to use this first. If drive C on the machine on which the share was created is globally available then the app will be run from that machine instead of the local one. This obviously has the undesirable effect of giving poor performance and increased network load (apart from this it did actually seem to work fine). NT has a similar problem to 95/98 in this regard. I was not able to get the "shortcut.exe" program to fix this issue under 95 as it was supposed to (surprise!!). I have now gotten into the habit of regularly checking machines for rogue shares of drive C and have advised all staff NOT to do this. I don't have any NT workstations so I'm not sure if the fixes proposed in the last article work (although they seem to be more complete than the 95 fixes) http://support.microsoft.com/support/kb/articles/q128/9/32.asp http://support.microsoft.com/support/kb/articles/q150/2/15.asp http://support.microsoft.com/support/kb/articles/Q158/6/82.asp Cheers Michael Anthon TAMS Systems> -----Original Message----- > From: Andrew Perrin - Demography [mailto:aperrin@demog.Berkeley.EDU] > Sent: Wednesday, 29 July 1998 1:41 > To: Multiple recipients of list > Subject: Re: Strange problem with icons! > > > I've got similar behavior here -- it seems to me that the > desktop shortcut > is set up with a complete UNC path, i.e., > \\machine-1\admin$\cmd.exe not > simply %systemroot%\cmd.exe (which is of course what it should be). > Anybody know why or care to comment? >
On Wed, 29 Jul 1998, Michael Anthon wrote:> I had a LOT of trouble when I first set up my LAN because people had a > nasty habit of sharing drive C (even I used to do this until I > discovered that this is a Bad Idea).NT shares your C drive as C$ automatically on every install. I don't know why you think this is such a 'Bad Idea', unless it's simply your shortcut problem.> I was not able to get the "shortcut.exe" program to fix this issue under > 95 as it was supposed to (surprise!!).Granted it's a terrible piece of code but I've gotten it to work. You simply need to call it from the directory the shortcut file is in, not with a pathname. I wrote a perl script to run through all of the shortcuts under c:\windows and disable the 'link tracking feature' with the -s switch. It does a chdir(), then calls 'shortcut.exe -s' on each .lnk file. [Darrin] -- "I have no special gift. I am only passionately curious." - A. Einstein Darrin M. Gorski, Research Computer Systems Network Support Scientific Research Laboratories, Ford Motor Company Internet: dgorski@ford.com | Tel/Fax: +1 (313) 248-3753
> -----Original Message----- > From: Darrin M. Gorski [mailto:dgorski@ford.com] > Sent: Thursday, 30 July 1998 12:28 > To: Michael Anthon > Cc: Multiple recipients of list > Subject: RE: Strange problem with icons! > > > > On Wed, 29 Jul 1998, Michael Anthon wrote: > > > I had a LOT of trouble when I first set up my LAN because > people had a > > nasty habit of sharing drive C (even I used to do this until I > > discovered that this is a Bad Idea). > > NT shares your C drive as C$ automatically on every install. > I don't know > why you think this is such a 'Bad Idea', unless it's simply > your shortcut > problem. >Yes, that's correct (and so does 95/98), but they are administrative shares, and only users with admin permission may access them, which is fine. The problem I was having was that the shares people were creating gave global r/w access. And yes, it WAS the shortcut problem that was giving me such grief. I couldn't get the shortcut.exe program to do it's stuff (can't remember if I tried running it in the same directory as the file). This still would not totally remove this issue since you would need to run shortcut.exe every time someone creates a new shortcut and would need to be run on every workstation as well as all the profile storage areas on the server. By not allowing global r/w access to C drive on all machines, this problem is completely removed since the UNC path in the shortcut is not accessible and it reverts to using the local path. Regards Michael Anthon TAMS Systems