From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10110020238.AA16262@clio.rice.edu>
Subject: _fixpath & getcwd W2K issues (why cvs fails but 2.03 works)
To: wojciech DOT galazka AT polkomtel DOT com DOT pl (Wojciech Galazka)
Date: Mon, 1 Oct 2001 21:38:17 -0500 (CDT)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <250B3114DA16D511B82C00E0094005F8023FC1C3@MSGWAW11> from "Wojciech Galazka" at Oct 01, 2001 11:31:29 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

I understand the problem.

cvs version (when symlink support was added) calls _fixpath for chdir 
where v2.03 did not.  Calling _fixpath during chdir on Win2000 results
in a set of interrupts (sending long instead of relative path, always
sets the drive letter) which v2.03 did not make.  (It also sets up the
dangerous situation where we can cd to root accidentally if _fixpath
does the wrong thing).  In particular, it appears setting the disk 
drive (0x0e) when the path is long causes the new problems.  

Removing the _fixpath in chdir makes things better, but I want to 
fully understand what's going on with some additional testing before
just coding up some changes which fixes a few test results.

Windows 2000 at times makes me feel like it's an axe hanging over 
my head, ready to drop when I least expect it ...