Propagate the auto Device Name from bootloader into OS settings

Microsoft.public.windowsce.embedded or
Microsoft.public.windowsce.platbuilder

Hi,

I am developing for a headless device with Windows CE.NET 4.1.
The idea is to read the Boot parameters network name that is
automatically built in bootloader, and rewrite in the registry the
machine name just after the initialization of the registry.
The OAL will take BootParams.WinceBootArgs.szDeviceNameRoot and change
the registry value [HKEY_LOCAL_MACHINE\Ident, Name] with
BootParams.WinceBootArgs.szDeviceNameRoot in IOCTL_HAL_INITREGISTRY in
OEMIOControl().
But always I am having exception in NK.exe (access violation) !!!
In OEMInit() when I print with DEBUGMSG() the
pBootArgs->szDeviceNameRoot it is not containing the same value that
was built in the bootloader by CreateDeviceName() Why?
Is there any other way to let me propagate the Device Name (and some
network parameters (IP, ..)...) Which are built in Bootloader to the
OS setting?
Any samples, any link, ...is very appreciate.
Thank you very much for you help.

sloh
Wed Jul 30 12:20:51 CDT 2003

You should be able to do what you're trying to do. Can you send your code
from IOCTL_HAL_INITREGISTRY which is getting the exception? Or is it that
the IOCTL code is fine, but the data you're storing in pBootArgs is getting
corrupted before you get to the IOCTL? If that's the case, then you should
first double-check that the bootloader's memory is not being used by
something else (check your config.bib file...). Also check that IMGEBOOT
is set to the right value, because if I remember right, that reserves some
memory for the bootloader. I'm not too familiar with bootloaders actually;
if the bootloader's memory is part of the driver globals then make sure no
other OAL init code is modifying it.

Sorry I'm not more help but hopefully that gives you enough to get started.
Maybe some better experts on these newsgroups will be able to make better
suggestions.

Sue
sloh@microsoft.com (remove "online" from reply-to address)
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________________________________
Windows Embedded FAQ
(http://www.microsoft.com/windows/embedded/faq/default.asp)

Steve
Wed Jul 30 12:44:28 CDT 2003

You should be able to re-compute the device name in the OAL (as part of the
KTIL support you need to) so you can just figure it out and store it in the
registry.

--
Steve Maillet (eMVP)
Entelechy Consulting
smaillet_AT_EntelechyConsulting_DOT_com

zmaddi
Mon Aug 04 12:11:05 CDT 2003

"Steve Maillet \(eMVP\)" <nospam1@EntelechyConsulting.com> wrote in message news:<eR2ERKsVDHA.1316@TK2MSFTNGP12.phx.gbl>...
> You should be able to re-compute the device name in the OAL (as part of the
> KTIL support you need to) so you can just figure it out and store it in the
> registry.

Hi,

Ok for the device Name, I will be able to re-compute it! But what
about network parameters (use or not the DHCP, static IP...)?

Steve
Mon Aug 04 19:18:02 CDT 2003

Again you can re-duplicate the code from the boot loader for that too. Or
you can reserve a region of memory for communicating parameters between the
boot loader and the OAL. I am not a fan of that as it ties the OAL to the
boot loader and does not allow a fully standalone OS image without
modification or special build options or flags.

--
Steve Maillet (eMVP)
Entelechy Consulting
smaillet_AT_EntelechyConsulting_DOT_com