The problem is quite likely with what MS calls “virtual storage”.
BitComet has always stored its various settings and tasks in .xml files contained in the program directory, which is in the Program Files tree. That’s very common, but it’s also a very bad thing to do.
Windows is finally waking up to the idea, after twenty-five years, that it’s a bad idea for applications to be messing around in the execution environment, so has taken steps to hide it from you.
What LOOKS like “C:\Program Files...” is not. Instead, it’s off in your individual username folder in the “Documents and Settings” tree. You may want to read up on this.
Wherever those .xml files are actually located, if BitComet cannot write to them when it shuts down, then it obviously can’t read what it didn’t write when BC restarts. The reason we most often see for this inability to write the file is a permission problem with either the file or the directory it’s in.
Problema e cel mai probabil in legatura cu ce Microsoft numeste spatiu de “stocare virtuala” .
Bitcomet si-a salvat de fiecare data setarile si sarcinile in fisiere .xml aflate in folderul de instalare, care se afla in sectiunea Program Files. E un lucru des intalnit dar si rau.
Windows s-a trezit insfarsit cu idea, dupa douazeci si cinci de ani, ca e un lucru rau ca aplicatiile sa se joace prin mediul de executie, asa ca l-a ascuns de tine.
Ce ARATA ca “C:\Program Files...” nu e. Se afla in sectiunea pentru contul tau din folderul “Documents and Settings”. Poate mai cauti si tu informatii despre subiect.
Oriunde ar fi acele fisiere .xml, daca BitComet nu poate sa scrie pe ele atunci cand se inchide atunci evident ca nu va putea citi ce nu a scris cand pornste din nou. Motivul cel mai intalnit pentru care nu se poate modifica fisierul este o poblema cu permisia de a modifica fisierul sau folderul in care se afla.