I am not sure what you think who you are. I remember you describing that you left the Amiga scene long ago and returned only recently. Since you returned you try to give advice to other users. But many if not all of your posts give a feeling that you never had an in-depth knowledge about the inner workings of AmigaOS and surely you missed all the developments which were made while you were off. You talk in headlines like "Kick 3.1 cannot access partitions larger than 2GB". This sentence is cut out of its context and by itself plain wrong. You never explain why you think that certain circumstances would explain the symptoms. Like in this case you just assume that a 2GB limit (which does not exist) could be the cause of the problem. But if a partition size limit would be a problem, the symptoms would be different. Also you do not investigate the problem systematically, you rather start at the wrong end and tell the user to destroy the product he bought as in working condition. He paid money for it and you tell him to destroy it.
The user has all the software he needs
compactflash.device
fat95
cf0
It's a matter of copying each file to the right place on the Workbench disk. If it still does not work, there are ways to find out more before you start destructive actions. Yes, I agree it is difficult if you cannot get additional software from the internet. But there are some possible things to do.
For example the PrepCard utility should display the vendor and product names of the CF card. If it doesn't, the card is not plugged in correctly.
I am not sure but I think HDToolbox should show the size of the card regardless of its partitioning and format. If this does not work, it's worthless to continue.
If all that works we can check if the needed files are indeed in their required locations. "CF0 is already mounted" is a good start. But it only means that AmigaDOS knows the name CF0. It does not mean that it found all the required files.
In a shell window if you try to access CF0:, the error message should give more clues.
I am writing this from memory, but I think if you access CF0: and nothing happens, it means that FAT95 was not found in L:. If it says "invalid whole number" or so, then FAT95 was found but it could not access compactflash.device. If the message is "no disk in drive" it might be that the card is not plugged in correctly. Only if the message is "not a DOS disk", only then I would perhaps agree that there is something wrong with the contents of the CF card (partitioning, format). But if it works on the PC's card reader, it's unlikely.
