Ed Cryer wrote:
> Removing an OS is done by two processes;
> 1. Remove it from the boot menu.
> 2. Delete or format the partition.
>
> I've removed it from the booting menu, but can't do 2 because that
> partition is currently the System one. It won't let me shrink it, delete
> it or format it. I could delete the vast majority of files on it, but
> not the lot.
> The best method would be to change the System setting to Win7 (C).
> How do I do that?
>
> Win7 (C) Simple, Dynamic, NTFS Healthy(Boot, Page File, Crash Dump)
> 291 GB
> Win8 (D) Simple, Dynamic, NTFS Healthy (System) 115 GB
>
> Ed
I don't really understand what's going on there and what the configuration is.
Why you can't boot into Windows 7 and delete Windows 8.
At the very least, you should have a backup of the entire disk, so if
a step turns out to be wrong, you've got options.
You could try using PTEDIT32, and set the "Type" field of the partition
you want to delete, to "00" from "07". The advantage of that, is you don't
have to change any of the other fields. Setting it to 00 might, in the
case of Windows, cause Windows to ignore that partition on the next boot.
Now, whether Windows will allow you to change the current "C:" partition
in that way, I don't know. I haven't tried that.
You'd run PTEDIT32 as admin.
You can also do this from a Linux LiveCD. Fdisk has the same capabilities as
PTEDIT32, with a less convenient interface. I like in PTEDIT32, how I can just
edit the numbers, copy the numbers from one row to another and so on. But this
also has a simple command for changing the type field of a primary partition.
sudo fdisk /dev/sdb
You could also edit the partition table with a hex editor, by using "dd"
and copying the MBR into a 512 byte table, make edits, then write it back.
(There are four 16 byte fields in the MBR, which is the same info that PTEDIT32
displays.)
Note that, changing the partition type, isn't sufficient in all cases.
I've had software "sniff" a partition, and examine the header portion of the
partition itself, and figure out it's NTFS and mount it. So changing the
partition type to 0x00 is not a guarantee it can't be detected. I'm hoping
in this case, that Windows 7 Repair won't ferret out that partition and
change the field back to 0x07 on you.
*******
The other complicating factor here, is "Dynamic". That has the advantage of
being able to span a partition onto more than one disk, but it can complicate
other things you do. I don't know now, if a partition table manipulation
will be enough to do the job. I've never done partition table changes on a
Dynamic Disk. The thing is, the metadata also contains information on
the disk structure...
I *never* leave partitions in dynamic mode, because I don't know the mechanics
of dealing with issues on them! Dynamic Disks uses something like 1 megabyte
of metadata, up near one end of the disk. As far as I know, this allows
logical volume management, supports spanning across multiple physical disks
and the like. A Partition Editor would know how to safely manipulate something
like that, but I'd have a little research to do, before I used the "Paul approach"
on it (hex editor and sticks of dynamite) :-) As far as I know, the partitions
on my Win7 laptop are Basic rather than Dynamic. It's one less thing to worry
about when I'm hacking stuff.
There is a section here on Dynamic disks. It doesn't go into enough detail
to "get out the hex editor".
http://en.wikipedia.org/wiki/Logical_Disk_Manager
There are recipes out there, to convert a simple dynamic disk back to basic,
but I don't know if they would cover Vista/Win7/Win8. The recipes rely on
the layout of the data itself, being compatible across both modes, such that
changing the partition table value.
OK, this is what i was looking for.
http://www.win.tue.nl/~aeb/partition...n_types-1.html
"42 Windows 2000 dynamic extended partition marker
If a partition table entry of type 0x42 is present in the legacy partition
table, then W2K ignores the legacy partition table and uses a proprietary
partition table and a proprietary partitioning scheme (LDM or DDM). As
the Microsoft KnowledgeBase writes: Pure dynamic disks (those not containing
any hard-linked partitions) have only a single partition table entry (type 42)
to define the entire disk. Dynamic disks store their volume configuration in
a database located in a 1-MB private region at the end of each dynamic disk."
I think that's why I don't like Dynamic Disks for home usage. It prevents
me from using PTEDIT32 for a lot of things... When there is only a single
partition, I think that's when the recipe of changing 42 to 07 works.
But you'll want to go off and Google that, because I don't know all the details
of when that's safe to do.
42 signals that the metadata is in control. If there is more than one partition
on the disk, then obviously the MBR partition table no longer has a valid picture
of the disk contents. It might be reconstituted with TestDisk, but that's a
stretch.
If your disks weren't Dynamic, this would be so much easier.
Paul