The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Hans-Peter Jansen <hpj@urpla.net>
To: "Bryan O'Sullivan" <bos@serpentine.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA KT133 data corruption update
Date: Sat, 27 Oct 2001 14:22:52 +0200	[thread overview]
Message-ID: <20011027122255.36BFDFC2@shrek.lisa.de> (raw)
In-Reply-To: <1004179736.1615.19.camel@pelerin.serpentine.com>
In-Reply-To: <1004179736.1615.19.camel@pelerin.serpentine.com>

On Saturday, 27. October 2001 12:48, Bryan O'Sullivan wrote:
> After several months of begrudgingly putting up with my ASUS A7V
> motherboard corrupting roughly 1 byte per 100 million read during
> moderate to heavy PCI bus activity, I flashed VIA's 1009 BIOS this
> evening.
>
> I have not been able to reproduce any corruption since then (it was
> ridiculously easy before the new BIOS), and my machine seems otherwise
> as stable as I would hope.  This marks the first time since 2.4.6 that
> I've been able to run a Linus kernel without cowering.

Good news. Congrats.

> I also discovered, of necessity, a halfway manageable process for
> creating a DOS boot floppy using Windows ME, which Microsoft would
> apparently prefer was not possible.  I'll reproduce the steps here,
> since otherwise flashing a new BIOS is likely to be nightmarish for
> people stuck dual booting into WinME.
>
> Most of these steps occur under Linux, and I'll assume that your Windows
> Me "C:" drive is mounted as /dos/c.
>
> - Format a floppy:
>   fdformat /dev/fd0H1440
>
> - Create a FAT filesystem:
>   mkdosfs /dev/fd0
>
> - Mount the floppy:
>   mount /dev/fd0 /mnt
>
> - Copy across a few files:
>   cp /dos/c/command.com /mnt
>   cp /dos/c/io.sys /mnt
>   cp /dos/c/msdos.sys /mnt
>
> - Edit /mnt/msdos.sys, and change values as follows:
>   [Paths]
>   WinDir=a:\
>   WinBootDir=a:\
>   HostWinBootDrv=a
>
>   [Options]
>   BootMulti=0
>   BootGUI=0
>   AutoScan=0
>
> - Copy across your BIOS flash utility (probably aflash.exe) and BIOS
>   image.  Unmount the floppy (important; don't just reboot):
>   umount /mnt/floppy
>
> - When you reboot to the floppy, it will desperately try to boot into
>   Windows.  When it prompts you for the path to some Windows VXD, just
>   type "a:\command.com", and lo, you've got a DOS prompt.

Since your floppy doesn't contain a valid bootsector, it won't start
from floppy here. At least my mkdosfs created boot sector says:
This is not a bootable disk.  Please insert a bootable floppy and
press any key to try again ...

The simplest solution is choosing win(9*|me) from boot manager then, press
F8 immediately, select boot to command prompt. (Hope this works in me, too) 
Issue
c:\> sys a:
and
c:\> edit msdos.sys
then, as above. If booting from floppy still fails, check BIOS boot order.

Note: if you don't trust your winloose inst., check the created bootsector:
1) Label at offset 3 should read MSWIN4.1 or the like
2) some readable error messages at around 0x180 
3) IO      SYSMSDOS  SYS at ~0x1d8

BTW[FAR OT]: Somebody remember IHC here?

> Cheers,
>
> 	<b

Have-a-nice-stay-where-ever-you-are-ly yours,
FrisPete

  reply	other threads:[~2001-10-27 12:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-27 10:48 VIA KT133 data corruption update Bryan O'Sullivan
2001-10-27 12:22 ` Hans-Peter Jansen [this message]
2001-10-27 13:17 ` Jan Niehusmann
2001-10-27 15:11   ` Bryan O'Sullivan
2001-10-27 15:01 ` Tobias Ringstrom
2001-10-30 13:26 ` Sam Vilain
2001-10-30 13:39   ` Martin Eriksson
2001-10-30 14:19     ` Sam Vilain
  -- strict thread matches above, loose matches on Subject: below --
2001-10-29  2:50 David Grant

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=20011027122255.36BFDFC2@shrek.lisa.de \
    --to=hpj@urpla.net \
    --cc=bos@serpentine.com \
    --cc=linux-kernel@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