×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

4.3.5 NBX OS

4.3.5 NBX OS

4.3.5 NBX OS

(OP)
Folks over at the www.nbxgroup.com have 4.3.5

Problems Corrected in Release 4.3.5

· If, after recording an Auto Attendant prompt, you hang up the telephone without pressing the pound key (#), the voice mail port that you were using is properly returned to service. Previously, if you failed to press the pound key the voice mail port became unavailable for use. (ID
5335)
· Previously, a call could not be answered under these conditions:
· The call was made to a linear hunt group, all members of which were busy,
· The call forwarding point of the hunt group was the same hunt group or another hunt group.

This issue has been resolved. (ID 5340)
· If you create a new Class of Service and apply it to a newly created user account, the CoS properly persists after a system reboot. Previously, the CoS changed after a reboot. (ID 5360)
· If you are using an analog telephone to blind transfer a call, the call is now properly transferred when you hang up the handset. Previously, the transfer did not complete successfully (ID 5378)

RE: 4.3.5 NBX OS

(OP)
4.3.5 does in fact correct the ATA BLIND transfer issue.

The older I get, the less I know

RE: 4.3.5 NBX OS

(OP)
Release Notes for Release R4.3.5
SuperStack? 3 NBX? Networked Telephony Solution
NBX 100 Communications System

!    CAUTION: To upgrade an NBX system to R4.3 software, you must first upgrade to NBX Release R4.2.7 or higher. If you upgrade from R4.2.6 or an earlier release, and then later reboot to that earlier release, 3Com 3102 Business Telephones become disabled and the error message "checksum error" appears in the telephone display panel. See the NBX System Software Upgrade Instructions on the NBX Resource Pack CD for detailed information on upgrading your system. (ID 5291)

!    CAUTION: 3C10165D E1 Digital Line Cards and 3C10116D T1 Digital Line Card can have their flash memory corrupted if you remove power from the cards or remove the cards from the NBX chassis while they are receiving their download after a system upgrade. (ID 5306)

NOTE: The SuperStack 3 NBX system is shipped with a factory default 4-digit dial plan. If you import any 3-digit plan, you must manually specify any 3-digit extension ranges that are not set by the imported plan. The NBX 100 system is shipped with a factory default 3-digit dial plan. If you import any 4-digit plan, you must manually specify any 4-digit extension ranges that are not set by the imported plan.
CAUTION: If you participated in the R4.3 Beta testing program and you received Beta hardware, be aware that after you upgrade your NBX system software from the Beta testing version to the final released version of R4.3, Beta versions of these hardware components will no longer be supported:
•    3Com Model 3101 and 3101SP Basic Telephones
•    3Com 3105 Attendant Console
•    3C10116D and 3C10165D Digital Line Cards
NOTICE: Starting with Release R4.2, the NBX system software requires a license. Upgrades from previous releases must be done with this requirement in mind. See the NBX System Software Upgrade Instructions for details on upgrading your system.

New Features in NBX Release 4.3    2
Applications in Release 4.3    3
Problems Corrected in Release 4.3.5    3
Problems Corrected Since Release 4.2    3
Known Anomalies and Considerations in Release 4.3    6
 
