Configuration Notes

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 Console window size (cols:rows), show state (H=hide, N=normal, F=full-screen) and browser embedding (E) are specified in file conini.
The Console screen buffer size (cols:rows) is specified in file scrini.
Files nat32.js and mynat32.htm are generated each time NAT32 starts. Clicking a shortcut to mynat32.htm will always connect a web browser to the correct NAT32 Server Port.

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 Urls that are loaded into the Address Bar when a Web window is activated
dhcpd.ini The DHCP Server initialization file (user-defined)
dhcp.tcl A Tcl script that is executed whenever the DHCP Server performs an action
Script files can contain any NAT32 command, including names of files containing NAT32 commands, Tcl scripts and even Windows commands.

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.