Debug Zones question

I noticed that when running the debug version of CE6.0 (x86 or ARM BSPs) it
takes a long time to start up compared to 5.0. I believe that I need to
disable debug zones. I think one big culprit is KITL who appears to spit out
this on the debug port in an incredible rate:

Timer: Removing entry, slot: 15, expire: 4294952713
TimerEnt: slot 0, expire: 345400192

I read that I should be able to mask off zones in the
HKEY_LOCAL_MACHINE/DebugZones
From what I can discern from code the name should be KITL so I added
"KITL"=dword:1
to try and only display errors.

This does not seem to work. When I open CE Debug Zones window the other
zones under kitl.dll is still enabled. And messages are still displayed.

Anyone have any advice on this?

Daniel

Michel
Tue Jun 03 19:46:39 PDT 2008

Add it to your *development* PC:

[HKEY_CURRENT_USER\Pegasus\Zones]
"KITL"=dword:1

On the CE device should work as well, but you probably need it between
;HIVE BOOT SECTION tags so it is available in the boot hive.

Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Daniel Johansson wrote:
> I noticed that when running the debug version of CE6.0 (x86 or ARM BSPs) it
> takes a long time to start up compared to 5.0. I believe that I need to
> disable debug zones. I think one big culprit is KITL who appears to spit out
> this on the debug port in an incredible rate:
>
> Timer: Removing entry, slot: 15, expire: 4294952713
> TimerEnt: slot 0, expire: 345400192
>
> I read that I should be able to mask off zones in the
> HKEY_LOCAL_MACHINE/DebugZones
> From what I can discern from code the name should be KITL so I added
> "KITL"=dword:1
> to try and only display errors.
>
> This does not seem to work. When I open CE Debug Zones window the other
> zones under kitl.dll is still enabled. And messages are still displayed.
>
> Anyone have any advice on this?
>
> Daniel

DanielJohansson
Wed Jun 04 07:37:05 PDT 2008

Thank you for the advice. For some reason it still does not pick up my
adjustments, even after trying putting it on the desktop or making sure it is
put in the boot hive. I'm starting to think the KITL module is called
something different but the only dpCurSettings I could find that related to
KITL was called KITL. Is there a way to retrieve a list of the names? In the
CE debug zones dialog it only lists the name of the dll/exes.

"Michel Verhagen (eMVP)" wrote:

> Add it to your *development* PC:
>
> [HKEY_CURRENT_USER\Pegasus\Zones]
> "KITL"=dword:1
>
> On the CE device should work as well, but you probably need it between
> ;HIVE BOOT SECTION tags so it is available in the boot hive.
>
> Good luck,
>
> Michel Verhagen, eMVP
> Check out my blog: http://GuruCE.com/blog
>
> GuruCE Ltd.
> Microsoft Embedded Partner
> http://GuruCE.com
> Consultancy, training and development services.
>

Michel
Wed Jun 04 23:27:15 PDT 2008

Yes, use the Target Control window.

First get a list of modules: "gi mod"
Then find the module number in the list, let's say it is 34.
Then type "zo m 34". It will show you the registered debug name.



Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Daniel Johansson wrote:
> Thank you for the advice. For some reason it still does not pick up my
> adjustments, even after trying putting it on the desktop or making sure it is
> put in the boot hive. I'm starting to think the KITL module is called
> something different but the only dpCurSettings I could find that related to
> KITL was called KITL. Is there a way to retrieve a list of the names? In the
> CE debug zones dialog it only lists the name of the dll/exes.
>
> "Michel Verhagen (eMVP)" wrote:
>
>> Add it to your *development* PC:
>>
>> [HKEY_CURRENT_USER\Pegasus\Zones]
>> "KITL"=dword:1
>>
>> On the CE device should work as well, but you probably need it between
>> ;HIVE BOOT SECTION tags so it is available in the boot hive.
>>
>> Good luck,
>>
>> Michel Verhagen, eMVP
>> Check out my blog: http://GuruCE.com/blog
>>
>> GuruCE Ltd.
>> Microsoft Embedded Partner
>> http://GuruCE.com
>> Consultancy, training and development services.
>>
>

