- Joined
- Feb 20, 2019
- Messages
- 8,280 (3.93/day)
System Name | Bragging Rights |
---|---|
Processor | Atom Z3735F 1.33GHz |
Motherboard | It has no markings but it's green |
Cooling | No, it's a 2.2W processor |
Memory | 2GB DDR3L-1333 |
Video Card(s) | Gen7 Intel HD (4EU @ 311MHz) |
Storage | 32GB eMMC and 128GB Sandisk Extreme U3 |
Display(s) | 10" IPS 1280x800 60Hz |
Case | Veddha T2 |
Audio Device(s) | Apparently, yes |
Power Supply | Samsung 18W 5V fast-charger |
Mouse | MX Anywhere 2 |
Keyboard | Logitech MX Keys (not Cherry MX at all) |
VR HMD | Samsung Oddyssey, not that I'd plug it into this though.... |
Software | W10 21H1, barely |
Benchmark Scores | I once clocked a Celeron-300A to 564MHz on an Abit BE6 and it scored over 9000. |
It's not just Windows that will constantly wake up sleeping drives for no good reason. Synology and QNAP will also both do that unless you go and disable so much functionality that you've essentially turned them back into a local drive using an RJ45 connector instead of a SATA connector, and if you're mapping it to a Windows machine, then Windows will never let it sleep for more than a few minutes, regardless.Ah. Good to know. I'm planning (and delaying as much as possible) a transition from 7 to 10, and also adding a HDD to the system. Will wrap it in rubber so thoroughly that no sound can come out. But seriously, back when all we had were HDDs, I always suspended them on rubber strips.