Co-Installer and Service Always Required?

I've developed a WDM class driver for my device. It's a device that attaches
to a SCSI bus for doing I/O with some dedicated hardware. I only need to
open/close/read/write to the dedicated hardware.

So I started with a 'storage/class' example in the WDK and got the device
working, now I'm working on installation.

This is a simple driver with no user interface or anything. Do I need to
create some 'dummy' service for it? Do I need a dedicated coinstaller dll
for this? I read through the toaster example and all that's nice but I don't
really need this. Can I just omit that from the package?

Thanks,

If this is a WDM driver need nothing more than the sys file and an INF file.
You do not need a service or a co-installer.


--
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply



"Mike Fochtman" <> wrote in message
news:1E40E94C-65FB-4451-9332-...
> I've developed a WDM class driver for my device. It's a device that
> attaches
> to a SCSI bus for doing I/O with some dedicated hardware. I only need to
> open/close/read/write to the dedicated hardware.
>
> So I started with a 'storage/class' example in the WDK and got the device
> working, now I'm working on installation.
>
> This is a simple driver with no user interface or anything. Do I need to
> create some 'dummy' service for it? Do I need a dedicated coinstaller dll
> for this? I read through the toaster example and all that's nice but I
> don't
> really need this. Can I just omit that from the package?
>
> Thanks,
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4668 (20091207) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4668 (20091207) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

Thanks Don, That's what I was hoping for.

So I just leave out coinstaller and service entries from the inf??


"Don Burn" wrote:

> If this is a WDM driver need nothing more than the sys file and an INF file.
> You do not need a service or a co-installer.
>
>
> --
> Don Burn (MVP, Windows DKD)
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
> Remove StopSpam to reply
>
>
>
> "Mike Fochtman" <> wrote in message
> news:1E40E94C-65FB-4451-9332-...
> > I've developed a WDM class driver for my device. It's a device that
> > attaches
> > to a SCSI bus for doing I/O with some dedicated hardware. I only need to
> > open/close/read/write to the dedicated hardware.
> >
> > So I started with a 'storage/class' example in the WDK and got the device
> > working, now I'm working on installation.
> >
> > This is a simple driver with no user interface or anything. Do I need to
> > create some 'dummy' service for it? Do I need a dedicated coinstaller dll
> > for this? I read through the toaster example and all that's nice but I
> > don't
> > really need this. Can I just omit that from the package?
> >
> > Thanks,
> >
> >
> > __________ Information from ESET NOD32 Antivirus, version of virus
> > signature database 4668 (20091207) __________
> >
> > The message was checked by ESET NOD32 Antivirus.
> >
> > http://www.eset.com
> >
> >
> >
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus signature database 4668 (20091207) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
> .
>

Mike Fochtman <> wrote:
>
>Thanks Don, That's what I was hoping for.
>
>So I just leave out coinstaller and service entries from the inf??

Well, no. Every driver needs a "Services" entry in the registry. That's
how the operating finds your driver's binary.

As to whether you need a co-installer or not, that depends. If your driver
is KMDF, then you probably want to include the KMDF co-installer. If you
driver is for a class that normally uses a co-installer, then you need
that. General WDM drivers don't need a co-installer.

You haven't given us very much detail, so we can't give you detailed
advice.
--
Tim Roberts,
Providenza & Boekelheide, Inc.