Michel
Wed Jun 04 23:32:55 PDT 2008

On my CE 6 kernel kitl was at M 38 and shows:

Windows CE>zo m 38
Registered Name:KITL CurZone:00008003
Zone Names - Prefixed with bit number and * if currently on
0*Warning : 1*Init : 2 Frame Dump : 3 Timer

4 Send : 5 Receive : 6 Retransmit : 7 Command

8 Interrupt : 9 Adapter :10 LED :11 DHCP

12 OAL :13 Ethernet :14 Unused :15*Error




Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Michel Verhagen (eMVP) wrote:
> Yes, use the Target Control window.
>
> First get a list of modules: "gi mod"
> Then find the module number in the list, let's say it is 34.
> Then type "zo m 34". It will show you the registered debug name.
>
>
>
> Good luck,
>
> Michel Verhagen, eMVP
> Check out my blog: http://GuruCE.com/blog
>
> GuruCE Ltd.
> Microsoft Embedded Partner
> http://GuruCE.com
> Consultancy, training and development services.
>
> Daniel Johansson wrote:
>> Thank you for the advice. For some reason it still does not pick up my
>> adjustments, even after trying putting it on the desktop or making
>> sure it is put in the boot hive. I'm starting to think the KITL module
>> is called something different but the only dpCurSettings I could find
>> that related to KITL was called KITL. Is there a way to retrieve a
>> list of the names? In the CE debug zones dialog it only lists the name
>> of the dll/exes.
>>
>> "Michel Verhagen (eMVP)" wrote:
>>
>>> Add it to your *development* PC:
>>>
>>> [HKEY_CURRENT_USER\Pegasus\Zones]
>>> "KITL"=dword:1
>>>
>>> On the CE device should work as well, but you probably need it
>>> between ;HIVE BOOT SECTION tags so it is available in the boot hive.
>>>
>>> Good luck,
>>>
>>> Michel Verhagen, eMVP
>>> Check out my blog: http://GuruCE.com/blog
>>>
>>> GuruCE Ltd.
>>> Microsoft Embedded Partner
>>> http://GuruCE.com
>>> Consultancy, training and development services.
>>>
>>

DanielJohansson
Fri Jun 06 07:19:01 PDT 2008

Thank you! Very useful!

This is interesting, when I do the same (kitl.dll was 37 on mine) I get this:
Registered Name:OAL CurZone:00000000
Zone Names - Prefixed with bit number and * if currently on
0 Error : 1 Warning : 2 Function : 3 Info

4 Stub/Keyv/Args : 5 Cache : 6 RTC : 7 Power

8 PCI : 9 Memory :10 IO :11 Timer

12 IoCtl :13 Flash :14 Interrupts :15 Verbose

Even so, it does not seem to react to either OAL nor KITL, in the targets
DebugZones or the desktops Pegasus registry keys.

Am I the only one with this problem? It really starting to seem that I may
have a corrupt installation or something...

"Michel Verhagen (eMVP)" wrote:

> On my CE 6 kernel kitl was at M 38 and shows:
>
> Windows CE>zo m 38
> Registered Name:KITL CurZone:00008003
> Zone Names - Prefixed with bit number and * if currently on
> 0*Warning : 1*Init : 2 Frame Dump : 3 Timer
>
> 4 Send : 5 Receive : 6 Retransmit : 7 Command
>
> 8 Interrupt : 9 Adapter :10 LED :11 DHCP
>
> 12 OAL :13 Ethernet :14 Unused :15*Error
>
>
>
>
> Good luck,
>
> Michel Verhagen, eMVP
> Check out my blog: http://GuruCE.com/blog
>
> GuruCE Ltd.
> Microsoft Embedded Partner
> http://GuruCE.com
> Consultancy, training and development services.
>

Travis
Fri Jun 06 15:04:21 PDT 2008

I'm assuming you're just using the reference BSPs. If that's not the case,
is it possible that a function in your BSP is periodically setting the zones
to some default?

