Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <000801c1f1aa$521dbee0$6fc82486@medschool.dundee.ac.uk> Reply-To: From: To: Cc: Subject: RE: using Windows links Date: Thu, 2 May 2002 08:23:56 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 If it helps anybody, which it might not : in the entire Cygwin provision there are I think a dozen *.lnk files. I found that 5 of them induced objections from Norton ("invalid shortcuts"). As was pointed out to me on this list, this is a Windows/Norton glitch, not a Cygwin glitch ... but it bugged me all the same. Also other people have reported problems with *.lnk files (either their creation or interpretation). So, on my system, I have rewritten all filename.lnk files as one-line textfiles of the form !target_ where ! is as written; target is the target of the original link; the final character is not actually _ as shown but ASCII 00. There is no closing . Then rename filename.lnk simply as filename; remove R attribute; add S attribute; and that's it. At the cost of some minor editing effort, Norton is silenced, Windows can't see any things it even thinks are Windows shortcuts, and Cygwin works as well as ever. Fergus -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/