New Mail Notification Keeps Enabling Itself

[Protocol]

I disable the New Mail notification in Tools > Options > Notification, but after a computer restart, the setting is enabled again.
Is there some way to make this setting stick?

OS: Windows 10 64-bit.

[Jeff]

There's a very good chance that you have the same problem source as another recent topic:
http://www.esumsoft.com/Forums/viewtopic.php?f=3&t=6347
Basically, if you have installed POP Peeper in the C:\Program Files... folder, and PP is trying to save data in that folder, then Windows is preventing any files from being saved because of UAC.

You'll have to follow the same advice that lakrsrool referred to:
http://www.esumsoft.com/Forums/viewtopi ... ath#p31360

[Protocol]

You'll have to follow the same advice that lakrsrool referred to:
http://www.esumsoft.com/Forums/viewtopi ... ath#p31360

I tried doing this, but the poppeeper.ini path won't change from C:\Program Files (x86)\POP Peeper. I am unable to manually change it.

[mjs]

After following each of the delineated steps in the link provided prior to which you would have exited Pop Peeper before going through these specific enumerated steps, did you then restart Pop Peeper and go to "Tools" > "Options" > "Storage" and delete the value for the data path?

Doing this will reset the directory path to the default "application folder".

[Protocol]

Yes, I did exactly that.

[mjs]

Oh, I just noticed you stated "poppeeper.ini path won't change.... ", OK so you're talking about the "ini location", so then that means you did the first procedure?:
1)
- Exit POP Peeper
-Move the folder:
C:\Program Files (x86)\POP Peeper\
to somewhere that isn't protected by UAC, e.g.
C:\POP Peeper\

If so, you did a "move" of the folder and not a "copy", right?

You don't want to leave a path that includes "Program files".

And where did you "move" it, (what is the path now). If you moved it to anywhere that does not include "c:/Program Files", you should be OK.

If you continue to have problems Here is a more detailed procedure to follow:
Again you need to move the file (NOT COPY IT)
Step 1.) In POP Peeper's main menu, select "Tools" > "Options"
Step 2.) Select the "Storage" page
Step 3.) Note the "Ini Location" ---> If the ini location does not start with "C:\Program Files" then do not continue (continue if C:\Program Files)
Step 4.) Exit POP Peeper
Step 5.) MOVE (so that the original file is no longer there) the ini file noted in step #3 to: %userprofile%\AppData\Roaming\POP Peeper
-----> To do this do the following:
-----> A) Copy that line above (in red) and enter it into the Windows "Run prompt" (start>run) to open the correct folder in Windows Explorer
-----> B) Note: The "POP Peeper" folder may not exist, in which case, you should open the parent folder (%userprofile%\AppData\Roaming\), and create "POP Peeper"; now move (drag) the ini file (poppeeper) from where it is now to this new location (not copy)
Step 6.) Restart POP Peeper
Step 7.) Go to "Tools" > "Options" > "Storage" and make sure that the "ini location" is now "C:\users\[username]\AppData\Roaming\POP Peeper\poppeeper.ini"
Step 8.) Also, while you're at this point, make sure you reset the value in the data path, you should remove it so the value is empty and press OK

[Protocol]

I did No. 2

2) or, Move the ini file and data folder:

- Exit POP Peeper
- Move the ini file from:
C:\Program Files (x86)\POP Peeper\poppeeper.ini
to:
%userprofile%\AppData\Roaming\POP Peeper
- Restart POP Peeper
- Go to Tools / Options / Storage and delete the value for the data path, this will reset it to the AppData folder

[Jeff]

It's perfectly fine that you did #2 -- it's actually more proper for Windows.

However, if you did it correctly, then the ini file should not exist under:
C:\Program Files (x86)\POP Peeper\
And after you restart POP Peeper, the path displayed under Options / Storage will not display that. If it continues to display that location, then the file is still there. The file must be *moved* so that it is no longer exists under "Program Files". POP Peeper will look for and use the file in that location first.

[Jeff]

Just to clarify -- you must manually move the poppeeper.ini file yourself using Windows Explorer.

[Protocol]

Yes Jeff, I moved the file manually.
It is a simple enough procedure, but the procedure doesn't have the outcome you are expecting, because the path still shows C:\Program Files (x86)\POP Peeper\.

[mjs]

Protocol, would you please do the following below.

Using your Windows Explorer: Under "My Computer", left-click on "Local Disk (C:)" (from now on double-left-click on the following folders), in the right pane double-left-click on the folder "Program Files (x86)", then scroll down until you find the "Pop Peeper" folder and double-left-click on "Pop Peeper" then in the upper right search box type in "poppeeper" without the quotes (see image below, click on images to enlarge if necessary, then click the go back arrow to return to previous page):

Search Windows Explorer for poppeeper

Now tell me if you see a file listed in the right pane of the Windows Explorer that looks the same as you see below where the file name is "poppeeper" and the file type is "Configuration settings":

poppeeper configuration file

poppeeper configurations settings file.png (3.05 KiB) Viewed 8642 times

You should NOT find this file at this location, that is if you had "moved" that same file as described in the 2nd step of the instructions that you used.

If you click on "start" and then click on "run..." then type into the run box: %userprofile%\AppData\Roaming\POP Peeper

You should see the following (if you had "moved" the file as described):

