There are  a few restrictions about  mixed case paths and  file names. In
general, things will work as expected with the understanding that the all
uppercase file names you find on VM/VMS/NT become all lowercase. The only
exception is exits, which  are in upper case so that  they stand out from
regular  files.  Paths  (directories)  come either  from  an  environment
variable, or from some configuration file, list header, etc. If you set a
mixed  case path  in  an environment  variable, it  will  work fine.  The
standard configuration scripts  essentially define environment variables,
so this too works fine. List  headers, however, aren't case sensitive, so
when LISTSERV reads the unquoted path from the "Notebook=" keyword, it is
all uppercase and  gets converted to all lowercase. It  might work if you
enclosed the entire path in double quotes, and it will definitely work if
you change  D to  d, or  do setenv  X "/listserv/arch/D"  and then  use X
instead of the path.  This will all be documented in  the new list header
keyword.
 
  Eric