Depends on how you define "target," or a distinction between "target" and "source."
In this case, I'm referring to source files. My earlier comment in regards to cache-hit rate was meant to imply that a highly generalized cache, such as the Windows built-in cache, will likely have a lower hit rate, since you can't cache everything. Contrast this to a utility like primo-cache that will cache only the data you specify, thus greatly enhancing the hit rate in a circular sort of way.
I think the key thing to remember: the nephew's computer (which is i7/i5-etc. gen 1 or later) needs an SATA-III port and controller to really take advantage of any options -- caching or no caching. If not, there are quality, inexpensive controllers available -- at least a few offering the Hyper-Duo option as well as usefulness with PrimoCache. And I noted that my laptop system has only SATA-II, but the performance boost from a 3GB RAM-cache assignment can't be overlooked.
Bringing this back to the OP, this is one point I have to disagree with. Take the following counter example:
500GB SATA II HDD
128GB SATA II SSD
Setting the SSD up as a dedicated cache for the HDD will provide tangible performance increases as the HDD will have no chance of saturating SATA II, but the SSD should.
I also have to echo the cautionary statements of the other posters regarding L1 write-back. Data loss can be an ugly thing, and for games (which are nearly 100% read IO), it's really not required. (It sounds like the OP is not interested in this anyways, but it's worth calling out.)
As for L2 caching, it sounds like the OP has already made the decision I would recommend: Option 2 (or any SSD+HDD read cache option). Follow the KISS principal, and keep the nuts and bolts out of reach of the non-tech.
My questions were rhetorical.
Ah, sorry, I was focusing on the technical merits of the post, given that the social undertones may be lost on the less informed.
Anyway, Windows does not cache block operations. Windows file system cache is a file cache only.
Perhaps this is just an assumption on my part, but if files are not cached as raw 256KB blocks, how are they cached in memory?
Windows write cache on desktop systems is 1GB.
Are you referring to some write-specific caching mechanism? I'm referring to the System Cache, which contains the file look-aside table. The System Cache can be much, much larger than 1GB.
Microsoft said:System cache virtual address space (physical size limited only by physical memory)
Limited by available kernel-mode virtual address space or the SystemCacheLimit registry key value.
Windows 8.1 and Windows Server 2012 R2: 16 TB.
Windows Vista: Limited only by kernel mode virtual address space. Starting with Windows Vista with SP1, system cache virtual address space can also be limited by the SystemCacheLimit registry key value.
Windows Home Server, Windows Server 2003, and Windows XP: 860 MB with LargeSystemCache registry key set and without 4GT; up to 448 MB with 4GT.