Hive based registry (again, sorry)

Hi,

Sorry to post a question on that matter, but I can't find
why my configuration does not work for the hive-based
registry.

I read the documentation about the hive-based registry
settings and I set this into platform.reg :

(NOTE : I use the Geode BSP and Windows CE 4.2. I put the
HIVE-BASED registry feature into my platform).

; HIVE BOOT SECTION
[HKEY_LOCAL_MACHINE\init\BootVars]
"SYSTEMHIVE"="\\Hard Disk\\system\\"
"DefaultUser"="User"
"Start DevMgr"=dword:1

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
"MountFlags"=dword:2
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile\FATFS]
"MountFlags"=dword:2

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Instance\GeodeIDE1\Device0]
"Flags"=dword:1000
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Instance\GeodeIDE1]
"Flags"=dword:1000

[$(PCI_BUS_ROOT)\Template\GeodeIDE]
"Flags"=dword:1000
[$(PCI_BUS_ROOT)\Template\GeodeIDE\Device0]
"Flags"=dword:1000
; END HIVE BOOT SECTION


The settings concerning the IDE devices are taken from the
geodeide.reg file. That's the only reference I found about
the IDE settings and the "[HKEY_LOCAL_MACHINE\Drivers\"
keys mentionned in bullet 5. of the "Using the Hive-based
registry" help topic.

I use a Compact Flash as an IDE device and I have the
"ATAPI PCI/IDE Storage block driver" included in my platform.

This platform runs well and I can see the "Hard Disk"
folder as long as I don't set anything for the hive-based
registry.

Here is what I have from the debug traces on COM port:

Booting Windows CE version 4.20 for (x86
)
&pTOC = 80225408, pTOC = 80c81744, pTOC->ulRamFree =
80cc1000, MemForPT = 000240
00

Old or invalid version stamp in kernel structures -
starting clean!
Configuring: Primary pages: 12055, Secondary pages: 0,
Filesystem pages = 6027

Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 80ce6000, extension: 00003000, length: 02f17000
X86Init done, OEMAddressTable = 80238918.
Windows CE KernelInit
Updated eptr->e32_vsize to = 00085000
Scheduling the first thread.
0x83bff030: KernelInit2: pCurThread=83bff030
hCurThread=03bff1da hCurProc=03bff0
02, KernelInit = 80265aae
0x83bff030: Updated eptr->e32_vsize to = 00010000
0x83bff030: >>> Loading module NK.EXE at address
0x80220000-0x802A5000 (RW data
at 0x80C83000-0x80CB62EB)
0x83bff030: first = 01f50000, last = 02000000,
SharedDllBase = 03530000

0x83bff03
0: >>> Loading module coredll.dll at address
0x03F70000-0x03FF2000 (RW data at 0
x01FFF000-0x01FFFBD0)
0x83bff030: Did not find emulation code for x86... using
floating point hardware
.
0x83bea3e0: >>> Loading module filesys.exe at address
0x04010000-0x04074000
0x83bea3e0: FileSystem Starting - starting with clean file
system
0x83bea3e0: ERROR:
d:\mckendric\private\winceos\coreos\filesys\reg\reghive\.\reg
istry.c line 534: 0x83bea3e0: FSREG: Unable to mount boot
hive from ROM
0x83bea3e0: FSREG: Unable to load system registry!
Registry will be unavailable
.
0x83bea3e0: FileSys: DEBUGCHK failed in file
d:\mckendric\private\winceos\coreos
\filesys\reg\reghive\.\registry.c at line 825
+KITLRegisterDfltClient, service:2
+OEMKitlInit
Unable to initialize KITL Transports!
-OEMKitlInit
!KITLRegisterDfltClient: Fail to initialize KITL
+KITLRegisterDfltClient, service:2
+OEMKitlInit
Unable to initialize KITL Transports!
-OEMKitlInit
!KITLRegisterDfltClient: Fail to initialize KITL
0x83bea3e0: DEBUG_BREAK @00025396 Ignored.
0x83bea3e0: FSREG: Logging in default user.
0x83bea3e0: SetCurrentUser: Logging out (nobody), logging
in default
0x83bea3e0: Exception 00e Thread=83bea3e0 Proc=03bea5ba
'filesys.exe'
0x83bea3e0: AKY=00000003 PC=03fb814f ESP=0408f668 EA=00000000
0x83bea3e0: ERROR:
d:\mckendric\private\winceos\coreos\filesys\reg\profiles\.\pr
ofiles.c line 171: 0x83bea3e0: FS: User Profile Exception
Handler
0x83bea3e0:
Initializing Database
0x83bea3e0: DB:Validation: Name already exists DB_notify_events
0x83bea3e0: DB:CeCreateDatabase failed
0x83bea3e0: Filesystem initialized!
0x83bea000: InitializeJit
0x83bea000: InitMUI: DISABLED (-2144960088)
0x83bea3e0: FS: HKLM\System\Events not available, no signal
events created.
0x83bea3e0: ERROR:
d:\mckendric\private\winceos\coreos\filesys\main\.\fsmain.c l
ine 2821: 0x83bea3e0: Unable to locate init key for
starting apps!

