Sometimes when I set up a hard drive I get 7 to 8 meg of unallocated space. Other times the whole drive is used. It has never seemed to make any difference - so just wondering if anyone knows why this unallocated bit is there and what is its purpose ? Yesterday I wanted to restore a system image and Shadow Protect complained that there wasn't enough space to restore. I was actually restoring to the same drive I gad imaged but in the meantime had installed Xp as a test. Using Disk Direct 10 I deleted everything and set up a new partition - with no unallocated space, then used SP to restore. Everything seems ok but should there be an unallocated space ?
Hi Hairy. Rightly or wrongly I have using Disk director 10 to set up C: as primary /active with 7.8 mg unallocated at the end and D: as Logical with 7.8 mg unallocated at the beginning. Having D: without any unallocated worked fine but I'm not going to argue about the los of 7.8 mg from a 1 TB drive.
I addressed this issue with Velocity Micro, as when I receive machines new from them and they've loaded with a script, the complete disk is allocated. But when a clean install is done that free space is always there. They said it was windows leaving it in case you wanted to create dynamic disks and if you didn't then there was no need for that empty space. The last time my machine came back from a repair, they had done a clean install. I used Disk Director and eliminated that space. No harm done at all. Pete
