Verisign Expiration Information: Important Notice to Webmasters, Internet Administrators, and Users (updated December 22, 1999)
Netscape Communicator 4.05 or earlier include root certificate authority (CA) certificates set to expire on December 31, 1999. Users of these browsers will see an additional dialog box when connecting to secure sites after January 1, 2000. The root CA certificate expiration does not affect SSL encryption. A user may safely click on Continue and proceed with secure transactions.
To eliminate the additional dialog box, the user must upgrade their browser or update expiring Verisign certificates. IBM recommends that all users upgrade their browser to Netscape Communicator 4.61 for OS/2 Warp from Software Choice.
Since many customers are unable to upgrade their browsers at this time, the following summarizes the choice of solutions for each version:
Choice # 1: Upgrade Your Browser Please go to Software Choice to select and download Netscape Communicator 4.61 for OS/2 Warp.
Choice #2: Update all expiring Verisign certificates that shipped with your browser Netscape Navigator 2.02 for OS/2 users may update all expiring Verisign certificates. This solution provides a replacement for your current certificate database file. Please be aware that any certificates you have added since you installed the browser will be removed with this procedure. You will have to accept those certificates again when you go to the originating Web site.
Get the new CERT.DB (hold left SHIFT Key and Left Mouse Button to Download) for Netscape Navigator 2.02 and place in a temporary directory. Shut down the browser and back up (rename) the file CERT.DB found in your Netscape 2.02 directory. Place the new CERT.DB in your Netscape 2.02 directory.
Note: If you re-install your browser, you will need to replace the CERT.DB file again. If your certificates file becomes corrupt, your browser will rebuild the original certificates file and you will need to replace the CERT.DB file again.
Choice # 3: Ignore the Additional Dialog Box Remember your other choice is to inform users about the dialog box and to make sure they know that they can click continue to ignore the warning and continue with full SSL encryption for their transaction.
Choice # 1: Upgrade Your Browser Please go to Software Choice to select and download Netscape Communicator 4.61 for OS/2 Warp.
Choice # 2: Update all expiring Verisign certificates or the Verisign/RSA Secure Server Certificate
Netscape Communicator 4.04 for OS/2 Warp users and administrators have two options and may replace all the expiring Verisign certificates included in your browser today or may replace just the Verisign/RSA Secure Server Certificate.
Option A: Update all expiring Verisign certificates that shipped with your browser
IBM is providing this interim workaround until you are able to upgrade your browser to Netscape Communicator 4.61 for OS/2 Warp. This interim solution provides a replacement for your current certificate database file.
Note: Have you added your own certificates since you began using the browser? If no, go to 2.
Get the new CERT7.DB (hold left SHIFT Key and Left Mouse Button to Download) for Netscape Communicator 4.04 and place in a temporary directory.
Shut down the browser and back up (rename) the file CERT7.DB found in your current profile directory in Users in Netscape 4.04 directory. For example, this might be d:/netscape/users/myprofile. Place the new CERT7.DB in your current profile directory. Restart Netscape Communicator 4.04.
Note: If you previously exported your own certificates in Step 1, the last thing to do is:
Option B: Update only your Verisign/RSA Secure Server Certificate used by many banking institutions Shut down the browser
Now you are ready to add the updated Verisign/RSA Secure Server CA , please go to the Verisign site to obtain step-by-step instructions specific to Netscape Communicator 4.X.
Choice # 3: Ignore the Additional Dialog Box
Remember your other choice is to inform users about the dialog box and to make sure they know that they can click continue to ignore the warning and continue with full SSL encryption for their transaction.
For more information from Verisign please go to:
Verisign Alert for Webmasters
FAQs on Root CA Certificate Rollover
More Information on Root CA Certificate Rollover
Also, see Netscape's Message for Users of Older Browsers
We have discovered a problem on the second time you use FixTool 1.38 or later on a Warp Server SMP system. For instance, if you are installing a Fix Pack on a Warp Server SMP system and Multimedia is not selectable as a Serviceable Product, you have the problem. The solution is to download a corrected SYSLEVEL.MPM. This fix is for US ONLY. NLV versions are corrected by using the SYSZMPM.CMD file. To get the corrected SYSLEVEL.MPM file, click on "Up to higher level directory" in Fix Pack 42 directory in service.boulder.ibm.com. Go to directory "syslevel/wrpsvsmp" or use this link to get the corrected SYSLEVEL.MPM (you may have to hold the SHIFT key when clicking on the link to get the file). Copy this file to the "MMOS2\INSTALL" directory where Multimedia is installed. Install the Fix Pack or Select Multimedia only if installing a Fix Pack that has already been installed.
Updated on June 28th, 2001, version 3.03 released.
A new version of Theseus has been released. This new version is known as Theseus3. To get this new version, select Theseus3 to get the executable, and readme for instructions.
This new version works on Warp 3, Fix Pack 38 or later, Warp 4 at any Fix Pack level, including WSOD, and the e-Business Server.
Please use the Fix Pack Repository to access these Fix packs.
Warp 3 Fix Pack will only install on Warp Server, if you need this Fix Pack for either Warp 3 Base or Warp 3 Connect (any version), please contact IBM Service.
We have released an update for Netscape 4.04 for OS/2. This update is not a complete refresh of the product. We have built this update as a Fix Pack. There are 3 versions of the Fix Pack:
XR_1404I.ZIP - 40 bit International (applies to any 40 bit SBCS or DBCS version)
XR_1404N.zip - 40 bit French (applies only to the 40 bit French version)
XR_1404S.zip - 128 bit US and Canadian French North America (128-bit version)
These Fix Packs will only apply to the 2/99 version of Netscape 4.04 for OS/2 (commonly referred to as version 000006). To see if you have this verion, on your version of Netscape, pulldown the HELP and then ABOUT COMMUNICATOR. On the BLUE frame bar you should see "Version 4.04 [en] - 990212". If you do not see this, you need to upgrade to this version first. Select this link to get the Feb. '99 4.04 version.
The 40 bit versions are available without restriction. The 128 bit version is being released in a new area that handles Fix Packs that contain high encryption according to government rules.
In an effort to reduce the size of Fix Pack downloads, IBM separated out Device Drivers from OS/2 base product Fix Packs. The intention was to create a Base Device Driver Fix Pack that could be applied to both OS/2 Warp 3 and Warp 4 products. This eliminated th e need to ship the same files on both product Fix Packs, thereby reducing the size of those Fix Packs. The first of the Base Device Driver Fix Packs is numbered XR_D001.
After we released FP 11 and F 41, it was determined that in some instance, that some systems might not be made Year 2000 Ready after the application of only FP 11 or FP 41. We have since re-releasded the FP's to include the clock driver that was missing and in some instances would have stopped a system from being Year 2000 Ready if the Base Device Driver FP was not also installed.
If your system was already Year 2000 Ready due to the application of a prior Fix Pack that made your system Year 2000 ready, you do not have to worry or do anything further. You are still Year 2000 Ready.
If your system was at GA level, or a Fix Pack level that did not make your system Year 2000 Ready, and you have applied the original Fix Pack 11 or 41 already (if the README.1ST in the Fix Pack doesn't state Release 2 or greater, then you have the original release) you have a few choices on ways to make your system Year 2000 Ready.
In all future OS/2 Base Product Fix Packs, IBM will include any Device drivers that have Year 2000 fixes in them, as well as including those drivers in the Base Device Driver Fix Packs.
As of April 6, 1999, fee based defect support for the following products is no longer available.
On February 26, 1999 IBM OS/2 Fix Distribution released Fix Pack 10.
Diskette images can be found at ftp://service.boulder.ibm.com/ps/products/os2/fixes/v4warp/
Select the language you are interested in then the Fix Pack 10 (XR?M010) entry. If there is none then Fix Pack 10 is not available for that language.
Software Updates enabled versions (RSU) can be found
here
On Dec. 4, 1998 IBM OS/2 Fix Distribution released Fix Pack 39.
Diskette images can be found at ftp://service.boulder.ibm.com/ps/products/os2/fixes/v3.0warp/
Select the language you are interested in then the Fix Pack 39 (XR?W039) entry. If there is none then Fix Pack 39 is not available for that language.
Software Updates enabled versions (RSU) can be found here
On February 10, 1999 IBM OS/2 Fix Distribution released Fix Pack 40.
Diskette images can be found at ftp://service.boulder.ibm.com/ps/products/os2/fixes/v3.0warp.
Select the language you are interested in then the Fix Pack 40 (XR?W040) entry. If there is none then Fix Pack 40 is not available for that language.
Software Updates enabled versions (RSU) can be found
here
The readme.txt for IP08528 has been updated with important new information regarding how to backout the
Fix Pack, and also documents a potential problem with one version of the converged Adaptec driver. In addition,
2 files required to backout the Fix Pack have been added to the ftp sites. If you have previously downloaded IP08528,
please return to the site where you downloaded it from to read the new readme.txt, and access the new backout files.
IBM has removed Lan Server Fix Pack IP08525 from distribution. This Fix Pack
was released and then later found to not include the following 4 APAR
solutions which the readme said were included:
This Fix Pack was functionally correct, but did not contain an important HPFS386 data corruption fix (IC21503) that was initially distributed in IP08508 and was still present in IP08525. In order to not further distribute this HPFS386 data corruption problem, IBM has replaced this Fix Pack with IP08528, which contains the correct solution for the corruption problem, as well as the other missing solutions.
We apologize for any inconvenience that this may have caused.
On Nov. 5, 1998 IBM OS/2 Fix Distribution released Fix Pack 9. It was subsequently withdrawn on Nov 6 due to a Workplace Shell hang in PMWP.DLL.
On Nov. 11, 1998 IBM OS/2 Fix Distribution re-released Fix Pack 9. This is covered in the README.1ST on the first Fix Pack disk.
Diskette images can be found at ftp://service.boulder.ibm.com/ps/products/os2/fixes/v4warp.
Select the language you are interested in then the Fix Pack 9 (XR?M008) entry. If there is none then Fix Pack 9 is not available for that language.
Software Updates enabled versions (RSU) can be found here
CLOCK01.SYS in Warp 3 Fix Packs 37 and 38 and Warp 4 Fix Packs 7 and 9, can cause strange clock behavior, like the System clock on some systems jumping from the 29th of one month to the 1st of the next month. Systems currently known to experience this problem are:
To see if your system has this problem after applying one of the Fix Packs
mentioned above, do the following:
1. Shutdown all applications
2. Start the System Clock program from the System Setup folder
3. Click mouse button 2 on the clock face, select properties.
4. Click on the View tab
5. Select "Both date and time" under Information
6. Select "Digital" under Mode.
7. Click on the "Date/Time" tab
8. Set system time to 11:59:30
9. Set system date to 29
10. Close the Properties window
Watch the date as the time crosses midnight. If it jumps to the 1st of the month then you have the problem, follow the instructions below. If not, you do not have the problem and do not need to apply the fix below.
In either case, reset the clock to the correct date and time after the test.
To resolve this problem, replace CLOCK01.SYS in the OS2\BOOT directory of your boot drive with the CLOCK01.SYS you get from the PJ25912.ZIP file via this link.
Instructions:
1. Download PJ25912.ZIP in binary
2. Unzip PJ25912.ZIP (Use UNZIP or PKUNZIP). Contains the following.
APAR's have been opened for these problems, Warp 3, PJ25912, and
Warp 4, JR12447. The fix will go into Warp 3 Fix Pack 41 and Warp 4 Fix Pack 11.
As part of our ongoing commitment to communication with our customers, we are providing an outlook of upcoming features that will be available in our Fix Packs, in addition to the regular collection of fixes. IBM intends to deliver the following features in our Fix Pack 38 for OS/2 Warp:
Partitioned Removable Media Support (for DBCS languages only -- this support was delivered for SBCS languages in Fix Pack 35). With the popularity of the new SCSI Syquest Syjet 1.5 GB portable and Iomega jaz 1 GB and 2GB personal hard drives, OS/2 Warp extends the support of these removable hard drives with caching HPFS and FAT file systems
SES Enablement for SMP. Security Enablement Services for SMP.
Enhanced Debugger Support. This debugging interface is essentially an extension to the DosDebug() support within OS/2 that allows "Debugger" applications to control another process.
All statements regarding IBM's future direction and intent are subject
to change or withdrawal without notice, and represent goals and objectives
only.
Instructions for accessing the >8.4 GB IDE Hardfile Support update:
From the web browser of your choice
- Link to http://service.software.ibm.com/os2ddpak/index.htm (below)
- Click on "Yes, I agree. Show the Device Category List..."
- Click on "OS/2 Component Updates"
- Click on "Installation Diskette Updates"
- Click on ">8.4GB IDE Hardfile Support"
- Download the IDEDASD.EXE file and run it. Then follow the instructions
in the README.TXT to install.
Link to http://service.software.ibm.com/os2ddpak/index.htm now
On Sept. 6, 1998 IBM OS/2 Fix Distribution released Fix Pack 8.
Diskette images can be found at ftp://service.boulder.ibm.com/ps/products/os2/fixes/v4warp.
Select the language you are interested in then the Fix Pack 8 (XR?M008) entry. If there is none then Fix Pack 8 is not available for that language.
Software Updates enabled versions (RSU) can be found at here
On Aug. 29, 1998 IBM OS/2 Fix Distribution released Fix Pack 37.
Diskette images can be found at ftp://service.boulder.ibm.com/ps/products/os2/fixes/v3.0warp.
Select the language you are interested in then the Fix Pack 37 (XR?W037) entry. If there is none then Fix Pack 37 is not available for that language.
Software Updates enabled versions (RSU) can be found here
On June 26, 1998 IBM OS/2 Fix Distribution released Fix Pack 7.
Diskette images can be found at ftp://service.boulder.ibm.com/ps/products/os2/fixes/v4warp.
Select the language you are interested in then the Fix Pack 7 (XR?M007) entry. If there is none then Fix Pack 7 is not available for that language.
Software Updates enabled versions (RSU) can be found here
On May 29, 1998 IBM OS/2 Fix Distribution released Fix Pack 36.
Diskette images can be found at ftp://service.boulder.ibm.com/ps/products/os2/fixes/v3.0warp.
Select the language you are interested in then the Fix Pack 36 (XR?W036) entry. If there is none then Fix Pack 36 is not available for that language.
Software Updates enabled versions (RSU) can be found here
1998/05/05
Some system with non-Intel CPUs are experiencing TRAP 0006 or Hangs at boot after installing Warp 3 Fix Pack 35. APAR PJ25494 was opened for this problem. Look at PJ25494.TXT for more information and installation instructions.
1998/07/24
OS/2 and LAN Server products were declared to be Year 2000 Ready starting with the Fix Packs listed on this WEB site.
OS/2 and LAN Server Fix Packs are usually "cumulative" in nature, so future Fix Packs will continue to be Year 2000 Ready. Whenever we find additional Year 2000 problems, we will add them to the next available Fix Pack and to the following list. In the list, in the 'File location' column, is a link to a location where you can download the Year 2000 fix and apply it to a Year 2000 Ready system if you do not want to install a complete Fix Pack and only update the Year 2000 Readiness of the system. You do not need to use the latest Fix Pack to still be Year 2000 Ready if you apply the file fixes listed in the table below.
| Defect/APAR | Fix Pack included in | File location | Description of Problem |
|---|---|---|---|
| -- May 6, 1999 -- | |||
| New BACKUP fix for Year 2000, APAR=JR12925 | Applies to Warp 3 prior to FP41 and Warp 4 prior to FP11 | JR12925.ZIP |
Specifying a year of 00 with the /D Date option of BACKUP is rejected as an invalid date. The /D option of BACKUP takes a date as an argument. This date can have either two or four digit years, for example, Ffbruary 22, 2000 can be specified as:
In the first case, the date is incorrectly rejected as invalid.
For example,
There is a work around if you do not wish to apply the fix. That is to only use four digits for the year. To apply the fix, please D/L JR12925.ZIP, unzip and follow the directions in JR12925.TXT. |
| -- December 17, 1998 -- | |||
| New WINOS2 fix for Year 2000, APAR=JR12296, PJ25967 | Applies to Warp 3 prior to FP39 and Warp 4 prior to FP10 | Click here to start, then select the language you want. If JR12296.ZIP is not there that means no Fix Pack containing this fix has been released for that language yet. You can use the US version in the "english-us" directory until one is released. | Symptom is the day changing from February 28 to March 1 in the year 2000 in the WINOS2 Control Panel Date/Time program. The code did not recognize that 2000 is a Leap Year. The fix file is MAIN.CPL. |
| -- July 22, 1998 -- | |||
| Java Year 2000 Statement | Java 1.1.7 Download | Software Choice Java 1.1.7 Download page |
Sun Microsystems, Inc. has announced that only Java 1.1.4 and
later versions are Year 2000 ready. IBM previously released the
following versions that are not Year 2000 ready:
|
| -- July 21, 1998 (updated Feb. 25, 1999) -- | |||
| Clock Files for Year 2000, Regression due to PJ25495 | Problem in both Warp 3 FP 37/38 and Warp 4 FP 7/8 and you should use Y2KCLOCK.EXE to restore the Clock drivers. | Y2KCLOCK.EXE from the DDPAK On-Line Web page for both Warp 3 and 4 | After the Fix Pack updated the CLOCK01.SYS and CLOCK02.SYS device drivers (April 29, 1998), included in FP 37/38 of Warp3 and FP 7/8 of Warp 4, to include a BIOS fix for PCs used for dual booting between OS/2 and DOS, additional problems with the handling of the month rollover information in the BIOS in certain SMP PCs were found. The CLOCK0x.SYS device drivers have been backleveled to the FP 36 Warp 3 and FP 6 Warp 4 level in Fix Packs after FP 38/8, and are available as CLOCK01.SYS and CLOCK02.SYS in the EXE file. The EXE file also includes a detailed description of the fixes. The clock regression is being worked as PJ25912 and will be put back into a Fix Pack when completed. The Y2KCLOCK.EXE file is being made available as a Year 2000 file because if you should not be at the FP 36 Warp 3 or FP 6 Warp 4 level and then restored the CLOCK drivers from your backup, you might lose a Year 2000 Fix, therefore this file should be used. |
| -- April 29, 1998 -- | |||
| APAR PJ25309 (Warp 3) / JR11383 (Warp 4) | FP 35 (Warp 3) / FP 6 (Warp 4) | Included with the above fix from the DDPAK On-Line Web page for both Warp 3 and 4 | Dual booting from OS2 to DOS after year 2000 results in time in BIOS DATA AREA to be reset to 1-4-1980. The fix files are CLOCK01.SYS and CLOCK02.SYS. This is a software fix for a hardware problem. | -- March 24,1998, updated March 2, 1999 -- |
| APAR JR11077, Warp 4 Only | FP 7 US, FP 6 NLV | Click here to start, then select the language you want. If JR11077.ZIP is not there that means no Fix Pack later than Fix Pack 5 has been released for that language yet. You can use the US version in the "english-us" directory until one is released. | WINOS2 File Manager shows date as 1/1/:0, due to a missing module from Warp 4 Fix Pack 05. The fix for this APAR should have added a new module, WINFILE.EXE, to the Fix Pack. It is being provided as a separately downloadable file. |
1998/04/29
Some faster Intel systems (166mhz or faster) hang when you try to install OS/2 2.11 or OS/2 Warp 3. IBM has released a set of updated OS/2 Loader files (OS2LDR) to correct this problem. Click here to access these fixes. Look at the README.TXT file for download instructions.
1998/04/16 - 1998/04/23
IBM has discovered a problem with the IPSRAID.ADD device driver that is contained in previously released versions of FP35. This driver will cause machines containing the ServeRAID II disk subsystem to fail to boot after installation of the Fix Pack. We are releasing an updated version of FP35 with a new version of this file. Users of FP35 that do not have this hardware configuration are unaffected and should not have to install the new version. Users of ServeRaid II should only install this new version of FP35. Here is how you can tell which version you have:
(Released in US, UK, German, Spanish, Portuguese, Norwegian, Dutch, Italian, French and Danish)
Diskette images dated prior to 04-15-98
README.1ST dated prior to 04-15-98
IPSRAID.ADD dated 12-05-98, 18714 bytes (listed in README.1ST or in \OS2\BOOT directory)
Diskette images dated on or after 04-15-98
README.1ST dated on or after 04-15-98
IPSRAID.ADD dated 03-10-98, 19922 bytes (listed in README.1ST or in \OS2\BOOT directory)
If you have already installed the initial version of FP35, you may install the new FP35 and the driver will be replaced, or you can access the driver at http://www.pc.ibm.com/us/searchfiles.html where you will need to enter the search string of: ServeRAID II device driver. This will bring up the US and Japanese version of this driver to choose from as well as the associated text file. Use the US version for all Single Byte versions of FP35.
We have removed all previously released FP35 Fix Packs from our internal and external sites and replaced them with the new version.
Following Fix Pack 35's have been re-released. Find the language you require in the table the links below point to then click on Fix Pack 35 for the RSU enabled version or click on AlsoAvailable for the diskette images.
English-US 1998/04/20
Danish 1998/04/21
German 1998/04/21
English-UK 1998/04/21
Portuguese 1998/04/21
Spanish 1998/04/21
French 1998/04/22
Italian 1998/04/22
Dutch-Netherlands 1998/04/23
Norwegian 1998/04/23
A problem has been found when using Development Technologies Deskman/2 product with FP35 or FP6 installed.
The problem was found after FP35 and FP6 were released. It is a SYS3175 in DOSCALL1.DLL that occurs when you run the DM2IMAGE program.
The fix is a replacement DOSCALL1.DLL. The Warp 3 fix contains a UNI and SMP fix.
Read DOSCALL1.TXT for installation instructions.
The APARs for this problem are:
These fixes will be picked up in US FP36 and US FP7.
The current OS/2 Display Drivers are Year 2000 ready.
If one of the current Display Drivers is installed on a machine and the installation fails, a log file is created. If the installation is on a machine with a date past 12/31/99, the install log entry will be reported in the following format: mm-dd-10x. In this case, 10x represents 200x. As we release Display Driver updates, the install log entries will indicate dates in the normal mm-dd-yy format even if installed after 12/31/99.
This CSF build can be used with all OS/2 Warp 3, Warp 4, and WSeB Fix Packs. It replaces (supersedes) all previous CSF release up to and including F.143.
Click here for:
For NLS versions, find the language you need then download the CS?nnnc.EXE file you need here. If there is none, use the US version from the english-us directory.
Older CSF versions are available. They are here in case they are needed for
specific Fix Packs. Fix Packs were shipped and tested with the FixTool available
at the time the Fix Pack was created, and may call specifically for that level of
FixTool. You may use that version if you wish.
This CSF build can be used with all OS/2 Warp 3, Warp 4, and WSeB Fix Packs. It replaces (supersedes) all previous CSF release up to and including F.142.
Click here for:
This CSF build can be used with all OS/2 Warp 3, Warp 4, and WSeB Fix Packs. It replaces (supersedes) all previous CSF release up to and including F.141.
Click here for:
This CSF build can be used with all OS/2 Warp 3 and Warp 4 Fix Packs, and contains fixes for some of the problems found with previous versions.
Click here for US:
This CSF build can be used with all OS/2 Warp 3 and Warp 4 Fix Packs, and contains fixes for some of the problems found with previous versions.
Click here for US:
This CSF build can be used with all OS/2 Warp 3 and Warp 4 Fix Packs, and contains fixes for some of the problems found with previous versions.
Click here for US:
This CSF build is currently meant to be used only with Warp 4 Fix Pack 7. It is a significant change from the previous releases up to and including the F.137B build.
Click here for US:
This CSF build can be used for all Fix Packs up to Warp 4 Fix Pack 7.
Click here for US:
On December 2, 1997 IBM OS/2 Fix Distribution released Fix Pack 5.
Diskette images can be found at ftp://service.boulder.ibm.com/ps/products/os2/fixes/v4warp.
Select the language you are interested in then the Fix Pack 5 (XR?M004) entry. If there is none then Fix Pack 5 is not available for that language.
Software Updates enabled versions (RSU) can be found here.
If you use Java or any of the other products available via IBM Software Choice you should update to this latest version of Feature Installer! It has been updated to better manage feature dependencies on service levels of system modules during installation and removal of various features.
Also, better support for upgrading to the latest level of Java has been added.
We recommend you upgrade to this latest level!
A problem with MOUSE.SYS has been found after Fix Pack 5 is installed on some systems. Mouse movement becomes slow, feels sluggish.
To recover, restore the MOUSE.SYS from the Fix Pack archive directory.
This problem will be fixed in all NLV Fix Pack 5 and US Fix Pack 6 releases.
Note: The fix DID NOT make it into Fix Pack 6. It has been deferred to Fix Pack 7.
Dump Formatter and symbols file for various OS/2 Fix Packs can be obtained from:
ftp://service.boulder.ibm.com/ps/products/os2/fixes/debug/
Files begining with the last 4 characters of the Fix Pack name are the ones you need to download. For example, all files starting with w034*.* are for Warp 3 Fix Pack XR_W034, m004*.* for Warp 4 Fix Pack XR_M004, ETC.
Through Warp 3 Fix Pack XR_W028, the files are:
Starting with Warp 3 Fix Pack XR_W029, the files are:
Starting with Warp 3 Fix Pack XR_W035, the files are:
SMP means you are running Warp Server SMP
UNI means you are running any of the other Warp 3.x family
Through Warp 4 Fix Pack XR_M005, the files are:
Starting with Warp 4 Fix Pack XR_M006, the files are:
Both the IBM Technical Connection and the IBM Developer Connection are no longer available.
You can find Fix Packs on CD-ROM at The OS/2 SUPERSITE
On October 13, 1997 IBM OS/2 Fix Distribution released Fix Pack 4.
Diskette images can be found at ftp://service.boulder.ibm.com/ps/products/os2/fixes/v4warp.
Select the language you are interested in then the Fix Pack 4 (XR?M004) entry. If there is none then Fix Pack 4 is not available for that language.
Software Updates enabled versions (RSU) can be found here.
On October 1, 1997 IBM OS/2 Fix Distribution released Fix Pack 32.
Diskette images can be found at ftp://service.boulder.ibm.com/ps/products/os2/fixes/v3.0warp.
Select the language you are interested in then the Fix Pack 32 (XR?W032) entry. If there is none then Fix Pack 32 is not available for that language.
Software Updates enabled versions (RSU) can be found here.
This replacement OS2KRNL for OS/2 Warp 4 Fix Pack XR_M003 fixes a problem that was causing some SYS2070 traps. It is also required for the new IBM Feature Install Version 1.2.
Additonally, if you are having problems running some applications after installing FP3 you should also try this replacement OS2KRNL to see if it will help.
See the FP3KRNL.TXT file for installation instructions (also included in the self-extracting FP3KRNL.EXE file).
Fix Packs for the Korean version of OS/2 Warp 3 and OS/2 Warp 4 are now available from the World Wide Web (WWW) at http://www.ibm.co.kr/ibm/product/sw_biz/down/os2.html
Instructions for accessing the >4.3 GB IDE Hardfile Support update:
From the web browser of your choice
- Link to http://service.software.ibm.com/os2ddpak/index.htm (below)
- Click on "Yes, I agree. Show the Device Category List..."
- Click on "OS/2 Component Updates"
- Click on "Installation Diskette Updates"
- Click on ">4.3GB IDE Hardfile Support"
- Read and follow instructions...
Link to http://service.software.ibm.com/os2ddpak/index.htm now
NCS is now making available the latest releases of OS/2 Family Fix Packs, both Public and Controlled on our External Web Site. Controlled Fix Packs will no longer be in restricted distribution and all customers will have open access to those Fix Packs.
All Fix Packs (Controlled and Public) are tested to the same rigorous levels before release.
Follow this link to the page where Download Services and Software Updates (Install from the Internet) are available.
If you get a "CSF0208 No products were found on the target system to service" message when you try to apply service (a Fix Pack) to your system, the cause may be an invalid SYSLEVEL.OS2 or SYSLEVEL.MPM file. look here for replacements.
Check here for OS/2 Warp 3 and OS/2 Warp 4 Fix Packs. "Software Updates" installable Fix Packs and diskette images for manual install are available.
IBM Internal users should look here for the same data.
Do not install LAN Server Fix Packs on DSS Server or DSS Client systems. If you install LAN Server Fix Packs on your DSS Severs and/or Clients, you will severely damage your system by back leveling executables and DLLs. DSS Servers and Clients may not func tion properly after the application of a LAN Fix Pack.
NOTE: This information is ONLY for internal IBM personnel who are accessing either of these servers (external customers are NOT affected):
The Boulder location has changed its Internet firewall to comply with new Corporate Internet Security requirements. As a result the procedures to access the above servers has changed. These servers are now only accessible from the Internet and no longer from the IBM Internal MPN network. You will be able to access the servers using one of the IBM socks gateways such as socks1.server.ibm.com. Full instructions can be found at "Access instructions for Boulder Internet servers." [ IBM home page | Order | Search | Feedback | Help | (C) | (TM) ]