Dan's Data letters #2

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

 

Resolution reduction

After reading your comments on your new Canon digital SLR, I decided that perhaps I should ease up on my pro-emulsion, anti-digital campaign and give digital a try. I purchased the Canon S30 point-and-shoot and so far am quite pleased with the results. It's not the quality of my Nikon N90s but it is fast and much more portable.

My question is actually about CCD technology. I noticed that the S30's maximum resolution is 2048 by 1536, or an effective 3145728 pixel count on my "3.2 Megapixel" camera. Now, if I don't shoot in RAW mode (which is rare), I can scale the JPEGs down to as small as 320x240 (I think) but I had a thought at work the other day: does the camera actually use all 3.15 megapixels and then scale down (using some sort of raster arithmetic, I suppose) to the resolution, or does it just simply use a progressively smaller portion of the CCD?

Either way, I'm sold on the RAW format so it doesn't present much of an issue, but there are occasions when I will shoot in 1024 by 768 JPEG to conserve space.

Jon

Answer:
If the camera did lower resolutions by using less of the CCD in a simple cropping sense, then you'd get a longer and longer effective focal length (more and more zoom) as you went to lower and lower resolutions. You'd only be looking at a rectangle in the middle of the sensor. This is exactly what "digital zoom" does; it just takes a crop of the normal imager area, and may interpolate it up to a higher resolution, but can't put back the detail that's been lost by using less than the whole sensor. You can do "digital zoom" in post-processing.

If the camera did lower resolutions by only using, say, every second output pixel, then that'd work. It'd be doing that after taking a full-resolution shot, though, because there's little point giving the imager the ability to disregard pixels when you can do it in the in-camera image processing stage, before the file's written to flash memory.

What I bet the camera is actually doing, though, is quite nice weighted scaling, not a dumb pixel-dropping routine. Some cheap and nasty digitals used pixel-dropping for lower resolutions, which resulted in really ugly images - see my old review here for a perfect example. Nowadays, image processing hardware is cheap and low power enough that cameras can do bilinear scaling and produce nice-looking results, and that's very probably what your S30's doing.

There are a number of other issues to do with sensor pixel counts, by the way. You may find this page interesting.

 

I am not a spammer! I am a human being!

I need your advice on what I think may be a dreadful trend in spamming. The past few weeks, my beloved Yahoo e-mail account has recieved a disturbing number of messages that are replies from various mail servers telling me that the mail I've tried to send to joeblow@anydomain.com was undeliverable as joeblow doesn't have an account on that server, or some similar error.

Upon closer inspection of these e-mails it would appear that I've tried to send mail to joeblow informing him that if he's interested in watching siblings engage in various illicit acts, or has an odd curiosity involving the mating habits of various farm animals, he can see these things and many other oddities at a Web site that is conveniently linked in the e-mail. The really disturbing part is it would appear that I've sent this e-mail to a LOT of people.

Granted, I've been known to send some very interesting e-mails while under the influence of various legal substances, but my "sent mail" box does not have any evidence of these messages. I must conclude that some spammer has chosen my e-mail address to use in the "return address" field in their spam. I understand that spamming can be a profitable business, and I also understand that theses spammers don't want to put their address in the "Return Address" field, but why not just add an invalid address in there? Why use my address?

Can you tell me if there is a way to stop this? The e-mail headers don't seem to contain any useful information, other than that my address is indeed the return address. The links in the e-mails point to various personal pages on www.terra.es and unfortunately my Espaņol is not up to par, nor do I believe that Babelfish is sufficient to convey my displeasure with this practice.

(name expunged, to prevent any further address-guessing)

Answer:
Yes, your address is being forged as the reply address for spam. This isn't new; it's just new to you. It happens to me all the time.

Spammers have been known to do this because they don't like someone. Joe@wherever.net tries to shut them down; ten million penis enlargement spams go out with joe@wherever.net as the reply address.

