> cp froze at that point - I had hit the OK button to save the changes, I > did NOT hit start or anything else in the cp.
The issue here was that the CP tried to cnonnect to SC in order to store changed prefs. But as SC was not running at this point, it was timing out a lot. This issue should be fixed in the next nightly build. Thanks for the feedback! > minutes the cp program finally shut down. The squeezecenters also had > stopped (probably because 2 of them were running). When activating service mode, CP will run SC with some command line to tell it to register as a service. Therefore you could temporarily see two instances of it running. Again, there was some very optimistic implementation. This job was run on any click on Apply or Ok, not only when the startup mode actually had changed. > I went into the windows services control program and noticed that the > sc service was set to "manual". I changed that to automatic (was set to > automaticly start in the SC CP, by the way). This should be fixed too. > Noticed that the "start > automatically" was still set (even though it had set the service to > manual). The user and password were both blank again. You should now at least see the username. We can't store the password though. As the service is not re-registered unless you unregistered it before, this shouldn't be that big of a problem any more. > Typed them in > again and hit the OK button. System basically freezes. The _system_? As mentioned above the CP could lock up for a few minutes, but not the system. But I've never seen the system freezing. Anyway - please give the next nightly build another try. It should behave much better already. -- Michael _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
