I have downloaded the new 0.22.1 version. When I get
to the screen to select a folder (c:\program files\popfile) to install into I get an
error message that says
"Current configuration does not support short file names!
Please select a folder location which does not contain
spaces."
What is wrong? I have installed and have been running
that last version with no problems and it installed
without any problems.
Can some body help me?
Thanks
Tom
njbeasst@comcast.net
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Windows installers allow the 'User Data' to be stored separately from the POPFile program files (this is Phase 1 of the multi-user changes). Two environment variables (POPFILE_ROOT and POPFILE_USER) are used to tell POPFile where to find the program files and the 'User Data' files.
The Windows installer always creates these environment variables even if the 'User Data' is stored in the same folder as the POPFile program files. The current version of POPFile does not work properly when the values used in these environment variables contain spaces, so the installer always uses the short file name (SFN) format for the environment variables.
Just before the 0.21 release someone reported a problem when trying to install on a system which did not support short file names so the installer was modified but the changes were too late for the 0.21 release. (The 0.21.x installers assume that short file names are always supported so they don't bother to look at the result of converting the long file name into the short file name.)
The 0.22.x installers can detect when an NTFS-based system has disabled short file name support but are not clever enough to detect if the selected installation folder has a short file name (because it was created before short file names were disabled).
The easiest solution is to enable short file name support, use the 0.22.x installer to upgrade your existing installation (assuming that is what you want to do) and then disable short file name support (assuming you want to keep it disabled). Temporarily enabling short file name support is a common solution to this problem.
Another solution would be to copy your existing 'User Data' to a folder path which does not contain spaces and then use the 0.22.x installer to upgrade this data. Then you can uninstall the old version of POPFile.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You quoted the error message as containing, "Current configuration does not support short file names!"
Was that a typo in your report or does the error message really say "short?" I believe it should say something like "Long file names are not supported!"
--
Jim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> Was that a typo in your report or does the error message really say "short?" <<
Yes, the message really does say "short".
>> I believe it should say something like "Long file names are not supported!" <<
I suppose it depends upon your point of view.
Normally the installer converts the long file names into short ones when creating the environment variables. However a few systems do not support short file names so this conversion cannot be performed.
As far as the installer is concerned the problem is that the target system does not support short file names, hence the reference to "short" in the message the installer displays.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have downloaded the new 0.22.1 version. When I get
to the screen to select a folder (c:\program files\popfile) to install into I get an
error message that says
"Current configuration does not support short file names!
Please select a folder location which does not contain
spaces."
What is wrong? I have installed and have been running
that last version with no problems and it installed
without any problems.
Can some body help me?
Thanks
Tom
njbeasst@comcast.net
The Windows installers allow the 'User Data' to be stored separately from the POPFile program files (this is Phase 1 of the multi-user changes). Two environment variables (POPFILE_ROOT and POPFILE_USER) are used to tell POPFile where to find the program files and the 'User Data' files.
The Windows installer always creates these environment variables even if the 'User Data' is stored in the same folder as the POPFile program files. The current version of POPFile does not work properly when the values used in these environment variables contain spaces, so the installer always uses the short file name (SFN) format for the environment variables.
Just before the 0.21 release someone reported a problem when trying to install on a system which did not support short file names so the installer was modified but the changes were too late for the 0.21 release. (The 0.21.x installers assume that short file names are always supported so they don't bother to look at the result of converting the long file name into the short file name.)
The 0.22.x installers can detect when an NTFS-based system has disabled short file name support but are not clever enough to detect if the selected installation folder has a short file name (because it was created before short file names were disabled).
The easiest solution is to enable short file name support, use the 0.22.x installer to upgrade your existing installation (assuming that is what you want to do) and then disable short file name support (assuming you want to keep it disabled). Temporarily enabling short file name support is a common solution to this problem.
Another solution would be to copy your existing 'User Data' to a folder path which does not contain spaces and then use the 0.22.x installer to upgrade this data. Then you can uninstall the old version of POPFile.
Brian
I'm confused by what you and Brian have said.
You quoted the error message as containing, "Current configuration does not support short file names!"
Was that a typo in your report or does the error message really say "short?" I believe it should say something like "Long file names are not supported!"
--
Jim
Jim,
>> Was that a typo in your report or does the error message really say "short?" <<
Yes, the message really does say "short".
>> I believe it should say something like "Long file names are not supported!" <<
I suppose it depends upon your point of view.
Normally the installer converts the long file names into short ones when creating the environment variables. However a few systems do not support short file names so this conversion cannot be performed.
As far as the installer is concerned the problem is that the target system does not support short file names, hence the reference to "short" in the message the installer displays.
Brian