Xscale, PSM & Hive Registry

I've run into a strange condition on two different reference platforms, both
based on the PXA255 cpu, but using different code bases under CE .Net 4.1
(one is the Wince 4.1 XSC1BD, the other is a 3rd party package).

Both platforms worked fine with RAM based registries. Then I switched over
to Hive based registries, with the hives stored in the PSM file system.

To enable and disable the PSM as the destination for the Hives, I either set
to 1 or 0, respectively, the "Start DevMgr" value under
[HKEY_LOCAL_MACHINE\Init\BootVars].

If I enable the Hive on PSM, the system generates several DEBUGCHKs while
booting, and I lose the use of ActiveSync over USB on one device. The USB
driver appears to be loaded and running, but I cannot connect to the
desktop, and if I open the Networking control panel and try to manually
create a new connection, the USB device is not shown as an option. On the
second system, I lose use of the Compact Flash slot.

If I disable the device manager ( so the Hive winds up in RAM), everything
works just fine.

In both systems, I delete the Hive stored in the PSM, re-enable the device
manager (just to be sure I'm not looking at leftover/old registry data).

I also downloaded and exported the registries, both with and without the
device manager active. I did notice something different between the two:

With the one with the device manager active (i.e. USB not functional), the
two following keys exists that were not in the other version:

[HKEY_LOCAL_MACHINE\Drivers\Active\15]
"Hnd"=dword:003ad7f0
"Key"="Drivers\\BuiltIn"
"ClientInfo"=dword:00000000

[HKEY_LOCAL_MACHINE\Drivers\Active\21]
"Hnd"=dword:003ad860
"Key"="Drivers\\BuiltIn\\TAPI"
"ClientInfo"=dword:00000000


The DEBUGCHK messages are:

4294785347 PID:23ad28e6 TID:23ad28c2 0x83ad2684: RegisterAPISet failed for
api set id 23.

4294785349 PID:23ad28e6 TID:23ad28c2 0x83ad2684: Unknown: DEBUGCHK failed in
file d:\jameson\private\winceos\comm\tapi\tapi\init.c at line 643



4294787589 PID:23ad28e6 TID:23ad28c2 0x83ad2684: RegisterAPISet failed for
api set id 19.

4294787590 PID:23ad28e6 TID:23ad28c2 0x83ad2684: Unknown: DEBUGCHK failed in
file d:\jameson\private\winceos\comm\pm\lib\peginit.c at line 402



4294789722 PID:23ad28e6 TID:c39a7fd6 0x83998400: Unknown: DEBUGCHK failed in
file d:\jameson\private\winceos\comm\pm\lib\buffers.c at line 256



Any idea what this is about?

Thanks

Steve
Thu Sep 25 07:35:38 CDT 2003

What version of PSM. Is demand paging for PSM storage enabled? There were
issues with earlier versions of PSM in V4.x where demand paging was not
supported. This is a requirement of any device you wish to put the hive
registry on to.

--
Steve Maillet (eMVP)
Entelechy Consulting
smaillet_AT_EntelechyConsulting_DOT_com

Pete
Thu Sep 25 09:44:17 CDT 2003

Thanks for the reply, Steve.

I'm using PSM version 3.53. I also have 3.62 (once we upgrade to WinCE
4.2)... but I looked in the notes and didn't notice either version
mentioning a fix for demand paging. Do you know if that problem was ever
fixed by Intel?


"Steve Maillet (eMVP)" <nospam1@EntelechyConsulting.com> wrote in message
news:uPGWJI2gDHA.1648@TK2MSFTNGP10.phx.gbl...
> What version of PSM. Is demand paging for PSM storage enabled? There were
> issues with earlier versions of PSM in V4.x where demand paging was not
> supported. This is a requirement of any device you wish to put the hive
> registry on to.
>
> --
> Steve Maillet (eMVP)
> Entelechy Consulting
> smaillet_AT_EntelechyConsulting_DOT_com
>
>

Martin
Thu Sep 25 15:09:32 CDT 2003

There is an issue in 4.1 caused by PSM starting too quickly for hive. I
can't remember all the detals right now, but a result is that not all
devices are loaded correctly. A work around is to add a delay when PSM
loads. You can do this by adding a file system filter driver to PSM - we
used the fsdspy example and called Sleep() in FILTER_HookVolume.
Or you could move to 4.2 - it's been fixed there.


"Pete Gabrail"
<peteg.you.have.to.remove.these.words@rticorp.take.this.out.com> wrote in
message news:3f721cd2$0$174$a1866201@newsreader.visi.com...
> I've run into a strange condition on two different reference platforms,
both
> based on the PXA255 cpu, but using different code bases under CE .Net 4.1
> (one is the Wince 4.1 XSC1BD, the other is a 3rd party package).
>
> Both platforms worked fine with RAM based registries. Then I switched
over
> to Hive based registries, with the hives stored in the PSM file system.
>
> To enable and disable the PSM as the destination for the Hives, I either
set
> to 1 or 0, respectively, the "Start DevMgr" value under
> [HKEY_LOCAL_MACHINE\Init\BootVars].
>
> If I enable the Hive on PSM, the system generates several DEBUGCHKs while
> booting, and I lose the use of ActiveSync over USB on one device. The USB
> driver appears to be loaded and running, but I cannot connect to the
> desktop, and if I open the Networking control panel and try to manually
> create a new connection, the USB device is not shown as an option. On the
> second system, I lose use of the Compact Flash slot.
>
> If I disable the device manager ( so the Hive winds up in RAM), everything
> works just fine.
>
> In both systems, I delete the Hive stored in the PSM, re-enable the device
> manager (just to be sure I'm not looking at leftover/old registry data).
>
> I also downloaded and exported the registries, both with and without the
> device manager active. I did notice something different between the two:
>
> With the one with the device manager active (i.e. USB not functional), the
> two following keys exists that were not in the other version:
>
> [HKEY_LOCAL_MACHINE\Drivers\Active\15]
> "Hnd"=dword:003ad7f0
> "Key"="Drivers\\BuiltIn"
> "ClientInfo"=dword:00000000
>
> [HKEY_LOCAL_MACHINE\Drivers\Active\21]
> "Hnd"=dword:003ad860
> "Key"="Drivers\\BuiltIn\\TAPI"
> "ClientInfo"=dword:00000000
>
>
> The DEBUGCHK messages are:
>
> 4294785347 PID:23ad28e6 TID:23ad28c2 0x83ad2684: RegisterAPISet failed for
> api set id 23.
>
> 4294785349 PID:23ad28e6 TID:23ad28c2 0x83ad2684: Unknown: DEBUGCHK failed
in
> file d:\jameson\private\winceos\comm\tapi\tapi\init.c at line 643
>
>
>
> 4294787589 PID:23ad28e6 TID:23ad28c2 0x83ad2684: RegisterAPISet failed for
> api set id 19.
>
> 4294787590 PID:23ad28e6 TID:23ad28c2 0x83ad2684: Unknown: DEBUGCHK failed
in
> file d:\jameson\private\winceos\comm\pm\lib\peginit.c at line 402
>
>
>
> 4294789722 PID:23ad28e6 TID:c39a7fd6 0x83998400: Unknown: DEBUGCHK failed
in
> file d:\jameson\private\winceos\comm\pm\lib\buffers.c at line 256
>
>
>
> Any idea what this is about?
>
> Thanks
>
>