Gosev
26th September 2007, 04:45
Hi guys
I've been using NSIS since it turned 2, so since a little while back. I work in a game dev studio and basically I end up doing most of the installers (so that's something like 15 games x 5 languages, and that's without counting various versions for journalists, beta testers and so on).
I just wanted to add my voice to the 2Gb limit discussion. I realize that it is not trivial to change (and that it is due to int being 32 bit = 2Gb address space, not due to Win9x compatibility reasons).
When I'm creating retail disks (usually DVDs now) I create a multi part installer, either using CABs, or just separate NSIS scripts; this allows me not only to go over the 2Gb limit, but also to work faster, since I've organised my data into stuff that's big but doesn't change very fast (like cutscenes) and stuff that's small and changes a lot (configuration file, settings, etc.)
However, from time to time we release a game for download. To do that, it makes more sense to have only one file for download, which is where the CAB-type solution doesn't work for me. I could (and probably will have to) create a multi-stage installer, with a first 7zip file with no compression to tar the different files together, and a second NSIS installer to do the installation proper.
Mind you, I'm not saying removing the 2Gb limit will solve my problems, since we'll probably be hitting 4Gb downloads before the 2Gb limit is lifted :)
Gosev
I've been using NSIS since it turned 2, so since a little while back. I work in a game dev studio and basically I end up doing most of the installers (so that's something like 15 games x 5 languages, and that's without counting various versions for journalists, beta testers and so on).
I just wanted to add my voice to the 2Gb limit discussion. I realize that it is not trivial to change (and that it is due to int being 32 bit = 2Gb address space, not due to Win9x compatibility reasons).
When I'm creating retail disks (usually DVDs now) I create a multi part installer, either using CABs, or just separate NSIS scripts; this allows me not only to go over the 2Gb limit, but also to work faster, since I've organised my data into stuff that's big but doesn't change very fast (like cutscenes) and stuff that's small and changes a lot (configuration file, settings, etc.)
However, from time to time we release a game for download. To do that, it makes more sense to have only one file for download, which is where the CAB-type solution doesn't work for me. I could (and probably will have to) create a multi-stage installer, with a first 7zip file with no compression to tar the different files together, and a second NSIS installer to do the installation proper.
Mind you, I'm not saying removing the 2Gb limit will solve my problems, since we'll probably be hitting 4Gb downloads before the 2Gb limit is lifted :)
Gosev