Dan's Data letters #4

Publication date: 22-Oct-2002.
Last modified 03-Dec-2011.

 

Lighting up

I'm about to put lights inside my computer and I'm having trouble figuring out which would provide more light: a blue 20cm (tube size) neon from Brisbane Car Sound which runs from a 12V cigarette lighter plug, or a few red or yellow LEDs?

With the neon I'll obviously have to convert the cigarette lighter plug to a Molex plug, but would a neon of this type be safe to run from my PSU without blowing it up? The neon only costs about $AU20.

Also, if I were to use LEDs, which colour out of yellow and red would be the brightest for my case? At Jaycar there are yellow 5mm 5000mcd LEDs and red 5mm 6500mcd LEDs. Also, I was wondering how many I would need to supply sufficient lighting to the inside of my case?

Benjamin

Answer:
The tube (which, being blue, doesn't actually contain neon; actual neon glows orange-red) should be much brighter than an array of 5mm LEDs, unless you put a few dozen LEDs in the array. Some cheap tubes are miserably dim, but most aren't.

The tube should also be perfectly safe to use in your PC. Sometimes RF from cheap tubes' power supply can cause issues, but that happens with the ones that are allegedly meant for use in PCs as well. LEDs have no such problems, since they're low voltage all the way. LEDs, if not severely overdriven, will also greatly outlast cheap tube lights. The nastier tubes have been known to drop dead after a couple of weeks; you can generally expect a much better lifespan than that from a half-decent tube, but LEDs will last effectively forever; don't overdrive them and, according to the most frequently quoted manufacturers' spec, they'll still be at 80% of their original brightness after ten straight years of service.

Regarding brightness - the higher up the spectrum you go towards green, the brighter an LED with a given output power will look, all things being equal. 100mW of red LED light looks dimmer than 100mW of yellow, which looks dimmer than 100mW of green, assuming they're all pushing the same number of actual photons. 100mW of blue looks dimmer than the same amount of green, because now you're past the eye's peak sensitivity point, but it'll still look much brighter than 100mW of red.

Then again, red and yellow LEDs are cheaper than green and blue ones.

Millicandela (mcd) ratings are affected by focus. The tighter the LED's beam, the more millicandelas it'll score for a given actual power. Most Jaycar stores have demo breadboards with LEDs on them so you can see how bright they really are; if the LED you want isn't on show, pester someone to set it up.

How many you'll need for sufficient illumination depends on your definition of "sufficient". Many people find cold cathode fluorescent lights (CCFLs - the super-thin gas discharge tubes) are too bright. Generally speaking, I'd say 16 recent-model high intensity yellow LEDs would give you enough light for a case. Just a few of them would still be noticeable, though.

Given how cheap LEDs are (in small quantities, at least), you could easily hack up a circuit-board-less mini-array of two or three LEDs running through a resistor from 12V, and see what you thought. That'd still be useful as an accent light for your CPU or something, even if you decided to go with a tube for the main light.

 

Undoin' the voodoo

I plugged the floppy power cable into my new Quantum 3D Voodoo 5 6000 card wrong (the power connector was specially installed) and blew the card up. The wire burnt in seconds. Is this normal, I thought? Hasn't my PSU got a cutoff circuit? Why can't they put a simple regulator on the input line to stop surges? I must get this card working!

Tony

Voodoo 5 6000
The Voodoo 5 6000.
Vintage. Classic.
Toast.

Answer:
Um, yeah, that'll happen. If you get a four pin drive-type power connector backwards, you'll apply 12V to components expecting 5V; result, toast. If you manage to plug it in off-by-one, then you'll apply voltage to an earth pin, which could blow a track off the board. Result, also toast.

Is this normal? Well, yes. Not that I've ever made this particular mistake myself, but people who manage to reverse plugs with power supply wires in them commonly blow stuff up and/or set cables on fire.

Your PSU will blow a fuse if you ask for way too much current; it takes considerably less than its maximum current capacity to blow up a component if you plug stuff in wrong.

A regulator wouldn't help you, by the way. Regulators regulate voltage, not current. A current limiter could have saved the day, if it clamped down fast enough; it's possible to put some kind of current limiter (a simple fuse would qualify, in this case) on the supply lines for any piece of hardware. But it's not often done, because it's not normally assumed that people will manage to connect the power plug wrongly.

Fuses are used on some hardware, though; many motherboards, for instance, have little surface mount fuses to protect the board from mis-plugged expansion port devices. The classic example is older PS/2 keyboards with large smoothing capacitors that charge too quickly and can, in theory, damage the motherboard if you hot-plug the keyboard (which you're not meant to do). Plug such a keyboard in when the computer's turned on and you may blow the protection fuse, which'll zonk the PS/2 port. Just bridging the blown fuse with a shred of wire, mind you, will bring the port back to life, and hot-plugging the same keyboard in the future probably won't damage the motherboard. The reason for this is that the value of the fuse has been deliberately set rather low, to give it the best chance of actually doing its job by blowing before damage has been done, and avoiding the situation where a $500 piece of hardware manfully sacrifices itself to protect a $0.05 fuse. The low value, however, means the fuse can and will blow when no damage would have been done - so-called "nuisance triggering". Nuisance triggering is a big reason why designers don't bother with protection hardware like this.

Most hardware just relies on the PSU's own circuitry to keep it safe, and that generally works very well. Provided stuff is plugged in properly.

To be honest, I'm not sure why you're so hot to run this weird old video card. I can understand someone wanting to buy a V5 6000 to put in a cupboard and sell in ten years, when it'll probably be worth quite a bit of money; they're certainly a rarity. But there's really no practical reason to bother with a V5 6000 any more. A GeForce4 MX isn't far behind it in performance, and any full GeForce4 beats the pants off it in every department.

 

Where do keys come from?

I have a... friend... who recently got a burnt copy of Unreal Tournament 2003. The game asked for a CD key so he downloaded a key generator, and within seconds he was fragging away. My question is, how on earth are people able to make these generators? CD keys for games are often more than 20 characters long, with millions of different combinations, and I'm assuming that game publishers invest a lot of money into making the whole CD key system.

Also, when a cd key is generated, does it mean that a legitimate user is having his key stolen?

Mr Mc Chicken

Answer:
There are two kinds of software key.

First up, consider software that lets you convert an unregistered version into a registered one with a serial number that you have to pay for. That sort of key is generated by algorithmic twiddling of the user name (and/or company name, and/or e-mail address) you enter when you register. The name-to-serial algorithm may or may not be difficult to work out (some software has really long keys; the key for MailWasher is 294 characters!), but all it takes is one coder somewhere to figure it out and create a keygen and bing, it's cracked forever. Or at least until the next version of the software changes the algorithm. Even if the key algorithm is fiendishly complex, people can still tell other people their paid-for username and key.

This key-generation strategy explains why ripped-off keys for various shareware apps come with both a username (generally something rather whimsical) and a key; without the right username, the key won't work.

The other kind of software key system works like credit card numbers. Credit card numbers are not random; they obey algorithmic rules. The initial digits tell you what kind of card it is and who issued it, and the whole number has to pass a Luhn Algorithm test.

If you generate a credit card number in a truly random way - just roll a ten-sided die 16 times - you're unlikely to come up with a number that passes the Luhn test (only one in ten numbers will), very unlikely to come up with a number with starting digits that correspond to a real card type and issuing institution, and very very unlikely to come up with the number of an actual card that exists, and its expiry date, and the extra three digits on the end of the number on the signature side of current Visas and MasterCards that're used by some vendors for extra verification.

It's easy to generate a credit card number that passes the first two tests, though; the Luhn algorithm's simple enough that you can do it with pencil and paper, and there are lists of tons of valid card prefixes. There are lots of freeware utilities that'll spew out dozens of card numbers whenever you like.

There's no way for a merchant, by himself, to tell that one of these fake numbers is, actually, fake. All online shopping cart software worth its salt does at least a Luhn check on numbers to make sure they've been typed in properly, but that only tells you that the number could be real, not that it is. The next step is to use the card issuers' verification services; the merchant, or more commonly the merchant's card-handling hardware and software, calls up Visa or Mastercard or American Express or whoever, and checks to see that the card details are the details of a real card, and that the card isn't lost or stolen or overdrawn.

Games with online play that come with a CD key work the same way. The game software on every CD is exactly the same; it has no idea what serial number's on the sticker on the jewel case. It, therefore, does basically the same thing to the key you type in when you install the software as a simple Luhn-checker does to a credit card number; it checks the serial against some algorithm or other to see if it matches, and if it does, it lets you play the game locally. If someone cracks the key-check algorithm, then they can generate arbitrary quantities of keys that'll pass the game's built in test.

When you try to connect to an online game server, though, the game checks with an authentication server run by the publishers, which knows all of the real keys - the keys that have actually been printed on a sticker, of which there will be far fewer than the number of keys that pass the algorithmic test, just as most Luhn-passing 16-digit numbers aren't real credit card numbers. Your generated key might be a real key (in which case yes, the faked-key player can take the place of a legitimate buyer of the game), but it very probably isn't. If you fail to provide the authentication server with a key that it accepts (and known-to-be-warezed serials are likely to be regularly deleted from the authentication database), then you won't be able to play online.

Well, not without further hacking, anyway. It's apparently possible to play UT2003 online with a generated key, after a bit of config fiddling to input a hard-coded server list; presumably an outboard utility could update that list from the standard server list and make the game work exactly like a registered version. But, to be perfectly frank, I really think buying the game would be less trouble.

Copy protection schemes that actually do make every game CD different, so only the key provided with that CD will work with it, have been suggested. But anybody who thinks that'd stop crackers is, themselves, on crack, and it'd do nothing more to stop people playing online with fake keys than the simpler, all-CDs-alike system does.

 

Firebottle computing

I can scarcely believe my eyes. Tubes! Tubes! (I think you Commonwealth folks call them valves?). On a new AMD Hammer motherboard of all things (AOpen AK86)!

And here we're worrying about the thermal characteristics of the CPU - those tubes are bound to cook the innards of the average PC case. The 80-100 watts of heat from the CPU look paltry compared to the heat output from real, live, glowing filaments!

I can't wait to see the wanky coolers that'll get designed for the tubes (electronics newbies have no idea that a certain amount of heat is required for these things to work, hence the filament called the heater!).

Well, at least the 5.1 sound system will be resistant to EMP effects from the next atmospheric nuclear detonation!

Susan

Answer:
Yeah. Weird. AOpen produced a one-valve board a while ago, but apparently that wasn't enough for them :-).

The tubes aren't a thermal problem, though. They're not power valves, just dual triode pre-amps, probably 6DJ8/6922/ECC88 type. Their full rated heater power isn't much more than two watts per unit, their total aggregate power isn't much more, and many applications run them well below rated power. Check out my review here for a bit more info on this subject.

If you want to ask me a question, feel free - but please read this and this first.

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)