Issue 33117 - Self-extracting installer for 1.x Windows
Summary: Self-extracting installer for 1.x Windows
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: OOo 1.1.3
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 1.1.6
Assignee: Martin Hollmichel
QA Contact: issues@tools
: 22137 28387 33827 (view as issue list)
Depends on:
Blocks: 33827 35917
  Show dependency tree
Reported: 2004-08-17 20:33 UTC by lsuarezpotts
Modified: 2006-10-09 16:21 UTC (History)
8 users (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---

hacky script to create 7zipped install archive (253 bytes, text/txt)
2004-09-16 18:18 UTC, Martin Hollmichel
no flags Details
Main NSIS file for creating the self-extracting installer. (14.15 KB, text/txt)
2004-09-22 08:36 UTC, justinclift
no flags Details
Script file for the NSIS installer to ask what type of install. (532 bytes, text/plain)
2004-09-22 08:36 UTC, justinclift
no flags Details
Recompress and InnoSetup builder 1.0 (English and Hungarian) (123.80 KB, application/x-compressed)
2004-09-27 13:30 UTC, kami911
no flags Details
Python script for rezipping installation files (1.95 KB, text/plain)
2004-10-06 20:54 UTC, stp
no flags Details
Icon for use with NSIS installer (9.90 KB, application/octet-stream)
2004-10-06 20:55 UTC, stp
no flags Details
NSIS script used for danish installer (1.68 KB, text/txt)
2004-10-13 07:14 UTC, stp
no flags Details
NSIS script for OOo 1.1.4 English self extractor. (1.59 KB, text/txt)
2004-12-09 16:11 UTC, justinclift
no flags Details
NSIS script for OOo 1.1.4 German self extractor + translated installtype.ini (1.35 KB, application/x-compressed)
2004-12-15 11:26 UTC, ingog
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description lsuarezpotts 2004-08-17 20:33:39 UTC
Daniel Carrera and Chad have found a way to compress Windows binaries by 30 percent. Compression 
takes place after initial release.  Proposal:

1. Binaries are created as usual
2. They are then made available to Daniel and co.
3. Daniel uploads them to stardiv or otherwise makes them avail for uploading
4. they are then promulgated. 

Comment 1 dcarrera 2004-08-17 23:42:19 UTC
I should point out that the change we've made is very simple.  Anyone with a
Windows computer (or wine) could do this:

   * Recompress all the f_* and f0_* files with zero compression.
   * Turn the entire directory into a self-extracting 7-zip archive with LZMA

That's it.  No need to edit any config files or hack anything.

Comment 2 stx123 2004-08-18 10:05:34 UTC
[changed title from "new compressed Windows binaries"]


could you please confirm the md5sum:
5c007bed5966753df887833274858f7d  OOo_1.1.2-kewl.exe

The file has been uploaded to the master at the location we use for 1.1.2
release candidates:
It's propagating to the mirrors.

I changed the name according to our file naming scheme:

I assume the self-extracting, 7-zip compressed version is another way to
distribute our standard Windows installation set. If don't see a need to use the
name of "1.1.2-kewl-4-skuul" and would prefer to use the standard entry "1.1.2"
in the setup.inf file.
Daniel, would you provide such a 7-zip file?

Please keep in mind that some documentation needs some additional paragraphs, if
we provide the self-extracting 7-zip-files for 1.1.x for all

Btw, is there a way to define a default extraction path during the creation of
the file? IMHO it's very convenient to extract to a directory (with a given
default name).

I hope that Martin will have a chance to follow-up with Daniel regarding a more
general process for future 1.1.x releases on

Greetings, Stefan
Comment 3 dcarrera 2004-08-18 17:23:35 UTC
The "1.1.2-kewl-4-skull" distribution was meant for testing.  We picked a
different name so that people would be able to test it without breaking their
existing 1.1.2 distribution.

I certainly didn't expect that we'd be doing this for the already existing 1.1.2.

I'll provide a non-kewl :-) 7-zip file as soon as Chad (the Windows guy) can
make it.  For the future, I really think we should have a spot in where
we can upload the file.  Louis says that IZ is not good for that.  So what
should we use instead? CVS?  I understand that CVS is even more complex under

Comment 4 lsuarezpotts 2004-08-18 17:34:16 UTC
Daniel: if the file is to be promulgated, then it should be simply ftpd (or whatever) to stardiv, for which 
you need Stefan's permission.

CVS is pretty simple under Windows, they tell me.

Comment 5 dcarrera 2004-08-18 17:47:33 UTC
CPH and I were just talking, and we have an idea.  We could provide two
distribution sets:

