missing list of s w2a6d

[Tiger.711]

1. Missing list of s. Screenshot:

2. Problem occurs after an program crashing while creating a list of from site using the site spider.
3. Normal start with all my s
4. Windows7 x64
5. FDM 3.9.1537.0

[Alex]

Hello,
It's a bug of 1537 build.

[Tiger.711]

I have updated FDM to version 3.9.1559.0
Error occurs again.

[Usher]

Installing a new FDM build won't fix your broken *.sav files, I'm afraid. You should do tests on a clean install - create a new Windows , to it and only then run tests.

[Tiger.711]

How can I fix my broken *.sav files?
Is it any tools for that, or should I use something like Notepad++?

[Usher]

Service files in FDM are binary files, there is no tool to fix them. But you did the backup, didn't you?

If you suspect that only one file is broken, you can restore it from your backup or replace it with empty file from your new WIndows .

In most cases of crashes reported in older topics the service files were not broken, they were just too big for FDM to manage them properly.
If it is your case (file sizes greater than 2 MB), you can manually delete unneeded entries from list, history list and recycle bin in FDM. You can also open FDM menu Options | Settings | General | History and set limits there (recommended for the future) or use "Clean history" buttons (good enough for now). When you restart FDM, the program will definitely remove deleted or expired entries from service files.

[Alex]

Hello,

Follow this instruction to fix your SAV files:
viewtopic.php?p=40412#p40412

[Tiger.711]

Hello,

Follow this instruction to fix your SAV files:
http://freemanager.sitesdebloques.org/board/vi ... 412#p40412

This solution doesn-t solve the problem. Error still occures.

[Tiger.711]

Perhaps, I should send sav-files to you?

[Usher]

Follow this instruction to fix your SAV files:
http://freemanager.sitesdebloques.org/board/vi ... 412#p40412

This solution doesn-t solve the problem. Error still occures.

You should expect that special FDM Build 1538 can fix only errors caused by bugs in 1537 build (or earlier builds). Build 1538 cannot fix all errors caused by build 1537 if *.sav files were updated by newer FDM builds.

Note that I can only guess what is going on, because you haven't provide enough details. What FDM version do you use now? Have you problems with newly created *.sav file or maybe you are still trying to use old broken *.sav files?
Have you checked your hardware (HDD, RAM) and file system on your partition? Do you close FDM before shutting down your system? Have you properly configured your antivirus, antimalware or other internet security software, if you use any?