This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
troubleshooting:disable8dot3 [2008/02/08 18:49] – external edit 127.0.0.1 | troubleshooting:disable8dot3 [2009/03/10 22:35] – Highlight the error message xuesheng | ||
---|---|---|---|
Line 10: | Line 10: | ||
By default Windows systems support the SFN format so whenever a file is created using a long file name (LFN) Windows will create a unique SFN alias for the file. Therefore it should not matter where POPFile is installed. However on some systems this SFN support may have been disabled therefore the 0.22.2 (or later) installer checks for SFN support and will display a message like this if it has been disabled: | By default Windows systems support the SFN format so whenever a file is created using a long file name (LFN) Windows will create a unique SFN alias for the file. Therefore it should not matter where POPFile is installed. However on some systems this SFN support may have been disabled therefore the 0.22.2 (or later) installer checks for SFN support and will display a message like this if it has been disabled: | ||
- | + | ^To install on the ' | |
- | *//"To install on the ' | + | |
There is a small overhead involved in generating these SFN aliases on NTFS-based systems but if there are folders containing a large number of files with similar names this overhead can become significant so many Windows tweaking/ | There is a small overhead involved in generating these SFN aliases on NTFS-based systems but if there are folders containing a large number of files with similar names this overhead can become significant so many Windows tweaking/ | ||
Here is some information from Microsoft' | Here is some information from Microsoft' | ||
- | + | >//" | |
- | *//" | + | |
===== Solutions | ===== Solutions |
Should you find anything in the documentation that is incomplete, unclear, outdated or just plain wrong, please let us know and leave a note in the Documentation Forum.