well ... just tried with the -tmsdos flag ... no go. It still hangs after 
the "wd1: no disk label" msg.

wait ... I just checked fdisk /dev/wd1

And this is the output:

pcmcia1: card irq 3
wd1: no disk label
Disk: /dev/wd1d <--- 1d instead of 1a or 1e!! ok ... let me try this ... ;)
....

"Snappy!" <direct2system@yahoo.com> wrote in message 
news:cu0vao$edi$1@sea.gmane.org...
> hi all,
>
> I just tried this.
>
> # mkdir 512mb
> # mount /dev/wd1a /512mb
> pcmcia1: card irq 3
> wd1: no disk label
> mount: cannot open `/dev/wd1a': Device not configured
>
> So I figured maybe the CF msdos partition is not on wd1a. I tried wd1e 
> instead:
>
> # mount /dev/wd1e /512mb
> pcmcia1: card irq 3
> pcmcia1: card irq 3
> wd1: no disk label
>
> then the system hangs. I will try again with the -tmsdos flag to 
> explicitly force msdos type. Will update new results later. Anyone with 
> any idea, please let me know ya? Thx!
>
> -Robin
>
>
>
> "Matt Dainty" <matt@bodgit-n-scarper.com> wrote in message 
> news:20050204171222.GB19383@gelf.bodgit-n-scarper.com...
>>* Snappy! <direct2system@yahoo.com> [2005-02-04 16:51:24]:
>>> ya ... the thingie about disklabel is wrecking!! ... when I try to use
>>> disklabel on this 2nd CF card, will it wipe out its data? In any case, 
>>> the
>>> command keep giving me a unknown/invalid type error.
>>
>> You shouldn't need to put a disklabel on there, just try and mount
>> /dev/wd1e or /dev/wd0e as msdos format, or is that what you're trying?
>>
>> Matt
>> -- 
>> "I know it's your T1 because our network guy teleported into the Baywatch
>> hub and checked it!"
>> "It's 'telnet' and 'Bay Networks'."
>>
>
>
>
>