Emulating a WebCamera
in [Device Drivers]
|
From: pradeep_TP on 14 Jan 2006 00:31 Hello everybody, Thank you all for participating in this thread. I started this thread to know how they may have developed a software such as virutualCam. By looking at the files installed, i came to know that its nothing but a driver. I wanted to know whether the same feat can be achieved by an individual programmer like me. Now I fully understand that is like playing with a fire and requires patience and dedication. Let me repeat it, I am very new to driver development and still have no idea where exactly do i start from. I can download the KMDF, but unless i know the basics of driver development, it will be of no use to me. Can someone tell me how do I start. Is there any good book that you can recommend me so that i learn the basics first and then delve deep into the core of driver development. When i search in the internet, i get way too many acronyms and really not able to get good picture of the whole episode. I just want to learn from your experiences, like for eg. i want to know how did you start with learning it, books you may have read, any formal training etc. Thanks Pradeep_tp "Skywing" wrote: > It is in fact freely downloadable once again. Search for KMDF on > microsoft.com; the KMDF ISO also includes an installer for the Win2003 SP1 > DDK. > > "pradeep_TP" <pradeepTP(a)discussions.microsoft.com> wrote in message > news:28AAE602-B635-4953-80BF-240AD847D102(a)microsoft.com... > > Hello all, > > > > ab, thanks for pointing me towards the DDK sample. Unfortunately, i dont > > have the DDk with me. I know it is not freely downloadable, but is is > > possible that i can download just the samples from somewhere. > > > > cat, can i ask you how long have you worked on developing device drivers. > > can you share your experience with me so that i can have some inspiration. > > Did you work on device drivers individually or with a team. what are the > > important things that i should keep in mind while starting to learn about > > device drivers. > > > > Thanks > > pradeep > > > > > > "Cat" wrote: > > > >> Generally, I stay away from kernel-mode as much as possible, the reason > >> being that crashes in kernel-mode are a lot more time-consuming to > >> debug than in usermode, where you can simply attach a debugger, > >> terminate the process, etc. > >> > >> That's why I was pointing toward a user-mode solution. If, however, you > >> genuinely need the device to show up in Device Manager, etc., etc., > >> then indeed kernel-mode seems like the only solution. > >> > >> Good luck, > >> -Cat > >> > >> > > >
From: Anonymous on 14 Jan 2006 08:27 I take my hat off, I had no idea this was available (strangly this does not appear on the ddk home page) This is more than generous. "Gary G. Little" <gary.g.little(a)seagate.com> wrote in message news:43c80f1f$0$30394$6d36acad(a)taz.nntpserver.com... > But this a moot point as > http://www.microsoft.com/whdc/driver/wdf/KMDF_pkg.mspx has a downloadable > ISO image of KMDF 1.0 which has the DDK install package for the current DDK. > The S&H cost of the DDK has never been $100, unless you live in the deepest > and darkest part of Antartica and you have to pay for feeding the sled dogs > to get it to your igloo. The $100 cost was for the DDK Suite which contained > the DDK and provided miscelaneous flotsam and jetsam you might or might not > find useful. > > My company pays for my work Universal MSDN subscription, but I pay for my > own MSDN subscription, out of pocket, so that I have a home environment. > That has come in very handy a few times during layoffs when I did not have > access to "company supplied" tools. It's the cost of doing business, > whether it be S & H for the DDK or an MSDN subscription, and if you can't > afford it, tough, perhaps you need to find a career you can afford. > > -- > The personal opinion of > Gary G. Little > > <ab> wrote in message news:OqQ7tdGGGHA.3000(a)TK2MSFTNGP14.phx.gbl... > >I am not sure, I once looked and it was "free" with a cost of $100 for > > post and "handling". Perhaps microsoft has realised it is absured to > > say something is free when the "administration fee" is 100, and if so > > this is a good thing. In the same way it is also absured to say the > > ddk is "free" with msdn, because msdn>>$100. I think you are quite > > rich, or ,maybe your company buys all the software for you, and > > there you live in a bubble. > > "Gary G. Little" <gary.g.little(a)seagate.com> wrote in message > > news:43c7c52d$0$2746$6d36acad(a)taz.nntpserver.com... > >> Last time I looked, for $100 you get the DDK suite, or something that > >> included the actual DDK. By itself, the DDK was only the cost of shipping > >> ... around $15 US. It is included in an MSDN subscription, which is an > >> annual subscription. > >> > >> -- > >> The personal opinion of > >> Gary G. Little > >> > >> <ab> wrote in message news:%23NkCYAEGGHA.3444(a)TK2MSFTNGP10.phx.gbl... > >> > Max was right, testcap is what you want, it is a virtual device like > >> > you > >> > need, > >> > displaying, instead of a real picture, a Test Screen of bars, so you > > don't > >> > even need to program anything, just compile, and there you go! > >> > Get the DDK, it's $100. Mind you Max was a bit optimistic I think with > >> > his "few months" estimate, more likely "few years". Anyway, good luck! > >> > > >> > "pradeep_TP" <pradeepTP(a)discussions.microsoft.com> wrote in message > >> > news:A64E1540-833B-4BF8-A71E-329DFD5D73DE(a)microsoft.com... > >> >> Hello Mark, > >> >> > >> >> I am willing to spend even years, if I want to learn about device > > driver > >> >> programming. The reason I am hanging around this forum is to get some > >> >> idea > >> >> about where and how to start and also the advices and suggestions from > >> > people > >> >> like you. > >> >> > >> >> My biggest problem now is the DDK, which I dont not have. Meanwhile I > >> > would > >> >> like to spend some time reading about driver development. Do you have > > any > >> >> suggestions on any good books for the same? > >> >> > >> >> Thanks > >> >> pradeep_TP > >> >> > >> >> "Max Paklin" wrote: > >> >> > >> >> > DDK's TestCap is probably the best starting point for your effort. > >> >> > However I must point out that it is not a trivial task even for an > >> >> > experienced dev. > >> >> > Given the fact that you don't seem to know kernel - and KS in > >> > particular - > >> >> > at all, it'd be very hard for you to do this unless you are willing > > to > >> > spend > >> >> > months learning. > >> >> > > >> >> > -- Max. > >> >> > > >> >> > > >> >> > > >> >> > "pradeep_TP" <pradeepTP(a)discussions.microsoft.com> wrote in message > >> >> > news:28AAE602-B635-4953-80BF-240AD847D102(a)microsoft.com... > >> >> > > Hello all, > >> >> > > > >> >> > > ab, thanks for pointing me towards the DDK sample. Unfortunately, > >> >> > > i > >> > dont > >> >> > > have the DDk with me. I know it is not freely downloadable, but is > > is > >> >> > > possible that i can download just the samples from somewhere. > >> >> > > > >> >> > > cat, can i ask you how long have you worked on developing device > >> > drivers. > >> >> > > can you share your experience with me so that i can have some > >> > inspiration. > >> >> > > Did you work on device drivers individually or with a team. what > > are > >> > the > >> >> > > important things that i should keep in mind while starting to > >> >> > > learn > >> > about > >> >> > > device drivers. > >> >> > > > >> >> > > Thanks > >> >> > > pradeep > >> >> > > > >> >> > > > >> >> > > "Cat" wrote: > >> >> > > > >> >> > >> Generally, I stay away from kernel-mode as much as possible, the > >> > reason > >> >> > >> being that crashes in kernel-mode are a lot more time-consuming > >> >> > >> to > >> >> > >> debug than in usermode, where you can simply attach a debugger, > >> >> > >> terminate the process, etc. > >> >> > >> > >> >> > >> That's why I was pointing toward a user-mode solution. If, > > however, > >> > you > >> >> > >> genuinely need the device to show up in Device Manager, etc., > > etc., > >> >> > >> then indeed kernel-mode seems like the only solution. > >> >> > >> > >> >> > >> Good luck, > >> >> > >> -Cat > >> >> > >> > >> >> > >> > >> >> > > >> >> > > >> >> > > >> > > >> > > >> > >> > > > > > >
From: rep_movsd on 14 Jan 2006 15:29 Hi I too am on the same track, but unlike you, I have already developed a user mode virtual Video capture device using plain old directshow. You can find the basic code and example at http://tmhare.mvps.org/downloads.htm. This works under yahoo messenger, AMCAP, WMENC etc. However for some reason ( namely it fails to work in moviemaker, and some versions of MSN) I have decided to rush in where angels fear to tread ( ie im going into device driver blackmagic ) Today happens to be the day when i actually was able to edit the testcap sample to remove the VBI, CC NABTS and tv input pins and leaving only the rgb video pin. IT compiles and works. Next thing i intend to do is to create a shared memory section for the frame buffer, into which i will pump in data from a user mode app.
From: Max Paklin on 16 Jan 2006 01:04 There is no books about KS (Stream Class or AVStream) so DDK is your best source. As other posters mentioned there is now a version of the DDK that you can download for free. -- Max. "pradeep_TP" <pradeepTP(a)discussions.microsoft.com> wrote in message news:A64E1540-833B-4BF8-A71E-329DFD5D73DE(a)microsoft.com... > Hello Mark, > > I am willing to spend even years, if I want to learn about device driver > programming. The reason I am hanging around this forum is to get some idea > about where and how to start and also the advices and suggestions from > people > like you. > > My biggest problem now is the DDK, which I dont not have. Meanwhile I > would > like to spend some time reading about driver development. Do you have any > suggestions on any good books for the same? > > Thanks > pradeep_TP > > "Max Paklin" wrote: > >> DDK's TestCap is probably the best starting point for your effort. >> However I must point out that it is not a trivial task even for an >> experienced dev. >> Given the fact that you don't seem to know kernel - and KS in >> particular - >> at all, it'd be very hard for you to do this unless you are willing to >> spend >> months learning. >> >> -- Max. >> >> >> >> "pradeep_TP" <pradeepTP(a)discussions.microsoft.com> wrote in message >> news:28AAE602-B635-4953-80BF-240AD847D102(a)microsoft.com... >> > Hello all, >> > >> > ab, thanks for pointing me towards the DDK sample. Unfortunately, i >> > dont >> > have the DDk with me. I know it is not freely downloadable, but is is >> > possible that i can download just the samples from somewhere. >> > >> > cat, can i ask you how long have you worked on developing device >> > drivers. >> > can you share your experience with me so that i can have some >> > inspiration. >> > Did you work on device drivers individually or with a team. what are >> > the >> > important things that i should keep in mind while starting to learn >> > about >> > device drivers. >> > >> > Thanks >> > pradeep >> > >> > >> > "Cat" wrote: >> > >> >> Generally, I stay away from kernel-mode as much as possible, the >> >> reason >> >> being that crashes in kernel-mode are a lot more time-consuming to >> >> debug than in usermode, where you can simply attach a debugger, >> >> terminate the process, etc. >> >> >> >> That's why I was pointing toward a user-mode solution. If, however, >> >> you >> >> genuinely need the device to show up in Device Manager, etc., etc., >> >> then indeed kernel-mode seems like the only solution. >> >> >> >> Good luck, >> >> -Cat >> >> >> >> >> >> >>
From: Max Paklin on 16 Jan 2006 01:07
The OP wants to do a minidriver for KS. KMDF is of no use to him. This is one of those cases where the big step in generic KM driver development doesn't help folks working in port/miniport domains. -- Max. "Gary G. Little" <gary.g.little(a)seagate.com> wrote in message news:43c7c615$0$30387$6d36acad(a)taz.nntpserver.com... > Your best bet is to start with the WDF, currently KMDF 1.0 (Kernel Mode > Driver Framework). The framework provides much of the power and PnP > management that has made drive developement so difficult. It stilll tain't > easy, but the framework does make it easier. > > -- > The personal opinion of > Gary G. Little > > "pradeep_TP" <pradeepTP(a)discussions.microsoft.com> wrote in message > news:A64E1540-833B-4BF8-A71E-329DFD5D73DE(a)microsoft.com... >> Hello Mark, >> >> I am willing to spend even years, if I want to learn about device driver >> programming. The reason I am hanging around this forum is to get some >> idea >> about where and how to start and also the advices and suggestions from >> people >> like you. >> >> My biggest problem now is the DDK, which I dont not have. Meanwhile I >> would >> like to spend some time reading about driver development. Do you have any >> suggestions on any good books for the same? >> >> Thanks >> pradeep_TP >> >> "Max Paklin" wrote: >> >>> DDK's TestCap is probably the best starting point for your effort. >>> However I must point out that it is not a trivial task even for an >>> experienced dev. >>> Given the fact that you don't seem to know kernel - and KS in >>> particular - >>> at all, it'd be very hard for you to do this unless you are willing to >>> spend >>> months learning. >>> >>> -- Max. >>> >>> >>> >>> "pradeep_TP" <pradeepTP(a)discussions.microsoft.com> wrote in message >>> news:28AAE602-B635-4953-80BF-240AD847D102(a)microsoft.com... >>> > Hello all, >>> > >>> > ab, thanks for pointing me towards the DDK sample. Unfortunately, i >>> > dont >>> > have the DDk with me. I know it is not freely downloadable, but is is >>> > possible that i can download just the samples from somewhere. >>> > >>> > cat, can i ask you how long have you worked on developing device >>> > drivers. >>> > can you share your experience with me so that i can have some >>> > inspiration. >>> > Did you work on device drivers individually or with a team. what are >>> > the >>> > important things that i should keep in mind while starting to learn >>> > about >>> > device drivers. >>> > >>> > Thanks >>> > pradeep >>> > >>> > >>> > "Cat" wrote: >>> > >>> >> Generally, I stay away from kernel-mode as much as possible, the >>> >> reason >>> >> being that crashes in kernel-mode are a lot more time-consuming to >>> >> debug than in usermode, where you can simply attach a debugger, >>> >> terminate the process, etc. >>> >> >>> >> That's why I was pointing toward a user-mode solution. If, however, >>> >> you >>> >> genuinely need the device to show up in Device Manager, etc., etc., >>> >> then indeed kernel-mode seems like the only solution. >>> >> >>> >> Good luck, >>> >> -Cat >>> >> >>> >> >>> >>> >>> > > |