Re: FIXMBR redux
From: Michael Solomon \(MS-MVP Windows Shell/User\) (user_at_#notme.com)
Date: 06/04/04
- Next message: Michael Solomon \(MS-MVP Windows Shell/User\): "Re: FIXMBR redux"
- Previous message: anonymous_at_discussions.microsoft.com: "Re: hard drive limit"
- In reply to: *Vanguard*: "Re: FIXMBR redux"
- Next in thread: William B. Lurie: "Re: FIXMBR redux"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 4 Jun 2004 15:26:30 -0700
Yeah but aren't we just modifying the bootstrap? I agree, deleting the
partition does not touch the bootstrap. Of course, if I extend my thinking
on this, it doesn't have to touch the bootstrap or MBR. If you've modified
so that the bootstrap or MBR is looking for something that doesn't exist in
this particular image, that would explain the error William was getting. In
other words, the MBR is set to look for something that isn't in the image.
I know he's going to bust my chops on that because he'll say it's an exact
image but that is what I have been telling him. The hal or the hash is
different because of the changed hardware configuration, hence he gets a
missing or corrupt HAL.dll warning as he described. That means he's bumping
right into XP's anti-piracy scheme as I had surmised. He made an image of a
setup that was not installed when the other hard drive was also connected to
the system. When he restores the image, XP thinks it's a different
computer.
-- Michael Solomon MS-MVP Windows Shell/User Backup is a PC User's Best Friend DTS-L.Org: http://www.dts-l.org/ "*Vanguard*" <reply-to-newsgroup@to-email.use-Reply.obey-signature.invalid> wrote in message news:OQF9cYnSEHA.3812@TK2MSFTNGP11.phx.gbl... > Michael Solomon (MS-MVP Windows Shell/User) said in > news:u5nS3KFSEHA.2704@TK2MSFTNGP10.phx.gbl: > <snip> >> If you delete the partition on the drive you originally imaged, the >> MBR is gone, hence, if that drive is bootable upon restoring the >> image you created of that drive, it must be restoring the MBR when it >> restores the image. > > Deleting a partition only updates the partition table (which is after > the 460-byte bootstrap area of the MBR, or sector 0). Deleting a > partition does NOT touch the bootstrap program! That's why you can > still use that bootstrap program on that drive after deleting, changing, > or moving partitions whether using PartitionMagic, DriveImage, or FDISK > (without using its undocumented /MBR parameter). > >
- Next message: Michael Solomon \(MS-MVP Windows Shell/User\): "Re: FIXMBR redux"
- Previous message: anonymous_at_discussions.microsoft.com: "Re: hard drive limit"
- In reply to: *Vanguard*: "Re: FIXMBR redux"
- Next in thread: William B. Lurie: "Re: FIXMBR redux"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
