Author Topic: Altbinz wont start  (Read 2953 times)

Offline Appel

  • Contributor
  • ***
  • Posts: 15
Altbinz wont start
« on: February 25, 2011, 03:20:27 pm »
I use version 0.35.1 which has always worked.

Now I want to start it, and it only starts in the windows tray (right bottom of screen), but I cannot open it. When I look in the proces list, the program takes up more than 50% of the CPU. Has anyone had the same problem?

« Last Edit: February 25, 2011, 04:23:40 pm by Ascathon »

Offline Appel

  • Contributor
  • ***
  • Posts: 15
Re: Altbinz wont start
« Reply #1 on: February 25, 2011, 03:30:34 pm »
Update to 0.35.2 gives the  same problem.
« Last Edit: February 25, 2011, 04:23:46 pm by Ascathon »

Offline Appel

  • Contributor
  • ***
  • Posts: 15
Re: Altbinz wont start
« Reply #2 on: February 25, 2011, 04:34:45 pm »
I hope I'm not spamming my own topic....

I installed 0.36.0 which is now out. The same problem, but I found out that it takes around 10 minutes to start Altbinz. The only thing changed on my PC is that I have a new directory with E-books that has several thousands of folders. Could it be that for some reason Altbinz looks through the harddrive to look for things, such as nzb files or so?

Offline Rdl

  • Administrator
  • *****
  • Posts: 4050
Re: Altbinz wont start
« Reply #3 on: February 25, 2011, 05:16:47 pm »
The only thing that comes to my mind is:

- nzb autoimport dir with lots of files in it.
- explorer tab default dir

Could you move that ebook folder somewhere else to try and figure out what's causing it. Then it can be fixed :)

Offline Appel

  • Contributor
  • ***
  • Posts: 15
Re: Altbinz wont start
« Reply #4 on: February 25, 2011, 08:16:27 pm »
Thanks for your reply Rdl. I don't have the autosearch on, I already found that option in another topic. However, at one moment it started working again. I had restarted my pc for at least 5 times and was looking into maybe setting back a restore point, or moving that folder, when it started to work as before again. Very weird, no explaination, but I'm happy it's working again.