Antec Releases "Skeleton" PC Case 124
ThinSkin writes "It is appropriate to say that Antec was 'thinking outside the box' when the idea of the 'Skeleton' PC Case sprung to mind. The Antec Skeleton is an open-air PC case with a pair of shelves for the motherboard and other components — held up by arching arms. There are no side panels. This is ideal for the computer user who is constantly fidgeting with his PC parts, or someone who wants to show off his fancy components. Just have a compressed air can nearby. There is also a slideshow of Antec Skeleton images available."
What TFA fails to report is... (Score:4, Funny)
Re:Good for a lab. (Score:4, Funny)
Tesla Coil! (Score:5, Funny)
Just put a Tesla coil on top.
No, I haven't thought mu cunning plan through.
Re:But... (Score:4, Funny)
"Already ordered one for our development lap where we're testing under lots of hardware configurations."
And don't think your lap wouldn't appreciate the weight reduction. :)
Awesome. (Score:5, Funny)
Re:Noise Level? (Score:3, Funny)
And if the computer is running Windows Vista, the whining from the user itself.
Re:EMI (Score:5, Funny)
Screw EMI. After all, they're part of the RIAA.
Re:But... (Score:3, Funny)
"Perhaps closed cases are overrated in terms of the amount of "actual" protection they provide."
IME with customer machines, closed cases protect many interesting "dust bunny and (usually) dead insect" ecosystems. As for "pets", I've seen some machines with enough hair/dust/primordial "stuff" to build a small dog.
Re:But... (Score:4, Funny)
Only the one time. And if they did survive, you could be sure they would learn the lesson.
Had a Irish Setter once. And an electric fence. He wizzed; I winced. But I must say, I never saw him repeat the experience.
Re:Good for a lab. (Score:5, Funny)
Sooner or later you'll notice that your FSB has had an upgrade.
After that you'll just have to find a female connector if you got the male one, or a male one if you got the female one, and the rest is basic IO.
There seem to be some sort of protocol using a closed handshaking routine to initiate the data transfer though and I haven't got that one figured out. There have been quite a few attempts to reverse engineer and document the procedure for the whole handshaking process, part of the progress can be found in TFM by Neil Strauss, but there are no complete documentation yet.
Common practise for finalising the handshake routine includes brute-forcing. But that method requires a wide array of targets since the target host most often will notice the probe and close all ports well before the initializing handshake routine and following data transfer is over. Alternative practise includes paying for a one-time key usable against a single target. This method got its flaws though since the target are usually well protected against intruding code which won't execute whereby not finalizing the final stages of the procedure. You will still get all the benefits of making the connection and following thru the whole data transfer process, but the application will never fork into a new process.
But believe it or not, some people even see benefits of the lack of a child process. For instance you don't have to fight over resources, share memory or try to fight for priority.
Re:But... (Score:4, Funny)
But! Even my mom wants this case!
Though my friends tell me how her case is always open.
Re:Good for a lab. (Score:4, Funny)
Thanks for pointing that out. If he kept on contracting himself, he'd form a singularity.
Re:What TFA fails to report is... (Score:4, Funny)