Hi all,
I remember that this question was already discussed here once.
I have an FSD which now works OK for directory browsing and reading bitmap
files + text files using TYPE + PE images using Quick View.
However, NOTEPAD.EXE does not works OK when reading a text file from my
FSD - it behaves exactly as if the file is zero size.
Does anybody remember what particular FSD functionality is used by NOTEPAD?
What is the place of the possible bug in this case?
regards,
Max
Empirically, if on Win2K, it looks as if NOTEPAD.EXE relies on full
memory-mapped file support. FastIoAcquire/ReleaseFile dispatches must be
supported.
-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Monday, August 21, 2000 8:01 PM
To: File Systems Developers
Subject: [ntfsd] NOTEPAD and FSD
Hi all,
I remember that this question was already discussed here once.
I have an FSD which now works OK for directory browsing and reading bitmap
files + text files using TYPE + PE images using Quick View.
However, NOTEPAD.EXE does not works OK when reading a text file from my
FSD - it behaves exactly as if the file is zero size.
Does anybody remember what particular FSD functionality is used by NOTEPAD?
What is the place of the possible bug in this case?
regards,
Max
You are currently subscribed to ntfsd as: xxxxx@ENGENIA.COM
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
In my case, in my FSD, I was not properly returning EA information back to
Notepad. The check to determine whether this is your problem as well is to
open a file remotely and locally using notepad.
Remote access to a file on a mapped drive using Notepad does not require
extended attribute information to be returned.
Local access to the same file, however, will generate a query for EA info.
HTH
UKO.