- Joined
- Nov 4, 2005
- Messages
- 11,682 (1.73/day)
| System Name | Compy 386 |
|---|---|
| Processor | 7800X3D |
| Motherboard | Asus |
| Cooling | Air for now..... |
| Memory | 64 GB DDR5 6400Mhz |
| Video Card(s) | 7900XTX 310 Merc |
| Storage | Samsung 990 2TB, 2 SP 2TB SSDs and over 10TB spinning |
| Display(s) | 56" Samsung 4K HDR |
| Audio Device(s) | ATI HDMI |
| Mouse | Logitech MX518 |
| Keyboard | Razer |
| Software | A lot. |
| Benchmark Scores | Its fast. Enough. |
Through the use of Process Monitor (to track the writes to disk), HxD ( a hex read tool that will read your disks), crystal mark to create the writes to the disk. I have discovered the following.
Disk images at byte level take awhile to save.
My 640 is passing along the TRIM command to the disks.
By choosing to add a filter of.
Operation, contains, Write File, then Include.
Then apply it, you can see where the file(s) were written and compare the disk Hex values (00 being empty) to whatever data was written.
Disk images at byte level take awhile to save.
My 640 is passing along the TRIM command to the disks.
By choosing to add a filter of.
Operation, contains, Write File, then Include.
Then apply it, you can see where the file(s) were written and compare the disk Hex values (00 being empty) to whatever data was written.