Comments on: IE Dev Toolbar 1.00.2188.0 annoying popup fix

By: Manish Bansal

Manish Bansal — Mon, 25 Aug 2008 06:05:01 +0000

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

By: jrivero

jrivero — Thu, 03 Jul 2008 20:53:50 +0000

Thank you very much.

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

Cheers, JR

By: IE Dev Toolbar 1.00.2188.0 Dll Patching - Eurohackers.it Blog di informaica, notizie, programmazione, linux e tecnologia

Sun, 22 Jun 2008 11:15:29 +0000

[...] 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 [...]

By: Daniel LaLiberte

Daniel LaLiberte — Fri, 09 May 2008 14:06:58 +0000

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: Daniel LaLiberte

Daniel LaLiberte — Thu, 08 May 2008 23:38:17 +0000

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.

By: Daniel LaLiberte

Daniel LaLiberte — Thu, 08 May 2008 23:34:30 +0000

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.

By: paul

paul — Thu, 06 Mar 2008 14:51:56 +0000

couldnt get any of the resource editors to work so i couldnt fix the issue, any help greatly appreciated

By: Chepech

Chepech — Fri, 29 Feb 2008 23:37:40 +0000

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 !

By: Rob

Rob — Wed, 23 Jan 2008 13:30:07 +0000

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!

By: Rob

Rob — Fri, 04 Jan 2008 16:43:02 +0000

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!