releasenotes.txt Driver File Contents (wdm371d.exe)

;*************************************************************************
; Dynalink ISDN Adapter Driver release notes
; By Bert Keizer
; 24-01-2002 
;
;  
; release Version 3.07.01
;
; Win98, Win98SE, 
; Windows ME, Windows 2000
; Windows XP 
;
;
; If you have questions, tips or other suggestions: mail us.
;*************************************************************************
;
;
; Version 03.07.01
;
; Fixed: Windows XP(1 CPU), Passive USB W type
;         1. System will crash while D channel is activated
;         All Windows platforms Passive USB W type
;
; Fixed: a illegal pointer access in some special condition, especially WinXP
; Fixed; a problem will cause a "MULTIPLE_IRP_COMPLETION"
;
;
;
; Version 3.07.00
;
;
; Fixed: a endless loop while processing INFO ELEMENT
; Fixed: a bug which will cause a deadlock in NDISWAN driver running in 2k/XP
; v.110 can work normally on P-IN100-ST-D2 and PC-100
; NDISWAN driver can select V.110
; ISDN monitor will display trash after running for a long time
;
;
;
; version 3.6.92
; 
; Fixed: Problem with Standby (Windows XP)
;
;
; Version 3.6.8 [official 'experience' release]
; 
; Fixed: problem of crash system when scanning for new hardware (Win98)
; Fixed: bug causing isdn TA loose D channel messages when the CPU-load is 100%
; Fixed: NDISWAN crashed system under Windows XP
;
; Version 3.6.79 (beta driver not released)
; Fixed some problems for Windows 2000 / Windows XP
;
; Version 3.6.7 (beta, not released)
;
; add supplementary services
; - CF Activate (Call Forwarding)
; - CF Deactivate (Call Forwarding)
; - CF Interrogate Parameters (Call Forwarding)
; - CF Interrogate Numbers (Call Forwarding)
; - CD (Call Deflection)
;
;
; Version 3.6.6 (official It's raining release)
;
; Fixed: Virtual NDISWAN device did not work (sometimes, since 3.6.5)
; Fixed: System crash when changing the MLP/BOD setting of the NDISWAN device (since 3.6.6)
; fixed: D-channel did not receive signalling data after Windows reconfigured hardware resources
;
; Version 3.6.5 (beta not released)
; Fixed: incompability issue between our passive USB ISDN TA and OHCI USB controller
; Fixed: isdn monitor crashed when saving the log
; fixed: bug in EARLY_B3_CONNECT BVRP Phonetools crashed
; add: CAPI AP can issue a CONNECT REQ with CIP=0
; fixed: Encoding INFO ELEMENT of FACILITY
; fixed: LED control of our passive USB TA with winbond chipset
; New: support for Windows XP added (beta2 version only)
; fixed: a bug could crash windows when the device was starting
; 
; Version 3.6.4 (beta)
; Minor improvements (isdn monitor, bod)
;
; Version 3.6.3 (release version prior beta version)
; Fixed: After a CAPI application established a call, and abnormally abort.
; the call will be released.
; Fixed: When the ISDN TA is paralleled with other TA and there is an 
; activation and deactivation of the S0-bus the driver will not work
; Change: saved log will show more detailed information about the OS
; Fixed: bug which could cause a Dual Processor system freezing
; Fixed: bug windows 2000 cannot shutdown with USB TA
; Added: support for multiple PCMCIA ISDN TA devices in one notebook.
;
; Version 3.6.2 (only for beta testers)
; * Fixed: bug in Ndiswan device. After some changes in the MLPPP settings
;   callback will fail.
; * fixed: bug in Ndiswan device. if MLPPP BOD include more than 3 channels
;   a bugger will overflow correct an error in CAPI management, if MLPPP
;   BOD include channels on different TA, only the channgels on the main
;   device will connect
; * Change: incoming call management, to avoid locating new call on a
;   using slot
;
; Version 3.6.1 (release version)
; *fixed: Internal ISDN TA can work again after resuming 
;  from hibernation (w2k)
; PCI ta can normally hibernate in such a system (Asus K7V 4x AGP)
; *added feature: support multicard of PC Card TA
; *fixed: cancel routine problem between CAPI and NDISwan driver
; *fixed: restart problem (after stopped in Win98/ME of the passive USB
;  TA
;
; Version 3.6.0 (not released)
; Fixed: X.75 Packet size problem. 
;
; Version 3.5.9 (not released)
; *fixed: Bug of not activating the D-channel when the USB TA was in use
; *fixed: Windows ME can suspend now (this was prevented by vport in
; previous driver version)
; *changed/fixed: After installation Windows98/ME has to restart to
; enable 16bits CAPI DLL and VxD CAPI. 
; *fixed: Linetest will report the errorcode more precisely
;
; Version 3.5.8 (not released)
; *fixed: bug of control the PCI ISDN card (D-Channel). If there was an 
; error (underrun, over flow or collission), it could happen that the 
; data received maybe wrong in sequence
;
; Version 3.5.7 (not released)
; *New feature: Support of Supplemental Services over CAPI Interface
;
; Version 3.5.6
; * Fixed: When a POTS call was made, the B channel was not released. This
;  will prevent other paralleled ISDN CPE to use the B-channel
;
; Version 3.5.5 (not released)
; * Improved: Increased the primitive bugger of the 
; physical layer to ensure POTS
; function is working correctly
; Version 3.5.4 (released 10-07-2000)
;
; * Changed: data sequence recovery in BOD mode
;   Linetesthas high priority to avoid incoming call being catched by 
;   Ndiswan.
;   Changer Layer 3 checking while suspending (according behaviour Ndiswan)
;   if any channel is not in IDLE state, reject to pwer down (old style)
;   If no channel is in ACTIVE state, confirm to power down (new style)
;
; Version 3.5.3 (not released)
; * Changed: No response to a setup if there is no free channel
;   Fixed a null pointer in WANLINK (log a LinkAllocate)
;   Correct of mis-judgement in our passive USB TA
;   Fixed a bug of our PCI ISDN Adapter. When the Operating System stops
;   the hardware an then start the device (reconfiguration) again the device
;   did not work properly when the ISDN cable was inserted.
;
; Version 3.5.2 (not released)
; * Fixed buffer leakage when there was a INFO_IND generated
;   Fixed null pointer whele changing MLPPP setting
;   Allow MLPPP slave channel accept first MLPPP data (problem occured when
;   a Win2000 server was in use)
;   Fixed suspend problem with our USB device since 3.4.8
;
; Version 3.5.1 (not released)
; * Fixed a bug in an overlap sending setup since 3.4.9
;    A null CAPI_INFO_IND caused problem in a multi-processor machine
;
; Version 3.5.0 (not released)
; * Fixed a bug for our passive USB while disconnecting 1B if 2B was in
;    use. 
;    Changed layter 2 state maintenance (null cct)
;
;  Version 3.4.9 (not released)
; * Changed layer 2 state maintenance. 
;   Numbering plan for Japan changed
;
; Version 3.4.8 (not released)
; * Some W2K fixes
;
; Version 3.4.7 (not released)
; * Fixed bug in ISDN monitor after logging for a long time, open log 
;   viewer will crash
;   Fixed bug of 16 bits CAPI20.DLL
; 
; Version 3.4.6 (not released)
; * Fixed error of MLP (BOD) user control for Windows 2000
;   Changed CAPI_INFO_IND implementation
;   Changes in Ndiswan aliasname (W2K)
;   Changed in ISDN monitor when stop loggin in some circumstances
;
; Version 3.4.5 --> Release version 02-03-2000
; * Fixed an illegal pointer while IRP_MN_STOP_DEVICE
;   Fixed an illegal pointer while no user responding an incoming call
;
; Version 3.4.4 (not released)
; * Fixed voice card restart problem when Window reconfigure HW resources
;   provide user control on MLP(BOD)
;   fix some bugs of UUS (User to User Signaling)
;   enhance CAPI INFO IND for call progress.
;   user can edit some extra command for active TAs
;
; Version 3.4.3 (not released)
; No fixes for passive USB, some minor fixes
;
; Version 3.4.2 (not released)
; implementation for PCMCIA ISDN card. 
;
; Version 3.4.1 (released)
; * Bug fixed: Passive USB will disconnect after some AP grab cpu for a while
;
; end
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: web4, load: 0.96