NMFirewalls.ini Driver File Contents (DFE530TX__driver__346.zip)

; $Date: 2005/07/13 $
; $Revision: #1 $
;
; -----------------------------------------------------------------------------
;
; The information in this file is used to discover if any firewalls are installed AND
; running on the system.  This information can then used to properly message connection
; failures, in case a firewall is blocking connectivity.
;
; The format for this file is as follows:
;
; [Name of Firewall]
; VendorId=<n>
; RegKey1=<RegKey>
; RegKey2=<RegKey>
; .
; .
; .
; RegValue1=<RegValue>
; RegValue2=<RegValue>
; .
; .
; .
; Process1=<ProcessName>
; Process2=<ProcessName>
; .
; .
; .
;
; -----------------------------------------------------------------------------
;
; Where VendorId=<n> is used to indicate the vendor of the firewall.  Replace the
; <n> portion with an integer from the list of known (supported) vendors:
;
; Use VendorId=0 for generic (i.e. any vendor not specifically mentioned in the list).
; Use VendorId=1 for McAfee.
; Use VendorId=2 for Norton.
; Use VendorId=3 for ZoneAlarm.
; Use VendorId=4 for PC-Cillin.
; Use VendorId=5 for Black Ice.
;
; You can use the same VendorId number in multiple sections, but only once in a
; given section.  If you use a VendorId number that is not supported, the default
; of generic will be used.
;
; DO NOT just add new VendorId numbers, thinking it will work.  It won't.  Adding
; a new VendorId requires corresponding DLL code changes.
;
; -----------------------------------------------------------------------------
;
; Where <RegKey> is a registry KEY, with an optional root key prefix.  For example:
;
;   RegKey1=HKEY_LOCAL_MACHINE:Software\Zone Labs\ZoneAlarm
;
; and the prefix in this case is HKEY_LOCAL_MACHINE:
;
; The prefix can be any one of:
;   HKEY_LOCAL_MACHINE:
;   HKEY_CLASSES_ROOT:
;   HKEY_CURRENT_USER:
;   HKEY_USERS:
;
; Further, the prefix is optional, and if omitted defaults to HKEY_LOCAL_MACHINE:
; You can specify as many RegKey1=<RegKey> lines as you like, but make sure there is
; NO GAP in the numbers used in the RegKeyN= key.  In otherwords, if you
; want to specify three reg keys to look for, then you MUST use RegKey1=...,
; RegKey2=... and RegKey3=...
; If you used 1, 2 and 4 then the "4" item would not get checked.
;
; -----------------------------------------------------------------------------
;
; Where <RegValue> is a registry VALUE, with an optional root key prefix.  For example:
;
;   RegValue1=HKEY_LOCAL_MACHINE:Software\Zone Labs\OEM
;
; <RegValue> works EXACTLY THE SAME as <RegKey>, EXCEPT that it looks for a VALUE.
;
; In the example, above, HKEY_LOCAL_MACHINE:Software\Zone Labs is the KEY, and OEM is
; the value in that KEY.  That actual contents of the OEM value are IGNORED.  It is
; simply checked for EXISTENCE, when determining if the firewall entry is present on
; the machine.
;
; -----------------------------------------------------------------------------
;
; Where <ProcessName> is the name of a process that will be *running* on the machine
; when the firewall check is done.  For example:
;   Process1=MpfAgent.exe
;   Process2=MpfTray.exe
;
; The comparison of process names is done without regard for upper/lower case.
; When deciding what to use for a process name, a good guide is to use what
; task manager displays.
; The numbering rules for Process1= Process2= etc are the same as for RegKey1=, as
; mentioned above.
;
; -----------------------------------------------------------------------------
;
; As an example, here is a section that will match against a McAfee firewall:
;
;   [McAfee]
;   VendorId=1
;   RegKey1=HKEY_LOCAL_MACHINE:Software\McAfee.com\Personal Firewall
;   Process1=MpfAgent.exe
;   Process2=MpfTray.exe
;
; All three items (1 reg key & 2 processes) MUST be found for the firewall to
; be considered "found".
;
; WARNING: The strings in this file should NOT BE LOCALIZED, unless you really,
; really, really know what you are doing.
;
; -----------------------------------------------------------------------------

