From - Mon Oct 20 08:09:56 1997
Path: news.mitre.org!blanket.mitre.org!agate!howland.erols.net!ais.net!news.idt.net!nntp.farm.idt.net!news
From: andy@stratostech.com (Andy Shajenko)
Newsgroups: comp.os.ms-windows.programmer.nt.kernel-mode
Subject: Re: NdisMCreateLog
Date: 18 Oct 1997 17:43:40 GMT
Organization: Stratos Technology, Inc.
Lines: 25
Message-ID: <62asgc$kgb@nnrp2.farm.idt.net>
References: <01bcdb45$66e2d7a0$147dcbc7@isak>
NNTP-Posting-Host: 207.113.16.53
Mime-Version: 1.0
Content-Type: Text/Plain; charset=US-ASCII
X-Newsreader: WinVN 0.99.8

In article <01bcdb45$66e2d7a0$147dcbc7@isak>, isak@elementrix.co.il says...
>did anyone tried using NdisMCreateLog in a minport driver.
>the documentation says that the user mode application should use CreateFile
>to open the driver.
>what filename should I pass to CreateFile?

Isak,

Check out the "macaddr" sample app and the "ntddndis.h" file in
the NT DDK. Just use IOCTL_NDIS_GET_LOG_DATA instead of 
IOCTL_NDIS_QUERY_GLOBAL_STATS.  This probably only works under NT,
since NDIS under Windows 95 does not support or provide an
interface to Win32 apps via DeviceIoControl().  Perhaps the output
goes to some log file - I haven't tried this under Win95.

The "filename" will be the symbolic link for the adapter device object.
For example, if "foo" is the device name and it is the Xth network
adapter installed (in the order of installation), then use "fooX"
in CreateFile().  You can get the name from the Registry under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\fooX.

A. Shajenko
Stratos Technology, Inc.