Among the powerful Windows Sysinternals tools there are two that can help you find the culprit. The first is 'Process Explorer' (https://technet.microsoft.com/en-us/sysinternals/processexplorer), a very detailed task manager from which the Windows Task Manager learned a lot in recent versions, and the second is 'Process Monitor' (https://technet.microsoft.com/en-us/sysinternals/processmonitor), a real-time file, registry and process watcher.
You can download and unzip them to any folder. Start with Process Explorer to see if a currently running process accesses your music files. Start procexp.exe either directly as admin or, once started, use it's File menu to restart it as admin. Then type Ctrl+F or click on the spyglass icon and enter the path to your music library. Process Explorer will give you a list of processes that *currently* have file handles open in this path. If this doesn't give you a hint, close it and try Process Monitor. Be careful: when it starts, it immediately captures hundreds of thousands of file and registry accesses and might slow down your system a bit. Stop capturing with a click on the magnifier glass icon or type Ctrl+E. Define a filter to exclude stuff you are not interested in. First, deselect all of the five right-most buttons in the toolbar except the one for file access (2nd from left in this group). Then click on the filter icon (or type Ctrl+L). Add two new filters to the list of predefined filters: 1) from the first dropdown list select 'Path', from the conditions select 'exclude', in the 3rd field enter the path to your music library and from the last list select 'exclude' and click the Add button (don't forget this!). This filter exludes all events that don't have the path you've entered. 2) from the first list select 'Operation', from the 2nd 'exclude', from the 3rd select 'WriteFile' and from the 4th 'exclude' and click Add(!). This filter excludes all events that are not about writing a file. Now close the filter window and re-enable capturing. Note that the filters just hide excluded events but still a huge amount of events need to be processed. But if no process is currently writing a file in your path, you'll see no events (you can temporarily create and modify a file manually to see the events are working). ------------------------------------------------------------------------ reinholdk's Profile: http://forums.slimdevices.com/member.php?userid=36070 View this thread: http://forums.slimdevices.com/showthread.php?t=106892 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
