Author Topic: OS2 warp 4 hard drive size problems  (Read 13626 times)

millese

  • Newbie
  • *
  • Posts: 26
    • View Profile
Re: OS2 warp 4 hard drive size problems
« Reply #15 on: 2008.10.25, 00:03:55 »
That is fantastic! I have to run down a spare HD to attemp this, but I will get back with you on my sucess/failure! I'm glad that this exercise was useful for you as well. I know I've been blasting with questions, but here was another glitch that happened to me that I was hoping you could shed some light on. When I put a second drive on as a slave the boot mananger changed all of my drive designations which really P$%## off my config.sys as nearly every line referenced the D: drive. I went through and changed every instance of D: to E: and the system then booted, but it said it could not find my desktop in os2.ini. When I found os2.ini in the os2/install directory and tried to open it with E:e os2.ini it said the editor found embedded null characters in the file. I elected to open it anyway and can see more references to the D: drive, but there is a bunch of gobblie gook as well. Is there some way I can view this file in a normal fashion so I can change the references to E: as well. P.S. i made backup copies of all the original files so i can go back, and even when the desktop couldn't be stared in gave me a command window. It just raised another question for me.  If this is getting tiresome please tell me. Thanks

RobertM

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2034
    • View Profile
    • A.I.BuiltPC - using OS/2 Warp Server & eComStation for Custom Web and Database Solutions
