Okay, it's finally time to talk about the latest chapter of my Bernoulli 20MB adventures. Fortunately, we have some good news! I'll be building a 🧵 here as we go, so let's get to it!
Before we get into it, in case you haven't seen what a Bernoulli disk looks like, here we have one! We have the "sleeve" for storage, and then we have the front & back of a disk! And, as you see, we have a few disks.. I went form not being able to find them, to having a bunch!
So, first of all, I suspected that I MIGHT have a bad drive. As such, I found this Bernoulli Beta 20Z drive for sale on eBay, and I picked it up! It got here on Tuesday. I actually asked the seller to lower the base price, and the seller did!
When the drive got here, I realized that I didn't have any SCSI cables that would work. As such, I took the enclosure apart and removed the drive so that I could install it in the Tandy 1000 SX!
Being an external drive, there is actually a SCSI selector that connects to a "jumper" block. It does count up in binary (001, 010, 011, etc.). Basically the top 3 pins are the binary value of the ID (in reverse), and the bottom center pin always has continuity!
I did some testing on the drive, of course taking a picture of the connectors before removing it from the enclosure (yea, we are a little out of chronological order on the thread 😂). And it WORKED! More on that in a minute.
Since the drive worked, I went ahead and put it in the Tandy, and put the "old" Beta20I drive into the enclosure for safe keeping. Since the jumper block has that "binary" configuration, I went ahead and just taped the SCSI ID selector inside the Tandy 😂
On boot, we can see the Beta20Z drive is detected! What's the difference between this Beta20Z & the Beta20I drive? Maybe one was intended to be internal and the other external? No idea, documentation is really SCARCE! But it is nice to see the drivers detect it properly!
So, now, I started to REALLY explore a bit. I took an existing disk that I had run Scandisk on, and decided to take my chances using the Iomega SCSIUTIL and format it. And it worked!!
So, then I decided to run Scandisk again. And the bad blocks disappeared. Wait... what?? Okay, time to REALLY dig in and learn about this.
Some of you might have speculated what happened here: the Bernoulli disks have reserved tracks. And when we do a long format and verify, if there are enough spare blocks to take place of the bad blocks, they get replaced!
By the way, those screenshots about the bad block replacement process were taken from this manual about a 10MB 8 inch (Alpha) drive. Documentation is super scarce, I never found a similar manual for my 20MB 5 inch (Beta) drive. bitsavers.org/pdf/iomega/007…
So taking this into account, I have a few disks that are giving format "failures." Per what we learned above from the technical guide, these disks must have too many bad blocks sadly.
Something cool that you can do in the Iomega SCSIUTIL is see details about the disk, including disk life, Julian date of disk, etc. And.. .oh man, the first one I chose has a REALLY poor disk life. I chose another disk and it is much better!
So, the next question is: how many good and bad disks do we have? Of the ones I have tested, I have three bad disks (far right). Four disks are good (center), and the rest are untested (left, and second picture).
And since we are here, let's unwrap another disk and test it together. I'll run Scandisk, then we will format it, and we will go from there! See you in a few minutes 😅
Actually, I had a thought: let's get the disk info first. So, here it is! Looks like this disk was made in 1993, that's a newer disk! Disk life is 100%. Let's see if that changes in a bit.
Scandisk is running, and we have made it to the surface scan. Could this end up being my first error-free Bernoulli disk? Somehow I doubt it! 😂
Hahaha, no freaking way!! This is the first disk that has had zero bad blocks. Wow! It makes me want to try another, but I think I have unsealed enough disks already
Well, folks, with that, I am going to quit while I am ahead 😂. Thanks as always for following along, I am very glad that this story has a happy ending! And maybe for a future task, we will try to see if we can fix the bad disks, if it is even possible.
@threadreaderapp unroll
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Another successful operating system install on the IBM PS/2 Model 70 386 (with 486 upgrade and 16MB RAM). This time, it's Slackware 4.0. It's installed, networked, and we even have the graphical X server running! Let's talk about what it took in a 🧵 here.
So, basically what I decided to do is to use ZipSlack, which is a version of Slackware that you can just unzip to a system with a FAT16 or FAT32 partition! It's available as a folder on the Slackware 4.0 ISO, available here: slackware.cs.utah.edu/pub/slackware/…
Now, as people may recall, this PS/2 is a microchannel system. Fortunately, there is a microchannel kernel called ibmmca.s. I dragged the bzImage file over top of the vmlinuz file in the zipslack\linux folder to get this going! No, it didn't work 100%, more on that in a minute!
So, time to install another operating system on the PS/2 Model 70 386. This time, we are going with Windows/386 2.11. And as you can see from the screenshot below, we are multitasking like it's going out of style 🤣. Let's talk about the install in a 🧵 here!
First, I cheated a bit. I actually did the install in a virtual machine, and talked about some of the "fun" I had here, including issues with high memory area & MS LAN Manager. I had the same issues on the "real" system. You can read all about that here:
Anyway, install was pretty basic. Funny enough, Windows/386 asks what type of machine you have, but doesn't appear to do much with that information from what I have heard (unfortunately, I don't think I screenshotted that part of the install.. sorry!)
I spent some time toying around with Microsoft Windows/386 today (Version 2.11). I installed Word 1.1a and Excel 2.0, and also (using mTCP NetDrive) connected up to a network share! Here's a little video I did (sped up in several parts). I'll make some observations in a 🧵here.
First, when it comes to Windows 2.x, I am a total novice. I've never used it before today. I was actually surprised at how capable it is. But, I have to put the disclaimer that I may have missed some features or did some things wrong since this was my first usage of it!
Getting it running was an interesting exercise. You can use it with DOS versions greater than 4.x, but you have to load setver. And Win2.x loads into the HMA, so you better load DOS low! Here are my configs. You'll see that I also loaded up mTCP NetDrive for a network share.
I've got the FutureTel PrimeView NS 320 MPEG up and running on the CompUSA PC under Windows 2000! For reference, this PC is a Pentium II 350 MHz. I used some footage from The Great Outdoors to test things out capture a bit. Let's talk about it in a 🧵here!
So, first, thanks to the Wayback machine, I was able to locate the software for this card! Although it does target Windows NT, we will be installing Windows 2000 to try things out!
Using my boot manager BootIt, I carved out a Win2k partition and set up a Win2k boot option. I then set the BIOS to boot from CD, and we were off to the races.
So, yesterday, I mentioned that I wanted to move an MPEG capture card to my dual Pentium Pro system. Oh man, did I ever go down the rabbit hole! Let's just say that in the end, I didn't do it, and I ended up swapping out a network card too. Let's talk about it in a 🧵here
So, first, this dual Pentium Pro has multiple OSes on it, hence why my first screenshot is running Fedora Core 3. I like to have hardware in this system that is compatible with all of the OSes, because.. well.. why not!
And, second, this is NOT the first time I have had network card issues on this system. I used a PCI 3Com card in the past, and it had issues with drivers in SMP operating systems. I talk about it towards the end of this video for the interested