1) "Simplified auto-installer".
Here, the self-extractor would then call "setup.exe" to perform a standard
(non-network) distribution.

This would provide the easiest possible installation, and it would cover most users.

2) "Expert package"
Instead of a self-extractor, we provide a plain 7-zip file (and setup.exe is not

This would take care of the users who need to pass a flag to setup.exe (such as
-net).  The idea of not making it self-extracting is to allow the user to select
a different extraction directory.

Do you guys think this is a good idea?

Comment 6 lsuarezpotts 2004-08-18 18:47:38 UTC
Comment 7 chadley78 2004-08-18 19:26:20 UTC
Okay, I can see the point of having one that calls up setup.exe and one that doesn't...  But what benefit is 
there to having the one that doesn't call up setup.exe just a .7z file?

First of all, people can't open .7z files without 7-Zip.  From what I know, no other archival software opens the 
.7z format.

Secondly, with the self-extractor, you can still move the folder whereever you want it.

Thirdly, if we make it a .zip file, then we lose most of, if not all, of the size reduction we gained by using 7-Zip.

I'm not saying we can't do it that way, I'm just saying that I don't see the point.

-Chad Smith
Comment 8 stx123 2004-08-18 20:58:18 UTC
And please keep in mind that disk space at the mirrors is limited...
Comment 9 lsuarezpotts 2004-08-18 21:09:27 UTC
reassigning to martin to evaluate using 7 zip to compress by default all windows installer sets.

Daniel: we can have only one set per platform per build.

Comment 10 dcarrera 2004-08-18 21:25:25 UTC
Ok.  It was just a thought.  It seemed good at the time :-)
Comment 11 Martin Hollmichel 2004-09-16 17:17:42 UTC
just tried the stuff on 1.1.3, recompress with -mx=0, selfextracting archive
with LZMA and ultra compress, the setup (loader) hangs forever after deflating
the first file :(. can you provide the command line and parameters for each step ?
Comment 12 Martin Hollmichel 2004-09-16 18:16:00 UTC
works better with -tzip -mx=0 switch :)
Comment 13 Martin Hollmichel 2004-09-16 18:18:47 UTC
Created attachment 17755 [details]
hacky script to create 7zipped install archive
Comment 14 Martin Hollmichel 2004-09-16 18:19:51 UTC
does anybody has the command line for the sfx archive at hand ?
Comment 15 chadley78 2004-09-16 23:23:24 UTC
um, why were all the votes removed?

Where do we stand on this - are we a "go" for the 1.1.3 release?
Comment 16 Martin Hollmichel 2004-09-17 06:42:06 UTC
setting to fixed, although we still need the command lines for automation the
Comment 17 dcarrera 2004-09-18 23:35:08 UTC

Could you please report on how to produce the 7-zip compression?
I notice that people have asked.  I can't answer that because I don't have a
computer that can run 7-zip.  My part here was to re-compress the f_* files with
zero compression.

We need to know what flags/procedures/etc you used the installation team can
replicate the process.  We need this to include the smaller installer when 1.1.3
comes out (due out soon).

Comment 18 chadley78 2004-09-19 23:17:33 UTC
To create a self-extracting file on Windows using 7-Zip:

I took the uncompressed files that Daniel made, and downloaded them to my
desktop.  I then opened the folder using 7-Zip.  I then selected all of the
files within that folder and pressed the "Add" button (as in add to archive).

In the windows that followed, I selected these options:

Archive:  *Whatever you want to name it* OOo_113_windows.exe (the exe will show
up when you check "Create SFX archive")

Archive format:  7z
Compression Level: Ultra
Compression Method: LZMA
Dictionary Size: 32MB
Word Size: 64
Create Solid Archive: Checked
Update Mode: Add and replace files

And under "Options"
I checked the box marked "Create SFX archive"

Password is blank
Parameters is blank

all other boxes unmarked

Then I clicked "Ok"  a few minutes later, I've got an archive.

Hope that helps.

-Chad Smith
Comment 19 justinclift 2004-09-22 02:33:18 UTC
Arrrgh, this is seriously flawed.

Why are we creating a 1.1.3 installer that still requires the user to launch the
setup.exe themselves, when we can do so automatically by using NSIS instead of 7Zip.

That was the *whole point* of IZ 33827, to improve on from the 7Zip method.


Regards and best wishes,

Justin Clift
Comment 20 justinclift 2004-09-22 08:24:35 UTC
This is a self-extracting version that automatically launches "setup.exe -alluser":

