In message <199903152121.WAA28726@vader.runit.sintef.no>
	on Mon, 15 Mar 1999 22:21:08 +0100,
	Havard.Eidnes@runit.sintef.no wrote:
> I think this problem got solved just before the weekend, and it
> should work now.
Yes, I've reported my success.  Thanks much for good works.  :-D

> Message-Id: <199903081604.BAA24858@edge.sky.yamashina.kyoto.jp>
> Subject: Re: warning: i386 bootblocks
> Date: Tue, 09 Mar 1999 01:04:19 +0900
> From: Takahiro Kambe <taca@sky.yamashina.kyoto.jp>
> To: port-i386@netbsd.org
> Cc: current-users@netbsd.org
> X-Mailer: Mew version 1.94b2 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA)
> Precedence: list
> Delivered-To: port-i386@netbsd.org
> Content-Type: Text/Plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> X-Dispatcher: imput version 981124(IM104)
> 
> After today's sup, I succeed to create boot1.fs, boot2.fs and
> bootfloppy-tiny.
> 
> >Module Name:	src
> >Committed By:	he
> >Date:		Sun Mar  7 20:03:44 UTC 1999
> >
> >Modified Files:
> >	src/sys/arch/i386/stand/lib: loadfile.c
> >Log Message:
> >Add handling of OMAGIC files, where exec header isn't part of the
> >text segment.  Needed for woring installboot, since biosboot.sym is OMAGIC.
> 
> Is this the fix for these day's i386 boot code problem?
> 
> Anyway, I thank much!!

--
Takahiro Kambe <taca@sky.yamashina.kyoto.jp>