Hi Carl, and thanks for your reply:I have instituted your suggested changes, plus the following PATH statement in AutoExec.Txt, which was mainly a surmise on my part:PATH C:\xy-4017;C:\Xy-Util;C:\Xy-4017\Docs;C:\Xy-4017\Filters;C:\vDosXyIt looks like the **reported** errors are then down to "Keyboard repeat rate was not accepted", which I think I have seen in every setup regardless, going back to at least the XY under W2K days, so it is likely of little consequence, or not amenable to a fix anyway.But I think there is still plenty more configuring and adjusting to be done in various places, and that we have definitely not overcome all the bugs. I will cite other examples as they come to light, but here is one I saw right away. Executing the FIND command in search of the old sample text file LIBERTY, which is indeed there in the path and should be readily findable, I get a crashbox informing me that "vDos has stopped working." Can you replicate this ? Either way, I bet there will be more than a few like that. But so far this is much more hopeful, and I would call it progress.Jordan
From: Carl Distefano
To: xywrite@xxxxxxxx
Sent: Tuesday, January 27, 2015 2:04 PM
Subject: Re: new computer XY-DOS
Reply to note from J R FOX mailto:jr_fox@xxxxxxxx Mon, 26 Jan 2015
20:22:18 -0800
> Sorry Carl, but I have to challenge that claim.
But, Jordan, the evidence you adduce doesn't support the challenge!
The litany of error messages you cite has nothing to do with vDosXy;
they indicate that Editor can't find the directories and files that
it's looking for. It's a Xy setup error, not a flaw in vDosXy.
Try this. In AUTOEXEC.TXT, rem out or delete the drive assignments
you have now and substitute:
USE C: C:\
If your XyWrite setup is located on a drive other than C:, swap in
that drive too. For example, if your Xy setup is in F:\XY, do:
USE C: C:\
USE F: F:\
If XyWrite looks for document/data files on yet another drive, say
G:, add that drive as well:
USE C: C:\
USE F: F:\
USE G: G:\
Edit subsequent drive references in AUTOEXEC.TXT accordingly. For
example,
X:
cd \Xy-4017
would become
C:
cd \Xy-4017
or whatever the appropriate drive letter is.
Revert to all of your original XyWrite customization files:
SETTINGS.DFL, STARTUP.INT, .KBD, the lot. Now see what happens.
If you set up the directory tree in vDosXy to mirror the directory
tree in the host Windows system, that should obviate all of the "File
not found", "Path not found" errors you've been getting in XyWrite.