On Wed, 19 Mar 1997, Ben C. O. Grimm - Libertatis Praesidium NL - wrote:
> In article <199703190555.RAA32265@rata.vuw.ac.nz>,
> "Chris Owen" <christopher.owen@vuw.ac.nz> wrote:
>
> > I've been trying to install Yarn 0.92 for Dos. I've been able to
> > read news and mail okay, but I've run into persistent problems trying
> > to post news or send mail. At the moment any attempt to said
> > something up brings up a pop-up menu with "cancel, send, edit, spell
> > check" etc etc, but the editor refuses to open the right file.
> > (Selecting edit causes a message reading something like "Can't open
> > c:\qedit\q.exe error 0"[?] to flash across the screen.)
> How does your 'editor=' line in your config look? Does it say:
>
> # editor program
> editor=c:\qedit\q.exe
One other (remote) possibility -- he might somehow have grabbed
the version that does not have Chin's fix for the DOS extender.
I forget, but didn't Chin have to pull 0.92 down right after he
released it, and put up a new copy with the same version number?
Seems unlikely that Chris got the bad one, but stranger things
have happened.
And it's easy to test -- just change the "editor" line in the
config file to read:
editor=%COMSPEC% c:\qedit\q.exe
As I understand it, this problem occurred when the DOS extender
was not set up right and was hogging all the memory in the session
where Yarn is running. Changing the line per the above spawns
a separate DOS "session," much like typing "COMMAND" at the C:\>
prompt, and allows the editor to run successfully.
(Using the more general %COMSPEC% instead of C:\COMMAND.COM covers
4DOS or other idiosyncratic setups.)
If this change solves your problem, there is a permanent fix you
can apply to the Yarn executable, which I won't go into unless
it's necessary. Let us know what happens, please!
-- Kevin <cannon@nic.com> http://www.nic.com/~handson.html