![](/images/new-backgrounds/1145464/145464569x1.webp)
Network Considerations | I |
Newt Networking Software |
After configuring Vines for NDIS driver support, install Newt. Select "None" when asked for a hardware Vendor.
Once Newt is installed, edit the protocol.ini file in the Vines directory to add the following section:
[NETMANAGE]
DRIVERNAME=NETMNG$
BINDINGS=hardware driver name
The hardware driver name should be the same as that used in the drivers section of the protocol.ini file (section that identifies the hardware used).
Add a line to the config.sys just after the line where the NDIS network driver is loaded as follows:
device=c:\netmanag\netmanag.dos
Delete the following line from your autoexec.bat file (the Newt Setup program placed it there):
c:\netmanag\netbind
At present, the Banyan TCP/IP software package doesn’t support winsock.dll. Since this is needed to run NetDAQ Logger, you must replace the Banyan TCP/IP package with Newt.
Newt TCP/IP vs. Windows for Workgroups |
Microsoft Windows for Workgroups contains
If you already have the TCP/IP for Windows for Workgroups optional software package from Microsoft, you do not need to install Newt. Just install NetDAQ Logger. It will use the winsock.dll included in your TCP/IP package.
We recommend that you upgrade to Windows for Workgroups Version 3.11 before attempting to install Newt and NetDAQ Logger. You should also have Windows for Workgroups configured and operating with networking enabled before starting Newt installation.
After ensuring that the proper version of Windows for Workgroups is installed and working properly, install Newt. Select "None" when asked for a hardware Vendor. Aside from that, install Newt in the same way as described above.
Newt will modify the following files: