nanoANT » Blog Archive » IE Dev Toolbar 1.00.2188.0 annoying popup fix

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.

This entry was posted on Monday, June 11th, 2007 at 21:44 and is filed under Tweaks. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

29 Responses to “IE Dev Toolbar 1.00.2188.0 annoying popup fix”

1
June 20th, 2007 at 11:27 ezpot

Brilliant. This really works. I cannot believe that Microsoft cant get their head out of their arse to fix this. properly I used Visual C++
to edit the dll as described above but I couldn’t “replace” the bin file, I had to import the changed file as a new resource and then copy and paste the binary data from the new resource to the existing 235 one. I then deleted the new resource, saved the dll and now the toolbar works great.
2
June 20th, 2007 at 12:04 Adam

Well, this isn’t first time Microsoft doesn’t bother fixing some annoyance in widely used product. At least IEDev Toolbar is free product, yet.. I’ve submitted time ago some bug reports about Visual Studio 2005 Pro ($800 per license) that was introduced in SP1, that was making fancy release folder names like “release”, “Release” didn’t care of filename case, and well… they confirmed the bug, two weeks later they made it “won’t fix” because it doesn’t crash VS, later on they wrote that doesn’t appear in Orcas (VS2007).. so they don’t care, I may downgrade the SP1.
But for God’s sake I paid $800 and I expect they make an effort to support the product at last for 1 year !! So that’s why sometime we need to manage some bits & bites ourselves
3
June 29th, 2007 at 23:38 Marantz

AGAIN!
>> collSelectors.item(i).SetQuirksMode(true);

Any hint on the REAL cause of this bug ? Where this function is supposed to be defined ?
Why is it missing ? Editing resource files seem too much on the HACK side to me.
4
July 6th, 2007 at 12:06 Adam

@Marantz: Well, I just post here a cure for this bug. Editing the resource is only way to hack it, as it is an error directly inside internal IE Dev Toolbar scripts, and I think Microsoft is the right one to ask about the real cause of this problem and better solution.
5
July 24th, 2007 at 09:11 Peter

I’ve had the toolbar and VisualStudio 2005 installed on the current PC I’m using for a couple of months now and had been debugging javascript fine until today. Now the bug has bit…. no idea what triggered it to start failing.
6
July 27th, 2007 at 12:04 davins

When I am trying to reinstall the same version of Internet Explorer, A message has appear the following error message:Setup has detected a newer version of Internet Explorer already installed on this system.Setup cannot continue.
7
August 16th, 2007 at 11:39 Fabian Robok

Great stuff. Didn’t manage to find the location of this script, since I don’t have any third party search tool on this machine and as of Windows XP, explorer search no longer searches binary files for text.

This behaviour really seems to be related to IE Dev Toolbar 1.0 and Visual Studio being installed at the same time and affects IE 6.0 as well.

One hint for users of XN Resource Editor: The file extension determines where an imported customer resource will go. So, to be able to replace the existing resource, store as “235.txt” when exporting the original.

@davins [6]: This is normal (as far as Microsoft’s definition of normal goes). You cannot reinstall the same version of IE in XP.
8
September 6th, 2007 at 15:55 Stefan

There is a new version (date 05/09/2207) of the Developer Toolbar, that solved this problem for me
9
October 1st, 2007 at 17:01 glamour-agency

Digital Photography…

hey great stuff…
10
October 9th, 2007 at 09:18 Victor Ott

@Adam THANKS for this workaround! I wouldn’t have tracked it down to IE Dev Toolbar. For about one week I wondered why some parts of the pages I’m working on aren’t showing up. And because IE 6 is only my test browser (my main browser is Firefox) I haven’t noticed that it happens on almost every page.
@StefanI’ve downloaded last week the latest version 1.00.2188.0 from “5/9/2007″, uninstalled the old version and installed the new one: the error occured.

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.

Thanks again!
11
October 22nd, 2007 at 09:04 Microsoft Script Debugger breaking on a JavaScript ParseDoc function caused by IE Developer toolbar

