LeRoy Cressy on 1 Nov 2005 13:55:55 -0000 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Michael C Finn wrote: > ----- Original Message ----- > From: "Doug Crompton" <doug@crompton.com> > Sent: Wednesday, October 26, 2005 03:34 PM > > > >>When creating nested, long filename directories there is a potential for >>unexpected files loss. I had a tree about 7-10 deep with names that were >>rather long at most levels. When attempting to manipulate the files in a >>directory window at the bottom of the tree (left click the filename to >>mark and right click to display the actions) the file immediately >>disappeared from view. No warning no nothing. At first I thought I had a >>virus or some other system problem but that is not the case. This is a >>real windows bug. I was able to recreate it and it seems that in general >>windows treatment of file paths over the 256 character limit is handled >>very poorly. Just beware. I lost an important file last night. In >>disbelief I spent a great deal of time trying to fine it to no avail. When >>this problem happens it just evaporates. I assume it is still really >>somewhere until overwritten but it does not appear in any directory or any >>search. >> >>This was on WinXP media center 2005 edition. > > > It's worse than a Windows bug; it's a Windows design feature! > > I have a copy of the Windows 95 Resource Kit book. Beginning with long file > name support in Win 95, maximum filename component length is 255 characters > and maximum path length is 260 characters. In the administrative > considerations subchapter, it is suggested that file names be limited to 50 to > 75 characters and to keep total path length in mind when using nested file > folders so there will be room for copying and moving files. > > As far as I know, all subsequent versions right up to XP follow that same > rule. > I think that you can find your file if you mount the filesystem as a msdos file system mount -t msdos /dev/fatfs-dev /mountpoint This will take away all of the long filenames from view, and every file will be 8.3 This might work, though I never tried it. - -- Rev. LeRoy D. Cressy mailto:leroy@lrcressy.com /\_/\ http://lrcressy.com ( o.o ) Phone: 215-535-4037 > ^ < FAX: 215-535-4285 gpg fingerprint: 62DE 6CAB CEE1 B1B3 359A 81D8 3FEF E6DA 8501 AFEA For info on enigmail: http://lrcressy.com/linux/mozilla.pdf For info on gpg: http://www.gnupg.org/ Jesus saith unto him, I am the way, the truth, and the life: no man cometh unto the Father, but by me. (John 14:6) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iQIVAwUBQ2dzenlsxrSGsIsqAQqjcA//UlRz19g7g459Iln3sSJb8MKQufMsXufb hmR1WB0zNyXf1+pKztQnGCw4mAR3C59fGLUrWjM7hbBd48KQtWxf+gPOGOhDXILb EjA6+wSSjN0xoe2QGRUquzy6ZHH9nmyDJEJXXcS3b39H+RvCuvP9IeKiPEdjkvfN Z/hlMC2H3gyi+Cyw4IclHmo69k7kh+iRZq9RcOffIU7lTmhZx+baQ/dDCrMRR4Fr kFfVisUoyNUUiuiY2pHMK1FXT5Gla6neLML8nS6hKDWW2vZxdcXt9klTQtBjtNcv 43L3RK6GEXPaSrk+2Nq0tbDHCEtpMUcMN2s8ARYwE3roKPFZ1pWGmf4RMfsdqNAh Ms4IiZdL2f/kEdyl+uIqx3WeeYSPiho8goWSgkMiijQPkxPmbngEc8GNtuEuAt8R j6Eh0qmGCthlvT0o/whAW4e41OC1oOAsWScHgZ1PLRKPg4GAYaQ+VHxmFlrJVrtv oujUDFXH76ukHgvLcDVJgTT9qamjiSeDtFQFqiFcUggWhuVPpwivomk2T3nFhqXq zoZb/bJLQGLANkBCCUQgBTRzkI+EvK3A6h1YvOptGVml5dmVLGBwdWqtNmGp0k/f KKjunU/HFXKlIM/b3KUtCRExnRqX5HliRgxIcJLObaDltYkfOyO3eVpLaE6wQcnX Qp/UDuXie8c= =JBJv -----END PGP SIGNATURE----- ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|