From owner-freebsd-questions Wed Jul 30 07:21:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA03600 for questions-outgoing; Wed, 30 Jul 1997 07:21:00 -0700 (PDT) Received: from gateway.ormond.unimelb.edu.au (gateway.ormond.unimelb.edu.au [203.17.189.194]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA03593 for ; Wed, 30 Jul 1997 07:20:56 -0700 (PDT) Received: (from gavin@localhost) by gateway.ormond.unimelb.edu.au (8.8.5/8.8.5) id AAA19265; Thu, 31 Jul 1997 00:20:25 +1000 (EST) From: Gavin Cameron Message-Id: <199707301420.AAA19265@gateway.ormond.unimelb.edu.au> Subject: Re: System Commander & 2.2.2R Boot Floppy In-Reply-To: from Vincent Poy at "Jul 30, 97 06:52:40 am" To: vince@venus.GAIANET.NET (Vincent Poy) Date: Thu, 31 Jul 1997 00:20:24 +1000 (EST) Cc: questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Another thing was that since my FreeBSD is on my second hard drive > (wd1a), after installing System Commander 3.05, it would just say Read > Error even before it showed anything from the bootstrap. Same case with > using the 2.2.2R boot floppy if booted through system commander. The only > booting method that works is booting the boot floppy and putting in > wd(1,0)kernel to boot from the hard drive at the boot floppy. > > Any ideas? > Here's what I got back from the V Communications when I reported the same problem. > Let's try this...At the System Commander main menu at boot time hit ALT+S. > From here highlight but do not hit enter the global special options menu, > and then hit the ALT+F9 keys to bring up the internal options menu. If the > choice for clear items is set to memory, change it to no by using your right > arrow key with that line highlighted. If it does not work write me again. Hope this helps. Gavin