[amc49]

Hey, not trying to needle you. Just wanted your take on the term and I already realized it makes some sideways sort of sense. Like a screen freezeup or the BSOD on a laptop when software clashes or two things try to grab the same memory range or oldschool IRQ. It used to happen a LOT back when you only had a very few IRQs before software was devised to create virtual IRQs ro expand the adding of different equipment to the basic computer> Before that you had 'logic locks' left and right and you had to go and create free memory ranges or move IRQ devices around to get the new device working with whatever clashed with it.

 

[amc49]

What exactly is a logic lock? I build computers and have never heard of it. I of course have run into issues where a computer overlooks something written in software to reboot it and the next time it works fine and forever after. I call it vagaries of the electron world and usually not repeatable although it can be. When computers are made to learn with AI then they can learn bad as well as good and why 80% of your software is commonly protection rules against this thing or that from happening but still, sometimes it happens. Often a full power down forces those operating rules back front and center to remove corruption of instructions and take charge as intended. When software is used over and over it tends to get erratic, it can be physical RAM gates or drive locations or even the instruction may not error correct properly. A power off/on can often lay that back down nicely.

 

[amc49]

That logic lock thing is way stretching things to me. The 'Had a customer...' example could easily have been a simple low power situation that resolved by scratching battery terminals while putting them back on. Both that and the OP could easily have been simple low power problems, they can make some of the weirdest issues show up. AND, the computer has even caught it, the 12 volt system error is screaming the power is low along with putting the other issues in with it.