IE Dev Toolbar 1.00.2188.0 annoying popup fix
Some time ago Microsoft has released great addon to Internet Explorer called Internet Explorer Developer Toolbar. Latest version 1.00.2188.0 bring many great features, however it also brings huge annoyance with IE7 and any script debugger installed on system such as Visual Studio 2005 - an error popup asking for debugger selection every time we open new page. Want to know how to fix it?
How to fix that ?
It is possible to fix that with any good Resource Editor. Follow the recipe to get rid of popping up JavaScript error:
- Close all Internet Explorer windows.
- Locate and extract IE Dev Toolbar JavaScript source using any resource editor. Open C:\Program Files\Microsoft\Internet Explorer Developer Toolbar\IEDevToolbar.dll and extract resource TXT/235/1033 (type/resource ID/resource language). I used Resource Extractor extension of Total Commander. Alternatively you can use XN Resource Editor. I didn’t use Resource Hacker for this because it was saving the resource as hex-dump rather than binary file.
- Modify extracted JavaScript source 235.bin using any text editor. Locate function:
function ParseDoc(doc) { var aRules = GatherRulesFromDoc(doc); collSelectors = parser.Parse(aRules); // Set quirks mode if necessary if("BackCompat" == doc.compatMode) { for(var i = 0; i < collSelectors.Count; i++) { collSelectors.item(i).SetQuirksMode(true); } } }Change red marked line into:
try { collSelectors.item(i).SetQuirksMode(true); } catch(e) {} - Save back the resource file 235.bin into TXT/235/1033 of IEDevToolbar.dll. I used “replace” function of Resource Hacker.
Now you should have fixed IEDevToolbar.dll, that is not raising any errors anymore.
Note
Please don’t ask me about any binaries as it is against EULA of IE Dev Toolbar.
I have Replaced error line by this, but no luck
anyone lucky temme does it worked after replacing it ?
Regards,
Manish
Thank you very much.
I had problems with Total Commander but XN ResourceEditor worked smoothly.
Cheers, JR
[...] questo fastidioso popup. Le istruzioni su come effettuare le modifiche sono disponibili su questa pagina. Riassumendo: 1. Chiudere eventuali istanze aperte di Internet Explorer. 2. Individuare il file [...]
Well, this try…catch around the setQuirksMode call turned out to not quite enough for me. When visiting local files, I would get access denied errors in other parts of this code. But the same idea will work applied in a different place.
function ParseDoc()
{
try { api.ParseDoc(doc); } catch (e) {}
}
Also the XN resource editor appears to have problems saving the modified dll file, or it doesn’t complain if it can’t save for some reason. But if I Save as… using intermediate files, the newly saved dll is correct.
By the way, I think I am suddenly seeing this error because some other upgrade or software installation exposed this bug. MS developers may not be seeing this bug because they know how to work around it. I can’t believe they would tolerate the choice of either disabling the useful toolbar, or getting a popup error on almost every page.
This, from Victor Ott above, worked for me:
‘I used “XN Resource Editor”, saved the resource as .txt file, edited it, removed the old one (English USA), imported the editedone, changed language property to “English USA” and everything went smooth.’
A couple notes that might help.
* To save the 235.bin resource, right-click on the resource icon under the 235 ‘folder’ and select Export Resource.
* I used Notepad++ to edit the 235.bin file.
* To delete the old resource in the dll, right-click and select ‘Delete Resource’.
* To add the edited 235.bin back into the dll, select Resource menu: Import User Resource…, and select the file.
For me the edited resource ended up under a BIN folder rather than the original TXT folder, but I don’t think it cares. Maybe saving as .txt will help - I didn’t do that.