Install program

[Magnum]

I am interested in learning how to install programs.

Something simple, like copy a program to a directory, inform the user, etc.

If my program doesn't use the registry, do I need to register it?

[donkey]

From the start menu select Run, in the dialog type iExpress, its a useful little install maker with a number of great options. You can also build scripts (inf files) to modify the registry, for versioning and a number of other functions.

Using iExpress technology

[jj2007]

From the start menu select Run, in the dialog type iExpress, ...

Very useful hint, thanks Edgar. It reports somewhat hilarious compression ratios ("85%" when the effective size is 120k from 60k sources...) but works just fine and allows a single prompt install.

[oex]

It reports somewhat hilarious compression ratios ("85%" when the effective size is 120k from 60k sources...) but works just fine and allows a single prompt install.

A simple Gateometric formular.... :lol

120 + 60=180 / 60 = 3 => 60 / 3 = 20
120 / 60 = 2 => 20 * 2 = 40 + 2 = 42 + 60 = 102 = 85%

[Magnum]

Thanks for the info gentlemen.

At my stage of development, my programs aren't complex.

The executable and a batch file to make a directory and install and uninstall may suffice.

I have some programs now that don't install in C:\Program Files.

[Vortex]

I have some programs now that don't install in C:\Program Files.

Hi Magnum,

Why not to create a portable application? The user should be able to select the installation directory.

[Magnum]

I will look up how to create a portable app.

I use a portable version of Firefox on my thumbdrive for when I go to the Senior Center.

[donkey]

I have some programs now that don't install in C:\Program Files.

Hi Magnum,

Why not to create a portable application? The user should be able to select the installation directory.

Not sure but I think that installing in C:\Program Files now requires an elevation manifest since any writes to that folder actually go to a shadow folder. However, and I can't verify this, if the name of the application is setup.exe the system will assume an elevation manifest and prompt the user for admin privileges. I seem to remember reading that somewhere but I can't find the reference anymore.

Edgar

[Antariy]

It reports somewhat hilarious compression ratios ("85%" when the effective size is 120k from 60k sources...) but works just fine and allows a single prompt install.

It uses makecab archiver - this is reason. LZX-21 compression pretty good, and may beat WinRAR and many other archives with some kinds of data.

makecab can be called from a command line - read its "help".

Though, makecab cannot compress directories, and may compress many files only if they are in a file with a "directives".

This is simple example of using makecab with maximal standard LZX:21 compression:

Code Select Expand


makecab /D CompressionType=LZX /D CompressionMemory=21 SomeFile.Ext


[Yuri]

However, and I can't verify this, if the name of the application is setup.exe the system will assume an elevation manifest and prompt the user for admin privileges. I seem to remember reading that somewhere but I can't find the reference anymore.

Maybe it's here: Inside Windows Vista User Account Control

The vast majority of installation programs require administrative rights, so the image loader, which initiates the launch of an executable, includes installer detection code to identify likely legacy installers. Some of the heuristics it uses are as simple as detecting if the image has the words setup, install, or update in its file name or internal version information; more sophisticated ones involve scanning for byte sequences in the executable that are common to third-party installation wrapper utilities.

[Magnum]

I started looking to see if makecab can be used as a file compressor instead of
relying on outside compressors.

Found some info here.

http://msdn.microsoft.com/en-us/library/ms916839

[Antariy]

I started looking to see if makecab can be used as a file compressor instead of
relying on outside compressors.

Found some info here.

http://msdn.microsoft.com/en-us/library/ms916839

Interesting article. Though, advise to use zip compression looking strange - MS uses LZX-21 to compress their things (like files in installations of WinNT v <6).

Needed to set CompressionType and CompressionMemory differently from the example - to have a lot better compression:

Code Select Expand


;*** Sample Source Code MakeCAB Directive file example
;
.OPTION EXPLICIT ; Generate errors
.Set CabinetNameTemplate=Sample.cab   
.set DiskDirectoryTemplate=CDROM ; All cabinets go in a single
  directory
.Set CompressionType=LZX; <---
.Set CompressionMemory=21 ; <---
  files
.Set UniqueFiles="OFF"
.Set Cabinet=on
.Set DiskDirectory1=SAMPLE.CAB
manifest.xml
WebPart1.dwp
SampleWebPartLibrary.dll
Image1.gif
help.htm
.Set DestinationDir=de-DE
de-DE\WebPart1.dwp
de-DE\image1.gif
de-DE\help.htm


[Magnum]

There are links from here to get all the cabinet utilities.

They have one that makes, view, etc. cabinet files.

Just follow the "yellow brick road."

http://support.microsoft.com/kb/310618

[Magnum]

The compression is comparable to Winzip as you can see if you run the bat file.

Now to see if the utility can be redistributed.

The utility was first used when floppies were common.

[Antariy]

tail...