It's because of idiots like this that we can't have nice toys. Laser pointers get banned and people who buy them get looked on with suspicion. All because some morons think pointing them at aircraft is a good idea.
How about we punish the idiots, and let the rest of us have our toys?
Uh huh. Put into perspective, isn't this the current "gun control" movement? A few $hits do really awful things with firearms and the rest of the peaceful population gets to pay for it?
Best way is a supersonic projectile, usually 9mm or larger in handgun calibers, 5.56mm or larger in long gun calibers. While JHP flatten out on the case and usually don't puncture the shell and the platters (they're much better for soft tissue), most FMJ work great as they pierce the case and generally shatter the drives as well. It's also cost effective- as little as $.10/drive for destruction!
Multi Sound cards is a good idea (i've been playign around with it for a while myself). There's just a couple of things to watch for...
1) Some sound cards don't like running in the same computer with another one of themselves. The old soundblaster cards were notorious for this. These days with PCI soundcards negotiating (is that spelt right?) their resources, it SHOULDN'T be a problem, but I've still had some problems with it. I have two Yamaha PCI DS-XG cards here that refuse to run together (under Winblows, anyway). Both detect and negotiate just fine at startup, but the drivers conflict like nothing else. I haven't yet bothered to go lookign for Linux drivers for this card, to see if they'll work together with a decent set of drivers, tho (as my multiple channel autio output needs are under Winblows at the moment). I ended up getting one of those cards, as well as an ESS Solo-1 PCI card working together quite happily tho.
and
2) Synchronisation between the cards. It doesn't look like this'll be a problem for you, but output over multiple soundcards, can lose synchronisation after a while. (Well, technically, it was always out of synch, but you tend to notice it more the longer it plays). This is only a problem if (like me) you've got one song takign up multiple channels over several sound cards.
Eg, I record stuff for my band to have as backing for when we play. We're trying to make this stuff output over 4 channels so that we have a greater controll over it at the PA. What we've got is 2 mono drum tracks coming out of the stereo output of one sound card, and then two mono keyboard tracks coming out of the other cards output. Problem is that the cards don't quite have perfect synch between their respective sample timings, and so one card can end up outputting the waveform slightly quicker or slower than the other. Now, the difference is less than the space of a sample (1/44000th of a second), but it's still there, and the longer a song goes for (we play 8 minute songs on average, with 12-13 minutes being about our ceiling) the more this slight difference gets compounded. For short songs you may very well not notice it at all. Bear in mind too, that the problem only starts everytime you start playing something, and stops when you stop. It's only for extended playing times that you'll really notice it.
Anyway, if you're planning on having seperate (unrelated) waveforms output from each card it's not an issue for you. If, however, you want the outputs kept in synch for some reason (say, you want the same song comign out all outputs so you can listen to it in 3 different rooms) you may (and I say, only may) start to notice the synch difference.
I don't know about the rest of you, but I'm finding that this whole NT vs Linux war is starting to annoy the crap out of me!
I hear (and even advocate) pro linux and anti M$ stuff on one side, and then ( mostly thanks to a M$ Certified mate of mine) hear pro M$ and anti linux stuff on the other side. And to be honest, I don't much care.
I'm beginning to think that this whole "We have to beat NT" thing is becoming a dangerious obsession. Linux ( and, indeed the opensource comminuty ) has different priorities to Windows NT, and Micro$oft.
Now, while it's certainly not a bad thing to keep an eye on what's happening "on the other side", hell, as was mentioned in a previous thread (sorry to whoever mentioned it, I can't remember your name) the competition drives the advancement to a degree. But I fear that we're becommign so obsessed with beating Micro$oft, that we're losing perspective of everything else.
I remember an article by the name of "The Two Towers" here on slashdot some months ago (again, apologies to the author, as i can't remember your name to quote it), and I think I should reiterate it here. We really need to be careful that in our attempts to "Destroy the beast" (Micro$oft in this case), we don't inadvertently become it ourselves!
Let's just try not to lose track of where we're headed, and why we're here in an attempt to prove that our products are better than somebody elses.
One question tho. Is having a cold surface like that on a chip ( questions of the moisture asside, at the moment ) actually going to cool it any better? I thought the idea of the heat sink was to transfer heat FROM the cpu, and dissipate it. Now, I'm not totally convinced that putting a colder surface on the CPU is really going to be able to cool it down any better ( you're still going to want your heat transfer and dissipation properties of the heatsink ). And yes, I realise that the object in question was definately a heat sink. The question being is the cold contact surface going to make it perform better than any other heatsink?
THEN we get to the question of whether or not you'd want something that produces moisture like that near our computers. I dont' know about the rest of you, but my answer to that is a big fat NO!:)
Slashdot Mirror
It's because of idiots like this that we can't have nice toys. Laser pointers get banned and people who buy them get looked on with suspicion. All because some morons think pointing them at aircraft is a good idea.
How about we punish the idiots, and let the rest of us have our toys?
Uh huh. Put into perspective, isn't this the current "gun control" movement? A few $hits do really awful things with firearms and the rest of the peaceful population gets to pay for it?
It's like the elephant joke...
How do you eat an elephant?
One bite at a time...
Best way is a supersonic projectile, usually 9mm or larger in handgun calibers, 5.56mm or larger in long gun calibers. While JHP flatten out on the case and usually don't puncture the shell and the platters (they're much better for soft tissue), most FMJ work great as they pierce the case and generally shatter the drives as well. It's also cost effective- as little as $.10/drive for destruction!
Right between the cracks....
Sounds cool!!
:)
So where do we get it from?
Multi Sound cards is a good idea (i've been playign around with it for a while myself). There's just a couple of things to watch for ...
1) Some sound cards don't like running in the same computer with another one of themselves. The old soundblaster cards were notorious for this. These days with PCI soundcards negotiating (is that spelt right?) their resources, it SHOULDN'T be a problem, but I've still had some problems with it. I have two Yamaha PCI DS-XG cards here that refuse to run together (under Winblows, anyway). Both detect and negotiate just fine at startup, but the drivers conflict like nothing else. I haven't yet bothered to go lookign for Linux drivers for this card, to see if they'll work together with a decent set of drivers, tho (as my multiple channel autio output needs are under Winblows at the moment). I ended up getting one of those cards, as well as an ESS Solo-1 PCI card working together quite happily tho.
and
2) Synchronisation between the cards. It doesn't look like this'll be a problem for you, but output over multiple soundcards, can lose synchronisation after a while. (Well, technically, it was always out of synch, but you tend to notice it more the longer it plays). This is only a problem if (like me) you've got one song takign up multiple channels over several sound cards.
Eg, I record stuff for my band to have as backing for when we play. We're trying to make this stuff output over 4 channels so that we have a greater controll over it at the PA. What we've got is 2 mono drum tracks coming out of the stereo output of one sound card, and then two mono keyboard tracks coming out of the other cards output. Problem is that the cards don't quite have perfect synch between their respective sample timings, and so one card can end up outputting the waveform slightly quicker or slower than the other. Now, the difference is less than the space of a sample (1/44000th of a second), but it's still there, and the longer a song goes for (we play 8 minute songs on average, with 12-13 minutes being about our ceiling) the more this slight difference gets compounded. For short songs you may very well not notice it at all. Bear in mind too, that the problem only starts everytime you start playing something, and stops when you stop. It's only for extended playing times that you'll really notice it.
Anyway, if you're planning on having seperate (unrelated) waveforms output from each card it's not an issue for you. If, however, you want the outputs kept in synch for some reason (say, you want the same song comign out all outputs so you can listen to it in 3 different rooms) you may (and I say, only may) start to notice the synch difference.
ANyway, I hope this is helpful to you.
I don't know about the rest of you, but I'm finding that this whole NT vs Linux war is starting to annoy the crap out of me!
I hear (and even advocate) pro linux and anti M$ stuff on one side, and then ( mostly thanks to a M$ Certified mate of mine) hear pro M$ and anti linux stuff on the other side. And to be honest, I don't much care.
I'm beginning to think that this whole "We have to beat NT" thing is becoming a dangerious obsession. Linux ( and, indeed the opensource comminuty ) has different priorities to Windows NT, and Micro$oft.
Now, while it's certainly not a bad thing to keep an eye on what's happening "on the other side", hell, as was mentioned in a previous thread (sorry to whoever mentioned it, I can't remember your name) the competition drives the advancement to a degree. But I fear that we're becommign so obsessed with beating Micro$oft, that we're losing perspective of everything else.
I remember an article by the name of "The Two Towers" here on slashdot some months ago (again, apologies to the author, as i can't remember your name to quote it), and I think I should reiterate it here. We really need to be careful that in our attempts to "Destroy the beast" (Micro$oft in this case), we don't inadvertently become it ourselves!
Let's just try not to lose track of where we're headed, and why we're here in an attempt to prove that our products are better than somebody elses.
-Matt Sk
Hmmm, OK so that's how it's done. Interesting.
:)
One question tho. Is having a cold surface like that on a chip ( questions of the moisture asside, at the moment ) actually going to cool it any better? I thought the idea of the heat sink was to transfer heat FROM the cpu, and dissipate it. Now, I'm not totally convinced that putting a colder surface on the CPU is really going to be able to cool it down any better ( you're still going to want your heat transfer and dissipation properties of the heatsink ). And yes, I realise that the object in question was definately a heat sink. The question being is the cold contact surface going to make it perform better than any other heatsink?
THEN we get to the question of whether or not you'd want something that produces moisture like that near our computers. I dont' know about the rest of you, but my answer to that is a big fat NO!