| Author |
Message |
|
Joined: 22 Oct 2008, 12:32 Posts: 1
|
 Centro memory card limitations
I bought a SanDisk 8 GB micro SDHC card for my centro. The salesman told me it would work even though my centro docs say I can use up to a 4 GB card. When I look at the card info on my centro it shows 3686.5 MG. Can I get the full benefit of this card on the centro or should I take it back and get a 4 GB card?
|
| 22 Oct 2008, 19:53 |
|
 |
|
Joined: 29 Jun 2004, 08:54 Posts: 97 Location: New Hope, MN
|
 oops
The salesman just didn't know what he was talking about. Palm's usually pretty good about stating the specs accurately.
|
| 23 Oct 2008, 10:06 |
|
 |
|
Joined: 01 Oct 2002, 07:30 Posts: 1274 Location: North Carolina
|
Palm OS Garnet basically has a limitation that causes it to only \"see\" 4GB (or less) volume sizes. So an 8gb card will be seen as two contiguous 4gig chunks. You'll still be able to access all of the data on the card but different apps (including Card Info) may behave differently.
So you CAN continue to use your 8gb microSDHC card, you'll just have to remember that if if you have ~5gb used on it, it'll just show ~1gb out of 4gb in use. If you'd rather not have any risk involved, just return it if you can and get a 4gb card instead.
The Windows Mobile powered Treo 800w and Pro have no such card capacity limitations, by the way.
_________________ Pilot 1000->Pilot 5000->PalmPilot Pro->IIIe->Vx->m505->T|T->T|T2->T|C->T|T3->T|T5->Zodiac 2->TX->Verizon Treo 700P->Verizon Treo 755p->?
|
| 23 Oct 2008, 19:58 |
|
 |
|
Guru
Joined: 17 Jan 2002, 06:18 Posts: 1999 Location: South West, VA
|
The limitation that hkklife referenced is a limitation in the design of the API and it affect the volume size and the free space queries. Basically any time any application asks the OS what the volume size is or what the free space available is, if the actual returned value should have been greater than 4G, it will return the remainder of the correct size divided by 4G. This is because both of these API entries return the results in bytes in a 32-bit unsigned integer. The maximum value that one can represent in a 32-bit unsigned integer is 4G.
I understand that there is a patch available from PalmPowerups that will change these two API entries such that if the return value should have been greater than 4G they will return 4G. This value still isn't correct, but at least programs are not likely to do the wrong thing which such a value.
|
| 24 Oct 2008, 07:29 |
|
 |
|
Joined: 20 Jan 2009, 00:31 Posts: 4
|
 Centro 4GB Limit - Problems with 8GB and TomTom 6 Navigation
I have a Palm Centro Rev A. (firmware 1.07) and used it with 4GB (A-Data Class 6) microSDHC card and TomTom 6 Navigation paired with Globalsat bluetooth GPC receiver. Everything worked perfectly. As soon as I upgraded to 8GB (Transcent Class 6) microSDHC card application is extremely slow (almost unusable!). As a test I copied all my files back to 4GB card and everything is fast again. I did try to defragment the 8GB and it is at 0% fragmentation and still TomTom is very slow (please note that I don't see any other application problems and was able to access all 8GB). Any ideas?
Thanks!
Gene
|
| 20 Jan 2009, 08:42 |
|
 |
|
Joined: 20 Jan 2009, 00:31 Posts: 4
|
 Centro 4GB Limit - Problems with 8GB and TomTom 6 Navigation
I have a Palm Centro Rev A. (firmware 1.07) and used it with 4GB (A-Data Class 6) microSDHC card and TomTom 6 Navigation paired with Globalsat bluetooth GPC receiver. Everything worked perfectly. As soon as I upgraded to 8GB (Transcent Class 6) microSDHC card application is extremely slow (almost unusable!). As a test I copied all my files back to 4GB card and everything is fast again. I did try to defragment the 8GB and it is at 0% fragmentation and still TomTom is very slow (please note that I don't see any other application problems and was able to access all 8GB). Any ideas?
Thanks!
Gene[/b]
|
| 20 Jan 2009, 08:44 |
|
 |
|
Joined: 20 Jan 2009, 00:31 Posts: 4
|
 Centro 4GB Limit - Problems with 8GB and TomTom 6 Navigation
I have a Palm Centro Rev A. (firmware 1.07) and used it with 4GB (A-Data Class 6) microSDHC card and TomTom 6 Navigation paired with Globalsat bluetooth GPC receiver. Everything worked perfectly. As soon as I upgraded to 8GB (Transcent Class 6) microSDHC card application is extremely slow (almost unusable!). As a test I copied all my files back to 4GB card and everything is fast again. I did try to defragment the 8GB and it is at 0% fragmentation and still TomTom is very slow (please note that I don't see any other application problems and was able to access all 8GB). Any ideas?
Thanks!
Gene
|
| 20 Jan 2009, 08:45 |
|
 |
|
Joined: 20 Jan 2009, 00:31 Posts: 4
|
 Sorry for multiple posts
I was getting an error \"Invalid User\" and didn't realize that my posts went through. Maybe someone from Palm Infocenter can fix the posting bug????
Thanks,
Gene
|
| 20 Jan 2009, 08:49 |
|
 |
|
Guru
Joined: 17 Jan 2002, 06:18 Posts: 1999 Location: South West, VA
|
Re: Card issue.
I have heard, but do not have direct experience, that this is due to a poorly written FAT32 driver under Palm OS, that is does get slower with larger cards. This can be minimized by reformatting the card with smaller cluster sizes. Alas the Format on the Palm does not let one select the cluster size, so one has to do it from a desktop.
Re: Posting error.
Yeah, I've seen that error a lot here lately. I have taken to, when I see an error, double check to see if what I was trying to do happened anyways before trying again.
|
| 20 Jan 2009, 20:26 |
|
 |
|
Joined: 24 Sep 2009, 17:58 Posts: 2
|
 Re: Centro memory card limitations
Same problem w/ slow TomTom on an 8GB Class 6 SDHC. Nothing really to add. Just getting the thread in case someone finds a solution. 
|
| 24 Sep 2009, 18:09 |
|
 |
|
Joined: 24 Sep 2009, 17:58 Posts: 2
|
 Re: Centro memory card limitations
Nevermind. I reformatted my card using the command "format X: /FS:FAT32 /A:16K" and that did the trick. Another good thread on this here: http://discussion.treocentral.com/treo- ... 0-a-2.htmlBTW, turns out the default cluster size for Fat32 on my 8GB card was 4k, and that the 16k cluster size helped speed up TomTom considerably. So the issue seems to be that the default cluster size is too small, not too large.
|
| 24 Sep 2009, 19:14 |
|
|