Groups | Search | Server Info | Keyboard shortcuts | Login | Register
Groups > alt.os.linux.slackware > #26205
| From | Rich <rich@example.invalid> |
|---|---|
| Newsgroups | alt.os.linux.slackware, comp.os.linux.misc, alt.os.linux.debian |
| Subject | Re: Debugging advice? |
| Date | 2016-02-03 11:46 +0000 |
| Organization | My Linux Box |
| Message-ID | <n8spbf$p8a$4@dont-email.me> (permalink) |
| References | <n8r57s$p3q$1@dont-email.me> <n8sdgk$hup$1@dont-email.me> |
Cross-posted to 3 groups.
In alt.os.linux.slackware no.top.post@gmail.com wrote: > In article <n8r57s$p3q$1@dont-email.me>, Rich <rich@example.invalid> wrote: > > In alt.os.linux.slackware noSpam@gmail.com wrote: > > > Some months ago I spilled a glass of warm water over the exposed > > > mother-board. Of couuse the systen stopped immediately, > > > apparently via the various safety circuits in the hardware; and I > > > cut the mains power. > > > > There is your major mistake. There are *NO* "safety circuits" in > > the hardware that protect against water spillage on a motherboard. > > > > You've damaged one or more components, and the *only* recovery will > > be a new motherboard. > > > --- Respondent snipped my original info. for his sales pitch ---- > OK, let's move beyond layman simplistic thinking. aka I want to speak > with the injun-year, not the sales clerk. You are speaking with the injun-year, Chris Glur. > Assume that your assistant spilled the water, while you were at Davos > for the week. So you don't know the simplistic answer/reason why > after several hours usage the system's kybrd & mouse fail. One is > ps2, one is USB. Because your water spill damaged the motherboard, and now some subset of components are operating just slightly outside of their engineered margins. When digital circuits operate just slightly outside of their engineered margins, the result is exactly what you see. Sometimes they work, sometimes they don't, for seemingly random occurrences. Your *only* fix is to replace the motherboard that *you damaged* with a new, undamaged, motherboard. And then to keep yourself far away from it because you have admitted that you can not be trusted to protect your things from damage by your own actions.
Back to alt.os.linux.slackware | Previous | Next — Previous in thread | Next in thread | Find similar
Debugging advice? noSpam@gmail.com - 2016-02-02 19:33 +0000
Re: Debugging advice? Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2016-02-02 12:05 -0800
Re: Debugging advice? Chick Tower <c.tower@deadspam.com> - 2016-02-04 18:18 +0000
Re: Debugging advice? Rich <rich@example.invalid> - 2016-02-02 20:57 +0000
Re: Debugging advice? no.top.post@gmail.com - 2016-02-03 08:24 +0000
Re: Debugging advice? Richard Owlett <rowlett@cloud85.net> - 2016-02-03 05:06 -0600
Re: Debugging advice? Rich <rich@example.invalid> - 2016-02-03 11:46 +0000
Re: Debugging advice? no.top.post@gmail.com - 2016-03-02 17:36 +0000
Re: Debugging advice? Haines Brown <haines@engels.histomat.net> - 2016-02-20 07:02 -0500
Re: Debugging advice? John Hasler <jhasler@newsguy.com> - 2016-02-20 07:42 -0600
Re: Debugging advice? "Carlos E.R." <robin_listas@invalid.es> - 2016-03-02 19:48 +0100
Re: Debugging advice? Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2016-02-03 00:46 -0800
Re: Debugging advice? Rich <rich@example.invalid> - 2016-02-03 11:48 +0000
Re: Debugging advice? Michael Black <et472@ncf.ca> - 2016-02-03 12:51 -0500
Re: Debugging advice? Rich <rich@example.invalid> - 2016-02-03 19:26 +0000
Re: Debugging advice? Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us> - 2016-02-03 14:27 -0800
Re: Debugging advice? philo <philo@privacy.net> - 2016-02-03 08:34 -0600
Re: Debugging advice? John Hasler <jhasler@newsguy.com> - 2016-02-03 10:06 -0600
csiph-web