Squelch

How is this progressing? I'm just about to set up a new Tuxbox and would like to help if I can. I'm not a programmer, but do have passing knowledge of C++, networks and shell scripts, and have good fault finding skills with an eye for user interfaces. Any specific areas that need attention or research I'm happy to do. So a progress update with particukar problems and needs that need attention would be useful. [edit] Nevermind. I just managed to open the other thread http://forums.apexdc.net/index.php?showtopic=1065 I kept getting time outs for some reason and assumed it was a dead link. [/edit]

Hey Guys, My last post may have come over a bit terse. I was annoyed at having to fault find what I thought was a router problem, but was in fact Apex playing up. I always welcome new features and improvements, and in the past have suggested them. These new features and improvements need to be tested. After all that is what beta code is. The thing that concerned me the most was the fact that the new version had quickly been established as being unstable, but it was still the most predominant version on the download page two weeks later. Problems do happen and need to be fixed. Downgrading ver 1 to alpha, or flagging the possible problems on the news page would have saved me some time and hassle, and I hazard a guess, other users too. I hope you can fix the problem soon, and without too much hair pulling. I look forward to trying it out. I volunteer myself for testing anything you want to try out. Just don't scare off new customers with dodgy code on the front page :)

Is this anywhere near resolution, or is the advice still to roll back to the previous version? I just recently had cause to fire up Apex and downloaded the latest version 1.0.0 b2(auto update didn't see new ver) This was yesterday 23/04 I now have the same crash errors as other users here (exception.txt ommited for brevity) So the question is, why is a very unstable version still on the download page since the 10/04? I submit that a version jump from 0.4.0 to 1.0.0 would indicate a feature complete and major bug free version. Any new users to Apex might be very dissapointed, and therefore pass on the belief that it is very unstable. Does this issue only affect upgraded clients, or is it the same for new installs?

Hi darko79, I have the same problem and didn't spot that a username might be the problem. Are you able to open the filelists entry in the queue? Apex crashes as soon as I mouse over the entry. Tbh, the entry is redundant, because the queued filelists are shown in the progress window anyhow.

Hehe, which ones? I'll back them up so I don't lose the info, and see if the newly generated ones are useable.

That would explain it then. A misunderstanding in what the log would contain. I thought it might be the formatted transfer history for that user. Perhaps a change of option description to "Open User Message Log" or something might help. Thanks for clearing that up. Ps I can't edit topic title. It's not a bug so could someone change and move it to [support] instead.

Log analyser seems to freeze when processing the logs. It eventually gives up with an exception, and never gets past uploads.log. It's version 0.992 I might have corrupt logs. I can't view user logs from within Apex either. If anyone can confirm it works with Apex logs then I'll look into it further. I might have to resort to drastic measures and reinstall Apex. :thumbsup:

I'm not sure what you mean there. I have all logging turned on except personal and main chat. My config has the correct path too "\ApexDC++\Logs\" I just can't view them. I'm tempted to re-install Apex again but I have a big queue and don't want to lose all of the other data as well. :thumbsup:

I think the hash table is simply that. The file list references the index for that file in the table. I'm not sure if adding files different to the default tree would cause problems, but I'm only after a subset of the default tree so the files have been hashed anyhow. I had trouble with topic tool button after forum update too. Try a hard page reload (Ctrl-F5)

Hi guys, I've recently discovered the "Open user log" right click command in favorite users. Even though logs for that user are present, I receive "User log not exist". Is this a bug, or specific to my installation?

Hi all, Is there a log analyser that can be used with ApexDC++? I've tried DC++ Log Analyser, Clones DCStatGenerator, and dC++Lv. None of them seem to work with Apex logs. If there isn't such a beast, it might be worth a feature request or addon. Being able to identify for sure that a user that is always downloading, but never has an open slot for you would be very useful.

Ah! So it doesn't work out as I thought then. But surely if another user is queueing for that file, they get to connect on my disconnection. Does the slot remain opened? Is the pause user defineable?

Isn't the "Auto grant extra slot" option for favorite users a partial method of what bigcanuck is asking for? If this could be implemented hub wide on the enabled hub in favorites, wouldn't this achieve what is required regardless of multiple user id's on different hubs? If a truncated version of the default filelist is presented to a hub, then surely searches would still give the correct resposes to another user. If they are on another hub, and see the other content, then they could only download via your id on that hub. It appears to me, that the same user (even with different nick) on different hubs, is treated as different users even though they have the same content. Therefore changing the filelist presented as that user doesn't matter. Both of these seem related.

An update, Using the Automatically add downloaded files to share option has a big impact on performance. It appears that hashing the new file increases CPU usage greatly, and the disk io causes the freezing. Turning this option off improves the situation, but doesn't cure it completely.

I've noticed that using automatically add downloads to share does increase CPU usage. Hashing the new file does cause an apparent freeze. Turning this option off helped me a bit, but hasn't cured it totally.