Re: JAWS for DOS and NTFS file access?

  • From: arnaud <arnaudb@xxxxxxxxxxx>
  • To: jfw@xxxxxxxxxxxxx
  • Date: Tue, 28 Dec 2004 14:53:07 +0100

yes.

however, I prefer to warn you, file access is extremely slow with this
driver, and since JFD is also a TSR, it won't help.
but It works.


On Tue, 28 Dec 2004 07:59:37 -0500, you wrote:

>Hello Arnaud,
>
>Do you know if this NTFS DOD is compatible with JAWS for DOS?
>
>You wrote:
>From: arnaud <
>arnaudb@xxxxxxxxxxx>
>
>Subject: Re: JAWS for DOS and NTFS file access?
>Date: Mon, 27 Dec 2004 17:37:38 +0100
>
>you need to find ntfsdos, from
>www.winternall.com=3D20
>
>it's a read only driver, the read-write driver is quite expensive.
>
>On Mon, 27 Dec 2004 11:02:37 -0500, you wrote:
>
>>Hello listers,
>>
>>I used a DOS boot disk which includes JAWS for DOS to boot up my new =
Pc,=3D
>=3D20
>>which is a Windows XP Pro system. But when I attempted to change =3D
>directory=3D20
>>to access some text files, DOS informed me that it couldn't find =
the=3D20
>>specified directory.
>>
>>I did a dir on the root of my C: hard drive, and was surprised to see =3D
>that=3D20
>>very little was listed. The only directory shown was from a partition =
of=3D
> the=3D20
>>hard drive which is using FAT32.
>>
>>I recall reading something about how DOS could not access files stored =
=3D
>in=3D20
>>the NTFS format used by Windows XP. Is this the problem? Is there any =3D
>way to=3D20
>>get a DOS boot disk and JAWS for DOS to access files on an NTFS system?
>>
>>Alan

 --------------------
Arnaud de Bonald - Paris, France - Sysop Netcava BBS =
http://www.netcava.net
--
To post a message to the list, send it to jfw@xxxxxxxxxxxxx
To unsubscribe from this mailing list, send a message to 
jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at: //www.freelists.org/archives/jfw

If you have any concerns about the list, post received from the list, or the 
way the list is being run, do not post them to the list. Rather contact the 
list owner at jfw-admins@xxxxxxxxxxxxxx

Other related posts: