Bug 5826 - Windows install hangs on last few nightlies
: Windows install hangs on last few nightlies
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Installer
: 7.0
: PC Windows (legacy)
: P2 normal (vote)
: ---
Assigned To: Squeezebox QA Team email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-10-17 05:54 UTC by jeffrey s miller
Modified: 2007-10-18 00:15 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jeffrey s miller 2007-10-17 05:54:55 UTC
Started noticing this on the 10/14, and on all versions up to 10/17. 10/8 was the last version I installed where this didn't occur. I'm using Windows 2k.

When I click 'Install' after specifying folder locations and start menu options there is up to a five minute wait before anything actually gets extracted. Once the unpacking starts it goes quickly and as expected (wizard comes up if I deleted prefs, scanning starts if not).

I've tried various combinations of uninstalling, installing over, and deleting the Squeezecenter folder, to the same effect. 

Following the hang up it does install correctly, but I get these in Event Viewer.

Event Type: Error
Event Source: Service Control Manager
Description:
The SqueezeCenter service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action.

Event Type: Error
Event Source: Service Control Manager
Description:
The SqueezeMySQL service terminated unexpectedly. It has done this 4 time(s). The following corrective action will be taken in 0 milliseconds: No action.
Comment 1 jeffrey s miller 2007-10-17 06:19:41 UTC
One additional note:

The process is-G7J95.tmp seems to be causing trouble. Killing the squeeze process in task manager doesn't get rid of the 
progress window, but killing this process does.
Comment 2 Michael Herger 2007-10-18 00:15:14 UTC
There was a fault in the uninstall logic which was waiting for a service to be shut down, before it actually was told to stop... change 13877 should fix this (to be expected in the 10-18 nightly build)