loading sys drivers as protocols

 This may be OT, but i have to ask (otherwise i would had to create yet another user/password
for some more appropriate forum).

 I have successfully compiled and tested the uitest.exe from ndisprot (renamed from old ndisuio) example
found on Driver Development Kit CD. The Windows itself contains the ndisuio.sys driver, but it's
functioning is subject to change (an already known issue, won't repeat it here all over again).

 Now i have two chioces : either use ndis shipped with Windows and risk possible incompatibility
between Windows versions or updates or having to manually install the ndisprot example network protocol
driver (which i'd like to avoid).

 So, i would like to load the ndisprot, but programmatically. I already tried the service loading/starting
examples, but it doesn't help here.

 More to the point, the ndisprot driver can be programmatically loaded but it is not bound to any
network adapters. The effect of this can be seen when the uiotest example is changed to call built-in
ndisuio.sys.

 When the programmatically loaded ndisprot is used, uiotest does not enumerate any devices. When this
driver is loaded as protocol with provided inf file, it works ok. OTOH, ndisuio works immediately since
it is properly loaded during system startup.

-- 
Best regards,
 soya



------------------------ Yahoo! Groups Sponsor --------------------~--> 
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.
http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/i7folB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/Delphi-JEDI/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/