Have a NDIS 5.0 protocol driver along with a notify object and an inf [with
class as NetTrans]
After adding it from the Local Area Connection properties, the DriverEntry
& BindAdapterHandler are not getting called.
Is it that we need 2 inf’s for installing a transport protocol? Similar to
what we need for IM driver [Passthru]?
If I just replace the passthru.sys with my driver I find the driver entry
getting called. I also receive the NetEventBindsComplete PnP event.
Thanks,
Nitin
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> I am writing a Virtual Printer driver.Which convert any office document file
to BMP. Now i want to generate JPEG instead of BMP.
Not so good idea, JPEGs are for photos only, using JPEG for things like vector drawing will cause noticeable quality loss.
Why not use GIF or PNG? Their compression is simple.
provided GDI + . Please guide how can I genertae JPEG direct ly like BMP to
improve its performance.
Can GRE draw on JPEG surface? I have large doubts in it.
So, convert your surface bitmap to JPEG using the same GDI calls or by your own code.
Max
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Nitin,
The passthru requires 2 inf files because it performs 2 functions: it behaves
as a miniport on the upper edge and it behaves as a protocol on the lower edge.
If your driver is a pure protocol driver, which means that it behaves as a
protocol on the lower edge and supports TDI on the upper edge, then I would
think 1 inf is appropritate.
Be careful when swapping drivers. In addtion to providing equivalent
functionality, the protocol characteristics for each driver must contain the
same protocol name.
Dave
xxxxx@wipro.com wrote:
Have a NDIS 5.0 protocol driver along with a notify object and an inf [with
class as NetTrans]
After adding it from the Local Area Connection properties, the DriverEntry
& BindAdapterHandler are not getting called.
Is it that we need 2 inf’s for installing a transport protocol? Similar to
what we need for IM driver [Passthru]?
If I just replace the passthru.sys with my driver I find the driver entry
getting called. I also receive the NetEventBindsComplete PnP event.
Thanks,
Nitin
You are currently subscribed to ntdev as: xxxxx@okena.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Nitin,
Protocol drivers only require a single .INF file. It will get loaded by
NDIS if it is bound to any miniports. It will then call your
BindAdapter handler for each miniport it is bound to with each adapter’s
name. It should bind to one or more miniports if any of its
Ndi\Interfaces\LowerRange entries match up to a miniport’s UpperRange.
In the XP DDK, see the protocol driver Network\Ndis\Ndisuio\Sys as an
example.
As Dave rightly pointed out, the PASSTHRU and MUX samples require two
INFs because they are implementing both a protocol edge and a miniport
edge.
If your DriverEntry isn’t getting called, you have reviewed the bindings
and are confident that your driver should be loading, this may indicate
a completely different problem. It’s possible that you are importing a
function that is not supported, and therefore, your driver isn’t loading
at all. You might want to run DUMPBIN /IMPORT YOURDRIVER.SYS and review
the list of imported functions. Compare it to a driver that works.
Then verify any imported functions by running DUMPBIN /EXPORTS
<sysdriver.sys>.
Lastly, testing your driver on the checked build of the OS, or at least,
with the checked build of NDIS.SYS, with NDIS tracing enabled may help
verify that NDIS is attempting to load your driver and may indicate why
it is failing. See:
Q248413 [Win2K]
INFO: NDIS Debug Tracing and Kernel Debugger Extensions
For more information. Set DebugLevel to 0x00000000 and DebugSystems to
0xffffffff under HKLM\System\CurrentControlSet\Services\NDIS\Parameters
(both DWORDs).
Bryan S. Burgin
xxxxx@microsoft.com
bburgin x58049 40/2153
-----Original Message-----
From: Dave McCowan [mailto:xxxxx@okena.com]
Sent: Friday, December 21, 2001 5:03 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Does a protocol driver also need 2 inf’s? Need help
Nitin,
The passthru requires 2 inf files because it performs 2 functions: it
behaves
as a miniport on the upper edge and it behaves as a protocol on the
lower edge.
If your driver is a pure protocol driver, which means that it behaves as
a
protocol on the lower edge and supports TDI on the upper edge, then I
would
think 1 inf is appropritate.
Be careful when swapping drivers. In addtion to providing equivalent
functionality, the protocol characteristics for each driver must contain
the
same protocol name.
Dave
xxxxx@wipro.com wrote:
> Have a NDIS 5.0 protocol driver along with a notify object and an inf
[with
> class as NetTrans]
>
> After adding it from the Local Area Connection properties, the
DriverEntry
> & BindAdapterHandler are not getting called.
>
> Is it that we need 2 inf’s for installing a transport protocol?
Similar to
> what we need for IM driver [Passthru]?
>
> If I just replace the passthru.sys with my driver I find the driver
entry
> getting called. I also receive the NetEventBindsComplete PnP event.
>
> Thanks,
> Nitin
>
> —
> You are currently subscribed to ntdev as: xxxxx@okena.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com</sysdriver.sys>