Product Finder

Select a Product

Support

ESP Driver for Windows XP/2003 IA-64 WHQL

Driver Name:

Version:

6.0.0.3

File Size:

1.35 MB

Post Date:

28-Jun-07

File Name:

espxp2k3_ia64_6.0.0.3.exe
(Click to Download)

Release Notes: Windows XP/2003 IA-64 ESP Driver (WHQL)

Note: This version is for IA-64 systems running Windows XP or Windows 2003 only.

Note: Prior to installation, turn off Windows updates (via System->Hardware Tab->Windows Update button). This will prevent Windows from downloading an older, signed version of the driver.

Release Notes for Version 6.0.0.3

Build for WHQL release. The following table gives the ESP application and bootstrap firmware versions for this release:

Model	Application Version	Bootstrap Version
ESP-2 MI	3.12b	0.82
ESP-2 OPTO	3.10	0.81
ESP-4 MI	3.12b	0.82
ESP-8 MI (Avocent)	3.12b	1.05
ESP-16 MI (Avocent)	3.12b	1.05
ESP-8 (Equinox)	3.05d	3.80
ESP-16 (Equinox)	3.05d	3.41

Fix for goBTS bug 19858 - BSOD during uninstall with espdiag.exe running.
Fix for BSOD when doing more than one replace of the same esp.
Fix for ESP setting two stop bits.

Release Notes for Version 6.0.0.2

Build for WHQL release.

Release Notes for Version 6.0.0.1

Vista driver support. Note we will use TDI at this point.
Fix for goBTS bug 15939.

Release Notes for Version 4.0.0.6

Added the IP address to the friendly name for device manager.
Added a Notes field to the co-installer properties page. The customer can add now comments to an ESP, i.e. the location of the ESP in a large deployment.

Release Notes for Version 4.0.0.5

Added SET_XOFF and SEX_XON to be reported in epc_commstat. Also got rid of EspOut and EspIn for all ep_commstat, epc_commstatexp2 and epc_commstatexp. Need to add support for SET_XOFF and SET_XON to work exactly like the serial.sys driver and then to put back both IOCTL_SERIAL_GET_COMMSTATUS aggregation and sending.

Release Notes for Version 4.0.0.4

Beta release for the CD and web.

Release Notes for Version 4.0.0.3

Fixed Windows XP SP2 where we would not EpcReconnect when TDI failed. If you do a Soft/Hard reboot, the COM ports would not always come back with SP2 installed. McDonalds saw the problem with XP Embedded with SP2.

Release Notes for Version 4.0.0.2

Fixed IOCTL_GET_COMMSTATUS to return the stats collected from the driver for the ESP-8. A customer application would used the received chars number to read that many times and the driver would be out of sync where IRP_MJ_READ would return a len=0 at low baud rates.

Release Notes for Version 4.0.0.1

Fix for a secure GPS application using the ESP-8 MI.

Release Notes for Version 4.0.0.0

Added Avocent branded ESP-8 MI and ESP-16 MI models.
Fix for old generation ESP-8 MI to get both RLSD and DSR events where there is an EPC_CS_DELTA for DCD.
Added support for IOCTL_SERIAL_GET_STATS and IOCTL_SERIAL_CLEAR_STATS.
Fixed two synchronous race conditions bugs in the driver that revealed themselves on the x64 with 4 processors.
Added x64 support.
Changed the replace esp functionality to allow the replacement of ESP serial hubs based on the number of serial ports only.

Release Notes for Version 3.5.8.09

Added ESP-4 MI support.
Fixed a timing problem with respect to espxin where the Friendlyname would be overwritten.
Fixed the coinstaller when you installed an MI that needs the IP Address assigned and then selected the Back Button. You would get an error when you then select the Next Button again. I now do not allow the Back Button to be selected after the IP Address is assigned for an ESP unit that does not have an IP Address. The Interface Select Wizard Page will now not allow the Back Button when an ESP Unit is assigned an IP Address on installation. (WE003980)
Fixed the coinstaller where the Port Dialog Box would truncate digits for the IP address when the IP address was 9 or more digits. (WE004224)

Release Notes for Version 3.08.5

Fixed where if you enabled Auto Flash Update and then tried to Disable Auto Flash Update the ESP would still send the TFTP request for a Flash download.
Fixed the UpdateFlash dialog that was broke with respect to the GUI, i.e. Going from Enable Auto Flash Update to Disable Auto Flash update the GUI would not present the saved entries for Auto Flash Update correctly.

Release Notes for Version 3.08.04

