From fa652cdb564061fae8fd80bd5665f595dbbb2796 Mon Sep 17 00:00:00 2001 From: Bill Zissimopoulos Date: Tue, 7 Feb 2017 17:15:41 -0800 Subject: [PATCH] launcher: change registry location --- Changelog.asciidoc | 1 + doc/WinFsp-Service-Architecture.asciidoc | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/Changelog.asciidoc b/Changelog.asciidoc index 40564864..a4302c56 100644 --- a/Changelog.asciidoc +++ b/Changelog.asciidoc @@ -6,6 +6,7 @@ v1.0RC2:: This is the WinFsp 2017 Release Candidate 2. Some important changes included below: - WinFsp is now available under the GPLv3 with a special exception for Free/Libre and Open Source Software. +- The location of the WinFsp launcher registry entries is now `HKEY_LOCAL_MACHINE\Software\WinFsp\Services`. [On Win64 the actual location is `HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\WinFsp\Services`.] This change was necessary to avoid loss of third party file system registry entries during WinFsp uninstallation. [See GitHub issue #31.] - Despite stating in the previous release that the API has been finalized the `ReadDirectory` `FSP_FILE_SYSTEM_INTERFACE` operation has been changed. Extensive testing with multiple file systems has shown that `ReadDirectory` was hard to implement correctly. The new definition should make implementation easier for most file systems. [See GitHub issue #34.] - Some API's to facilitate `ReadDirectory` implementation have been added. Look for `FspFileSystem*DirectoryBuffer` symbols. - The installer now (optionally) installs a sample file system called "passthrough". This is a simple file system that passes all operations to an underlying file system. There is also a tutorial for this file system (in the doc directory). diff --git a/doc/WinFsp-Service-Architecture.asciidoc b/doc/WinFsp-Service-Architecture.asciidoc index b520588e..bf5bbc3c 100644 --- a/doc/WinFsp-Service-Architecture.asciidoc +++ b/doc/WinFsp-Service-Architecture.asciidoc @@ -46,4 +46,4 @@ One final note regarding security. Notice the `Security` registry value in the e WinFsp includes a Network Provider that integrates with Windows and can be used to start and stop user mode file systems from the Windows shell. To achieve this the Network Provider (implemented as part of the WinFsp DLL) works closely with the WinFsp.Launcher service. -For example, if a user uses the Windows Explorer to map `\\memfs64\share` to the `Z:` drive, the Network Provider will instruct the WinFsp.Launcher to start an instance of the memfs64 service with command line `-u \\memfs64\share -m Z:`. When the user disconnects the `Z:` drive, the Network Provider will instruct the WinFsp.Launcher to stop the previously started instance of the memfs64 service. +For example, if a user uses the Windows Explorer to map `\\memfs64\share` to the `Z:` drive, the Network Provider will instruct the WinFsp.Launcher to start an instance of the memfs64 service with command line `-i -F NTFS -n 65536 -s 67108864 -u \\memfs64\share -m Z:`. When the user disconnects the `Z:` drive, the Network Provider will instruct the WinFsp.Launcher to stop the previously started instance of the memfs64 service.