: The test worked perfectly for me on my DOS PC .. for other DOS users who
: may be having trouble I extracted the newsitem direct to my local hard disk,
: (I use WinQVTNET 3.0) Editted the file as suggested by Jeff,
: undecoded it using EXTRACT (extrct32.zip) and
: uncompressed it using UMCOMP (comp430s.zip & comp430d.zip)...
: ALL availble from any good ftp site.
: I then simply copied the resultant end file to a postscript printer.
: Hopefully this may help out some others.
Thanks for that info Graeme. Who sez nothing good ever came out
of Oz ?
The two files for UNCOMP are on a Simtel CD-ROM ( Sept 1992 )
which is available on one of our local BBS's. So no need to use
a "good" FTP site :-)
I still have to find access to a postscript printer but it's
really reassuring to learn that you found it all so easy.
As a bonus I send you a prezzie of UUDECODE.COM and DOC taken
from the Starter Kit posted twice each month in the newsgroup
All you have to do is simply copy and save the file(s) and just
name them UUDECODE.COM and UUDECODE.DOC respectively.
No decoding - no nothing. An executable file in ascii text -
---CUT HERE--- Save as UUDECODE.COM
---CUT HERE--- Save as UUDECODE.DOC and read
UUDECODE uudecodes uuencoded files to original binary form. It is
compatible with the Unix (and other) uuencode/uudecode utilities.
Displays usage message, prompts for input file name.
UUDECODE [-o ][d:][\path\]filename.uue
Produces a uudecoded file, with the filename taken from
within the uuencoded file (which might include a path),
(provided the filename doesn't exist. Use the "-o"
(or "/o") switch to force overwriting of any existing
UUDECODE /? (or -?)
Writes a brief help screen to STDOUT and terminates.
UUDECODE checks for existing files with the same name as the newly
created output file. It will produce an error message and abort if it
finds one! (Use the "-o" switch to force overwriting existing files.)
UUDECODE will accept an input path\filename up to 80 chars long, and will
prompt if none is specified.
A uudecoded filename is taken from the uuencoded source file and is
written to the current directory (or to the path included in the file
Input files may be any length.
Uuencoded file headers (mailing headers, etc.) need not be removed.
However, any spurious lines between the "begin" and "end" lines MUST
Anything beyond the "end" line is ignored. If no "end" is found, the
output file is saved, but an error message is displayed.
Certain uuencoders append a "checksum" character to the end of each
uuencoded line. UUDECODE ignores these.
Uuencoded files generated or moved through a Unix system may have LF
(ASCII 10) line endings instead of the DOS-convention CR/LF (ASCII
13/10) endings. UUDECODE will handle those LF ends of line as well.
you MAY get a "end not found" message, but the uudecoded file will be
Certain systems and mailers will strip off trailing spaces on lines.
UUDECODE attempts to replace them.