Xref: utzoo comp.editors:1325 comp.unix.questions:19905 comp.unix.wizards:20596
Path: utzoo!mnetor!tmsoft!torsqnt!jarvis.csri.toronto.edu!cs.utexas.edu!usc!ucsd!helios.ee.lbl.gov!ux1.lbl.gov!nolra
From: nolra@ux1.lbl.gov (Arlon Hunt)
Newsgroups: comp.editors,comp.unix.questions,comp.unix.wizards
Subject: vi on VMS Problem
Message-ID: <4857@helios.ee.lbl.gov>
Date: 14 Feb 90 19:11:52 GMT
Sender: usenet@helios.ee.lbl.gov
Lines: 12
X-Local-Date: 14 Feb 90 11:11:52 PST

Hello Usenetters,

I was running vi on our VMS system (I don't know who's the
vendor - all I know is that it's not the TPU version)
when some network problem interrupted the editing
session.  When I logged back on, and tried to do a
'vi -r fname', it gave me the error message:
'Can't Fork to execute recovery'.  From the temporary space,
I copied over the temporary files, which on VMS are called
$E$X01105.;1 and $R$X01105.;1.  What went wrong?  What is
forking?  And of course, what can I do to recover the editing
session (it would be difficult to reconstruct manually).  Thanks.