Assuming you haven't been going out of your way to annoy spammers, it's not totally beyond comprehension that someone might have come up with your abcdef@yahoo.com address (letters changed to protect the innocent) by means of random keyboard-bashing. Type six alphabetic characters and any given sequence has a one in 308,915,776 chance of coming up; given the amount of spamming going on today and the clear qwertyuiop-ishness of many of the reply addresses, some dork may well have chanced upon your address. Or maybe they just plugged in an address from their faithful One Zillion Guaranteed Opt-In Customers CD, for whatever reason, and yours was that address.

Spammers are idiots. Who knows why they do things.

Fortunately, people who've got their act together won't be complaining to you. Everybody sensible knows that the reply address on spam means nothing; only newbies complain to it, and no competent sysadmin will pay any attention to their complaints. This isn't to say that an incompetent Yahoo admin might not ban your account, but I wouldn't lie awake worrying about it. If your cow-orkers are irked, and/or some manager decides you're a spammer and wants to fire you, that sucks, but an appeal to the company sysadmins (assuming such people exist) ought to clear things up.

Can I tell you if there is a way to stop this? Yes, I can tell you. No, there isn't.

Well, short of killing all spammers. I'm developing a plan involving red hot crowbars, but I haven't worked out the details yet.

Stopping the spam is hard, but sending complaints is easy. Check out SpamCop.

 

Bad RAM?

Last year I finally upgraded from my P133 to a Duron 900 - it was something of a shock to see a computer do things so fast! The motherboard that I got with it was an Asus A7VL-VM, and 128MB RAM to go with it. Everything was fine untill I recently bought a 256MB DIMM so Windows XP might be a tad faster.

An Odd Thing happened... Windows refused to load whenever the DIMM was inserted..

I then went through the whole house, trying out all the different PC133 RAM in the house. There is some 736MB of PC133 RAM here; 3x32Mb, 3x128Mb, and 1x256Mb.

None of the 32MB DIMMs work at all in this computer. Two of the 128MB DIMMs work in this computer - but not both at the same time - Windows hates me when I use both at once. The remaining 128MB DIMM is suspected of being corrupt. The 256MB DIMM is brand spanking new, but Windows hates me if I use it in this computer.

When I say "Windows Hates Me" I mean it gives me the good old NT BSOD with "Unknown Hard Error: NT.DLL" or something like that.

Anyway, seeing as there's little to nothing that I can do about this, I was thinking of upgrading to another motherboard. I was looking at the Jetway 867AS-H and the ECS K7S5A - both around $AU100. Notice that both motherboards support DDR and SDR modules - I have been told that such motherboards have stability problems. Is this true, or is it just an urban myth?

unfunk

Answer:
Your Odd Thing isn't that odd, if you've got a bum memory module. Very cheap RAM often has compatibility problems of one kind or another, and if the module's been mishandled, it could be sufficiently static-damaged that it isn't completely dead, but still won't work right ever again.

The various other compatibility problems you're seeing, though, make this look more like a problem with your motherboard, which is possible. Motherboards can be static-damaged too. Asus boards don't have a particularly high fault rate, but you can kill anything if you're talented enough.

Memory modules that work alone but not together, like your 128Mb modules, are common enough. The problem could be caused by the motherboard, or by the memory, or both.

If I were buying one of the two alternative motherboards you mention, it'd be the ECS one. I'd steer clear of the Jetway one. I don't know of any endemic problems caused by the "dual fuel" design itself.

I wouldn't buy either of them, though, if I had a choice. Since dual fuel boards are all earlier models that don't get much benefit from DDR memory, there's not really a lot of point to them. It's not as if you can use both kinds of memory at once.

If you hunt around, you could probably find yourself a top-class SDR-memory board - an Abit KT7, say - pretty darn cheap. That's what I'd buy.

Of course, if it's the memory that's toast, a new motherboard won't help at all.

 

PSU reliability?

