You're right I think. The issue is in 'strip or die.' It uses two saved values stripordie.audio_estim and stripordie.no_estim. It tests if audio_estim is null, and if so sets audio_estim to true and saves the result. This should happen the first time the script is run, and is fine as it can be changed during the set up. It does the same for no_estim, but instead of saving a value for no_estim, it saves audio_estim as false. Again, this can always be changed during set up, but the value of no_estim is never saved. Every time the script runs, it is null, and audio_estim is set to false.
I think the result is that if you run 'strip or die' without going through the set up, it defaults to non-audio estim device. audio_estim is false and no_estim is null. The script uses !no_estim to test for non-audio estim (!null = true), which means it tries to find the file usbcontrol.exe to control it, even if you have an audio estim or no estim.
If you go through the set up process, it all works, but because the corrected value for no_estim is not saved, you have to do it every time.
The question for 'the white queen' is should it follow 'strip or die' or should 'strip or die' be made more logical? There is no set up for estim in 'the white queen.' In any case, I think a script should test that a file exists before using it, either directly or using the groovy try-catch method. I have found working with files in sexscripts needs careful error trapping!
On a different tack, files called usbcontrol.exe have been associated with some old trojans and viruses. This means over-zealous malware detectors may have deleted the files. It goes to show that we should probably know exactly what a script does before running it.
Sorry for the long post. Any ideas?
|
But was a thrill and saved a trip to the gym with how many calories I must of burned jumping up whilst being shocked 
