03-24-2009, 08:28 PM
|
#1
|
Administrator
Join Date: Feb 2005
Posts: 993
Credits: 52,764
|
System Specifications
Brand:
|
Dell |
Model:
|
Inspiron E1705 |
Processor Type:
|
Intel Core Duo |
Processor Model:
|
T2600 (2.33Ghz / 4MB L2 Cache / 667FSB ) |
Chipset:
|
n/a |
LCD:
|
17" Widescreen |
Screen Type:
|
Matted |
Native Resolution:
|
1920 x 1200 (WUXGA) |
Video Card:
|
NVIDIA GeForce Go 7950 GTX |
Video Memory:
|
512MB |
S-Video Out:
|
No |
HDMI Out:
|
No |
Second Monitor Output:
|
DVI and VGA |
SLI support:
|
No |
Memory Speed:
|
DDR2 533 |
Hardrive 1:
|
320GB 7200rpm SATA 150 |
Hardrive 2:
|
No |
Hardrive 3:
|
No |
Raid Configuration:
|
No |
Optical Drive 1:
|
DVD±R/RW |
Optical Drive 2:
|
No |
Built-in Speakers:
|
2 speakers & Subwoofer |
Audio Jack Ports:
|
2 |
S/PDIF Digital Output:
|
No |
Built-in Card reader:
|
5-in-1 Card Reader |
Built-in Web camera:
|
No |
Built-in Wireless Device:
|
Intel 3945 (A/B/G) |
Built-in TV Tuner:
|
No |
Built-in Bluetooth module:
|
Optional |
Floppy Drive:
|
No |
Fingerprint Reader:
|
No |
USB Ports:
|
6 USB 2.0 Ports |
1 IEEE 1394a (Fire Wire):
|
1 Port |
Numeric Keypad:
|
No |
Battery Type:
|
9-Cell Lithium-Ion |
Battery Life:
|
2 Hours+ |
Secondary Battery:
|
No |
Width:
|
15.5" |
Length:
|
11.3" |
Height:
|
1.6" |
Weight:
|
7lbs |
The side bar to the right contains Skillz's notebook specifications and benchmarks
The first box contains the notebook specifications and the boxes below are the benchmark results cooresponding to this system.
Note - forum members now have the ability create benchmark logs where they can submit multiple benchmarks and group their results by their current settings.
Quote:
Originally Posted by Skillz
Hmm, strange.
If you have benchmarks that are already approved, then you go back and add more it'll automatically take you off the "latest benchmark" block it seems.
|
Yeah, it's designed by settings groupings and to take you the main pages until all the benchmarks in a box have been verified. You can create new groupings/settings changes and add benchmarks though.
There are few benefits to this in terms of optimizations in the backend with this method but I can change it later, I'm just in the middle of some other projects right now. As long as the benchmarks are indexed regularly it shouldn't be much of a problem.
|
|
|