| carled 2004-02-13, 1:30 pm |
| Thought I'd add a helpful solution to this problem that DOESN'T involve
reinstalling windows
A C programmer friend of mine picked through the dll and isolated the cause of
the error. The dll falls over when inspecting the registry key
HKEY_CLASSES_ROOT/MIME/Database/Charset
You can immediately get around the crash by entirely deleting the 'charset''
key directory, however I'm not sure of the effect this would have on the
windows system! I deleted mine, exported the 'charset' key from a friends
registry, merged the exported key with my registry and all was fixed
The dll is programmed to just back out if it cannot find the charset key
structure, so it's a dirty fix, but it works
Now then, Macromedia... can I just say I am extremly unimpressed with your
attitude to this problem in the past. Just to say "it's someone elses problem,
not ours" is seriously unhelpful. YOU have included the dll file in your
software so YOU have some flipping responsibility to get involved in fixing the
problem
Now you have an idea where the problem is occurring, what about sending a nice
corporate email to the Apache XML lot and get them to root further into the
registry key to find the exact cause of the error, then they can issue a fix
that removes the corruption. Macomedia are likely to make far more progress
than an individual user, so I reckon you should do it
|