--
--Travis Hobrla
http://blogs.msdn.com/ce_base/

This posting is provided "AS IS" with no warranties, and confers no rights.
"Daniel Johansson" <DanielJohansson@discussions.microsoft.com> wrote in
message news:699227F6-05BE-4C40-BD07-1EB821364EB7@microsoft.com...
> Thank you! Very useful!
>
> This is interesting, when I do the same (kitl.dll was 37 on mine) I get
> this:
> Registered Name:OAL CurZone:00000000
> Zone Names - Prefixed with bit number and * if currently on
> 0 Error : 1 Warning : 2 Function : 3 Info
>
> 4 Stub/Keyv/Args : 5 Cache : 6 RTC : 7 Power
>
> 8 PCI : 9 Memory :10 IO :11 Timer
>
> 12 IoCtl :13 Flash :14 Interrupts :15 Verbose
>
> Even so, it does not seem to react to either OAL nor KITL, in the targets
> DebugZones or the desktops Pegasus registry keys.
>
> Am I the only one with this problem? It really starting to seem that I may
> have a corrupt installation or something...
>
> "Michel Verhagen (eMVP)" wrote:
>
>> On my CE 6 kernel kitl was at M 38 and shows:
>>
>> Windows CE>zo m 38
>> Registered Name:KITL CurZone:00008003
>> Zone Names - Prefixed with bit number and * if currently on
>> 0*Warning : 1*Init : 2 Frame Dump : 3 Timer
>>
>> 4 Send : 5 Receive : 6 Retransmit : 7 Command
>>
>> 8 Interrupt : 9 Adapter :10 LED :11 DHCP
>>
>> 12 OAL :13 Ethernet :14 Unused :15*Error
>>
>>
>>
>>
>> Good luck,
>>
>> Michel Verhagen, eMVP
>> Check out my blog: http://GuruCE.com/blog
>>
>> GuruCE Ltd.
>> Microsoft Embedded Partner
>> http://GuruCE.com
>> Consultancy, training and development services.
>>

DanielJohansson
Mon Jun 09 07:13:02 PDT 2008

I'm using reference BSPs yes. I don't think so because I'm using two
different BSPs for two different platforms from two different vendors. Unless
they have happened to have changed the same thing which seems unlikely.

"Travis Hobrla" wrote:

> I'm assuming you're just using the reference BSPs. If that's not the case,
> is it possible that a function in your BSP is periodically setting the zones
> to some default?
>
> --
> --Travis Hobrla
> http://blogs.msdn.com/ce_base/
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Daniel Johansson" <DanielJohansson@discussions.microsoft.com> wrote in
> message news:699227F6-05BE-4C40-BD07-1EB821364EB7@microsoft.com...
> > Thank you! Very useful!
> >
> > This is interesting, when I do the same (kitl.dll was 37 on mine) I get
> > this:
> > Registered Name:OAL CurZone:00000000
> > Zone Names - Prefixed with bit number and * if currently on
> > 0 Error : 1 Warning : 2 Function : 3 Info
> >
> > 4 Stub/Keyv/Args : 5 Cache : 6 RTC : 7 Power
> >
> > 8 PCI : 9 Memory :10 IO :11 Timer
> >
> > 12 IoCtl :13 Flash :14 Interrupts :15 Verbose
> >
> > Even so, it does not seem to react to either OAL nor KITL, in the targets
> > DebugZones or the desktops Pegasus registry keys.
> >
> > Am I the only one with this problem? It really starting to seem that I may
> > have a corrupt installation or something...
> >
> > "Michel Verhagen (eMVP)" wrote:
> >
> >> On my CE 6 kernel kitl was at M 38 and shows:
> >>
> >> Windows CE>zo m 38
> >> Registered Name:KITL CurZone:00008003
> >> Zone Names - Prefixed with bit number and * if currently on
> >> 0*Warning : 1*Init : 2 Frame Dump : 3 Timer
> >>
> >> 4 Send : 5 Receive : 6 Retransmit : 7 Command
> >>
> >> 8 Interrupt : 9 Adapter :10 LED :11 DHCP
> >>
> >> 12 OAL :13 Ethernet :14 Unused :15*Error
> >>
> >>
> >>
> >>
> >> Good luck,
> >>
> >> Michel Verhagen, eMVP
> >> Check out my blog: http://GuruCE.com/blog
> >>
> >> GuruCE Ltd.
> >> Microsoft Embedded Partner
> >> http://GuruCE.com
> >> Consultancy, training and development services.
> >>
>
>