Note : I also tried to set up the environment variable
BSP_ENABLE_FSREGHIVE but this has no special effect. I
guess it just enable the device manager by setting the
"Start DevMgr" registry key which I already override in my
registry settings above.

Regards.

Gabriel

Harald
Wed Jan 14 10:35:13 CST 2004

Hi,

Ensure the following settings:

Platform.reg

; HIVE BOOT SECTION
[HKEY_LOCAL_MACHINE\init\BootVars]
"SYSTEMHIVE"="\\HardDisk\\system.hv"
"PROFILEDIR"="\\HardDisk\\Documents and Settings"
"Start DevMgr"=dword:1
; END HIVE BOOT SECTION

You have also to specify the name of your mounted filesystem. You can do
this in your <profile>, e.g.

; HIVE BOOT SECTION
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
"DefaultFileSystem"=""
"Name"="IDE Hard Disk Drive"
"Folder"="HardDisk"

....
"MountFlags"=dword:2

; END HIVE BOOT SECTION

It's very important to set the MountFlags-Key here.

And the atapi-driver must be loaded in the first boot phase.

; HIVE BOOT SECTION
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Atapi]
"Dll"="atapi.dll"
....
....
"Flags"=dword:1000

; END HIVE BOOT SECTION

--
...
Harald Kraschina
3SOFT GmbH
Harald_DOT_Kraschina_AT_3soft_DOT_DE
"Gabriel" <anonymous@discussions.microsoft.com> schrieb im Newsbeitrag
news:06df01c3da76$b75f2d50$a501280a@phx.gbl...
> Hi,
>
> Sorry to post a question on that matter, but I can't find
> why my configuration does not work for the hive-based
> registry.
>
> I read the documentation about the hive-based registry
> settings and I set this into platform.reg :
>
> (NOTE : I use the Geode BSP and Windows CE 4.2. I put the
> HIVE-BASED registry feature into my platform).
>
> ; HIVE BOOT SECTION
> [HKEY_LOCAL_MACHINE\init\BootVars]
> "SYSTEMHIVE"="\\Hard Disk\\system\\"
> "DefaultUser"="User"
> "Start DevMgr"=dword:1
>
> [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
> "MountFlags"=dword:2
> [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile\FATFS]
> "MountFlags"=dword:2
>
> [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Instance\GeodeIDE1\Device0]
> "Flags"=dword:1000
> [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Instance\GeodeIDE1]
> "Flags"=dword:1000
>
> [$(PCI_BUS_ROOT)\Template\GeodeIDE]
> "Flags"=dword:1000
> [$(PCI_BUS_ROOT)\Template\GeodeIDE\Device0]
> "Flags"=dword:1000
> ; END HIVE BOOT SECTION
>
>
> The settings concerning the IDE devices are taken from the
> geodeide.reg file. That's the only reference I found about
> the IDE settings and the "[HKEY_LOCAL_MACHINE\Drivers\"
> keys mentionned in bullet 5. of the "Using the Hive-based
> registry" help topic.
>
> I use a Compact Flash as an IDE device and I have the
> "ATAPI PCI/IDE Storage block driver" included in my platform.
>
> This platform runs well and I can see the "Hard Disk"
> folder as long as I don't set anything for the hive-based
> registry.
>
> Here is what I have from the debug traces on COM port:
>
> Booting Windows CE version 4.20 for (x86
> )
> &pTOC = 80225408, pTOC = 80c81744, pTOC->ulRamFree =
> 80cc1000, MemForPT = 000240
> 00
>
> Old or invalid version stamp in kernel structures -
> starting clean!
> Configuring: Primary pages: 12055, Secondary pages: 0,
> Filesystem pages = 6027
>
> Booting kernel with clean memory configuration:
> Memory Sections:
> [0] : start: 80ce6000, extension: 00003000, length: 02f17000
> X86Init done, OEMAddressTable = 80238918.
> Windows CE KernelInit
> Updated eptr->e32_vsize to = 00085000
> Scheduling the first thread.
> 0x83bff030: KernelInit2: pCurThread=83bff030
> hCurThread=03bff1da hCurProc=03bff0
> 02, KernelInit = 80265aae
> 0x83bff030: Updated eptr->e32_vsize to = 00010000
> 0x83bff030: >>> Loading module NK.EXE at address
> 0x80220000-0x802A5000 (RW data
> at 0x80C83000-0x80CB62EB)
> 0x83bff030: first = 01f50000, last = 02000000,
> SharedDllBase = 03530000
>
> 0x83bff03
> 0: >>> Loading module coredll.dll at address
> 0x03F70000-0x03FF2000 (RW data at 0
> x01FFF000-0x01FFFBD0)
> 0x83bff030: Did not find emulation code for x86... using
> floating point hardware
> .
> 0x83bea3e0: >>> Loading module filesys.exe at address
> 0x04010000-0x04074000
> 0x83bea3e0: FileSystem Starting - starting with clean file
> system
> 0x83bea3e0: ERROR:
> d:\mckendric\private\winceos\coreos\filesys\reg\reghive\.\reg
> istry.c line 534: 0x83bea3e0: FSREG: Unable to mount boot
> hive from ROM
> 0x83bea3e0: FSREG: Unable to load system registry!
> Registry will be unavailable
> .
> 0x83bea3e0: FileSys: DEBUGCHK failed in file
> d:\mckendric\private\winceos\coreos
> \filesys\reg\reghive\.\registry.c at line 825
> +KITLRegisterDfltClient, service:2
> +OEMKitlInit
> Unable to initialize KITL Transports!
> -OEMKitlInit
> !KITLRegisterDfltClient: Fail to initialize KITL
> +KITLRegisterDfltClient, service:2
> +OEMKitlInit
> Unable to initialize KITL Transports!
> -OEMKitlInit
> !KITLRegisterDfltClient: Fail to initialize KITL
> 0x83bea3e0: DEBUG_BREAK @00025396 Ignored.
> 0x83bea3e0: FSREG: Logging in default user.
> 0x83bea3e0: SetCurrentUser: Logging out (nobody), logging
> in default
> 0x83bea3e0: Exception 00e Thread=83bea3e0 Proc=03bea5ba
> 'filesys.exe'
> 0x83bea3e0: AKY=00000003 PC=03fb814f ESP=0408f668 EA=00000000
> 0x83bea3e0: ERROR:
> d:\mckendric\private\winceos\coreos\filesys\reg\profiles\.\pr
> ofiles.c line 171: 0x83bea3e0: FS: User Profile Exception
> Handler
> 0x83bea3e0:
> Initializing Database
> 0x83bea3e0: DB:Validation: Name already exists DB_notify_events
> 0x83bea3e0: DB:CeCreateDatabase failed
> 0x83bea3e0: Filesystem initialized!
> 0x83bea000: InitializeJit
> 0x83bea000: InitMUI: DISABLED (-2144960088)
> 0x83bea3e0: FS: HKLM\System\Events not available, no signal
> events created.
> 0x83bea3e0: ERROR:
> d:\mckendric\private\winceos\coreos\filesys\main\.\fsmain.c l
> ine 2821: 0x83bea3e0: Unable to locate init key for
> starting apps!
>
> Note : I also tried to set up the environment variable
> BSP_ENABLE_FSREGHIVE but this has no special effect. I
> guess it just enable the device manager by setting the
> "Start DevMgr" registry key which I already override in my
> registry settings above.
>
> Regards.
>
> Gabriel
>

Maks
Thu Jan 15 09:23:34 CST 2004


- Change to $(PUBLICDIR)\COMMON\OAK\DRIVERS\BLOCK\ATAPI\
- open diskmain.cpp

Insert the following line:
BOOL CDisk::Init(HKEY hActiveKey)
{

....

Exit:
m_fDMAActive = FALSE; <== This line was inserted
return bRet;
}
At least you have to compile the ATAPI Block Driver !
Finished :-)

