\Services\Smbserver\SMB\Shares\VirtualRoot\UserList '*'
\Services\Smbserver\SMB\Shares\VirtualRoot\Path 'a valid path' \Services\Smbserver\SMB\Shares\VirtualRoot\Type Dword:0 My registry settings are all under HKEY_LOCAL_MACHINE: Ident\Name 'aName' It would be 'interesting' to rebuild NK.exe).ĭo I need to rebuild the OS to use a hive-based registry? That way, I can just set the registry values programatically in my application program, restart the SMB service, and not have to rebuild the kiosk NK.exe (the kiosk NK.exe seems to include the smbserver.dll - it was built by a not very competent third party, and the tools to rebuild it go back to Visual Studio 2005. I'd hoped that refreshing the SMB server process would be enough to get file sharing going. I wonder if it's necessary for the SMB registry settings to be available at boot time? My devices is NOT using a hive-based registry, so the registry settings aren't available a boot time. However, I never see the service advertised when I attempt to attach an SMB client (for example, by looking for file shares in desktop windows, or attempting to connect an SMB client to the IP address of the WinCE device. I've set (hopefully) suitable registry values, and then re-started the SMBServer process: When I start, SMB0: is running as smbserver.dll My initial attempts have mostly been with the desktop version of NK.exe.
I'm attempting to configure an SMB file sharing server on a Windows CE 6 device.
