Did you get to the GUI-Installer? It sounds to me, like a sort of hardware related issue.
Perhaps removing the V2?

brostenen wrote:

Did you get to the GUI-Installer? It sounds to me, like a sort of hardware related issue.
Perhaps removing the V2?

It hangs while booting the GUI installer. Removing both Voodoo2 and SB16 did not help.

How does the BIOS settings look? Check if "Memmory hole" is enabled and "Boot to Os/2" is enabled.

Have you updated the Warp 4 disk with a hdd driver that supports that capacity drive? Al Savages OS/2 pages should help. http://asavage.dyndns.org/os2/warp4install/warp4install.html

Also once installed OS/2 does hang on the boot splash screen for a wee while.

brostenen wrote:

How does the BIOS settings look? Check if "Memmory hole" is enabled and "Boot to Os/2" is enabled.

I don't have "Boot to OS/2" setting in my BIOS but have "OS/2 Onboard Memory > 64M". Already tried with that setting enabled/disabled and also every memory hole setting possible. Does not make any difference.

Caluser2000 wrote:

Have you updated the Warp 4 disk with a hdd driver that supports that capacity drive? Al Savages OS/2 pages should help. http://asavage.dyndns.org/os2/warp4inst ... stall.html

AFAIR Warp 4.5.x handles large IDE HDDs fine. At least it successfully installed in VirtualBox with disk setup mirroring that of the physical machine.

Caluser2000 wrote:

Also once installed OS/2 does hang on the boot splash screen for a wee while.

I waited about 20 minutes.

Select Alt-F2 when you see the OS/2 boot blob top left. That'll show you whats loading and where the hang up is. Alt-F1 will give you a menu selection. See if it boots to the command prompt.

OS/2 has manny issues. Too fast processors, too big harddisks, too much RAM.

The hard drive is too large. Out of the box, Warp 4 could only support IDE drives up to 8 GB. With the last free fix pack (FP 15), you could go larger, but that's not exactly helpful for getting things installed. Perhaps, you could look online for a copy of Warp 4.52, which is basically Warp 4 pre-updated with the latest fixpack.

Whatever you do, don't give up. OS/2 makes an awesome retro-computing platform with its excellent DOS and Win3.1 support and a bunch of cool stuff unique to it.

Caluser2000 wrote:

Select Alt-F2 when you see the OS/2 boot blob top left. That'll show you whats loading and where the hang up is. Alt-F1 will give you a menu selection. See if it boots to the command prompt.

It hangs while loading I2OSOSM.ADD.

mjkerpan wrote:

The hard drive is too large. Out of the box, Warp 4 could only support IDE drives up to 8 GB. With the last free fix pack (FP 15), you could go larger, but that's not exactly helpful for getting things installed. Perhaps, you could look online for a copy of Warp 4.52, which is basically Warp 4 pre-updated with the latest fixpack.

I'm already using Warp 4.52.

MasterM wrote:

It hangs while loading I2OSOSM.ADD. […]
Show full quote

Caluser2000 wrote:

Select Alt-F2 when you see the OS/2 boot blob top left. That'll show you whats loading and where the hang up is. Alt-F1 will give you a menu selection. See if it boots to the command prompt.

It hangs while loading I2OSOSM.ADD.

mjkerpan wrote:

The hard drive is too large. Out of the box, Warp 4 could only support IDE drives up to 8 GB. With the last free fix pack (FP 15), you could go larger, but that's not exactly helpful for getting things installed. Perhaps, you could look online for a copy of Warp 4.52, which is basically Warp 4 pre-updated with the latest fixpack.

I'm already using Warp 4.52.

I'd remove it from config.sys and see what happens 😀

So I removed I2OSOSM.ADD from CONFIG.SYS and it hangs at next driver: IBMINT13.I13. Then I removed IBMINT13.I13 and it hangs on IBMIDECD.FLT. So I removed IBMIDECD.FTL and it hangs on XDFLOPPY.FLT...

All these drivers seem to be related to storage (I2OSOSM being "ISO Storage and Transportation Operating System Module" and IBMINT13 is, what I assume, a BIOS INT13H handler) but at this point it's hard to tell if all of those hang by themselves or just because I2OSOSM is not being loaded.

I also tried physically unplugging the second HDD but that not helped either.

Got any other equipment? Maybe a ZIP drive?

RacoonRider wrote:

Got any other equipment? Maybe a ZIP drive?

Only floppy and IDE CD drive.

MasterM wrote:

RacoonRider wrote:

Got any other equipment? Maybe a ZIP drive?

Only floppy and IDE CD drive.

I remeber having trouble with Warp 3 refusing to boot due to a newer CD-drive. Had to install it using an older ASUS CD-ROM from 1999 and replace the IBMIDECD.FLT with newer and better drivers by Daniella Egbert.

Will the machine boot with no CD drive?

RacoonRider wrote:

MasterM wrote:

RacoonRider wrote:

Got any other equipment? Maybe a ZIP drive?

Only floppy and IDE CD drive.

I remeber having trouble with Warp 3 refusing to boot due to a newer CD-drive. Had to install it using an older ASUS CD-ROM from 1999 and replace the IBMIDECD.FLT with newer and better drivers by Daniella Egbert.

Will the machine boot with no CD drive?

It did not help either.

At this point I'm sadly giving up. I tried everything, changed IDE channels, tinkered with master/slave settings, plugged/unplugged drives in various configurations, disabled DMA etc... nothing works. There must be something inherently incompatible with OS/2 in my setup. I'll try it if I ever assemble a low-end 386/486 box. 😀