From: Bernard Dautrevaux <DAUTREVAUX@microprocess.com>
To: "'John Cooper'" <John.Cooper@citrix.com>, mh@mike.franken.de
Cc: gnu-win32@cygnus.com
Subject: RE: uudecode?
Date: Sun, 31 Jan 1999 23:52:00 -0000 [thread overview]
Message-ID: <8135911A809AD211AF6300A02480D1750348C6@IIS000.microdata.fr> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1762 bytes --]
> -----Message d'origine-----
> De: John Cooper [SMTP:John.Cooper@citrix.com]
> Date: lundi 18 janvier 1999 11:33
> Ã: mh@mike.franken.de
> Cc: gnu-win32@cygnus.com
> Objet: Re: uudecode?
>
> mh@mike.franken.de (Michael Hirmke) writes:
>
> > >Can anyone point me to a reliable version of the command line
> > >uudecode.exe/uuencode.exe utilities for NT 4.0?
> >
> > Don't know, what you mean by reliable, but you can get the
> sharutils-4.2c
> > package, which contains uuencode/uudecode among other utilities
>
> These just don't work at all:
>
> $ cp c:/WINNT/NOTEPAD.EXE n.exe
> $ ./n.exe # works fine!
> $ uuencode n.exe n.exe > n.uu
> $ rm n.exe
> $ ls n.*
> n.uu
> $ uudecode n.uu
> $ ls n.*
> n.exe* n.uu
> $ ./n.exe
> zsh: exec format error: .\n.exe
> $
> $ ls -l n.exe
> -rwxrwxrwx 1 JCooper Domain_Users 594 Jan 18 10:37
> n.exe*
> $
>
> Any ideas what's wrong with it?
>
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...
Regards,
Bernard
>
------------------------------------------------------------------------
------
Bernard Dautrevaux
Microprocess Ingéniérie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel: +33 (0) 1 47 68 80 80
Fax: +33 (0) 1 47 88 97 85
e-mail: dautrevaux@microprocess.com
b.dautrevaux@usa.net
------------------------------------------------------------------------
------
>
-
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 Bernard Dautrevaux [this message]
1999-01-31 23:52 ` uudecode? John Cooper
1999-01-31 23:52 ` uudecode? Benjamin Riefenstahl
1999-01-31 23:52 ` uudecode? Anil K Ruia
-- strict thread matches above, loose matches on Subject: below --
1999-01-31 23:52 uudecode? Lincoln, W. Terry
1999-01-31 23:52 uudecode? N8TM
1999-01-31 23:52 uudecode? Tom St Denis
1999-01-31 23:52 uudecode? Mark Newnham
1999-01-31 23:52 ` uudecode? $Bill Luebkert
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? Earnie Boyd
1999-01-31 23:52 uudecode? Bernard Dautrevaux
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=8135911A809AD211AF6300A02480D1750348C6@IIS000.microdata.fr \
--to=dautrevaux@microprocess.com \
--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).