Liquid Cooling More than One Component?
static0verdrive asks: "I am new to liquid-cooling, and I have designed a system for use in a micro-ATX OpenBSD server, with the following layout: Fillport > Reservoir/Pump > Y Split (one to CPU and the other to chip-set) > Y Reconnect > Radiator/Fan > Back to the fillport. I don't like the idea of having the hot coolant coming from the CPU going directly to the chip-set, hence the Y split. Could this split cause any problems? Would there be a difference in pressure (considering the CPU is most likely a lot hotter) that could cause an issue? How would you handle liquid-cooling more than one component? What if I wanted to cool 3 components, such as in the case where I add a video card to this setup later on?"
Oooooooo!! Now THAT'S a whoop-ass idea! Any thoughts on how to accomplish this?!
========
77 77 77 2e 6d 65 6c 76 69 6e 73 2e 63 6f 6d
sorry in advance for nagging but please refrain from naming your URLs undescriptive names such as "here" or "click". :P ) use the link title to categorize it. If you name the link properly, the search engine will index it properly and someone looking for information will find it. If people kept naming this link "here", the page would need 10 times as many links pointing to it to get indexed.
There are 2 problems with naming a link "here": those who use a link summary program won't know what the link is about unless they read the post - which completely defeats point of using the link summary program. Obviously, they get frustarated as hell.
Second problem is that search engines (yes i mean google
In this post, a perfect way to name that link would be "info about liquid cooling".
Did you know that "FTW" ("for the win") is a direct translation of "Sieg Heil"?
There are 2 problems with naming a link "here": those who use a link summary program won't know what the link is about unless they read the post - which completely defeats point of using the link summary program. Obviously, they get frustarated as hell. :P ) use the link title to categorize it.
Second problem is that search engines (yes i mean google
I don't write for people who use "link summary programs", nor do I write to make google's profit-making easier for them. If google want to make profit from my efforts, they'll have to write a better algorithm. If people want to get an idea what I'm linking to and don't bother reading anything but the few words on a link itself instead of actually reading the paragraph it's part of, then they can just go take their brains that are trained to exist on nothing but soundbites (while rejecting all relevant context) and just go get frustrated like they deserve to (and continually will do by adopting such habits).
So take that
I'm sure I will find that too, if I go into the past and look at macs from the IIci back. Unfortunately, the IIfx was craptacular (all kinds of things are wacky, down to nonstandard SCSI termination) and everything since then has been shit - either it's been about half as fast as PCs of the day, not to even mention price, or it's been unreliable, or both. Sorry, but I've been using Macs almost as long as they've existed and we must be talking about a different Apple Computer or something. That or you're a tool.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"