Re: OS2 warp 4 hard drive size problems
« Reply #16 on: 2008.10.25, 00:08:38 »
One addition... if the machines are very old, and have problems either booting or finishing post with that configuration (re point #2) then install the CD ROM as slave on the 2nd IDE controller (instead of master).
|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


millese

  • Newbie
  • *
  • Posts: 26
    • View Profile
Re: OS2 warp 4 hard drive size problems
« Reply #17 on: 2008.10.25, 00:55:52 »
Ya, I agree I don't need it, was just curious more than anything. I can do anything I need from the os2, but I came across it and wondered if there was anyway I could deal with it just for learning more than anything.

ivan

  • Hero Member
  • *****
  • Posts: 593
    • View Profile
Re: OS2 warp 4 hard drive size problems
« Reply #18 on: 2008.10.25, 00:59:18 »
The OS2*.INI files are binary data files and should only be edited with something like INIedit by Goran (Hobbes is your friend).

You can use the SET DESKTOP=<d>\desktop in config.sys where <d> is the drive with the desktop dir.

Some information you may find interesting I have quoted below (edited to show only the relevant information)

Quote
  FIXED IDE HARD DRIVE AND REMOVABLE MEDIA SUPPORT

  June  12, 2003

  OS/2 Device Driver Development
  IBM Solution Technologies
  Austin, TX

  (c) Copyright International Business Machines Corporation, 2001, 2003.
  All rights Reserved.

  CONTENTS
  ________

  1.0  INTRODUCTION

  2.0  INSTALLATION
  2.1  Updating the Installation Diskettes
  2.2  Updating a Previously Installed Warp System

  3.0  LARGE HARD DRIVE CONSIDERATIONS
  3.1  System Hang or Hard Drive Hesitation
  3.2  Cannot Mark a Partition Installable
  3.3  IPE on Boot, "Trap D"
  3.4  Inconsistencies in Total Disk Space
  3.5  Application Install Fails with "Not Enough Space"
  3.6  Performance Problems With Two Devices on a Single Channel
  3.7  Install Diskettes or Utility Diskettes Hang on Boot (APAR JR12065)
  3.8  Additional Parameters For IDE Device Driver
  3.9  Additional Parameters for IBMATAPI.FLT and IBMIDECD.FLT drivers
  3.10 Very Large (128/137 Gb limit) Hard drive considerations (48 bit LBA)

  4.0  REMOVABLE MEDIA SUPPORT
  4.1  Partitioned Removable Media
    4.1.1  Using Protected Media
    4.1.2  Assignment of Drive Letters
    4.1.3  Configuring Partition Support (OS2DASD)
    4.1.4  Ejecting the media
    4.1.5  Limitations of Partitioned Removable Media Support
  4.2  Large Floppy Removable Media (LS-120)
    4.2.1  Limitations of LS-120 Support
  4.3 CD-ROM Device Manager (OS2CDROM.DMD)
  4.4 CD-RW media support in IBMIDECD.FLT

  5.0 SUPPORTED CHIPSETS, KNOWN RESTRICTIONS AND LIMITATIONS
  5.1 Supported chipset table
  5.2 Known restrictions and limitations
    5.2.1 Intel chipsets limitations
    5.2.2 VIA chipsets restrictions
    5.2.3 SiS chipset limitation
  5.3 Chipset Extended Detection Algorithm for Intel chipsets

  6.0  COPYRIGHT AND TRADEMARK INFORMATION

  1.0  INTRODUCTION
  _________________

  FixPak 35 (FP35) for Warp 3 and FixPak 6 (FP6) for Warp 4 extended support
  for fixed Enhanced IDE drives to sizes up to 8.4GB and added new caching HPFS
  and FAT file system support for removable media drives such as SCSI Syquest
  Syjet 1.5GB portable hard drive and the Iomega jaz 1GB and 2GB personal hard
  drives.

  This package contains updates to the support in FP35 and FP6,
  extending support to fixed Enhanced IDE drives greater than 8.4GB,
  fixing some problems, and adding additional documentation on
  removable media support.  Beginning with FP40 and FP10 OS/2 base
  device drivers were separated into a Base Device Driver FixPak.

  This package also contains extensions to OS2CDROM.DMD, providing support for
  multi-session CDROM media.

  The package also contains an updated floppy diskette driver (IBM1FLPY.ADD),
  which corrects a failure that occurs upon a Resume on a ThinkPad when
  the diskette drive is installed in the ThinkPad docking station.

  For Warp Server Advanced HPFS386 support of removable media, you additionally
  need LAN Server SelectPack IP_8508.

  These fixpaks are available from http://ps.software.ibm.com/ under the link
  "Downloads and News."  Install the fixpaks first, carefully following the
  instructions with the fixpaks; then follow the directions in this README to
  install this package.

  If you are attempting to install Warp 3 or Warp 4 for the first time on a
  fixed hard drive greater than 4.3GB, then:

  1.  Follow the instruction on "Updating the Installation Diskettes" in this
      README and use the new diskettes to install Warp.

  2.  Install FP35 for Warp 3 or FP6 for Warp 4.

  3.  Follow the instructions in this README to install this package.

  2.0  INSTALLATION
  _________________

  2.1  UPDATING THE INSTALLATION DISKETTES
  ________________________________________

  If you are attempting to install Warp on a hard drive greater than
  4.3GB, or your are attempting to install Warp Server for e-business on
  a hard drive greater than 30GB, then the Installation diskettes must
  be updated.

  1.  Make a backup copy of your Diskette 1 (D1).

  2.  Copy the new versions of IBM1S506.ADD, and IBMIDECD.FLT
      device driver files onto your D1 diskette.

  3.  If the installation diskettes are for Warp Server for e-business,
      Warp Server for e-business Convenience Pak, or Warp 4 Convenience Pak,
      copy the DASD32.DMD file to your D1 diskette and rename it to
      OS2DASD.DMD.  Otherwise copy the DASD16.DMD file to your D1
      diskette and rename it to OS2DASD.DMD.

  4.  Add the statement SET COPYFROMFLOPPY=1 to the CONFIG.SYS on D1.

  5.  Save the changes.

  6.  Start the installation with the Installation Diskette.

  7.  When you are prompted for Diskette 1, use the diskette you modified.

  8.  Proceed with the installation.

  9.  If during the installation process or when restarting your system, you
      lose connection to your hard disk or CDROM, make sure that the device
      driver statements are in the CONFIG.SYS file and the new versions of the
      IBM1S506.ADD, IBMIDECD.FLT and OS2DASD.DMD device drivers have been
      copied to the \OS2\BOOT directory.  Use the date of the files to distin-
      guish the newer versions.

  2.2  UPDATING A PREVIOUSLY INSTALLED WARP SYSTEM
  ________________________________________________

  1.  (Optional) Save the existing (old) level of drivers in your system.

      a.  Change Directory to the \os2\boot directory on your boot drive.

      b.  Rename the drivers (for example, where the boot drive is C:).  The
          IBMATAPI.FLT driver may not have been previously installed.

            [C:\os2\boot] rename IBM1S506.ADD  IBM1S506.ORG
            [C:\os2\boot] rename IBM1FLPY.ADD  IBM1FLPY.ORG
            [C:\os2\boot] rename IBMIDECD.FLT  IBMIDECD.ORG
            [C:\os2\boot] rename IBMATAPI.FLT  IBMATAPI.ORG
            [C:\os2\boot] rename OS2CDROM.DMD  OS2CDROM.ORG
            [C:\os2\boot] rename OS2DASD.DMD   OS2DASD.ORG

  2.  Open an OS/2 Window and enter the SYSLEVEL X: (where X: is your
      boot drive).  Look for the entry x:\OS2\INSTALL\SYSLEVEL.OS2 and
      see which version of OS/2 you have installed; for example "Version
      4.00" or "Version 4.50".

  3.  Device Driver Install

      o   (Warp 3, Warp Server) Open the Device Driver Install program
          in the OS/2 System Folder/System Setup Folder.

      o   (Warp 4, Warp Server for e-business) Open the Device Driver
          Install program in the OS/2 System/System Setup/Install-Remove
          Folder.

  3.  Point the Device Driver Install file dialogue to the directory where you
      have placed the new files in this package.

         If your version of OS/2 is 4.00 or earlier, select the driver
         named IBM IDE AND REMOVABLE MEDIA SUPPORT (V4.00).

         If your version of OS/2 is 4.50 or later, select the driver
         named IBM IDE AND REMOVABLE MEDIA SUPPORT (V4.50).

      Click on INSTALL.

  4.  Reboot the system.

  3.0  LARGE HARD DRIVE CONSIDERATIONS
  ____________________________________

    3.2  CANNOT MARK A PARTITION INSTALLABLE
  ________________________________________

  There is a BIOS restriction that installable (startable) or bootable parti-
  tions must be contained within the first 1024 logical cylinders of the disk.
  This is true for both EIDE and SCSI hard disk drives.  If FDISK fails to
  allow a partition to be marked installable, the partition is either above
  1024 cylinders or the partition spans the first 1024 logical cylinders of the
  disk.  Use FDISK to reduce the size of the startable or bootable partition by
  sufficient MBytes.  One way to calculate the correct partition size is to do
  the following:

  1.  Edit your CONFIG.SYS and add the parameter /W or /V to the
      BASEDEV=IBM1S506.ADD statement.

  2.  Save this change and reboot the system.

  3.  At initialization, record the far left hand column of numbers of the
      geometry information under the OS2:log heading; for example, where
      C=cylinder, H=head, and S=sector:

            OS2:log
       C       1027
       H         63
       S        128

  4.  Calculate the 1024 cylinder size in MBytes as ( H x S ) / 2.  (round
      down).

      All bootable partitions must be contained within this size.  In this
      example the bootable partition must be contained in the first 4032
      MBbytes of the disk and cannot exceed a single partition size of 4032
      MBytes within this area.  No bootable partition may extend beyond the
      first 4032 MBytes.

  5.  Use FDISK to resize the partitions and reboot.

  ---------------------------------------
  3.5  APPLICATION INSTALL FAILS WITH "NOT ENOUGH SPACE"
  ______________________________________________________

  FAT partitions under OS/2 are limited to a 2.1GB maximum size.  HPFS parti-
  tions are limited to a 64GB maximum size.  However there is the magic number,
  2,147,483,647 (2.1GB).  This 2.1GB value is the maximum number that will fit
  into a signed 32-bit integer.  Some application software installation pro-
  grams query OS/2 about the available remaining space on the partition and
  save the result into a signed 32-bit integer.  If more than 2.1GB is avail-
  able there is an overflow, it appears no space is available, and the instal-
  lation program refuses to continue.  Two solutions are:

  o   Partition the remaining space into maximum 2GB partitions.

  o   Retain the large partition, but before trying to install software create
      a large temporary file that reduces available space to less than 2.1GB.
      After installation of the application delete the temporary file.

 
  3.10  Very Large (128/137 Gb limit) Hard drives considerations (48 bit LBA)
  _____________________________________________________________________________

      Legacy LBA (also know as 28 bit LBA) maximum drive size is limited to 137
  GB (268,435,455 sectors by 512 bytes each). The 48 Bit LBA support was
  introduced to break this barrier and provide support for hard disk with sizes
  larger than 137 GB.
      This version  of the IBM1S506.ADD driver has the 48 bit LBA support and
  the driver will automaticaly detect drives with the capability of 48 bit LBA.
  This 48 bit LBA support will allow the use of hard disk drives with up up to
  2 TB (Terabytes) (1 TB = 1024 GB) in size.
      Currently the OS2DASD.DMD driver has a limitation of 502 GB in size for a
  hard disk.  Therefore the maximum physical hard disk size OS/2 will support
  currently is 502 GB.
      To maintain backward compatibility a new config.sys parameter,"/!BIGLBA",
  is introduced. If "/!BIGLBA" is specify in config.sys, this parameter for the
  specfic drive will disable 48 bit LBA  support and will revert to legacy 28
  bit LBA and usable drive size will be limited to 137 GB (268,435,455 sectors
  by 512 bytes each). If the drive is partitioned when using this switch, then
  it will be compatible when connected to a system without 48 bit LBA support.
  See section 3.8 for the "/!BIGLBA" parameter syntax.


  4.1.2  ASSIGNMENT OF DRIVE LETTERS

  New Algorithm: no filters assumed

     Primary from fixed disk 1
     Primary from fixed disk 2

     Primary from fixed disk n
     Extended from fixed disk 1
     Extended from fixed disk 2

     Extended from fixed disk n
     Primary from removable disk 1
     Extended(s) from removable disk 1
     Primary from removable disk 2
     Extended(s) from removable disk 2

     Primary from removable disk n
     Extended(s) from removable disk n

  Lack of a primary partition (or Extended Partition only) is allowed.  If no
  media is present at boot, a single logical drive is reported.  Note that some
  drives, Syquest EZ135A for example, do NOT report correctly when no media is
  present and will not be seen at all.  If media with multiple partitions is
  present at boot, then all partitions will be assigned drive letters.

 

Another thing, to install boot manager on a new install you need updated install disks and you must select advanced install.  You will automatically be presented with the fdisk screen from which you can select boot manager etc.

RobertM

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2034
    • View Profile
    • A.I.BuiltPC - using OS/2 Warp Server & eComStation for Custom Web and Database Solutions
Re: OS2 warp 4 hard drive size problems
« Reply #19 on: 2008.10.25, 02:06:21 »
"In that case, resort to DOS 6.22 (or whatever version you have already on HDs) may be necessary to first "un-lock" the drive, from whatever OS/2 FDISK won't touch."

Which may mean deleting any "non-standard" partitions (ie: any that OS/2 doesnt like, like a FAT32 partition, a greater than 2GB FAT16 partition, or an NTFS or Linux partition, or another bootloader).
|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


RobertM

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2034
    • View Profile
    • A.I.BuiltPC - using OS/2 Warp Server & eComStation for Custom Web and Database Solutions
Re: OS2 warp 4 hard drive size problems
« Reply #20 on: 2008.10.25, 04:29:30 »
Oh, and there's NO difference between FAT16 partitions as such created by whatever OS, though are OS-dependent differences in master boot records (MBR).

Yeah, I wasnt entirely sure about that - I just know that certain versions of Windows (and maybe certain DOS versions?) started using weird (or different) codes to represent them that fdisk would choke on.
|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


Fahrvenugen

  • Full Member
  • ***
  • Posts: 203
    • View Profile
Re: OS2 warp 4 hard drive size problems
« Reply #21 on: 2008.10.25, 19:52:08 »
That is fantastic! I have to run down a spare HD to attemp this, but I will get back with you on my sucess/failure! I'm glad that this exercise was useful for you as well. I know I've been blasting with questions, but here was another glitch that happened to me that I was hoping you could shed some light on. When I put a second drive on as a slave the boot mananger changed all of my drive designations which really P$%## off my config.sys as nearly every line referenced the D: drive. I went through and changed every instance of D: ...


Hi,

Skimming through, I think this was hit upon in one of the posts, but just if it wasn't...  the second drive you installed as a slave probably had a primary partition on it.

The way non-LVM OS/2 assigns drive letters is to first assign them to primary partitions, then logical partitions.  So if you add a new primary to the system, upon boot, it'll scan and find it, and anything on a logical partition will have its drive letter changed.  (at least that's the quick answer).  I know, it is a pain in the a**.