Fixed where Perist Open works with the optimization on GET_MODEM_STATUS and GET_COMM_STATUS.

Release Notes for Version 3.08.03

Fixed IOCTL_SERIAL_GET_COMMSTATUS for the ESP-2MI, ESP-2MI OPTO and ESP-MC where we would send the packet to the ESP when it was not necessary to do.
Allowed espureg changes to place without a reboot and to be applied with the ports are open.

Release Notes for Version 3.08.02

Allowed the heart beat rate and frequency change to take effect without a reboot. Allowed perist open, features and the heart beat rate and frequency to work with the Replace ESP functionality.

Release Notes for Version 3.08.01

Added support for persist open.

Release Notes for Version 3.07.01

Added support for the ESP-4 Mc and the ESP-4 Mc POE.

Release Notes for Version 3.07.00

The Port Properties Dialog was showing more than None and Xon/Xoff flow control for the ESP-2 OPTO. (pr11160)
Fixed "Unknown Esp type returned on query" error when trying to update flash on an ESP-2 OPTO. (pr11324)
Fixed when IOCTL_SERIAL_GET_MODEMSTATUS was called and sendmodemstatus was off we need to remap the saved de_msr bits.
Fix to show the Boot and App Flash versions on the Upgrade Flash Screen. Properties->ESP->Update Flash->Next. You will see the Application Version: and Boot Version:. You can then select Cancel if you do wish to upgrade the neither the Flash nor Boot.
Added the IP Address and Physical Port Number to the Ports Property Page. Select Properties on any Equinox ESP Port->Port Settings. You will see the IP Address and the Physcial Port Number.

Release Notes for Version 3.06.27

Unable to transfer files using Zmodem or Zmodem with crash recovery with Hyperterminal using 2003 (pr10510)
Very slow transfer rates using ESP ports with Hyperterminal using 2003.
Added sendmodemstatus and sendcommstatus control with espureg.exe. Note that sendmodemstatus in off by default for each port while sendcommstatus is on by default for each port. espureg.exe is now part of the ESP package.
Added ESP-2 OPTO support.

Release Notes for Version 3.06.26

ESP-16 would have its ports permuted when all the ports were moved as a block. (pr7856 and pr10008)
Changed text in ESP setup.exe to mention Windows 2000 or above systems. (pr10124)
Fixed where setup.exe would give an error message unable to read registry key. (pr10114)
Fixed where espdiag.exe would fail with an error message unable to retrieve unit status. This only happened with the IA64 driver package. (pr10117)
Fixed where epcsendpending() when gathering data on a write would hang when the length got bigger than the transmit window. (pr10421)
Fixed where eqxloop.exe would give a Dr. Watson access error it you started eqxloop.exe, stopped, selected the property icon, canceled and then did a restart. (pr10417)
Fixed where if you did a replace the esp property page showed defaults but the driver was using previous changed values if the values had been changed by the user. Now after a replace the driver is set the defaults and so the property page and driver agree after a replace. So after a replace the ESP is put back to defaults. (pr10426)

Release Notes for Version 3.06.18

Completed the WHQL certification allowing the driver to be digitally signed for Windows 2000, XP, and Server 2003.
Updated the ESP Property page that allow for selecting a starting Com number and to move all other Com Ports to be contiguous from that number.
Fixed a bug where if the Port Monitor from Equiview Plus is running and you change the Com port numbers the Port Monitor would not see it.
Fixed a bug where you could give the same IP address to an Inited ESP if the IP address belonged to an uninstalled ESP.
Fixed an issue in 2K when you would move the COM portsn the Device Manager would not show the hour glass Cursor. This was very confusing to the user because for 2K moving the Com ports can take a long time. The driver now shows and hour glass Cursor when required.
Added yellow text to the INUSE and CURR icons in the Device Property Page combo. If you see yellow text it means the port is disabled.
Fixed an issue when you have a COM Port on a computer being used by a device and the name of the device is less than the Characters in Equinox ESP Port. Eqxloop would repeat the COM port number of the device.
Created a workaround for a Windows issue in XP / 2003 where the Uninstall (Advanced) Button would not uninstall the ports and left the Com Aribiter still claiming the ports. Note: Microsoft is aware of this issue
Fixed broken heart in the ESP property page where it was showing a gray rectangle around the broken heart.
Added a WM_TIMER to the ESP property page where the broken heart is updated. You do not need to exit the ESP property page and re-enter to see the true status of the heartbeat for the ESP.
Saving the ESP property page data on a per dialog basis. You can open multiple ESP property pages and see the status.
Added our own Port Settings Dialog for our Equinox ESP Ports. This includes a Line Parameters dialog - Bits/Second, Data Bits, Parity, Stop Bits, Flow Control.
Added help for the Port Settings Dialog for our Equinox ESP Ports.
Changed esp.sys to identify support for 230400 bits per second with the Equinox ESP Ports property page.
Changed two cancel routines, read and write to check if the irpSP is zero.

