This is not a really "how to install the kbfiltr sample driver?"
question! I know that it comes with a text teaching how to install it.
The problem is that it uses a .INF file and i want to know how to
install it without this .INF file. I tried to use the Driver Loader,
it registers the driver but i can't start its service because it gives
me the following error: "The service could not be started because it
is disabled or does not have associated devices enabled." I tried to
restart the computer and this message still appears!
Any solution?

With modern versions of Windows, it's really recommended that you
install with an INF file. While it's technically possible it to do all
the work yourself, you're very likely to get it wrong. On Vista in
particular, drivers all have to get copied to a driver store to be
installed by the OS in session 0, and that process essentially requires
an INF and there aren't really APIs available to do it manually, so
you'd have to somehow get all the details right yourself and it would
probably break with the next service pack anyway, because it's all
undocumented.

In other words: don't try. Just use the INF.

Thiago wrote:

--
Ray

I will only use this filter in my PC with Windows XP installed and i'm
not going to make a release for Windows Vista.

Thanks for your tip.

Write it to UpperFilters multi-string value below KbdClass at

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E96B-E325-11CE-B
FC1-08002BE10318}

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"Thiago" <thiforums@gmail.com> wrote in message
news:b02770a6-8dcc-4d4c-b718-d477a04bbc65@56g2000hsm.googlegroups.com...

Cool... so why exactly do you care if it's installed with an INF file?

Is there some reason you're trying to make this as difficult as possible
on yourself?

Anyway, as others have said, you can get it to work by adding your
service and then putting it in i8042prt's UpperFilters key. But it's
still only about 1% of what UpdateDriverForPlugAndPlayDevices does when
given an INF file, even on XP.

Thiago wrote:

--
Ray

90% actually, only copying the file to Driver Store and INF file to OEMxxxx.INF
is skipped, as also restarts of the existing active stacks.

Registry updates are the same.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

(all the following is assuming a filter on a PNP stack like kbfiltr)

I would call your accounting odd, given that even the 3 steps you
mentioned would imply no more than 25%, even if you count setting 1
registry key as equal in complexity to those steps.

But UDFPNPD also updates the dev node (to include, for example, the
device description, HWIDs, etc., in the INF), validates the INF against
the device IDs, creates a driver and system rollback point, updates the
last known good configuration, compiles the INF to a PNF, executes any
class and device coinstallers, puts entries in the system log for
auditing purposes, checks domain device rules, and probably half a dozen
other things I don't know about (but I won't count those).

Each of these is *far* more complex than setting a registry key, but
I'll count them the same for the sake of argument. That would make the
reg key at most 7% of what UDFPNPD does.

Forgive my exaggeration.

Maxim S. Shatskih wrote:

--
Ray