> -----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Vodicka, Michal
Sent: Thursday, 1 March 2001 6:29
To: NT Developers Interest List
Subject: [ntdev] RE: Win2K and NT4 intermediate Q’s, plus one or two
other s.> ----------
> From: Paul “TBBle” Hampson[SMTP:xxxxx@Pobox.Com]
> Reply To: NT Developers Interest List
> Sent: Wednesday, February 28, 2001 5:48 PM
> To: NT Developers Interest List
> Subject: [ntdev] Win2K and NT4 intermediate Q’s, plus one or two
> others.
>
> Trying to port a Win2K intermediate driver to NT4…
>
> DriverEntry is being called, but ProtocolBindAdapter isn’t. The
status at
> the end
> of DriverEntry is 0, so I dunno what’s wrong. Is NT4 that different
> underneath to
> Win2K in that respect?
>
It is probably caused by incorrect registry configuration i.e.
oemsetup.inf
file. Writting correct one is probably the most difficult part of NT4 IM
driver development. You can temporarily create correct adapter information
by hand, it will work until binding engine is called (so don’t
touch NCPA).
Do you know if the IMSAMP from Microsoft has a working
oemsetup.inf file? Certainly my adapters and things
appeared in network control panel AOK, and DriverEntry
runs, so I assumed I was somewhat correct. And the
protocol is bound to a network card or two (Even the
upper half of itself!)
> Also, under Win2K, our notify DLL is unable to remove our
> driver without a reboot,
> and the miniport-part seems to be locked in memory due to a process
> waiting on an event from (somewhere) in a call to PtGetRelatedDevice (I
> think, I forgot about
> this problem until recently, and we’re focussing on the OS porting right
> now)
>
There are some bugs. I’m not sure what exactly do you mean by ‘remove
driver’ (uninstall or just unload?). As a workaround I disable
all drivers’
devices and OS unloads driver automatically. It can be uninstalled without
problems in this state. Also, if you want just reload it, update image,
re-enable devices and OS will load it back. I’m not sure if there are some
additional problems when notify DLL is used, I have a NDIS filter
driver and
there is (fortunately!) no need for notify DLL.
Unfortuneately, if I disable the miniport, it hangs
Device manager, and I won’t be able to shutdown.
If I do uninstall, it tells me I need to reboot, but the
miniport’s still present after reboot, although with a ?
'cause the driver .sys file is removed when the protocol
uninstalls.
I meant to say, (and this is the important bit!) it’s a
WAN/TAPI adapter, and this only happens (Can’t disable)
after I have dialed (or attempted to dial) through the
driver. Before this, I think it uninstalls properly,
although it still insists on rebooting, even when our
ApplyRegistryChanges returns OK, not NEED_REBOOT.
Another IM driver doing a similar thing works fine in
that way.
Michal Vodicka
Thanx for those suggestions, I’m gonna go try and work
out the oemsetup.inf and registry formats now!
=========================================================
Paul “TBBle” Hampson
xxxxx@Pobox.Com
Even a mosquito doesn’t get a slap
on the back until it starts to work.
Random signature generator 2.0 by TBBle
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