Release Notes for Version 3.06.4

Added changes to the coinstaller where you now have a ComboBox on the ESP Property page that allows you to select a starting Com Number to move all the Com Ports to be contiguous from that number. This works with the independent moving of the ports given by the msports.dll.
Fixed a bug where if the Port Monitor from Equiview Plus is running and you change the Com port numbers the Port Monitor would not see it.
Fixed a bug where you could give the same IP address to an Inited ESP if the IP address belonged to an uninstalled ESP.
Fixed a bug in 2K where when you would move the COM ports Device Manager would not show the hour glass Cursor. This was very confusing to the user because for 2K moving the Com ports can take along time. I now show and hour glass Cursor. Note that the SST driver will need the same workaround for 2K as the ESP now has.
Added yellow text to the INUSE and CURR icons in the Device Property Page combo. If you see yellow text it means the port is disable. For example you get INUSE with a Yellow is you Disable some other Com port not belonging the Current ESP. If you Disable a Current Port belonging to the ESP you get CURR with yellow text. INUSE with yellow text shows when you use a Com port with the kernel debugger too.
Fixed a bug that was found in System Test. If you have any other COM Port on a computer being used by a device, for example a modem and the name of the device is less than the Characters in Equinox ESP Port, eqxloop would repeat the COM port number of the device. Note the Com port had to appear before the Com ports being used by the ESP This is now fixed too.
Fixed Eqxloop not showing the X marks correctly when there are errors.
As a workaround fixed a bug in XP / 2003 where the Uninstall (Advanced) Button would not uninstall the ports and left the Com Aribiter still claiming the ports. Note Microsoft is aware of the bug and should fix in either a service pack or Longhorn and then this workaround would not be necessary. It is now fixed in the coinstaller.

Release Notes for Version 3.06

Added support for the ESP-2 MI.

Release Notes for Version 3.05

Win2000:

Driver Installation will automatically start the eqmtftps.exe service.

Driver Update will unload the old driver, load the driver and start and stop the service all automatically. So no need for reboot when Driver Update is done. This is with any other driver after this Driver. All subsequent ESP drivers will support Dynamic Driver Updating with No Reboot Needed. This works completely with 1 installed ESP driver.

Driver Uninstall will completely unload the esp driver from memory. This works completely with 1 installed ESP driver.

When the user does a Driver Update no need to ask for the IP address since this is already known anyway. In the past the user could enter a duplicate IP causing our driver to fail. So now on with Driver Update no need to ask the IP address.

On bootup, Driver Install and Driver Update are much faster. We had a delay on installing the individual ports but not now.

We had a bug when all the ESPs already had IPs in firmware but the computer had no previous ESP driver "service" installed. Before we would fail to install unless you reinitialize the ESP firmware. Now you can install without reinitializing the ESP device.

We can not now enter an existing IP address of any installed ESP device as the IP address to use for a new ESP device during installation.

XP:

Our Driver now works with XP.

Fixed eqxloop.exe to work with both our SST and ESP products for XP.

Release Notes for Version 3.01

NOTE that this release of the ESP requires that you FLASH update the ESP. Instructions for performing the flash update using EquiView Plus are available upon completion of the ESP software installation or upgrade.

The correct steps are:

Using EquiView Plus, update the ESP Application to version 3.01
Reboot the ESP

ESP Application version 3.01 is installed on the Windows 2000 server with this ESP release, but each ESP's FLASH must also be updated as described above. You may also use the new ‘Update Flash’ feature in the Device Manager if you are not using EquiView Plus.

