Does the installer complete the first half (the text based half) of the install? Or does it not even get that far? If it does complete the first half of the install a few things to check...1. when you updated the install disks, did you update with the IBM file IBM1S506.ADD or did you use Danis506.add? I recommend using Danis506, it works a lot better then the IBM driver. But you may have to find a few drivers not used to remove from the install disk, because DANIS506 is a little bigger then IBM's driver.
http://hobbes.nmsu.edu/cgi-bin/h-search?key=danis506&pushbutton=Search
2. Are you trying to install OS/2 to the FAT partition, or an HPFS partition? And is that partition set as "Startable" in FDISK? If FAT, then be sure your partition is no larger then 2 GB (but it appears you've already done that). But I recommend formatting it HPFS and installing on that... OS/2 just runs so much nicer on HPFS.
3. Try booting up with your install disks, exit out to a command prompt, find which disk has SYSINSTX.EXE on it (I think it is on Disk 1 or 2 within the 3 install disks), pop that into your floppy and run:
sysinstx c:
from the command prompt. This will copy over some of the boot files to the hard disk. Usually the installer will do this for you during the install, but I have seen systems where this for some reason doesn't happen and needs to be done manually.
4. If all of the above fail to help, it is possible that it is actually starting the boot process, and one of the drivers loading up in the config.sys on the hard disk is causing the PC to lock up. Try hitting ALT-F2 initially when the computer starts to boot (with this it normally will show you the driver names as they load up), this might tell you if it is hanging on a particular driver. If that doesn't work, try using your install disks to boot to a command prompt, and edit the config.sys on the C: drive, REMing out any drivers that are not needed for that notebook. While I havn't seen the difficulty with Warp 4, I recall with Warp 3 there was a driver (I think it was for a Sony CD Rom or soemthing like that) that always seemed to be installed, but never seemed to be needed by any system, which would cause a lot of systems to lock up... and once that driver was REMed out, things worked again. It is possible that there is a driver like that in your Warp 4 install which does not like that notebook.
Good luck!