This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I have just upgraded by computer with the latest nightly build, all seemed ok. FYI, I installed over a previous installation rather then remove and install. The computer worked fine until I started VS. This again worked fine for about 10 mins until I opened an existing model, and bang, the computer shutdown and restarted, without warning, loosing me some valuable work. I thought this may be a problem with the computer, maybe because using 64bit or VS2010? So I performed a similar upgrade on my laptop, 32 bit, VS2008, I again installed over an existing installation, this time I thought I will restart the computer incase any files locked or something. Then I opened VS, all seemed ok, until I opened a new model this time, and bang, the computer shut down again. This seems very strange, and dangerous, I already lost one lot of work. Do you have any idea why it would do this? I copied this from the Event Log, it was the same on both computers. The Windows Installer initiated a system restart to complete or continue the configuration of 'Mindscape LightSpeed 3.11'. |
|
|
I'm afraid we don't know why this might happen. As you know there is no need to restart after installing LightSpeed and I have no idea why Windows Installer would decide it needs to, let alone why it would restart the machine without prompting. Adding to the mystery is why it would do the restart only when you opened a model. The only theory I have is that this is some sort of Visual Studio issue where it remembers that it was asked to update a package while it had files locked, and next time it loads that same package it tells Windows Installer to restart the machine. However, I've tried a number of installs in different configurations, and have been unable to reproduce the behaviour, so this remains nothing more than a guess, and I'm afraid we therefore don't know how to prevent it from happening in future. Sorry. |
|