![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
alexpgpClients have begun to call again, which is always a good thing, and the timing was impeccable. The only hiccup in the mix has been some strange new behavior in Word, causing the application to crash repeatedly unless started from the command line with the /a parameter, which prevents add-ins and templates from being loaded automatically.
Had the incoming assignment been more urgent, I would have had to run Word in this manner and then load Wordfast manually. The job did have a little slack in it, so I spent what ended up being too much time tracking down the solution, which involved a forum post that explained the crash as the result of an add-in or template looking for the wrong or a corrupted version of the wwlib.dll dynamic library (which sounded plausible, as Microsoft applied a particularly large Windows Update shortly before I left Baikonur; there may be no cause-and-effect, but my Fine Reader installation went south after the update was applied, too).
In any event, the forum post suggested that deleting the
So now I find myself with two jobs to be done "as soon as reasonably possible" - one of them breathing hotly down my neck as a result of today's pereginations - along with a "part B" to write for this week's LJ Idol.
However, given the increasingly short time periods that have been available to devote to LJ Idol over the past several weeks, I'm now to the (dangerous) point where I'm confident I'll come up with something. It wouldn't do for "part B" to behave like a petard.
Cheers...
Had the incoming assignment been more urgent, I would have had to run Word in this manner and then load Wordfast manually. The job did have a little slack in it, so I spent what ended up being too much time tracking down the solution, which involved a forum post that explained the crash as the result of an add-in or template looking for the wrong or a corrupted version of the wwlib.dll dynamic library (which sounded plausible, as Microsoft applied a particularly large Windows Update shortly before I left Baikonur; there may be no cause-and-effect, but my Fine Reader installation went south after the update was applied, too).
In any event, the forum post suggested that deleting the
HKEY_CURRENT_USER\Software\Microsoft\Office\version number\Word\Datakey for Word in the registry would solve the problem (since the key would be regenerated the next time Word was run). I followed the advice and the problem went away.
So now I find myself with two jobs to be done "as soon as reasonably possible" - one of them breathing hotly down my neck as a result of today's pereginations - along with a "part B" to write for this week's LJ Idol.
However, given the increasingly short time periods that have been available to devote to LJ Idol over the past several weeks, I'm now to the (dangerous) point where I'm confident I'll come up with something. It wouldn't do for "part B" to behave like a petard.
Cheers...
