Re: burning hard drive to disk

From: Eddie Corns (eddie_at_holyrood.ed.ac.uk)
Date: 03/24/04


Date: Wed, 24 Mar 2004 12:27:04 +0000 (UTC)

jpd <read_the_sig@do.not.spam.it> writes:

>In article <c3plvl$6pf$1@scotsman.ed.ac.uk>, Eddie Corns wrote:
>[snip]
>> The critical word is "need", the booting process for Windows uses information
>> in the MBR to know where critical files are etc., repartioning can overwrite

>*bzzzt* Thanks for playing.

>The MBR (Master Boot Record, that what resides on the first sector of
>the DISK, all of 512 bytes big) only holds a bootloader and a table with
>parti^Wslice info. That one loads and jumps to, depending on bootloader;

>a) the secondary bootloader which resides on the first sector of a parti^W
> slice marked active in the slice table (the default MBR does this)
>b) like a) but you get to choose which slice to read the bootloader from
> (the FreeBSD bootloader), or
>c) the second-and-further sectors of the disk that are not in use normally
> as a slice has to start on (IIRC) a cylinder boundary and can be hijacked
> for storing extra bootloader code (lilo, grub, etc) which then provides
> a fancy way of doing b) or even just a).

Yes, this is what I was thinking of and misremembered the name. I only got
involved in the first instance because I could see potential for things going
wrong and was trying to clarify the requirements. I should have punted more
on the follow-up situation where my knowledge was less complete. I will write
out 100 times "I do not have to try and answer a question just because it is
directed explicitly to me".

>Where exactly DOS^Wwindows stores its info I blissfully forgot, but it's
>not in the MBR. AFAIK it's not in the secondary bootblock either, but
>somewhere in what would be a superblock if FAT had such a notion.
>However, IME judicious application of the SYS utility (can't remember if
>it was SYS.EXE or SYS.COM, and I don't care) can help you make a
>DOS^Wwindows partition bootable again. This goes for DOS based stuff, as
>you might have guessed. The other variety, that of NT[T]* windowses,
>have their own brand of booting and bootloaders and Stuff.

I would hope that a recovery disk, hopefully anybody's win98 recovery
disk, would be able to do this.

Eddie



Relevant Pages

  • Re: burning hard drive to disk
    ... > in the MBR to know where critical files are etc., ... That one loads and jumps to, depending on bootloader; ... the secondary bootloader which resides on the first sector of a parti^W ... slice marked active in the slice table ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Dual booting problems
    ... or an alternative boot manager such as grub or gag. ... the slice table and some flags and just enough code to look at its ... other disk to see which ones have a similar boot block. ... the MBR on other disk. ...
    (freebsd-questions)
  • Re: Zfs Q
    ... The bootloader is installed on a slice, not a disk. ... Each bootable slice will have its own bootloader. ...
    (comp.unix.solaris)
  • Re: FreeBSD 7.0 fdisk issue during installation
    ... then I should only create 1 slice of the ... disk which FreeBSD can use, but nothing else can including some non-FreeBSD ... boot managers. ... you can do that by putting an MBR on each ...
    (freebsd-questions)
  • Re: Adding a disk
    ... If you "dangerously dedicate" the disk (i.e., ... including a DOS partition table), then there are no slices, since ... My advice is to create an ordinary MBR, ... will work on that slice and you can create BSD partitions. ...
    (comp.unix.bsd.freebsd.misc)