millese

  • Newbie
  • *
  • Posts: 26
    • View Profile
Re: OS2 warp 4 hard drive size problems
« Reply #22 on: 2008.10.25, 23:40:36 »
O.K. all I went to run the sysinstx command and it says it is not recognized as an internal or external command. Any Ideas? I tried "help sysinstx" and it comes back as "topic not found". Thanks

RobertM

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2034
    • View Profile
    • A.I.BuiltPC - using OS/2 Warp Server & eComStation for Custom Web and Database Solutions
Re: OS2 warp 4 hard drive size problems
« Reply #23 on: 2008.10.25, 23:47:23 »
O.K. all I went to run the sysinstx command and it says it is not recognized as an internal or external command. Any Ideas? I tried "help sysinstx" and it comes back as "topic not found". Thanks

Hi,

From the CD media, do the following...

DIR SYSINSTX* /S /P

That will tell you where it is located. Then simply call it by it's full path (eg: "g:\OS2\BOOT\SYSINSTX C:")

It just means that the program is not in the path statements defined by the installer.


Though, I am curious, why are you trying to run sysinstx?

-Robert
|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


millese

  • Newbie
  • *
  • Posts: 26
    • View Profile
Re: OS2 warp 4 hard drive size problems
« Reply #24 on: 2008.10.26, 00:48:44 »
I'm not sure how you copy and paste in peoples comments like you do, but earlier on in ddan's suggestions on how to copy a system over he said to xcopy c: x: /h /o /t /s /e /r /v then run sysinstx x: i'm assuming x: is the drive i'm trying to set up. One other question does the xcopy command move all the files? I though I caught a glimpse of file that wouldn't copy when I kicked it off, but it was going by so fast I wasn't sure. 

