Skip to main content

Recover Deleted files from a FAT12 Floppy Disk

While cleaning and re-arranging a closet, I came across several boxes of ancient 1.44MB floppy disks, some of which were labeled indicating they contained pictures I had taken using a now-ancient Sony Mavica digital camera (which I still have). I also have a Mitsumi D353FUE USB floppy drive I purchased years ago when floppy drives became old-fashioned.

I wanted to save all the images to my hard drive, but what a labor-intensive task that started to be. The Mitsumi drive was showing a /dev/sdk (there are no partitions on a FAT12-formatted floppy disk), so I wrote a simple script.

# copy jpeg files from floppy disks

sudo mount /dev/sdk /home/hoyt/floppy

ls /home/hoyt/floppy && echo "NOW COPYING FILES"

sudo cp -p /home/hoyt/floppy/* 
/home/hoyt/OLD_PICTURES &&

sudo chmod +rw /home/hoyt/OLD_PICTURES/*

sudo umount /dev/sdk

rm -f /home/hoyt/OLD_PICTURES/*.411 && rm -f /home/hoyt/OLD_PICTURES/*.HTM

echo "NEXT DISK"

One feature of the Mavica camera was that the disk contained not only the original images, bit thumbnails of them (named as *.411) and an INDEX.HTM file for your browsing pleasure.  Those files were not needed by me and are deleted by the script.

At the end of the day, I had just over 600 images made more useful.

There were a few floppies that might have had images, but could not be read. These, it turned out, held images that had been deleted. To undelete them, I used testdisk, an application that can recover deleted files and more. There's a nice HOWTO here.

There are, of course, many disk, file and partition recovery and forensic tools available.

In case you are curious, it is easy to make an image file of a floppy disk using dd.

# dd -if=/dev/XXX -of=floppy.img

There are several alternate formats for the 3.5" floppy disk that seemed like black magic back in the halcyon days of 8086 processors and 256k RAM when adding a few bits of capacity to a floppy disk was useful.

There's an interesting site that discusses various disk formats and sizes and controllers. Back in the day, every manufacturer built different and non-compatible controllers and drives because there was no incentive to help the user migrate to a different computer. Notice that there used to be 8" floppy drives.

Of curse, with Linux it's possible to create a FAT12 floppy image from scratch, without the need for a physical device. These can be useful perhaps in booting some odd-ball virtual machine or just to amuse your self.

For creating disk images from scratch, you can always consult my book.


Popular posts from this blog

DOS4GW.EXE Version 2.01a and Alternative DOS Extenders

The TenberryDOS extender DOS4GW.EXE was used by many early DOS games. I still enjoy playing many of these games and DOS4GW.EXE is usable with DOSBox, so they can be played on Linux.

However, the version of DOS4GW.EXE that was included with the game was whatever was current at the time. The most recent version that includes many bugfixes that possibly affected the games when used with DOSBox have been fixed in the latest version, 2.01a.

It's not free at US$49, but you can downloaded it here. Simply substitute it for whatever version of DOS4GW.EXE your game provided and enjoy the bug-fixed goodness. Tenberry also makes a "high-performance" "pro" version of DOS4GW.EXE, but it costs $300. I think that they could sell quite a few of these to hobby users (since, you know, DOS is dead) for US$5.

Open Souce to the Rescue
There are better performing, free and Open Source alternatives available and worth a look.

DPMI Explained
But first, let's understand w…

Fixing a Buggy ACPI BIOS Updated for Windows 8 and Linux Kernel 3.x

In the BIOS, there is a table that configures/determines a number of hardware values for ACPI and your system to use.

One of the features of ACPI is that the values and methods used can be differentiated at boot time depending on what OS you run. Each version of MS Windows has a unique identifier and while Linux can identify as "Linux", the Linux ACPI gurus have decided that Linux will always identify itself as "Windows NT". Even if you force Linux to identify itself as Linux, the Linux ACPI code still lies to the BIOS, except for the computers specifically listed in drivers/acpi/blacklist.

If you are running very new hardware intended for Windows Vista or Windows 8, you might get better performance on ACPI-related issues if you identify, or "spoof", your Linux OS as Vista or Windows 8. This is done by adding the boot-time kernel parameter of acpi_osi="Windows 2006" or "Windows 2012" respectively (and the quotes are necessary). still,…


The first release of Mageia 1 is out. You can download it from here and read the release notes here.

If you've used Mandriva Linux, you'll feel right at home with Mageia. Mandriva has always had a reputation of working well for both the novice user and the power user. Installation is typically easy and hardware support is among the best of any distro. The user and administrative tools are comprehensive and easy to use. Of course, under the hood, it's all Linux and all configuration files are plain text files and all a competent administrator needs do is to choose a shell and a text editor.

Mandriva has also been known for excellent default fully-featured configurations of the KDE, GNOME, XFCE and LXDE desktop environments as well as a broad range of available applications. Mageia is no exception in this regard.

For the average user, the changes are mostly cosmetic. The Mageia art, colors and graphics are very well done (and contributed by the Mageia user community). But …