[Date Prev][Date Next][Subject Prev][Subject Next][
CAlling a Binary File
- Subject: CAlling a Binary File
- From: Carl Distefano cld@xxxxxxxx
- Date: Thu, 7 Feb 2013 00:36:08 -0500
CAlling a binary file in XyWrite is a big no-no. If you inadvertently
SAve it, the file is toast. Even if you REad instead of CAll, the
screen will often be skew-whiff (as Patricia liked to say) due to the
likely presence of control characters that were never meant to be
displayed in XyWrite. The on-screen result is a volatile, chaotic
mess. Still, if you're like me, you'll try to do it anyway.
Enter a new U2 routine, CAB, for CAll Binary file. CAB creates a
faithful yet inert rendition of any binary file for review in
XyWrite 4 or Nota Bene for Windows. It uses XYENC.COM's "B" option to
bypass encoding of most low- and high-order Ascii characters, with
further "cooking" of the encoded output. The original file is not
changed and stays out of harm's way. CAB works with any binary format
(.EXE, .COM, .PDF, .ZIP, .MSI, etc., etc.); it does a good job of
rendering the text portions of Word (.DOC) files (once you scroll
past the initial garbage).
With cursor on filename in directory listing:
XYENC.COM must be present in the directory that contains EDITOR.EXE.
CAB has been added to the XYENC.ZIP package, which can be downloaded
Here is frame CAB. XYDECode it, DeFine it, and issue ADD2U2
to add it to U2.