These notes are for use as an aid to installing FTP's Workstation Pack release 2.3 with Windows For Workgroups 3.11 as far as enabling TCP and WFWG networking to co-exist. Included in the notes are minimal instructions for installing FTP 2.3, but these notes are not designed as a replacement for the FTP documentation - see the section entitled "FTP 2.3 basic installation steps".

Throughout these notes any reference to Windows for Workgroups is assumed to be for version 3.11, and all network driver configuration files are for i82596.

When installing FTP's release 2.3 the network stack should already be configured and working. If this is done the FTP installation routine will recognise an installed network driver interface and configure itself to use whichever type of network stack is in place (Packet Driver, ODI, or NDIS). For workstations that also require Novell NetWare connectivity, the preferred stack is now ODI. For LAN Manager connectivity the stack will be NDIS. A Packet Driver can only be used if WFWG is installed without network support so is not relevant here. These notes will therefore give more detail for an ODI based installation.

Confirm that WFWG is configured for ODI

Editing the protocol.ini file

Example Configuration Files

• autoexec.bat - ODI
  
• protocol.ini - ODI
  
• net.cfg
  
• config.sys

NDIS2 or NDIS3

FTP 2.3 Basic Installation Steps

• FTP 2.3 install routine does not recognise a network stack

NetWare and FTP under Windows

FTP Print Redirection under WFWG

IPB 2160

Confirm that WFWG is configured for ODI

Start by confirming that WFWG is configured to run its peer to peer networking (Windows Network Setup --> Install Microsoft Windows Network), and has had the NetWare Workstation Shell 3.x support installed running over ODI. Study the section entitled "Windows for Work Groups, NetWare, i82596 & ODI" in IPB 2160 to confirm this. A similar IPB which details this configuration for i82592 based systems is IPB 2164. If the NetWare shell and Windows utilities are not actually required they can be removed after the FTP installation.

ODI or NDIS configurations for FTP on WFWG systems must contain entries for a Packet Driver interface in the file c:\windows\protocol.ini. The FTP installation routine will fail to recognise the network stack without such an entry. No such entry will exist after a WFWG installation even in a NetWare environment - see the section entitled Editing the protocol.ini file.

Editing the protocol.ini file

Before reviewing the various example files that are shown later in these notes, add a [PKTDRV] section to allow FTP PC/TCP 2.3 to recognise the network stack during its installation. It is likely that such a section will not already exist. WFWG uses the file protocol.ini for configuration of the various network stack modules. This file is used for an NDIS stack or ODI stack configuration.

FTP expects to be talking to a Packet Driver interface, add the following to the end of the c:\windows\protocol.ini file:-

[PKTDRV]
DriverName = PKTDRV$
Bindings = APR$596
Intvec = 0x65
Chainint = 0x66

Here, PKTDRV$ refers to the Packet Driver interface which is actually what FTP call the ODI to packet driver converter program when running ODI, or the Packet Driver to NDIS converter (dis_pkt.gup which is loaded by the config.sys file) when running NDIS. The ODI to packet driver converter program is also referred to as the ODI Packet Driver and is the file ODIPKT.COM. - see the section entitled "Example configuration files" later in these notes.

Important note: Ensure that the ODIPKT.COM supplied on the FTP 2.3 floppy (Disk 5 of 6) is used - other public domain versions are known to cause TCP to hang. This file is 5765 bytes and dated 10/11/93. The FTP installation will install its ODI Packet Driver into the c:\pctcp directory by default, so ensure that this is the file being executed by autoexec.bat.

Example configuration files

These example files show the configuration once FTP PC/TCP is installed. The FTP added entries are given in the comments that follow each relevant example, so when reviewing these files prior to installing PC/TCP, ignore such entries.

autoexec.bat - ODI

@ECHO OFF
PROMPT $p$g
PATH C:\WINDOWS;C:\DOS
lh C:\WINDOWS\SMARTDRV.EXE
C:\WINDOWS\net start

lh c:\windows\lsl
lh c:\windows\82596odi
lh c:\windows\ipxodi
C:\windows\odihlp.exe
lh c:\netx

lh KEYB UK,,C:\DOS\KEYBOARD.SYS

H:login johneu <c:\novell.pwd
lh doskey

