Microsoft KB Archive/129201

= PC MMTA: OS/2 Version 1.3 Installation Issues =

Article ID: 129201

Article Last Modified on 10/30/2006

-

APPLIES TO


 * Microsoft Mail Multitasking Message Transfer Agent 3.2

-



This article was previously published under Q129201



SYMPTOMS
When you install the OS/2 version 1.3 system software (included with the Mail Multitasking version 3.2), and you encounter an error, the most likely cause is a system or hardware problem.

Below are three examples of the most common errors, along with their causes and solutions.
 * 1) SYS1733 error

This error message may be displayed during installation. A SYS1733 occurs because the country information file A:\COUNTRY.SYS is incorrect; the system has stopped.

This error explanation is likely misleading as it rarely explains the cause.

See the Cause section below for likely reasons for this error.
 * 1) Fdisk Unsuccessful or Cannot Locate Fixed Disk Drive errors

One or both of these errors occur when the hard drive and/or adapter require a .BID file not included on the Installation disks A and B.
 * 1) Looping on reboot after installation

After you install OS/2 and reboot your system, the computer reboots in an infinite loop until you insert a bootable floppy.



CAUSE

 * 1) SYS1733 error

The error stems from a hardware configuration problem. Known causes are:


 * 1) * Misconfigured CMOS for the floppy disk drives.
 * 2) * Missing one of two floppy disk drives, but CMOS states both exist.
 * 3) * Incorrect SCSI configurations.
 * 4) Fdisk Unsuccessful or Cannot Locate Fixed Disk

The installation requires a special .BID file not included with the OS/2 installation disks A and B. A BID file is a Layered Device Driver Architecture (LADDR) driver for hard drives and adapters. Some PC computer hardware manufacturers require a proprietary .BID file.
 * 1) Looping on reboot after installation

The most likely cause is selecting the wrong mouse driver during the installation process.



RESOLUTION
 SYS1733 error

To see if your CMOS is configured incorrectly, check your computer's BIOS setup parameters and verify they match the drives physically installed. To see if you have a misconfigured SCSI adapter card check the card's settings against the documented settings in the adapter's installation manual. Fdisk Unsuccessful or Cannot Locate Fixed Disk errors

To resolve the error and complete installation, try the following steps:

 If you used Installation Disk A to boot the PC, try Installation Disk B and vice versa. This will insure that all .BID files have been tried and tested. Contact the disk adapter manufacturer and request a .BID file for the adapter model. Once the .BID file is obtained you must:

 Make a copy of your Installation disk A Delete all the .BID files on the disk A copy</li> Copy the new .BID file to the disk A copy</li> Rename the new file to BOOTBID.BID.</li></ol> </li> Reboot the computer with the newly modified Installation disk and proceed with installing OS/2.</li></ul> </li> Looping on reboot after installation

Reboot OS/2 using the Installation disk and select the appropriate mouse driver for your configuration. If the problem persists, edit the CONFIG.SYS and remark out the suspect mouse driver as shown:

rem DEVICE=C:\OS2\MOUSE.SYS TYPE MSSER$

Reboot the OS/2 computer.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
The information in this article only pertains to Microsoft's OS/2 version 1.3, included with the Microsoft Mail Multitasking MTA version 3.2.

Additional query words: 3.20

Keywords: KB129201

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.