Partition Info Question 7.8mb unallocated space

  • Thread starter Thread starter Dr. Sysop
  • Start date Start date
D

Dr. Sysop

One of my systems I have a 120 gig & a 60 gig as slave. The Slave use to be
a master & used ghost or maxblast 3, anyways I used partition magic drive
mapper to see drives & noticed on main I see 7.8 mb of unallocated space &
the slave which was cloned had nothing. I made a 7.8 mb unallocated space on
slave like master. What exactly & why do I need that 7.8 mb of unallocated
space? I was told to make it but do I actually need it? my master has it if
I remove it or make it usable & format that area will windows run normally?
Using Windows XO Pro.
 
Dr. Sysop said:
One of my systems I have a 120 gig & a 60 gig as slave. The Slave use
to be a master & used ghost or maxblast 3, anyways I used partition
magic drive mapper to see drives & noticed on main I see 7.8 mb of
unallocated space & the slave which was cloned had nothing. I made a
7.8 mb unallocated space on slave like master. What exactly & why do
I need that 7.8 mb of unallocated space? I was told to make it but do
I actually need it? my master has it if I remove it or make it usable
& format that area will windows run normally? Using Windows XO Pro.
Click to expand...

I don't know the answer but suggest that it is to do with the size of the
sectors/clusters, the unallocated may be an odd size that is just
disregarded.
I had XP (on installation), partitition my 60G drive as one FAT32 partition
and it left ~8MB spare.
Hope someone else will come-up with an answer.
 
You're not also using BootMagic by any chance?
It creates a partition abot that size.
If you are, uninstall BM, as it MUST NOT be used with XP.
Reclaim that spare space into one of your drives and let boot.ini handle
your dual-boot.
 
Back
Top