Time for an update on this machine.
The system checks out fine, I even dug out my JEIDA Wrap Card and IBM 3-way serial/parallel wrap plug to run all the diags

Pentium 150, 48MB RAM and a 2GB hard disk.
Changed the OS/2 desktop to Workplace Shell, reinstalled the correct video drivers, and lo and behold, it's a pretty much standard OS/2 Warp 4 install with FixPak XR_M010 applied, dating from early 1999. From the file access date stamps it looks like it hadn't been booted since 2002.
Any foray into
Selective Install was thwarted by the fact that it had been installed off an additional drive no longer present, and there was no local copy of the OS2IMAGE directories; I enabled the PCMCIA ATA storage support (drivers were commented out) to allow me to use a MicroDrive in a PCMCIA adapter to transfer a copy of the files across.
The installation is not what I'd call a 'proper' preload, more a vanilla OS/2 Warp 4 install with the FP10 and System/390 tools added, like any number of corporate internal deployment images. There's no ThinkPad-specific stuff beyond the basics of video drivers and PCMCIA support, not even audio drivers. It's spread across 4 partitions: C: for operating system, D: for System/390 tools, E: for log files, and F: as basically unused space. I took an image of the entire drive for posterity. Counter-intuitively, all partitions including the OS/2 boot partition are FAT16 formatted, but that makes sense for servicing since the system can then even be booted from a DOS diskette for maintenance, e.g. if it becomes unbootable, or to transfer files to/from.
Actually I've had quite a trip down OS/2 memory lane with this. In order to make minimal change, but recover gracefully from my inadvertent initial error in resetting it to VGA, I spent a few weeks installing, patching, breaking, and recovering various revisions of OS/2 Warp 4 and 4.52 in VirtualBox. Reminded myself of an awful lot that had been forgotten, but was most pleased to find that
Alex Taylor's OS/2 FixPak Information pages are still alive and well - I remembered these from my last active OS/2 work circa 2008, superb flowcharts for versions and revisions to base OS, fixpaks, TCP/IP, LanServer, and so on. The FixPak structure is very logical for OS/2 and its subsystems, I suspect coming from other the more mature midrange and mainframe platforms, meaning that as long as you start with Warp 4 you can successively patch it up to the final available releases.
As a dead OS (or not, see
ArcaOS), it's easy to track down pretty much everything except the last few service updates that were made available to IBM enterprise customers on a subscription-only basis. The final accessible editions that I located were the v4.52 patch-rollup
Convenience Package 2 Refresh distributions of Feb 2002, essentially complete install CDs for Warp Client or Warp Server with all the prior fixes & updates slipstreamed in, plus
Software Choice update packages up to v9 released in Oct 2002, adding updates and fixes for USB support, TCP/IP, long-obsolete web browsers and Java versions, and so on. To remember where we were back then, one of the later updates was to fully support scroll-wheel mice!
One thing that surprised me was how easy it was to render OS/2 unbootable by, e.g. installing a driver for hardware that isn't present, but then also how easy it is to boot to a command prompt (ALT-F1 when you see the "OS/2 blob" after POST) and sort it out. I very quickly got into the habit of saving a copy of CONFIG.SYS before any such change, so that a quick boot to a command prompt could allow me to revert in seconds if necessary with a file copy, or by using TEDIT to head to the bottom of the current CONFIG.SYS and REM out the offending changes. Even things like properly installing the VirtualBox Guest Additions required such a move, in order to swap out the normally-locked video driver for the VirtualBox version. Incidentally, the VirtualBox Additions for OS/2 are on the standard Guest Additions CD image, and have good support for mouse/keyboard integration and host folder sharing. I was pleasantly surprised by how good they were.
In order to deal with live hardware, in particular for transferring files via USB or the MicroDrive/PCMCIA adapter, I first pulled out a T43 and installed OS/2 onto that, but rapidly realised that it was past the 2001 OS/2 development cut-off, and things like USB support were frustratingly obtuse. Instead, I back-tracked to a T21 and a spare 10GB drive and everything just worked - of course it would, OS/2 was still actively supported within IBM when the T2x range was current. In some ways, a 600 would seem like the Rolls Royce of Warp 4 support, being arguably 'peak ThinkPad' released before the axe hung over OS/2, but I'll leave that for a future project
Having worked with the 380 for some hours now, I have a little more respect for it, but still little love compared to the premium & ultraportable models. Swapping the button cell CMOS battery was trivial, after sourcing one. The FSTN display is OK, better than DSTN but still clearly not a TFT. Fiddling with the single slider to find least-worst contrast and clarity balance gets old quickly, although luckily on this unit there is only a slight intrusion of any panel degradation, which just shows up as fringe shading at the very corners. Of course the lack of a soft-touch rubber means it is in excellent cosmetic shape, given its peculiar life, and the absence of a cancer-inducing standby battery probably explains the cockroach-like survivability of the 380 series compared to other concurrent models. Since the 380 is not one of my favourite machines, I've pretty much had my fun with it and will be listing it on ebay in the next few days. Time for somebody else to enjoy it
I've been left with the T21 and T43 physical installs, several VirtualBox client images of Warp 4 and 4.52, plus a nicely set-up virtual Warp Server 4.52 with a LanServer domain and some file shares. I'd been mulling over what to use as a secure SMB v1 file server for installing and patching the ThinkPads. I don't have much love for SAMBA on Linux, so a virtualised OS/2 LanServer file server (with a shared host folder for ease of file transfer) seems like just the job. How many exploits are there in circulation for OS/2? Security by obscurity? Anyhow, it just seems "more IBM"

Following that logic, I'll need to dig out the Token Ring MAU, media converters and PCMCIA cards, and set up a DOS boot disk with TCP/IP, LAN requester, and PCMCIA token ring card support... actually I still have an image somewhere of just such a disk that I set up in the late 1990's
