Hi All,

I have a WDM driver for W2k/XP for a NIC this **IS NOT AN NDIS
DRIVER** but a normal WDM driver that allows direct access to the NIC
hardware. The hardware is a 3COM 3c90x on PCI. Once the driver is
installed the user is not able to change any network settings for
other installed network drivers (that do use NDIS drivers). The
properties of other installed network drivers is disabled. The client
has to uninstall the non-NDIS WDM driver to change the network setting
and then re-install.

Why is this and how can I prevent it?

Cheers,
SAB.

Re: WDM NIC driver causes diabling of all network properties by Eliyas

Eliyas
Tue Oct 19 08:16:21 CDT 2004

What is the setup class of your WDM driver? Shows us your INF. I have
written a similar driver for Intel NIC and don't have any issue.

--
--
-Eliyas
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/whdc/driver/default.mspx
http://www.microsoft.com/whdc/driver/kernel/KB-drv.mspx



"Simon Block" <sblock@computer.org> wrote in message
news:d09f6417.0410121547.37e8d2fc@posting.google.com...
> Hi All,
>
> I have a WDM driver for W2k/XP for a NIC this **IS NOT AN NDIS
> DRIVER** but a normal WDM driver that allows direct access to the NIC
> hardware. The hardware is a 3COM 3c90x on PCI. Once the driver is
> installed the user is not able to change any network settings for
> other installed network drivers (that do use NDIS drivers). The
> properties of other installed network drivers is disabled. The client
> has to uninstall the non-NDIS WDM driver to change the network setting
> and then re-install.
>
> Why is this and how can I prevent it?
>
> Cheers,
> SAB.



Re: WDM NIC driver causes diabling of all network properties by sblock

sblock
Thu Oct 21 19:51:28 CDT 2004

Hi Eliyas,

I use a private (non-standard) class for my clients devices. Here is the INF file:
(thanks in advance for any help)
;;----------------------------------------------------------------------------

[Version]
Signature="$WINDOWS NT$"
Class=StrobeHardware
ClassGuid={D311AF5B-7D8E-4ed7-89F0-F769FCCC8085}
Provider="Strobe Data Inc."
CatalogFile=Osp3c90x.cat
DriverVer=11/27/2002, 1.0.0.06

[SourceDisksNames]
1=%DiskId%

[SourceDisksFiles]
Osp3c90x.sys=1

[ClassInstall32]
Addreg=StrobeHwClassAddReg

[StrobeHwClassAddReg]
HKR,,,,%ClassName%
HKR,,Icon,,"-5"

[DestinationDirs]
DefaultDestDir=12

[Manufacturer]
%Mfg%=DeviceList

;[ControlFlags]
;ExcludeFromSelect=*

;------------------------------------------------------------------------------
; Device List
;------------------------------------------------------------------------------

[DeviceList]

; 3COM 3c90x Series
%3c90x-TX% = Install_3c90x, PCI\VEN_10B7&DEV_9050
%3c90x-TPO% = Install_3c90x, PCI\VEN_10B7&DEV_9000
%3c90x-COMBO% = Install_3c90x, PCI\VEN_10B7&DEV_9001

; 3COM 3c90xB Series
%3c90xB-TX% = Install_3c90x, PCI\VEN_10B7&DEV_9055&SUBSYS_905510B7
%3c90xB-TPO% = Install_3c90x, PCI\VEN_10B7&DEV_9004&SUBSYS_900410B7
%3c90xB-COMBO% = Install_3c90x, PCI\VEN_10B7&DEV_9005&SUBSYS_900510B7
%3c90xB-TPC% = Install_3c90x, PCI\VEN_10B7&DEV_9006&SUBSYS_900610B7
%3c905B-COMBO% = Install_3c90x, PCI\VEN_10B7&DEV_9058&SUBSYS_905810B7

; 3COM 3c90xC Series
%3c90xC-TX% = Install_3c90x, PCI\VEN_10B7&DEV_9200&SUBSYS_100010B7

;------------------------------------------------------------------------------
; Pointers to DriverCopyFiles Sections
;------------------------------------------------------------------------------
[Install_3c90x.NT]
CopyFiles=Osp3c90xDriverCopyFiles

