public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "L. C. Robinson" <lcr@onewest.net>
To: "blinux-list@redhat.com" <blinux-list@redhat.com>
Subject: Re: redhat bootdisks with brltty
Date: Wed, 28 Aug 2002 02:26:00 -0600 (MDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0208272351450.2193-100000@rupin.localnet> (raw)
In-Reply-To: <Pine.LNX.4.44.0208280000210.4991-100000@maranatha.chartermi.net>

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




  parent reply	other threads:[~ UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Cheryl Homiak
 ` Jude DaShiell
   ` Cheryl Homiak
     ` Jude DaShiell
       ` Cheryl Homiak
         ` L. C. Robinson
           ` Cheryl Homiak
         ` Jude DaShiell
           ` Cheryl Homiak
             ` Jude DaShiell
               ` Cheryl Homiak
                 ` L. C. Robinson
                   ` Cheryl Homiak
     ` L. C. Robinson [this message]
       ` Cheryl Homiak
   ` Gil Andre
     ` Cheryl Homiak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0208272351450.2193-100000@rupin.localnet \
    --to=lcr@onewest.net \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).