Would just like to let you, and everyone know that your solution worked
perfectly. After trying many times on a windows box (with
physdiskwrite, and DD after extraction on a Linux box), I used SLAX
instead. My 20MB Sans CF card works perfectly now. I was unable to get
my 96MB Simple Tech card to work at all, even though I can see it in
windows, format it, and write to it. It simply will not boot, even
using the SLAX method. While I think your method is the way to go (it
obviously works better than any of the windows utilities), it appears
not all cards will work no matter what you do.
Aaron Robinson wrote:
> On Mar 3, 2004, at 11:06 PM, <EXT dash Mike dot Bradshaw at nokia dot com> wrote:
>> The continuing saga of attempting to get this Verbatim 32M CF card to
>> Due to having NO current working Un*x boxes, everything has been done
>> on MS Windows.
>> what i tried last night:
> One suggestion that I would give is to use a bootable livecd (if you
> want a gui) or a floppy distribution (which I have not explored yet).
> You don't have to touch your windows installation and it's a quick and
> easy way to keep a linux distribution around.
> I used slax from http://slax.linux-live.org/ and it worked just fine
> once once I got over some human typing error. It boots just fine and
> gives me a linux machine without having to install it to my HD.
> Once it's was booted, just type...
> gunzip -c wrap-1.0.img | dd of=/dev/<your flash device here> bs=16k
> For figuring out what device it is, you might find the e-mail below
> written by Jim Gifford of use...
> Oh, and I am using 20MB Sandisks in a linnix.com (cheap, functional)
> CF IDE adapter.
> I hope this is helpful,
>> Is your CF-IDE adapter on the primary or secondary bus, master or slave?
>> The first thing you have to do is make sure the CF card is being seen by
>> your linux machine before you can write to it.
>> Try using hdparm -i on the devices /dev/hda, /dev/hdb, /dev/hdc, and
>> /dev/hdd and look for the drive information that matches your CF. Then
>> use that device name for your dd command. You can also do
>> 'dmesg | grep hd' and look for your CF media in that output. If you
>> don't find it this way, it isn't being recognized.
>> You won't need to blank the media, as dd does a direct write to the
>> hope this helps,