rem ******* PC/TCP INSTALL ADDED LINE(S) - BEGIN ******
rem ** If you do not have lsl and odi driver already running from **
rem ** autoexec.bat before this, please do so. **
C:\PCTCP\ODIPKT.COM
SET PATH=C:\PCTCP;%PATH%
SET PCTCP=C:\PCTCP\PCTCP.INI
C:\PCTCP\ETHDRV.EXE
rem ******* PC/TCP INSTALL ADDED LINE(S) - END ******

rem ### FTP Interdrive drive redirector
idrive

rem ### FTP print redirection - config in pctcp.ini
predir

Note the section that is added by the FTP installation routine -

rem ******* PC/TCP INSTALL ADDED LINE(S) - BEGIN ******
to
rem ******* PC/TCP INSTALL ADDED LINE(S) - END ****** .

These entries were created in the file C:\pctcp\aexecftp.bat by the install routine and once verified as acceptable this file is manually copied to C:\autoexec.bat after the installation completes.

The ODI stack is loaded by the following section of the autoexec.bat file - note here that the NetWare workstation shell is also being loaded:-

lh c:\windows\lsl
lh c:\windows\82596odi
lh c:\windows\ipxodi
C:\windows\odihlp.exe
lh c:\netx

If NetWare connectivity was not being installed the ODI stack entries would appear as:-

lh c:\windows\lsl
lh c:\windows\82596odi
C:\windows\odihlp.exe

The lh c:\windows\lsl entry is the Link Support Layer (LSL) part of the ODI stack and the lh c:\windows\82596odi entry is the Multiple Link Interface Driver (MLID) part. The LSL and MLID programs and the net.cfg file should all reside in the same directory - by default this will be c:\windows.

FTP's ODI Packet Driver is loaded by the line:-

C:\PCTCP\ODIPKT.COM

See the comments after the net.cfg file example for possible command line arguments that could be used with odipkt.exe.

The FTP TCP kernel is loaded by the line:-

C:\PCTCP\ETHDRV.EXE

The last two entries are for loading FTP's Interdrive (drive redirection to Unix host via NFS) and FTP's print redirection. These are not needed for connections using FTP's terminal emulators, but may well be required later. Refer to the FTP documentation for further information:-

idrive
predir

protocol.ini - ODI

This will by default be c:\windows\protocol.ini.

[network.setup]
version=0x3110
netcard=ms$odimac,1,MS$ODIMAC,4
transport=ms$nwlinknb,NWLINK
transport=ms$netbeui,NETBEUI
lana0=ms$odimac,1,ms$netbeui
lana1=ms$odimac,1,ms$nwlinknb

[PKTDRV]
DriverName=PKTDRV$
BINDINGS=APR$596
INTVEC=0x65
CHAININT=0x66

[net.cfg]
PATH=C:\WINDOWS\net.cfg

[MS$ODIMAC]

[Link Driver 82596]
data=Frame Ethernet_SNAP
data=Frame Ethernet_802.2
data=Frame Ethernet_II
data=Frame Ethernet_802.3
data=Link Driver 82596

[NWLINK]

BINDINGS=82596

[NETBEUI]
BINDINGS=82596
LANABASE=0
SESSIONS=10
NCBS=12

Note here the [PKTDRV] section referred to earlier in these notes and the [net.cfg] section which is needed to define the location of the net.cfg file which is the configuration file for the ODI stack.

net.cfg

This is the ODI configuration file and is by default c:\windows\net.cfg as mentioned after the autoexec.bat example file.

Link Driver 82596ODI

Frame Ethernet_802.3
Frame Ethernet_II
Frame Ethernet_802.2
Frame Ethernet_SNAP
Protocol IPX 0 Ethernet_802.3

Note here that the order of these entries is important, especially where NetWare connectivity is also required.

Note too that the entry Frame Ethernet_II may have to be referred to specifically by the C:\PCTCP\ODIPKT.COM entry. The method of specifying the entry in the net.cfg file of the form C:\PCTCP\ODIPKT.COM 2, where the 2 specifies the second entry in the net.cfg file, appears to be for the public domain ODI Packet driver that is available from area 37 of Apricot Insight BBS. As mentioned earlier this ODI Packet driver is known to hang the system with FTP 2.3. When using FTP's ODI Packet driver the syntax is:-

