There’s a good chance you know this device already. It’s a floppy disk emulator. Here’s how it is supposed to work: you take a well-organized, homogeneous group of disk image files, tell the software to bulk-convert the images to .HFE format, move them to a SD card, plug the SD card into the emulator device, and plug the device into the computer. And in theory it is pretty much that simple. Here’s an idea of what it looks like:

First is the hardware kit:

And here it is connected to a computer, loading a game (first browsing for the directory, then selecting a file in the directory, and finally actually loading the disk image):

It keeps track of the current drive (it supports up to two drives simultaneously), the current operation (R)ead or (W)rite, the current track, the total number of tracks, and the side of the disk being accessed (0 or 1). Here it is in action, loading Galaga from system bootup.

And there you have it, Galaga is ready to go!

But here’s my story about prepping a batch of X1 images to work on the HxC emulator. Learn from my mistake; don’t do it the way I did it the first time!

A while ago, I had images for about 180 games to process, some with multiple disks, for my Sharp X1 Turbo Z. I was given a mish-mash of .2D and .D88 files to work through. As D88 is a supported format by the HxC conversion software, I was able to conveniently bulk-convert to HFE, everything worked ultra-smooth with those files. Cool!

.2D, on the other hand, was a nightmare. The only converter from .2D to .D88 that I could locate was an ancient command-line tool that Windows 10 won’t even touch. I set up Windows XP on my machine via VirtualBox, but that was where the tedium began. I had to rename files to meet 8.3 standards and manually make a batch file that processes each file independently (no batch mode on the converter). Then move everything back to the non-virtual machine and convert *those* files and, in some cases, merge them with the files that were already in .D88 format, and usually rename them back to long filename standards.

But I powered through it. It was like 100 games that were in .2D format and it wasn’t worth asking for help regarding a better way to do it, and waiting for answers.

A few months later, I found a much bigger collection, about 900 images! And it was again a mish-mash of the two formats. I had a lot more motivation to ask for help this time!

The creator of the HxC floppy emulator is very helpful and active on his Facebook group. He answered me within a couple of hours, asked for an example .2D file, and showed me that I could set up the converter software to treat .2D files as raw files, by setting the correct disk parameters.

Unfortunately, even with this solution, I still can’t bulk-convert in one big batch, because the software doesn’t handle raw images and prepared format images simultaneously. But it did save me the whole process of renaming, moving to virtual machine, creating the batch file, moving back to the host machine, and reverting the names. So although it was about five times the number of images, I finished in less total time!

If you find yourself in this situation, here are the steps you need to follow to use .2D files as raw. First window, click “Batch converter”. Second window, check “Treat input files as RAW files.” Third window contains the parameters you need to set for the conversion to work correctly. Now when you select a directory of .2D files to bulk-convert, it should output an identical directory structure with .HFE files!

As some games or collections have a mixture of .2D and .D88 files, the most confusing step is to separate those and convert separately, then putting them back in the same directory once they’re in .HFE format. It’s also a good idea to use your favorite file rename utility so you don’t have massively long filenames, because the device screen can only display 16 characters at a time. My recommendation (although this is a fair bit more manual) is to make a directory with the game name, but inside the directory simply call the files disk1.hfe, disk2.hfe, etc.