This should be used as the self-extractor instead of the existing one that has
propagated to the mirrors.

Regards and best wishes,

Justin Clift
Comment 21 dcarrera 2004-09-22 08:27:30 UTC
I don't know if my opinion counts for this, but for what it's worth, I agree
with Justin.  The NSIS version is even simpler than the self-extractor.

Comment 22 justinclift 2004-09-22 08:34:25 UTC
The checksums for the NSIS version of the 1.1.3 installer are:

1219cca15dc520ae96f3f6fdc1772add *OpenOffice.org_1.1.3_english.exe

4328d89a8292b4de6c38f45ad53160dc9558b284 *OpenOffice.org_1.1.3_english.exe

Regards and best wishes,

Justin Clift
Comment 23 justinclift 2004-09-22 08:36:16 UTC
Created attachment 17854 [details]
Main NSIS file for creating the self-extracting installer.
Comment 24 justinclift 2004-09-22 08:36:56 UTC
Created attachment 17855 [details]
Script file for the NSIS installer to ask what type of install.
Comment 25 lsuarezpotts 2004-09-22 22:04:55 UTC
justin, why did you close the issue?
Comment 26 justinclift 2004-09-22 23:45:39 UTC
Sorry Louis,

I didn't know that I had, it was an accident.

Not sure how I did that.

Can you re-open it?

Regards and best wishes,

Justin Clift
Comment 27 lsuarezpotts 2004-09-23 13:53:25 UTC

Comment 28 justinclift 2004-09-24 05:33:10 UTC
Just had a thought...

For the self-extractor screen that asks what type of installation the user
wants, we'll need localised strings for each localised version to be created.

The text strings to be translated are:

 + Which type of installation do you want?
 + Normal Installation
 + Network Installation (experts only)
 + Auto-extractor

Regards and best wishes,

Justin Clift
Comment 29 kami911 2004-09-27 13:26:41 UTC
I created a little build env. to create smaller windows installation.
I recreated the (anti)recomprossor batch file under NT, then I created a
InnoSetup iss setup file...
I will try to send as attachment.
convert - the batch files, you should start 7zconv.bat
crea - temp extract, compress folder
dest - recompressed zip files go here
source - the source - original ooo files
ISSCR - InnoSetup script (work from dest)
LANGUAGES - InnoSetup Lanuguage resources - InnoSetup language includer
OUTPUT - Final Installer goes here

You will need IS latest 4.xx series to compile...

