Hi James, We've been looking into this back and forth for a while... The FEATURE_LOCALMACHINE_LOCKDOWN fix is not enough, as you've noticed, and honestly, I'm not sure what it takes to run DQSD under Windows XP SP2.
I think it may have something to do with the fact that comx creates external objects (Microsoft.XmlHttp in this case) - it seems all searches that do this get an InfoBar popup. That said, I have no idea what to do about it. Sorry, Kim > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > James Robertson > Sent: den 30 augusti 2004 21:55 > To: [EMAIL PROTECTED] > Subject: RE: [DQSD-Users] DQSD and Windows XP SP2 > > Kim - > > You posted a message a few weeks ago re. XP SP2 and modifying > a registry key to enable javascript etc. > originating from a local machine, specifically by doing the following: > > Add a DWORD value to > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet > Explorer\Main\FeatureControl\FEATURE_LOCALMACHINE_LOCKDOWN > named explorer.exe and set its value to 0. > > 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. The problem's not there > when windows are invoked by other searches I've tried, so > presumably there's a scripting-specific issue with comx.xml > > Any suggestions? ------------------------------------------------------- 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
