Could be either.. BUT FARR tries to be smart and not resolve the UNC shares, so it probably was not that. the network path definitely could have done it.
Since it was clearing your launch history that did it, this confirms that i probably need to have a way for farr to figure out which drives are network drives and shouldnt have their shortcuts resolved, or else allow a manual specification of such drives.
Putting a list of those drives in Options might be best, performance-wise.
I don't know how you'd check which drives are network drives via C++ or another .Net language, but I do know that you can query through WMI for that information. Of course, you may not want to use that method because WMI can be slow sometimes. If you want to try it, though, you'd use the following WMI query:
Formatted for SQL
with the GeSHI Syntax Highlighter [copy or print
SELECT * FROM Win32_LogicalDisk WHERE DriveType=4
Win32_LogicalDisk is the WMI class representing drives on a computer, and where that class's DriveType attribute is 4, that drive is a network drive.