You have now disabled the DMA Mode. The persistent
registry should work now.
Have Fun !
Maks

Yannick
Fri Jan 16 06:47:40 CST 2004

As Steve has already said lots of time :

DO NOT SUGGEST MODIFICATIONS OF MODULE LOCATED IN PUBLIC DIRECTORY

instead, before any modifications, you should duplicate the module in your
own BSP...



--
----------------------------------------------------------------
Yannick Chamming's
ADESET
Windows Embedded Manager
ychammings AT adeset DOT com>
http://www.adeset.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------

"Maks" <anonymous@discussions.microsoft.com> wrote in message
news:003101c3db7b$8a7687b0$a101280a@phx.gbl...
>
> - Change to $(PUBLICDIR)\COMMON\OAK\DRIVERS\BLOCK\ATAPI\
> - open diskmain.cpp
>
> Insert the following line:
> BOOL CDisk::Init(HKEY hActiveKey)
> {
>
> ....
>
> Exit:
> m_fDMAActive = FALSE; <== This line was inserted
> return bRet;
> }
> At least you have to compile the ATAPI Block Driver !
> Finished :-)
>
> You have now disabled the DMA Mode. The persistent
> registry should work now.
> Have Fun !
> Maks
>

Gabriel
Mon Jan 19 10:15:35 CST 2004

