Re: Install driver without modifying CE Image

Sure. Put the dll in the \Windows folder (or any other folder in the Loader
path), add the appropriate registry entries and either call
Register/ActivateDevice or soft reset.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com


<a.yearsley@xxxxxxxxx> wrote in message
news:869df9af-dc37-4b64-9b6f-d9e67d88c02d@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi

I'm a complete novice on Windows CE, and not sure if this post is in
the right place ... but here goes anyway.


I am looking to install a driver on a device running Windows CE 5.0,
but I do not want to have to build a new image including this driver.
Is there a way to copy the *.dll onto the device and register is
somehow ???


Any help would be appreciated ... thanks


.

Relevant Pages

  • Re: Transferring programmes from one partition to another
    ... > the same dll location. ... folder as the executable, in which case they are still in the same relative ... The dll may look to the registry but since the exe and ... to uninstall/reinstall. ...
    (microsoft.public.windowsxp.general)
  • Re: Getting File Not Found calling function in DLL from within IDE
    ... the APP_PATH registry entry, but the registry obviously does not get called, ... when invoked from the DLL. ... System32 folder. ...
    (microsoft.public.vb.general.discussion)
  • Re: Effects gone
    ... 2 registry files that contain all of the effects and transitions: ... I noticed that when I open Windows Movie Maker, ... When I went to rename the dll back to ... currently in the /Movie Maker folder. ...
    (microsoft.public.windowsxp.moviemaker)
  • Re: Effects gone
    ... files that are deleted by Movie Maker, ... I will have to unregister the dll and replace the registry files to add ... currently in the /Movie Maker folder. ...
    (microsoft.public.windowsxp.moviemaker)
  • Re: DLL search path question
    ... The 16-bit system directory. ... load location of a random dll in a chain of dlls is not ... register it in registry and have a.dll to instantiate it using ... > - a.dll is being loaded by some external APP stored in a different folder ...
    (microsoft.public.vsnet.general)