Thanks to Strel (and TC76 and all the people involved) for this useful tool.
I was trying to use only the .NET 1.1 part, and I got small pitfalls.
First, while my targets include Win2000 and Vista stations, I was building on XP64, which is seen as NT5.2 i.e. 2003 server (they share the same kernel). Even if I use WIN2K=YES in the .ini, the logic which discovers WIN2K3 according to the VER command operates, and then prevents the 1.1 installer to be built. The fix is obviously to check about the version only
if there are no explicit settings in the .ini. See attached patch to this effect
Number of downloads: 10
(GNU unidiff, against the version 20090316b.)
I am guessing the setting WINXP=YES will do the job to build a 1.1 installer for Vista, but I do not have checked it yet.
Second, for bare bones W2k targets (SP4 w/o IE6, which only have 2.0
Windows Installer), the /passive and /quiet and /norestart switches are not acceptable. It took me quite more time to come with a acceptable patch
, which doubles the %VERBOSITY% stuff with a %QSWITCH% (either qb or qn). It is still not perfect
, since for example it enables the Cancel button (and I do not know what /passive does, but I guess it doesn't). Also I broadly replaced throughout the script, but an educated guess is taht .NET 2.0 might require Installer 3.x at least, thus making it moot. Anyway I attach it in case anyone is interested.
Number of downloads: 16
Much more complex was the aim to have several
1.1 language packs (of course I am thinking about servers here, or MUI-enabled workstations). I succeded at manually building an installer which does that (by manually renaming the langpack.msi after their adminstrative installation), but I did not even try to enhance the script this way. Is there any interest?