From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <007401c5094a$f8ac79d0$51587d50@kilgore> From: "boyd, rounin" To: "Joel Salomon" , "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> References: <001e01c508ba$1e86d7e0$3f587d50@kilgore><000a01c508c4$25f2d290$4aec7d50@kilgore> <7871fcf505020120421bf9ff8e@mail.gmail.com> Subject: Re: [9fans] XP boot Date: Wed, 2 Feb 2005 18:16:43 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Cc: Content-Transfer-Encoding: quoted-printable Topicbox-Message-UUID: ff9dfcd8-eacf-11e9-9d60-3106f5b1d025 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. 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. 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. boot.ini essentially points at a 'boot block'. i'm a bit wary about [pot= entially] smashing a currently bootable system. this will take some thought. -- MGRS 31U DQ 52572 12604