- Joined
- Aug 9, 2006
- Messages
- 1,065 (0.16/day)
System Name | [Primary Workstation] |
---|---|
Processor | Intel Core i7-920 Bloomfield @ 3.8GHz/4.55GHz [24-7/Bench] |
Motherboard | EVGA X58 E758-A1 [Tweaked right!] |
Cooling | Cooler Master V8 [stock fan + two 133CFM ULTRA KAZE fans] |
Memory | 12GB [Kingston HyperX] |
Video Card(s) | constantly upgrading/downgrading [prefer nVidia] |
Storage | constantly upgrading/downgrading [prefer Hitachi/Samsung] |
Display(s) | Triple LCD [40 inch primary + 32 & 28 inch auxiliary displays] |
Case | Cooler Master Cosmos 1000 [Mesh Mod, CFM Overload] |
Audio Device(s) | ASUS Xonar D1 + onboard Realtek ALC889A [Logitech Z-5300 Spk., Niko 650-HP 5.1 Hp., X-Bass Hp.] |
Power Supply | Corsair TX950W [aka Reactor] |
Software | This and that... [All software 100% legit and paid for, 0% pirated] |
Benchmark Scores | Ridiculously good scores!!! |
I noticed that many are still using ancient Speccy that has outdated hardware database in order to dump/share their sysinfos, or worse an unholy combination of overly verbose cacophony of open windows of AIDA64/HwInfo/CPUZ+GPUZ stacked upon each other, all in a single screenshot in order to share their sysinfo in semi-coherent visual way. I've been playing around with building a quick and visually succinct sysinfo utility (screenshot below), VisInfo. Right now it is pretty rudimentary (by design) with basic screenshot taking and few other semi completed features, and many bugs (I do not have any EVGA or WD hardware for instance on the test machine!).
It seems building a comprehensive hardware database will be the most daunting task. I intend to scrape TPU's own GPU database (with permission naturally) to "fatten" up the pretty thin and somewhat lacking database I have now. The details panes I'm working on (not pictured below) will sort of have both of GPU-Z's and CPU-Z's way of info dumping, minus sensor monitoring data.
I'm open to any ideas and suggestions. I want to keep it very resource light, WinOS and WinOS legacy compatible (9x through Win10), and most importantly visually succinct.
...
..
.
It seems building a comprehensive hardware database will be the most daunting task. I intend to scrape TPU's own GPU database (with permission naturally) to "fatten" up the pretty thin and somewhat lacking database I have now. The details panes I'm working on (not pictured below) will sort of have both of GPU-Z's and CPU-Z's way of info dumping, minus sensor monitoring data.
I'm open to any ideas and suggestions. I want to keep it very resource light, WinOS and WinOS legacy compatible (9x through Win10), and most importantly visually succinct.
...
..
.
Last edited: