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
I got a new accessory for my Pocket 386 today! Let's talk about it briefly in a 🧵 here!
So, the majority of Pocket 386 systems were bundled with a serial port, I believe. I was an early adopter though, so mine didn't have one. We remedied that today! I also had a nice 3D enclosure to put the serial connector in. Looking good!
Installation was a snap...literally... and four screws to hold in the card.
I decided to reinstall Windows XP Embedded on my HP T5700 thin client today. This is a pretty versatile little system, let's have a look at some of its unique charm in a 🧵 here!
First of all, I actually have a YouTube video that I made a few years back that goes over the entire install process in detail. And yes, I did rewatch it today to remember what I needed to do 😂. Sometimes we are our own best resource I guess!
Following the process, I made a bootable USB drive. I kicked off the imager, and rebooted. The installer did the rest!
I thought I'd try booting from Zip 100 disks today. I gave it a shot with an internal ATAPI drive, and also tried an external SCSI zip drive. Let's talk about how it worked out in a 🧵 here!
We'll start with the ATAPI drive. The first thing I did was go into the BIOS and add my "ZIP100" drive to the boot list. Easy peasy.
From there, since I had trouble with DOS 6.22 and bootable zips in the past, I went into Windows 98 and use the "sys" command to make the disk bootable. Yet, oddly, it was hanging on boot. Weird. Surely this should have worked!
Looks like a new PicoGUS firmware was released last month that has built-in WiFi support! Time for me to update the PicoGUS Femto on my Pocket 386 with the latest and greatest, and we'll do so in a 🧵 here!
So, first, I have actually been running a WiFi "developer" firmware build for quite some time, since around April 2024 or so. I put together a procedure on how to build and update the firmware at the time. You actually had to hardcode your SSID and password back then!
For the curious, the release notes for the firmware we are using can be found here (you'll see which versions of PicoGUS can support this firmware and the caveats. My device supports it and I am most interested in WiFi capability, so this works for me): github.com/polpo/picogus/…
We're going to reach "Productivity Level 1000" in Windows 3.11 for Workgroups with this newly-developed
Win3.1 video driver, now running on my eMachines T2341. Let's talk about it in a 🧵 here!
So, for starters, I learned about this driver today, and tried it in virtualization. I wanted to try it on real hardware too!
To get things started, I booted Windows 98 to see what the "max" video resolution would be for this card. And it looks to be 1600x1200. Okay! So, I set the parameters accordingly using the same manner discussed in my earlier thread.
Let's take a few minutes and look at this newly written Modern Generic SVGA driver for Windows 3.1. We'll check it out in Oracle VM Virtualbox 5.2.44 first in a 🧵 here (I do plan to try real hardware next!)
First, I will say this is off to a GREAT start. The author has done a nice job at logging some of the issues that are present... and this driver has A LOT of promise!
Installation is pretty easy! Copy over vbesvga.drv and vbevdd.386 that you can download from the releases page of the project to your windows\system directory: github.com/PluMGMK/vbesvg…