            USING WINDOWS FOR WORKGROUPS WITH INVISIBLE LAN

                Copyright 1993 Invisible Software, Inc.




       [See GUIDE.TXT for a list of all manuals and text files.]




-----------------------------------------------------------------------




TABLE OF CONTENTS

 1.  Introduction
 2.  Installation
    2.1.  Hardware Driver Options
    2.2.  Installing Drivers Using Setup
    2.3.  Installing Drivers Using Control Panel
    2.4.  Checking CONFIG.SYS
    2.5.  Special Requirements for Servers
    2.6.  Starting Windows For Workgroups
    2.7.  Installing the Invisible LAN Icons
 3.  Using Windows For Workgroups
    3.1.  File Manager
       3.1.1.  Using File Manager to Display Files on Network Drives
       3.1.2.  Using File Manager to Establish Drive Mappings
       3.1.3.  Using File Manager to Discontinue Drive Mappings
    3.2.  Print Manager
       3.2.1.  Using Print Manager to Display Network Print Queues
       3.2.2.  Using Print Manager to Change Network Print Queues
       3.2.3.  Using Print Manager to Establish Printer Mappings
       3.2.4.  Using Print Manager to Discontinue Printer Mappings
    3.3.  Control Panel
       3.3.1.  Using Control Panel to Establish Printer Mappings
       3.3.2.  Using Control Panel to Start the Network Manager
 4.  Drivers and Protocol Stacks
    4.1.  Standard Invisible LAN Protocol Stack
    4.2.  Invisible LAN Protocol Stack with NDIS
    4.3.  Windows For Workgroups Protocol Stack
    4.4.  Combined Protocol Stack with TransBIOS Hardware Driver
    4.5.  Combined Protocol Stack with NDIS Hardware Driver
 5.  Parameters and Manual Installation
    5.1.  WIN.INI Parameters
    5.2.  SYSTEM.INI Parameters
    5.3.  PROTOCOL.INI Parameters
    5.4.  CONFIG.SYS Parameters
    5.5.  Required Files




-----------------------------------------------------------------------




1.  INTRODUCTION


     Windows For Workgroups is a special version of Microsoft Windows
that includes built-in network functions.  The network functions are:

     *  A network server that makes disk and printers available to other
        network users.

     *  A network redirector that lets you access disks and printers on
        other computers running Workgroups, as well as LAN Manager
        servers and other SMB servers.

     *  Network DDE (Dynamic Data Exchange), which allows applications
        to share information across the network.

     *  A Clipbook application that lets you cut and paste information
        across the network.

     *  Enhanced versions of File Manager, Print Manager, and Control
        Panel, that provide improved network functionality.

     *  A Mail application that provides a store-and-forward electronic
        mail facility.

     *  A Scheduler application that is used to schedule appointments.


     Although Workgroups can function as a peer-to-peer network all by
itself, there are numerous advantages to using Workgroups together with
Invisible LAN:

     *  Invisible LAN provides much better performance, especially if
        you use Ultra Server.

     *  Invisible LAN allows both DOS and Windows computers to be full
        participants in the network.  Workgroups only allows Windows
        computers to participate fully in the network.

     *  Invisible LAN network functions continue to operate when you
        exit from Windows and return to DOS.  Workgroups network
        functions terminate when you exit from Windows.

     *  Invisible LAN has many features that Workgroups lacks, such as
        an extensive security system, access rights, UPS monitoring,
        audit trails, server usage monitoring, and remote control
        capability.


     When you configure Workgroups to run on Invisible LAN, you get what
is known as a "multinet" system.  Multinet means that you have two
complete networks running in the same computer at the same time.  All
the features of both networks are available.

     Moreover, a multinet computer can interoperate with computers
running either of the two networks alone.  Thus you can mix-and-match
multinet computers running both Invisible LAN and Workgroups, computers
running Workgroups alone, DOS-based computers running Invisible LAN
alone, Windows-based computers running Invisible LAN alone, and
computers running Ultra Server.  And all the computers can exist on the
same network and communicate with each other.




-----------------------------------------------------------------------




2.  INSTALLATION


     In order to run Workgroups on Invisible LAN, you need to install
three drivers:

     *  A network hardware driver.

     *  The TransBIOS Protocol driver.

     *  The Invisible LAN Network driver.


     The three drivers can be installed using Windows Setup, or Windows
Control Panel.  If you are installing Workgroups for the first time, you
use Windows Setup to install the drivers.  If you have already installed
Workgroups, and you want to add support for Invisible LAN, you use
Windows Control Panel.  These two procedures are described separately in
sections 2.2 and 2.3 below.

     After installing the drivers, you may have to make some final
manual changes to the configuration.  These are described in sections
2.4 and 2.5.

     Before beginning, make sure that you have already installed the
network board, and that you have used SETUP30 to install the Invisible
LAN software on your hard disk.




2.1.  HARDWARE DRIVER OPTIONS


     The hardware driver is a program that is responsible for
controlling the network hardware.  The hardware driver has to be
customized for the particular type of network hardware that you are
using.

     Invisible LAN comes with a collection of hardware drivers for