RobertM

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2034
    • View Profile
    • A.I.BuiltPC - using OS/2 Warp Server & eComStation for Custom Web and Database Solutions
Re: OS2 warp 4 hard drive size problems
« Reply #25 on: 2008.10.26, 01:23:23 »
I'm not sure how you copy and paste in peoples comments like you do, but earlier on in ddan's suggestions on how to copy a system over he said to xcopy c: x: /h /o /t /s /e /r /v then run sysinstx x: i'm assuming x: is the drive i'm trying to set up. One other question does the xcopy command move all the files? I though I caught a glimpse of file that wouldn't copy when I kicked it off, but it was going by so fast I wasn't sure. 

Assuming you did not boot off either drive, there should be no errors, and all files should copy. If you booted off either drive, you may have gotten an error about a file bing locked and unabled to be copied. It should be accompanyied by a beep. Ideally, you should have booted off some other form of OS/2 boot media (floppies, bootable Warp v4.52 CD, etc) and then xcopy'd.

I've successfully moved entire OS/2 installs that way - and only once had to run sysinstx using that method.

Robert
|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


Fahrvenugen

  • Full Member
  • ***
  • Posts: 203
    • View Profile
Re: OS2 warp 4 hard drive size problems
« Reply #26 on: 2008.10.26, 06:00:56 »
I'd suggested sysinstx.com - I've found that when I copy over an entire partition using xcopy, it usually won't boot for me until I run sysinstx

