David C. Rankin composed on 2020-01-29 14:50 (UTC-0600):
Felix, if you like, I can write a short C program to
As should have been inferred from my previous post, that PC is not mine. Owner picked it up a few hours ago. Then I got a call that the screen was getting no signal. Turns out the PC powered up but didn't POST. I talked him through a process that got it on and him logged in and he was happy. Less than an hour later, he called with same problem. He also mentioned that after taking the side cover off as directed for examination of the POST code LED, he somehow was severely shocked, in a room with no carpet and average humidity. When I first got it here several days ago it wouldn't POST. I pulled CPU, repasted it, blew out the dust and tar, put it back together, and had no trouble with it over several days. This 62 month old PC is subjected to very heavy cigarette smoke. Something has probably tired of it, or the PS has gotten flaky, or some other hard to diagnose problem has arisen. I'm expecting it to return here in next day or two, but as to trying to diagnose the original problem, I doubt there is any practical way to duplicate or troubleshoot it. The optional user account where this occurred is there simply as a diagnostic aid of virtually non-zero use to the functionally blind owner. His previous PC only lasted 5 years or a little more before it got flaky. That was ultimately determined after he bought new PS, mobo, cpu, cooler and RAM to be his junk PS expired. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org