Daniel Veditz wrote:
> barney wrote:
>>
>> I recently started downloading win32 talkback nightlies again now that
>> they've shrunk down to a more tolerable size. I've had a couple of
>> crashes, but talkback didn't kick in. Then I noticed a message in the
>> console log when mozilla starts up: talkback can't initialize.
>>
>> I've just been unzipping the nightlies and starting up mozilla without
>> ever running -installer. Seems to me this worked just fine in the past,
>> but it's been a while, so I could be wrong. I'm just carrying over
>> profiles that are already migrated. Is it necessary to run -installer
>> with a new build, or is something else most likely the problem?
>
> Unzipping the nightlies on top of an old build may leave junk around. It
> also will probably not give Mozilla any reason to re-register components to
> discover any new things that were added that day. Delete component.reg each
> time, or use the -installer flag. There won't be any problems re-migrating
> your profiles, Mozilla knows which ones it has migrated.
>
> -Dan Veditz
I always unzip into clean directories, remove mozregistry.dat and
mozver.dat before trying a new build so leftover junk should not be the
culprit. This morning I removed the bin folder, unzipped again and ran
-installer. The console log shows:
I am inside the initialize
Hey : You are in QFA Startup
(QFA)Talkback error: Can't initialize.
I'm currently on build 0316, but get the same thing on other recent
builds. Is it possible that there is some other leftover junk hanging
around from an old win-installer.exe build that might cause it? I've had
both zip and installer versions coexisting before without it affecting
talkback.
