
  ----------------------------------------------------------------------
              README for Microsoft Internet Explorer 4.0 Preview 1 
                   For Microsoft Windows 3.1/ Windows NT 3.51
                                     July 1997            
  ----------------------------------------------------------------------

                      (c) Copyright Microsoft Corporation, 1997


------------------------
HOW TO USE THIS DOCUMENT
------------------------

To view Readme.txt on screen in Notepad, maximize the Notepad window.

To print Readme.txt, open it in Notepad or another word processor, 
and then use the Print command on the File menu.


--------
CONTENTS
--------

SYSTEM REQUIREMENTS

INSTALLING INTERNET EXPLORER 4.0

USING INTERNET EXPLORER 4.0
Changing Initialization Settings for Modems
Using the Dialer
Installation with Existing TCP/IP Connections and ISP Accounts	
How to Use Multiple Winsock
Automatically Loading the Subscription Manager
Internet Explorer Settings
Using Third-Party Telnet Helper Applications
Uninstall
Features Not Available in This Release
Object Model Differences
Settings for Java
Known Issues with Java on Windows 3.1
Technical Support

KNOWN ISSUES AND BUGS


-------------------
SYSTEM REQUIREMENTS
-------------------

This version is intended for users of Microsoft(R) Windows(R)
3.1/3.11 ,Windows for Workgroups 3.1/3.11 and Windows NT 3.51. 
If you are using Microsoft Windows 95 or Windows NT(R) 4.0, you 
can download a version optimized for these platforms at: 
  http://www.microsoft.com/ie/default.asp


Caution
For this Preview 1 release, do not install this version of Internet Explorer 
4.0 on a computer running Windows 95 or Windows NT 4.0 that has the Win32 version
of Internet Explorer 4.0 installed. The two versions of Internet Explorer cannot coexist.


Because this version is a 16-bit program, you do not need
to have Win32s(R) installed on your computer.

This preview release has not gone through final performance tuning and 
requires more memory and processor power than the final release will require.
In order to use this release, you will need:

- To run the browser only:
  - 8 MB memory, 486 processor required; 16 MB strongly recommended

- To run the browser and the VM for Java(TM):
  - 12 MB memory, 486 processor required; 16 MB strongly recommended

- Microsoft Windows 3.1 or 3.11, Microsoft Windows for Workgroups 3.1 
  or 3.11, or Windows NT 3.51 (Service Pack 4 is required if you want to run 
  Java applets)

- A VGA monitor or better

- A mouse

- A 9600 BPS modem or a LAN connection


--------------------------------
INSTALLING INTERNET EXPLORER 4.0
--------------------------------

Internet Explorer 4.0 supports Active Setup. The setup process is very simple.
You can install Internet Explorer from a browser or download it and then run the 
Setup program. 

When you install Internet Explorer 4.0, it downloads the files into a directory 
called IE4SETUP. Later, you can run the Setup program from this directory to 
install Internet Explorer again. 

Uninstall will be included in future releases.

We are not supporting upgrades in Preview 1.


Caution
For this Preview 1 release, do not install this version of Internet Explorer 
4.0 on a computer running Windows 95 or Windows NT 4.0 that has the Win32 
version of Internet Explorer 4.0 installed. The two versions of Internet Explorer 
cannot coexist.


---------------------------
USING INTERNET EXPLORER 4.0
---------------------------

Changing Initialization Settings for Modems
-------------------------------------------
If you are using an older phone system or hardware, or if you are installing 
a "generic" modem, the existing initialization settings for the modem might 
not be sufficient. If you have problems with the modem, you may need to modify 
the Modems2.ini file in order to change the initialization settings.  

Use Notepad or another text editor to open the file, and then, in the modems 
section, locate the line for the modem, and modify the InitString line as 
needed.


Using the Dialer
----------------
The dialer can be configured to run a script every time a connection 
is made. To do this run, Iescript.exe (which is located in the same 
directory as Internet Explorer).

In order to use the dialer with a PBX that does not have a dial tone, 
you need to modify the DialString in the "Dial-In Configuration" 
section of the Shivappp.ini as follows:

  [Dial-In Configuration]
  DialString=ATX3D

Note that adding the X3 command affects all locations and only functions
properly with Hayes-compatible modems.

To access an outside line, you might need to add a pause character (either 
a W or a comma, depending on your modem) after the outside access number, 
so that there is a pause before the outside number is dialed. To do this, 
click the My Locations tab, and then in the box labeled To Access An Outside 
Line, First Dial, type the outside line access number followed by a W or a 
comma. For example, if the number required to access an outside line is "9" 
and your modem's pause character is "," you would type the following in the box:
   
   9,

