At 11:39 PM 10/29/2001 -0500, Dave Culbertson" <[EMAIL PROTECTED]> wrote:
>It was the documents path. They had hand typed (rather than used the
>browse button). Even when I attempted to reset the path by using the
>browse button, Win2000 Server/IIs did not correct the path. It looks like
>Win2000 Server/IIs has a case sensitivity problem. I simply retyped the
>proper path to exactly match the path (including the case of the
>characters) and the site came alive. By using the headers option, I lost
>the www. variation specified in the DNS but I know what to do to fix that
>now. Thanks to everyone for the assistance. I learned a lot about IIs and
>the implications with Win2000 server.
>
>Dave Culbertson
Case sensitivity is not a "problem" - it is functioning as designed. Since
Windows NT 3.1, file names on NTFS volumes have been case sensitive - which
is a requirement for POSIX compliance and wanted by the government.
MSKB snippit:
====================
As part of the requirements for POSIX compliance, the Windows NT File
System (NTFS) provides a case-sensitive file and directory naming
convention. Even though NTFS and the POSIX subsystem each handle
case-sensitivity well, 16-bit Windows-based, MS-DOS-based, OS/2-based, and
Win32-based applications do not.
In NTFS, you can create unique file names, stored in the same directory,
that differ only in case. For example, the following filenames can coexist
in one directory on an NTFS volume:
CASE.TXT
case.txt
case.TXT
However, if you attempt to open one of these files in a Win32 application,
such as Notepad, you would only have access to one of the files, regardless
of the case of the filename you type in the Open File dialog box.
====================
-Jeff
--------------------------------------------------------------------------------
For unsubscription of this list send an email to [EMAIL PROTECTED] with email
data containing unsubscribe emailadd sambar
