Atomic I/O letters column #161

Originally published 2014, in PC & Tech Authority
(in which Atomic magazine is now a section)
Reprinted here March 14, 2015
Last modified 14-Mar-2015.
 

"Sound off!" "One!" "One!" "I'm one too!"

I work in a 10-person office with what you might kindly call a "chaotic" Windows network setup, but it works well enough most of the time with no more than the usual shared printer that one computer can't see, shared files that some other computer won't access, etc. We've got laptops and drive boxes and stuff coming and going all the time so there's no one configuration for us to fix, and no pressing need for it. Except when everything goes wrong.

Sometimes, in some particular configuration, everybody starts being unable to see everybody else, even if we unplug/disconnect-from-wireless every computer and start adding them back again one by one. So far the debugging process has revealed that if we give computers fixed IP addresses, they are immune to whatever this is. So we could just do that with a poster on the wall that says who has what address so new stuff doesn't clash, but it feels as if I'm right next to the solution but can't see it. Any ideas?

C F

Netgear router DHCP settings
Turn DHCP on for one device on your network...
Noontec storage box DHCP settings
...and off for everything else.

Answer:
You've got DHCP-server problems.

The Dynamic Host Configuration Protocol lets any computer, and various other things like "network appliances" of various kinds, work as a server that hands out IP addresses to anybody who asks. If you set something to "obtain an IP address automatically", it'll use DHCP.

