home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.barnyard.co.uk
/
2015.02.ftp.barnyard.co.uk.tar
/
ftp.barnyard.co.uk
/
cpm
/
walnut-creek-CDROM
/
CPM
/
XEROX
/
EDXE.LBR
/
EDFILE3.UPD
next >
Wrap
Text File
|
2000-06-30
|
3KB
|
53 lines
*** Note: This is a special version of EDFILE3 which I have named
EDXE.COM. It (and EDXE.DOC ) have been edited for use
on the Xerox 820, 820-II and 16/8 computers, in which
the arrow (cursor control) keys are defined to be CTRL-A
through CTRL-D, unlike any other computer I have heard of.
Therefore, just ignore the first paragraph of this update
message. Every thing else is valid.
Paul Foote May 22, 1987
EDFILE 3
UPDATE
1-12-87
Eugene L. Pizzetta
481 Revere Street
Revere, MA 02151
Voice - (617) 284-0891
This update was made to allow EDFILE to be used with CP/M
machines whose cursor keys default to WordStar's diamond pattern
(^S, ^D, ^E, ^X). Although the old version provided a patch area
for cursor codes, the ^E and ^X conflicted with built commands to
toggle between the hex and ASCII areas of the display and to
abort the edit, respectively.
The command to toggle between the hex and ASCII display areas has
been changed to ^T. The command to abort the edit has been
changed to ^Q. The documentation has been modified to reflect
these changes, as have the built-in help screens.
Two earlier patches have also been incorporated into this
version:
1. From Dennis Recla, Dallas, Texas, 1/10/84, fixing an error in
the Cursor up and Cursor down portion of the program. The
original version dated 01/09/84 had them reversed. The doc file
was revised to correct the same errors in it. I also added a
short paragraph describing the proceedure for writing the changes
to the memory buffer, and to use CTRL-C to write the memory
buffer to the disk.
2. From Clint Lew, South Bay Techincal Support RCP/M , 9/84, two
small bugs. The first bug limited the size of the file to which
direct jumps could be made. In the original version, for files
greater than about 8000H, the "dump relative address" or "A"
command would not consistently jump directly to all addresses.
(Actually the address jump limit was dependent upon the file
size). The second bug was a minor problem in that a jump to an
address which happened to be on a sector boundary would send you
to the block before the desired block.