From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Yuri Per <yuri@acronis.com>,
Martin von Loewis <loewis@informatik.hu-berlin.de>,
linux-kernel@vger.kernel.org,
Linux-ntfs@tiger.informatik.hu-berlin.de,
linux-ntfs-dev@lists.sourceforge.net
Subject: Re: [Linux-ntfs] Re: [Linux-NTFS-Dev] Re: ANN: NTFS new release available (1.1.15)
Date: Mon, 28 May 2001 18:50:59 -0600 [thread overview]
Message-ID: <20010528185059.A2290@vger.timpanogas.org> (raw)
In-Reply-To: <3B11E3F1.1090400@acronis.com> <5.1.0.14.2.20010526011903.00aab050@pop.cus.cam.ac.uk> <5.1.0.14.2.20010526000503.04716ec0@pop.cus.cam.ac.uk> <5.1.0.14.2.20010526011903.00aab050@pop.cus.cam.ac.uk> <5.1.0.14.2.20010527123154.00a96640@pop.cus.cam.ac.uk> <200105271253.OAA22557@pandora.informatik.hu-berlin.de> <3B11E3F1.1090400@acronis.com> <5.1.0.14.2.20010528125630.04729ba0@pop.cus.cam.ac.uk> <3B124DD7.1060908@acronis.com> <5.1.0.14.2.20010528154831.04438280@pop.cus.cam.ac.uk>
In-Reply-To: <5.1.0.14.2.20010528154831.04438280@pop.cus.cam.ac.uk>; from aia21@cam.ac.uk on Mon, May 28, 2001 at 03:49:28PM +0100
On Mon, May 28, 2001 at 03:49:28PM +0100, Anton Altaparmakov wrote:
> At 14:08 28/05/2001, Yuri Per wrote:
> >Anton Altaparmakov wrote:
> >
> >>Does anyone know what NTFS version the NT 3.1 / 3.51 volumes had? If I
> >>know I can make sure we don't mount such beasts considering we know the
> >>driver would fail on them... - I am aware of only one person stil using
> >>NT 3.51 and he doesn't believe in the NTFS Linux driver any more, so I
> >>guess we can just say we support NT 4.0 and above only.
> >
> >NT 3.51 uses exactly the same version of NTFS as NT 4.0 does.
>
> Ok. Thanks.
>
> Anyone know about 3.1?
>
> Anton
>
It's an HPFS variant. Try the HPFS driver, and it may work. The first cut
of NT was with a hacked up HPFS driver from Microsoft OS/2. NTFS was
designed internally by David G. and friends.
Jeff
>
> --
> "Nothing succeeds like success." - Alexandre Dumas
> --
> Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
> Linux NTFS Maintainer / WWW: http://sf.net/projects/linux-ntfs/
> ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-05-29 0:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 23:49 ANN: NTFS new release available (1.1.15) Anton Altaparmakov
2001-05-25 23:59 ` Jeff Garzik
2001-05-26 0:42 ` [Linux-NTFS-Dev] " Anton Altaparmakov
2001-05-27 11:23 ` [Linux-ntfs] " Martin von Loewis
2001-05-27 11:45 ` Anton Altaparmakov
2001-05-27 12:53 ` Martin von Loewis
2001-05-28 5:36 ` Yuri Per
2001-05-28 11:10 ` Martin von Loewis
2001-05-28 12:01 ` Anton Altaparmakov
2001-05-28 13:08 ` Yuri Per
2001-05-28 14:49 ` Anton Altaparmakov
2001-05-29 0:50 ` Jeff V. Merkey [this message]
2001-05-29 8:18 ` Martin von Loewis
2001-05-29 16:42 ` Jeff V. Merkey
2001-05-27 22:37 ` Anton Altaparmakov
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=20010528185059.A2290@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=Linux-ntfs@tiger.informatik.hu-berlin.de \
--cc=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=loewis@informatik.hu-berlin.de \
--cc=yuri@acronis.com \
/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