Page 1 of 3 123 LastLast
Results 1 to 20 of 52
  1.    #1  
    I've seen mentions here and there of a particular brand of 4GB SD card failing to work with a custom rom, but I haven't been able to find a comprehensive list. I thought I'd start the thread, get some input, and hopefully come up with a new resource to go on the stickies list. As new replies are added, I will add the cards to this first post to keep a single comprehensive list.

    Also, since this information is buried dep in other threads: the Palm FAT32 system operates much faster with larger allocation blocks. The default chunk size is 4k. FAT16 (FATFS.prc) operates well at that size, but FAT32.prc slows down noticibly. When formatting from a command line in Windows, use the following line:

    format DRIVE: /FS:FAT32 /A:BLOCKSIZE
    For a 4GB card, 32k is the largest chunk;
    for a 2GB card, 16k is the maximum.
    I hypothesize 1GB maxes at 8k, but I don't think we've seen that tested yet.

    And now for the meat: cards marked with an asterisk(*) have been confirmed by multiple users.

    Works:
    *Transcend 4GB
    *A-DATA 4GB
    Patriot
    RiData
    OCZ

    Does not work:
    DANE-ELEC 4GB
    PQi 4GB
    Bluememo 4GB
    Last edited by supersocialist; 10/08/2006 at 12:29 PM. Reason: Updating list.
  2. #2  
    Personal Experience FAT32.prc w/ Treo 650 (Cingular)

    Works:
    Transcend 4GB


    Doesn't work:
    DANE-ELEC 4GB
    Last edited by wagadesa; 09/01/2006 at 11:34 PM. Reason: view was muttled
    Visor Phone, Treo 180, Treo 270, Nokia 3650, Treo 650, Treo 680, Treo 800w
  3. #3  
    transcend 4 gig is working for me.

    Fred
  4. #4  
    My A-DATA 4 Gig Card (150x) works great.
  5.    #5  
    Quote Originally Posted by BNickO View Post
    My A-DATA 4 Gig Card (150x) works great.
    Man am I glad to hear that... I just ordered one!
  6. #6  
    I returned a PQi card. My A-data also works great.
  7. #7  
    My Patriot 4GB card works great
  8. #8  
    No problems with my RiData (150x) card!
    Handspring Prism ---> PalmOne Treo650
  9.    #9  
    Quote Originally Posted by rinkeedink View Post
    I returned a PQi card. My A-data also works great.
    Do you know if the PQi was a bad card, or bad brand? Did you try more than one?
  10. hopatz's Avatar
    Posts
    24 Posts
    Global Posts
    25 Global Posts
    #10  
    Bluememo 4gb not work with my treo 650 even using fat32.prc..
  11. #11  
    No problems with my A-data card (knock on plastic)
    Pilot 5K->Palm IIIc->Tungsten T/T2->Treo 650/680 -> Pre+ (1.4.5 & Uberkernel)
  12. #12  
    I have a problem with the Adata 4GB when using the camcorder, cannot write to it. Problem solved after reading the forums by filling up the card with more than 2GB of stuff and 32K cluster format.
    Dark Lord of the Sith...
    Fear is My Ally...

    http://www.ppcsg.com
    http://www.spug.net
  13.    #13  
    Quote Originally Posted by Ddeath View Post
    I have a problem with the Adata 4GB when using the camcorder, cannot write to it. Problem solved after reading the forums by filling up the card with more than 2GB of stuff and 32K cluster format.
    It's my understanding this is a problem with FAT32, not ADATA specifically.
  14. #14  
    format E: /FS:FAT32 /A:32K doesn't work for me, it says that "specified cluster size is too big for FAT32". Eh????
    (PowerPlay Vs) >> palmOne Zire 31 >>
    (palm Tungsten T3)/(palmOne Zire 72s) >> (palm Black Tie Trēo 650 Custom)/
    (palmOne LifeDrive Custom [SanDisk Ultra II CF])/(palm m515)/(palm T|X)
    handspring Visor Deluxe/Tapwave Zodiac 2/palm Trēo 680 Copper Orange


    Canuck PDA
  15.    #15  
    Quote Originally Posted by +Kardboard+ View Post
    format E: /FS:FAT32 /A:32K doesn't work for me, it says that "specified cluster size is too big for FAT32". Eh????
    Very interesting. I just tried this with a 128mb card and got the same error, but it definitely worked with my 4 gig card. I'll have to putz around with this when I've got more time.
  16. #16  
    Yeah, thanks. It's a Transcend 80x 1Gig card, by the way.
    (PowerPlay Vs) >> palmOne Zire 31 >>
    (palm Tungsten T3)/(palmOne Zire 72s) >> (palm Black Tie Trēo 650 Custom)/
    (palmOne LifeDrive Custom [SanDisk Ultra II CF])/(palm m515)/(palm T|X)
    handspring Visor Deluxe/Tapwave Zodiac 2/palm Trēo 680 Copper Orange


    Canuck PDA
  17.    #17  
    Quote Originally Posted by +Kardboard+ View Post
    Yeah, thanks. It's a Transcend 80x 1Gig card, by the way.
    I'm starting to suspect it has to do with the ratio of allocation block size to total disk space. I reformatted my 4GB card the same way and it worked again. Unfortunately, I don't have a 1 or 2GB card to test, only 128mb, 512mb, and 4GB.
  18. #18  
    Uh...in plain Engrish? hahah

    Is there a way to check cluster size? I formatted it on a "default" setting in Windows, but no idea what that is.
    (PowerPlay Vs) >> palmOne Zire 31 >>
    (palm Tungsten T3)/(palmOne Zire 72s) >> (palm Black Tie Trēo 650 Custom)/
    (palmOne LifeDrive Custom [SanDisk Ultra II CF])/(palm m515)/(palm T|X)
    handspring Visor Deluxe/Tapwave Zodiac 2/palm Trēo 680 Copper Orange


    Canuck PDA
  19.    #19  
    Quote Originally Posted by +Kardboard+ View Post
    Uh...in plain Engrish? hahah
    Honestly, I'm not sure how plain this is. The first thing I wrote was an analogy using pie, but it made me hungry and concerned I might come off condescending. You'd be amazed how many people fly off the handle when they hear, "Well, it's like pie."

    Anyway, file allocation blocks are the smallest size a file can be, and each takes some overhead for dealing with: the more chunks have to be moved, the longer it'll take, so one 32k chunk moves faster than four 8k chunks; additionally, the File Allocation Table from which FAT32 gets its name also has to account for every chunk, and sets aside space as a sort of table of contents. The more chunks you have, the more space you lose to the file allocation table.

    (That's one reason your "120GB" hard drive might actually show up as "100GB," for example; the other is a marketting trick that has to do with the definition of "megabyte." 1/6th of your space would be a huge FAT (heh-heh) but I'm just making up numbers to serve as an example.)

    However, there's a trade off with large chunks, because if you have 4k of data on 32k chunks, your 4k file actually occupies the full chunk, wasting 28k. If you have a 35k file, it takes two chunks, wasting 33k, etc. With larger drives a little waste is no big deal, but with smaller ones things get increasingly cramped. I wonder if there's an upper limit to chunk size as it relates to the total size ... but this is stuff I learned a long time ago and I'm rather fuzzy on some of the details.

    Is there a way to check cluster size? I formatted it on a "default" setting in Windows, but no idea what that is.
    Also from the command line, type CHKDSK DRIVE: (and add /F to do error-correction as well). It'll say "XXXX bytes in each allocation unit" near the bottom of the report.

    This actually does reveal something useful, maybe: my 40GB drives have 4k allocation chunks, so 32k over 4GB is enormously wasteful. I'm not surprised that it doesn't even allow it for smaller disks.
    Last edited by supersocialist; 09/10/2006 at 11:27 PM. Reason: fixing color formatting problems
  20. #20  
    That was WICKEDLY useful. Thanks!

    So 8K is the biggest size of chunks my card can handle. haha will have to test speed later to see if that's the same as the "default" setting (which I can't find out right now, because it' sin 8K chunks. )
    (PowerPlay Vs) >> palmOne Zire 31 >>
    (palm Tungsten T3)/(palmOne Zire 72s) >> (palm Black Tie Trēo 650 Custom)/
    (palmOne LifeDrive Custom [SanDisk Ultra II CF])/(palm m515)/(palm T|X)
    handspring Visor Deluxe/Tapwave Zodiac 2/palm Trēo 680 Copper Orange


    Canuck PDA
Page 1 of 3 123 LastLast

Posting Permissions