The eccoMAGIC Forums
http://forums.eccoMAGIC.com/forum/YaBB.pl Ecco Tutorials, Tips and How-to Guides >> How do I ..... >> Latent Courruption problem ?? EM- ADT ?? What is all That ? http://forums.eccoMAGIC.com/forum/YaBB.pl?num=1210775568 Message started by Admin on 05/14/08 at 09:32:47 |
Title: Latent Courruption problem ?? EM- ADT ?? What is all That ? Post by Admin on 05/14/08 at 09:32:47 A summary of past threads: although not fully ready, was trying to do something incredibly simple, and stumbled upon something deeply complex, a latent error lurking in ... perhaps *many* ecco files (Found it even in the default.eco installed on my own system...). have added a (fairly) solid analysis/testing tool for the problem to the (likely) soon to be released deep diagnosis toolkit (which solves/helps solve memory issues, and such), and easy cure (in most cases) simply by recoving of DB (losing only color selections and other sim. options). but... more on that... later.... (for the time being, will upload a safe default.eco for those interested, although yours may be perfectly fine [you'll need tool to test-- which ... likely soon will be released].) interestingly, the latent corruption is almost viral in it's effect, 'spreading' to every new file if the default is indeed corrupted. but... more on that.... later... Looks very much like in many, (maybe in all?) of the original 4.01 default.ect files there is an internal, latent corruption. Trying to understand it (not having the source code), is complex & somewhat tricky. Looks like a problem with the internal structure pointers. The resulting files can get very complex in the structure... Soon will release a diagnostic tool to test/repair as part of larger diagnostics toolkit..... the corruption can give rise to a few strange errors, including 'lost' notepads, out of resource errors, etc... including some 'fatal' (ie. non-recoverable) errors, and some 'irritation errors' (need to close & re-open ecco). the corruption sits latent.... until triggered... (in the original template, and... *every* file created from it...) see http://tech.groups.yahoo.com/group/ecco_pro/message/2278 1. Ecco *should not* **EVER** give you that error. Something is wrong. most likely WITH THE FILE CAUSING THE ERROR!! A) Have you checked out all folder counts, etc.. for potential problems ? [soon will have an tool to help with this, filtering and sorting by space limitations, but.. slang ext. also should be easy enough to use for this purpose]. also Have you looked at the memory with EM Memory reporter ? B) if (A) is not an issue not that there is a known latent corruption problem with files created from the 'original' default.ect template or anything created from that. this may or may not be relevant.. Q: was this born of the default.ect ?? 2. if relevant, At eccoTools.com you can find a (FREE!!) single folder ecco install. You just unzip the files to any directory and you are in business. 3. would not worry about Mfc42.dll !!!! 4. in some cases the config files can cause problems.. so deleting the \windows directy based ecco files (alarms, etc.) as addressed in prior posts, can be helpful-- if that is the genesis of problem... (best to simply rename them, let ecco rebuild when run & you can restore them of they were not the cause of problem-- to not loose your custom toolbar, etc.). --- In ecco_pro@yahoogroups.com, "chefjohn1955" <yahoo@...> wrote: > > OK I am slowly Kludging my way through using Ecco Pro more fully. > (The ominous warnings from YSWT has me a little worried). > Just replace the file "default.ect" in the ecco program directory with "default.ect" file uploaded to the file section of the forum, and [certainly for all new files] ... all will be joyful. in fact, it's all GOOD news... the nasty latent corruption is detectable, *and* in most cases cureable. In worst cases may require an export & rebuild, but still... without actual data loss... > I would like to "archive" or slice it off or save to different disk > file or .... then if at some future date need that info then reload it > and cut & paste etc. > > So how do I do that? > there is an actual archive feature, which personally don't use, because it does not allow ADDING to an existing archive. If you set up columns correctly (ie. must have an outgoing transfer pad with *ALL* folders which contain any item info showing as a column. [if you have >100 such folders this technique will not work for you, and you will lose folder data for those folders not showing in columns]. then you simply use the COPY NOTEPAD WITH DATA feature, and *presto* you can duplicate all the data (minus ole attachments), in *any* other outline. If you have a special "archive" outline, you are all set. you then DELETE THE ITEMS in your 'transfer over' notepad, and they are gone from the original outline. you can then Delete the newly created notepad view in 'archive' notepad, as the DATA will not be deleted with the notepad delete. anyhow, this is the technique am using.... likely there are others as well.... Re: new Default.eco file suggestion --- In ecco_pro@yahoogroups.com, r634718 <no_reply@...> wrote: > > I think it's important to keep this "corruption" discussion in > perspective. > > A file can have some "corruption" and it might not make any > difference to you at all. You may never notice it, and it may never > cause you any problems. > exactly! no problems is good!. And, if you're suddenly having problems... and your memory limits and folder limits are good to go, very likely your file's is showing it's long hidden fault lines.. (as with the uploaded corrupt file giving errors with native style slang rule assignment setting). Like you, I seldom had *any* memory or ecco crash issues. (Interestingly, the couple I had-- raised in the forum .eco archive, turn out to be the fault of the default.ect latent corruption.) thanks to the HUGE advances that have been made on many ecco fronts, been using ecco MORE than ever. Suddenly have got 5-8 files open at once, doing things that would never have thought to do in the past... on Ecco. and... suddenly... was noticing all kinds of crashes, errors, etc... so many, in fact, that ecco became less than fun... and so just couldn't take it any more! It turns out that if just one file is corrupted, it can mess up the internal ecco pointers so that, even if you've closed it, you'll end up out of memory on the files (non-corrupted) you're left working on. There are some THRILLING! advances comming... tools that have for me, radically changed the range of use for which Ecco is now the perfect tool. As these new tools become available, and as we increase our ecco reliance, it really is important --> defective files will more and more make themselves known.. Maybe it's human nature to resist hearing about a problem we've been blind to for years. Maybe if a solution is free, and comes to us too easily, it's easy not to take it seriously. so..... pretend you paid $50.00 for the fixed template & enjoy it ! Re: Tutorial: Rescuing an Ecco data file The EM Advanced Diagnostics Toolkit has officially opened for PRE- REGISTRATION. <http://forums.eccomagic.com/forum/YaBB.pl?num=1201026516/0#0> the tool is being released as "HelpWare", which hopefully will be good for everyone. There is a huge amount that the toolkit will (most likely ;)) *eventually* do, beyond the cool and helpful stuff it does right now. *But*, since diagnosis of corrupted files [which 99.9999% of the time is because of the much talked about original default.ect defect which got transfered directly or indirectly (a corrupt file was loaded into Ecco, messing up internal ecco pointers, a 'clean file' was then saved from same ecco, resulting in messed up pointers in 'new' 'clean' file) or with some prior (hopefully now solved) injection of rules by the Slang extension.] is maybe critical, the toolkit is being 'pre-released' so all files are diagnosable for internal latent corruptions... toolkit also gives visual warning for folders in danger of reaching capacity, and some other stuff. ps: a pre-word of caution and warning. The advanced diagnosis uses in part stress testing to attempt to force the file being tested to break at the internal corruption pointers. If the pointers are not corrupt, file survives. highly recommended to MAKE A COPY of any file to be tested, DISCONNECT THAT COPY FROM ANY SYNC FILES, and test that, NOT the original. If file is corrupted and diagnostics tool forces 'break', you may not be able to fix the 'broken' version of the file.... After testing files I PERSONALLY CLOSE & RE-OPEN ECCO just to be sure. This is probably not necessary, but the interactions and pointers involved are super complex, and well, am not 100% sure! Note: The EM Memory Reporter and the EM Advanced Diagnostics Toolkit can be found at the EccoTools.com board. |
The eccoMAGIC Forums » Powered by YaBB 2.1! YaBB © 2000-2005. All Rights Reserved. |