[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: continued problems with 2.88 meg image



On Mon, 31 Aug 1998, Jeff Noxon wrote:

> On Mon, Aug 31, 1998 at 05:13:01PM -0400, Dale Scheetz wrote:
> > On Mon, 31 Aug 1998, Jeff Noxon wrote:
> > 
> > > I've often wondered if what you're trying to do is possible.  Can you
> > > boot a 2.88 meg CD image on a machine with a BIOS that doesn't even
> > > support 2.88 meg drives?  Inquiring minds want to know.
> > 
> > Am I really the first person to try this?
> 
> Do you really want to know the answer?  :)

Yes?

> 
> > > Did you place a valid boot sector on your 2.88 image?  I don't think
> > 
> > I supposed that mformat or syslinux did that. There is certainly one on
> > the 1.44 meg image I built.
> > 
> > > any of the Linux tools will write a valid MBR.  You can copy one from a
> > > DOS formatted 1.44 meg disk.  (Use dd to write the first 512 bytes.)
> > > 
> > What suggests that "Linux tools" don't write valid MBRs? The rescue
> > floppies are all built with "Linux tools". Why should this one image be
> > particular?
> 
> When I used format floppies with mtools, they didn't have valid boot
> records.  They would just lock up the machine if I booted with one in
> the drive.

>From looking at the boot record it looks like it is constructed by
syslinux. This must be why we use it instead of loadlin on the boot disks.

> > Know anyone with a 2.88 meg drive?
> 
> I've asked around here ... no bites.

I'll ask on the testing mailing list.

> 
> > > Good luck,
> > 
> > It appears that I need more than I have ;-)
> 
> Sorry I couldn't be more helpful...  :(
> 
It always helps to have a shoulder to cry on ;-)

Thanks, 

Dwarf
--
_-_-_-_-_-   Author of "The Debian Linux User's Guide"  _-_-_-_-_-_-

aka   Dale Scheetz                   Phone:   1 (850) 656-9769
      Flexible Software              11000 McCrackin Road
      e-mail:  dwarf@polaris.net     Tallahassee, FL  32308

_-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_-


Reply to: