reminder: CAREFULLY READ THE EM-ADT instructions *before* using the tool. Many features (F5 folder & pointer scan, Orphan search, etc.) are designed to be safe to play with.
the "DEEP AND DESTRUCTIVE" test, is, well, called "DESTRUCTIVE" for a reason.
it is trying to stress out your file.
DON'T DO THAT TO YOUR ACTUAL FILES!!!
MAKE A COPY TO TEST WITH DEEP AND DESTRUCTIVE.
and with shared files---
safest to DISCONNECT THE COPY FROM THE MASTER FILE!!
(Note, very much UNLIKE the "DEEP AND DESTRUCTIVE" testing, the EM Memory Reporter, is 100% file SAFE.. does not change *anything* in your file structure.)
final note:
on 'new' 'unused' files, it is hard to properly 'stress' the pointers enough to 'break' the file in a way that can be confirmed.
normally this is not an issue.
in rare instance there can be a *tiny* pointer corruption (so far only seen in special case caused by particular LUA rule manipulation in conjuction with auto orphan detect) in a 'new' file that won't be detected by just single pass Deep & destructive.
ie. either you'll need to use that file a while, or need to run the D&D twice to have the tool pick up on the corruption.
so... to sum up:
1) Ecco files are VERY safe and stable.
2) the default template shipped with v4.01 (and maybe prior) has an internal pointer corruption, FIXED in new files by using the updated default template. NOTE: Ecco is so stable that THOUSANDS of internally corrupted files have been used for years with no data loss.
3) The EM-ADT will reveal (on single test) corruption on any file that has been used even minimally to enter and modify data. If you have a new-new file it is safe (unless something odd has happened, such as something strange with external tool or extension etc.).
if you create a 'fresh' template file and want to test it, TEST ON A COPY and run the deep & destructive twice in sequence.
please,
after doing D&D test, EXIT ECCO!! and restart.
please do NOT TEST D&D on your live files, only do D&D on copies.
(orphan test, F5, etc. is designed for LIVE files, just the "DEEP AND **DESTRUCTIVE**) is not.
EM-ADT instructions warn of this, explaining NOT to test on live file, and that you will not be happy with result if you do D&D on live files.
Edited: For those new to ecco, this is what is going on here:
Ecco was shipped with a 'defective' default template file. Since many used that default template to start *all* of their own .eco files, that defect was carried on like a virus into (for some people) *every* ecco file they use.
Since Ecco is so robust and SAFE, even though the files were corrupted, no one knew-- there was no problem or data loss that anyone could see.
Then the years passed... and for myself and many other heavy users, there started to be strange and unexplained problems, crashes, memory errors, etc.
The variety of problems is wide from error messages, to duplicate folders, to phantom items, to notepads that could never be deleted {had this one myself}.
We now have a cure-- the EM-ADT. But, since the defect is a deep pointer issue within ecco, a generalized tool to detect is very difficult. The solution is to stress the file and try to break it. If it can be broken under great stress, there is a pointer corruption. Thus, use the D&D testing only on a copy of your file, so that you can FIX your original file before it 'breaks'. Ie. the testing tries to break the file... if it succeeds the defect is revealed. Which is good, unless it is revealed on your live file! (since you'll have data loss!)
Pages: 1
note on using EM-ADT (Popularity: 17062 )
