Bear with me here, this response is long. I'm going to reply to the fixpak questions, and also to the boot freezing issue... First, a quick crash-course on Warp 3 fixpaks....
Ignore the comments about the ddpak in the IDEDASD.EXE readme. For base Warp 3, you don't really need DDPAK to make things work, and in some cases I've seen it cause problems. The DDPAK fixpaks were meant to be installed on Warp Server (the version based on the Warp 3 code base, but with a few differences), Warp Server for e-Business (the version based on Warp 4), and Warp 4. While it is possible to install the DDPAK fixpaks on base Warp 3, I've run into problems whenever I've done this in the past. So I generally avoid it.
As for the OS2CDROM.DMD - eventually once you get Warp installed you'll end up with a line:
in your config.sys. This is one of the device drivers which OS/2 needs to access the CD Rom drive.
The other item about the IDEDASD.EXE package is that it contains a file called DASD16.DMD. You need to re-name this to OS2DASD.DMD and then use that copy to replace that file in your \os2\boot directory. I think this is outlined in the README but I'm not sure.
And that leads me to my second point... for Fixpaks for Warp 3 (base, non-server), I've found the best fixpak to install is Fixpak 40. This was the last *free* fixpak from IBM for Warp 3. Fixpaks 41, 42, and 43 all had the client stuff taken out of them and were only officially recommended for Warp Server. That's not to say that you can't get these fixpaks to install on Warp 3 - it is possible and some people have had success doing this. But the results have been mixed. Some have had good results, some have run into problems. As a result, I generally recommend FP40 over the others. But in the end it is your choice.
The other benefit of Fixpak 40 over 41 through 43 is that 40 still contained driver updates as a part of the base Fixpak. Fixpaks 41 to 43 had the driver updates removed and spun off into the DDPAK fixpak. So, by going with FP40, you get the OS updates and driver updates all in one.
Anyways, if you want Fixpak 40, you can download it direct from IBM at (and I'm assuming you're using the US English version here, if you need a different language post a response and I can post the correct location):
If you want Fixpak 42, it is at:
And Fixpak 43 is at:
These links are to the RSU version which can be installed directly off a hard disk / CD Rom. You can also download floppy-images for the fixpak and play floppy-toaster to install it (the same way it sounds like you did with the Warp install), although this takes a lot more time. The floppy images are at:
For the floppy version, you'll need the loaddskf.exe utility to create the floppies (I think there is a copy of this on the OS/2 CD Rom somewhere)
For installing Fixpaks off a hard disk / CD Rom... the RSU version, download all the XR_W040?.ZIP files into one directory, and the CSF143.ZIP into another directory. Once all downloaded, unzip all these files, using an unzip application which will create directories. Since you don't yet have OS/2 up and running with internet access you may want to do this on a working machine and burn it to a CD Rom or something. But that's up to you.
To install the Fixpak, you'll want to open up an OS/2 command prompt window. First create a directory where it will store a backup of the replaced file, my recommendation is something like:
Then change into the directory where you have unzipped the CSF143.ZIP file, and enter the following:
OS2SERV x:\csf143\CSF x:\fp40
Of course, fill in the drive letter and directory names as per whatever it is on your machine. When the Fixpak Installation window comes up, select one of the "Serviceable products" and click the "Advanced" check box, then hit Install. It will then kick in the Corrective Service facility, it should select all the serviceable products. Hit "Service", enter the directory name where you want the Archive put, and hit OK. It will probably tell you that there are some files it won't update until the next reboot, that's fine, just chose the "Continue" option. And as it goes, it will probably tell you there are some files which have newer date/time stamps then what is in the fixpak. The general rule of thumb that I use on a freshly installed system is to have it replace all the files with the ones in the fixpaks, except for the ones that I've manually updated to get the thing to boot (for example, files in the IDEDASD.EXE package).
Okay, end of the quick crash-course on Fixpaks... on to the question of the freeze-on-boot problem...
First, I'm assuming you've put the contents of the IDEDASD.EXE package (including the renamed OS2DASD.DMD file but EXCLUDING the DASD32.DMD file) into the c:\os2\boot directory. If you havn't yet then use your floppies to boot to a command prompt and do this and see if it fixes the problem.
If I understand you correctly, it is freezing on the OS/2 splash screen when you just start to boot it, after the little "boot blob" appears in the upper left corner of the screen. If this isn't the case, scan to the bottom of this post.
It sounds like it could be a driver issue. One thing to try is to reboot, then when you see the white boot "blob" in the upper left corner of the screen, hold down alt-F2 (you probably need to be quick on this). It'll list the driver names as they load up, see how far it gets.
Second thing - reboot again after it "freezes" only this time hit ALT-F1 while it has the "blob" while booting. You'll then get a menu where you can chose a command prompt, the maintenance desktop, revert to VGA, and boot normally.
If it is a driver which is causing the crash, you can try seeing if you can get to a command prompt and REM'ing out the driver in the config.sys (use something like TEDIT to edit config.sys)- that is as long as the drivers aren't critical to OS/2 running (for example, don't REM out the IBM1S506.ADD (or DANIS506.ADD if you're using that instead) - this is needed to control your IDE interface). I'm assuming this system does not have SCSI - if it does, then you may need to update your SCSI drivers - some of the SCSI drivers in the original Warp 3 release just didn't work properly. Also two drivers that I ran into problems with the last time I installed Warp 3 were:
For the purpose of getting booted up, you may want to try REM'ing out these drivers and see if it will boot. I should mention that the TESTCFG.SYS is required for the Selective Install utility, but not necessairly needed for Warp to just boot and run. But it is also worth noting that there are updated versions of these drivers in Fixpak 40, so once you get the system up and running, if you then manage to get FP40 installed you should be in good shape and able to restore these drivers.
I have also had freeze-up problems with the following:
If these drivers are listed in your config.sys, REM them out. Chances are you won't need them anyways.
Another thought - if you had Warp install a specific driver for your video card instead of standard VGA, this may be causing a problem (one driver I had trouble with was the base Warp 3 ATI Mach64 driver - but installing a newer driver worked fine for me). If this is the case, try the "Revert to VGA" option and see if that works.
And the final possibility that I can think of - if it isn't even getting to the OS/2 splash screen when you reboot, try booting to the command-prompt with your boot / install floppies and run the following:
I can't recall if SYSINSTX.COM is on Disk 0, 1 or 2, you'll have to look for this, but this will re-setup the hard disk partition to boot Warp (sort of like the old SYS C: command in DOS). If I recall correctly, the installer shipped with the old Blue-spine version of Warp 3 didn't always run this command properly when it did an install, and many had to run it manually during the installation process.
I should mention that there are some system kernels which seem to have difficulty booting on some machines, but I am guessing that this isn't the problem because you were able to get through the install process, and it just won't boot after installing. It sounds like the problem is elsewhere.
Sorry for the length of this reply, I hope this helps. It is possible to get Warp 3 running on current hardware, just a little difficult and frustrating at times. Let us know how things go!