All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henne <henne@nachtwindheim.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] 720KB Floppy on 64bit Linux
Date: Thu, 04 May 2006 09:27:30 +0000	[thread overview]
Message-ID: <4459C902.8090409@nachtwindheim.de> (raw)
In-Reply-To: <4457C938.1070601@nachtwindheim.de>

Randy.Dunlap wrote:
>> Henne wrote:
>>> Mounting it Kernel says:
>>> FAT: invalid media value (0x44)
>>> VFS: Can't find a valid FAT filesystem on dev fd0
>> I found out something interesting:
>> I made an image of my old disk with dd and here's the hexdump of the bootsector:
>>
>> 00000000  eb 3c 90 4d 53 44 4f 53  35 2e 90 6e 02 02 7f cf  |.<.MSDOS5..n....|
>> 00000010  eb 3c 90 4d 53 44 4f 53  35 2e 30 00 02 02 01 00  |.<.MSDOS5.0.....|
>> 00000020  02 70 00 a0 05 f9 03 00  09 00 02 00 00 00 00 00  |.p..............|
>> 00000030  00 00 00 00 00 00 29 dc  1c 2c 02 00 53 41 00 00  |......)..,..SA..|
>>
>> You may notice, that the media invalid media value (0x44) is that from offset 0x15.
> 
> Yes, but part of that line looks wrong (like duplicated from above).
> Suspicious.
> 
>> But on the disk image the correct value is on offset 0x25 (the 0xf9), so struct fat_boot_sector
>> must start on 0x10 to work correctly.
> 
> Yes, looks weird.
> 
>> IN THIS CASE!
>>
>> "Normal" 1.44MB FAT disks have a bootsector like this one:
>>
>> 00000000  eb 3c 90 4d 53 44 4f 53  35 33 79 00 02 01 01 00  |.<.MSDOS53y.....|
>> 00000010  02 e0 00 40 0b f0 09 00  12 00 02 00 00 00 00 00  |...@............|
>> 00000020  00 00 00 00 00 00 29 45  49 53 41 53 59 53 52 4f  |......)EISASYSRO|
>> 00000030  4d 35 20 20 20 20 46 41  54 31 32 20 20 20 fa 33  |M5    FAT12   .3|
>>
>> So there everything is allright!
>>
>> But why everything works under i386 and not under x86_64?
> 
> I tested on x86_64 with no problems.  Formatted a 720 KB floppy
> and a 1.4 MB floppy using both mkdosfs and kfloppy, mounted and
> read them both fine.

But I don't understand why a slackware10.2/2.6.17-rc3(selfcompiled) got it,
and Suse10.0_64/2.6.17-rc3(selfcompiled) got it not.
I have also FREEDOS on my i386 which got it too. Strange..
The disks are 3.5 inch with no hole on the left side, are purchased by EBay and seem to be original.
They are from the game "Das schwarze Auge-Schicksalsklinge" which is the german original of "Realms of arkania-Blade of destiny".
And if the work under FREEDOS and i386 I can't belive that the disks are broken.
Nevertheless it is not critical for me, since I got the files from my i386 and moved it to my x86_64.
It's nice to see how you can bypass the install routine with open-source tools and a little knowledge how to use them :) .

But the main question is: Why does it not work?
Can you send the first 5 lines of the disks you formatted, please?
And also try to format a 1.44 disk to 720.

Greets,
Henne
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2006-05-04  9:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02 21:03 [KJ] 720KB Floppy on 64bit Linux Henne
2006-05-03 11:54 ` Henne
2006-05-04  0:38 ` Randy.Dunlap
2006-05-04  9:27 ` Henne [this message]
2006-05-04 17:01 ` Randy.Dunlap

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=4459C902.8090409@nachtwindheim.de \
    --to=henne@nachtwindheim.de \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.