On Fri, 30 Oct 1998 12:26:21 GMT,
Ralf S. Engelschall <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 30, 1998, Dave Paris wrote:
>
> > Email over the exe and I'll create a self-extracting exe for you. Just let
> > me know where it should default (expand) to.
>
> Oh, I was not precise enough. What I actually want is not only a
> self-extracting program. My favorite would be that when I run patch.exe it
> extracts itself (in memory on in current working dir) and immediately runs
> itself. So I can use the packed patch.exe similar to the unpacked patch.exe.
> At least under my C64 times the years ago this was common practice. Exists
> such stuff for Windows NT? Or did I misunderstand you and you mean exactly
> this? Then it should unpack into the current working directory because this is
> maximum portable, IMHO.
Ralf, I don't see your point here. Why do you want to compress the
patch.exe file? The tarball distribution is a compressed file itself.
Do you have difficulty putting binary file into CVS?
I notice you have patch's source files in ./etc and compile and run it
for UNIX platforms. Can we do the same for Win32? The user must have
the C compiler in any case. I can prepare the makefile and modify
Configure.bat accordingly.
-trung
P.S. Info-ZIP can (almost) do what you want: compress the file, add a
small executable stub to that. The resultant file is a self-extracting
file, which extracts itself in a working dir. The catch is that the
stub is of fixed size; for small files (like patch.exe), it's too big.
patch.exe (~120K) -> patch_exe.zip (~60K) ...
unzipsfx.exe + patch_exe.zip
... ----------------------------> patch_exe_zip.exe (~150K)
Not good.
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
