Unable to open list at lists\permallow.p2b

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start PeerBlock with Windows

What is the expected output? What do you see instead?

Error dialog with message "Unable to open list at lists\permallow.p2b"

What version of PeerBlock are you using? On what operating system? 32- or
64-bit?

PeerBlock r131 - INTERIM RELEASE
Win XP 32 bit

Log file attached.

Original issue reported on code.google.com by joshpa...@gmail.com on 18 Sep 2009 at 9:51

Attachments:

• peerblock.log

[GoogleCodeExporter]

Currently experiences the same problem as "joshpaech" Same OS, Same steps that
produce the problem. Get the same message when starting up PeerBlock.I also 
received
this same error message with the last release of PeerBlock as well release
"PeerBlock, v0.9.1 (r71)" 

Original comment by anti-be...@hotmail.com on 18 Sep 2009 at 10:45

[GoogleCodeExporter]

Hmm, this might have been related to a bug in the older releases in which the
installer didn't used to copy over all static list-files from a pre-existing PG2
installation if you told it to transfer over the PG2 config.  Do either of you
remember if you instructed the installer to "Use PG2 settings" back when you 
first
installed PeerBlock?

You should be able to work around this by going into the List Manager, 
highlighting
the "lists\permallow.p2b" line, and clicking Remove.  Alternatively, if you 
still
have PG2 installed on your machine you can copy over the
"[PG2_install_dir]\lists\permallow.p2b" file, in case you had some IP addresses 
on
that list that you'd decided to "allow permanently".

Thanks for the problem report!

Original comment by peerbloc...@gmail.com on 19 Sep 2009 at 2:50

[GoogleCodeExporter]

Is this bug still affecting anybody?  I never heard back about the possibility 
that
this was related to an earlier problem transferring over a pre-existing PG2 
config,
and nobody's "Starred" it recently so I'm wondering it this is no longer an 
issue...?

Original comment by peerbloc...@gmail.com on 2 Nov 2009 at 4:14

[GoogleCodeExporter]

Sorry, forgot to report back.

I went into List Manager and removed permallow.p2b and all is fine.

I don't remember if I originally instructed the installer to use PG2 settings, 
but I
probably would have.

Original comment by joshpa...@gmail.com on 2 Nov 2009 at 6:34

[GoogleCodeExporter]

Okay, great, at this point I think I'll chalk it up to that earlier problem 
migrating
settings from old PG2 installations and close this bug.  If someone reports the
problem with recent releases, we can always reopen this bug.

Thanks for the followup!

Original comment by peerbloc...@gmail.com on 2 Nov 2009 at 1:46

• Changed state: Fixed