View Single Post
  #2  
Old December 15th 05, 12:29 PM posted to microsoft.public.win98.gen_discussion
external usenet poster
 
Posts: n/a
Default Batch file for IE 6 - 5.5 dll replacement (explorer hang issue with bulk move/delete file operations)

I documented the problem and the work around and sent it to MS over a year
ago and while they were able to duplicate the problem, there has been no
fix. I suspect none will be forthcoming.
--
Regards


Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo



"Ivan Bútora" wrote in message
...
In regard to the issue of Explorer (with IE 6 installed) hanging on bulk
move/delete file operations, as documented on these two sites:

http://cquirke.mvps.org/bexp1.htm
http://www.frankprovo.com/win98ie6filesproblem.htm

I have created a batch file that will execute Frank Provo's workaround.
The download is available at

www.princeton.edu/~ibutora/IE_dll_patch.zip

The contents are browselc.dll and browseui.dll (most recent IE 5.5 SP2
version from June 2005), and my batch file. The batch file performs Frank
Provo's workaround, i.e. copying the IE 6 dll files to C:\Program
Files\Internet Explorer (for use when browsing the Internet), while
placing the IE 5.5 dll files into C:\Windows\System (for use when browsing
local folders).


Notes:
- The batch file *can* be applied in conjunction with an IE 6 SP1 patch,
i.e. apply a patch (say "No" to the restart prompt), and then run the
batch file, which will prompt you for a restart. After rebooting, you'll
have both the patch and the IE 5.5 files in the C:\Windows\System folder.
- You must not run the batch files twice in a row before rebooting, or
else you'll end up with the 5.5 files in IE's program directory.
- The batch file assumes that the MS-DOS name for your "C:\Program
Files\Internet Explorer" directory is "C:\Progra~1\Intern~1". It also
assumes that Windows is installed under C:\Windows.
- There is no warranty of any sort, i.e. if your computer blows up because
of this, it is not my problem. I just tried it on my own machine, though,
and it worked.


Feedback is appreciated.


Thanks and best regards,

Ivan


P.S. CQuirke, do you predict there is any chance at all that Microsoft
will fix this incredibly annoying and terrible bug before June 30, 2006?