aabo@nntp-server.caltech.edu (Andrew Masami Abo) (03/09/91)
I uudecoded a uuencoded file and received the error: Short file. The resulting binary file was incomplete. What does this error mean and how can I fix it? The man page was unenlightening. I examined the uuencoded file and saw that both the 'begin' and 'end' statements were intact. I am running on SunOS 4.1.1.
henry@angel.Eng.Sun.COM (Henry McGilton) (03/11/91)
In article <1991Mar9.104048.21207@nntp-server.caltech.edu>, aabo@nntp-server.caltech.edu (Andrew Masami Abo) writes:
* I uudecoded a uuencoded file and received the error: Short file.
* The resulting binary file was incomplete. What does this error
* mean and how can I fix it? The man page was unenlightening. I
* examined the uuencoded file and saw that both the 'begin' and
* 'end' statements were intact. I am running on SunOS 4.1.1.
Right before the `end' statement of a uuencoded file there should be
what appears to be a blank line. That line should in fact have one
space at the beginning of the line. I have had the same experience
with a `smart' mailer removing the single space. The results is
uudecode complaining about a short file.
........ Henryjik@athena.mit.edu (Jonathan I. Kamens) (03/11/91)
In article <1991Mar9.104048.21207@nntp-server.caltech.edu>, aabo@nntp-server.caltech.edu (Andrew Masami Abo) writes: |> I uudecoded a uuencoded file and received the error: Short file. |> The resulting binary file was incomplete. What does this error |> mean and how can I fix it? The man page was unenlightening. |> I examined the uuencoded file and |> saw that both the 'begin' and 'end' statements were intact. |> I am running on SunOS 4.1.1. It means that the file was missing some data. It somehow got corrupted, despite the fact that it contains both "begin" and "end" lines. If you understand the uuencode format enough (the man page for uuencode should document the format), and if the corruption is simple, then you might be able to load the file into an editor and figure out what's wrong with it. If not, you'll have to get the file again, and hope that it doesn't get corrupted this time. One possibility is that there should be a line containing a backquote (`) and nothing else right before the "end" line, and that line is missing. Although, given that the binary file is incomplete, it seems likely to me that adding the line will not fix the problem, since I suspect that other data is missing as well. -- Jonathan Kamens USnail: MIT Project Athena 11 Ashford Terrace jik@Athena.MIT.EDU Allston, MA 02134 Office: 617-253-8085 Home: 617-782-0710
dichter@chdasic.sps.mot.com (Carl Dichter) (03/15/91)
Did anybody cover the obivious?
I have seen this message becuase the file containing the uuencoded
file was the same name as the file which uudecode is trying to create.
For example, if this stuff:
begin 644 LISTING
M("`@,2`N9'4M.3`M,#DM,3(*("`@,2`N9'4M.3`M,#DM,C@*("`@,2`N9'4M
M.3`M,3$M,3<*("`@,"!,25-424Y'"B`@(#0@4TE'4$Q!3B],1E`Y,"YC9G`*
M("`@,B!324=03$%.+TUI9%=E<W0N9C@Y"B`@,3(@4TE'4$Q!3B]/3U!33$$X
M.2YC86QL"B`@,38@4TE'4$Q!3B]03U!,.3`N86YN;W5N8V5M96YT"B`@(#0@
[deleted]
end
Was in a file called LISTING, you would get this error, and the
original file would be permanantly corrupted.
I'm sure you can guess how I found this out!
Regards,
Carl R. Dichter
Staff Software Engineer/Scientist
Motorola ASIC Division