public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: David Given <dg@cowlark.com>
To: linux-8086@vger.kernel.org
Subject: Re: howto start
Date: Tue, 07 Feb 2012 14:46:53 +0000	[thread overview]
Message-ID: <4F31395D.2040502@cowlark.com> (raw)
In-Reply-To: <4F312FF6.1070801@jodybruchon.com>

[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]

Jody wrote:
[...]
> I believe this is a problem with lots of 720KB floppies being written in
> 1.44MB drives. You'll have to format the disk as a 720KB disk, THEN
> write the image to it, and even then it has a chance of not working. I
> assume that you are using a 1.44MB disk; make sure it's formatted as a
> 720KB disk, not a 1.44MB disk.

The disk head on a 1.44MB drive is half the size of the head on a 720kB
drive. If you format a 720kB disk in a 1.44MB drive it just formats
every other track on the disk.

This is fine if the disk was previously unformatted, but if it had been
formatted with something else then the wide 720kB head will pick up the
new formatted track *and* the old data from the other half of the 720kB
track and get confused. [*]

To make it work reliably you may well need to scrounge up a 720kB drive
to put in the PC, or else find a way to use a 1.44MB drive for the
Tandy. (There's a reason why everyone hates floppies...)



[*] It may be technically feasible to make the 1.44MB drive duplicate
the data to both halves of the 720kB track, but this will require magic
hackery to write tracks with the 'wrong' track ID, and I don't know how
to do that.

-- 
┌─── dg@cowlark.com ───── http://www.cowlark.com ─────
│ "I have always wished for my computer to be as easy to use as my
│ telephone; my wish has come true because I can no longer figure out
│ how to use my telephone." --- Bjarne Stroustrup


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2012-02-07 14:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06  5:14 ELKS CVS imported into Git with all history Jody
2012-02-06 11:48 ` howto start kqt4at5v
     [not found]   ` <4F30291D.5030908@telia.com>
2012-02-07 12:08     ` kqt4at5v
2012-02-07 14:06       ` Jody
2012-02-07 14:46         ` David Given [this message]
     [not found]           ` <CAMKR1ysKw2SaGObU38Gv8Sh1GMkxjRRkc7wwNPvNDKAa7Z=0pw@mail.gmail.com>
2012-02-07 16:29             ` David Given
2012-02-07 18:48         ` kqt4at5v
2012-02-07 20:02         ` kqt4at5v
2012-02-07 14:49 ` ELKS CVS imported into Git with all history Harley Laue
2012-02-07 21:38   ` Jody Bruchon
2012-02-08  0:15     ` David Given
2012-02-08  2:56     ` Kirn Gill
2012-02-08 21:28     ` Juan Perez-Sanchez
2012-02-09  2:53     ` Harley Laue

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=4F31395D.2040502@cowlark.com \
    --to=dg@cowlark.com \
    --cc=linux-8086@vger.kernel.org \
    /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