One of the more popular videos on my YouTube channel is a tutorial on how to prepare a bootable CF card for a retro install (DOS/Win95, etc.). My video procedure uses VirtualBox 5.2.44, but I know a lot of people use VirtualBox 7.x. Let's make a 🧵on how to use that instead!
First, if you'd rather watch a video on how to do this, see here! Even though I use VirtualBox 5.2.44, all of the commands are essentially the same. You might reference this thread if you want to use the more "modern" commands or for subtle differences:
As for a CF card reader/writer, I'll be using this cheapo $3 one I found on eBay a while back. It's worse for the wear, but it works. And for a host operating system, I'll be using Windows 10. Hopefully Windows 11 is similar.
To get started, if you don't already have VirtualBox 7 installed, go ahead and download and install it. The website where you can find it is virtualbox.org/wiki/Downloads
Once installed, you are going to want to launch a command prompt in administrator mode (yes, this will be different in Windows 11, sorry!). To do that on Windows 10, launch the start menu, type "cmd", then right click on "Command Prompt" and click "Run as administrator"
Now, plug in the CF card and reader/writer to your computer. After doing that, run the following command: wmic diskdrive list brief
You should see your CF card in the list. BE CAREFUL, you will want to get this right. I know my CF card is 4GB and is PHYSICALDRIVE1. Good.
Next up, change to the Oracle VM VirtualBox directory: cd "\Program Files\Oracle\Virtualbox"
Then we can create a VMDK file that we can use to mount the CF card in VirtualBox! You'll use the PHYSICALDRIVE from the previous command, and choose a location to put the VMDK file...
In my case, we use PHYSICALDRIVE1 and I am just going to create the image as a file called D:\cfcard.vmdk. For you, it may be a different PHYSICALDRIVE and you might want to store the image elsewhere. The image file will be small, it is just a "passthrough" to the real CF card.
Next up, still in the administrator command prompt and still in the VirtualBox directory, launch VirtualBox by typing VirtualBox.exe. We need to run this as an administrator so that the CF card will mount properly.
In VirtualBox, click "New" to create a new VM. Name it "DOS". Default hardware settings are fine, just click "Next". For Virtual Hard Disk, choose "Use an Existing Virtual Hard Disk" and select your CF card file that you created above!
If all done correctly, your summary screen should look like this!
Next, I am going to set up a DOS 6.22 FAT16 partition. If you want to install Windows 95B or later, you can create a FAT32 partition, but the concept will be similar. I went to and downloaded a DOS 6.22 floppy boot image (they also have Win95 boot disks) allbootdisks.com
There are a few ways to set up the boot disk. I am just going to click on Settings, then Storage, then click on the "Empty" floppy, then Attributes to choose a disk file, and the choose my downloaded DOS 6.22 image. Piece of cake, right?
Okay, now it's time for the moment we have all been waiting for: let's fire up the virtual machine by clicking Start.
One started up, launch the "fdisk" program. Select "1" to create a DOS partition or Logical DOS drive. Then "1" for Primary DOS partition. And then "Y" to make the partition active.
But...wait, Chris! My CF card already has a partition on it, and I can't create a partition, what do I do? Go ahead and close VirtualBox, go back to the start menu, and type "create and format hard disk partitions." Proceed to find all partitions on the CF card and delete them!
So, back on track, once you create a partition, the VM will prompt for restart. Go ahead and do that.
Once restarted, run a "fdisk /mbr" for good measure to rewrite your master boot record.
Then let's format the disk with a "format C: /s" to make the CF card bootable!
At this point, let's boot from the card. But first, we need to remove that bootable floppy disk image from the disk drive. Go to "Devices", then "Floppy Drives" then "Remove disk from virtual drive."
After doing that, go to "Machine" and then "Reset" to restart the VM.
With a little luck, you should be greeted with a DOS startup! If not, oh well, at least we tried! Reach out to me and I will try to help as time permits.
At this point, perhaps you want to copy over some programs or installers, etc. Doing this is really a cinch. Go ahead and close VirtualBox (shut down the VM first), and from there, you can use Windows Explorer to copy files to the CF card!
Okay, great! So with this, we are all set. But I do want to share one caveat: what if you want to start up VirtualBox again and do something with the CF card you have created? Well, unfortunately, Windows will lock the volume, and you won't be able to write to the CF card...
Can we fix this? Absolutely. There is a great utility called xclusive that will do just that for you. Navigate to . Download dskacl-1_0_0-i386.cab. Open it up, and pull out the xclusive COM file that you see. Put it somewhere where you can run it. kaufmann.no/roland/dskacl/
In my case, I put the xclusive COM file on drive D:
So, once again, we are going to run VirtualBox in an administrator command prompt window, but w/ xclusive. You will need to know the drive letter that Windows assigned to the CF card, for me, drive H:
Sample command below.
Okay, and with that, we can now make changes to the CF card once again. I hope that SOMEONE finds this tutorial useful, if not, well, at least I tried 😂. Thanks for following along!!
@threadreaderapp unroll
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Back in the day, I was oddly fascinated with the different types of DOS GUIs... and which applications seemingly had similar ones! I thought I'd take a few minutes and look at three different styles of DOS GUIs from the past, I am sure it will bring back memories for you too! 🧵
First of all, I have to give credit to this Reddit post, which was the inspiration for my post. Lots of great discussion over there, and I will borrow some of it for here! reddit.com/r/DOS/comments…
So, I'm going to start out with TurboVision, a framework included w/ Borland Pascal, Turbo Pascal, and Borland C++. Some of the programs I recognize that use it are Novell apps and one of my favorite files transfer programs, FastLynx. Note the title and "blocky" background.
Time for another "Operating System" install on the PS/2 Model 70 386 (with 16MB memory and a 486 upgrade). This time, we went with DESQview/X, which actually isn't an OS since it runs on top of DOS. But it has some cool features! Let's talk about it in a 🧵 here!
So, first, to do the install, I was once again lazy. I installed DESQview/X in a virtual machine, and then copied the contents to the PS/2. Installation is straightforward, just make sure to have FILES=20 (or more) in config.sys! I'll show some screenshots from the install.
After installing, an optimize program runs and reboots the system several times to find the optimal memory usage. This reminds me of memmaker in MS-DOS 6.x. Gee, I wonder which came first 😂 (hint: it probably wasn't memmaker!)
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!
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!
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.