c:\pctcp\odipkt frame=ETHERNET II.

This entry has been required on i82592 based systems. Normally no such entry is needed for i82596 based systems.

config.sys

ODI & NDIS
The config.sys file should have an entry as below - this is the real mode part of the WFWG 3.11 32 bit drivers:-

DEVICEHIGH=C:\WINDOWS\IFSHLP.SYS

For ODI there are no other relevant entries.

NDIS specific
For a non-32 bit (NDIS2) stack the config.sys file will be of the form:-

DEVICE=C:\WINDOWS\HIMEM.SYS
DEVICE=C:\DOS\APRUMB.SYS
DOS=HIGH,UMB
COUNTRY=044,,C:\DOS\COUNTRY.SYS
FILES=120
BUFFERS=20
DEVICEHIGH=C:\WINDOWS\IFSHLP.SYS
deviceHIGH=C:\WINDOWS\protman.dos /i:C:\WINDOWS
deviceHIGH=C:\WINDOWS\eth596.dos
deviceHIGH=C:\WINDOWS\msipx.sys
deviceHIGH=C:\WINDOWS\ndishlp.sys
LASTDRIVE=P
STACKS=9,256
DEVICE=c:\PCTCP\DIS_PKT.GUP

The NDIS stack for WFWG 3.11 is loaded by the following section:-

deviceHIGH=C:\WINDOWS\protman.dos /i:C:\WINDOWS
deviceHIGH=C:\WINDOWS\eth596.dos
deviceHIGH=C:\WINDOWS\msipx.sys
deviceHIGH=C:\WINDOWS\ndishlp.sys

The FTP supplied NDIS to Packet Driver Converter is loaded by the entry:-

DEVICE=c:\PCTCP\DIS_PKT.GUP

NDIS2 or NDIS3

For WFWG 3.11 an entry such as:-

device=protman.dos /i:c:\windows\

may NOT be required in config.sys for an NDIS installation. This is because the protocol manager for a particular network card may be a 32 bit enhanced mode driver (NDIS3) and is therefore part of the 32 bit networking drivers of Win 3.11. These run in protected mode and are installed at Windows runtime.

However, to use FTP PC/TCP under DOS then the autoexec.bat and config.sys files must be configured to load the older NDIS2 driver (see previous section entitled "Example configuration files") even if WFWG has been configured to use an NDIS3 driver. This is because the NDIS3 driver is not installed until WFWG starts. An NDIS3 driver is not available for i82592 based systems, but i82596 based systems are now supplied with an NDIS3 driver.

FTP 2.3 Basic Installation Steps

Having edited the protocol.ini, net.cfg (for ODI), config.sys, and autoexec.bat where appropriate by referring to the earlier sections in these notes, a basic FTP 2.3 installation should now be carried out. Carry out the following:-

