Netcnucm.inf Driver File Contents (dcm200_drivers_win_2.zip)

;============================================================================
;   Installation file for the D-Link USB Cable Modem
;   Copyright (C) 1999-2000 D-Link Co. Ltd.
;   http://www.dlink.com
;============================================================================

[version]
Signature   = "$Chicago$"
Class       = Net
ClassGUID   = {4d36e972-e325-11ce-bfc1-08002be10318}
CatalogFile = netcnucm.cat
Provider    = %DLINK%
DriverVer   = 10/25/2000, 1.0.2.6

; MAE NOTE - HCT 9.502 complains about this next line, 9.6 does not. A quick search through the NTDDK network
; .inf help file has this line included (section 4.1.2)
Compatible  = 1                    ; works with Win2K and Win9x 

;LayoutFile  = layout.inf // MAE Commented this out to fix warning

[Manufacturer]
%V_MANUFACTURER% = D-Link

[D-Link]
;
; Display Name          Section           DeviceID
;_________________________________________________________________ 
%ndiscm.DeviceDesc% =   ndiscm.ndi,       USB\VID_2001&PID_9414


[ControlFlags]
;
; Provides limited control on UI dispalys and events during installation.
; Must for any device on an enumerable bus like USB
;
ExcludeFromSelect = USB\VID_2001&PID_9414


;
; Windows 98 specific entry
;
[ndiscm.ndi]
AddReg = ndiscm.id.reg, ndiscm.9x.reg, common.reg 
CopyFiles       = ndiscm.9x.CopyFiles        ;MAE Added this line

;DeviceID = "USB\VID_2001&PID_9414" //MAE COMMENTED OUT - Looks like its only in the registry section
;LogConfig = DefaultConfig //MAE COMMENTED OUT - This I think is only used for non-PNP devices

;
; Windows 2000  specific entry
;
[ndiscm.ndi.NT]
Characteristics = 0x84                       ; NCF_PHYSICAL | NCF_HAS_UI ??
BusType         = 15                         ; PNPBus // MAE This is a problem with net.pm not having any concept of PNPBus for networks cards
AddReg          = common.reg, ndiscm.nt.reg  ;
CopyFiles       = ndiscm.nt.CopyFiles        ;


[ndiscm.ndi.nt.Services]
AddService = ndiscm, 2, ndiscm.Service, common.EventLog

;----------------------------------------------------------------------------
; Win9x id registry sections
; These are not needed by NT
;
[ndiscm.id.reg]
HKR, Ndi, DeviceID, 0, "USB\VID_2001&PID_9414"


;-----------------------------------------------------------------------------
; common registry entries
;
[common.reg]


;-----------------------------------------------------------------------------
; WIN2K (NT) specific
;
[ndiscm.nt.reg]
HKR, Ndi,                       Service,    0, "ndiscm"
; use ndis5 as the upper bound because NT supports it
HKR, Ndi\Interfaces,            DefUpper,   0, "ndis5"
HKR, Ndi\Interfaces,            DefLower,   0, "ethernet"
HKR, Ndi\Interfaces,            UpperRange, 0, "ndis5"
HKR, Ndi\Interfaces,            LowerRange, 0, "ethernet"


[ndiscm.Service]
DisplayName     = %ndiscm.Service.DispName%
ServiceType     = 1 ;%SERVICE_KERNEL_DRIVER%
StartType       = 3 ;%SERVICE_DEMAND_START%
ErrorControl    = 1 ;%SERVICE_ERROR_NORMAL%
ServiceBinary   = %12%\netcnucm.sys
LoadOrderGroup  = NDIS
AddReg          = TextModeFlags.reg


[common.EventLog]
AddReg = common.AddEventLog.reg

[common.AddEventLog.reg]
HKR, , EventMessageFile, 0x00020000, "%%SystemRoot%%\System32\netevent.dll"
HKR, , TypesSupported,   0x00010001, 7

[TextModeFlags.reg]
HKR, , TextModeFlags, 0x00010001, 0x0001


;----------------------------------------------------------------------------
; Win9x specific
;
[ndiscm.9x.reg]
HKR, ,              DevLoader,          0, "*ndis"
HKR, ,              DeviceVxDs,         0, "netcnucm.sys"
HKR, ,              EnumPropPages,      0, "netdi.dll,EnumPropPages"
; memphis appears to not support the ndis5 upper range, so use ndis3
HKR, Ndi\Interfaces,DefUpper,   	0, "ndis3"
HKR, Ndi\Interfaces,DefLower,   	0, "ethernet"
HKR, Ndi\Interfaces,UpperRange, 	0, "ndis3"
HKR, Ndi\Interfaces,LowerRange, 	0, "ethernet"


HKR, NDIS,          LogDriverName,      0, "NDISCM"
HKR, NDIS,          MajorNdisVersion,   1, 03
HKR, NDIS,          MinorNdisVersion,   1, 0A

HKR, Ndi\Install,   ndis3,              0, "ndiscm.install"

[ndiscm.install] ; MAE This section flags as a warning, but is used by the registry install reference
CopyFiles = ndiscm.9x.CopyFiles 


[SourceDisksNames]
1 = %Disk1%,,,

[SourceDisksFiles]
netcnucm.sys = 1 

;-----------------------------------------------------------------------------
; DestinationDirs
;
[ndiscm.nt.CopyFiles]
;netcnucm.sys,,,2 ; MAE Commented out this line
netcnucm.sys      ; MAE Replaced it with this line

[ndiscm.9x.CopyFiles]
;netcnucm.sys,,,2 ; MAE Commented out this line
netcnucm.sys      ; MAE Replaced it with this line

[DestinationDirs]
DefaultDestDir = 12        ; MAE Added this line 
ndiscm.nt.CopyFiles = 12
ndiscm.9x.CopyFiles = 11

[Strings]
DLINK    = "D-Link"
Disk1    = "Installation disk 1"

;
; String that gets displayed while installing the device
;
ndiscm.DeviceDesc = "D-Link USB Cable Modem"

;
; NT Service name
;
ndiscm.Service.DispName = "D-Link USB based Cable Modem NT Driver"
V_MANUFACTURER = "D-Link Co. Ltd."

Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web3, load: 2.27