How to use Windows 2000 API for IEEE 1394

Hello,
I studied the IEEE 1394 APIs provided by Win2000. However I’m not getting
how should I use certain commands. There is 1394api.dll, I got it.
Suppose I want to use AsyncRead API & get the data bytes read from the
address specified.
Following is the prototype for the API:-

ULONG WINAPI AsyncRead(
HWND hWnd,
PSTR szDeviceName,
PASYNC_READ asyncRead,
BOOL bAutoAlloc
);
typedef struct _ASYNC_READ {
ULONG bRawMode;
ULONG bGetGeneration;
IO_ADDRESS DestinationAddress;
ULONG nNumberOfBytesToRead;
ULONG nBlockSize;
ULONG fulFlags;
ULONG ulGeneration;
UCHAR Data[1];
} ASYNC_READ, *PASYNC_READ;

Then where will I get the data read from DestinationAddress ?
Same is the case for AsyncWrite . I don’t understand where to get/specify
the data ?
If anybody has used 1394 APIs then please let me know.
Thanks in advance.
Regards,
Aparna
Member technical staff
Nital Computer systems pvt. ltd, Pune

the 200ddk contains source of 1394 filter driver called 1394diag.sys.
This exposes all the sync and async calls of kernel mode.

Additionally it contains source for a dll(1394api.dll) which exposes all the
apis.
The APIs are documented in 1394api.doc.

If u want to directly use 1394 calls these should be sufficient.

Note ; 98ddk also contains an older version of 1934diag (but no 1394api.dll)

Warm regards
Jeseem
mailto:xxxxx@nestec.net

*************************************************************
The truest form of enlightenment is not in knowing that there
are things you don’t know, but in realizing that there are things
you don’t even know that you don’t know…
*************************************************************

> the 200ddk contains source of 1394 filter driver called 1394diag.sys.

This exposes all the sync and async calls of kernel mode.

Additionally it contains source for a dll(1394api.dll) which exposes all
the

So, 1394api.dll uses 1394diag for its work? Too bad.
1394diag requires switching the 1394bus enumerator to diagnostic mode in
order to be loaded. In this mode, any 1394 devices will be enumerated as
“1394 Test Device”. So, 1394diag and 1394api will work, but no original
WDM drivers will be loaded for any 1394-attached hardware.

Max