New Features in NBX Release 4.3
New 3Com Basic Telephones
NBX Release 4.3 introduces the 3Com 3101SP and 3101 Basic Telephones. The 3101SP Basic Telephone (3C10401SPKRA) has a microphone and supports speaker phone operation. The 3101 Basic Telephone (3C10401A) does not include a microphone and it does not support speaker phone operation. The 3101SP and 3101 telephones each have 4 programmable Access buttons that are mapped by default as 2 system appearances, Feature, and Transfer. The telephones support Power over Ethernet (PoE), wideband audio, and G.729 compression.
New T1 and E1 Cards
The 3C10116D T1 Digital Line Card is a second generation NBX T1 and ISDN Primary Rate Interface (PRI) Card. The 3C10165D E1 Digital Line Card is a second generation NBX E1 and ISDN Primary Rate Interface (PRI) Card. These new digital line cards support the functionality of the previous generation of NBX Digital Line Cards plus these new extended capabilities:
•    On-board Channel Service Unit (CSU) interface — An integrated CSU simplifies installation and configuration.
•    CSU statistics — You can use the NBX NetSet™ utility to view industry-standard near-end and far-end statistics.
•    Remote Layer 3 operation — Each new Digital Line Card can communicate with its Network Call Processor over a routed network.
•    Support for G.729 compression — You can configure the card to use G.729 audio compression and silence suppression for bandwidth efficiency.
New Attendant Console
Release 4.3 introduces the 3Com 3105 Attendant Console which supports up to 100 station appearances using 50 Access buttons and 4 Feature buttons. The 3105 Attendant Console supports Power over Ethernet and 10/100 connectivity.
Support for G.729A/B
Release 4.3 introduces a new voice codec to the existing codec set. G.729, an ITU standard, employs a sophisticated compression technique that compresses the audio information to 8kbit/sec. G.729A defines a method of compressing audio information. G.729 Appendix B (G.729B) defines a method of handling silence suppression.
New LabelMaker Utility
Release 4.3 introduces a new format for the NBX LabelMaker. This new LabelMaker, a Windows .exe file that you can download through the NBX NetSet utility, allows users and administrators to create labels for any 3Com Telephone or Attendant Console and then save the labels to a file.
Applications in Release 4.3
In addition to the Release 4.3 system software, Release 4.3 contains these applications:
•    NBX Complement Attendant Software R4.3.0    •    NBX TAPI Service Provider R4.3.1
•    NBX Call Reports R4.3.2    •    NBX Palm Dialer R1.1.3
•    NBX ConneXtions Gateway R4.0.1    •    3Com Network Supervisor V4.0.1
•    NBX pcXset? Soft Telephone R4.3.0    •    NBX Desktop Call Assistant R4.3.0
•    NBX Media Driver (formerly called WAV Driver) R4.3.0
Problems Corrected in Release 4.3.5
•    If, after recording an Auto Attendant prompt, you hang up the telephone without pressing the pound key (#), the voice mail port that you were using is properly returned to service. Previously, if you failed to press the pound key the voice mail port became unavailable for use. (ID 5335)
•    Previously, a call could not be answered under these conditions:
•    The call was made to a linear hunt group, all members of which were busy,
•    The call forwarding point of the hunt group was the same hunt group or another hunt group.
This issue has been resolved. (ID 5340)
•    If you create a new Class of Service and apply it to a newly created user account, the CoS properly persists after a system reboot. Previously, the CoS changed after a reboot. (ID 5360)
•    If you are using an analog telephone to blind transfer a call, the call is now properly transferred when you hang up the handset. Previously, the transfer did not complete successfully (ID 5378)
Problems Corrected Since Release 4.2
ID numbers in parentheses are for internal 3Com use.
3Com eXchange Call Center
•    Previously, when there was an idle agent on the system, calls were not always routed to an available agent and were not counted as queued. This problem no longer occurs. (ID 4602)
•    If someone is connected to the Auto Attendant and makes a call to a hunt group, the person answering the call now sees the hunt group number on the LINECALLINFO line in the telephone’s display panel.
(ID 4941)
3Com Telephones
•    Under very heavy network traffic conditions, telephones sometimes did not successfully receive software downloads. That problem has been resolved. (ID 4684)
•    In the telephone directory that appears on a 3Com telephone’s display panel, names that begin with a lower-case letter now appear in proper alphabetic order. Previously, all names beginning with an upper-case letter appeared first in the list, followed by names beginning with a lower-case letter.
(ID 5000)
Analog Terminal Card
•    A caller now hears audio from a conferenced IP telephone under these conditions:
•    A call is placed from analog telephone A to analog telephone B, both of which are connected to a 3C10117C Analog Terminal Card on NBX system A.
•    NBX system A uses IP On-the-Fly and both telephone A and telephone B are Ethernet (Layer 2) telephones.
•    The caller conferences a third telephone into the call. The third telephone is on the same subnet as NBX system A, but is an IP (Layer 3) telephone connected to NBX system B.
•    NBX system B is on a different subnet than NBX system A.
Previously, the caller on telephone A did not hear any audio from the IP telephone connected to NBX system B. (ID 4895)
AudioCodes
•    Previously, a caller heard ringing instead of immediately connecting to a voice menu under these conditions:
•    The call was placed from a SIP telephone connected to an AudioCodes box.
•    The AudioCodes box was connected to an NBX system through an ISDN PRI line.
•    The NBX system was connected to the PSTN through an ISDN PRI line.
•    The call destination was on the PSTN.(ID 4903)
Call Reports
•    Invalid dates are no longer accepted. When you specified an invalid date when defining a report, the date was accepted. The invalid date caused problems when you tried to run the report. (ID 3989)
Call Transfer
•    If user A attempts to transfer a call to user B when user B is on a call, the message “On A Call” now properly appears in the display panel on user A’s telephone. (ID 4926)
Caller ID
•    When an NBX system is connected to certain DMS100 voice switches, caller ID information is now properly received from the telephone company equipment. (IDs 3990 and 3991)
•    The system administrator can now select the way in which Caller ID information is transmitted from an NBX system to the Public Switched Telephone Network (PSTN) for forwarded or transferred trunk-to-trunk calls. Before NBX release R4.1.77, a call to an NBX system that was forwarded or transferred to an outgoing trunk contained the Caller ID information of the forwarding party, not the originating party. In NBX release R4.1.77 and later releases, a forwarded or transferred trunk-to-trunk call contains the Caller ID information of the originating party. However, some PSTNs do not connect calls unless the Caller ID information matches the forwarding telephone’s ID. Customers who want to send the forwarding party Caller ID on forwarded or transferred trunk-to-trunk calls must consult their representative for the instructions on how to make a change to the nboss.cfg file. (ID 4929)
•    See also ID 4584 under Virtual Tie Lines, (VTLs) for a description of CLIR over VTL calls.
Citel Analog Gateway
•    On a telephone connected through a Citel Analog Gateway, a caller who enters Feature Codes 403 through 408 now sees a “Not Supported” message in the display panel of the telephone. Previously, the caller heard an error code and the display panel flashed, but it did not contain an appropriate message. (ID 4766)
Digital Line Cards
•    If, in the NBX NetSet interface, you reconfigure the IP settings on a Digital Line Card and change only the default gateway address, the change now occurs. Previously, such a change did not occur unless at least one other parameter was also changed. (ID 4608)
•    The ISDN PRI stack Progress Indicator Information Element now contains correct information. (ID 4999)
•    If a call arrives at an NBX system on any Digital Line Card channel and is routed to any outgoing channel that is not in service (on either a Digital or Analog Line Card), the caller now properly hears a busy signal. Previously, the caller heard ringing but the call was never answered. (ID 5007)
Error Logs
•    The following misleading message no longer appears in the Nboss error log file:
TermSession    E 2004 : LastNumDialed by diverting party is NULL - SendCallState() will not contain szDivertingPartyDialedNum information
(ID 4653)
Hunt Groups
•    If you created a hunt group for fax machines, an outside caller who called the auto attendant and tried to leave a message in the hunt group voice mailbox (at AA prompt, enter the fax hunt group extension) was disconnected. You can now send a fax by dialing into a hunt group for fax machines. (ID 4171)
IMAP E-Mail Client
•    If you forward e-mail from the NBX system to one or more IMAP e-mail clients, the NBX system no longer experiences a memory leak. (ID 4506)
NBX System Log Files
•    Messages beginning with “Q931 Utils” no longer appear in the NBX system log files. These messages were previously added to the log files to help debug a problem and were never removed after the problem was resolved. (ID 4930)
NBX System Software
•    A memory leak that occurred when an NBX system was connected through an AudioCodes gateway to a Unified Messaging System has been fixed. (ID 4839)
NBX Voicemail
•    Callers who have more than 100 voicemail messages can now listen to any of the messages using their PC. Previously, they could listen to the first 99 messages using their PC but could listen to all messages using their telephones. (ID 4504)
•    Callers who create and send a voicemail message to a distribution list that contains their own names no longer see incorrect time duration for the message. Also, when those callers listen to the message, they no longer hear “The following message cannot be delivered to mailbox number xxxx.” (ID 4829)
Off-Site Notification
•    Off-Site Notification no longer fails if the default Class of Service groups “Default User Group” and “Super User Group” has been deleted. (ID 4726)
TAPI Route Points
•    Previously, the TAPI software could handle up to 256 simultaneous calls. Now, TAPI Route Points can handle up to 400 simultaneous calls on a SuperStack 3 NBX system, as designed. (ID 4320)
•    During the initialization of a TAPI Route Point, the maximum number of extensions is no longer limited to 19 instead of 400. (ID 4498)
Telephone Display Panel
•    In the directory that appears in the telephone display panel, names are now sorted correctly without regard to case sensitivity. (ID 4641)
Virtual Tie Lines (VTLs)
•    CLIR Next and CLIR All functions now work on VTL calls. However, you must add a pretranslator to the dial plan. See the Dial Plan chapter of the NBX Administrator’s Guide for information on how to add a pretranslator for caller ID over VTL calls. (ID 4584)
•    If a caller on a SuperStack 3 NBX system places a VTL hopoff call to an NBX 100 system, and the destination number is not valid, the VTL connection is now properly disconnected. Previously, a timing problem caused the VTL connection to remain in an unusable state. (ID 4834)
•    A caller now properly hears a busy signal under these conditions:
•    The call is placed from NBX system A over VTL to NBX system B.
•    The call hops off to from NBX system B over and ISDN PRI line.
•    The number being called is busy.
Previously, the caller heard ringing instead of a busy signal. (ID 4939)
Known Anomalies and Considerations in Release 4.3
ID numbers in parentheses are for internal 3Com use only.
3Com eXchange Call Center
•    If "Handsfree on Transfer" is enabled system-wide, an external call that is redirected to an agent after being queued to an NBX TAPI Route Point extension initiates Hands Free mode if the agent has enabled the Hands Free feature on the telephone. Hands Free mode should apply only to internal calls. To eliminate this behavior, you can use the NBX NetSet utility to disable Handsfree on Transfer (System Settings > System Wide) for all telephones on the system. (ID 5096)
Attendant Consoles
•    On a 3Com 1105 or 3105 Attendant Console, if you map a button to the Hunt Group Login feature, and you have that button/feature active (the Hunt Group member has used it to log in), the LED for that button is lit. If you then associate the Attendant Console with a different telephone extension whose user is a member of that same Hunt Group but not currently logged in, the LED remains lit. (ID 5281)
•    On a 3Com 1105 or 3105 Attendant Console, if you map a button to the Do Not Disturb (DND) feature, and you have that button/feature active, the LED for that button is lit. If you then associate the Attendant Console with a different telephone extension whose user does not have DND activated, the LED remains lit. Incoming calls will ring normally at the new extension, however, if you press that lighted button on the Attendant Console, the telephone’s LCD correctly displays "Do Not Disturb," but that user will be connected with voice mail of the original telephone’s extension. (ID 5282)
Automated Attendant
•    If you record an Auto Attendant prompt, and then hang up the telephone before you press the # key to save the new prompt, the voice messaging port can become unavailable until after the next system reboot.  
For example, In the NBX NetSet utility, you have added a new Auto Attendant. (NBX Voice Messaging > Auto Attendant > Add) When you record a prompt for the new Auto Attendant, the system issues this prompt,
 “Please make your recording after the tone and then press pound.”
If you record the new prompt and then hang up the phone without pressing the # key, one voice messaging port becomes unavailable. If you record a number of prompts without pressing the # key, you might eventually “hang” all the voice mail ports on the system, and then any attempt to access voice mail results in the message, "ALL PORTS Busy." (ID 5199)
Browser Issues
•    If you click the Help button on any screen in the NBX NetSet utility, then close the Help window and click the Help button again, the Help window might display incomplete information. (ID 3118)
•    Viewing the NBX NetSet utility with Microsoft Internet Explorer might result in this error message, “Page cannot be located” along with the error number 800C0007
Workaround:
1.    From the Microsoft Internet Explorer Tools menu or the View menu (depending on your version of Internet Explorer), select Internet Options.
2.    Click the Advanced tab, and scroll to HTTP1.1 Settings.
3.    Clear the two checkboxes titled “Use HTTP1.1” and “Use HTTP1.1 through proxy connections.”
4.    Reboot the PC.
(ID 3121)
CALLER ID
•    A call from an internal extension that is forwarded to an external number might fail to connect if the CO checks the validity of the caller ID string before completing the call. (ID 5192)
Digital Line Cards
•    3C10165D E1 Digital Line Cards and 3C10116D T1 Digital Line Card can have their flash memory corrupted if you remove power from the cards or remove the cards from the NBX chassis while they are receiving their download after a system upgrade. (ID 5306)
•    Digital Line Cards 3C10165D (E1) and 3C10116D (T1) do not support DHCP Option 184, which is used by NBX devices to receive the IP address of the Network Call Processor. See the NBX Administrator’s Guide for complete information on how to configure IP address information for these Digital Line Cards. (ID 5109)
•    3C10165D E1 Digital Line Cards and 3C10116D T1 Digital Line Cards do not support DHCP lease times of less than 20 minutes.
•    T1.231 and TR 54016 near End performance data does not accurately report severely errored framing events. A severely errored framing event is reported when the number of framing bit errors exceeds 2 in one second, which causes a greater number of severely errored framing events to be reported than actually exist. (ID 4764)
•    On a system where Trunk-to-Trunk transfers are enabled, a caller that dials into the NBX system from the PSTN and is then transferred to an integrated voice response (IVR) system over a PRI connection, cannot select options on that IVR system. The NBX system does not correctly transmit the DTMF tones that are sent when the caller presses buttons on the phone. This issue exists only in R4.1.71 and higher releases. A workaround exists for this issue. However, the workaround causes a different issue if the call is forwarded to a 3Com V3700 Unified Messaging System. For information on the workaround, contact the 3Com Customer Service Organization. (ID 5011)
•    3C10165D E1 Digital Line Cards and 3C10116D T1 Digital Line Cards do not support the NBX IP On-the Fly feature. If your system uses IP On-the-Fly, then you must assign a static IP address to the card or use DHCP to assign an IP address to the card, even if the card will be installed on the same subnet as the NCP. (ID 5109)
•    3C10165D E1 Digital Line Cards configured as Multiframe with CRC4, HDB3, ETSI, cannot detect bi-polar violations. The problem does not happen if the line code is AMI, instead of HDB3. (ID 5129)
Hunt Groups and Calling Groups
•    If you select several hundred users to be included in a hunt group that you are creating, the transfer of these names into the hunt group takes several minutes to be completed. (ID 3150)
•    Linear hunt group behavior is inconsistent when the hunt group members are bridged extensions. This example of a four-member hunt group illustrates the behavior:
1000 is first in the hunt group and it is a primary bridged extension.
1001 is second in the hunt group and it is the first secondary bridged extension of 1000.
1002 is third in the hunt group and it is the second secondary bridged extension of 1000.
1003 is fourth in the hunt group and it is the third secondary bridged extension of 1000.
A call to the hunt group extension rings extension 1000. The bridged station appearances on all secondaries ring and light up, and the call is forwarded to the voice mail of the hunt group if no one answers the call. If you remove the secondary bridge on extension 1002, a call to the hunt group rings extension 1000, and the bridges 1001 and 1003 ring and light up. Then 1002 rings as a member of the hunt group. Then 1003 rings as a member of the hunt group. If no one answers, the call is transferred to the voicemail of the hunt group. (ID 3158)
International
•    The Italian prompt for the Off-Site Notification is incorrect. To access the prompt, log into your personal mailbox, press 9 for mailbox options, and then press 4. The prompt you hear refers to logging off the voicemail box instead of the prompt for setting up Off-Site Notification. (ID 3157)
•    The Exit prompt (“To return to the previous menu, press *”) is missing from UK voice mail, Mailbox Options menu. (ID 5239)
NBX Devices Configured Behind a Home Router/Firewall
•    If you have an NBX device configured behind a D-Link DI-640 router, the port to which the device is attached may become disabled periodically. (ID 3927)
Workaround for ID 3927: Disconnect the NBX device, reboot the router, and reconnect the NBX device.
•    If you have an NBX device configured behind a 4-port LinkSys Cable/DSL plus Voice Router, the NBX device can no longer communicate with the host NBX system if you change the port to which the device is connected or if you change the IP address of the device. (ID 3928)
Workaround for ID 3928: Remove and reapply power to the LinkSys router.
•    If you send a VPIM message to an NBX device configured behind a home router/firewall, the VPIM software does not use the correct IP address. (ID 3960)
NBX Media Driver
•    If you run the NBX Media Driver Configuration Wizard on a PC running Windows NT, clicking the System Information button results in an error:  "System information is unavailable at this time." (ID 5290)
Workaround for ID 5290: You can access System Information through Start > Programs > Administrative Tools or the Windows NT Control Panel.
NBX Palm Dialer Application
The NBX Palm Dialer application supports only versions 3.5 and 4.1 of the Palm operating system.
•    Under the following conditions:
•    You use a Palm Personal Digital Assistant (PDA) with version 3.5.2 of the Palm Operating System.
•    You are on a call.
•    You try to set up a conference call or to transfer the existing call.
The error message “make call first / no resources” appears in the display panel of your NBX Business Telephone and the status light associated with the next System Appearance button remains lit indefinitely. (IDs 743 and 3163)
NBX TAPI Service Provider (NBXTSP)
•    You cannot use Remote TSP clients with Windows NT, Windows XP Home, or Windows 98.
(ID 4640)
•    If you replace a telephone that is using a TAPI application, you must reboot the NBX system before the new telephone will be able to connect to and work with the TAPI application. (ID 5159)
 
NBX System Software
•    To upgrade an NBX system to R4.3 software, you must first upgrade to NBX Release R4.2.7 or higher. If you upgrade from R4.2.6 or an earlier release, and then later reboot to that earlier release, 3Com 3102 Business Telephones become disabled and the error message "checksum error" appears in the telephone display panel. See the NBX System Software Upgrade Instructions on the NBX Resource Pack CD for detailed information on upgrading your system. (ID 5291)
•    Enabling VLAN Control disables WAV devices. (ID 1917)
•    If you navigate to System Settings > Regional Settings > Advanced, the Israel and Russia entries in the list should show English as the language because the documentation is not translated into Hebrew or Russian. (ID 4000)
NBX Voice Messaging
•    If you use the Call Logs on your NBX telephone while you are listening to one of your voice mail messages, the messaging system behavior is not predictable. For example, the message you are listening to may be deleted or saved, or you may hear the time and date stamp information for the message. (ID 3796)
•    If you configure e-mail as your first and second method of off-site notification, you receive the first e-mail notification with the voice message attached but the second e-mail has no attachment. (ID 3144)
•    Under some conditions, the VPIM Statistics indicate that a higher-than-actual number of calls were successfully delivered. (ID 3258)
Polycom Telephony Equipment
•    If a Polycom Telephone is located behind a home router or firewall device, the time and date information in the display panel is updated only when certain external events occur. For example, if you make or receive a call, the display panel information, including the time and date information, is updated.
(ID 3910)
Telephones
•    Cordless Telephones are included the NBX NetSet utility interface and the NBX LabelMaker utility. However, cordless telephone support has been deferred to a future release. (ID 4591)
•    The button mappings on a 3Com 3102 Business Telephone might occasionally revert to the default mapping and then change back to your customized mapping. Typically this is an isolated issue that affects only a small percentage of the 3102 telephones on a system. (ID 5312)
Virtual Tie Lines (VTLs)
•    If an external call is forwarded from one NBX system to another over a VTL connection before the Central Office equipment provides caller ID information, the caller ID information may not be sent over the VTL connection to update the destination telephone’s display panel. (ID 3996)

The older I get, the less I know

RE: 4.3.5 NBX OS

My Vendor cannot download 4.3.5 from 3Com currently. Is it out or what?

RE: 4.3.5 NBX OS

donporter-
Your vendor should be able to download 4.3.6, which replaces 4.3.5, at the ftpnbx download site.

RE: 4.3.5 NBX OS

I have problem with 3com NBX auto attendant
My software is 4.3.14

The problem is that all days work fine exept thursday. When i put a custom greeding through the menu tree tab to be played on thursday the NBX plays nothing. Instead if a greeding is apllied in wendsday it plays that greeding. So in short the software sees thursday as wensday and nothing i do can fix that problem. I tried to upgrade to 4.3.14 and nothing has been fixed

Please help

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close