From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a0502021114c9fcf2d@mail.gmail.com>
Date: Wed,  2 Feb 2005 14:14:41 -0500
From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] XP boot
In-Reply-To: <007401c5094a$f8ac79d0$51587d50@kilgore>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <001e01c508ba$1e86d7e0$3f587d50@kilgore>
	<ee9e417a05020116121d8d0463@mail.gmail.com>
	<000a01c508c4$25f2d290$4aec7d50@kilgore>
	<ee9e417a05020117201baa4a6b@mail.gmail.com>
	<7871fcf505020120421bf9ff8e@mail.gmail.com>
	<007401c5094a$f8ac79d0$51587d50@kilgore>
Topicbox-Message-UUID: ffb10cd8-eacf-11e9-9d60-3106f5b1d025

it's much easier just to install smart boot manager
and avoid the nt boot loader. =20
hget http://pdos.lcs.mit.edu/~rsc/mbr.bootmgr
disk/mbr -m mbr.bootmgr /dev/sdC0/data

russ


On Wed, 2 Feb 2005 18:16:43 +0100, boyd, rounin <boyd@insultant.net> wrote:
>     Any other method fails=E2=80=94boot.ini is protected by more than the=
 NTFS
>     file protection scheme, and I don't believe there's another way aroun=
d it.
>=20
> yes, it is a very strange file.  i got some private mail from russ and af=
ter
> finding boot.ini it was read only.  turn that off and write it with notep=
ad.
> [seemingly] randomly it would turn on read only.
>=20
> there is this command line thing called 'bootcfg' which is absolutely
> undecipherable, although i now understand something about the format
> of the file by tinkering.
>=20
> boot.ini essentially points at a 'boot block'.  i'm a bit wary about [pot=
entially]
> smashing a currently bootable system.
>=20
> this will take some thought.
> --
> MGRS 31U DQ 52572 12604
>=20
>