On Mon, 04 Apr 2005, David Laight wrote:

> On Mon, Apr 04, 2005 at 10:38:41PM +0200, Martin Husemann wrote:
> > On Mon, Apr 04, 2005 at 10:08:52PM +0200, Oliver Fuchs wrote:
> > > That is my problem - I cannot do that:
> > > boot wd1a:
> > > 	booting wd1a:netbsd
> > > 	open wd1a:: Device not configured
> > > 	boot: wd1a:netbsd: Device not configured
> 
> You've got something funny in you BIOS setup.
> 
> The bios normally boots by reading sector 0 of the first disk (bios disk
> 0x80 in bios calls) and executing that code.  Pressing F5 on the 1.6
> netbsd bootselect code would have done the same thing, F6 would have
> read sector 0 of disk 0x81 etc (F1 and F2 do the same with the netbsd 2.0
> bootsel code).
> 
> However you've said that pressing F5 caused windows to boot - which makes
> it look like the bootselect code had been read from somewhere else.
> Have you set an unusual boot order? or disabled one of the disks?

Originally (with my first working setup wd0=windowsxp and
wsd1=netbsd1.6.1 and the netbsd bootselector on wd0) I have in my BIOS:

First Boot Device: Floppy
Second Boot Device: CDOM
Third Boot Device: Disabled
Boot Other Device: Enabled

I enabled the bootselect with
fdisk -B wd0
The  problem was that I only could select windowsxp because it is the
only os on wd0. But then I read that F6 causes the second harddrive to
be booted ... and that was what I did.

For running and testing netbsd2.0 I only set the third boot device to
harddisk hd1 and disabled 'boot other device'.

>  
> > Could you boot the install media, go to the utility menu and start
> > a shell
> 
> Or just type ^C and exit sysinst
> 
> > - then show us the output of 
> > 
> >   disklabel wd1
> 
> also the output from:
> 	sysctl machdep.diskinfo

Here is the output of sysctl machdep.diskinfo

machdep.diskinfo: 80:78156225(1024/255/63),2 81:156243600(1024/240/63),2  wd0:80 wd1:81

Oliver
-- 
... don't touch the bang bang fruit