Hi Dave, > > The NSIS script looks to use $INSTDIR to refer to the (default or > > chosen) directory in an appropriate way, but I can't be sure. > > The NSIS script should be OK, I'm more concerned about the > script code and DQSDTools.dll. But as I recall it, DQSDTools > exposes an InstallDirectory property, so the DQSD scripts can > ask the DLL where it's installed, so probably that's catered > for. It'd be nice to hear from someone running DQSD from > someplace other than C:\Program Files, though.
OK, so I've been investigating this further... I can't find a single location in the source code where C:\Program Files or C:\Program Files\Quick Search Deskbar is referenced directly. All file access seems to go through DQSDTools.WriteFile, which only allows writing in the install directory (read from registry, written there by the installer) or in the AppData directory (also dynamically looked up). I think you should try it out, and see if you can get it to run from, say, C:\temp\dqsd. Also, you could try adding some localsearches, verify that the history works (up- and down arrows should browse through the recent search history), etc. Does anybody have any fears about this? I'm feeling pretty calm :-) - Kim ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Archive: https://lists.sourceforge.net/lists/listinfo/dqsd-devel
