Dalexan
asked on
CF adapter not able to format compactflash
I have a PCMCIA compact flash memory adapter "CompUSA brand". When I try to format the compact flash using xp pro I get an error message:
commands I used:
format e:
format e: /u /fs:fat32
format e: /u /fs:fat
error:
Cannot determine the number of sectors on this volume
Is this an issue with my laptop where it does not support ATA Type PC Cards? I have confirmed my CF card works in my camera.
commands I used:
format e:
format e: /u /fs:fat32
format e: /u /fs:fat
error:
Cannot determine the number of sectors on this volume
Is this an issue with my laptop where it does not support ATA Type PC Cards? I have confirmed my CF card works in my camera.
These little cards come with some real compatability problems. You should be able to format the card on your camera if it works there. Will the laptop read the card ok?
Jerry
Jerry
ASKER
I can format the card in the camera since I can take pictures. I have called compusa customer service and they were able to tell me that the pcmcia adapter card is no longer supported.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have the kingston USB adapter now, it works perfectly. Thanks. PCMCIA is not the way to go.
Dalexan,
Glad I could help!!!
Thanks for the points,
Jerry
Glad I could help!!!
Thanks for the points,
Jerry
I did some experimenting involving a CF card in a PCMCIA adapter on a w2k system. No protests whatsoever when formatting from either the disk manager or the command prompt (except usual warnings about losing data). This is a pretty old P II system. I kinda doubt your problem is with your laptop; I'd guess the drivers for the adaptor or somehting, perhaps even win XP, can be giving you trouble here. Have you installed any special drivers for this setup or are you using O/S generic drivers?
One thing I couldn't do, however, was to remove the partition on the CF card. This could be done in Linux, though. Seems unrelated, I know, but serves to show that the hardware is probably not the culprit here; more probabaly it is software-related (OS, drivers, other programs/processes involved and interfering)
regards
/RID