From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by listman.redhat.com (Postfix) with ESMTP id 37CB33ED60 for ; Wed, 28 Aug 2002 04:26:09 -0400 (EDT) Received: (from mail@localhost) by int-mx1.corp.redhat.com (8.11.6/8.11.6) id g7S8Q5Z27522 for blinux-list@listman.redhat.com; Wed, 28 Aug 2002 04:26:05 -0400 Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with SMTP id g7S8Q5Y27517 for ; Wed, 28 Aug 2002 04:26:05 -0400 Received: from mx2 (root@mx2.onewest.net [199.104.81.35]) by mx1.redhat.com (8.11.6/8.11.6) with SMTP id g7S8B2l11339 for ; Wed, 28 Aug 2002 04:11:02 -0400 Received: from id07.onewest.net ([199.104.81.25] ident=root) by mx2 with esmtp (Exim 3.36 #1 (Debian)) id 17jy9L-0005mk-00 for ; Wed, 28 Aug 2002 02:26:03 -0600 Received: from du137.204.onewest.net ([65.19.204.137] helo=rupin.localnet) by id07.onewest.net with esmtp (Exim 3.35 #1 (Debian)) id 17jy9J-0004Pg-00 for ; Wed, 28 Aug 2002 02:26:02 -0600 Received: from localhost (lcr@localhost) by rupin.localnet (8.11.6/8.11.6) with ESMTP id g7S8Q1W31114 for ; Wed, 28 Aug 2002 02:26:01 -0600 Date: Wed, 28 Aug 2002 02:26:00 -0600 (MDT) From: "L. C. Robinson" To: "blinux-list@redhat.com" Subject: Re: redhat bootdisks with brltty In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Loop: blinux-list@redhat.com Sender: blinux-list-admin@redhat.com Errors-To: blinux-list-admin@redhat.com X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: blinux-list@redhat.com X-Reply-To: no_spam+munged_lcr@onewest.net.invalid List-Help: List-Post: List-Subscribe: , List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: Well, based on what I have read in the syslinux documentation, it's probably buggy BIOSes (the BIOS can only read certain dos based formats). Syslinux has some workarounds for such situations, such as memdisk, and some options. You'd have to experiment with modifying the boot disks with small syslinux config changes to find out for sure. Make sure you have the latest syslinux, too, so that you have the most recent improvements for buggy BIOSes: see syslinux home page at http://syslinux.zytor.com/ Quote from the syslinux site: "NEWS! SYSLINUX 1.76 was released on August 27, 2002; this version contains a workaround for certain broken Toshiba BIOSes." I know that RH uses syslinux on their boot disks, but don't know about Debian -- but you will be able to determine that easily enough (probably already know). LCR On Wed, 28 Aug 2002, Cheryl Homiak wrote: > Well, it could be that the laptop floppy has a different > format; in fact, just this evening it was insisting I was > putting in some floppies with vfat. However, the Redhat > disks aren't working on either machine and they were done > on the desktop. so I don't think that's the problem with > the Redhat floppies. It might, however, explain why the > debian floppies, both standard and brltty-modified, work > on my desktop but not on my laptop. I'll go looking for > the disk utilities, as I do have a DOS partition. -- L. C. Robinson reply to no_spam+munged_lcr@onewest.net.invalid People buy MicroShaft for compatibility, but get incompatibility and instability instead. This is award winning "innovation". Find out how MS holds your data hostage with "The *Lens*"; see "CyberSnare" at http://www.netaction.org/msoft/cybersnare.html