public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Blaz Antonic <blaz.antonic@havn.com>
To: Michael Kallas <michael.kallas@web.de>
Cc: linux-8086@vger.kernel.org
Subject: Re: 1.44MB disks (was: Forthcoming 0.1.0 release)
Date: Fri, 26 Apr 2002 12:59:43 -0700	[thread overview]
Message-ID: <3CC9B1AF.3E4E@havn.com> (raw)
In-Reply-To: 200204260942.g3Q9g0v22131@mailgate5.cinetic.de

> > I'm not sure what exactly you want to know; if your system boots from
> > 1.44 formatted floppy that means you have a drive that supports (at
> > least) 1.44 MB media.
> The only confusing thing I can think of would be 1.44MB media that's
> formatted with 720kB.
> Such a disk could also be handled in a double density (720kB) drive.

There's shoun't be any problem with that, yes.

> Test: Format a disk with 1.44MB and try to access it.

That's what i do all the time :) All my disk are 1.44 MB and work just
fine (in my 1.44 MB drive) ?!

Anyway, ELKS probe code should be able to handle some really exotic
formats as well (for example single-sided media with 18 sectors per
track and 80 tracks = non-standard 720 KB format) - it does rely on
"standard" formatting scheme though so you could feed it a floppy
deliberately formatted in a way that would confuse the probe (and
consequently cause problems to doshd code). It also counts on sectors
being formatted to 512 bytes (which is normal, standard format, only
exception i can think of is lame copy-proetction some compaines used to
employ .. this is not an option anymore with CDs replacing floppies as
installation media).

Bottom line being: use standard formats and everything should work just
fine :-)))

Blaz Antonic


      reply	other threads:[~2002-04-26 19:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26  9:42 1.44MB disks (was: Forthcoming 0.1.0 release) Michael Kallas
2002-04-26 19:59 ` Blaz Antonic [this message]

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=3CC9B1AF.3E4E@havn.com \
    --to=blaz.antonic@havn.com \
    --cc=linux-8086@vger.kernel.org \
    --cc=michael.kallas@web.de \
    /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