The ESP software and Device Manager plug-in have been updated to support the Multi-Interface ESP and the 10/100 ESP products.
A new Automatic ESP FLASH update feature has been implemented. This feature allows you to customize the ESP to automatically FLASH update itself each time a new driver package is installed or updated. Refer to the online help for the ‘Update Flash’ wizard of the Device Manager.
The ESP configuration applet has been enhanced to support user-configurable ESP connection timeouts. This allows you to have additional control of when a connection failure between an ESP and its host will be declared. This advanced feature is intended for applications that need a failover mechanism between two different hosts on a network that share an ESP’s serial ports.
Fixed a timing problem with setting control signals and then reading them back. This problem was discovered during testing with external loopback connectors. Raising a control signal, such as DTR, and the reading back the control signals to see if the signal had correctly looped back as DCD may fail due to the timing problem.
Fixed a test timeout problem with the EquiView Plus loopback test. If a timed loopback test is started, but no data is received, the test never timed out.
Fixed a problem issuing resets to the COM ports. COM port resets were not correctly acknowledged by the ESP which caused the application’s IOCTL to fail.
ESPAPP.IMG Version 3.01 (03/20/01)
The ESPAPP.IMG embedded application now implements functions that support the Windows 32API calls for SETXOFF and SETXON.
The ESPAPP.IMG embedded application will no longer accept connections from hosts when memory resources are low. Previously, attempting to connect with more than 8 hosts could cause a memory allocation error resulting in a system reboot.
The ESPAPP.IMG SST driver has been corrected to prevent output of characters during initialization after power up. This does not correct problems with BREAK transmission during transient power conditions.
ESP.SYS Version 3.01
The ESP.SYS device driver now implements functions that support the Windows 32API calls for SETXOFF and SETXON.

BIOS Bootstrap Release Notes Version 3.41

The Linux dhcpd will not return the subnet and router RFC1048 option fields unless the BOOTP request contains the required 'magic cookie' value 0x63, 0x82, 0x53, 0x63. This has been added to comply with RFC1048. The NT DHCP server returned options regardless of the setting of the vendor extension field.

Release Notes for Version 3.00

NOTE that this release of the ESP requires that you FLASH update the ESP. Instructions for performing the flash update using EquiView Plus are available upon completion of the ESP software installation or upgrade.
The correct steps are:
Using EquiView Plus, update the ESP Application to version 3.00
Reboot the ESP

ESP Application version 3.00 is installed on the Windows 2000 server with this ESP release, but each ESP's FLASH must also be updated as described above. You may also use the new ‘Update Flash’ feature in the Device Manager if you are not using EquiView Plus.

The ESP software and Device Manager plug-in have been updated to support the Multi-Interface ESP and the 10/100 ESP products.
A new Automatic ESP FLASH update feature has been implemented. This feature allows you to customize the ESP to automatically FLASH update itself each time a new driver package is installed or updated. Refer to the online help for the ‘Update Flash’ wizard of the Device Manager.
The ESP configuration applet has been enhanced to support user-configurable ESP connection timeouts. This allows you to have additional control of when a connection failure between an ESP and its host will be declared. This advanced feature is intended for applications that need a failover mechanism between two different hosts on a network that share an ESP’s serial ports.
Fixed a timing problem with setting control signals and then reading them back. This problem was discovered during testing with external loopback connectors. Raising a control signal, such as DTR, and the reading back the control signals to see if the signal had correctly looped back as DCD may fail due to the timing problem.
Fixed a test timeout problem with the EquiView Plus loopback test. If a timed loopback test is started, but no data is received, the test never timed out.
Fixed a problem issuing resets to the COM ports. COM port resets were not correctly acknowledged by the ESP which caused the application’s IOCTL to fail.
Release Notes for Version 2.00
NOTE that this release of the ESP requires that you FLASH update the ESP. Instructions for performing the flash update using EquiView Plus are available upon completion of the ESP software installation or upgrade.
The correct steps are:

· Using EquiView Plus, update the ESP Application to version 2.07

· Reboot the ESP

ESP Application version 2.07 is installed on the NT server with this ESP release, but each ESP's FLASH must also be updated as described above.
A problem with SNMP initialization has been corrected in the ESP embedded application.
A BSOD problem with the driver has been corrected. It was possible for the driver to attempt to send delayed data after the TCP connection had been lost resulting in a crash. The delayed send logic now verifies the state of the TCP connection before sending.

Known Problems with Version 2.00

Pressing and holding the RESET button on the front of the ESP unit will cause the ESP to reboot. However, if it is held too long (more than about 3 seconds), the ESP may not come back ONLINE. The ESP must be power-cycled to clear this condition.
After running the EquiView Plus datascope application for a long period of time, the ESP does not forward data to the EquiView Plus management workstation. EquiView Plus indicates that the datascope is running, but no data is received from the ESP. The ESP MIB agent is not correctly forwarding datascope file information to EquiVIew Plus. Stopping and restarting the datascope corrects this problem.

Release Notes for Version 1.56

Initial release version of Windows 2000 ESP support.
Added COM port to the ESP tab of the Device Manager’s Properties.
Added the SETUP.EXE file for registering the ESP Multiport Serial Adapter co-installer.