Re: autosave--and mysterious EOFs

["..." yesss@xxxxxxxx]

≪ There's a pie-simple way to get rid of EOFs that truncate
the visibility (readability) of a larger file. Using
XYWWWEB.U2, just command:
	DEL26
This removes from the file the first EOF that it encounters
(replaces it with a space character). ≫

≪ I should have added that this powerful tool has to be
applied with brains! If you use it on a non-text file, i.e.
a binary file such as an EXEcutable, you WILL trash it. And.
moreover, the change that DEL26 makes is irreversible. So if
there is ANY doubt in your mind, make a backup of the target
file before you use DEL26. ≫

Since the issue has come up, I'll point out that
FIZFIX1A.EXE, the !xyWise EOF-zapper, as implemented
in !xyWise doesn't have this problem if the file has any
of a baker's dozen common binary extensions. But XYWWEB.U2
of course is a xyW4 add-on and Carlos's query referred
to a xyWrite 3.56 situation; !xyWise (including FIZFIX1A)
and !xyWiz are xyWrite 3 solutions (not to mention that
setting xyDos 4 d 1A=1 to zap midfile EOFs seems pretty
simple without involving U2, but what do I know).

I neglected to cite in my original msg one classic way
to introduce a destructive midfile EOF to a xyW file: Edit
a file previously saved or stored in xyW with an app that
doesn't manage EOFs. When you reopen the file in xyW the
original EOF is still present as are any data added past
the EOF. But the data past the EOF don't display, and if
you save or store, kiss the added data goodbye.

That's a piece of information that seems to get passed from
programmer to programmer only by word of mouth. I've never
read it in any book, and building an EOF-handler into apps
that will manipulate ascii files is really important.
..... Ciao. 						--a

======================================= adpFisher  nyc
	xyWrite 3 supplements !xyWise and !xyWiz +
	Wolfgang Bechstein's seafaring adventures:
http://www.escape.com/~yesss/ ========================================