Compact flash disk image with dd and cygwin

I found a way to make an exact duplicate of a compact flash card using cygwin. I suspect this method only works with identical flash cards - i.e. both the same capacity, and possibly both from the same manufacturer.
Anyhow, based on Reimaging CompactFlash cards tutorial, I looked in Computer Management, Disk Manager, and discovered my compact flash card was 'disk 2'
Then, using 'a' for disk 0, and 'c' for disk 2, at the cygwin command prompt:
dd if=/dev/sdc of=b2.img
It reports this, for a 32Mb flash card:
62592+0 records in
62592+0 records out
32047104 bytes (32 MB) copied, 10.725 s, 3.0 MB/s
Then, 'eject' the flash card in explorer, and insert the new one (to be erased and copied over). In cygwin again, note 'if' and 'of' swap:
dd of=/dev/sdc if=b2.img
62592+0 records in
62592+0 records out
32047104 bytes (32 MB) copied, 43.448 s, 738 kB/s

And it works! It's even bootable.
I'm still puzzled by a cygwin list suggestion, which has weird syntax for mounting the drive first. I tried it, and I got 'permission denied' when trying to write the image to the card, too. I think you want to treat it as a device, not a drive.

Update: I am able to copy the disk image onto a larger CF card, and all the data is preserved, but the CF is not bootable. An exact duplicate read from a 32Mb card and copied to a 32Mb card is bootable.

To fix that, I downloaded the latest syslinux, looked in the win32 subdirectory, and then ran this command (in cygwin), since my CF is the F: drive:
syslinux.exe -m -a f:
I also discovered that simply copying all the files, and then run the syslinux command above to make the CF bootable, works just fine too.

One more thing. The older version of syslinux allows 'append=' in syslinux.cfg, but the newer version doesn't like the '=' sign. Once I changed all occurences to 'append', it booted correctly. The older syslinux likes that format, too.

Comments

Post a Comment

Popular posts from this blog

Inno Setup custom data directory location

In my last post , I forgot to point you to Inno Setup ; go get the Inno Setup QuickStart Pack to get going. I showed how to copy a directory full of data, like tutorials or sample data, that might change depending on the customer. That means the files are not known when the installer is compiled. Here's what it looked like: Source: {src}\data\*; DestDir: C:\MyCompany\data;    Flags: external recursesubdirs skipifsourcedoesntexist onlyifdoesntexist uninsneveruninstall;    Permissions: users-modify This time, I 'm going to show how to let the user choose where this directory is located, and whether to install the contents of the directory at all. First, let's show an obvious choice: Source: {src}\data\*; DestDir: {userdocs} \MyCompany\data; Flags: [as above.... ] That new constant will put the data in a subdirectory of My Documents, for the user that installs the program. This might be fine for you, if each user of your program is going to install it the...
Read more

OpenEmbedded Angstrom for Advantech PCM-9375

I'm attempting to install a modern embedded linux OS on a 3.5" single-board computer (SBC), made by Advantech, the PCM-9375. It uses an AMD Geode processor, and has lots of connectors, but the main one we need is the PC/104 connector, because we have a PC/104 board for a laser rangefinder we use. After some investigation, I found that Cliff Blake at BEC systems has successfully used OpenEmbedded and the Anstrom distribution on this SBC. I'm going to attempt the same thing myself, then go beg for help. :) First, I upgraded my box to Ubuntu Hardy Heron, 8.04 Next, follow the Anstrom build page : Get bitbake and OpenEmbedded I look at the GettingStarted wiki page , and it points to OE and your Distro , which says make sure Dash is not /bin/sh. It was on my system, so I did: " sudo dpkg-reconfigure dash " and select No when it asks you to install dash as /bin/sh. as instructed. Next install a bunch of stuff. I checked these off in System .. Administration .. Synaptic...
Read more

Inno Setup MSVC vcredist without bothering your users

If your C++ program is compiled with MS Visual Studio 2005 Express, and you link with the DLL versions of the C run-time libraries, you probably already know that you have to run vcredist_x86.exe to install those dependencies on a new computer before your program will run. Here's how to do that in an Inno Setup script. First, download vcredist_x86.exe from MSDN, Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) Notice that's for SP1, the instructions are different for non-SP1, and for the vcredist_x86.exe that comes with Visual Studio Standard or Professional. See the credit link below. Include this in your script: [Files] Source: {src}\bin\vcredist_x86.exe; DestDir: {app}\bin\; [Run] Filename: {app}\bin\vcredist_x86.exe; Parameters: "/q:a /c:""VCREDI~3.EXE /q:a /c:""""msiexec /i vcredist.msi /qn"""" """; WorkingDir: {app}\bin; StatusMsg: Installing CRT... Alternative for x64 ( I hav...
Read more