Hi,
A few thoughts.
If you have not already, grab warpinst.exe from IBM and copy replace older files on your boot disk(s) with files in the archives. Especially anything dealing with SCSI since you're working with a SCSI system - with perhaps the exception of the drivers that actually work with your SCSI card. You can grab this file from:
ftp://service.boulder.ibm.com/ps/products/os2/fixes/v3.0warp/english-us/warpinst/Yes, IBM still has OS/2 files available on its FTP servers!
The system memory should not be a problem. The main issue with Warp 3 was that if the system had more then 64 MB, then Warp would not see memory above 64 MB. Once installed and up and running you can use patchldr from Hobbes to see the "extra" memory - up to 512 MB as I recall (the Warp 3 kernel has a 512 MB limit)
http://hobbes.nmsu.edu/h-search.php?key=patchldr&pushbutton=SearchFor the hard disk, there is a limit on how big the boot drive partition can be in Warp 3. The boot partition for OS/2 must be with the first 1024 cylinders of the disk - if the end of your boot partition is beyond the first 1024 cylinders then the install won't complete, the system won't boot.
For starters - try the install using the Advanced install, go into FDISK when it lets you do so, and delete all partitions on the drive. Select the option to write the changes to the disk and then reboot - power down, boot back up with your floppies selecting the Advanced install.
After the reboot see if it'll let you install Boot Manager and create a parition on your drive. Your boot partition does not need to be very big. Remember this is Warp 3 which came out originally in 1994. 200 MB is adequate for the OS install, in fact the original manual recommends 25 to 55 MB for the boot partition (although I do recommend more since - after you get things like TCP/IP, stuff from the bonus pack, and Fixpak 40 installed you'll need more then 55 MB). Assign your Boot partition as Startable and assign it as Drive C (if FDISK doesn't do this already, I can't recall - it has been a few years since I did a Warp 3 install from original install disks). Exit FDISK and select the option to write the changes to disk.
On Warp 3 installs I've often gone with 500 MB boot drives with success. Note that making sure the boot partition is within the first 1024 cylinders of the drive should take care of the issue that Bogdan is talking about suggesting a smaller then 8 GB drive. If Warp can see the drive itself (which is suggested based on the posted screen shots), then it is more likely a problem that the partition is just too big.
Note - if Warp 3's fdisk won't let you partition the drive properly you may have to use something like DFSee as suggested in an earlier post.
If I recall correctly you'll have to reboot again with your floppies, again select the Advanced install. See if you can get it to the section where it'll let you format the partition - use HPFS - and if it'll do that then hopefully it'll go through the rest of the install.
** On some systems it'll get through the first part of the installation process, will try and boot to the hard disk to continue the process, and it'll fail to boot. On these systems if it gets through the text-based install but fails to boot to the graphicall install part, try the following:
1. Boot with your floppies, when it gets to the "select easy install or advanced" it also has an option to press F3 to go to a command prompt/exit. Press F3
2. From the command prompt, type:
sysinstx c:
You might need to search around to figure out which floppy the sysinstx utility is on - if I recall it is on either disk 1 or 2, you can do a dir command at the promot to see the floppy directory / contents.
Assuming it does not come up with an error, pull your floppy out and reboot with CTRL-ALT-DEL
Sysinstx is a utility on one of the boot floppies that'll transfer some of the main boot files over to the hard disk specified. The installation app is supposed to do this for you, but it doesn't always work.
Also a few hints during install. If you do get to the point of the graphical desktop and graphical install, do NOT try and install video drivers / sound drivers during install. Just let it do its thing using VGA and such. I've seen the installer crash while trying to install these drivers during an initial install. You can always install them once your desktop is up and running.
Hope this helps.
