Sadly i gave up trying to install OS/2 even on my T21, too many ifs and buts to make it work. So i just run it on a VM in my x201.
One cannot simply just give up in the wake of Windows 10 and languishing T43s.
After reading from more (ancient) webpages, this is the best avenue for creating the three diskettes. It turns out much of the antiquated information makes you do extra foot work for no reason so we'll skip all of that. There'll be two CD-ROMs for OS/2 Wwarp 4.52, the boot CD-ROM (which is also the one you put in if you want to boot from disc instead of diskette) and the client CD-ROM.
Spoiler: it is possible to modify the CD-ROM boot image and 'cure' it of its antiquated drivers.
You'll want to put in the second 'client' CD-ROM and navigate to the following directory:
(assuming D:\ is your disc drive)
In this folder you'll see three .DSK files (antiquated docs will require you to use XDFCOPY, but just use WinImage since it handles that file format without issue). The three diskette images are as follows:
disk0.DSK - "installation diskette"
dsk1_cd.DSK - "diskette 1"
disk2.DSK - "diskette 2"
NOTE: when referring to 'diskette 1', never assume the installation diskette.
Copy the three images and write them to three diskettes using WinImage
Now it's time for a brief detour and relish in the problem of IDEDASD.EXE. Apparently IBM did update this (which is one of the problems for removeable storage and addressing higher capaities) in 2005. Which, is the same time the T43 came out. Maybe that was deliberate since IBM did offer T43s with OS/2 preinstalled, although I imagine it wasn't a popular option and stock preloads of that are long gone no doubt. Fortunately we're lucky IBM still had the IDEDASD.EXE package for download. Most sites will link the following:ftp://ftp.software.ibm.com/ps/products/ ... dedasd.exe
Which of course is long gone. BUT, it's still for download here:http://service.software.ibm.com/os2dd/free/idedasd.exe
(Really it would be awesome if someone could dump the entire http://service.software.ibm.com/os2dd
directory, but public viewing is not enabled). IBM probably still has it up for scarce clients that still go to them for OS/2 support. Here's the note about it on eCS regarding IDEDASD.EXE:http://www.ecomstation.com/news.phtml?a ... ws&id=1079
However the problem with eCS is that you need a registered license to log in and download the files... so I'm glad IBM kept their old link up. IBM's does seem to be an older 2003 release, but the updated 'OS2DASD.DMD' to fix 'traps' with removable media can be searched for later. At the end of the day if I like OS/2 Warp 4.52 enough, I can always buckle down and buy an eCS license.
In fact, IBM still has a bunch of files and fixes for Warp 4.5:ftp://service.boulder.ibm.com/ps/produc ... /v4.5warp/
(I'm going to dump all of those files later for preservation).
Going back to IDEDASD.EXE, you'll need to fire up a Windows 9x or MS-DOS computer because it's in a 16-bit self-extracting module (I'm going to be uploading the uncompressed IDEDASD files so this step can be evaded in the future). Why'd they even do this? It's not like 100 KB was a big difference in 2003, they could have just used a standard .ZIP instead of using an MS-DOS self extracting module. 2003 was the year when I went from 98 to XP, **so let's say I was actually doing this back then**, I wouldn't have had an MS-DOS computer handy if it failed to extract under XP.
Sidenote: it was utter torture being stuck on XP with no MS-DOS support. The clown interface always bothered me, too.
So the DASD readme has some useful tidbits, including mentioning that SATA is supported (I've had trouble finding this information out since it's not really explicitly mentioned anywhere):
The IBM1S506.ADD driver automatically detects Intel Serial ATA and Parallel ATA controllers described in section 5.1 and enables the highest possible DMA/UDMA modes for all drives.
Well great, T43s with the SATA mod will have no problem then. Although OS/2 Warp 4.52 does detect something even under sata because it attemps to do the dumb LVM thing until you wipe the drive.
Taking a look at what OS/2 Voice had added in regards to IDEDASD.EXE:http://www.os2voice.org/VNL/past_issues ... newsf4.htm
Follow the instructions in the IDEDASD.EXE's readme file and copy the patched drivers to disk 1. Missing from the instructions is that OS2CDROM.DMD from the IDEDASD fix needs to be copied to Disk 2. Be sure to copy this new driver to Disk 2.
The IDEDASD readme is already long enough as it is and they forgot to add that? I'm guessing some poor sap in 2003 probably copied the OS2CDROM.DMD to diskette 1 without knowing then (an earlier file of OS2CDROM.DMD is on diskette 2, so that's how you're supposed to know, presumably).
Okay, section 2.1, updating the installation diskettes:
If you are attempting to install Warp on a hard drive greater than 4.3GB, or your are attempting to install Warp Server for e-business on a hard drive greater than 30GB, then the Installation diskettes must be updated.
So here's what we want to copy to diskette 1 (note that's diskette 1 and not the installation diskette):
DASD32.DMD (and rename to OS2DASD.DMD before copying)
And the following needs to be copied to diskette 2:
And we're adding the following line to the top of CONFIG.SYS on diskette 1:
*insert obligatory 'don't copy that floppy' jingle*
Next we need to free up some space on diskette 1 to copy over the extra IDEDASD files. These are the files that I removed off of the diskette (563 KB in total):
And here's the following lines in CONFIG.SYS that need to be removed (you could comment them out but who cares):
(otherwise the COPYFROMFLOPPY=1 will presumably get upset that it can't copy).
But wait-- we're not done yet! The SNOOP list needs to be edited too, so that it doesn't look for the three .SNP files we removed. Comment out the corresponding SNPs under SCSI snoopers:
; SCSI Snoopers
;aha6360.snp <-- bing
;aic7870.snp <-- bang
AIC7770 isn't listed in the snoopers list, so... I guess we can shrug our shoulders since what's not there to begin with cannot be commented out. And if it could, it would break time in the world as we know it, causing a WARP to appear. Suddenly all PC clones would become IBM PCs with OS/2, and every monitor would be converted to 4:3. *gasp*
These are all for Adaptec SCSI cards, so if you need adaptec, copy some different drivers off that you won't need. Rinse and repeat for editing CONFIG.SYS and SNOOP.LST. Don't be a snoop and keep your snoopers in order.
Anyways, once that's done, THEN you can finally overwrite CONFIG.SYS and SNOOP.LST with your new files to diskette 1. Now connect le USB floppy diskette drive to your T43p w/ RBS SATA mod. Pop in the INSTALLATION DISKETTE (not diskette 1, or diskette 2, or OS/2 Warp 4.52 boot or OS/2 Warp 4.52 client). Then it'll ask you to put in diskette 1 and 2 afterwards.
And once you get to diskette 2, you'll get the following error message:
OS/2 is unable to operate your hard disk or diskette drive. The system is stopped. Correct the preceding error and restart the system
That's OS/2-babble for "we cannot find the appropriate driver from the diskette to install to this T43 hard disk". So even a stock IDEDASD.EXE didn't update it to the point where the T43's hard disk could be initiated. Therefore, time to try out the danis506.ADD instead.
So I'm changing basedev=ibm1s506.add to basedev=danis506.add, and I copied the following files to diskette 1:
And soon as it hits diskette 2 like last time, the same OS/2 is unable to operate your hard disk. Investigating the contents of diskette 1, there's CONFIG.X, I'm not sure if this needs to be changed, but I updated it to this as well: basedev=danis506.add
After some other searching yeah, we can make a few more changes.
I commented out 'ibm1s506.snp' on the snoop list (apparently this is only needed for ISA devices). Actually, Dani advises to get rid of all snoopers, so this is the before:
After de-snooping and editing CONFIG.X as well, giving it another shot. Same story.
The issue could be the following of reasons:
#1 soon as it hits diskette 2, the installer fails to recognize the USB floppy drive properly
#2 the danis506 package doesn't work / doesn't support T43s
#3 I'm not doing something correctly
Since IBM *did* have Warp 4.52 installed on T43s, it should theoretically be possible to use exclusive IBM packages for the process, but we'd need the 2005 IDEDASD along with the latest service packs etc.
I investigated the contents of the first boot CD-ROM, it apparently contains the diskette boot images and simply goes through the process like it would the diskette, although with more things obviously (also I've never had the "OS/2 is unable to operate your hard disk or diskette drive" issue with the CD-ROM). Therefore, it is possible to edit the CD-ROM image with the proper boot files and forgo diskettes entirely. So I'm going down this path since the CD-ROM doesn't catastrophically fail like the diskettes, it just doesn't find the hard disks which *should* be resolved with danis506.
Changes need to go to d:\bootimgs\disk_0_1.img on the first Warp 4.52 disc.
I'm using 4.52 .086 instead of .089 due to the fact that the .089 package on winworld reportedly has issues. However, .089 may have some needed changes for the T43 hardware so I am downloading that image to see if some of the files are updated.
I've also read that danis506.add needs to be in '\os2\boot', so I'm guessing the drive should be partitioned prior to OS/2 being installed. My suspicions were correct, .089 has updated boot images versus .086. So let's frankenstein the updated files over.
I took the following updated files from .089:
And as usual added the updated IBM IDEDASD files and the DANIS506 files / and the CDROM one for disk 2. But this time I also moved over the following, because why not, may as well update everything:
Then I use ImgBurn to create two updated disk_0_1 and disk_2 .img files. Then using WinRAR I extracted the Warp 4.52 .086 .ISO, injected the files, rebuilt the .ISO -- burning to a CD-ROM
And we get the following:
Operating system not found
Okay, so it's clearly referring to the disk images we edited (disk_0_1.img and disk_2.img). I didn't use the 2.88 and 1.44 (which seem to be mirroring floppy sizes). So we need to get a bit more clever by using WinImage to assist.
Why did IBM use .IMG for some weird pseudo floppy diskette images anyways? You'll notice there are no .MD5 files as a result...
I had to delete the updated IBM1S506.ADD to make it fit on 2.88, but hopefully it's not calling that file anymore anyways since we removed it entirely from CONFIG.SYS/X and SNOOP.
So we create a 2.88 disk size and flip it to 'all files' so we can actually save in the .IMG extension, and its name of course is disk_0_1.img. Rinse and repeat for disk_2.img. Recompile the ISO, burn another disc, and give it another test.
Aaand, still no dice. The problem appears to be that the disc isn't bootable after the recreation. Because I am too lazy to investigate the cause (I have come across it before if you just extract the contents out of an .ISO and attempt to recreate it it's no longer bootable-- probably needs a special flag or signature), I'm downloading WinISO to edit the original ISO and re-inject the new files, but because we can't go over 500 MB, I'm deleting the Java118 folder. With that done, let's see if THIS works now. This will be CD-ROM #3, good thing I have a massive stash of writable CDs...
Shebam! Editing the .ISO worked and it's booting from the modified disk_0_1 and disk_2 images. However, one step forward, two steps backwards, I get the same error "OS/2 is unable to operate your hard disk or diskette drive". So this problem isn't being corrected by danis506 for some reason (the same error will happen with the IDEDASD package). I'm going to try editing disk_0_1 again and see if I can track down some more drivers and things to help it along.
Once that's done, it can all be edited back to the .ISO and nobody will have to deal with diskettes again.