Quote:
Originally Posted by DMcCunney
ER, got a cite for that?
|
No, and not going to bother going to look it up. I personally created hard links in NT 4 and in Windows 2000, Server 2003, and XP. It was fairly hidden in earlier versions (I used Interix to do it in NT4/2000 though there was a resource kit tool that would do it as well, IIRC), but I have been personally told by one of the original NTFS developers that the capability was always there, just not exposed.
First use of symlinks that I'm aware of was Interix (a third party UNIX / POSIX subsystem that MS then bought), and then in Microsoft Services for UNIX (when they included the Interix subsystem in SFU). The hard links that Interix/SFU created were visible to the Windows user, but the symlinks were NOT (though, curiously, the junctions were). Symlinks that were visible to the Windows user were added in Vista, and exposed in Windows 7. (On a side note, the mount points or junctions that SFU/Interix created were visible to the Windows user, but they were BUGGY as all get out. They used "reparse points" and these weren't properly handled until the Vista/7 version of NTFS. This also affected the NFS file system, by the way.)
Quote:
|
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.
|
Hard links were always there. It would take a special driver to make symlinks work before Vista/Win7. Which is why hard links I created with Interix in NT4 were completely visible and behaved "normally" to the regular Windows user.
Quote:
|
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.
|
I would have said that Vista was the introduction of mklink, but I can't prove it without spinning up a VM and that's more work than it's worth. As for a GUI tool being better or an advantage? Sorry, you'll never get me to agree to that.
Quote:
And who uses Power Shell who isn't a developer or sysadmin? 
|
Any power user who wants to get stuff done fast and efficiently without having to click so much that they develop an RSI.
FWIW, I've been using PowerShell since before there was a public beta of Monad. And I was a hard core Korn shell user before that, even in Windows.
Quote:
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
|
Fair enough. I think it's a waste, but it's your RAM.
And let's face it, RAM is cheap. However, spending money on SSDs v. HDDs is probably the single biggest speed up you can do these days if you're still using conventional rotating media.
And all of this is completely off-topic for this (admittedly broad) thread.