I would like to create a Monolithic, non stream-interface, onboard
Device Driver. It doesn't fit any of the Device Classes that exist
for CE, and so I would like to provide a simple interface (non
stream-interface). How do I go about it and how do I provide the
interface for application developers? Is this essentially a "service"?
Even so, how do I export an API as part of a custom SDK via the SDK
export capability? I am having difficulty finding references to doing
this.

Thanks

Re: Monolithic, non stream-interface, onboard Device Driver by Steve

Steve
Thu Aug 25 20:56:11 CDT 2005

You make a stream driver and provide a wrapper library for applications to
use that ultimately calls the stream interfaces (CreateFile,
DeviceIoControl, CloseHandle) this is typically how it's done.

To include the lib and headers in the SDK just configure the SDK and use the
additional files tab to add the files needed into the SDK.

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com



Re: Monolithic, non stream-interface, onboard Device Driver by gerrit

gerrit
Fri Aug 26 08:53:53 CDT 2005

Thanks Steve, I was hoping there was a "cleaner" way. But I don't
suppose it will be too difficult. Is there a Stream Driver shell
(minimal implementation) in the tree anywhere?


Re: Monolithic, non stream-interface, onboard Device Driver by Steve

Steve
Fri Aug 26 09:42:04 CDT 2005

The RAMDISK sample driver is a fairly simple one and the system.c file
contains the required entry points.

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com



Re: Monolithic, non stream-interface, onboard Device Driver by Paul

Paul
Fri Aug 26 10:24:28 CDT 2005

Or you could just build a DLL with whatever interface you want and call it a
'driver'. You'll have to deal with some special cases, like what happens
when multiple applications try to access the functions at the same time...

Paul T.

"Steve Maillet (eMVP)" <nospam1@EntelechyConsulting.com> wrote in message
news:OpApuFeqFHA.2624@TK2MSFTNGP10.phx.gbl...
> You make a stream driver and provide a wrapper library for applications to
> use that ultimately calls the stream interfaces (CreateFile,
> DeviceIoControl, CloseHandle) this is typically how it's done.
>
> To include the lib and headers in the SDK just configure the SDK and use
> the additional files tab to add the files needed into the SDK.
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>



Re: Monolithic, non stream-interface, onboard Device Driver by John

John
Fri Aug 26 13:41:26 CDT 2005

Although it is centered on a service that runs in services.exe,
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnce50/html/implement_network_service.asp?frame=true
has a sample "finger server" that shows how to have a local app be able to
interface to the service (which looks just like a device driver as far as
DLL exports, apps calling it...).

--
John Spaith
Software Design Engineer, Windows CE
Microsoft Corporation

Check out the new CE Networking Team Blog at http://blogs.msdn.com/cenet/.

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2003 Microsoft Corporation. All rights
reserved.

"gerrit" <google@gerritk.com> wrote in message
news:1125064433.681166.305140@g14g2000cwa.googlegroups.com...
> Thanks Steve, I was hoping there was a "cleaner" way. But I don't
> suppose it will be too difficult. Is there a Stream Driver shell
> (minimal implementation) in the tree anywhere?
>