From: Jason Venner <jason@vennerable.com>
To: Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Total loss with 2.4.0 (release) (win98 not honoring partitioning)
Date: Tue, 23 Jan 2001 10:13:59 -0800 [thread overview]
Message-ID: <200101231813.KAA24039@echo.vennerable.com> (raw)
In-Reply-To: Message from Ragnar Hojland Espinosa <ragnar@fuckmpaa.com> of "Tue, 23 Jan 2001 13:43:33 +0100." <20010123134333.A1096@lightside.2y.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1986 bytes --]
Windows 98 and possibly followons doesn't quite honor 'b' type
partitions in the extended area of the disk, particularily if you are
past the 8gig boundary and the partitions in question are over 2gig.
The above numbers are NOT hard boundaries, I have only seen this on 2
computers and those numbers are approximate.
Generally, I have to use partition magic to make partitions past that
point if I don't want windows to scribble all over my other
partitions.
This is quite a nightmare, and not all that easy to diagnose or fix.
> On Tue, Jan 23, 2001 at 12:33:45AM -0500, Mike A. Harris wrote:
> > On Mon, 15 Jan 2001, Trever Adams wrote:
> >
> > >I had a similar experience. All I can say is windows 98
> > >and ME seem to have it out for Linux drives running late
> > >2.3.x and 2.4.0 test and release. I had windows completely
> > >fry my Linux drive and I lost everything. I had some old
> >
> > 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
>
> WS Windows might reprogram IDE / drives in some way that, being left in that
> state, conflict with linux's. .. well, ask Andre, he'll know :)
>
> --
> ____/| Ragnar Højland Freedom - Linux - OpenGL Fingerprint 94C4B
> \ o.O| 2F0D27DE025BE2302C
> =(_)= "Thou shalt not follow the NULL pointer for 104B78C56 B72F0822
> U chaos and madness await thee at its end."
> -
> 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/
>
-
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 18:15 UTC|newest]
Thread overview: 20+ 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
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 ` Jason Venner [this message]
2001-01-23 18:36 ` Total loss with 2.4.0 (release) (win98 not honoring partitioning) J Sloan
2001-01-23 20:17 ` Total loss with 2.4.0 (release) Mike A. Harris
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=200101231813.KAA24039@echo.vennerable.com \
--to=jason@vennerable.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