I'm glad I'm not alone on that one too. I cheated by placing the
startup.int in two places. My default Xy directory (c:\xywrite) and in the
main disk directory (c:\). That's the only cure I've found for it so
far. Works clean for me. I'm still working on the icon
problem. It also has a glitch where you click on the text file that's
outside your main directory and it puts an unfamiliar icon on the window.
Not a serious problem though.
----- Original Message -----
Sent: Sunday, January 23, 2000 10:37
Subject: XyWrite + Win98SE glitch
I have just set up a new computer, and have run into a very
glitch. I am hoping that those familiar with Win98SE will have
suggestion, and that those who disapprove of Windows will
not burden the
list with excoriations, Itoldyousos, etc.
I use the latest versions of
both XYDOS and XYWIN. If I want to
edit an existing file, I start the
program by locating the file
in Explorer (actually PowerDesk) and clicking
on it. Each such
file has an extension associated with the pertinent
(e.g., *.xy for XYDOS). This posed no problem on my
computer with Win95 OSR2. It poses no problem with XyWin. But
XYDOS files, selecting one of them starts the program from the
directory as the file is in, rather than from C:\XY.
can't find STARTUP.INT, and it starts up
crippled. I can correct the
problem each time with CD \XY and
then RUN STARTUP.INT, but that is not
much of a solution.
I tried editing the file association so that
That gets XYDOS up and running correctly, but the
problem is that
it doesn't open the file that I clicked on. In a DOS
filespec would come just before the comma. If I put a
mark there, it would query me for the filespec. But
modification is no faster than starting up XY and then
the file with the CA command.
History and Sociology of
University of Pennsylvania
Philadelphia PA 19104-6304