From: Mark Newnham <mark.n@usa.net>
To: "'John Cooper'" <John.Cooper@citrix.com>
Cc: mh@mike.franken.de, gnu-win32@cygnus.com
Subject: RE: uudecode?
Date: Sun, 31 Jan 1999 23:52:00 -0000 [thread overview]
Message-ID: <95DE24D1FCFED0118B910060940A334006C31F@mailhub.adacorp.com> (raw)
The problem appears to be with the uuencode portion, because a file
encoded on a different system will uudecode correctly with the source
supplied.
If you compare a file encoded with the source code, against the same
file encoded on a Unix system, although the files are the same size,
each line on the Unix encoded file starts with a 'M' (or possibly the
'M' is after the newline on the previous. This does not appear with the
source code version.
Also when an attempt is made to decode a file uuencoded with the source
code version on a Unix system, the error "No end line" appears.
Excuse me for not being able to offer a solution, but this information
might help those more capable than myself.....
Mark Newnham
Application Design Associates, Inc
6021 S.Syracuse Way #302
Englewood, CO 80111, USA
+1 303 779 8958
-----Original Message-----
From: John Cooper [SMTP:John.Cooper@citrix.com]
Sent: Tuesday, January 19, 1999 7:40 AM
To: mark@adacorp.com
Cc: 'John Cooper'; mh@mike.franken.de; gnu-win32@cygnus.com
Subject: Re: uudecode?
Bernard Dautrevaux <DAUTREVAUX@microprocess.com> writes:
> I'm not sure, but I'll bet that you have to sligthly change
the uudecode
> source code to ensure that the open of the output file is
done in binary
> mode : open(... O_BINARY) or fopen(..., "wb")). Your problem
is most surely
> this infamous text!=binary feature :-( of Losedows...
It already does this - is there a known problem with `fopen'?
Do I need to use
`open' instead?
4 lines matching "open" in buffer uudecode.c.
9: FILE *out, *in = fopen(fname, "rb");
11: fprintf(stderr,"Impossible to open %s\n",fname);
33: out = fopen(outname, "wb");
35: fprintf(stderr,"Impossible to open %s\n",outname);
1 line matching "open" in buffer uuencode.c.
10: if ((in = fopen(nom, "rb")) == NULL)
--- John
-
For help on using this list (especially unsubscribing), send a
message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1999-01-31 23:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-31 23:52 Mark Newnham [this message]
1999-01-31 23:52 ` uudecode? $Bill Luebkert
-- strict thread matches above, loose matches on Subject: below --
1999-01-31 23:52 uudecode? Lincoln, W. Terry
1999-01-31 23:52 uudecode? Bernard Dautrevaux
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? Anil K Ruia
1999-01-31 23:52 ` uudecode? Benjamin Riefenstahl
1999-01-31 23:52 uudecode? John Cooper
1999-01-31 23:52 ` uudecode? Michael Hirmke
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? Glenn Spell
1999-01-31 23:52 ` uudecode? root
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? Pierre A. Humblet
1999-01-31 23:52 ` uudecode? Corinna Vinschen
1999-01-31 23:52 uudecode? Bernard Dautrevaux
1999-01-31 23:52 uudecode? Earnie Boyd
1999-01-31 23:52 uudecode? Tom St Denis
1999-01-31 23:52 uudecode? N8TM
1997-09-09 23:33 uudecode? John Cooper
1997-09-10 10:28 ` uudecode? root
[not found] <root@jacob.remcomp.fr's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Mon,>
[not found] ` <18>
[not found] ` <Jan>
[not found] ` <1999>
[not found] ` <19:42:30>
[not found] ` <+0100>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=95DE24D1FCFED0118B910060940A334006C31F@mailhub.adacorp.com \
--to=mark.n@usa.net \
--cc=John.Cooper@citrix.com \
--cc=gnu-win32@cygnus.com \
--cc=mh@mike.franken.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).