Hi all,

Here is a summary of all I experienced about the hive based
registry problems with the GEODE bsp.
Please note that most of these problems are only
encountered with this particular BSP.

I first started from a platform set-up for a RAM based
registry and tried to change the settings for an
hive-based registry. The problem is that the wizard, on
that case, does not define and show you all the settings
inside platform.reg for this feature. So you have to find
yourself the parameters and keys to activate the hive-based
registry.

I tried to set up the hive settings with the help
documentation. But the problem is that the GEODE bsp has
some special registry keys for the IDE/ATAPI block driver.
Most settings are for GENERIC IDE devices which are not
applicable for the GEODE ATAPI driver. This last take its
settings from keys such as the one defined in GEODEIDE.REG
file.

If from the beginning and with the wizard, you set up a
platform with an HIVE-BASED registry, than these keys are
taken from GEODEIDE.REG for you and set up. Here they are :

; @CESYSGEN IF FILESYS_FSREGHIVE
; HIVE BOOT SECTION
[HKEY_LOCAL_MACHINE\init\BootVars]
"SYSTEMHIVE"="\\System\\system.hv"
"PROFILEDIR"="\\System"
"Start DevMgr"=dword:0
IF BSP_ENABLE_FSREGHIVE
"Start DevMgr"=dword:1
ENDIF
; END HIVE BOOT SECTION
; @CESYSGEN ENDIF FILESYS_FSREGHIVE


; @CESYSGEN IF FILESYS_FSREGHIVE
; @CESYSGEN IF CE_MODULES_ATAPI
; HIVE BOOT SECTION
IF BSP_ENABLE_FSREGHIVE
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
"MountFlags"=dword:2
[$(PCI_BUS_ROOT)\Template\GeodeIDE]
"Flags"=dword:1000
[$(PCI_BUS_ROOT)\Template\GeodeIDE\Device0]
"Flags"=dword:1000
[$(PCI_BUS_ROOT)\Template\GeodeIDE\Device2]
"Flags"=dword:1000
ENDIF BSP_ENABLE_FSREGHIVE
; END HIVE BOOT SECTION
; @CESYSGEN ENDIF CE_MODULES_ATAPI
; @CESYSGEN ENDIF FILESYS_FSREGHIVE

