Configuration and Installation

NAT32 configuration consists of two distinct procedures: Interface Selection and Interface Configuration.

The Interface Selection dialog shows a list of all adapters known to Windows on your machine. Some of those adapters may not actually be installed at the time and will be displayed in red. Select each adapter you would like NAT32 to use and then click an Adapter Type radio button.
Note that you should only click the One-way button if the adapter connects to a true one-way cable modem or to a Satellite device.
If you decide to use NAT32 in the presence of Windows ICS, click the ICS checkbox. Be sure to read the extended help pages on this topic before you do this.

Interface Configuration

An Interface Configuration dialog box will appear for each selected adapter. NAT32 auto-configuration will usually select the correct settings. Be sure to read the help page before you change any of the suggested settings.

Please click here for more NAT32 Configuration Details.

NAT32 Installation

While NAT32 does have a Windows Setup Application, its use is entirely optional. Setup.exe makes only minimal changes to your system registry, so it can be run with complete confidence. The prudent user may even wish to view the Setup Source Code, available here.

How to Uninstall NAT32

If you ran the Setup application to install NAT32, the changes it made to your system can be undone by running the Uninstall Application. Be sure to stop NAT32 before clicking OK.

Configuration Files

The list of selected interfaces is in file nat32ini, along with the connectivity type indicators.
Interface settings are in the files netcfg1, netcfg2 and so on for each configured interface.
The initial size and show state of the Console are specified in file conini.
The size of the Console screen buffer is specified in file scrini.

Script Files

startup	executed when NAT32 starts, specifies default settings
user.txt	executed just before startup exits (user-defined)
onexit	executed when NAT32 terminates
dialup.txt	executed before dialing takes place (user-defined)
hangup.txt	executed before a hangup takes place (user-defined)
connect	executed after a connection has been dialed
disc	executed after a connection is terminated
change	executed after an IP address change has occurred
typed.txt	loaded when a Web window is selected

File readme.txt contains a list of changes in each build. If a new NDIS3PKT driver is available, the build information will indicate this, and you must install the new version before you run that build.

File typed.txt contains URLs that are displayed in a Web window's combobox prior to the Typed URLs fetched from the Registry.

You may need to modify file startup, but note that custom settings should be placed in file user.txt, which is executed by startup just before it completes. File user.txt is not overwritten when you install a new build of NAT32.