• From the FTP floppy number 1 run install.
  
  
• When prompted for the serial number and key, note that the numbers should be entered with the "-" characters included. E.g. 1234-2222-5678
  
  
• Select the defaults of a new installation and a directory of C:\PCTCP
  
  
• You will then be asked to select the application groups to install. Base your answers on the following guidelines. Apricot's recommendations are highlighted in bold type:-
  
  

  Do you have a connection to the Internet?	NO
  If connected to the Internet and are therefore able to use the nicname command. (See FTP Command Reference manual). For most installations, answer no.
  Do you want to install the Windows 3.x applications?	YES
  Do you want the mail programs?	NO
  For installing the mail reader based on the Berkeley Unix mail program, or to access an nntpd Internet News daemon on the Unix host. (See Ref manual mail, nntp, pop2, pop3 etc.)
  Do you want to install Interdrive?	YES
  For drive redirection to Unix directories via NFS.
  Do you want NETBIOS capability?	NO
  If your network relies on NETBIOS - not required for NetWare + WFWG + FTP PC/TCP as described in these notes.
  Do you want to use PC/TCP with any Berkeley Unix systems?	YES
  Even though SCO Unix is not a Berkeley Unix it does have several Berkeley commands such as rcp and rcmd, of which the FTP equivalents are installed here. This also installs the lpr command which is for printing files on a Unix printer via LPD.
  Do you want the remote login programs that do terminal emulation?	YES
  To install tn (telnet), rloginvt (rlogin), wtnvt (Windows telnet if Windows apps selected), and others.
  Do you want the remote login programs that emulate no terminals?	YES
  To install "glass" terminal programs that do no emulations - they are used with a 3rd party terminal emulator that uses DOS INT 14.
  Do you want Kerberos authentication?	NO
  For a Unix/networking environment that is running Kerberos security - which is a 3rd party add on product.
  Do you want hot-key print redirection?	YES
  To install predir, the FTP printer port redirector that can redirect to a program of your choice such as lpr which uses the LPD protocol to access Unix printers.
  Do you have an IMAGEN laser printer on your network?	NO
  For printing to this specific type of network printer. (See Ref manual iprint command.)
  Do you want to use this PC as an LPD print server?	YES
  To print from Unix to a printer attached to the workstation via LPD, i.e. a remote printer as far as Unix is concerned. Configure SCO Unix to use such remote printers with the SCO mkdev rlp command. (See Ref manual lpd command).
  Do you want to use a serial port for your Internet connection?	NO
  To install the kernels for slip and ppp - these are for TCP/IP over serial lines.
  Do you want to run a Novell NetWare Client over PC/TCP?	YES
  When using an ODI stack this will load the FTP ODI Packet Driver odipkt.com referred to earlier in these notes.

FTP 2.3 install routine does not recognise a network stack

