Hi,
Win9x have dynamic loading vxd’s, which means
that, when ever an application request to open/get a
handle to the driver, the OS will dynamically load the
driver. Also when the last handle to the driver is
closed, the OS will dynamically unload the driver.
“CreateFile API” in an application requests for
openning of the Handle to the driver and becomes the
triggerer for the respective driver to load.
“CloseHandle API” triggers the unloading of the driver
if and only if the handle which is closing is the last
that the driver owns.
!!! - ??? #@*&%#$^&*^*@^# (Confused)
I wonder, Is there a “DriverEntry” in the VXD
world?
I all these days believed that, it is the system
initialization message such as Sys_Critical_Init,
Device_Init, and Init_Complete is dispatched on vxd
loading sequence.
Cheers,
Jay
— xxxxx@accton-sh.com wrote:
hi dear all:
I find a strange problem when I load/unload vxd in
win98.
in the firstly load vxd in my application, the vxd’s
DriverEntry will be
entered, but only the first times, if I use
CloseHandle to unload the vxd
in my user mode application, then I load the vxd use
createfile again, but
I find the Vxd’s DriverEntry have not be entered,
why???
thanks
You are currently subscribed to ntdev as:
xxxxx@yahoo.com
To unsubscribe send a blank email to
leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.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