Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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: <3D767411.CE1BDB47@t-online.de>
Date: Wed, 04 Sep 2002 22:58:57 +0200
From: Andreas DOT Hadler AT t-online DOT de (Andreas Hadler)
X-Accept-Language: en
MIME-Version: 1.0
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: NTVDM error
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Sender: 051392936-0001 AT t-dialin DOT net

I've seen the problem of NTVDM-error messages on W2k, generated while
e.g. building cross-compilers (powerpc-eabi in my case), sometimes asked
and answered in the archives, but I've never seen any confirmation, that
e.g. replacing symlinks with direct copies is the ultimate remedy.

Can anyone, who was concerned by this problem, comment on the remedies? 

I'd love to see another way than replacing the about 2500 symlinks of my
cygwin installation with the real files - not because of the work, which
is scriptable, more worried about the disk space, but mostly because I
can not judge, what will break on updates or system changes.

Kind regards
   Andreas Hadler

-- 
"Computers are useless. They can only give you answers."
Pablo Picasso

--
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/