First of all, I am joining Ivan: which version of OS/2 are you using? Warp 3 (up to late fixpacks) and Warp 4 (up to FP6) cannot install to a 7 GB disk without patching installation diskettes.
Probably not correct in
THIS scenario. Warp *3* (as updated in Warp Server v4) will install on larger drives than that in certain scenarios (many scenarios of this particular nature where a high end (for it's time) machine of this sort is being used). You are missing the point that this is a system designed to control some automated or manufacturing or monitoring system. Various IBM systems of it's age worked on larger drives... PARTITIONING is the key on the problematic ones (and not necessary on various other setups).
This especially applies to SCSI from my experience. I've used both 9GB Seagate and 36.4GB IBM drives as boot drives under Warp Server v4.
which version of OS/2, Warp3, Warp3 connect, Warp4, WSeB etc, all have slightly different requirements to install. What type of hard disk IDE or SCSI and if SCSI what controller is used?
Assuming this is the same system, new hard drive.
This system will be a Warp 3 or Warp 4 system. Most systems of that nature are either OS/2 2.1 (not applicable based on drive size - note his comment about how much data they had on the failed drive - 3GB), the rest are split between Warp 3 (normally 60%+ chance), or Warp 4 (normally 40%- chance). At 10 years old, it would *seem* Warp 4 is the more likely candidate, though in this scenario, that may not be true since numerous machines like this came out on the same version of OS/2 for many years after a new version of the OS was released. Just as numerous ancient ATMs started on v1.3... and continued (for ages) to be replaced with brand new v1.3 machines.
This system is
probably IDE. There were not many SCSI drives that formatted down to 7GB (the general size in that range was 9GB, which formatted to the 8.x or sometimes as low as 7.8GB range). There were a variety of short run IDE drives that were 7GB in size, including various 7.2GB drives that came pre-installed in various DELL systems that were used for such purposes.
If the system IS SCSI, then it will be a matter of determining the SCSI subsystem's boot limitations. They were generally 8GB (CANNOT format a boot partition to anything over 7.8GB, MUST be in the beginning of the disk - EVEN if Bootmanager is installed to kick off the boot process), or 4GB (approx 3.9GB boot partition, same rules), or 2GB (1.9GB boot part, same rules). These rules (for SCSI) apply to virtually every setup, for ANY version of OS/2 up to and including WSeB/Aurora v4.52 CP2 PF, for virtually all Adaptec and LSI Logic (and thus IBM and most HP systems) SCSI subsystems.
Most IBM/Adaptec cards of that age support up to a 7.8GB (partitioned size) boot partition. Numerous HP systems, non-IBM LSI Logic based systems, etc have different boot limitations. Those CANNOT be gotten around by ANY patch available. Many Adaptec based setup has an option that MUST be set to enable booting to over 2GB (1.9GB partition size). If that option is NOT set, then the boot partition is limited to 1.9GB (as the OS recognizes it).
These types/age systems, if they can install on the drive (as is his case), usually are installing to a partition beyond the boot capabilities of the BIOS (IDE or SCSI), or on the border of the BIOS' boot limitations - which results in the error shown.
The simple fix is to have a boot partition in the 1st 1023 cylinders (IDE) or within the boot limitations of the SCSI card (2GB/4GB/8GB depending on card).
Best,
Robert