Now the other problem is that, even if you take the HIVE
based registry from the beginning, the environment
variable BSP_ENABLE_FSREGHIVE is not set up. So in fact,
you start with a RAM based registry settings (the
device manager is not started). THIS IS ONLY TRUE FOR THE
GEODE BSP.

Once you set up BSP_ENABLE_FSREGHIVE in the platform
settings, your hive based registry works.

Another potential issue is the slave IDE settings which are
not enabled by default. If your IDE device
is setup as the slave, be sure to add this in platform.reg
(always between HIVE BOOT SECTION / END HIVE BOOT SECTION
delimiters as above) for the slave device on first IDE
channel :

[$(PCI_BUS_ROOT)\Template\GeodeIDE\Device1]
"Prefix"="DSK"
"Dll"="atapi.dll"
"Settings"=dword:F
"DeviceId"=dword:1
"Ioctl"=dword:4
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"

You can find these settings in geodeide.reg file (part of
your GEODE BSP install).

Some other people experienced problems with the DMA
support. So do I. With the latest compact flash of a well
known manufacturer, DMA mode was forced ... but not
recognized by the ATAPI driver. Thus, the IDE device was
never mounted and the "Hard Disk" folder was not viewable
under the File Explorer. With a non-DMA based Compact
Flash, I never had this problem.

Some people have disabled the DMA support to force the PIO
mode with the "Settings" key:

[$(PCI_BUS_ROOT)\Template\GeodeIDE\Device0]
"Prefix"="DSK"
"Dll"="atapi.dll"
; rl changed from F
"Settings"=dword:A
"DeviceId"=dword:0
"Ioctl"=dword:4
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"

I didn't test this but this may help someone to dig around
this key value.

Hope this will help.

Regards.

Gabriel.

