Bugzilla – Bug 10434
SqueezeCenter 7.3 does not Start on Windows Vista
Last modified: 2012-02-27 17:18:50 UTC
Created attachment 4501 [details] SC Log from 081220-002121 Ticket #081220-002121 **Very Similar to Bug 9284, but without the beeps**** Symptom: SqueezeCenter will not Start on Windows Vista Troubleshooting Steps: -Performed a Clean Install of SqueezeCenter 7.3 -Tried changing the Port -Uninstalled AVG, same result -Ran netstat -a to see if there was anything conflicting with the ports -Added Port Information to Windows Vista Built in firewall -Turned off UAC -Changed start-up options -Verfied that there are no other firewalls or security software See log file below: [08-12-22 18:19:54.3476] main::init (293) SqueezeCenter OS Specific init... [08-12-22 18:19:54.3486] main::init (348) SqueezeCenter binary search path init... [08-12-22 18:19:54.3504] main::init (351) SqueezeCenter strings init... [08-12-22 18:19:54.3937] Slim::Utils::Strings::loadStrings (111) Retrieving string data from string cache: C:\Documents and Settings\All Users\Application Data\SqueezeCenter\Cache\strings.bin [08-12-22 18:19:54.4020] main::init (354) SqueezeCenter MySQL init... ************************************************************************* Please note that the above log file is referring to "C:\Documents and Settings\All Users\Application Data\SqueezeCenter\Cache\strings.bin" But this is a Windows Vista Machine, this path does not exist!! ************************************************************************* Could this be due to an "Upgrade" to Windows Vista from XP, and somewhere in the registry it still has references to Windows XP file paths?? Thanks, LaRon
LaRon: Please have the customer try 7.3.1, do they have the same issue?
Customer responded, he will try when he get home. Also he stated that this was an HP that came with Windows Vista on it, and it is not an upgrade.
no new information from customer, closing bug for now. If you still see the issue, please comment and reopen the bug.
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version. If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.