[...] This post with a hack to edit IE Dev Toolbar with a resource editor and add a blank try catch block around the line in question. [...]
12
October 23rd, 2007 at 22:06 Tony

Victor,

Thanks for the pointer on “XN Resource Editor”! After an afternoon of trying to wrestle with Total Commander and the Resource Extractor extension, I was able to finally get things working in about ten minutes with XN Resource Editor.

Cheers!
13
November 6th, 2007 at 19:16 Carl

Brilliant! Thanks for the info. I was telling a co-working it was in a js file but couldn’t find it, then I realized it must have been compiled in a dll but I thought the debugger itself was the offender, not IE toolbar. I was looking in the debugger folder in program files (would have been looking for a long time!). I already had XN Resource Editor and Resource Hacker so it was a very simple fix!

Thanks!
14
December 13th, 2007 at 07:02 David

Instead of using a try .. catch block you could use the following:

for(var i = 0; i
15
December 28th, 2007 at 01:19 Nakago

It’s failing for FIELDSET elements for me. I’ve fixed the script by doing “if (collSelectors.item(i).SetQuirksMode)” check before invoking that method
16
December 28th, 2007 at 01:20 Nakago

nanoANT, respect and cheers!
17
January 4th, 2008 at 18:43 Rob

I tried following the instructions for Resource Extractor (extensino of Total Commander) and the XN Resource Editor but their one of these applications had the applicable functionality to get to the ParseDoc() function. Can someone shine a bit more light for me.

Thanks in Advance!
18
January 23rd, 2008 at 15:30 Rob

Just stopping by again to see if anyone else has had similar problems trying to implement this “fix” to the tool. Can anyone offer additional assistance?

Thanks in advance!
19
March 1st, 2008 at 01:37 Chepech

Thats the magic of Open Source, you don’t have to wait for some bureaucratic asshole to fix something that doesn’t represent profits.

I LOVE FIRE FOX Firebug for that !
20
March 6th, 2008 at 16:51 paul

couldnt get any of the resource editors to work so i couldnt fix the issue, any help greatly appreciated
21
May 9th, 2008 at 01:34 Daniel LaLiberte

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.
22
May 9th, 2008 at 01:38 Daniel LaLiberte

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.
23
May 9th, 2008 at 16:06 Daniel LaLiberte

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.
24
June 22nd, 2008 at 13:15 IE Dev Toolbar 1.00.2188.0 Dll Patching - Eurohackers.it Blog di informaica, notizie, programmazione, linux e tecnologia

[...] 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 [...]
25
July 3rd, 2008 at 22:53 jrivero

Thank you very much.

I had problems with Total Commander but XN ResourceEditor worked smoothly.

Cheers, JR
26
August 25th, 2008 at 08:05 Manish Bansal

I have Replaced error line by this, but no luck try { collSelectors.item(i).SetQuirksMode(true); } catch(e) {}
anyone lucky temme does it worked after replacing it ?

Regards,
Manish
27
November 17th, 2008 at 18:45 Hal Diggs

Access Denied error after this fix applied. oh the fun, ok this fix works but then you might get a new Access denied error.
below is my additional fix.

try {
      for(i = 0; i < ssCurrentSheet.rules.length; i++)
      {
        rulCurrentRule = new RuleWrapper(ssCurrentSheet.rules(i), ssCurrentSheet, i);
        aRules.push(rulCurrentRule);
      }
} catch(e) {}
28
February 18th, 2009 at 03:58 Andrew

IT works!! may thanks
29
March 23rd, 2009 at 17:02 Tony’s Technical Blog | Quirksmode Problems in IE7 After Installing the IE Developer Toolbar

[...] to check what’s going on in my browser. After some surfing around there net there appears to be a hack. It does mean getting a copy of XN Resource Editor to manually edit some of the IEDevToolbar.dll [...]

IE Dev Toolbar 1.00.2188.0 annoying popup fix

How to fix that ?

Note

29 Responses to “IE Dev Toolbar 1.00.2188.0 annoying popup fix”

Leave a Reply