Failed install on windows xp sp3

Hi Stefano,

could you please send the contents of your installjammer registry directory? (found under program files or program files(x86))

In the mean time things to check

- antivirus interference

- did you fully unzip before installing

- do you have a non standard (eg 7zip) unzip utility installed?

Best Regards,
Lisa

There's tons of files.

This can be help?4760.20120913-164959.ccs_setup_5.2.1.00018_install.log

ps: i use the online installer, so don't unzip nothing

Hi Stefano,

I think the problem is that you are using a directory with a space. C:\Documents and Settings\Ste Stuk\Desktop   Please try with no spaces or accented/special characters and keep us informed.

Best REgards,

Lisa

Nothing has change... always get that failed

Hi Stefano,

- can you verify you did a fresh install not using any directories with accents or spaces?

- would you please double check you unzip utility/settings?  See this post as an example

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/214141/757650.aspx#757650

Please keep us informed.

Best Regards,

Lisa

Hello Lisa,

I have exactly the same problem Stefano describes.

Unfortunately leaving the install path to <C:\ti> as set by default by the installation-tool did not solve the problem.

It seems, as only the TI supplements are affected. The bare eclipse is installed properly and runs.

It's really frustrating, after trying for an entire day!

Best regards,

Paul

Hello everybody,

just found the following (http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv5):

CCS does not install completely/missing TI components : After installing CCSv5, if only Eclipse components are installed and TI components are missing, it is possible that some repos were not extracted properly. In such cases, check if there is a unzip utility in your system PATH. If so, remove or rename the utility temporarily from the PATH so CCS installer can use its own unpacking utility

Sounds very promising, will test it tomorrow, as soon as back in the office.

Regards,

Paul

It's very disappointing.

I really tried everything. Even deinstalled WinZip and WinRAR. Left the install path to <C:\ti>. It just won't work.

Any further ideas?

Unfortunately, copying the folders over from another machine may not be an option in some circumstances... like mine.

Another thread mentioned that a space in the path may be to blame.  I know, the xNIX world abhors a space, but this is problematic when Windows XP uses C:\Documents and Settings\username\ in the default PATH, where CCsetup likes to unpack it's files for install...

Has anyone tried renaming the PATH to a non-spaced path?

I can try setting the path, and let you know, but this is a bit frustrating.  I broke a perfectly good install with this point release.

Hello Scott,

As I wrote, my installation path was C:\ti. Besides that this is the path proposed by CCS, you can hardly go any shorter and there are no blanks in it as well. But it didn't work, unfortunately.

Renaming a path after intallation is not a good idea.

Are the problems possibly related to Java?

It would be fair if some TI employee would help solving this problem.

Regards,

Paul

Scott,

Didn't try the following, but you may.

As explained in the following post

  http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/214141/757650.aspx#757650

There will be a fix in CCS5.3, which addresses this problem. The release of CCS5.3 is not availabe, but the beta is out. So maybe you give it a try.

Regards,

Paul

Paul,

I'm not changing any of the default installation paths.  It is still C:\TI. 

What I planned on changing, is the %TEMP% environment variable.  The installer app places a number of files to %TEMP% during install.  In Windows XP (which is still used in this case, because of other loaded apps), The normal path to the TEMP folder includes spaces (C:\Documents and Settings\User\.... ), and is tripping up the CCS portion of the install.

I SOLVED THE ISSUE by changing the TEMP environment variable to C:\Temp, a folder without spaces.  This, in addition to renaming any instance of UNZIP.EXE in the PATH.  Doing so enabled a full and successful install.

As for your suggestion to use a beta in a production lab, my preference is to decline.  The release version has cost me quite enough downtime, thanks.

I submit this bug, that the Ti CCS portion of the installer routine may be at fault for not handling spaces in the PATH.  It is the only portion tha does not load successfully.

Scott,

great idea to chenge the TEMP file as well. And even better that it led to a successful installation.

Regards

Paul

P.S.: Of course you better don't use the beta if you have the released version running.

Thanks Scott,

I had the same problem and had gone through all the same scenarios. While I did not have spaces in my TEMP environment variable, it was an old UNZIP.EXE in the path that was the culprit.