After several days of trial and error, I finally got Windows NT 3.51 up and running on my IBM PS/2 Model 70 386. It's actually quite zippy and a well-suited OS for this! I'll hit a few highlights of the setup process in a 🧵 here. Let's talk about it!
So, first of all, for days and days, when I went to install either NT 4.0 or NT 3.51, I was getting this dreaded screen. I tried different versions of NT, different service packs, no luck. As it ends up, all of my problems were self inflicted...
So, you see, I have two McIDE cards: one is the McIDE and one is the McIDE-CF. I had assumed that they used the same Adapter Description File. That was an incorrect assumption! One visit later to the ZZXIO website, I had the right file!
From there, since I do have an internal ESDI drive, I needed to do some deconfliction in setup. Here were my final settings. I set Channel A to secondary, and Channel B to primary (more on that in a minute!) and the ESDI to primary. Boom!
So, why set the ESDI and Channel B to both primary? I needed to connect up a CD-ROM. I connected it as slave, and with this configuration, nothing conflicted.. and the DOS CD-ROM driver could find the drive. It's not everyday you see a CD-ROM drive hooked up to a PS/2 like this!
With this connected, I used some advice from this online article I found. Basically, I booted with a DOS boot disk and did a "winnt /B" to do a floppyless install. And it worked GREAT!
Installation of Windows NT 3.51 is "interesting." My network card did get detected after I loaded the driver disk, but later in the process, I had to enter its MAC address? Really? Yea, I guess so!
So, these days, it is all about minimum password length. For NT 3.51? It's about maximum password length: don't exceed 14 characters 😂
Anyway, I'm very pleased with this installation. NT 3.51 is a great OS for this system. I do plan to try NT 4.0 next, so keep an eye out for that. But that's all I have for now, thanks for following along!
@threadreaderapp unroll
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Okay, another successful experiment: Windows NT 4.0 Workstation installed on the PS/2 Model 70 386 with a 486 DX/33 upgrade! Let's talk about it in a 🧵
So, first, just like when we installed NT 3.51, settings are important. Here are my settings for my McIDE-CF and ESDI hard drive. Channel A (secondary) is my CF card. Channel B (primary) is where I connected up a CD-ROM on the slave channel. And the ESDI is primary!
I booted up into DOS and loaded CD-ROM drivers, and then used the "/b" flag to do a diskless install of NT 4.0 (I learned about the "/b" flag from a great online article!)
Alright, admittedly I did a TERRIBLE job trying to copy and preserve these disks! What did I do wrong? Well, pretty much everything. Let's talk about what I missed and just how terrible I did in a 🧵
So, first, I used a 1.2MB drive for 360K disks. While this isn't a totally terrible sin, we'll be much better off using machines with 360K drives due to the size of the read heads of the drive. As such, I've enlisted my Tandy 1000 HX and Compaq Portable II to help!
So, first sin? Not checking for hidden files. Using the attrib command, I found that all disks have them, and now I know why disk 2 was "blank." I should have caught this: when I ran the virus scanner yesterday, I saw additional files, but just figured they were in an archive.
The $2 optical drives are here! Let's try and test them out. I feel the Pacman PC will make a good test rig. Let's go! 🧵
So, here is the first drive. A 32X drive by Techmedia. Funny enough there was a Braveheart disk in the drive 😂. Looks like this drive doesn't want to recognize my test disk. Uh oh. Maybe we should open it up!
I opened it up and cleaned the lens. Tried a few CDs, both pitted and burned. Nothing. Going to call this drive a "fail"
I recently picked up this laptop stack you see here. I had one goal in mind: get a working processor card for my LTE 5200. We talked about the LTE Elite 4/75CX earlier today, but let's talk about the LTE 5200s. And... oh man... I think one of them spent some time swimming! 🧵
So, we'll talk about the "fun one" first. It must have spent some time underwater. To get it apart, I had to DRILL out the screw you see here. It was quite the ordeal, but we go through it!
Once I got inside, here was the first thing I really saw. Eek! Yea, that motherboard is going to be a lost cause. The system did not power on, and that is indeed the reason why: the mobo is shot!
It's time for some updates on the PS/2 Model 70 386. This week, I got a ton of parts in to put it together and spent some time configuring it with DOS and Windows for Workgroups 3.11. And, it has been an adventure. Buckle up for a fun 🧵. Here we go!
So, first, I did get all of the components installed! Here is what the system looks like with everything populated. You'll notice that the ESDI hard drive is plugged in. More on that in a minute... spoiler alert.. it's good news!
On a microchannel system, each board has to be configured. When you've added something and haven't configured it, you get an error message on boot, and you need to grab your Reference Disk and get to work. However, the system does a good job with automatic configuration.