PS: For GEODE users, I also posted a potential issue
between VGA FLAT and MEDIA GX driver, with its solution.
>-----Original Message-----
>Hi,
>
>Sorry to post a question on that matter, but I can't find
>why my configuration does not work for the hive-based
>registry.
>
>I read the documentation about the hive-based registry
>settings and I set this into platform.reg :
>
>(NOTE : I use the Geode BSP and Windows CE 4.2. I put the
>HIVE-BASED registry feature into my platform).
>
>; HIVE BOOT SECTION
>[HKEY_LOCAL_MACHINE\init\BootVars]
> "SYSTEMHIVE"="\\Hard Disk\\system\\"
> "DefaultUser"="User"
> "Start DevMgr"=dword:1
>
>[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
> "MountFlags"=dword:2
>[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile\FATFS]
> "MountFlags"=dword:2
>
>[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Instance\GeodeIDE1\Device0]
> "Flags"=dword:1000
>[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Instance\GeodeIDE1]
> "Flags"=dword:1000
>
>[$(PCI_BUS_ROOT)\Template\GeodeIDE]
> "Flags"=dword:1000
>[$(PCI_BUS_ROOT)\Template\GeodeIDE\Device0]
> "Flags"=dword:1000
>; END HIVE BOOT SECTION
>
>
>The settings concerning the IDE devices are taken from the
>geodeide.reg file. That's the only reference I found about
>the IDE settings and the "[HKEY_LOCAL_MACHINE\Drivers\"
>keys mentionned in bullet 5. of the "Using the Hive-based
>registry" help topic.
>
>I use a Compact Flash as an IDE device and I have the
>"ATAPI PCI/IDE Storage block driver" included in my platform.
>
>This platform runs well and I can see the "Hard Disk"
>folder as long as I don't set anything for the hive-based
>registry.
>
>Here is what I have from the debug traces on COM port:
>
>Booting Windows CE version 4.20 for (x86
>)
>&pTOC = 80225408, pTOC = 80c81744, pTOC->ulRamFree =
>80cc1000, MemForPT = 000240
>00
>
>Old or invalid version stamp in kernel structures -
>starting clean!
>Configuring: Primary pages: 12055, Secondary pages: 0,
>Filesystem pages = 6027
>
>Booting kernel with clean memory configuration:
>Memory Sections:
>[0] : start: 80ce6000, extension: 00003000, length: 02f17000
>X86Init done, OEMAddressTable = 80238918.
>Windows CE KernelInit
>Updated eptr->e32_vsize to = 00085000
>Scheduling the first thread.
>0x83bff030: KernelInit2: pCurThread=83bff030
>hCurThread=03bff1da hCurProc=03bff0
>02, KernelInit = 80265aae
>0x83bff030: Updated eptr->e32_vsize to = 00010000
>0x83bff030: >>> Loading module NK.EXE at address
>0x80220000-0x802A5000 (RW data
>at 0x80C83000-0x80CB62EB)
>0x83bff030: first = 01f50000, last = 02000000,
>SharedDllBase = 03530000
>
> 0x83bff03
>0: >>> Loading module coredll.dll at address
>0x03F70000-0x03FF2000 (RW data at 0
>x01FFF000-0x01FFFBD0)
>0x83bff030: Did not find emulation code for x86... using
>floating point hardware
>..
>0x83bea3e0: >>> Loading module filesys.exe at address
>0x04010000-0x04074000
>0x83bea3e0: FileSystem Starting - starting with clean file
>system
>0x83bea3e0: ERROR:
>d:\mckendric\private\winceos\coreos\filesys\reg\reghive\.\reg
>istry.c line 534: 0x83bea3e0: FSREG: Unable to mount boot
>hive from ROM
>0x83bea3e0: FSREG: Unable to load system registry!
>Registry will be unavailable
>..
>0x83bea3e0: FileSys: DEBUGCHK failed in file
>d:\mckendric\private\winceos\coreos
>\filesys\reg\reghive\.\registry.c at line 825
>+KITLRegisterDfltClient, service:2
>+OEMKitlInit
>Unable to initialize KITL Transports!
>-OEMKitlInit
>!KITLRegisterDfltClient: Fail to initialize KITL
>+KITLRegisterDfltClient, service:2
>+OEMKitlInit
>Unable to initialize KITL Transports!
>-OEMKitlInit
>!KITLRegisterDfltClient: Fail to initialize KITL
>0x83bea3e0: DEBUG_BREAK @00025396 Ignored.
>0x83bea3e0: FSREG: Logging in default user.
>0x83bea3e0: SetCurrentUser: Logging out (nobody), logging
>in default
>0x83bea3e0: Exception 00e Thread=83bea3e0 Proc=03bea5ba
>'filesys.exe'
>0x83bea3e0: AKY=00000003 PC=03fb814f ESP=0408f668 EA=00000000
>0x83bea3e0: ERROR:
>d:\mckendric\private\winceos\coreos\filesys\reg\profiles\.\pr
>ofiles.c line 171: 0x83bea3e0: FS: User Profile Exception
>Handler
>0x83bea3e0:
>Initializing Database
>0x83bea3e0: DB:Validation: Name already exists
DB_notify_events
>0x83bea3e0: DB:CeCreateDatabase failed
>0x83bea3e0: Filesystem initialized!
>0x83bea000: InitializeJit
>0x83bea000: InitMUI: DISABLED (-2144960088)
>0x83bea3e0: FS: HKLM\System\Events not available, no signal
>events created.
>0x83bea3e0: ERROR:
>d:\mckendric\private\winceos\coreos\filesys\main\.\fsmain.c l
>ine 2821: 0x83bea3e0: Unable to locate init key for
>starting apps!
>
>Note : I also tried to set up the environment variable
>BSP_ENABLE_FSREGHIVE but this has no special effect. I
>guess it just enable the device manager by setting the
>"Start DevMgr" registry key which I already override in my
>registry settings above.
>
>Regards.
>
>Gabriel
>
>.
>