[McAfee]
VendorId=1
RegKey1=HKEY_LOCAL_MACHINE:Software\McAfee.com\Personal Firewall
Process1=MpfAgent.exe
Process2=MpfTray.exe

[McAfee v2.10]
VendorId=1
RegKey1=HKEY_LOCAL_MACHINE:Software\McAfee\McAfee Firewall
Process1=cpd.exe

[Norton]
VendorId=2
RegKey1=HKEY_LOCAL_MACHINE:Software\Symantec\SymNetDrv
RegValue1=HKEY_LOCAL_MACHINE:Software\Symantec\InstalledApps\Norton Internet Security
Process1=ccpxysvc.exe

[Norton 2002 DE]
VendorId=2
RegKey1=HKEY_LOCAL_MACHINE:Software\Symantec\IAM
RegValue1=HKEY_LOCAL_MACHINE:Software\Symantec\InstalledApps\Norton Internet Security
Process1=NISSERV.EXE
Process2=Sympxsvc.exe

[Norton 2002]
VendorId=2
RegKey1=HKEY_LOCAL_MACHINE:Software\Symantec\IAM
RegValue1=HKEY_LOCAL_MACHINE:Software\Symantec\InstalledApps\Norton Internet Security
Process1=NISSERV.EXE
Process2=SYMPROXYSVC.EXE

[Norton 03/04]
VendorId=2
RegKey1=HKEY_LOCAL_MACHINE:Software\CLASSES\CcFWSettg.FirewallSettings
RegValue1=HKEY_LOCAL_MACHINE:Software\Symantec\InstalledApps\Norton Internet Security
Process1=ccapp.exe

[ZoneAlarm Pro]
VendorId=3
RegKey1=HKEY_LOCAL_MACHINE:Software\Zone Labs\ZoneAlarm
Process1=ZAPro.exe

[ZoneAlarm Plus]
VendorId=3
RegKey1=HKEY_LOCAL_MACHINE:Software\Zone Labs\ZoneAlarm
Process1=zlclient.exe

[ZoneAlarm]
VendorId=3
RegKey1=HKEY_LOCAL_MACHINE:Software\Zone Labs\ZoneAlarm
Process1=zonealarm.exe

[ZoneAlarm plus 3.7]
VendorId=3
RegKey1=HKEY_LOCAL_MACHINE:Software\Zone Labs\ZoneAlarm
Process1=zaplus.exe

[PC-Cillin]
VendorId=4
RegKey1=HKEY_LOCAL_MACHINE:Software\TrendMicro\PC-cillin
Process1=pccguide.exe
Process2=PCCPFW.exe
Process3=tmproxy.exe

[Black Ice]
VendorId=5
RegKey1=HKEY_LOCAL_MACHINE:Software\Network Ice\BlackIce
Process1=BlackD.exe
Process2=BlackIce.exe

;
; Generic firewalls (i.e. not specifically recognized by vendor name)
;

[Tiny 5.5]
VendorId=0
RegKey1=HKEY_LOCAL_MACHINE:Software\Tiny Software\Tiny Personal Firewall
Process1=UmxTray.exe
Process2=UmxAgent.exe
Process3=UmxPol.exe
Process4=UmxCfg.exe

[Tiny 4.5]
VendorId=0
RegKey1=HKEY_LOCAL_MACHINE:Software\Tiny Software\Tiny Personal Firewall
Process1=amon.exe

[Sygate]
VendorId=0
RegKey1=HKEY_LOCAL_MACHINE:Software\Sygate Technologies, Inc.\Sygate Personal Firewall
Process1=smc.exe

[Panda]
VendorId=0
RegKey1=HKEY_LOCAL_MACHINE:Software\Panda Software\Firewall
Process1=apvxdwin.exe

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.64