various types of hardware.  Windows For Workgroups also comes with a
collection of hardware drivers.  The drivers that come with Invisible
LAN are called "TransBIOS hardware drivers." The drivers that come with
Workgroups are called "NDIS hardware drivers."

     When you install both Workgroups and Invisible LAN, you can only
use one hardware driver.  It is possible to use either the TransBIOS
hardware driver or the NDIS hardware driver.  Here are the options:


     *  Option 1 -- Using the TransBIOS hardware driver.  This is the
        preferred option, since the TransBIOS hardware driver gives
        better performance.

        You can use this option on any Ethernet hardware, provided that
        there is a TransBIOS hardware driver available.

        To use this option, you need to set the "Network Hardware Type"
        in the SETUP30 program to match the hardware you are using.
        (Note -- you can't select "NDIS" as the network hardware type.)

        In Workgroups, you select "TransBIOS Ethernet Driver" as the
        network adapter.


     *  Option 2 -- Using the NDIS hardware driver.  You need to use the
        NDIS hardware driver if you are using Token Ring hardware, or if
        there is no TransBIOS driver available for your hardware.

        To use this option, you need to set the "Network Hardware Type"
        in the SETUP30 program to "NDIS."  (Note -- "NDIS" is only
        available in the serialized version of Invisible LAN.)

        In Workgroups, you select the network adapter that matches the
        hardware you are using.


     Before continuing, make sure that you know which option you want to
use.




2.2.  INSTALLING DRIVERS USING SETUP


     If you are installing Windows For Workgroups for the first time,
you use the Windows Setup program.  Proceed as follows:

     1. Proceed normally with Setup until the Add Network Adapter dialog
        box appears.

    2a. If you want to use the TransBIOS hardware driver, select
        "TransBIOS Ethernet Driver" from the list of adapters, and then
        choose OK.

        If "TransBIOS Ethernet Driver" is not included in the list of
        adapters, then select "Unlisted or Updated Adapter," choose OK,
        and type the directory where the Invisible LAN files are
        installed (usually C:\NET30).

        It is recommended that you use a TransBIOS hardware driver if
        possible.  Remember that if you select this option, you must set
        the "Network Hardware Type" in the SETUP30 program to match your
        network hardware.

        Workgroups displays the Settings dialog box.

    2b. If you want to use the NDIS hardware driver, select the network
        hardware you are using from the list of adapters, and then
        choose OK.

        Remember that if you select this option, you must set the
        "Network Hardware Type" in the SETUP30 program to "NDIS."

        Workgroups displays the Settings dialog box.  If you need to
        make changes to the adapter settings (for example, I/O port or
        interrupt number), do so now.

     3. Choose Protocols.

        Workgroups displays the Protocols dialog box.

     4. Select "TransBIOS Protocol" from the list of available
        protocols, and then choose Add.

        If "TransBIOS Protocol" is not included in the list of
        protocols, then select "Unlisted or Updated Protocol," choose
        Add, and type the directory where the Invisible LAN files are
        installed (usually C:\NET30).

        Workgroups lists both "TransBIOS Protocol" and "Microsoft
        NETBEUI" in the list of protocols in use.

     5. Choose OK to exit from the Protocols dialog box.  Then choose OK
        to exit from the Settings dialog box.  Then choose Continue to
        exit from the Network Adapters dialog box.

        Workgroups displays the Compatible Networks dialog box.

     6. Select "Invisible LAN" from the list of available network types,
        and then choose Add.

        If "Invisible LAN" is not included in the list of networks, then
        select "Unlisted or Updated Network," choose Add, and type the
        directory where the Invisible LAN files are installed (usually
        C:\NET30).

        Workgroups lists "Invisible LAN" in the list of other networks
        in use.

     7. Choose OK to exit from the Compatible Networks dialog box.

     8. Continue with Setup normally.




2.3.  INSTALLING DRIVERS USING CONTROL PANEL


     Use Control Panel if you have already installed Windows For
Workgroups, and you want to add support for Invisible LAN.  Proceed as
follows:

     1. Start Control Panel by double-clicking on the Control Panel icon
        in Program Manager.  Then double-click on the Network icon in
        Control Panel.

        Workgroups displays the Network dialog box.

     2. Choose Adapters from the button bar.

        Workgroups displays the Network Adapters dialog box.

        (Note -- Optionally, if you want to use the NDIS hardware
        driver, and the correct adapter is already listed in the Network
        Adapters dialog box, you can choose Setup and skip ahead to step
        number 6.  Otherwise, or if you're not sure, continue with step
        number 3.)

     3. If there is an adapter shown in the dialog box, choose Remove.

        Workgroups removes the adapter.  There should be no adapters
        shown in the dialog box.

     4. Choose Add.

        Workgroups displays the Add Adapter dialog box, which contains
        a list of supported adapters.

    5a. If you want to use the TransBIOS hardware driver, select
        "TransBIOS Ethernet Driver" from the list of adapters, and then
        choose OK.

        If "TransBIOS Ethernet Driver" is not included in the list of
        adapters, then select "Unlisted or Updated Adapter," choose OK,
        and type the directory where the Invisible LAN files are
        installed (usually C:\NET30).

        It is recommended that you use a TransBIOS hardware driver if
        possible.  Remember that if you select this option, you must set
        the "Network Hardware Type" in the SETUP30 program to match your
        network hardware.

        Workgroups displays the Settings dialog box.

    5b. If you want to use the NDIS hardware driver, select the network
        hardware you are using from the list of adapters, and then
        choose OK.

        Remember that if you select this option, you must set the
        "Network Hardware Type" in the SETUP30 program to "NDIS."

        Workgroups displays the Settings dialog box.  If you need to
        make changes to the adapter settings (for example, I/O port or
        interrupt number), do so now.

     6. Choose Protocols.

        Workgroups displays the Protocols dialog box.

     7. Select "TransBIOS Protocol" from the list of available
        protocols, and then choose Add.

        If "TransBIOS Protocol" is not included in the list of
        protocols, then select "Unlisted or Updated Protocol," choose
        Add, and type the directory where the Invisible LAN files are
        installed (usually C:\NET30).

        Workgroups lists both "TransBIOS Protocol" and "Microsoft
        NETBEUI" in the list of protocols in use.

     8. Choose OK to exit from the Protocols dialog box.  Then choose OK
        to exit from the Settings dialog box.  Then choose Close to exit
        from the Network Adapters dialog box.

     9. Choose Networks from the button bar.

        Workgroups displays the Compatible Networks dialog box.

    10. Select "Invisible LAN" from the list of available network types,
        and then choose Add.

        If "Invisible LAN" is not included in the list of networks, then
        select "Unlisted or Updated Network," choose Add, and type the
        directory where the Invisible LAN files are installed (usually
        C:\NET30).

        Workgroups lists "Invisible LAN" in the list of other networks
        in use.

    11. Choose OK to exit from the Compatible Networks dialog box.

    12. Choose OK to exit from the Network dialog box.

        At this point, Workgroups informs you that you must reboot your
        computer for the new settings to take effect.




2.4.  CHECKING CONFIG.SYS


     Invisible LAN includes two device drivers that are installed in
CONFIG.SYS.  They are called CACHE30.SYS and N30DEV.SYS.  CACHE30.SYS
must be the very first device driver listed in CONFIG.SYS, and
N30DEV.SYS must be the very last device driver listed in CONFIG.SYS.

     When you install network drivers in Windows For Workgroups, the
CONFIG.SYS file is modified.  Sometimes Workgroups adds device drivers
before CACHE30.SYS or after N30DEV.SYS.  If this happens, you must edit
the CONFIG.SYS file.

     After completing the network driver installation, you need to check
your CONFIG.SYS file to make sure that CACHE30.SYS is the first device
driver listed, and N30DEV.SYS is the last device driver listed.  If this
is not the case, then you need to do one of the following:

     *  Use a text editor to edit the CONFIG.SYS file so that
        CACHE30.SYS is the first device driver and N30DEV.SYS is the
        last device driver.

     *  Alternatively, run the SETUP30 program and select "Modify
        CONFIG.SYS" from the main menu.  SETUP30 automatically inserts
        the CACHE30.SYS and N30DEV.SYS device drivers in the correct
        order.




2.5.  SPECIAL REQUIREMENTS FOR SERVERS


     If your computer is an Invisible LAN file server, you need to edit
your SYSTEM.INI file.  The SYSTEM.INI file is a text file located in
your Windows directory (usually C:\WINDOWS).


     *  If your computer is a server, you must remove the following line
        from the SYSTEM.INI file:

                [386enh]
                device = vshare.386


     *  If your computer is a server, and you are using COM1 as a
        shared network printer, you must add the following line to the
        SYSTEM.INI file:

                [386enh]
                COM1AutoAssign = 0


     *  If your computer is a server, and you are using COM2 as a
        shared network printer, you must add the following line to the
        SYSTEM.INI file:

                [386enh]
                COM2AutoAssign = 0




2.6.  STARTING WINDOWS FOR WORKGROUPS


     You always need to start Invisible LAN before starting Windows For
Workgroups.  A typical start-up sequence is:

                NET30
                WIN




2.7.  INSTALLING THE INVISIBLE LAN ICONS


     The Invisible LAN icons provide access to Invisible LAN functions.
You should install the icons in a Program Manager group.

     To install the icons:

     1. Activate Program Manager.

     2. Select File from the menu bar, and then select Run from the
        drop-down menu.

     3. Type SETUPW and press Enter.


     The SETUPW program automatically creates a Program Manager group
called "Invisible LAN," and automatically installs all the Invisible LAN
icons in the group.




-----------------------------------------------------------------------




3.  USING WINDOWS FOR WORKGROUPS


     Windows For Workgroups includes enhanced versions of File Manager,
Print Manager, and Control Panel.  These enhanced versions have
additional network functionality.  This section describes the network
functions available in File Manager, Print Manager, and Control Panel.




3.1.  FILE MANAGER


     The Windows For Workgroups File Manager can display files on
network drives, establish drive mappings, and discontinue drive
mappings.




3.1.1.  USING FILE MANAGER TO DISPLAY FILES ON NETWORK DRIVES


     File Manager displays files in a tree diagram that shows the
directory structure.

     You can display the files on a network drive in exactly the same
way as you display files on a local drive.  The drive bar at the top of
the File Manager window shows the available drives;  network drives are
indicated by a special network icon.  To display the files on a network
drive, simply click on the corresponding icon.




3.1.2.  USING FILE MANAGER TO ESTABLISH DRIVE MAPPINGS


     To establish drive mappings:

     1. Select "Connect Network Drive" from the Disk drop-down menu.
        Or, click on the "Connect" icon on the toolbar.

        File Manager displays the Connect Network Drive dialog box.  You
        can use this dialog box to establish drive mappings for
        Workgroups file servers.

     2. Choose NetWare or Invisible.

        File Manager displays the Invisible LAN Drive Mappings dialog
        box.  You can use this dialog box to establish drive mappings
        for Invisible LAN file servers.


     Note -- You can also control your Invisible LAN drive mappings by
double-clicking on the Drive Mappings icon in Program Manager.




3.1.3.  USING FILE MANAGER TO DISCONTINUE DRIVE MAPPINGS


     To discontinue drive mappings:

     1. Select "Disconnect Network Drive" from the Disk drop-down menu.
        Or, click on the "Disconnect" icon on the toolbar.

        File Manager displays the Disconnect Network Drive dialog box.

     2. Select the drive(s) that you want to disconnect, and choose OK.

        File Manager discontinues the selected drive mapping(s).  You
        can discontinue one or more mappings.  This dialog box can
        discontinue both Workgroups drive mappings and Invisible LAN
        drive mappings.




3.2.  PRINT MANAGER


     The Windows For Workgroups Print Manager can display network print
queues, establish printer mappings, and discontinue printer mappings.




3.2.1.  USING PRINT MANAGER TO DISPLAY NETWORK PRINT QUEUES


     The main Print Manager screen shows the print jobs for each network
printer that you are using.  For each network printer, Print Manager
shows:

     *  The printer status.

        If the printer is paused, a "double bar" icon appears next to
        the printer.

     *  The network path for the printer.

     *  The number of jobs in the print queue.


     For each job in the print queue, Print Manager shows:

     *  The job status.

        If the job is currently printing, an "arrow" icon appears next
        to the job, and the word "Printing" appears in the status
        column.  If the job is currently queued, a "document" icon
        appears next to the job.  If the job is on hold, a "double bar"
        icon appears next to the job, and the word "Paused" appears in
        the status column.

     *  The title of the print job.

        For Invisible LAN printers, print jobs submitted by Windows
        applications have descriptive titles.  Print jobs submitted by
        the NETPRINT program have the file name as the title.  Print
        jobs submitted by other DOS programs have no title.

     *  The name of the user who submitted the job.

     *  The size of the job, in kilobytes.

     *  The date and time that the job was submitted.


     The print queue display is updated automatically every 30 seconds.
You can manually update the display by selecting Refresh on the View
drop-down menu, or by pressing F5.




3.2.2.  USING PRINT MANAGER TO CHANGE NETWORK PRINT QUEUES


     For Workgroups printers, you can use Print Manager to:

     *  Pause and resume the printer.

     *  Pause and resume individual print jobs.

     *  Delete individual print jobs.

     *  Rearrange jobs in the print queue.


     For Invisible LAN printers, Print Manager cannot change the print
queue in any way.  You need to use the Invisible LAN Network Manager to
change an Invisible LAN print queue.




3.2.3.  USING PRINT MANAGER TO ESTABLISH PRINTER MAPPINGS


     To establish printer mappings:

     1. Select "Connect Network Printer" from the Printer drop-down
        menu.  Or, click on the "Connect" icon on the toolbar.

        Print Manager displays the Connect Network Printer dialog box.
        You can use this dialog box to establish printer mappings for
        Workgroups file servers.

     2. Choose NetWare or Invisible.

        Print Manager displays the Invisible LAN Printer Mappings dialog
        box.  You can use this dialog box to establish printer mappings
        for Invisible LAN file servers.


     Note -- You can also control your Invisible LAN printer mappings by
double-clicking on the Printer Mappings icon in Program Manager.




3.2.4.  USING PRINT MANAGER TO DISCONTINUE PRINTER MAPPINGS


     To discontinue printer mappings:

     1. Select "Disconnect Network Printer" from the Printer drop-down
        menu.  Or, click on the "Disconnect" icon on the toolbar.

        Print Manager displays the Disconnect Network Printer dialog
        box.

     2. Select the printer(s) that you want to disconnect, and choose
        OK.

        Print Manager discontinues the selected printer mapping(s).  You
        can discontinue one or more mappings.  This dialog box can
        discontinue both Workgroups printer mappings and Invisible LAN
        printer mappings.




3.3.  CONTROL PANEL


     The Windows For Workgroups Control Panel can establish printer
mappings and start the Invisible LAN Network Manager.

     Control Panel can also install network drivers.  The use of Control
Panel to install network drivers was described in section 2.3 above.




3.3.1.  USING CONTROL PANEL TO ESTABLISH PRINTER MAPPINGS


     To establish printer mappings:

     1. Double-click on the Printers icon.

        Control Panel displays the Printers dialog box.

     2. Choose Connect.

        Control Panel displays the Connect dialog box.

     3. Choose Network.

        Control Panel displays the Connect Network Printer dialog box.
        You can use this dialog box to establish printer mappings for
        Workgroups file servers.

     4. Choose NetWare or Invisible.

        Control Panel displays the Invisible LAN Printer Mappings dialog
        box.  You can use this dialog box to establish printer mappings
        for Invisible LAN file servers.


     Note -- You can also control your Invisible LAN printer mappings by
double-clicking on the Printer Mappings icon in Program Manager.




3.3.2.  USING CONTROL PANEL TO START THE NETWORK MANAGER


     To start the Invisible LAN Network Manager:

     1. Double-click on the Network icon.

        Control Panel displays the Network dialog box.

     2. Choose "Invisible" on the button bar.

        The Invisible LAN Network Manager is displayed.


     Note -- You can also start the Invisible LAN Network Manager by
double-clicking on the Invisible LAN Manager icon in Program Manager.




-----------------------------------------------------------------------




4.  DRIVERS AND PROTOCOL STACKS


     This section is intended for advanced users who want a better
understanding of how Windows For Workgroups is configured.

     Network communication is achieved using a collection of software
modules, which are usually called "drivers." Each driver handles a
specific function;  for example, one driver is dedicated to controlling
the network hardware.

     The drivers are joined together to create a "protocol stack." You
can envision the drivers as being piled atop one another, with each
driver in the stack being supported by the drivers below it.




4.1.  STANDARD INVISIBLE LAN PROTOCOL STACK


     A standard installation of Invisible LAN for Windows has the
following protocol stack:



                         +-----------+
                         | ISNET.DRV |
                         | Windows   |
                         | Network   |
Protected                | Driver    |
Mode                     +-----------+
---------                      |
Real Mode                      |
                               |
    +-------------+      +------------+         +-----------+
    | Invisible   |      | Invisible  |         | Invisible |
    | File Server |      | Redirector |         |  NetBIOS  |
    +-------------+      +------------+         +-----------+
           |                   |                       |
           |                   |                       |
           +-------------------+-----------------------+
                               |
                               |
                         +-----------+
                         | TransBIOS |
                         | Protocol  |
                         +-----------+
                               |
                               |
                               |
                         +-----------+
                         | TransBIOS |
                         | Hardware  |
                         | Driver    |
                         +-----------+



     The protocol stack includes the following components:

     *  TransBIOS Hardware Driver -- Controls the network hardware.  The
        hardware driver has to be customized for the particular type of
        hardware in use.  When you select the network hardware type in
        the SETUP30 program, you are selecting a hardware driver.

     *  TransBIOS Protocol -- Basic procedures for reliable
        communication on the network.  The protocol includes procedures
        for detecting and recovering from communication errors.

     *  Invisible File Server -- Handles requests from other network
        users for access to your computer's disks and printers.

     *  Invisible Redirector -- Provides your computer with access to
        the disks and printers of Invisible LAN servers.

     *  Invisible NetBIOS -- Allows application programs to communicate
        with each other across the network.

     *  ISNET.DRV Windows Network Driver -- Provides Windows programs,
        such as File Manager or Print Manager, with access to network
        functions.


     In this protocol stack, ISNET.DRV operates in protected mode, and
all the other modules operate in real mode.

     The diagram of the stack indicates the relationship among the six
components:

     *  The hardware driver interacts directly with the hardware, so it
        does not depend on any other components.

     *  The TransBIOS protocol relies on the hardware driver to send and
        receive network packets.  This allows the protocol itself to be
        independent of the particular type of hardware in use.

     *  The server, redirector, and NetBIOS each rely upon the TransBIOS
        protocol for network communication.

     *  ISNET.DRV relies on the redirector to perform various network
        functions.




4.2.  INVISIBLE LAN PROTOCOL STACK WITH NDIS


     The serialized version of Invisible LAN (also called the "adapter
independent" version) can use an NDIS driver in place of the TransBIOS
hardware driver.  This allows Invisible LAN to run on any Ethernet or
Token Ring hardware that has an NDIS driver.

     When you use an NDIS driver, the protocol stack is enlarged to
include several new components, as shown:



                         +-----------+
                         | ISNET.DRV |
                         | Windows   |
                         | Network   |
Protected                | Driver    |
Mode                     +-----------+
---------                      |
Real Mode                      |
                               |
    +-------------+      +------------+         +-----------+
    | Invisible   |      | Invisible  |         | Invisible |
    | File Server |      | Redirector |         |  NetBIOS  |
    +-------------+      +------------+         +-----------+
           |                   |                       |
           |                   |                       |
           +-------------------+-----------------------+
                               |
                               |
                         +-----------+
                         | TransBIOS |
                         | Protocol  |
                         +-----------+
                               |
                               |
                               |
                       +---------------+
                       | TBPROTO.DOS   |
                       | TransBIOS     |
                       | NDIS Protocol |
                       | Driver        |
                       +---------------+
                               |
                               |
                               |
                       +---------------+
                       | PROTMAN.DOS   |
                       | NDIS Protocol |
                       | Manager       |
                       +---------------+
                               |
                               |
                               |
                       +---------------+
                       | NDIS Hardware |
                       | Driver        |
                       +---------------+



     The protocol stack includes the following new components:

     *  NDIS Hardware Driver -- Controls the network hardware.  The
        hardware driver has to be customized for the particular type of
        hardware in use.

     *  PROTMAN.DOS NDIS Protocol Manager -- Provides the connection
        between the hardware driver and the protocol driver.

     *  TBPROTO.DOS TransBIOS NDIS Protocol Driver -- Provides the
        connection between the TransBIOS protocol and the NDIS driver.
        TBPROTO accepts requests from TransBIOS to send and receive
        network packets, and converts them into corresponding NDIS
        commands.


     The three new components all operate in real mode.




4.3.  WINDOWS FOR WORKGROUPS PROTOCOL STACK


     A standard installation of Windows For Workgroups has the following
protocol stack:



                                                +------------+
                                                | WFWNET.DRV |
    +-------------+      +------------+         | Windows    |
    | Microsoft   |      | Microsoft  |         | Network    |
    | File Server |      | Redirector |         | Driver     |
    +-------------+      +------------+         +------------+
           |                   |                       |
           |                   |                       |
           +-------------------+-----------------------+
                               |
                               |
                         +-----------+
                         | Microsoft |
                         | NETBEUI   |
                         | Protocol  |
Protected                +-----------+
Mode                           |
---------                      |
Real Mode                      |
                       +----------------+
                       | WORKGRP.SYS    |
                       | NDIS Transport |
                       | Driver         |
                       +----------------+
                               |
                               |
                               |
                       +---------------+
                       | PROTMAN.DOS   |
                       | NDIS Protocol |
                       | Manager       |
                       +---------------+
                               |
                               |
                               |
                       +---------------+
                       | NDIS Hardware |
                       | Driver        |
                       +---------------+



     The protocol stack includes the following components:

     *  NDIS Hardware Driver -- Controls the network hardware.  The
        hardware driver has to be customized for the particular type of
        hardware in use.

     *  PROTMAN.DOS NDIS Protocol Manager -- Provides the connection
        between the hardware driver and the protocol driver.

     *  WORKGRP.SYS NDIS Transport Driver -- Provides the connection
        between NETBEUI and the NDIS driver.  Since NETBEUI operates in
        protected mode, while the NDIS driver operates in real mode, the
        main function of WORKGRP.SYS is to provide an interface between
        real-mode software and protected-mode software.

     *  Microsoft NETBEUI Protocol -- Basic procedures for reliable
        communication on the network.  The protocol includes procedures
        for detecting and recovering from communication errors.  It
        allows application programs to communicate reliably on the
        network.  NETBEUI is Microsoft's version of NetBIOS.

     *  Microsoft File Server -- Handles requests from other network
        users for access to your computer's disks and printers.

     *  Microsoft Redirector -- Provides your computer with access to
        the disks and printers of Workgroup servers and other SMB
        servers.

     *  WFWNET.DRV Windows Network Driver -- Provides Windows programs,
        such as File Manager or Print Manager, with access to network
        functions.


     The NDIS hardware driver, PROTMAN.DOS, and WORKGRP.SYS operate in
real mode.  All the other components operate in protected mode.

     The diagram of the stack indicates the relationship among the seven
components:

     *  The hardware driver interacts directly with the hardware, so it
        does not depend on any other components.

     *  PROTMAN.DOS uses the hardware driver to provides services that
        allow protocol drivers to send and receive network packets.

     *  WORKGRP.SYS provides a way for protected-mode software to access
        the real-mode protocol manager, PROTMAN.DOS.

     *  The NETBEUI protocol relies on WORKGRP.SYS to send and receive
        network packets.  This allows the protocol itself to be
        independent of the particular type of hardware in use.  Using
        WORKGRP.SYS also allows the protocol to run in protected mode,
        even though the hardware driver runs in real mode.

     *  The server, redirector, and WFWNET network driver each rely upon
        the NETBEUI protocol for network communication.




4.4.  COMBINED PROTOCOL STACK WITH TRANSBIOS HARDWARE DRIVER


     The recommended procedure for combining Invisible LAN with Windows
For Workgroups is to use the TransBIOS hardware driver.

     When the TransBIOS hardware driver is used, the resulting combined
protocol stack is this:



                                                        +------------+
                                                        | WFWNET.DRV |
            +-------------+      +------------+         | Windows    |
            | Microsoft   |      | Microsoft  |         | Network    |
            | File Server |      | Redirector |         | Driver     |
            +-------------+      +------------+         +------------+
                   |                   |                       |
                   |                   |                       |
                   +-------------------+-----------------------+
                                                               |
                                                               |
                    +-----------+                              |
                    | ISNET.DRV |                        +-----------+
                    | Windows   |                        | Microsoft |
                    | Network   |                        | NETBEUI   |
                    | Driver    |                        | Protocol  |
Protected           +-----------+                        +-----------+
Mode                      |                                    |
---------                 |                                    |
Real Mode                 |     +---------------+              |
                          |     | TBPROTO.DOS   |     +----------------+
                          |     | TransBIOS     |     | WORKGRP.SYS    |
                          |     | NDIS Protocol |     | NDIS Transport |
                          |     | Driver        |     | Driver         |
                          |     +---------------+     +----------------+
                          |             |                      |
                          |             |                      |
                          |             +----------------------+
                          |                                    |
                          |                                    |
                          |                            +---------------+
                          |                            | PROTMAN.DOS   |
                          |                            | NDIS Protocol |
                          |                            | Manager       |
                          |                            +---------------+
                          |                                    |
                          |                                    |
                          |                                    |
                          |                              +-----------+
                          |                              | TBMAC.DOS |
+-------------+     +------------+     +-----------+     | TransBIOS |
| Invisible   |     | Invisible  |     | Invisible |     | NDIS MAC  |
| File Server |     | Redirector |     |  NetBIOS  |     | Driver    |
+-------------+     +------------+     +-----------+     +-----------+
      |                   |                  |                 |
      |                   |                  |                 |
      +-------------------+----+-------------+-----------------+
                               |
                               |
                         +-----------+
                         | TransBIOS |
                         | Protocol  |
                         +-----------+
                               |
                               |
                               |
                         +-----------+
                         | TransBIOS |
                         | Hardware  |
                         | Driver    |
                         +-----------+



     The protocol stack includes one new component:

     *  TBMAC.DOS TransBIOS NDIS MAC Driver -- Provides a connection
        between TransBIOS and the NDIS Protocol Manager.  TBMAC relies
        on the TransBIOS protocol to send and receive network packets.
        It provides an interface that allows the NDIS protocol manager
        to send and receive packets.  In effect, TBMAC tricks the NDIS
        protocol manager into thinking that it is talking to a hardware
        driver, when it is actually talking to TransBIOS.


     In this protocol stack, the function of TBPROTO is to act as a
placeholder.  TBPROTO informs Workgroups that there is another protocol
present in the system, even though the TransBIOS protocol does not rely
on any of the NDIS drivers.  Workgroups has to know that TransBIOS is
present in order to work properly.

     Notice that there are two Windows network drivers in the system -
WFWNET.DRV and ISNET.DRV.  This ability to install two network drivers
is called "multinet." WFWNET provides access to Workgroups network
functions, and ISNET provides access to Invisible LAN network functions.




4.5.  COMBINED PROTOCOL STACK WITH NDIS HARDWARE DRIVER


     When an NDIS hardware driver is used, the resulting combined
protocol stack is this:



                                                        +------------+
                                                        | WFWNET.DRV |
            +-------------+      +------------+         | Windows    |
            | Microsoft   |      | Microsoft  |         | Network    |
            | File Server |      | Redirector |         | Driver     |
            +-------------+      +------------+         +------------+
                   |                   |                       |
                   |                   |                       |
                   +-------------------+-----------------------+
                                                               |
                                                               |
                    +-----------+                              |
                    | ISNET.DRV |                        +-----------+
                    | Windows   |                        | Microsoft |
                    | Network   |                        | NETBEUI   |
                    | Driver    |                        | Protocol  |
Protected           +-----------+                        +-----------+
Mode                      |                                    |
---------                 |                                    |
Real Mode                 |                                    |
                          |                                    |
                          |                                    |
+-------------+     +------------+     +-----------+           |
| Invisible   |     | Invisible  |     | Invisible |           |
| File Server |     | Redirector |     |  NetBIOS  |           |
+-------------+     +------------+     +-----------+           |
      |                   |                  |                 |
      |                   |                  |                 |
      +-------------------+------------------+                 |
                          |                                    |
                          |                                    |
                    +-----------+                              |
                    | TransBIOS |                              |
                    | Protocol  |                              |
                    +-----------+                              |
                          |                                    |
                          |                                    |
                          |                                    |
                  +---------------+                            |
                  | TBPROTO.DOS   |                   +----------------+
                  | TransBIOS     |                   | WORKGRP.SYS    |
                  | NDIS Protocol |                   | NDIS Transport |
                  | Driver        |                   | Driver         |
                  +---------------+                   +----------------+
                          |                                    |
                          |                                    |
                          +---------+--------------------------+
                                    |
                                    |
                            +---------------+
                            | PROTMAN.DOS   |
                            | NDIS Protocol |
                            | Manager       |
                            +---------------+
                                    |
                                    |
                                    |
                            +---------------+
                            | NDIS Hardware |
                            | Driver        |
                            +---------------+



     In this protocol stack, PROTMAN allows both TBPROTO and WORKGRP to
send and receive network packets.  PROTMAN provides a special function
that allows two protocols - TransBIOS and NETBEUI - to operate
simultaneously on the same network adapter.




-----------------------------------------------------------------------




5.  PARAMETERS AND MANUAL INSTALLATION


     This section describes the parameters that are placed in the
WIN.INI, SYSTEM.INI, PROTOCOL.INI, and CONFIG.SYS files when you install
the Invisible LAN support in Windows For Workgroups.

     Using this information, you can manually install all the necessary
drivers to run Invisible LAN with Windows For Workgroups.  However, only
advanced users should attempt manual installation, since the process is
fairly complex.




5.1.  WIN.INI PARAMETERS


     WIN.INI is a text file that configures your Windows desktop and
applications.

     Installing the Invisible LAN support in Windows For Workgroups
automatically adds the following lines to your WIN.INI file:

        [windows]
        Spooler = yes

        [spooler]
        netupdate = yes
        netspool = yes




5.2.  SYSTEM.INI PARAMETERS


     SYSTEM.INI is a text file that installs device drivers and
configures Windows for your hardware.

     Installing the Invisible LAN support in Windows For Workgroups
automatically adds the following lines to your SYSTEM.INI file:

        [boot]
        secondnet.drv = isnet.drv

        [386enh]
        secondnet = *dosnet, visnet.386
        FileSysChange = off
        OverlappedIO = off
        InDOSPolling = FALSE
        INT28Critical = TRUE
        ReflectDosInt2A = FALSE
        UniqueDOSPSP = FALSE
        LPT1AutoAssign = 0
        LPT2AutoAssign = 0
        LPT3AutoAssign = 0
        PerVMFILES = 0
        TimerCriticalSection = 1000
        V86ModeLANAs = 0

        [network]
        multinet = invisible
        exclude = 0


     If you are running the Invisible LAN file server, then you must
remove the following line from your SYSTEM.INI file:

        [386enh]
        device = vshare.386


     In addition, if you are running the file server, and you are using
a serial printer attached to port COM1 as a spooled network printer, you
must also add the following line:

        [386enh]
        COM1AutoAssign = 0


     If you are using a serial printer attached to port COM2 as a
spooled network printer, you must add the following line:

        [386enh]
        COM2AutoAssign = 0




5.3.  PROTOCOL.INI PARAMETERS


     PROTOCOL.INI is a text file that configures the network drivers.

     Installing the Invisible LAN support in Windows For Workgroups
automatically creates the PROTOCOL.INI file shown below.  This is the
entire file:

        [network.setup]
        version = 0x3100
        netcard = tbmac, 1, TBMAC
        transport = ms$netbeui, MS$NETBEUI
        transport = tbproto, TBPROTO
        lana0 = tbmac, 1, tbproto
        lana1 = tbmac, 1, ms$netbeui

        [protman]
        DriverName = PROTMAN$
        PRIORITY = NS$NETBEUI

        [MS$NETBEUI]
        DriverName = netbeui$
        SESSIONS = 10
        NCBS = 32
        BINDINGS = TBMAC
        LANABASE = 1

        [TBMAC]
        DriverName = TBMAC$

        [TBPROTO]
        DriverName = TBPROTO$
        BINDINGS = TBMAC


     The file shown above is the file that results when you use the
TransBIOS hardware driver.  PROTMAN is the NDIS protocol manager,
MS$NETBEUI is the Microsoft NetBIOS, TBMAC is the TransBIOS Ethernet
Driver, and TBPROTO is the TransBIOS protocol driver.

     If you use an NDIS hardware driver, then TBMAC will not appear in
the PROTOCOL.INI file.  The NDIS hardware driver will appear in place of
TBMAC.




5.4.  CONFIG.SYS PARAMETERS


     CONFIG.SYS is the text file that DOS uses to install device drivers
and configure itself to match your hardware.

     Installing the Invisible LAN support in Windows For Workgroups
automatically inserts the following lines into CONFIG.SYS:

        device = C:\WINDOWS\protman.dos  /i:C:\WINDOWS
        device = C:\WINDOWS\tbmac.dos
        device = C:\WINDOWS\tbproto.dos
        device = C:\WINDOWS\workgrp.sys


     The lines are for the case where you use the TransBIOS hardware
driver.  If you use an NDIS hardware driver, then TBMAC will not appear
in the CONFIG.SYS file.  The NDIS hardware driver will appear in place
of TBMAC.




5.5.  REQUIRED FILES


     When installing Invisible LAN support in Windows For Workgroups,
the following files are copied into the Windows directory (usually
C:\WINDOWS):

        NET30APP.EXE
        TBMAC.DOS
        TBPROTO.DOS


     The following files are copied into the Windows system directory
(usually C:\WINDOWS\SYSTEM):

        CISNET.CPX
        ISNET.DRV
        ISNET.HLP
        VISNET.386


     In addition, the OEMSETUP.INF file is copied into the Windows
system directory and simultaneously renamed to something like OEM0.INF,
OEM1.INF, etc.