Travis
Tue Jun 10 09:15:31 PDT 2008

Sorry, I missed something in my initial response - I don't expect that the
desktop registry key will actually work. That is read when a module calls
DEBUGREGISTER, but since the OAL and KITL initialize before the debugger is
active, DEBUGREGISTER is not called.

Take a look at this for more information:
http://blogs.msdn.com/ce_base/archive/2006/12/22/kitl-and-oal-debug-messages-in-windows-ce6-0.aspx

I would still expect you'd be able to change them using the 'zo' command
once the system was up and running. Of course, at that point, much of the
OAL and KITL code has already run.

--
--Travis Hobrla
http://blogs.msdn.com/ce_base/

This posting is provided "AS IS" with no warranties, and confers no rights.
"Daniel Johansson" <DanielJohansson@discussions.microsoft.com> wrote in
message news:046EDE35-4197-4DA2-8D1B-0C7C35FB1999@microsoft.com...
> I'm using reference BSPs yes. I don't think so because I'm using two
> different BSPs for two different platforms from two different vendors.
> Unless
> they have happened to have changed the same thing which seems unlikely.
>
> "Travis Hobrla" wrote:
>
>> I'm assuming you're just using the reference BSPs. If that's not the
>> case,
>> is it possible that a function in your BSP is periodically setting the
>> zones
>> to some default?
>>
>> --
>> --Travis Hobrla
>> http://blogs.msdn.com/ce_base/
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Daniel Johansson" <DanielJohansson@discussions.microsoft.com> wrote in
>> message news:699227F6-05BE-4C40-BD07-1EB821364EB7@microsoft.com...
>> > Thank you! Very useful!
>> >
>> > This is interesting, when I do the same (kitl.dll was 37 on mine) I get
>> > this:
>> > Registered Name:OAL CurZone:00000000
>> > Zone Names - Prefixed with bit number and * if currently on
>> > 0 Error : 1 Warning : 2 Function : 3 Info
>> >
>> > 4 Stub/Keyv/Args : 5 Cache : 6 RTC : 7 Power
>> >
>> > 8 PCI : 9 Memory :10 IO :11 Timer
>> >
>> > 12 IoCtl :13 Flash :14 Interrupts :15 Verbose
>> >
>> > Even so, it does not seem to react to either OAL nor KITL, in the
>> > targets
>> > DebugZones or the desktops Pegasus registry keys.
>> >
>> > Am I the only one with this problem? It really starting to seem that I
>> > may
>> > have a corrupt installation or something...
>> >
>> > "Michel Verhagen (eMVP)" wrote:
>> >
>> >> On my CE 6 kernel kitl was at M 38 and shows:
>> >>
>> >> Windows CE>zo m 38
>> >> Registered Name:KITL CurZone:00008003
>> >> Zone Names - Prefixed with bit number and * if currently on
>> >> 0*Warning : 1*Init : 2 Frame Dump : 3 Timer
>> >>
>> >> 4 Send : 5 Receive : 6 Retransmit : 7
>> >> Command
>> >>
>> >> 8 Interrupt : 9 Adapter :10 LED :11 DHCP
>> >>
>> >> 12 OAL :13 Ethernet :14 Unused :15*Error
>> >>
>> >>
>> >>
>> >>
>> >> Good luck,
>> >>
>> >> Michel Verhagen, eMVP
>> >> Check out my blog: http://GuruCE.com/blog
>> >>
>> >> GuruCE Ltd.
>> >> Microsoft Embedded Partner
>> >> http://GuruCE.com
>> >> Consultancy, training and development services.
>> >>
>>
>>