• The install routine may fail to recognise an installed and running network stack and it will then present a menu to select the kernel required and other information. Do not abort the installation. If you do, the Windows applications such as WTNVT (Windows telnet terminal) etc. will not be correctly configured - no icons will be setup.
  
  The installation routine will ask what type of network stack is to be used and it will then offer to browse directories for the appropriate files. Select a Packet Driver and use the FTP supplied floppy labelled Packet-Driver Disk 6 of 6 as the disk to browse for a driver. Select any packet driver from this disk, say the 3C503 driver, and continue with the installation routine.
  
  The reason for doing this is that opting for a packet driver is the quickest way to force the installation routine to continue and it will simply add this to the aexecftp.bat file, which is by default in the C:\pctcp directory, (FTP's modified autoexec.bat file that can then be used in place of the original autoexec.bat).
  
  Once the installation routine has completed, remove this entry and edit such files as autoexec.bat, config.sys, protocol.ini, etc. to correctly configure the network stack that is actually desired. Review the sections in these notes entitled "Editing the protocol.ini file" and "Example Configuration Files".
  
  
• After the installation routine has installed most of the software based upon the answers given above it will prompt for permission to edit progman.ini, system.ini, and win.ini. Answer Y as copies are made.
  
  
• The installation routine will detect a Network Driver defined in the Windows system.ini file - the network.drv=wfwnet.drv entry. The installation routine asks if this can be replaced with FTP's network.drv entry - network.drv=pctcpnet.drv must not be done. See the section later in these notes entitled "FTP Print Redirection under WFWG". If NetWare print redirection etc. is required under Windows see the section later in these notes entitled "NetWare and FTP under Windows".
  
  
• The installation routine proceeds to its "Phase III" which displays a scroll bar menu entitled "PC/TCP Kernel and Application Configuration". This is actually the program kappconf and can be run at any point after installation for further configuration. Select Basic Network Configuration from the list to define the IP address, subnet mask, host name, and other information.
  
  
• Select Detailed Network Configuration and then Kernel. The interface should already be set to ifcust0, the kernel interrupt will probably be 0x61. You will probably need to change the broadcast address which is set to 255.255.255.255 by default. For a class A network whose net number is 50, set it to 50.255.255.255. If there are old SCO TCP systems on the net (SCO TCP 1.1.3), the broadcast may need to be set to 50.0.0.0 so this setting may need clarification.
  
  
• It is possible to load the kernel into upper memory. This is defined in the Detailed Network Configuration --> Kernel menu. See the FTP manuals for more information. Recommended.
  
  
• Select Detailed Network Configuration --> User and enter the user's full name and user name. The user name entry defines the Unix username of the user. As far as a Unix host is concerned, the FTP workstation is recognised as by its hostname with a logged in user defined as user name in much the same way as any other Unix host. The username allows commands such as rcp to function and rloginvt to operate with no password being required - i.e. User Equivalence.
  
  
• Select Detailed Network Configuration --> Environment and define the host file entry. The likely entry will be C:\PCTCP\HOSTS. This is the hosts file that has the same function as the Unix TCP /etc/hosts file. There is no need to define the time zone and related entries at this time, they can be defined later by running kappconf.
  
  
• Exit and save at this point by entering escapes and then F10 to save and exit.
  
  
• View the file C:\PCTCP\AEXECFTP.BAT. This is the FTP modified autoexec.bat. It should have an added section such as:-
  
  rem ******* PC/TCP INSTALL ADDED LINE(S) - BEGIN *******
  rem ** If you do not have lsl and odi driver already running from **
  rem ** autoexec.bar before this, please do so. **
  C:\PCTCP\ODIPKT.COM
  SET PATH=C:\PCTCP;%PATH%
  SET PCTCP=C:\PCTCP\PCTCP.INI
  C:\PCTCP\ETHDRV.EXE
  rem ******* PC/TCP INSTALL ADDED LINE(S) - END *******
  
  This file may contain an entry for a Packet Driver such as the WD8003 as detailed earlier in these notes. A driver such as this should have been selected if the installation routine failed to recognise a valid network stack. Remove this Packet Driver entry (a single line).
  
  Copy C:\PCTCP\AEXECFTP.BAT to autoexec.bat.
  
  Note that manual configuration must be carried out if a Packet Driver entry was forced due to an invalid stack. Review these notes from the beginning for guidance.
  
  
• View the file C:\PCTCP\CONFIG.INS. For an ODI installation this file should be the same as config.sys, so no copying is required. For an NDIS installation an entry DEVICE=C:\PCTCP\DIS_PKT.GUP for the FTP supplied NDIS to Packet converter should be added. Copy this file to config.sys.
  
  
• Reboot the workstation and verify that the ODI Packet driver odipkt starts up without error, as does the TCP kernel ethdrv
  
  
• Create the hosts file c:\pctcp\hosts and include a Unix host to be used to test TCP connectivity. The format of the entries is as follows:-
  
  50.10.1.5 barney
  
  
• Use the ping command to test basic connectivity. Use the command ping -t barney. This will give a repeating echo request to a host called barney in a similar fashion to the SCO Unix ping barney command.
  
  If TCP does not function, check again for error messages at boot-up. The TCP kernel should include lines similar to those below at the end of its output at boot time:-
  
  5 free packets of length 1514, 5 free packets of length 160
  The Resident Module occupies 69.1K of conventional memory

If the installation routine failed to recognise the installed network stack review these notes from the beginning and manually configure autoexec.bat, config.sys, protocol.ini, and net.cfg (for ODI).

NetWare and FTP under Windows

As discussed in the "FTP 2.3 Basic Installation Steps" section above, you should not allow the install routine to replace the WFWG network driver defined in system.ini, if you do then WFWG peer to peer networking will be lost. If NetWare functionality is required under Windows or WFWG then the FTP 2.3 network driver cannot be loaded. However, drive redirection using FTP's Interdrive to a Unix host via NFS will function without the FTP network driver loaded - use the PC/TCP Network icon in the PC/TCP WinApps program group and select Drives to make a connection - such a connection can be set to be established at Windows boot time. For this configuration the network driver entries in the [boot] section of system.ini for WFWG would be as follows:-

network.drv=wfwnet.drv
secondnet.drv=netware.drv

FTP Print Redirection under WFWG

If FTP 2.3 print redirection to Unix via LPD is required under WFWG then the NetWare functionality under WFWG has to be sacrificed. For this configuration the network driver entries in the [boot] section of system.ini for WFWG would be as follows:-

network.drv=wfwnet.drv
secondnet.drv=pctcpnet.drv

This will allow drive redirection with FTP's Interdrive to Unix via NFS and print redirection to Unix via LPD under Windows as well as WFWG redirections.

IPB 2160

Please refer to IPB 2160, "Upgrading to Windows for Workgroups 3.11 with Apricot On-board Ethernet i82596".