Quote:
Originally Posted by CRussel
Hard links are and have been supported since the very first iteration of NTFS.
|
ER, got a cite for that?
AFAIK, hard link support first appeared in NTFS5, which was not the first iteration of NTFS to reach the world. IIRC, WindowsNT 3.51 had NTFS4.
Quote:
|
And can be created with the built-in command "mklink". In Windows 10 support for hard and symbolic links for files and directories, along with junctions for directories, is built in to PowerShell. (New-Item -Type {HardLink | SymbolicLink | Junction} ).
|
Link Shell Extension allows creation of hard links on XP, and symlinks on Win7. (Though a Japanese developer created a driver with source that makes hard links and symlinks work on Win2K.
Mklink is a built-in on Win7/8/10, but not prior, and is a command line tool. The advantage to LSE is integration with Windows Explorer.
And who uses Power Shell who
isn't a developer or sysadmin?
Quote:
|
The incremental value of a RAMDisk over an SSD is trivial and could actually be a detriment if not sized perfectly, since Windows is actually quite smart about using available RAM for caching.
|
In general, I advise folks to add RAM and let Windows manage it. Running a ramdisk is a "Because I have extra memory to play with, can do it, and have a use case for it."
______
Dennis