Install issue with Halcogen-03.04.00-Alpha on Windows XP

Hi Eugene,

Sorry that you are having problems.  I tried the update/install and did not see this behavior so that gives me some hope that this is not a catastrophic issue with our installer.  Could you please describe your PC/windows configuration?  Is it possible that a subseqent dialog box from the install was/is behind the main window and waiting for an input?  Another (unfriendly, I know) idea is to do the install immediately after a reboot?

Brian,

Same yesterday, today, after re-download, reboot etc. There are few pop ups installer shows when it gets to this point but after they are gone it just sits there. No other windows that  I can find anywhere. Is there a dependency at this point which it waits for? It still flashes Hercules info.

Eugene

I'm sorry you are having trouble, Eugene.  Our engineer who handles the installers is out this week.  I will see if we have a backup assigned.  Is it possible to install on a colleagues computer, if only temporarily?

Brian,

It will most likely install on different PC. The question is why it is failing on mine now when other TI tools and previous versions of Halcogen would install just fine. As the test I downloaded and installed spnc019.zip(http://www.ti.com/tool/fmzpll_calculator) with no problems.

Looking forward to a solution.

Thanks, Eugene

Thank you

Hi John,

The current download of HalCoGen 3.04.00 is dated 1/11/2013.  Does this include the new installer?

Thanks, Charlie Johnston

As the software did not change, just installer, the release date remains the same for both versions.  The updated installer has a slightly different name Halcogen-03.04.00-windows-installer.exe whereas the original installer with the issue that Eugene saw was Halcogen-03.04.00-Alpha-windows-installer.exe.  The updated installer should be downloading by 5PM tomorrow.

I noticed the latest HALCoGen shown by the check for update application is labeled v3.4.0.   I get an Error: Wrong file size,  when I try update to it.

Sorry about that.  I forgot to update that value.  I have pushed an update that should correct this issue in about 15mins.

John,

Thanks.   The v3.0.4 update is working now