(If there's no DHCP server, you should give every device on the network a matching subnet, and a unique IP address, as I explain in a million-year-old article here. If devices are set to automatically obtain an address but no DHCP server is available to give them that data, modern OSes will fall back to randomly picking addresses in a pre-determined range and subnet. I believe this may have actually been witnessed to produce a functioning network, in the wild, somewhere in the world, on more than one occasion.)

The ubiquity of a DHCP server as a feature of every network box, though, makes it easy for a frequently-changed network like yours to end up with more than one DHCP server on it. One server is meant to be there, probably as part of a router that that connects its clients to each other and the Internet; the other server is probably in out-of-the-box default configuration and actually will in theory connect its clients to each other, but not to anything else.

There's a simple little utility called DHCP Explorer, available as a command-line version for various OSes or as a possibly-made-by-someone-else graphical version for Windows. Run it, click the button, and it sends a DHCP request and tells you what responds.

If only one server does (and it's the router-box or whatever you expect to see...) then whatever your problem is, it's not multiple DHCP servers. If you see more than one DHCP server, then you need to go to the setup page for whatever access point, drive box, computer or whatever that is, and untick the DHCP-server option.

 

Keep pressure on it! Don't you die on me!

My living-room computer is an old 17-inch Dell laptop, almost 10 years old, that I'm frankly surprised still works. Except yesterday it didn't work, and today it does again.

Yesterday, about the bottom third of the screen turned into vertical lined garbage. OK, fair enough, ancient laptop finally dies but maybe I can get a new screen on eBay or something, but as I was closing the lid I caught a glimpse of it coming OK again. So I opened it and poked and prodded and discovered that if I squeezed the left side of the bezel back against the case, the screen worked again. So I got one of those little spring clamps, the ones you use in carpentry to easily hold thin things together, and put that on the side in the appropriate place, and bingo, screen perfect again. I suppose a more permanent solution, allowing the lid to close again, would be putting one of those binder clips with the silver wire handles on it, and then removing the handle wires.

So that's great and all, but my question is, why does putting a clamp on the SIDE fix it? I don't know much about laptops, but I do know that the data cable goes into the BOTTOM of the screen. What's a loose connector or something doing half way up the left side?

Josh

Answer:
LCD monitors are one of those commonplace technological things that obviously can't actually work, like jumbo jets and, come to think of it, CRT monitors too. (Just wiggling electrons around in a hair-bun of wires at the back of a giant vacuum tube steers three beams of other electrons through onto pinhead patches of phosphor? Suuuuure.)

Every square pixel of an LCD is made of three rectangular subpixels, but the screen itself is a sandwich of multiple layers from a reflector at the very back, through polariser and colour-filter and switching and the actual liquid-crystal layers in the middle, to the (hopefully) scratch-resistant frontmost layer. Even the simple liquid-crystal display in a calculator or watch has at least six layers; an ordinary computer monitor can have nine or more.

Every subpixel has its own transistor, and those transistors have to all be wired up, and both the transistors and the wires need to be pretty much see-through or the light from the back of the sandwich won't make it to the front. So you end up with a layer of transparent indium-gallium-zinc-oxide transistors, which is pressed up against super-thin transparent metallic wiring on a layer of glass. If those layers aren't pressed together any more then the transistors won't have power and the screen will go white (LCD subpixels are black when the transistor is fully on, blocking all of the light from the backlight). If the layers are slightly separated, some transistors will be connected and others won't, and the display will show random garbage.

So the side of your old LCD has, presumably, separated just a bit. Clamping it together, even through the plastic casing from the outside, is enough to push the layers back into contact. The connection to the laptop mainboard is, as you say, at the bottom through the hinge, but there are lots more connections within the LCD itself.

 

Needs more gaff and JB Weld

As my girlfriend will tell you I am one of the smartest idiots in the world, so I would like to know if my latest invention is as brilliant as I think it is.

Inadvisable computer-fan double adapter

That is a fan double adapter made of two bits of paper clip wire. You push the wire through the bottom of the connector until it comes out the top, and then you can carefully plug the bottom connector onto the motherboard and another fan onto the top.

How bad is this idea? I know paper clips are steel and that's not the usual choice for electrical wiring... what else have I missed?

Liam

Answer:
It's a... moderately bad idea.

Steel indeed is not a very good conductor - around an eighth as conductive as copper - but a little bit of it passing a low current, as is the case here, won't be a problem. Five millimetres of steel will drop only about as much voltage as four centimetres of copper of the same diameter. Big deal.

But, first, the fans you double-adapt this way must not between them exceed the power-delivery ability of the motherbaord header.

Second, if the connector comes apart - and there's not much holding it together - the paper-clip wires could short out and pop a motherboard fuse. (You could make this less likely by putting a couple of dots of glue into the top of the double-adapted plug, to hold the wires in place.)

Third, make sure you only connect the power and ground wires, as in the picture, not the third speed-sensor wire or the fourth speed-control wire. (In the picture, the top fan connector has the third wire, the bottom has third and fourth.) Actually, the speed-control wires of a couple of fans could probably be spliced together and the mobo could control them together, but splicing speed-sensor wires would confuse the mobo deeply.

Fourth, there are more reliable ways to run extra fans, like with a Molex-PSU-plug-to-fan-socket plug adapter, or with a proper wired Y-adaptor with the same electrical structure as your paper-clip adapter. This is exactly the sort of thing you could whip up as part of learning to solder; you'll be able to do simple wire-to-wire joints like this within ten minutes of picking up a soldering iron for the first time.

So I'd categorise this not as "it's stupid, but it works", but more as "slightly too stupid to work properly".

 

There are worse fluids

Time for another "weird gunk in the computer" letter!

I've got a nice old clicky IBM keyboard, which was suddenly made less nice by a pile of cat vomit on it. Mindful of your past mention of it being OK to clean electronic equipment with tapwater, I just ran the hot tap over the affected regions of the keyboard, then dug out what was between the keys, popping off keycaps where necessary and putting them back on when done, then I shook the remaining obvious water out of it and left it in the sun for an hour and plugged it back in... and it doesn't work.

The num lock / caps lock / scroll lock lights come on in unpredictable ways, and no keys seem to work.

Have I hosed my keyboard by hosing my keyboard?

Reb

Charley, desk-stretching
Charley has never puked on the keyboard...
Charley invading the keyboard
...but he does press a lot of keys.

Answer:
Probably not. You just need to dry it out completely.

If you leave the keycaps on, it's difficult to get water into the workings of an IBM keyboard, or any other kind where the plastic caps cover "wells" that go down into the switchgear. (The wells also keep dust and hair and the other stuff that settles into keyboards out of the works, as you can see here.) Running water vigorously over the whole keyboard will get some water in there, though, and IBM keyboards, like everyday cheap rubber-dome keyboards, use a water-sensitive sandwich of circuit-matrices to do the actual switching.

(The click from an IBM clicky "buckling spring" keyboard is the sound of the spring buckling, not a conventional keyswitch. When the spring buckles, it moves a little see-saw device that connects pads on the circuit matrix. Other clicky keyboards are now widely available - they've become popular gear for PC gamers - and they all use discrete keyswitches, and may or may not be easier to drown than an IBM 'board.)

While the contact membranes of keyboard are damp, the keyboard won't work. This goes for all keyboards that have such a circuit in there, whether it's the capacitive type in an IBM keyboard or the simple switching matrix of an ordinary cheap rubber-dome 'board. Water can even stop those sealed floppy rubber keyboards from working, if they spring a leak.

(The rubber domes in cheap keyboards are both spring and switch for each key. The inside of the dome is conductive, and bridges contacts on the circuit sandwich when pressed down onto it.)

In some cases you may need to actually take the keyboard completely apart to clean it, or at least to dry it. But often you'll be fine if you just thoroughly air-dry the thing.

So take your damp keyboard, put it in front of an ordinary household fan, and leave it there for a long time. Like, a few days. If you put it out in the sun and the breeze it may be thoroughly dried in an afternoon, but it doesn't hurt to leave it longer.

Well, unless it rains, and returns you to square one.

 

Other letters columns

I/O #1
I/O #2
I/O #3
I/O #4
I/O #5
I/O #6
I/O #7
I/O #8
I/O #9
I/O #10
I/O #11
I/O #12
I/O #13
I/O #14
I/O #15
I/O #16
I/O #17
I/O #18
I/O #19
I/O #20
I/O #21
I/O #22
I/O #23
I/O #24
I/O #25
I/O #26
I/O #27
I/O #28
I/O #29
I/O #30
I/O #31
I/O #32
I/O #33
I/O #34
I/O #35
I/O #36
I/O #37
I/O #38
I/O #39
I/O #40
I/O #41
I/O #42
I/O #43
I/O #44
I/O #45
I/O #46
I/O #47
I/O #48
I/O #49
I/O #50
I/O #51
I/O #52
I/O #53
I/O #54
I/O #55
I/O #56
I/O #57
I/O #58
I/O #59
I/O #60
I/O #61
I/O #62
I/O #63
I/O #64
I/O #65
I/O #66
I/O #67
I/O #68
I/O #69
I/O #70
I/O #71
I/O #72
I/O #73
I/O #74
I/O #75
I/O #76
I/O #77
I/O #78
I/O #79
I/O #80
I/O #81
I/O #82
I/O #83
I/O #84
I/O #85
I/O #86
I/O #87
I/O #88
I/O #89
I/O #90
I/O #91
I/O #92
I/O #93
I/O #94
I/O #95
I/O #96
I/O #97
I/O #98
I/O #99
I/O #100
I/O #101
I/O #102
I/O #103
I/O #104
I/O #105
I/O #106
I/O #107
I/O #108
I/O #109
I/O #109
I/O #110
I/O #111
I/O #112
I/O #113
I/O #114
I/O #115
I/O #116
I/O #117
I/O #118
I/O #119
I/O #120
I/O #121
I/O #122
I/O #123
I/O #124
I/O #125
I/O #126
I/O #127
I/O #128
I/O #129
I/O #130
I/O #131
I/O #132
I/O #133
I/O #134
I/O #135
I/O #136
I/O #137
I/O #138
I/O #139
I/O #140
I/O #141
I/O #142
I/O #143
I/O #144
I/O #145
I/O #146
I/O #147
I/O #148
I/O #149
I/O #150
I/O #151
I/O #152
I/O #153
I/O #154
I/O #155
I/O #156
I/O #157
I/O #158
I/O #159
I/O #160
I/O #161
I/O #162
I/O #163
I/O #164
Dan's Data letters #1
Dan's Data letters #2
Dan's Data letters #3
Dan's Data letters #4
Dan's Data letters #5
Dan's Data letters #6
Dan's Data letters #7
Dan's Data letters #8
Dan's Data letters #9
Dan's Data letters #10
Dan's Data letters #11
Dan's Data letters #12
Dan's Data letters #13
Dan's Data letters #14
Dan's Data letters #15
Dan's Data letters #16
Dan's Data letters #17
Dan's Data letters #18
Dan's Data letters #19
Dan's Data letters #20
Dan's Data letters #21
Dan's Data letters #22
Dan's Data letters #23
Dan's Data letters #24
Dan's Data letters #25
Dan's Data letters #26
Dan's Data letters #27
Dan's Data letters #28
Dan's Data letters #29
Dan's Data letters #30
Dan's Data letters #31
Dan's Data letters #32
Dan's Data letters #33
Dan's Data letters #34
Dan's Data letters #35
Dan's Data letters #36
Dan's Data letters #37
Dan's Data letters #38
Dan's Data letters #39
Dan's Data letters #40
Dan's Data letters #41
Dan's Data letters #42
Dan's Data letters #43
Dan's Data letters #44
Dan's Data letters #45
Dan's Data letters #46
Dan's Data letters #47
Dan's Data letters #48
Dan's Data letters #49
Dan's Data letters #50
Dan's Data letters #51
Dan's Data letters #52
Dan's Data letters #53
Dan's Data letters #54
Dan's Data letters #55
Dan's Data letters #56
Dan's Data letters #57
Dan's Data letters #58
Dan's Data letters #59
Dan's Data letters #60
Dan's Data letters #61
Dan's Data letters #62
Dan's Data letters #63
Dan's Data letters #64
Dan's Data letters #65
Dan's Data letters #66
Dan's Data letters #67
Dan's Data letters #68
Dan's Data letters #69
Dan's Data letters #70
Dan's Data letters #71
Dan's Data letters #72
Dan's Data letters #73
Dan's Data letters #74
Dan's Data letters #75
Dan's Data letters #76
Dan's Data letters #77
Dan's Data letters #78
Dan's Data letters #79
Dan's Data letters #80
Dan's Data letters #81
Dan's Data letters #82
Dan's Data letters #83
Dan's Data letters #84
Dan's Data letters #85
Dan's Data letters #86
Dan's Data letters #87
Dan's Data letters #88
Dan's Data letters #89
Dan's Data letters #90
Dan's Data letters #91
Dan's Data letters #92
Dan's Data letters #93
Dan's Data letters #94
Dan's Data letters #95
Dan's Data letters #96
Dan's Data letters #97
Dan's Data letters #98
Dan's Data letters #99
Dan's Data letters #100
Dan's Data letters #101
Dan's Data letters #102
Dan's Data letters #103
Dan's Data letters #104
Dan's Data letters #105
Dan's Data letters #106
Dan's Data letters #107
Dan's Data letters #108
Dan's Data letters #109
Dan's Data letters #110
Dan's Data letters #111
Dan's Data letters #112
Dan's Data letters #113
Dan's Data letters #114
Dan's Data letters #115
Dan's Data letters #116
Dan's Data letters #117
Dan's Data letters #118
Dan's Data letters #119
Dan's Data letters #120
Dan's Data letters #121
Dan's Data letters #122
Dan's Data letters #123
Dan's Data letters #124
Dan's Data letters #125
Dan's Data letters #126
Dan's Data letters #127
Dan's Data letters #128
Dan's Data letters #129
Dan's Data letters #130
Dan's Data letters #131
Dan's Data letters #132
Dan's Data letters #133
Dan's Data letters #134
Dan's Data letters #135
Dan's Data letters #136
Dan's Data letters #137
Dan's Data letters #138
Dan's Data letters #139
Dan's Data letters #140
Dan's Data letters #141
Dan's Data letters #142
Dan's Data letters #143
Dan's Data letters #144
Dan's Data letters #145
Dan's Data letters #146
Dan's Data letters #147
Dan's Data letters #148
Dan's Data letters #149
Dan's Data letters #150
Dan's Data letters #151
Dan's Data letters #152
Dan's Data letters #153
Dan's Data letters #154
Dan's Data letters #155
Dan's Data letters #156
Dan's Data letters #157
Dan's Data letters #158
Dan's Data letters #159
Dan's Data letters #160
Dan's Data letters #161
Dan's Data letters #162
Dan's Data letters #163
Dan's Data letters #164
Dan's Data letters #165
Dan's Data letters #166
Dan's Data letters #167
Dan's Data letters #168
Dan's Data letters #169
Dan's Data letters #170
Dan's Data letters #171
Dan's Data letters #172
Dan's Data letters #173
Dan's Data letters #174
Dan's Data letters #175
Dan's Data letters #176
Dan's Data letters #177
Dan's Data letters #178
Dan's Data letters #179
Dan's Data letters #180
Dan's Data letters #181
Dan's Data letters #182
Dan's Data letters #183
Dan's Data letters #184
Dan's Data letters #185
Dan's Data letters #186
Dan's Data letters #187
Dan's Data letters #188
Dan's Data letters #189
Dan's Data letters #190
Dan's Data letters #191
Dan's Data letters #192
Dan's Data letters #193
Dan's Data letters #194
Dan's Data letters #195
Dan's Data letters #196
Dan's Data letters #197
Dan's Data letters #198
Dan's Data letters #199
Dan's Data letters #200
Dan's Data letters #201
Dan's Data letters #202
Dan's Data letters #203
Dan's Data letters #204
Dan's Data letters #205
Dan's Data letters #206
Dan's Data letters #207
Dan's Data letters #208
Dan's Data letters #209
Dan's Data letters #210



Give Dan some money!
(and no-one gets hurt)