James and all, > > I've done that (the key already existed) and the basic problem with > > DQSD is solved in so far as DQSD runs when my machine boots into XP > > SP2, *but* I'm still getting the script disabling problem > and warnings > > popping up when new windows are opened by the comx.xml search.
So, I figured out a workaround, but I'm not sure what it does for browser security... Adding iexplore.exe (Internet Explorer) to the FEATURE_LOCALMACHINE_LOCKDOWN, with the value 0, seems to let DQSD work fine. comx runs without hitches, and so does the help window (which also suffers from an InfoBar without it). I believe this is because most of DQSD runs inside explorer.exe (while it's hosted in the taskbar), but some parts start up a new IE instance, which brings iexplore.exe into the picture. While this makes DQSD run smoothly, it also opens up IE to the problems that SP2 was designed to solve [1]. I don't know to what extent "the Local Machine zone is used as an attack vector to load malicious HTML code" [1], but I hate to tell people to lower their security bar in order to run DQSD. Currently, this seems to be the only solution, though. Hope that helps, Kim [1] http://msdn.microsoft.com/security/productinfo/XPSP2/securebrowsing/localloc kdown.aspx ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ To unsubscribe visit: https://lists.sourceforge.net/lists/listinfo/dqsd-users [EMAIL PROTECTED] http://sourceforge.net/mailarchive/forum.php?forum_id=8601
