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
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Tue, 7 Oct 2003 18:16:42 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: fergus AT bonhard DOT uklinux DOT net
cc: cygwin AT cygwin DOT com
Subject: Re: Moving devices from 98SE to XP and back again
In-Reply-To: <000c01c38c9f$c6497f20$6fc82486@medschool.dundee.ac.uk>
Message-ID: <Pine.GSO.4.56.0310071801340.15176@slinky.cs.nyu.edu>
References: <000c01c38c9f$c6497f20$6fc82486 AT medschool DOT dundee DOT ac DOT uk>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 7 Oct 2003 fergus AT bonhard DOT uklinux DOT net wrote:

> This is a file-handling problem that I have noticed in other contexts too.
>
> Windows 98/SE is good (faultless?) at preserving upper case and lower case
> in filenames, whether long or short or with spaces. However, I have noticed
> when moving devices back and forth between 98 and XP machines, that XP is
> nothing like as careful, and that in circumstances that I have not yet
> precisely identified, one can suddenly lose this distinction when all 8.3
> filenames that had been all lower case become all upper case.
>
> Mixtures of case in filenames are preserved (libW11.dll stays libW11.dll,
> XWin.exe stays XWin.exe) and so are long file names (cygcrypto.dll stays
> cygcrypto.dll) but in all other cases (less.exe, cygwin1.dll) the change
> takes place (LESS.EXE, CYGWIN1.DLL).
>
> In an important respect this does not matter at all: Windows is daft enough
> not to know there is a difference and so it does not notice it when seeking
> and reading a file. Eg when starting Cygwin it does not matter that
> cygwin1.dll has become CYGWIN1.DLL. But: Cygwin does notice, and once there,
> ls cyg* presents a quite different response to ls CYG* (for instance). So
> this is a very nasty occurrence, once it has happened.
>
> I appreciate that the list is well populated with traffic on the subject of
> long and short filenames but I have not found the answers to the following:
> (1) when moving devices between different OS as described, is there a
> particular class of activity that will cause this transformation? (Maybe
> something to do with pursuing activities in a XP Command Prompt window, but
> I can't confirm this.) (2) assuming the activity is a useful one to be
> continued, is there some protection that can be implemented against the
> transformation taking place?
>
> Thank you.
> Fergus

<http://www.thenakedpc.com/cgi-bin/annoyarchive.pl?read=3027>.  You'll
need to do this on the Win98 machine before copying to XP.  Hope this
helps.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/