Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: motorollin on September 16, 2008, 06:39:10 PM
-
I've got a 4GB CF card in a PCMCIA reader. I've got compactflash.device in DEVS:, fat95 in L: and CF0 in DEVS:DOSDrivers. When I mounted the device, I saw CF0:NDOS on Workbench. I formatted it, and the format hung on "initialising". So I took it out and formatted it on a Windows machine, which worked. But it wouldn't show up on the Amiga - it said no disk was inserted. I did a zero fill on the drive and it is now showing up as NDOS again, so I just wanted to check the best way to format it to make sure it works.
TIA
--
moto
-
Have you formated the drive as from Windows as Fat32 instead of NTFS which is the default?
-
Yes it was formatted as FAT32, but I think formatting it on the Amiga borked it. Is it best to format it on a Windows machine before use on the Amiga?
--
moto
-
Ok, after zero-filling the CF card I connected it to the Amiga and it showed up as NDOS. I then took it out and plugged it in to a USB CF reader and plugged that in to an XP machine. I formatted the partition as FAT32, and then when I connected it to the Amiga it once again said that no disk was inserted :-(
--
moto
-
Try formatting it as standard FAT and not FAT32
-
Just tried it as FAT rather than FAT32 and had the same problem - it doesn't recognise that a disk is inserted :-( Could it be that the card is incompatible?
--
moto
-
Ok, after zero-filling the CF card
If you format the CF card like a floppy disk, then Fat95 needs the exact geometry to be specified in its DosDriver (CF0 in your case), otherwise it will not detect the file system.
Fat95's automatic geometry recognistion does only works if the disk is partitioned (i.e. contains an MBR created by FDisk or the like).
I am not sure if you can partition a CF card with Windows' disk management. You probably have to fire up Linux and run its FDisk.
Whatever you do, you should first read Fat95's documentation. There is a lot of information in it. Especially note the section about the DosType and partition recognition.
Bye,
Thomas
-
Thomas wrote:
If you format the CF card like a floppy disk, then Fat95 needs the exact geometry to be specified in its DosDriver (CF0 in your case), otherwise it will not detect the file system.
Ahh, so is that why it thinks no disk is inserted?
Thomas wrote:
Fat95's automatic geometry recognistion does only works if the disk is partitioned (i.e. contains an MBR created by FDisk or the like).
I am not sure if you can partition a CF card with Windows' disk management. You probably have to fire up Linux and run its FDisk.
Will Linux's FDisk allow me to create an MBR?
--
moto
-
I have the same problem with a 4 GB CF card from A-data and Sandisk. The problem lies with the filesystem. The Compactflash disk driver only use Fat 16. Fat 16 has a limit of 2 GB and Fat 32 can cope 4 GB and above.
In other words. You can only use 2 GB CF cards with this driver.
-
But I thought Fat95 supported FAT32?
--
moto
-
Well I'm assuming it was either the size of the card or the type of card. I swapped the 128MB card I had internally with the 4GB one I was trying to use in the PCMCIA adapter and the 128MB one, formatted on a Windows machine as FAT, worked fine with Fat95.
I have now got another problem which is that the 4GB card, now installed internally with Workbench 3.1 on it, is complaining of checksum errors. The boot partition is just over 500MB (about 509) and the next partition is just over 2000MB. The rest of the card is unused, so I'm fairly sure I have followed the rules for partition layout in 3.1. Can anyone confirm this? I'm using FFS.
--
moto
-
Reduce MaxTransfer for all partitions to 0xfe00.
Bye,
Thomas
-
AFAIK Fat is limited to 2GB max per partition. That's why the small CF works just fine and the slightly over 2GB partition isn't working
-
Thomas wrote:
Reduce MaxTransfer for all partitions to 0xfe00.
Thank you, I will try this when I get home. Do I need to delete the partition and re-create it, or is it good enough to change the MaxTransfer value and re-format the partition?
--
moto
-
mfilos wrote:
AFAIK Fat is limited to 2GB max per partition. That's why the small CF works just fine and the slightly over 2GB partition isn't working
I have checked the Fat95 documentation and as far as I can tell it does support FAT32. The 4GB card did not work even when formatted as FAT32.
The problem with the partition which is just over 2GB is not related to the FAT95 problem as that partition was used on the internal IDE interface and formatted as FFS. Hopefully Thomas is correct and this can be easily fixed by changing the MaxTransfer value.
--
moto
-
Could it be the FIXED / REMOVABLE attribute that CF cards can have?
Ones which appear as REMOVABLE are not well supported. SanDisk cards can be changed between FIXED and REMOVABLE in software.
I had lots of problems with data corruption on my CF cards. I had put it down to fake CF cards but I'll have to see if this MAX TRANSFER thing will fix it.
-
I have heard about the fixed/removable attributes of CF cards before and was a bit worried that this was the case here, since changing the MaxTransfer rate didn't solver the problem. However, I swapped the card for a Transcend 4GB card and it seems to be working perfectly.
The card I was using before was not actually a CF card. It was a Sony MS Pro Duo in a MSPD -> CF adapter. This same combo refused to work in my EFIKA, so I assume it's not quite compatible enough.
--
moto