Return to BSD News archive
#! rnews 2183 sserve.cc.adfa.oz.au Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!news.netspace.net.au!stang.netspace.net.au!elkheirh From: elkheirh@stang.netspace.net.au (Haissam Elkheir) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Installation Problem Date: 4 Jun 1995 01:17:26 GMT Organization: NetSpace Online Systems Lines: 31 Message-ID: <3qr1j6$gq8@otis.netspace.net.au> References: <3qm08o$7pd@otis.netspace.net.au> <3qmraj$sv6@bonnie.tcd-dresden.de> NNTP-Posting-Host: netspace.net.au X-Newsreader: TIN [version 1.2 PL2] J Wunsch (j@narcisa.sax.de) wrote: > Haissam Elkheir <elkheirh@stang.netspace.net.au> wrote: > >I have a serious problem which I haven't been able to solve. After > >getting the Walnut Creek FreeBSD 2.0 CD and following the installation > >procedures I create the two boot disks and reboot. The system reads the > >boot disk for a few seconds and then continues to boot the normal HD OS, > >DOS 6.2. I have looked for a solution but have found none. > If it's continuing to boot DOS, the BIOS didn't detect a valid > bootstrap sector on your diskette. This is far before the point where > FreeBSD itself is coming up. I suspect either a bad medium, or > something's got wrong with the file image (e.g. it's been corrupted > due to an ASCII ftp download), so there's no valid bootstrap signature > at the end of the boot sector. > -- > cheers, J"org private: joerg_wunsch@uriah.heep.sax.de > http://www.sax.de/~joerg/ > Never trust an operating system you don't have sources for. ;-) I downloaded the boot_144.flp and cpio.clp files from ftp.freebsd.org in the 2.0-RELEASE/floppies directory and have gotten the same response. I donwloaded the files correctly (used bin, and checked file size) but still no go. I have used two different types of disks to create the boot images on. Both format OK and seem to be fine. Any help greatly appreciated. Btw, the CD I have from Walnut Creek says FreeBSD 2.0 on it but the date is January 1994, not 1995. What happened? It's version 2.0 I believe but could this be the reason, fault installation from Walnut Creek?