Atomic I/O letters column #56

Originally published in Atomic: Maximum Power Computing
Reprinted here April 2006.
Last modified 16-Jan-2015.

 

They're holding out on us

I've been an avid benchmarker of my PCs for a very long time now. As soon as I get a new PC, I load Windows, the relevant Service Packs and the latest drivers for all of the hardware. Then I sit down to a warm night of benching.

One day, after running through 3DMark05 (and watching my new PC crawl through the tests), a question started to bug me: If I buy the latest and greatest hardware, and it still performs like crap in these benchmarks, then what sort of 'off-world' hardware are these Futuremark guys using when they want to test their new benchmarks? If the new benchmark is designed to test the next generation of PC hardware, where are they getting their "next generation" hardware from? How do they know if their benchmark is going to turn out right?

I'll be able to sleep a few hours more each night if you know the answer to this.

Brett

Answer:
Hardware companies may give pre-release gear to some software makers - mainly game companies, but benchmarking outfits as well - but lead times are pretty short in PC hardware. No game coders are signing NDAs and collecting their GeForce 15000s yet.

Instead, people writing code for hardware that doesn't exist yet use emulation. Sometimes that emulation's running on a more powerful (or at least much more expensive) system, like a workstation or the custom development boxes that console coders use, but it doesn't have to be. You can emulate any level of 3D acceleration on pretty much any other hardware. If necessary, you can do the whole darn thing in software, through any video adapter at all.

That's achingly slow, of course, but it's not necessarily a big deal for most game development. There's a lot to a game besides the graphics; most of the development can be done with low-polygon basic-shader placeholders, and indeed may have to be, since final art for a modern game can take a very long time to finish.

Futuremark are an extreme case, because 3DMark can be thought of as a severely unfinished game. If you're writing a real game, you have to be careful not to add features that you're later going to have to take out to get the thing to run tolerably well on normal computers. Futuremark don't have to worry about that - the whole idea of each new 3DMark version is that it should bring current hardware to its knees.

Emulating future hardware doesn't work perfectly, because the specifications the emulator's written to match - and against which the final code is probably checked for official correctness - don't necessarily match what the graphics chip companies end up implementing. But it beats building a time machine.

 

Insufficient redundancy cycles

Every so often a CD I have will fail (usually a backup CD) and the error message I get is a "Cyclic Redundancy Check". Most of the data on the CD can be read, however some cannot. I'd like to know exactly what a Cyclic Redundancy Error is. Some sort of failure within the CD? Is there any way to fix the problem and recover the data?

Tom

Answer:
Cyclic Redundancy Check, or CRC, is a very simple error-detecting system. It's computationally cheap and it doesn't need much space for the "hash" it produces from the input data, so you'll find CRC error detection all over the computing world. On CD-ROMs, the CRC data is in one of the "subcode" channels that are evenly distributed through the disc along with the data you can actually access.

When you get a CRC error, that just means the data on the disc is corrupted for some reason (or, less probably, that the data's fine but the CRC's corrupt). Almost always, this is because of disc damage. There's nothing you can do about it (besides checking the disc for muck or scratches you can possibly repair - see this column), because CRC doesn't provide any facility for error correction. CRC tells you when something's wrong, but it can't fix it.

To recover as much data as possible from a damaged CD or DVD, try IsoBuster.

 

Roughing it

I'm heading out on a road trip out west soon, and as such my only source of power will be a 650W generator. I was wondering whether or not it was a good idea to charge my TPG widescreen laptop off the generator, or whether the irregular spikes would be too much for the power supply to handle?

Mike

Answer:
It ought to be A-OK. Switchmode power supplies of all kinds, including PC and laptop PSUs, are completely insensitive to power waveform, so they'll run fine from the output of any inverter or generator, even if it's an ancient squarewave unit that'll pretty much set a power drill on fire.

There's always the possibility of disaster, of course, and the management assumes no responsibility blah blah blah. If the generator's old and crusty (or just cheap and nasty) then it might be outputting too high a voltage, or have really spiky output that might cause problems. But, realistically, you're probably going to be fine.

 

Say it ain't so

