hi...

i have programmed device driver or DOS_16 using asm (masm ) language,
and i am now verey interest to programming device driver for win32
using HLA (high level assembly). i will be thankfull for how can help
me to find a books for this subject.

thnks for all programmers./........... :)

Unlike DOS, there is no real difference between programming DDs for Windows
in asm or in any HLL. Also you can't write a driver just for Windows. There
are two "types" of Windows: NT and 9x/Me. Their kernels are slightly
different. You need a good source on writing device drivers at all (not in a
concrete language). I'd suggest you MSDN (for both NT and 9x) and, specially
for NT, the following books:

"Undocumented Windows 2000 Secrets", Sven Schreiber
"Undocumented Windows NT", Prasad Dabak et.al.
"Inside Microsoft Windows 2000 (3rd ed.)", D.Solomon, M.Russinovich
"Windows NT/2000 Native API Reference:, Gary Nebbett

Ivan

bassamdo1@yahoo.com (system programming) wrote:
>
>i have programmed device driver or DOS_16 using asm (masm ) language,
>and i am now verey interest to programming device driver for win32
>using HLA (high level assembly). i will be thankfull for how can help
>me to find a books for this subject.

What kind of driver are you planning to write?  In general, Windows drivers
are not written in assembler.  They're all in C now.  To write in
assembler, you'd end up having to port the include files.

If you can tell us what you hope to do, I can give you specific advice.
-- 
- Tim Roberts, timr@probo.com
  Providenza & Boekelheide, Inc.

"Tim Roberts" <timr@probo.com> wrote in message >

> What kind of driver are you planning to write?  In general, Windows
drivers
> are not written in assembler.  They're all in C now.  To write in
> assembler, you'd end up having to port the include files.

For the most part, that has been done.
MASM/TASM, HLA, FASM, NASM, etc., all have reasonable
sets of converted header files (always a few defs missing, but adding
the missing ones you need usually isn't much of a problem to someone
who is competent enough to write device drivers under Windows).

Of course, one must be able to read C documentation and mentally
translate to assembly, as almost all documentation on the subject
assumes C. IIRC, there are a couple of examples of WMD and
other Windows drivers in assembly floating around on the net.
Cheers,
Randy Hyde