Re: Driver sample with *.asm source
- From: "Vetzak" <ptrshrn@xxxxxxxxx>
- Date: 12 Jun 2006 07:01:28 -0700
You can generate a .asm file from an existing driver using IDAPro 5.
This program generates an .asm file that can be passed to masm.
Tim Roberts wrote:
Peter <Peter@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
But like I mentioned it seems that all these directives are sufficient, but
I am not 100% sure about it, even if this part of code is really functional
in result NDIS IM driver. In *.cod file are much more directives, I am not so
good in MASM to know what of these I must to use also in *.asm source file.
.COD files cannot actually be passed directly into MASM. Unlike gcc,
Visual C++ doesn't create an assembly file and then assemble it. It
creates machine language more or less directly. The .COD files are
generated in a separate step, and are representative of what the MASM would
look like, but manual intervention is required.
--
- Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.
.
- References:
- Re: Driver sample with *.asm source
- From: Ali
- Re: Driver sample with *.asm source
- From: Gary G. Little
- Re: Driver sample with *.asm source
- From: Peter
- Re: Driver sample with *.asm source
- From: Tim Roberts
- Re: Driver sample with *.asm source
- Prev by Date: Re: LSA AU: DeRregisterLogonProcess Failed 0xc00002fe
- Next by Date: how to allow enable/diable keyboard in device manager
- Previous by thread: Re: Driver sample with *.asm source
- Next by thread: NdisProt and multiple handles to the same device
- Index(es):
Relevant Pages
|
