From: "Trever L. Adams" <trever_Adams@bigfoot.com>
To: "Mike A. Harris" <mharris@opensourceadvocate.org>
Cc: Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Total loss with 2.4.0 (release)
Date: Tue, 23 Jan 2001 05:03:26 -0500 [thread overview]
Message-ID: <3A6D56EE.2070003@bigfoot.com> (raw)
In-Reply-To: <Pine.LNX.4.32.0101230026490.7610-100000@asdf.capslock.lan>
Mike A. Harris wrote:
> On Mon, 15 Jan 2001, Trever Adams wrote:
>
> I don't see how Windows 9x can be at fault in any way shape or
> form, if you can boot between 2.2.x kernel and 9x no problem, but
> lose your disk if you boot Win98 and then 2.3.x/2.4.x and lose
> everything. Windows does not touch your Linux fs's, so if there
> is a problem, it most likely is a kernel bug of some kind that
> doesn't initialize something properly.
Well, I boot into Linux, all is fine, rebooted into a different version
of Linux for some testing, all is fine (this was an older version, I
believe it was 2.2.14 or .15) Try to install ME and run it, seems ok.
Go back to Linux, and my drive was fried with Windows files all over it,
etc.
I know Windows shouldn't touch a Linux partition. But, apparently it
did. Or else Linux and/or Fdisk are fried and made a bad partition table.
> Windows sucks, and I hate it as much (probably more) than the
> next guy. It's not fair to blame every computer problem on it
> though unless you KNOW that Windows directly caused the problem.
I said what I did, because it seems the evidence said Windows did do it.
If it didn't, oops. I have talked with others and they had a similar
experience, so I am not alone.
> Pick one of the 1000000000 good reasons to say Windows sucks
> instead...
>
> For what it is worth, I have a similar problem where if I boot
> Windows (to show people what "multicrashing" is), if I boot back
> into Linux, my network card no longer works (via-rhine). Most
> definitely a Linux bug. In this case, "via-rhine.o" sucks.
>
> ;o)
Well, this is actually the second time I have had Windows write all over
my Linux partition. The first time I think it was not a bug in either,
but a bug in hardware. However, I no longer have that hardware as my
desktop.
Trever
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-23 10:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 21:50 Total loss with 2.4.0 (release) Trever Adams
2001-01-23 5:33 ` Mike A. Harris
2001-01-23 7:01 ` Alan Olsen
2001-01-23 10:03 ` Trever L. Adams [this message]
2001-01-23 10:32 ` Patrizio Bruno
2001-01-23 14:57 ` Trever L. Adams
2001-01-23 15:25 ` Richard B. Johnson
2001-01-23 11:27 ` Mark I Manning IV
2001-01-23 10:53 ` Ben Ford
2001-01-23 17:42 ` Mike A. Harris
2001-01-23 18:28 ` Mike A. Harris
2001-01-25 13:43 ` Kjartan Maraas
2001-01-26 21:40 ` Mike A. Harris
2001-01-26 23:12 ` Peter 'Luna' Runestig
2001-01-27 1:24 ` Mark van Walraven
2001-01-23 10:22 ` Heikki Lindholm
2001-01-23 12:43 ` Ragnar Hojland Espinosa
2001-01-23 18:13 ` Total loss with 2.4.0 (release) (win98 not honoring partitioning) Jason Venner
2001-01-23 18:36 ` J Sloan
2001-01-23 20:17 ` Total loss with 2.4.0 (release) Mike A. Harris
-- strict thread matches above, loose matches on Subject: below --
2001-01-15 13:40 Heikki Lindholm
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=3A6D56EE.2070003@bigfoot.com \
--to=trever_adams@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mharris@opensourceadvocate.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