warvair / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 1 forks source link

Installs in Win7 32bit, but everything disappears after reboot #227

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Download newest stable peerblock for windows 7
2. Install peerblock (have it start with windows or not, doesn't matter)
3. Restart Windows.  

What is the expected output? What do you see instead?
Peerblock to be somewhere on windows. Not only does it not start, the
directory for peerblock is non-existant; meaning there is no .exe for it to
even open it or any associated files.

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

Please provide any additional information below.  Make sure to attach
peerblock.log and/or any screenshots that would help explain your problem.

I have tried reinstalling twice and doing things slightly differently,
nothing works. I checked the task manager looking at all users...nothing.
Maybe there is a location I haven't thought of? I've done a search and I've
looked around for it.

Original issue reported on code.google.com by mikel52588 on 13 Dec 2009 at 5:09

GoogleCodeExporter commented 9 years ago
Just want to update this. I have found a way around the problem, but this issue 
is 
probably correlated with the whole need to run as admin/no windows service/not 
able 
to startup issues already noted. 

The way I got around it, is by unpacking everything and installing from that 
folder 
as admin (right-click run as admin). And that allowed everything to be 
continuously 
saved within that folder. So now I just have to go to the folder and open at 
startup. 
So its basically operating like a portable program. Maybe you guys should note 
some 
of this in your package? Anyways, thanks for a great program nonetheless. 

Original comment by mikel52588 on 15 Dec 2009 at 7:30

GoogleCodeExporter commented 9 years ago
Hmm, I'm a bit confused...  I had meant to update this bug earlier but 
apparently forgot.

Did you download the Installer package (the .exe version, the one-size-fits-all 
one
marked "recommended for most users"), or the "portable version" (the .zip 
version,
the one for which you needed to pick the right one for your version of 
Windows)?  The
.exe installer version should have actually *installed* it onto your system in
C:\Program Files\PeerBlock (by default), and an entry should have shown up both 
in
the Start Menu and inside Add/Remove Programs.

It sounds like you may have downloaded the .zip file instead, which is really 
only
meant for "portable" usage as you suggested.  This is actually a common 
mistake, we
*really* need to update that download page to break out the Portable version 
into its
own separate page to help minimize peoples' confusion as to what they should be
downloading...

Original comment by peerbloc...@gmail.com on 15 Dec 2009 at 8:46

GoogleCodeExporter commented 9 years ago
You are so right. I installed the zip package, I didn't realize that the .exe 
was a
one-size-fits-all ordeal. Thank you for clarifying that. I'm installing it 
right now. 

Just wondering, I don't know if this is a bug, something that can be avoided, or
something that's fixed; but with pg2 the history file used to grow to over a gig
after about a month of use. Even when I had it set to remove logs every 3 
days..so I
would have to uninstall and reinstall pg2. 
Is there an reason for this or something I may not of noticed?

Thank you.

Original comment by mikel52588 on 15 Dec 2009 at 9:44

GoogleCodeExporter commented 9 years ago
Alright, great, glad to hear that was the only problem - I just updated the 
download
page for our Stable Release, would you mind taking a quick look at it to see if 
it
better highlights the Installer download? 
(http://www.peerblock.com/releases/public-releases/peerblock-1.0.0-r181)

For the history file growth problem, we've fixed a few bugs in that area - it 
should
be working much better now in PeerBlock compared to PeerGuardian.  Our latest 
Beta
Release also includes the option to give PeerBlock a max filesize for 
history.db,
after which point it will delete or archive its contents (whatever you've 
specified).

Marking this bug as "Invalid" in order to close it, as this was the "portable
version" operating as intended.  You can still (I think) update it with a 
response
(or email me: http://tinymailto.com/peerblock), it simply won't show up in our 
list
of open issues.

Original comment by peerbloc...@gmail.com on 15 Dec 2009 at 10:23

GoogleCodeExporter commented 9 years ago
Ok that works. Thanks for the help and info. And the new download page is Much
better. Shouldn't have anymore confusion with that.

Original comment by mikel52588 on 15 Dec 2009 at 11:11