Search resumed, Win2K problems

[Patricia M Godfrey pmgodfrey@xxxxxxxx]

Carl and Robert: Many thanks for SE /NV. I suspected you had dealt with
the sequential search problem, but have never been able to find the docs
to U2 that say what to do to do X (only the ones that say Y does X).
About Win2000, I suspect the DIR-reading problems may be related to the
one with C:\Program Files in 9x that was canvassed here last April. I had
discovered that XyWrite 4 DOS could not read that directory accurately,
whether in it or out of it, though it could read other long-file names if
given their 8.3 version. Mike Shupp solved the problem with a long post,
from which I give the most relevant excerpts here:
"It turns out, "C:\Program Files" and some number of the subdirectories
under this -- Common Files, Accessories, Outlook Express, Net Meeting,
Web Publisher, and Windows Media Player -- are write-protected. When you
look at their entries in a top-level directory, you'll see that the R
(for Read-Only) and D (Directory) attribute bits are set. Most other
directories simply have the D bit set.
...What's also of interest in a high level directory is that these things
show up TWICE. One entry always has the form
	Long File Name (LFN) RSH V
in Mr. Norton's view of directory and immediately below, is
	LONGFI~1 D
That second entry is the classical 8.3 DOS filename that XyWrite wants to
deal with. The first is, of course, a Long File Name, and it discloses
the fact to us (and the operating system, and properly clued-in
applications) by all those attribute bits. Which is kind of a kludge, but
face it, with current operating systems we aren't exactly building for
the the ages.
So anyway once more, what shows up for "C:\Program Files" is
	Program Files (LFN) RSH V PROGRA~1 R D
Most Windows programs and old DOS programs ignore the read-only
attribute, and see this simply as a run-of-the-mill directory. XyWrite IV
bounces, evidently seeing PROGRA~1 as another (illegible) Long File Name
because of that set R bit. I suspect it reflects the state of technology
at the time XyWrite IV was hitting the market-- the developers knew of
LFNs, knew something about how they would be recognized, and also knew
they didn't want to touch such files and possibly screw up the names and
attributes, so they made the program err on the side of caution. Whereas
the older, less sophisticated XyWrite III.... Well, there's a Cost To Be
Paid For Progress.
Of course, the "solution" to the tilde problem is now obvious: In
Windows, Right Click on the offending directories in Win Explorer, select
Properties (the last entry on the menu), and turn off the Read-Only
check. Press Apply and you're set-- you can read the directory. In DOS,
use the "attribute -r" command. Believe me, it works."
	I seriously doubt that Fat32 is the cause of the problem. I have been
running XyDOS and XyWin for three and a half years on Fat32 hard drives
(Win 95 OSR/2, and now, since January, Win 98), with no problems beyond
the one with C:\Program Files. Of course, NTFS may be a problem, but I
believe others have said they've run Xy on 2000. Furthermore, on my
current system, Xy (DOS and Win versions) resides on logical drive D: in
an extended partition of a 6 Gig hard drive--not "near the front of your
hard drive (ie, under the 1024-cylinder limit)." (C: is 2.6 G, so D:
comes somewhere after that.)
	I would suggest looking at all the files in the XyWin directory with
dates later than 2-1-1995 (XyWin apparently finished being edited in Jan
95), calling them from XyDOS, or even another text editor if that isn't
working, and comparing them with someone's who has XyWin working under
Y2K. Does anyone know what XWUIF.UIF is or does?
Patricia