> I also had problems installing root into an windows
> LONG NAME folder. This does not work for MANY unix
> based programs, I dont know why.
I dont' know what did you mean "unix based" program.
Usually the problems are caused by TWO reasons:
1. The blank in the file named is NOT treated by application as a trivial
"letter" rather as some significant delimiter. (this may be a case for
UNIX application also)
2. For each file name the Windows file system (NTFS or FAT32)
can generate the artificial short name for non-8dot3 file
This is done for the sake of the backward compitibility with the old MS DOS
codes they don't expect more the 8 characters with file names.
By programmer's mistake the code may be confused with both short
and long file names to compare and open file.
Some code may have concluded two different files were requested / provided
There is third case (that can be taken into account to port programs between two sort of OS's.
UNIX file system is case sensitive. UNIX does distinguish "File" and "file". Windows doesn't
Just my 2 cents.
Valeri
This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:51:10 MET