To: Reginald Middleton who wrote (13694 ) 10/25/1997 6:00:00 PM From: Richard M. Smith Respond to of 24154
IE4 is *very* buggy....... I just installed Internet Explorer 4 on my home computer. I am surprised at the number of bugs that I found in only a few hours of use: - I have both Communicator 4 and IE4 installed on my system. I found that IE4 must be the default Web browser. Otherwise, when a URL is typed in the IE4 address box, in starts up Netscape Navigator to view the HTML page! So there is no way to view an HTML page in IE4 if IE4 isn't the default Web browser. Luckily Netscape doesn't have this "feature". If I were into conspiracy theories, it would appear to me that Microsoft is attempting to force people into using IE4. However, my guess this is just a bug. - FrontPage Express won't open HTML pages from the Web on my computer. It always fails with an error box saying that it can't do it. No reason is given by FrontPage what the problem is. The error shows up both from the File|Open command in FrontPage and the Edit|Page command in IE4. - My default IE4 Email reader is Eudora. If I select the IE4 File|Send command, IE4 gets all confused and attempts to start up the Outlook mail reader in Microsoft Office. Things go from and bad to worse as Outlook puts up all of these weird dialog messages about corrupted files. If I reconfigure IE4 to use Outlook Express as my Email reader, everything works just fine. Another conspiracy? - The code which allows editting of the favorites window is busted. I some how got into a state where it started deleting sites on me and corrupting links. - I sometimes get this odd "Server Busy" dialog box while using IE4 saying that an operation can't be completed because the "Dial-Up Networking" program is busy. As far as I can tell, IE4 is working fine otherwise. I am not even sure what operation can't completed. Very annoying especially since the "cancel" button in the dialog button is disabled. The only option is to retry. - The built-in favorite "Cool Sites : Link Central" (http://www.msn.com/access/links/other.htm) comes up with a page not found error (404). Link rot in a product that's only 3 weeks old? - The built-in favorite "Links : Best Of Web" (http://home.microsoft.com/exploring/exploring.asp) comes up with the gebrish when I click on it: Microsoft VBScript runtime error '800a000d' Type mismatch: 'bc.majorver' /exploring/exploring.asp, line 71 Search button give 404 - I got a 404 error (page not found) the first time I pushed the search button. The problem disappeared a few hours later. Not exactly user friendly behavior. - After using IE4 for awhile, I got a GP fault inside of Windows and had to reboot. This doesn't usually happen on my home system. I do get application crashes, but not OS crashes. - The first time I attempted to use IE4, it was in some odd state called "Not Browsing". There was a "Not Browsing" command checked on the File menu, and the only page that IE4 would go to is "about:NotBrowsing". I couldn't uncheck the "Not Browsing" command. The solution to this problem was a system reboot. I haven't seen the problem since. - In the IE4 setup program, the "install addons" option is implemented as a series of HTML pages. It will fail if the default browser isn't IE4. - I had to fiddle with my desktop font size settings to get the IE4 tool bar to fit on my screen. I am running in 1024 by 768 mode, so there are plenty of pixels on the screen, but IE4 wants even more. With a font size of 12 for icons, the tool bar is too big for the screen. I had to drop the font size to 10 to get things to fit. This problem has never shown up before in any other Windows application. - Selecting "Help | Microsoft on the Web | Search the Web" gives a 404 error (page not found). The URL that IE4 is trying is "http://home.microsoft.com/access/allinone.asp". More link rot? - Selecting "Help | Microsoft on the Web | Best of the Web" gives the error message "HTTP 1.0 Invalid Application Name". I have not idea what this error means. - The Java virus that reformats hard drives failed in IE4 because the Microsoft JVM doesn't implement the JNI class library. (Yes, this last "bug" is a joke.) Richard