LCDs don't get screen burn? Yes they do. But how?

My brother bought a very expensive flat panel LCD monitor, a nice 19 inch one that rotates on its stand for portrait and landscape view.

The other day I plugged it into my laptop, and at the bottom of the screen, while the light blue Windows booting screen was on, the Windows XP Taskbar was clearly visible. With my brother's system tray icons and everything. I was booting Win2K, so I know it wasn't mine!

The screen's not more than a year or so old, and I've never seen this on any LCD before, and indeed thought it was impossible. I just wondered if you had ever heard of this before?

Jason

Answer:
Yes, LCD screens can suffer from "image persistence". It's not burn-in, though, in the CRT or plasma sense. The subpixels aren't actually getting any dimmer anywhere on the screen, and the "burn-in" shouldn't be visible when the monitor's displaying a white screen. But some sort of capacitive build-up does happen, giving the subpixels a bias depending on what they've been displaying for a long time.

The cure is supposed to be just turning the monitor off for a while (power-saving screen blanking ought to do the job, too), but it might be an unfeasibly long while. Some people report the image persistence just doesn't go away, and so might as well be CRT-style burn-in.

And, heck, maybe sometimes it is. It's not ridiculous to suppose that the characteristics of the thin film transistors in the LCD panel sandwich might change depending on how long and how often they're turned on. If this is the case, though, I don't know which kinds of panel are particularly susceptible.

Find more info here and (cursorily) here. There's a neat-o picture here.

 

Buzzkill

My PSU had been vibrating a lot lately so I decided to take it apart and oil the fan. One thing I forgot was the orientation of the fan, but I figured it would be better if the fan sucked cool air from the outside and blew it over the heat sink.

My question, though, is: Was there any real danger in taking apart the PSU, or am I obscenely lucky to be able to type up this email?

I didn't take any real precautions; just unplugged the computer and pressed its power button before opening it up.

Davo

Answer:
Your guess about the fan direction is logical, and perfectly matches the way PSU fans were meant to work in the original ATX spec. And it's wrong.

The standard airflow direction for PSU fans, enshrined in the revised spec that codified what everyone was doing anyway, is from the inside of the computer case to the outside. Yes, that means the PSU's breathing air that's been warmed by the computer, but it also means it's contributing to throughflow ventilation of the case. Front fans are, by convention, intake fans.

If you want to set your case up so the air flows back-to-front or top-to-bottom or whatever, that's fine, but if you've got a PSU fan and a front fan that're both trying to suck air into the case, they'll be fighting each other. You have to make sure that all of the fans are turned to match your brilliant ventilation scheme.

It is, however, pretty safe to open up a PSU that's not still plugged in.

The big electrolytic capacitors in PSUs can hold a charge after the PSU's turned off, but probably won't. Well-designed PSUs put bleeder resistors across their caps when they're turned off, draining them long before you could finish unscrewing the casing.

There's always the possibility that you've got a badly designed or faulty PSU, though. In that case, caps can hold a charge for ages (as in, weeks, easily). For that reason, treat all caps as if they have barbed rusty spikes sticking out of their terminals, until you've put a meter across them or just discharged them yourself (with, by preference, a resistor across the terminals; it's fun to discharge a cap the bang-and-weld way by sticking a screwdriver across it, but that's not good for the component).

If a cap is charged to some risky voltage, touching its contacts (or things connected to those contacts) will only give you a brief scary jolt at worst, unless you manage to touch one contact with one hand and the other contact with the other, in which case the jolt will be across your chest, which can be Bad.

Shocks from hand to foot can be lethal too (hand charged, foot earthed), but actual "primary" injuries from electric shocks, where the shock itself is what hurts you, are actually surprisingly rare. People who're injured by electricity are usually, in fact, injured because muscle spasms make them fall down and hit their head, jump off their ladder, stab themselves with their screwdriver, or whatever. If you're sitting at the kitchen table fiddling with an unplugged PSU, there probably aren't many such hazards waiting for you.

All usual disclaimers apply, of course. If anyone out there lights themselves up as a result of following my advice, then I never said a thing.

 

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)