Date: Sun, 26 Sep 2004 14:48:03 +0930 From: Malcolm Kay <malcolm.kay@internode.on.net> To: Saccheen Martin <sach_anna@yahoo.com>, questions@freebsd.org Subject: Re: cannot see Windows after installing FreeBSD Message-ID: <200409261448.03587.malcolm.kay@internode.on.net> In-Reply-To: <20040926032304.47194.qmail@web40006.mail.yahoo.com> References: <20040926032304.47194.qmail@web40006.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 26 Sep 2004 12:53 pm, Saccheen Martin wrote: > Hi Malcolm, > Please try to avoid top posting. Instead embed your comments/questions at the apropriate part of the thread. > The other computer is not on a network so I will try > to type the outputs. > > # /sbin/fdisk ad0 > *****Working on device /dev/ad0/ ****** > Parameters extracted are > cyl=787 heads 128 sectors/track=63 (8064 blks/cyl) > > parameters to be used for BIOS calculations are: > cyl=787 heads=128 sectors/track=63. (8064 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is : > The data for partition 1 is > sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size > 6346305 (3098Meg), flag 0 > beg: cyl 0/ head 1/ sector 1; > end: cyl 786/ head 127/ sector 63 > The data for partition 2 is > <UNUSED> > The data for partition 3 is > <UNUSED> > The data for partition 4 is > <UNUSED> > # > > > > # /sbin/fdisk ad1 > *****Working on device /dev/ad1/ ****** > Parameters extracted are > cyl=9729 heads 255 sectors/track=63 > > Figures below won't work with Bios for partitions not > in cyl 1. parameters to be used for BIOS calculations > are: cyl=9729 heads=255 sectors/track=63. (16065 > blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is : > The data for partition 1 is > sysid 7,(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced > Unix) start 63, size 156280257 (76308Meg), flag 80 > (active) > beg: cyl 0/ head 1/ sector 1; > end: cyl 1023/ head 254/ sector 63 > The data for partition 2 is > <UNUSED> > The data for partition 3 is > <UNUSED> > The data for partition 4 is > <UNUSED> > # > These look OK, i.e. as expected. > --- Malcolm Kay <malcolm.kay@internode.on.net> wrote: > > On Sun, 26 Sep 2004 12:23 am, Saccheen Martin wrote: > > > Hi Malcolm, > > > Thank you so much for replying. I did what you > > > > said > > > > > and I got the following: > > > > > > F1 FreeBSD > > > F5 Drive 1 > > > > > > When I press F5, I get: > > > >>FreeBSD/i386 BOOT > > > > > > Default: 0:ad0(0,a)/boot/loader > > > boot: _ > > > If the boot process has really switched over to Drive 1 then it is difficult (for me) to understand where these messages come from -- unless perhaps some part of the FreeBSD installation has overwritten part of your windows installation. But I would have expected you would need to try very hard to do this without changing the slice (in windows parlance - partition) to a BSD type. > > > What do I type at the boot: prompt to get windows? I don't believe there is anything that will do that from here. > > > Thanks > > > > Sorry, I don't understand how this has come about. > > It would seem that somehow you have some partial > > FreeBSD installation on Drive 1 (the Slave). > > > > It might help if you can post the outputs from > > # /sbin/fdisk ad0 > > and > > # /sbin/fdisk ad1 > > run as root under FreeBSD > > > > Malcolm You could try installing a boot manager also on the slave drive which should offer F1 Windows (or something similar) or F5 Drive 0; when you get there from the initial F5 -> Drive 1 But I'm not optimistic -- or at least I believe you'll get the offer but F1 will still lead into never-never land. I believe that what you have should have worked unless something became corrupted along the way; but I am sure there are people out there whose understanding is much better than mine. Malcolm
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409261448.03587.malcolm.kay>