Werner 回答說：
First, when you use IMGCELOGENABLE CeLog.dll is loaded very early in the
boot process, too early to read any registry info (as registry is not ready
yet at that time).
Second I see that you have set FlushTimeout=03e8. If you tell CeLogFlush to
use a timeout of 03e8 (1sec) it might be too fast.
What I do: Do not tick IMGCELOGENABLE, IMGOSCAPTURE, IMGAUTOFLUSH but add
celog.dll, oscapture.exe and celogflush.exe manually in your project.bib
(copy what you need to to from common.bib and common.reg). Make sure you add
the items in FILES section, not MODULES. Now CeLog.dll will only be loaded
when you run CelogFlsuh.exe or OSCapture.exe.As this is much later in the
boot process (I expect that the UI is up and running by then), CeLog.dll can
access the regsitry and load your registry settings. This way you can
increase the buffer size and leave the Flush Timeout to 10sec.
Are you using Celog in a DEBUG or RETAIL build? I have problems using CeLog
in DEBUG (together with VS + PlatformBuilder 6.0). After Celog.dll loads, it
crashes my image. In a RELEASE build everything works as expected.
Werner
沒有留言:
張貼留言