Comment 30 kami911 2004-09-27 13:30:43 UTC
Created attachment 17951 [details]
Recompress and InnoSetup builder 1.0 (English and Hungarian)
Comment 31 thegoldenear 2004-10-05 22:10:15 UTC
OOo112 unpacked is 65MB. OOo113 unpacked is 141MB. this seems quite an extreme
size difference. I am intending to distribute OOo on CD in a form that can be
installed directly from the CD using the '-net' option, called from a batch
script (as there's currently no UI for the multi-user install), and without the
.zip format offered for download, I now don't have room on the CD. is there an
explanation for this massive increase in size?
Comment 32 dcarrera 2004-10-05 22:32:07 UTC
No, you don't understand.  Those 65 MB are *still* packed.  The size has not
increased at all.  All the f* files (f_0001, ...) are actually zip files. 
Notice that the directory size for 1.1.2 is the same as that for the zip file.

What we did is package the program differently.  This means that the dowloadable
file is now only 45 MB instead of 65 MB.  The install size of OOo is exactly the
same.  Furthermore, now we don't require third-party zip software.

You should put the downlodable executable directly in the CD.  Don't unpack it.
 The user can select the file directly, and it will unpack on its own.

If you wish to discuss this, IZ is not a good place.  The best place, I think,
is the distribution list ( or

Comment 33 Martin Hollmichel 2004-10-06 06:41:34 UTC
reset target.
Comment 34 rail_ooo 2004-10-06 20:10:18 UTC
Script file for the NSIS installer which passes all command line parameters to
setup.exe and icon with gulls ;)
Comment 35 stp 2004-10-06 20:25:16 UTC
We should close either this issue or issue 33827.

And then rewrite the summary to a more generic: "Self-extracting installer for

I can't decide where to attach my NSIS scripts.
Comment 36 chadley78 2004-10-06 20:31:26 UTC
marking 33827 as a duplicate of this issue
Comment 37 lsuarezpotts 2004-10-06 20:48:07 UTC
*** Issue 33827 has been marked as a duplicate of this issue. ***
Comment 38 stp 2004-10-06 20:54:34 UTC
Created attachment 18180 [details]
Python script for rezipping installation files
Comment 39 stp 2004-10-06 20:55:22 UTC
Created attachment 18181 [details]
Icon for use with NSIS installer
Comment 40 stp 2004-10-06 21:14:02 UTC
Updated summary
Comment 41 kami911 2004-10-09 17:14:37 UTC
I compressed the 1.1.2, the size is 42,7 MB (44 793 378 bytes)
I will test with 1.1.3... Where can I upload my shrinked setup for testing?

Comment 42 kami911 2004-10-10 03:40:30 UTC
It is me again! I created a build with 1.1.3 Eng... The size of package is 43,1
MB (45297801 bytes)... So it is smaller tha current release. It contains a
little setup loader, with welcome screen, destination page, and task page (to
passing options to setup exe)... It is currently in English and Hungarian...
You may translate to your language:
ENG.OnlyExtract=Only Extract
ENG.MultiUser=Multi user
ENG.AllUser=All user
ENG.User=One user (not recommended)

Are you interested in my version?
Comment 43 stp 2004-10-13 07:14:03 UTC
Created attachment 18334 [details]
NSIS script used for danish installer
Comment 44 stp 2004-10-13 07:21:13 UTC
I have attached the NSIS script I made for the danish installer.

This danish builds an installer including an icon, lang = danish, uses the temp
directory, hides the installer while OOo's setup.exe is running and closes the
NSIS installer automatically when finished.

You still need the (translated) installtype.ini that Justin attached.

Thanks Justin for showing the way.
Comment 45 justinclift 2004-10-13 09:32:49 UTC
You're welcome.

From my point of view, I'm glad to see the effort that went into this being of
use to others.


Regards and best wishes,

Justin Clift
Comment 46 justinclift 2004-12-09 16:11:11 UTC
Created attachment 20320 [details]
NSIS script for OOo 1.1.4 English self extractor.
Comment 47 ingog 2004-12-15 11:26:10 UTC
Created attachment 20533 [details]
NSIS script for OOo 1.1.4 German self extractor + translated installtype.ini
Comment 48 pavel 2004-12-15 17:25:04 UTC
Do I understand it correctly that this installer also has some texts to translate?

Do we publish this installer also for big-10 languages?
Comment 49 ingog 2004-12-16 08:18:11 UTC
The installtype.ini contains 3 strings to translate.

The main ui from the installer is translated in 43 languages. You can include
one ore more language(s) and the installer tries to select the right one at runtime.
Comment 50 thegoldenear 2004-12-23 15:00:45 UTC
Why do you document this bug as fixed in 1.1.4 and include mention of a self
extracting executable in the installation instructions when you're still
releasing it is as a .zip file?:

Comment 51 jjr16 2004-12-24 00:32:14 UTC
I am wondering the same thing as thegoldenear, and also why the file size for
the Windows release is (currently) almost 65MB....?
Comment 52 jjr16 2004-12-24 01:29:33 UTC
OK, nevermind, I found out by browsing the releases mailing list that it was
decided to implement the self-extracting installer in 1.1.5 instead of 1.1.4.  I
see now that this issue has been reopened, even though the target milestone
currently says 1.1.4.
Comment 53 thegoldenear 2004-12-29 09:24:48 UTC
If this isn't implemented in 1.1.4 then the installation instructions shouldn't
be describing how to install using the self extracting installer:

And the list of issues new/fixed in 1.1.4 shouldn't mention this bug:

And this bug's target milestone should be set to 'OOo 1.1.5'
Comment 54 stp 2005-02-19 17:05:16 UTC
*** Issue 28387 has been marked as a duplicate of this issue. ***
Comment 55 justinclift 2005-02-20 13:45:42 UTC

Just ran the StarOffice 8 beta installer and it's unpacked and kicked off by
"NSIS 2.04".

Looks like someone in Sun really got the hang of NSIS, because the whole process
is very smooth.  :)

(Aint it funny to see where thing lead?)

Regards and best wishes,

Justin Clift
Comment 56 stp 2005-02-20 15:34:11 UTC
see also issue 4729
Comment 57 stp 2005-08-14 17:57:59 UTC
*** Issue 22137 has been marked as a duplicate of this issue. ***
Comment 58 lsuarezpotts 2005-11-28 16:04:08 UTC
can this be closed?

Comment 59 stp 2006-01-14 10:04:18 UTC
2.0 is out and self-extracting. I am closing this as WONTFIX being an issue for 1.x.

Comment 60 Martin Hollmichel 2006-10-09 16:21:33 UTC
close issue.