but you're right, sometimes it is not needed.

BigWarpGuy

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 649
    • View Profile
Re: OS2 warp 4 hard drive size problems
« Reply #27 on: 2008.10.27, 02:38:23 »
I tried to do a xcopy of the first cd of the eCS 1.1r disc onto an usb drive but it would not boot. I will check out the sysnstx.com .  8)

http://www.markcrocker.com/rexxtipsntricks/rxtt28.2.0113.html
"The SYSINSTX command

Use the command SYSINSTX.COM (normally in the directory
\OS2\INSTALL\BOOTDISK or on the installation disk) to make an OS/2 drive
or diskette bootable. Note that for using this command on HPFS drives the
DLL UHPFS.DLL must be in a directory in the <LIBPATH.   

Source:  The OS/2 WARP Survival Guide
http://www.markcrocker.com/rexxtipsntricks/rxtt28.2.0570.html
"
« Last Edit: 2008.10.27, 02:44:37 by BigWarpGuy »

RobertM

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2034
    • View Profile
    • A.I.BuiltPC - using OS/2 Warp Server & eComStation for Custom Web and Database Solutions
Re: OS2 warp 4 hard drive size problems
« Reply #28 on: 2008.10.27, 03:18:47 »
I tried to do a xcopy of the first cd of the eCS 1.1r disc onto an usb drive but it would not boot. I will check out the sysnstx.com .  8)

Indeed. For USB media, running sysinstx would be a requirement as there is no MBR set up (or not a proper one for OS/2 booting). The same would be true for various hard drive scenarios as well. It cant (or is unlikely to) hurt by running it as a "just in case" - as well as of course in scenarios such as above.

Robert
|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


BigWarpGuy

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 649
    • View Profile
Re: OS2 warp 4 hard drive size problems
« Reply #29 on: 2008.10.27, 04:49:24 »
I have a 1 gig usb flash drive and will give it another try. Thanks for the information.  8)