Where poppeeper configuration file should be located

Keep in mind we are not talking about poppeeper.ini.bak, we are only talking about the poppeeper file as illustrated above.

If you follow the 8 steps posted above (keep in mind in step 4 you need to exit Pop Peeper by right-clicking on the Pop Peeper icon in the systray and selecting "exit") then you should not have any problems. Note when you find where the ini file is supposed to go by using the "run" command you must keep that location in mind so that you know where the file should be moved when you go back to where the ini file is located currently (in the right pane of Windows Explorer) to move it (drag) to the new location where it should be that you find in the left pane of Windows Explorer.

[Jeff]

lakrsrool brings up a good point about the correct file. I always show the file extension and I tend to forget that it's not the default (why does Windows continue to make this the default... it doesn't help anybody!). So, hopefully that's what the problem is. The end result is -- if POP Peeper continues to show the ini file under "Program Files", then it must still be finding that file there.


btw, once you get PP to use the ini file under C:\Users\..., don't forget this step:
- Go to Tools / Options / Storage and delete the value for the "data path"; this will reset it to the AppData folder
(but don't do that until the ini file is fixed)

[Protocol]

Thanks lakrsrool & Jeff.

Thanks lakrsrool for the in depth and dumbed down instructions, but I have done all that, but with the same result as previous post.

And yes, you are right Jeff. File extensions should be on by default. It is the first thing I turn on after a fresh Windows installation.
Even better is to use Directory Opus.

[mjs]

So then to clarify one last time, using Windows Explorer you do not see any "poppeeper" configuration settings file anywhere at all in the path: C:\Program Files (x86)\Pop Peeper\, even though the Pop Peeper .ini file location path setting does actually display this path in the Pop Peeper "storage" interface

And you do actually see the "poppeeper" configuration settings file in the path: C:\Users\[username]\AppData\Roaming\POP Peeper\ (where you presumably moved the file)

If this is the case then hopefully Jeff will come up with something regarding this very odd situation tomorrow.

[Jeff]

Protocol -- does the problem only occur when you restart Windows or also when you start/exit PP? In the procedures we've been using, you should not exit Windows completely; you just need to exit and restart POP Peeper. So, if you:
1) Exit POP Peeper
2) Move the ini file
3) Restart POP Peeper

Answer these:
- Are your settings/accounts all the same just as before step #1 above?

- If you go to main menu: Tools / Options / Storage, does it still say that the "Ini Location" is:
C:\Program Files (x86)\POP Peeper\poppeeper.ini

- If you go to that folder (using WinExplorer or Directly Opus), is there now an ini file that wasn't there before (ie. after step #2 above)?

[Protocol]

So then to clarify one last time, using Windows Explorer you do not see any "poppeeper" configuration settings file anywhere at all in the path: C:\Program Files (x86)\Pop Peeper\, even though the Pop Peeper .ini file location path setting does actually display this path in the Pop Peeper "storage" interface

And you do actually see the "poppeeper" configuration settings file in the path: C:\Users\[username]\AppData\Roaming\POP Peeper\ (where you presumably moved the file)

If this is the case then hopefully Jeff will come up with something regarding this very odd situation tomorrow.

Correct.

[Protocol]

Protocol -- does the problem only occur when you restart Windows or also when you start/exit PP? In the procedures we've been using, you should not exit Windows completely; you just need to exit and restart POP Peeper. So, if you:
1) Exit POP Peeper
2) Move the ini file
3) Restart POP Peeper

Answer these:
- Are your settings/accounts all the same just as before step #1 above?

- If you go to main menu: Tools / Options / Storage, does it still say that the "Ini Location" is:
C:\Program Files (x86)\POP Peeper\poppeeper.ini

- If you go to that folder (using WinExplorer or Directly Opus), is there now an ini file that wasn't there before (ie. after step #2 above)?

1. Yes
2. Yes
3. Yes. It keeps making a new poppeeper.ini in C:\Program Files (x86)\POP Peeper\

[Jeff]

Sorry, but this doesn't make any sense. If the file doesn't exist under "Program Files", then POP Peeper should not be able to load the same configuration. Further, since POP Peeper is unable to write to that folder, it can't save a new file there either (ie. it's not POP Peeper that's creating the file again).

Possible explanations:
1) You're not actually exiting POP Peeper when you move the file. This would explain why when you "restart" POP Peeper, it still has the same configuration -- you're not actually restarting PP, but you're opening the instance of PP that's already running. However, this by itself isn't an explanation because it wouldn't explain why the file is still there.

2) You're only copying -- not moving -- the ini file. Or you're moving the wrong file. I think this is the most likely explanation.

3) Something external is restoring the file -- a restore point or some other restoration. I wouldn't think that this is likely if you're following the "exit/move/restart" procedure in immediate sequence.

If you think you're doing it correctly, here's what I suggest so that we can see what's happening:

1) Exit POP Peeper
2) Move the ini file
3) Take a screenshot of the "c:\Program Files (x86)\POP Peeper\" folder -- make sure the window is big enough to show all the files and folders in there. I'd prefer if you used WinExplorer instead of Directory Opus, simply because I'm not familiar with the latter and don't know what it's capable of.
4) Restart POP Peeper
5) Go to Tools / Options / Storage and take a screenshot of that.

Post both those screenshots.