Technical Document # - 8262710
Family: Operating Systems
Product: OS/2 (All Releases)
Release: 3.0, 4.0

Last Updated: 01/19/1998


OS/2 FDISK and Installation


FDISK Partition Setup Errors


OS/2 Install FDISK Notes

If you are having a problem with OS/2 installation related to hard drive
configuration and partition size do the following:

1. Set the prompt to display return codes from executables. From
   an OS/2 command prompt, type SET PROMPT=[$R $P]; then press Enter.

2. From the command prompt, query FDISK information as follows:


3. If any ***BIOS xxx statements are displayed from the FDISK
  query, you may have problems. This indicates that the
  system hardware BIOS can only see a limited amount of the hard
  drive space available. The number after the ***BIOS indicates how
  many megabytes of drive space the BIOS can see. Any partition
  that is not inside of this range will not be seen by the BIOS.
  There is nothing that OS/2 can do about this; it is a hardware
  BIOS problem.

4. The command prompt return code ($R) from the FDISK /QUERY command
  should be 0; if not, make note of what it is.

5. Perform an install FDISK query with the following statement:


Note: OS/2 Warp 4 uses /SIZE:100 instead of /SIZE:35.

   The command prompt return code ($R) should be 24; if not, make a
   note of what it is.

How to Use FDISK Command Line Parameters

* Some FDISK parameters are only used for restrictors; this means that they
  have no function if you are trying to create a partition. These parameters are:


  - Used to select a partition with a specific file system type like FAT.

/VOLID  [This option is not valid use /NAME instead]

  - Used to select a partition with a particular volume ID number.  This
    is like the
/NAME parameter, but is used when no name has been assigned
    to a particular partition. This is a new function for OS/2 Warp 4.


  - Used to select a partition with a specific name.


  - Used to select a partition that is bootable.

* Other parameters are:


   - Used to get current partition setup information for a system.


   - Used to create a new partition. This can add the partition to the
     Boot Manager menu if you specify a
:name with it, for example, /CREATE:OS2V4.
     This creates a partition and adds the new partition to the
  Boot Manager menu as OS2V4.


   - Used to delete a specific partition defined with restrictors or all
     partitions on a specific drive if used as


   - Used to select a specific hard disk for an operation.


   - Used to add a partition to the
Boot Manager menu or remove a partition
     from the
Boot Manager menu.


   - Used to define the C: partition if a hard drive has more than one
     primary partition.


   - Used to set a partition as startable. This operation is only valid
     on primary partitions.


   - Used with
/CREATE parameter to define whether the new partition should be
     at the start (top) of the drive or end (bottom) of the drive. OS/2 Warp
     4 allows for a
MB variable to define the starting location.

   - Used to define the size of a new partition with the
/CREATE parameter,
     or used as a restrictor to select a specific partition.


   - Used to define a partition as primary or logical with the
     parameter or used as a restrictor to select a specific partition.


   - Used with the
/CREATE parameter to create a Boot Manager partition.


   - Used to create special system partitions, such as IML/FE type, with the
    /CREATE parameter or as a restrictor to define a specific partition.


   - Used to rewrite the Master Boot Record information.


   - Used to pass FDISK a response file with a set of FDISK operations
     to perform.


   - Used to display information about FDISK parameters.

FDISK Command Line Examples


 - Create a
Boot Manager partition the using first available free space
   at the start of the drive.


 - Create a primary partition at the top of first drive and add this
   partition to the
Boot Manager as OS2V40.


 - Create a logical partition on disk 1 using all free disk space.


 - Delete all partitions on second disk. Note that this will not delete
   any system (IML/FE) type partitions.


 - Delete the logical FAT partition on first disk.


 - Delete the partition on disk 2 that is 400 MB size.


 - Delete a bootable logical partition.


 - Delete partition on disk 1 (01) with volume name 00101800.


 - Delete partition with the
Boot Manager name WARP.

FDISK Response File Example


Note: There is a restriction on the size of an FDISK command; if the command
      is too long, the last parameter or so will not be used.

How to Use SETBOOT

SETBOOT is used to reboot the system for CID (Configuration, Installation, and Distribution) procedures and control some of the Boot Manager functions. The following parameters are available:


- Requires the
Boot Manager to be present; reboots the system,
  and displays the Boot Manager menu.


- Reboots the system, configures
Boot Manager to not display
  a menu and start up on drive d.


- Reboots the system, configures
Boot Manager to not display
   a menu and startup on drive with name. For a partition name
   containing space characters, enclose the name in quotation marks.

To setup the Boot Manager to always boot a specific partition and not
display a menu use the following two commands:


- n is a number from 1 to 3;
name is the name of a partition as it
  is listed in the
Boot Manager menu.


- Sets the auto boot partition to
n, which can be a number from 0 to 3.
  0 resets the
Boot Manager menu to display.


- Query information from
Boot Manager partition


- Set the timeout delay for the display of the
Boot Manager menu. A
  value of 0 causes the menu not to display.
/T:NO sets
Boot Manager menu to timeout value.

IDE Hard Drive BIOS Setup

It is the responsibility of the PC system hardware BIOS to provide access to the hard drive so that software programs can use the hard drive. This is done using an industry standard BIOS call into the system interrupt 13 (INT13). This industry standard only allows 10 bits to define a cylinder to select for an operation. This limits the BIOS INT13 to using 1024 cylinders or less.  In the past, the BIOS INT13 code mapped INT13 cylinder requests directly to physical cylinders on the IDE hard drive. Because new IDE type hard drives commonly have more than 1024 cylinders, the industry was confronted with a problem. To get around this problem the industry has developed a
new standard for INT13 BIOS with the use of a LBA (Logical Block Addressing) mode for IDE type hard drives. The new LBA mode BIOS INT13 code takes the drive head count and increases it logically, while decreasing the cylinder count. Normal conversions double the head count and cut the cylinder count in half. They also quadruple the head count and cut the cylinder count to
one fourth. Some new versions of BIOS allow for eight times the head count and cut the cylinder count to one eighth.

When you configure a new hard drive for a system, it is recommended that you make sure that the INT13 BIOS can map all hard drive cylinders into the 1024 range.

Document Info

Related Docs:  

IBM disclaims all warranties, whether express or implied, including without limitation, warranties of fitness and merchantability with respect to the information in this document. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright (c) 1994, 1996 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.