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?

Admittedly, if ProtocolBindAdapter is called, it’ll reject the bindings
since I’m
using the imsamp oemsetup.inf file with just our .sys instead, but the
problem is
it’s not even getting started.

(We’re busy removing all the PnP code so that it’ll compile under Win98
DDK…)

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)

(Off topic a little)
Under Win98, our W2KDDK-compiled driver doesn’t give any debug output at all
in
Rterm98. If I’ve used a non-existant export, would Win98 complain like NT-4
did?
(Not in the debugger, but in a dialog on screen) or do I have to keep
trimming fn
calls until I find the culprit?

And a last Q: If I give WinDBG the symbols for both Win2K and NT4 in
different dirs,
will it be able to find the appropriate ones, or will it fail the timestamp
on the
first symbol it finds with the correct name, and stop searching the symbol
path?

Using the latest WinDBG. 2.00.0023 I think.

Anyways, thanx for all that…

=========================================================
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