If you are running Windows NT 3.51, you must use RAS to connect to the Internet 
by using a modem. The dialer included with Internet Explorer will not work.

  
Installation with Existing TCP/IP Connections and ISP Accounts	
--------------------------------------------------------------

To use a third-party stack and dialer, make sure that the directory that 
the third-party Winsock.dll is located in is in your path. For example, 
if your Winsock.dll file is in the directory C:\Connect, add a line 
to your Autoexec.bat file immediately under your current PATH setting 
that reads: 

  PATH=%PATH%;C:\CONNECT


How to Use Multiple Winsocks
----------------------------

Internet Explorer looks for a Winsock.dll to use in the following order:

1. If there is a Winsock.dll file which is currently in use by another 
   program, Internet Explorer will  use it.
2. Look for a Winsock.dll located in the Windows directory.
3. Look for a Winsock.dll located in the path.
4. Look for a Winsock.dll located in the directory for Internet Explorer.
 
If you have Microsoft TCP/IP-32 for Windows for Workgroups installed, 
the Winsock.dll that this stack uses is in the Windows directory. By default, 
Internet Explorer will use this Winsock. In order to use the Winsock.dll that 
comes with Internet Explorer, or a third-party dialer, you should start the 
dialer first and then load Internet Explorer.

In order for Internet Explorer subscriptions to use a Winsock.dll other than 
the one in the Windows directory, the user should start the dialer first so the 
Winsock.dll accompanying the dialer is loaded into memory. You do not need 
to dial and connect to the Internet. 

You can stop using a third-party dialer and start using the dialer that comes 
with Internet Explorer without restarting Windows. To switch to other dialers,
you need to restart Windows.


Automatically Loading the Subscription Manager
----------------------------------------------

Ierunsub.exe is a small program used to load the Internet Explorer Subscription 
Manager automatically when you start Windows. This allows your subscriptions 
to be automatically updated at their scheduled times. 

The program is added to the Win.ini [Main] section load entry. Every time Windows 
starts, this program is started automatically. Unless this program is running, 
Internet Explorer subscriptions will not be updated. If you do not use this 
feature, you can take it out from Win.ini by using a text editor such as Notepad.


Internet Explorer Settings
--------------------------

Internet Explorer 4.0 uses the registry to store all settings. If you want to 
edit or view the current settings, you need to use Regedit. Unless you are a 
very experienced Windows user you should not do this.

A few settings have not yet been moved from the Iexplore.ini file to the 
registry, but these settings will be moved for the final release.  Internet 
Explorer 4.0 does not use Iexplore.ini. 


Using Third-Party Telnet Helper Applications
----------------------------------------------
There is a setting in the Windows registry which sets the Telnet program that 
Internet Explorer uses. If you want to change the Telnet program, you need to use 
Regedit to edit the following setting. Unless you are a very experienced Windows 
user you should not do this.

  HKLM\Software\Microsoft\Internet#Explorer\Helpers\Telnet = telnet.exe %s


Uninstall
---------

Automatic uninstall is not supported in this preview release. Previous versions 
of Internet Explorer should continue to work after IE4.0PP1 has been installed, 
but if you want to remove Internet Explorer, the following is a list of files 
to delete:

* The entire Internet Explorer 4.0 directory can be deleted.
* The files installed in the Windows System directory are:

    Urlmon16.dll
    Win16x.dll
    Mshtml16.dll
    Webchk16.dll
    Msapsp16.dll
    Jobexc16.dll
    Inseng16.dll
    Advpck16.dll
    Setupx16.dll
    Mlang16.dll
    WAB16.dll
    Icomm16.dll

The following files are shared by Internet Explorer versions 3.0x and 
4.0. If you want to continue to use Internet Explorer 3.0, do not delete these 
files:

    Comctlie.dll 
    Secur16.dll
    Security.dll
    Msnssp16.dll
    Basic.dll
    Schnl16.dll
    Secssp16.dll

If you are comfortable using Regedit, you can also delete the keys HKLM and HKCU 
under the root key.


Features Not Available in This Release
--------------------------------------

* PICS
* Plug-ins
* Form-based file upload (RFC 1867)
* Channels
* Browser DDE
* Auto-proxy configuration
* Internet News
* Outlook Express does not support LDAP, IMAP, or S/MIME

These features will be available in the final version of Internet Explorer 4.0.


Object Model Differences
------------------------

There are some differences in the object model for Preview release 1 
and Preview release 2. Pages written for Preview release 2 may not be 
displayed correctly in Preview release 1. 
 
