Re: Loading USB driver @ boot

Tech-Archive recommends: Fix windows errors by optimizing your registry

If I follow this correctly, changing the nk.bin isn't possible. So you
could use the HIVE registry, that I hope you have. change the name of the
new version of the driver and change it in the registry, now it should work
with your system path change pointing to your NOR flash.

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

EuroTech Inc.
www.EuroTech.com

"Michel Verhagen (eMVP)" <michel@xxxxxxxxxx> wrote in message
news:uNJighguIHA.6096@xxxxxxxxxxxxxxxxxxxxxxx
The right way to do this is to mount the USB drive as root so that any
file on the USB drive will override any file in ROM:

Inside NK.BIN: usbdriver.dll (version 1.0)
On USB drive : usbdriver.dll (version 2.0)

Now if you mount the USB drive as root usbdriver.dll version 2.0 will be
used.

Inside NK.BIN: usbdriver.dll (version 1.0)
On USB drive :

In this case the system will just use version 1.0.

Of course you have to put all necessary USB driver registry settings
between ; HIVE BOOT SECTION tags to load everything at first boot. Then
set "MountAsRoot" in the USB drive profile and voila!

Of course loading a USB drive will increase your boot time with quite a
bit (the system won't continue booting until the USB drive is completely
loaded and mounted).

It's probably faster to use a part of the internal NOR flash as a
partition with a filesystem that can be mounted as root. Then you can just
"upgrade" the driver by copying usbdriver.dll v2 to the internal NOR
partition and on next boot the system will use the new version instead of
the one in the NK.BIN.



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.

Steve Hugg wrote:
We have a system with two partitions, the NK.bin and an internal
filesystem on the same NOR flash device. We have the need to load USB
drivers from the internal filesystem. The reason being, our NK.bin is
not upgradable but the filesystem is. So we have some ideas:

* We use the Loader/SystemPath registry variable to point to the
filesystem. This doesn't seem to work even though we put this entry in
the boot registry.

* We copy the USB driver files to the \WINDOWS directory after boot.
The problem here is that we have a race condition between the copy and
the USB driver loading.

* Let the USB driver fail loading the first time, then retry after we
boot up and copy driver files to \windows (is there a function to
reload a driver?)

Has anyone else had a similar problem? Thanks!


.

Relevant Pages

  • Re: Ho to run CF driver before reading hive-based registry
    ... BOOT SECTION": ... so I had to rewrite the driver for it. ... The problem is now the hive-based registry. ... FileSystem Starting - starting with clean file system ...
    (microsoft.public.windowsce.platbuilder)
  • Re: ROM-only FS and persisting registry on USB HD
    ... driver and step into the code to figure out how it failed. ... PCI bus driver and its relative registry setting should be moved into BOOT ... you have to have your USB host controller's driver ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Ho to run CF driver before reading hive-based registry
    ... BOOT SECTION": ... and later starts the .nb0 file from Compact Flash). ... is not located on an ordinary PCI bus, so I had to rewrite the driver ... hive-based registry to my image and adding some of the registry ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Cant run WINCE from a flash drive on my AMD M/B
    ... Hive-based Registry is not selected or fix the device default registry so ... didn't put the storage manager entries for your flash drive in HIVE BOOT ... bootable filesystem, so it won't boot. ... FS: Creating signal event SYSTEM/DevMgrApiSetReady ...
    (microsoft.public.windowsce.embedded)
  • Re: Ho to run CF driver before reading hive-based registry
    ... Did you place all the registry settings related to your CF driver inside ... ; END HIVE BOOT SECTION ... The problem is now the hive-based registry. ... FileSystem Starting - starting with clean file system ...
    (microsoft.public.windowsce.platbuilder)