Installer Path Problem

Hello everone. I a few others have had the same issue I just noticed but I am wondering when there will be an installer that does not have this problem anymore. Also I want to give my solution to this problem for others in case they read this posting.

Windows 2003 Standard Server x64 Edition

Lotus Domino 8.0.1 (32 bit) (Part # C18XPEN)

The first path that comes up is where to install the Domino binaries. This path shows C:\Program Files (x86)\IBM\Lotus\Domino. If you hit next, the data path will show something weird like this C:\Program Files(x86\IBM\Lotus\Domino)\data. Notice how the space between Files and (x86 is missing and how the right side parenthesis has moved over to after Domino. If you continue installing like this Domino will not work properly and the normal paths are dorked up.

My Solution:

When the installer ask for that first path I use the short name for Progra File (x86) which for me is progra~2. You can see the short name of your path by bringing up a command prompt window, going to C:, and typing dir /x then look to the left of Program Files (x86). My Domino binary path then is C:\progra~2\IBM\Lotus\Domino, and my data path then became C:\progra~2\IBM\Lotus\Domino\data

Of course using the Program Files directory will work fine or some other directory as long as there are no parenthesis in the path name. But I was wanting to get this to install in the C:\Program Files (x86) folder like it wanted to default to.

Does anyone know if there is a ticket in on this and if so when it is expected to be fixed?

Thank you

Subject: Reported in SPR…

I believe the issue has been reported in SPR#YYYY6SH8CL. However, the only reports of this type of error against the SPR seem to be related to previous releases and not 8.0.1.

Here is a technote:

Lotus Software Knowledge Base Document

Title: Incorrect default directory listed when installing Domino 7.0.2 on a Windows x64 OS

Doc #: 1252935

URL: http://www.ibm.com/support/docview.wss?rs=899&uid=swg21252935

The problem seems to be related to a limitation of the 32bit install shield code.