(1) When I added the most recent missing Perl component that Naoki reported I forgot to update the uninstaller. This means the component is unexpectedly left behind so the RC4 uninstaller has to ask for permission to remove the leftover file. CVS has been updated to fix this bug.
(2) The minimal Perl is still using an out-of-date Time::Local module (v1.11) which means the "Sec too big" bug has not been fixed (so warnings like "Sec too big - 29980 > 11647" may appear on the console when processing messages).
I have been using the v1.17 version of Time::Local (released January this year) which fixes this and several other bugs (in fact the function in question has been more or less re-written, if I remember correctly). PPM4 can get v1.17 of "Time-Local" from the "Bribes de Perl" repository.
The installer is using Time::Local from "site\lib" instead of the default "lib" folder so I'm not sure why RC4 has v1.11 (which is what is in the main "lib" folder on my system).
(3) If the installer is run from a "standard" account on Vista, the user will be prompted for an "administrator" password to allow the installer to write to the registry and "Program Files" folder etc.
This means the installer will think it is being run by the administrator account so when the "Add POPFile User" window appears offering to configure POPFile it will actually configure POPFile for the "administrator" user and _not_ the user who started the installer.
The wizard's WELCOME page mentions this ("This wizard will guide you through the configuration of POPFile for the <name of administrator account> user") but I guess most users won't notice that message :(
The "standard" user should click the "Cancel" button and then click "Yes" to confirm that they want to exit from the Add POPFile User wizard. The "standard" user can then configure POPFile by using the Start Menu:
Start -- All Programs -- POPFile -- Run POPFile
For a clean install this will display the "Add POPFile User" wizard's language selection dialog box and this time the wizard's WELCOME page will mention the correct username.
This is only a workaround until I fix this "feature" properly.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can download and test 0.22.5 here:
http://popfile.sf.net/popfile-0.22.5RC4.zip
http://popfile.sf.net/popfile-0.22.5RC4-windows.zip
If this looks good to everyone I'll write up the release notes, spin an RC5 for final testing and we should be able to release.
Suggestions for what needs to go in the release notes?
John.
John,
The problems which I've reported on RC3 are all fixed on RC4!
Naoki
I've found a few problems with 0.22.5 RC4:
(1) When I added the most recent missing Perl component that Naoki reported I forgot to update the uninstaller. This means the component is unexpectedly left behind so the RC4 uninstaller has to ask for permission to remove the leftover file. CVS has been updated to fix this bug.
(2) The minimal Perl is still using an out-of-date Time::Local module (v1.11) which means the "Sec too big" bug has not been fixed (so warnings like "Sec too big - 29980 > 11647" may appear on the console when processing messages).
I have been using the v1.17 version of Time::Local (released January this year) which fixes this and several other bugs (in fact the function in question has been more or less re-written, if I remember correctly). PPM4 can get v1.17 of "Time-Local" from the "Bribes de Perl" repository.
The installer is using Time::Local from "site\lib" instead of the default "lib" folder so I'm not sure why RC4 has v1.11 (which is what is in the main "lib" folder on my system).
(3) If the installer is run from a "standard" account on Vista, the user will be prompted for an "administrator" password to allow the installer to write to the registry and "Program Files" folder etc.
This means the installer will think it is being run by the administrator account so when the "Add POPFile User" window appears offering to configure POPFile it will actually configure POPFile for the "administrator" user and _not_ the user who started the installer.
The wizard's WELCOME page mentions this ("This wizard will guide you through the configuration of POPFile for the <name of administrator account> user") but I guess most users won't notice that message :(
The "standard" user should click the "Cancel" button and then click "Yes" to confirm that they want to exit from the Add POPFile User wizard. The "standard" user can then configure POPFile by using the Start Menu:
Start -- All Programs -- POPFile -- Run POPFile
For a clean install this will display the "Add POPFile User" wizard's language selection dialog box and this time the wizard's WELCOME page will mention the correct username.
This is only a workaround until I fix this "feature" properly.
Brian