DAP
Member
- Joined
- Aug 29, 2008
- Messages
- 432
For me, I'd want a fanless box with a gigabit ethernet port, and a SATA port that was fast enough to fully saturate a SATA drive or the etherenet port (whichever is slowest). I'd want it to be able to act as a NAS, a UPNP server, and a mythTV back end (Digital TV only, no analog tuners). For this purpose it would be a headless always on system, so I'd like its idle power to be below 5 Watts.
From what I have read in this thread, it appears there are a bunch of wants with opposing requirements. Some want a game machine with a high res display, and others want a low power server type device.
It seems to me that it might be better to design two devices: A low power always on headless back end with hard drive, and a front end that only uses power when the user wants to do something with it. The front end could drive a display & play games. Lets face it, a DVR would be useless if it did not record scheduled programs when someone was using it to play games. And a game machine requires horse power which translates to Watts.
A separate back end & front end, even if they share the same power supply & box, seems to make more sense (as long as the front end can be shut down separately from the back end).
From what I have read in this thread, it appears there are a bunch of wants with opposing requirements. Some want a game machine with a high res display, and others want a low power server type device.
It seems to me that it might be better to design two devices: A low power always on headless back end with hard drive, and a front end that only uses power when the user wants to do something with it. The front end could drive a display & play games. Lets face it, a DVR would be useless if it did not record scheduled programs when someone was using it to play games. And a game machine requires horse power which translates to Watts.
A separate back end & front end, even if they share the same power supply & box, seems to make more sense (as long as the front end can be shut down separately from the back end).