Prev: MULTIPLE_IRP_COMPLETE_REQUESTS
Next: send commands to the keyboard controller
From: fat_boy on 23 Jun 2005 12:01
Oh yes, forgot to mention the /subsystem:native switch for the linker.

From: fat_boy on 24 Jun 2005 04:57
Its not that difficult, if you know what you are doing, and once a
project is set up it is easy to reuse.

From: Peter Larsen on 27 Jun 2005 06:42
Thanks, (but) are you talking about changing the default values in VS so i
won't be able to build normal .Net projects ??

/Peter

"fat_boy" <m.sykes(a)option.com> wrote in message
news:1119532327.375136.74080(a)g43g2000cwa.googlegroups.com...
> Well, you can just use VS. It is a little trickky to set up, but you
> do get the added advantage of browsing your code.
>
> In Tools-OPtions-Directories-Executables you can point to the compiler
> shipped with 2003 ddk. Something like c:\winddk\3790\bin.
>
> You will need to copy bscmake.exe from the VS directory to the
> c:\winddk\3790\bin directory to.
>
> After that you need to get the project set up. Ignore all default
> includes and libs, and specify your own lib and include paths.
>
> You then need all the defines set properly in the VS project. Run set
> in the DDK build env for your prefered platform to see a list of what
> is being set. You will need a lot of them as preprocessor defines.
>
>
> However, I just use this for developement. For final builds and formal
> testing always use the build macro, which can also be used with
> prefast, a usefull DDK utility.
>


From: Peter Larsen on 27 Jun 2005 06:49
Does anyone of you, have a suggestion to the second part of my question ("Is
it possible to write a 1394 driver from the sample, or would it be easier to
start from scratch") ??


/Peter


From: r_konjeti on 27 Jun 2005 09:44
I wrote my driver based on sample. But you have to basically rewrite
entire sample. So sample is only a sample. You can understand framework
but cant use it. My advice is dont even start on sample code like I
did. Start fresh project. Just use sample to understand and reference.
1394 interface to driver can be done in many ways described in DDK and
sample dont use best ways. Sample uses async option which is not really
useful. You may need different async option. Isoch is also buggy. 1394
driver is not simple. Start with XP and my experience is Windows 2000
has issues.

Peter Larsen wrote:
> Does anyone of you, have a suggestion to the second part of my question ("Is
> it possible to write a 1394 driver from the sample, or would it be easier to
> start from scratch") ??
>
>
> /Peter

First  |  Prev  | 
Pages: 1 2
Prev: MULTIPLE_IRP_COMPLETE_REQUESTS
Next: send commands to the keyboard controller