The object model for IE for Win16 Preview release 1 (this release) is virtually 
identical to the IE 4.0 for Win32 Platform Preview Release 1 Object Model, as 
documented in  the Platform Preview 1 InetSDK documentation.


The following lists some of the differences between the IE 4.0 Preview 2 object 
model and the IE 4.0 Platform Preview 1 object model are:

1. Changes to the way that text ranges work.
2. Positioning syntax changes. The docTop, docLeft, docWidth, and   
   docHeight properties have been renamed to offsetTop, offsetLeft, 
   offsetWidth, and offsetHeight.
3. The getMember, removeMember and setMember properties have been 
   renamed getAttribute, removeAttribute, and setAttribute.
4. The string properties innerHTML, outerHTML, innerText, and outerText 
   are not supported.
	

Settings for Java
------------------
The settings for the VM for Java are in the system registry. Unless you are a 
very experienced Windows user you should not change these settings. 

The registry entries used by the VM for Java are:

HKLM\Software\Microsoft\Windows\CurrentVersion\Internet#Settings\
ClassPath:
 
                  Lists which directories to search for classes.
                  If you want to run Java applets on your local 
                  computer, you can put all the class files into 
                  an uncompressed Zip file and add the full path 
                  of the Zip file to your ClassPath string. 

                  For example:

                  ClassPath=c:\iedir\classes.zip;c:\myclass\myclass.zip

HKLM\Software\Microsoft\Windows\CurrentVersion\Internet#Settings\DefaultOptions: 
	
     The options for VM for Java 
     mx<number>   Sets the maximum Java heap size.
     ms<number>   Sets the minimum Java heap size.
     ss<number>   Sets the C stack size of the VM.
     oss<number>  Sets the Java stack size of the VM.
     verify       Verifies all classes when read in.
     verifyremote Verifies classes reading in over the network 
                  (default).
     noverify     Does not verify any class.

Typically, you do not need to change the default options settings. 
However, if you have problems running large and complicated applets 
(which include many classes and need more heap space), try increasing 
the numbers for the ms and mx settings. 

By default, ms is set as 600KB and mx is set as 2048KB. You can increase
the number of the ms option to 800KB or so; or increase mx to 3096KB 
or so. However, ms should not be larger than mx. You can try this when 
you see an Out Of Memory exception on the browser status bar.

*Java is a trademark of Sun Microsystems, Inc.


Known Issues with Java on Windows 3.1
-------------------------------------

Java is a 32-bit multithreaded environment that uses case-sensitive 
long file names and UNICODE. Windows 3.1 does not provide these services, which 
means they have to be emulated in the virtual machine. Further, computers 
running Windows 3.1 typically have slower processors and less memory than computers 
running Windows 95 or Windows NT, so fewer resources are available to applications. 
As a result, it is not possible to provide the same Java experience on Windows 3.1 
as on Windows 95 or Windows NT. Some of the symptoms you will see when you use 
Internet Explorer with Java applets are:

--  OutOfMemory exceptions on browser's status bar. This message 
    indicates an out-of-system-memory error. The Java virtual
    machine allocates limited memory for Java run time. If the
    Java applet is too big, it will use all the memory available
    on Windows 3.1.
--  General Protection Faults (GPFs) may occur when your system 
    runs out of USER or GDI resources. The  USER and GDI resources 
    are limited on Windows 3.1 and they are shared by all programs. 
    You may see GPFs in any applications when this happens.
--  For non-Latin1 versions of Windows, this release of Internet
    Explorer does not support loading Java applets in directories named 
    with extended characters. It will be supported in the next release.


Technical Support
--------------------
The VM for Java is supported through the Microsoft News Server. The
following newsgroup is dedicated to the discussion of the VM for Java and 
provides a great deal of support:

     news://msnews.microsoft.com/microsoft.public.java.win16.all

For support in using Internet Explorer, use this newsgroup:

     news://msnews.microsoft.com/microsoft.public.internetexplorer.win3.1x


---------------------
KNOWN ISSUES AND BUGS
---------------------

Password May Remain in Cache
----------------------------
When you restart the browser, the cached credentials for SSPI-based client 
authentication may not be cleared. This only happens when the Subscription 
Manager auto-loader (Ierunsub.exe) or Outlook Express is running. In this case 
you will need to restart Windows in order to clear your password from the cache.


Browser Might Become Unresponsive
---------------------------------
The browser might become unresponsive when it is handling some time-consuming 
tasks, such as printing. In this case, just wait until the task finishes. 
This will be fixed in a subsequent release. 


Width Property in a Script for an HR Causes General Protection Fault
---------------------------------------------------------------------
Using a script to set the width property of an HR causes a GPF to occur.

