![]() |
![]() |
![]() |
![]() |
|
|
#1 |
|
Member
Join Date: Oct 2011
Posts: 182
|
SanDisk 64GB Mobile Ultra MicroSDXC Memory Card with SD Adapter
http://www.amazon.co.uk/gp/product/B...7GK8ENYYWEVHR9 guiformat.exe http://www.ridgecrop.demon.co.uk/ind...?guiformat.htm os: windows 7 load microsd card into adaptor and plug into laptop format as fat32 with guiformat.exe - reported as 64gb insert into c2 windows sees it as 32gb so i re formatted as fat32 whilst in c2 then put it back into the adapter and reformatted as fat32 windows sees it as 64gb (59.4) re inserted it into the c2 and connected it and windows now saw the full size 59.4. related forum posts: http://anythingbutipod.com/forum/sho...57&postcount=8 http://iaudiophile.net/forums/showthread.php?t=40028 |
|
|
|
|
#2 |
|
Junior Member
Join Date: Oct 2011
Posts: 7
|
Thx for sharing !!
|
|
|
|
|
#3 | ||||||
|
Very Senior Member
Join Date: Aug 2010
Location: Marina Del Rey, CA
Posts: 1,006
|
Quote:
Quote:
But Windows didn't see that it was formatted as FAT32 (which had been done earlier by GUIFormat when the card was in the reader. It asked me if I wanted to format, and the lower panel from DISKMGMT.MSC showed it as 32GB "raw". Quote:
If you used GUIFormat through the C2, you had no fear using it with the 64GB card in the C2? I didn't want to take a chance perhaps doing some damage to the card if the J3 is unprepared for a 64GB card. But, if you did it, maybe I should too. Quote:
Quote:
Quote:
The card is last formatted exactly as it was originally, by GUIFormat in the reader. So why should this second format, following a format while still in the J3 which followed the original format while in the reader... why should this have any different results as far as how Windows now sees the card when it's back in your C2? This certainly doesn't make scientific sense to me, although you clearly state that there WAS a difference in how Windows saw the card the second time vs. how it saw the card the first time. The fact that there was an intervening format with the card in the C2 seems irrelevant, as you then did a third format with the card back in the reader. What possible effect could that second format in the C2 have to make the third format in the reader any different than the first format in the reader?? I suppose I could try it again, following your steps exactly. But again, my first Windows view showed it as 32GB "raw" and not 32GB FAT32. Was this what you saw? I'm a skeptic, but I'm willing to be a believer. I'd sure like to be able to have it possible to just connect the J3 to the PC and always be able to maintain both internal and external storage as I did when I had a 32GB external card. This is certainly more convenient than having to remove the card and put it in the reader in order to maintain it, so my fingers are crossed that somehow this odd "recipe" for overcoming the initial symptom will truly work on my J3. I'll give it a try. Nothing to lose, I suppose, as long as running GUIFormat again with the card in the J3 doesn't do any damage. It's just a few seconds. And then remove the card, put it back in the reader, and run GUIFormat yet again. And then remove the card, put it back in the J3 and magically it's now supposed to be perfectly acceptable FAT32 64GB... even though it wasn't seen that way after the first format. Powerful stuff, if it really works. |
||||||
|
|
|
|
#4 | |
|
Junior Member
Join Date: Jun 2009
Posts: 3
|
Quote:
Last edited by Marxzone; 09-07-2012 at 05:17.. |
|
|
|
|
|
#5 |
|
Junior Member
Join Date: May 2007
Posts: 8
|
which allocation size should be be best?
|
|
|
|
|
#6 |
|
Very Senior Member
Join Date: Aug 2010
Location: Marina Del Rey, CA
Posts: 1,006
|
|
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|