Save The Complete Download List

[Nihplod]

Is it some whay to save the list beucase my dc has crashed sometimes and my windows want to reboot sometimes. And after that i dont know what file is downloaded and what file that isnt downloaded.

I always removing the files from the Complete list when i have moved them away or burned them or something.... cant the list still be intact like the queue list after an reboot or such?...

Nihplod

[sarf]

Is [there] some [way] to save the [finished file] list [because] my [DC++ program] have crashed sometimes and my [OS (Windows)] wants to reboot sometimes. And after that I dont know what file is downloaded and what file isn't downloaded.

Currently, there is no way to save the finished file list. It's not impossible, it's just not done in DC++ at the moment.
I'd recommend you to used a finished file directory and an unfinished file directory. That way you'd know what files are complete depending on what path they have.

I always [remove] the files from the [finished file] list when I have moved them away or burned them or something.... Can't the list be [kept] intact like the queue list after an reboot or such?

Sure it can, but since it was "thrown in" as a nice and shiny feature it isn't. Besides, it would get huge in size at a very rapid pace. I'd recommend you to use the "log finished download" feature if you want to know what files have been downloaded.

Sarf
---
It is the wise bird who builds his nest in a tree.

[elakafarbrorn]

"Log downloads" is activated, however... last time dc++ crashed, no logfile was found in the logs directory... I am not sure abou this, but my guess is that the log is kept in memory while the program is running, and saved to disk only when closing the program --> No log when program crashes = Very annoying! Atleast autosave the log every 5 minutes, couldn't possibly be that resource demanding?

[GargoyleMT]

"Log downloads" is activated, however... last time dc++ crashed, no logfile was found in the logs directory.

Is your log directory set in the settings file? The logs aren't kept in memory, they're opened, written, and closed each time a line needs to be written to them. So the file is probably never opened due to some oddity in your logging settings.