;------------------------------------------------------------------------------
; Osp3c90x Section
;------------------------------------------------------------------------------
[Osp3c90xDriverCopyFiles]
Osp3c90x.sys,,,2

[Install_3c90x.NT.Services]
AddService = Osp3c90x,%SPSVCINST_ASSOCSERVICE%,Osp3c90xService

[Osp3c90xService]
ServiceType = %SERVICE_KERNEL_DRIVER%
StartType = %SERVICE_MANUAL_START%
ErrorControl = %SERVICE_ERROR_NORMAL%
ServiceBinary = %12%\Osp3c90x.sys

[Install_3c90x.nt.hw]
AddReg=Osp3c90xHwAddReg

[Osp3c90xHwAddReg]
HKR,,FriendlyName,,%Osp3c90xFriendly%
HKLM,%NicParamsPath%,,,
HKLM,%NicParamsPath%,%BreakVal%,0x00010003,0
HKLM,%NicParamsPath%,%AllowNot%,0x00010003,0

;------------------------------------------------------------------------------
; Strings Section
;------------------------------------------------------------------------------

[Strings]

;---------------------------------------------------------------
; Manufacturer and Class Descriptions
;---------------------------------------------------------------
Mfg = "Strobe Data Inc."
ClassName ="Strobe Data Emulation Cards"

;---------------------------------------------------------------
; Device Descriptions
;---------------------------------------------------------------
Osp3c90xFriendly = "3Com 3c90x Dequina Emulation Card"

3c90x-TX = "3Com 3C905TX-based Dequina Emulation Card"
3c90x-TPO = "3Com 3C900TPO-based Dequina Emulation Card"
3c90x-COMBO = "3Com 3C900COMBO-based Dequina Emulation Card"

3c90xB-TX = "3Com 3C905B-TX Dequina Emulation Card"
3c90xB-TPO = "3Com 3C900B-TPO Dequina Emulation Card"
3c90xB-COMBO = "3Com 3C900B-COMBO Dequina Emulation Card"
3c90xB-TPC = "3Com 3C900B-TPC Dequina Emulation Card"
3c905B-COMBO = "3Com 3C905B-COMBO Dequina Emulation Card"

3c90xC-TX = "3Com 3C905C-TX Dequina Emulation Card"

;------------------------------------------------------------------------------
; Registry Paths and Initial Values
;------------------------------------------------------------------------------
NicParamsPath = "SYSTEM\CurrentControlSet\Services\Osp3c90x\Parameters"

BreakVal = "BreakOnEntry"
AllowNot = "AllowNotFound"

;---------------------------------------------------------------
; Disk ID String
;---------------------------------------------------------------
DiskId = "Strobe Data Osp3c90x Drivers Install disk (1)"

;---------------------------------------------------------------
; Service Control Keys
;---------------------------------------------------------------
SPSVCINST_ASSOCSERVICE = 2
SERVICE_KERNEL_DRIVER = 1
SERVICE_MANUAL_START = 3
SERVICE_ERROR_NORMAL = 1




"Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message news:<#xUDN3dtEHA.220@TK2MSFTNGP15.phx.gbl>...
> What is the setup class of your WDM driver? Shows us your INF. I have
> written a similar driver for Intel NIC and don't have any issue.
>
> --
> --
> -Eliyas
> This posting is provided "AS IS" with no warranties, and confers no rights.
> http://www.microsoft.com/whdc/driver/default.mspx
> http://www.microsoft.com/whdc/driver/kernel/KB-drv.mspx
>
>
>
> "Simon Block" <sblock@computer.org> wrote in message
> news:d09f6417.0410121547.37e8d2fc@posting.google.com...
> > Hi All,
> >
> > I have a WDM driver for W2k/XP for a NIC this **IS NOT AN NDIS
> > DRIVER** but a normal WDM driver that allows direct access to the NIC
> > hardware. The hardware is a 3COM 3c90x on PCI. Once the driver is
> > installed the user is not able to change any network settings for
> > other installed network drivers (that do use NDIS drivers). The
> > properties of other installed network drivers is disabled. The client
> > has to uninstall the non-NDIS WDM driver to change the network setting
> > and then re-install.
> >
> > Why is this and how can I prevent it?
> >
> > Cheers,
> > SAB.