Hi...I am using windows xp pro and have been using POPFile v0.22.2. I downloaded v0.22.3 and tried to install. The destination folder is "C:\Program Files\POPFile". When I hit "upgade" I get the message "To install on the 'C' drive please select a folder location that does not contain spaces". What is going on here?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That probably has to do with using NTFS and turning off short filenames. POPFile needs to use the short DOS compatable filename so if you turn off this option it can cause problems. Previous versions of the installer didn't check for this which could lead to problems.
Since this is new I will have to let Brian give more detail of what solutions you have to work around it. I don't remember all the details.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> I ... have been using POPFile v0.22.2. I downloaded v0.22.3 ... When I hit "upgade" I get the message "To install on the 'C' drive please select a folder location that does not contain spaces" <<
In order to support the limited multi-user features introduced in the 0.21 release, the installer ensures that the POPFILE_ROOT and POPFILE_USER environment variables are initialised before POPFile is started.
POPFile does not work properly if these environment variables contain spaces therefore the installer uses the short filename (SFN) format (e.g. "C:\Program Files\POPFile" usually becomes "C:\PROGRA~1\POPFILE").
At first the installer assumed that short file names were always supported (this is the default Windows setting) but over a year ago the installer was updated to check if SFN support had been disabled.
The 0.22.2 installer contains code which checks for SFN support and will display a similar message to the one shown by the 0.22.3 installer.
It looks like SFN support was disabled on your system after 0.22.2 was installed. You can use the installer's diagnostic utility to confirm this. This utility is part of your existing POPFile installation and can be run from the Start Menu:
Here is some advice from Microsoft's Windows XP Resource Kit:
"Although disabling 8.3 name creation increases NTFS performance under Windows XP Professional ... some third-party programs cannot be installed on NTFS volumes if 8.3 names are disabled. In this case, use the fsutil behavior set command to enable short file names, restart the computer, and then try installing the program again."
After upgrading to 0.22.3 you should be able to disable SFN support again (I don't use NTFS so I cannot test this).
Another solution would be to copy your existing POPFile program folder and POPFile User Data folder to locations with paths which do not contain spaces and then select those locations when running the 0.22.3 installer. The installer diagnostic can be used to find these folders.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I face a problem after upgrading with SFN disabled - I install 22.3 over 22.2 and I specify another path (C:\Popfile).
Now I only have "backup" folder of 22.2 on hand, how can I put the history back to 22.3? I try to paste popfile.db and popfile.cfg back to 22.3 folder (C:\Popfile) but PF cannot start. =< if I enable SFN before upgrading, that's good.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> I install 22.3 over 22.2 and I specify another path (C:\Popfile) <<
If you specify another path then the installer will install the files using the path you specify. It will not transfer any files from the old path to the new path - the old files are ignored.
>> how can I put the history back to 22.3 <<
Do you mean the corpus which contains the data POPFile uses to classify new messages or do you mean the recent message history which lets you reclassify messages to correct any errors made by POPFile?
1) Actually when I run 22.3 the first time, the installer detects 22.2 and upgrade it. However, it complains about the space in folder name. I specify C:\Popfile after several trial.
2) I mean the corpus, which I hope I can get it back instead of teaching the engine again. Unluckily I have "backup" folder on hand after several install/uninstall. The backup folder includes oldsql\, nonsql\, backup.ini and popfile.cfg. I found popfile.db inside oldsql which I guess it's the corpus. Now 22.3 runs smoothly, but I want to "restore" the old corpus file from the backup folder.
Thanks a lot!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> However, it complains about the space in folder name <<
Normally the installer uses the short file name (SFN) format when it creates the two environment variables for POPFile. It looks like SFN support on your system was disabled after you installed 0.22.2.
>> I found popfile.db inside oldsql which I guess it's the corpus <<
That file is a backup created by the installer when it detects that a database upgrade is required.
Upgrading from 0.22.2 to 0.22.3 does _not_ involve a database upgrade so that file may have been created by the 0.22.x installer when you upgraded from 0.21.x. You can check the date of the backup\oldsql\popfile.db file to confirm this.
The backup\backup.ini file shows the location of the original popfile.db file - look for the "DatabasePath" entry in that "ini" file. This entry should point to a more up-to-date version of popfile.db.
If your 0.22.2 installation used the default 'User Data' location then the popfile.db file you want should be
C:\Documents and Settings\<user name>\Application Data\POPFile\popfile.db
(replace <user name> with your Windows login name).
If 0.22.3 is running OK then all you need to do is shut it down then replace the 0.22.3 version of popfile.db with the 0.22.2 version. When you restart 0.22.3 you should find that your training has been restored.
To find where the 0.22.3 version of popfile.db is stored use this Start Menu entry:
The Windows version of 0.22.3 comes with a utility (pfidbstatus.exe) which can check the SQLite database. The installer creates a Start Menu shortcut for this utility:
Start -> Programs -> POPFile -> Support -> Check database status
The installer also creates a "Check database status" shortcut in the 'User Data' folder.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi...I am using windows xp pro and have been using POPFile v0.22.2. I downloaded v0.22.3 and tried to install. The destination folder is "C:\Program Files\POPFile". When I hit "upgade" I get the message "To install on the 'C' drive please select a folder location that does not contain spaces". What is going on here?
That probably has to do with using NTFS and turning off short filenames. POPFile needs to use the short DOS compatable filename so if you turn off this option it can cause problems. Previous versions of the installer didn't check for this which could lead to problems.
Since this is new I will have to let Brian give more detail of what solutions you have to work around it. I don't remember all the details.
>> I ... have been using POPFile v0.22.2. I downloaded v0.22.3 ... When I hit "upgade" I get the message "To install on the 'C' drive please select a folder location that does not contain spaces" <<
In order to support the limited multi-user features introduced in the 0.21 release, the installer ensures that the POPFILE_ROOT and POPFILE_USER environment variables are initialised before POPFile is started.
POPFile does not work properly if these environment variables contain spaces therefore the installer uses the short filename (SFN) format (e.g. "C:\Program Files\POPFile" usually becomes "C:\PROGRA~1\POPFILE").
At first the installer assumed that short file names were always supported (this is the default Windows setting) but over a year ago the installer was updated to check if SFN support had been disabled.
The 0.22.2 installer contains code which checks for SFN support and will display a similar message to the one shown by the 0.22.3 installer.
It looks like SFN support was disabled on your system after 0.22.2 was installed. You can use the installer's diagnostic utility to confirm this. This utility is part of your existing POPFile installation and can be run from the Start Menu:
Start -> Programs -> POPFile -> Support -> PFI Diagnostic utility (full)
Here is some advice from Microsoft's Windows XP Resource Kit:
"Although disabling 8.3 name creation increases NTFS performance under Windows XP Professional ... some third-party programs cannot be installed on NTFS volumes if 8.3 names are disabled. In this case, use the fsutil behavior set command to enable short file names, restart the computer, and then try installing the program again."
After upgrading to 0.22.3 you should be able to disable SFN support again (I don't use NTFS so I cannot test this).
Another solution would be to copy your existing POPFile program folder and POPFile User Data folder to locations with paths which do not contain spaces and then select those locations when running the 0.22.3 installer. The installer diagnostic can be used to find these folders.
Brian
Easy to fix.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"NtfsDisable8dot3NameCreation"=dword:00000000
I face a problem after upgrading with SFN disabled - I install 22.3 over 22.2 and I specify another path (C:\Popfile).
Now I only have "backup" folder of 22.2 on hand, how can I put the history back to 22.3? I try to paste popfile.db and popfile.cfg back to 22.3 folder (C:\Popfile) but PF cannot start. =< if I enable SFN before upgrading, that's good.
>> I install 22.3 over 22.2 and I specify another path (C:\Popfile) <<
If you specify another path then the installer will install the files using the path you specify. It will not transfer any files from the old path to the new path - the old files are ignored.
>> how can I put the history back to 22.3 <<
Do you mean the corpus which contains the data POPFile uses to classify new messages or do you mean the recent message history which lets you reclassify messages to correct any errors made by POPFile?
>> but PF cannot start <<
Try running the installer's diagnostic utility:
Start -> Programs -> POPFile -> Support -> PFI Diagnostic utility (full)
The report will check some of the work done by the 0.22.3 installer.
Brian
Brian, thanks.
1) Actually when I run 22.3 the first time, the installer detects 22.2 and upgrade it. However, it complains about the space in folder name. I specify C:\Popfile after several trial.
2) I mean the corpus, which I hope I can get it back instead of teaching the engine again. Unluckily I have "backup" folder on hand after several install/uninstall. The backup folder includes oldsql\, nonsql\, backup.ini and popfile.cfg. I found popfile.db inside oldsql which I guess it's the corpus. Now 22.3 runs smoothly, but I want to "restore" the old corpus file from the backup folder.
Thanks a lot!
>> However, it complains about the space in folder name <<
Normally the installer uses the short file name (SFN) format when it creates the two environment variables for POPFile. It looks like SFN support on your system was disabled after you installed 0.22.2.
>> I found popfile.db inside oldsql which I guess it's the corpus <<
That file is a backup created by the installer when it detects that a database upgrade is required.
Upgrading from 0.22.2 to 0.22.3 does _not_ involve a database upgrade so that file may have been created by the 0.22.x installer when you upgraded from 0.21.x. You can check the date of the backup\oldsql\popfile.db file to confirm this.
The backup\backup.ini file shows the location of the original popfile.db file - look for the "DatabasePath" entry in that "ini" file. This entry should point to a more up-to-date version of popfile.db.
If your 0.22.2 installation used the default 'User Data' location then the popfile.db file you want should be
C:\Documents and Settings\<user name>\Application Data\POPFile\popfile.db
(replace <user name> with your Windows login name).
If 0.22.3 is running OK then all you need to do is shut it down then replace the 0.22.3 version of popfile.db with the 0.22.2 version. When you restart 0.22.3 you should find that your training has been restored.
To find where the 0.22.3 version of popfile.db is stored use this Start Menu entry:
Start -> Programs -> POPFile -> Support -> PFI Diagnostic utility (simple)
The popfile.db file will be found at the "User Data folder" address.
Brian
Yes, it works! Previously I though it's corrupted and PF did not response, but actually it loaded after waiting for a while. Thanks!
>> Yes, it works! <<
Glad to hear this news.
>> Previously I though it's corrupted <<
The Windows version of 0.22.3 comes with a utility (pfidbstatus.exe) which can check the SQLite database. The installer creates a Start Menu shortcut for this utility:
Start -> Programs -> POPFile -> Support -> Check database status
The installer also creates a "Check database status" shortcut in the 'User Data' folder.
Brian