Networking
Year 2000 Compliance
|
| Model | Component | Hardware | Software Version | Year 2000 ready | Change |
| MainWay 2001 MainWay 2005 MainWay 2005-E MainWay 2010 MainWay 2020 MainWay 2030 MainWay 2040 |
LAN Extender | LS 2200 | 8.1.2-1 | Update | |
| LP 6000 or CB 6000 | 4.3.1-3 (LMM Classic) |
|
Oct 12, 1999 | ||
| 7.0.0-39 / 8.3.2 (LMM+) when IS and ES | |||||
| CB 3500 | 1.0 | Oct. 16, 1998 | |||
| WAN Subsystem | WP or EWP | DNS-E V2U3 ET06 | Mar 30, 1999 | ||
| S-ONP, ONP or F-ONP | DNS-E V2U3 ET06 | Mar 30, 1999 | |||
| Service Processor | Any | SP 07.06-2 | Mar 30, 1999 | ||
| MainWay 2600 | LAN Extender | LS 2200 | 8.1.2-1 | Update | |
| CB 3500 | 1.0 | Jun 3, 1999 | |||
| CB 9000 | 2.0 | Jun 3, 1999 | |||
| WAN Subsystem | WP or EWP | DNS-E V3U1 | Jun 3, 1999 | ||
| S-ONP, ONP or F-ONP | DNS-E V3U1 | Jun 3, 1999 | |||
| Service Processor | Any | SP 08.02 | Jun 3, 1999 | ||
| MainWay ICC | ICC Subsystem | Any | Any | Oct. 16, 1998 |
(1) Year 2000 ready when running in conjunction with the
built-in 3Com product CoreBuilder 6000 (previously named LANplex 6000) including :
- either the board LMM Classic (3C6301) at software level
4.3.1-3 or higher.
- or the board LMM+ (3C6311) at software level 7.0.0-39,
8.3.2 or higher when intelligent switching software (IS) and extended switching software
(ES).
More detailed Year 2000 information is available on 3Com website.
(2) Year 2000 readiness requires the installation of the
Y2K kit which depends on the Service Processor HW platform :
- on DPX/20 (Product code : CPUJ009-0100), the Y2K kit
(Product Codes : CNMR002-MW20 and CNHR037-S0A0) includes DNS-E V2U3 ET06D upgrade, AIX
version 3.2.55 and SP build 07.06-2 upgrade;
- on Estrella (Product codes : CPUJ017-0100, CPUJ017-0200,
CPUJ017-1100 or CPUJ017-1200), the Y2K kit (Product-codes : CNMR003-MWES and CNHR042-S0A0)
includes DNS-E V2U3 ET06 upgrade, AIX version 4.2 and SP build 07.06-2 upgrade.
Click here to see MainWay 2000 / 2600 Year 2000 readiness in details.
Datanet
| Model | Software version | Year 2000 ready | Change |
| DN7500/xx | DNS V4U1 ET22 | No | |
| DN7500/xx | DNS V4U3 ET28 | Oct. 16, 1998 | |
| DN71xx | Any | No (2) | Oct. 16, 1998 |
| DN7100/xx | Any | No (2) | Oct. 16, 1998 |
| DN8/xx | Any | No (2) | Oct. 16, 1998 |
| CpNet5105 | Any | No (2) | Oct. 16, 1998 |
(2) Not Year 2000 ready even running DNS V4U3 ET28.
Click here to see Datanet Year 2000 readiness in details.| Hardware Subsystem | Software Version | Year 2000 ready | Change |
| CNP7 | CNS7 A2U3 ET30 | Oct. 16, 1998 | |
| CNP7 | CNS7 A2U0 ET14 | Oct. 16, 1998 | |
| CNP7 | CNS7 A2U2 ET26 | No | April 30, 1997 |
| FCP7 | FCP7 | Oct. 16, 1998 |
Click here to see GCOS 7 Year 2000 readiness in details.
| Hardware Subsystem | Software version | Year 2000 ready | Change |
| FCP8 | |||
| DXE (or DX) | Oct. 16, 1998 | ||
| G8LINK | No | ||
| OPEN8 | No |
Click here to see GCOS 8 Year 2000 readiness in details.
| Family | Model | Year 2000-ready | Change |
| Bull Questar | BQ200 / BQ205 / BQ210 | N/A | Dec. 9, 1998 |
| BQ303 / BQ305 / BQ306 | N/A | Dec. 9, 1998 | |
| BQ310 / BQ310C | N/A | Dec. 9, 1998 | |
| BQ330 | Dec. 9, 1998 | ||
| BQ380 | N/A | Dec. 9, 1998 | |
| WID Terminals | WID Terminal | Dec. 9, 1998 | |
| WID 210 / 220 / 221 / 230 / 231 | Dec. 9, 1998 | ||
| WID 300 | Dec. 9, 1998 | ||
| Others | MICRO / TCS | Dec. 9, 1998 |
Click here to see Terminals Year 2000 readiness in details.
| Model | Hardware Subsystem | Software version | Year 2000-ready | Change |
| BQ200 | BQ200 (Base Q400) | All | Dec. 9, 1998 | |
| BQ200 (Base Starsys) | All | Dec. 9, 1998 | ||
| BQ350 | BQ350 | 6.2.1.12 (3C5440D) | Feb 19, 1999 | |
| BQ350 | 6.2.1 (3C5441D) | Feb 19, 1999 | ||
| BQ380 | BQ380 (Base BM200) | Dec. 9, 1998 | ||
| BQ380 (Base Z-Station 420 Sn) | Dec. 9, 1998 | |||
| BQ380-2 (Base Z-Select 100) | Dec. 9, 1998 | |||
| BQ380-3 (Base Z-Station ES/P) | All | Dec. 9, 1998 | ||
| BQ380-4 (Base Z-Station EL) | All | Dec. 9, 1998 | ||
| BQ390/GALATA | Dec. 9, 1998 | |||
| Terminal Servers | TCU7022 | Dec. 9, 1998 | ||
| TCU704x | Dec. 9, 1998 | |||
| TCU705x | Dec. 9, 1998 | |||
| WID Servers | Any Y2K ready NT server | WinFrame 1.6 | No (2) | Feb 19, 1999 |
| WinFrame 1.7 | Feb 19, 1999 | |||
| MetaFrame 1.0 | Feb 19, 1999 |
(1) Although the BQ380 includes PC hardware, it does not use information from PC BIOS or real-time clock. Its functionning as a terminal cluster server is not affected by the roll-over to Year 2000.
(2) <<WinFrame 1.6 is no longer tested for Year 2000 compliance and therefore is not supported as Year 2000 compliant by Citrix Systems. An upgrade to WinFrame 1.7 is currently available for those customers who require a Year 2000 compliant system from Citrix. Please refer to your standard sales channel for information regarding this upgrade. Please refer to the Year 2000 Readiness Disclosure for WinFrame 1.7 for information regarding the Year 2000 status of the WinFrame 1.7 product.>> Information source : Citrix Systems, Inc.
(3) Year 2000 ready when running in conjunction with Windows NT version 3.51 or higher.
(4) <<WinFrame 1.7 is considered Year 2000 compliant when Service Pack 5b and the related hotfixes have been applied.>> Information source : Citrix Systems, Inc.
(5) Year 2000 ready when running in conjunction with Windows NT version 4.0 or higher.
Click here to see Terminals Cluster Servers Year 2000 readiness in details.
| Software Functionality | Version | Year 2000 ready | Change |
| Migration to AFFINITY 32 set 2 | 03.01.01 | Oct. 16, 1998 | |
| AFFINITY 2 | any | No | Oct. 16, 1998 |
Click here to see Affinity 2 Year 2000 readiness in details.
| Software Functionality | Version | Year 2000 ready | Change |
| Client/server | 03.01.01 | Oct. 16, 1998 | |
Desktop & Windows NT Gateways |
Oct. 16, 1998 | ||
| AFFINITY 32 / TNVIP for MAINWAY 2001/2005 | 03.01.01 | Oct. 16, 1998 | |
| AFFINITY 32 / WID | 03.01.01 | Oct. 16, 1998 | |
| AFFINITY VISUAL 32 | 03.00.08 | Oct. 16, 1998 |
(1) See Year 2000 ready version of related components.
Click here to see Affinity 32 Year 2000 readiness in details.
| Software Functionality | Version | Year 2000 ready | Change |
| Glink for Windows | R5.4 | Jun 3, 1999 | |
| GGATE system | R5.0 | Jun 3, 1999 | |
| G3270 | R5.0 | Jun 3, 1999 | |
| QSIM | R5.0 | Jun 3, 1999 | |
| GUFT | R5.0 | Jun 3, 1999 | |
| GSPOOL | R5.0 | Jun 3, 1999 | |
| GLAPI | R5.0 | Jun 3, 1999 | |
| GLINE | R5.0 | Jun 3, 1999 |
(1) Product origin : Gallagher & Robertson Inc. More detailed Year 2000 information is available on G&R website.
Click here to see Glink Year 2000 readiness in details.
| Software Functionality | Version | Year 2000 ready | Change |
| VIPlet | 2.0 | New |
Click here to see VIPlet Year 2000 readiness in details.
Bull is providing this information on behalf of 3Com, who take full responsibility for the Year 2000 readiness and support of their products. Bull makes no guarantees concerning the Year 2000 readiness of 3Com products.
Bull is providing this information on behalf of Motorola, who take full responsibility for the Year 2000 readiness and support of their products. Bull makes no guarantees concerning the Year 2000 readiness of Motorola products.
| Model | Hardware Subsystem | Software version | Year 2000-ready | Change |
| CpNet2510 | ACP10 | V1 | Oct. 16, 1998 | |
| CpNet2520 | ACP20 | any | No (4) | Feb 19, 1999 |
| CpNet2530 | ACP30 | any | No (4) | Feb 19, 1999 |
| CpNet2535 | ACP40 | any | No (4) | Feb 19, 1999 |
| CpNet2540 | ACP50 (286) | any | No (4) | Feb 19, 1999 |
| CpNet2550 | ACP50 (286/386) | any | No (4) | Feb 19, 1999 |
| CpNet2550/486 | ACP50/54 (486-T2) | V4 | Oct. 16, 1998 | |
| ACP70 | ACP70 | V4 | Oct. 16, 1998 |
(2) Year 2000 ready when running in conjunction with PCMCIA software version V4 which requires a 16MB memory size and an ELXII board for supporting PCMCIA media.
(3) Year 2000 ready when running in conjunction with software version V4 which requires a 16MB memory size.
(4) This product is partially Year 2000 ready, but the problems that we have identified occur only when the date is managed or when you are using network management utilities.
| Software Functionality | Version | Year 2000 ready | Change |
| VIEW25 | Any | No | Oct. 16, 1998 |
Click here to see CpNet 2500 Year 2000 readiness in details.
| Software Functionality | Version | Year 2000 ready | Change |
| LOAD/DUMP FOR DATANET 7500 | Oct. 16, 1998 | ||
| UFTF | V2.0 | No (1) | Oct. 16, 1998 |
| UFTF | V3 | Oct. 16, 1998 |
(1) Year 2000 readiness of UFTF requires migration to UFTF V3 which will be available by 4Q98. For more information, please contact your local Bull representative.
(2) Year 2000 ready when running in conjunction with an IBM Y2K ready environment.
Click here to see Miscellaneous Year 2000 readiness in details.
Without frames: [ Networking compliance overview | Quick Reference | MainWay 2000
/ 2600 | Datanet | GCOS 7 Communications | GCOS 8 Communications | Terminals | Terminal cluster
servers | Affinity | Glink | VIPlet | 3Com
products | Motorola products | CpNet2500 | Miscellaneous | Bull Year 2000 overview
]
With frames: [ Networking compliance overview
| Bull Year 2000 overview ]...and
use the navigation bars.
Notice
Bull is making every effort to provide accurate and explicit
information on the Year 2000 readiness of its products. The information on this page
reflects the current results of our compliance tests and may be updated as testing
continues. Please see the Bull Year 2000 Compliance Overview for
an explanation of the terms used and our commitments.
Year 2000 Information and Readiness Disclosure Statements
Information contained on Bull past and present
Year 2000 Internet Website pages regarding products and services offered by Bull are
"Year 2000 Readiness Disclosures" as defined by the Year 2000 Information and
Readiness Disclosure Act of 1998, (The United States of America's Public Law 105-271, 112
Stat. 2386) enacted on October 19, 1998. Bull Year 2000 Internet website pages have been
and will continue to be our primary mechanism for communicating year 2000 information.
Trademarks
Any trademarks referenced in this document are the property
of their respective owners.