Installers Lie

At work I have an SSD which is only 220 GB so it is almost full almost all of the time.  Gone are the days of lean software deployments, and I am a hoarder when it comes to information.  As a result, I was attempting to install DX Seattle on my SSD and Install Aware told me I had sufficient space after unselecting various features.

After proceeding, Install Aware told me it does not have enough!

In the end I did manage to free enough space to get DX Seattle installed, although it was like playing Russian roulette.  I ended up removing vital components for SQL Server Management studio that I then had to repair.

9 Responses to “Installers Lie”

  1. Joseph Mitzen Says:

    >Gone are the days of lean software deployments

    This reminds me of one thing I love about Linux: because of its package management, you don’t have static linking or multiple copies of DLLs scattered around the hard drive. Because most of the software is open source, many different programs tend to rely on the same libraries and the system will only need one copy installed. I can install a desktop distro that comes will PIM suite, office suite, IRC, IM, VOIP, mapping, image editing, image and audio management software, text editors, download managers, disk burning, PDF viewer, archiver, essentially everything your average desktop user needs and it will only take about 5GB of space! Even when I toss in everything and the kitchen sink in regards to development tools, virtualization, database management and business intelligence reporting, etc. that only takes it up to about 12 GB. This makes it feasible to carry around a full-featured bootable OS on a flash drive. There are several models out now that use SSD controllers, giving them hard disk-level random access, perfect for running an OS from.

    Meanwhile, a Windows 7 install takes up about 12GB without any additional software installed!

  2. C Johnson Says:

    It isn’t a lie, it is yet another sign that Embarcadero made a poor choice in installer.

  3. gverdile Says:

    I understood that you are like a lover that meet again an old girlfriend… Why don’t you give a try to Delphi 10S with a virtual machine installed on external usb 3 hard disk? Maybe you’ll find that some limits could be acceptable or leave definitely Delphi…
    I’m an old lover for delphi and I find some troubles on it but have many troubles with MS VS too…

  4. IL Says:

    Please give a vote to

  5. Peter Says:

    This is since Delphi 2005. The installer InstallAware is so bad. But Emba refuses to take Innosetup.

  6. Silver Warior Says:

    The main problem with current Delphi installer is its flawed workflow which looks to be something like this:

    1. Start of the installer
    2. username and serial key validation
    3. Retrieving certain data from user needed for installation (installation settings)
    4. Downloading one of the data packages (a compressed 7zip file) into selected “Download” location.
    5. Extracting that package usually containing separate installer (present in older versions, not sure for the newest) to temporary folder which resides inside “C:\ProgramData” folder
    6. Executing the extracted installer in so called chain link mode
    7. Loop back to 4. until all packages have been downloaded
    8. Remove temporary files that resided inside “C:\ProgramData” folder (in older versions this data wasn’t even removed)
    9. Finishing installation by registering some of the needed Libraries.

    So due to poorly designed workflow it can occur that installer would require a double amount of hard disk space.

    Now what can EMB do to solve these problems?
    1. Allow user to chose if he wants to keep downloaded files (no need to redownload them in case of reinstallation) or not
    2. Make sure that the files that were extracted from specific packages get immediately removed as soon as installation of that specific package is complete.
    3. OPTIONAL: Provide ability to directly download certain files to their final location.

  7. Gordon Says:

    While I agree that it is bad that the estimate and the installer check are not in sync. I have to wonder why you don’t upgrade your SSD. A 480GB SDD is about $125. And better one is maybe $50 more. So how much time do you waste on fighting for space all the time? I recently got my boss to approve an upgrade to a larger one and I figure I had a ROI of less than a month.

  8. Larry Hengen Says:


    I would have bought a larger SSD in the first place, but many organizations do not source hardware from Amazon and other places that have good pricing. They buy from their designated HP dealer that charges a premium. Since it’s my work machine, I’m not about to put any personal funds into it ;-)

  9. Jeroen Pluimers Says:

    You need about 60 gigabyte for a full RAD Studio XE7 and younger from ISO images. Lots of that is temporary disk space. About 20 gigabyte is required afterwards.

    It helps moving the content of %ProgramData% to a different drive and mklink to it.
    It helps compressing %Program Files (x86)% as it’s all readonly and NTFS has virtually no overhead.

    Most installers have a hard time estimating temporary disk space. RAD Studio derived products use excessive space so is especially bad about this.

    XE8 and younger clean out most of the %ProgramData% when the installation has finished.

    See my blog for some more in depth info around this.

Leave a Reply