Scope 4.5 Freeze and Crash - Out of nowhere

[soylent.green]

Hi planetz community,

Scope starts to freeze and crash with some devices that had worked in the past.

Today I've had a scope-crash with complete system freeze for C4T 0.4b and just now I've sent scope thinking about Spring03.mdl. What strikes me with Spring03.mdl is that SFP.exe is apparently doing "something" - it uses about 50% cpu. But the final result of thinking will be far more unpleasant than just "42", I guess. Most probably it will be like last time: It requires me to start my system again
What I already checked two days ago was my scope 4.5 installation. I thought that maybe some *.dsp or other importand stuff got corrupt but I wasn't able to find corrupted files. Then I tried to install the original files spring03.mdl and c4t...same result.

Hints anyone? (Please - Try to give me hints other than "install scope again" or "install complete system again". Thanks a lot!)

Peter

[astroman]

... What strikes me with Spring03.mdl is that SFP.exe is apparently doing "something" - it uses about 50% cpu. ...

well Peter, that is simply misleading - in fact the cpu may not 'do' anything (or much) at all. It is just locked, most likely in a closed loop which it cannot exit.
If you have a DualCore CPU my guess would be that the 'program loop' is running on one core and the condition check (to exit) happed to be loaded to the other one, so they'll never meet.
I have no evidence that this is the exact reason, but the precise 50% point into that direction (imho)

if they didn't already notice, you may adress the developers directly, as such conditions are not so easy to beta-test and you're input is certainly appreciated.
If the 'lock' is restricted to these devices, it's not a global Scope issue imho - for sure not need to wipe the disk...

cheers, Tom

[astroman]

he didn't change anything - he just installed a couple of 3rd party devices generated by Scope SDK.
You know that thing isn't really well documented ...

cheers, Tom