Creating an image reduces card partition

Asked by Sam Grow

I used ImageWriteer 0.1 on my Vista laptop to create an Android boot disk for the Nook. I had a few problems but basically all went well.
Trying to do this again a couple of months later for my wife's Nook is giving me fits.
When I create the image on a 8GB microSD card (as well as an experimental 4GB card), the image loads, but immediately the volume size is reduced from 8GB to about 144MB, and the rest of the storage is in an unallocated space which I cannot get to with Disk Management.
Problem exists with the latest version.
I repeatedly reformatted and reloaded - same result. I can't get the program to stop reducing the boot partition volume.
Why? What to do??
Thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
Image Writer Edit question
Assignee:
No assignee Edit question
Solved by:
Sam Grow
Solved:
Last query:
Last reply:
Revision history for this message
Esi Ibraj (e-si-07) said :
#1

I have this problem too, mine went from 16 Gb to only 1Gb ://

Revision history for this message
Sam Grow (sambogrow) said :
#2

Esi,

Here's how I solved the problem...

Evidently, the program partitions the card into two areas - one for a Windows operating volume and one for the android/linux volume (one that can be read by the device for storing programs and data once in operation). If it did not do this, your computer running Windows could not copy files to the card, and the card once in the android device could not be of further use. Obviously, some programmer made the choice of how much space to use for each volume.
When I tried to load the UNPACKED files to the card, they were too large for the space allowed. Then, I loaded the zipped file, and it worked! The device automatically unpacked (unzipped) the files and installed them correctly.
The moral of the story - don't read more into the message than is necessary. I ASSUMED you would have to unpack the files - WRONG!
Good luck...

Revision history for this message
Sam Grow (sambogrow) said :
#3

See the prior message - for me this is solved.