Dan,

I have a Linux server that I would like to keep running 24x7 - however the cheap ass power supplies you generally get in PC systems just don't seen to be designed to do this. The one in my system, after 2 weeks of constant operation, seems to have started making funny noises that haven't really stopped.

What I'd like to know is whether those quality power supplies you review are designed to be "always on", or are they just bigger better power supplies that are still made for use only 8 to 10 hours a day?

Craig

Answer:
Your noisy PSU probably has a bad fan bearing.

Super-cheap PSUs are amazingly reliable considering their price, but I wouldn't want one in an important machine. The various flashy case modders' PSUs that I've reviewed are OK quality, but there's no reason to presume they'll last any longer than a decent boring grey-box PSU from, say, AOpen. AOpen's PSUs cost easily twice as much as the real cheapies, but they're still cheap, and I'd be quite confident about using them in a 24/7 box.

Of course, for true reliability, you need hot-swap dual PSUs, so you can remove and replace a failed PSU without turning off the server. Various server cases come with these PSUs, but they ain't cheap.

 

Wavy screen

I have a vicious problem with my monitor... the image shakes like an absolute BITCH when the house is placed under high power load. The shaking pretty much renders the computer unusable.

I have come to the conclusion that it's not my hot water service, which many people link to monitors with this problem, but rather simple under-volting or whatever it may be from power use in our house.

Is there any way to fix this? I recently purchased a powerboard with basic RFI filtering, and that didn't do too much to stop the shaking. It helped a little though. If the problem is lack of power being supplied to our house, how can that be remedied?

Keith

Answer:
This sort of thing is often caused by quirky building wiring. If it happens in a home, the quirk is likely to be an actual fault, like a piece of steel in a wall that's carrying current when it shouldn't. It could be worth getting an electrician in.

Assuming that's not the problem, though, it's possible that it's an undervoltage problem, I suppose. Again, that may be indicative of a serious fault somewhere, but if you just want better power for the monitor, then you can get it by using a power conditioner. Some power conditioners are scarily expensive, but cheap ones exist, and may solve your problem; see here for instance. Note that I have no idea whether this store is any good; it's just what a search turned up.

Also, try changing the screen refresh rate you're using. That may reduce or eliminate the shaking problem.

 

STP vs UTP

I've just been reading your Ethernet Networking Explained page. At the end, it mentions STP cable. What is this?

Luke

Answer:
STP is Shielded Twisted Pair. It's like regular twisted pair network cable, but with an earthed shield around the conductors for better noise resistance. STP works the same as UTP, but you won't see it often used for normal networking, mainly because it's more expensive and less flexible. Furthermore, its better noise resistance isn't necessary for most applications.

Any twisted pair cable has pretty good noise rejection, because of the twisted conductors, which are used as balanced transmission lines.

Only two of the four wire pairs in ordinary Category 5 (Cat5) network cable are used for 10/100BaseT Ethernet; one pair has the positive and negative transmit wires twisted together, and the other pair has the positive and negative receive wires. Each negative wire carries an inverted version of the positive wire's signal, and twisting the cables means that any incident RF noise should affect each wire in each pair evenly. Since the noise will be the same on each wire, but the signals will be inverted, it's possible to delete whatever's the same on each wire and thus recover a low-noise signal. This technique allows quite long cable runs at quite high data rates without any shielding.

Earthing's also a bit of an issue for STP; shielded cables need their shield earthed at exactly one end, to avoid earth loop problems when the ground potential at the two ends of the cable isn't the same. This'll usually be the case, thanks primarily to mains power that's not in phase in different places due to the waveform-skewing effects of other loads.

STP cables should work OK with gear designed for UTP, but if you don't ground the shield somehow, the fatter, more expensive cable won't work any better. It may actually be worse; an ungrounded shield is basically a great big antenna for all kinds of RF, including noise from the cable it surrounds. It can actually worsen crosstalk problems.

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)