Newsgroups: bit.listserv.banyan-l
Date:         Thu, 1 Oct 1992 09:36:40 BST
From:         tp@JET.UK
Subject:      Problem with MARK and RELEASE (or POPDROP) and PROTMAN.DOS

    Hi,
        The problem :

     Lan                         : Banyan Vines V4.11 (5)
     Ethernet card               : SMC Elite 16
     Station                     : IBM PC clone 486 33MHz, with AMI BIOS
     Network file and Drivers    : PROTMAN.DOS, MACWD.DOS,
                                   IPCUST.SYS, IFCUST.SYS
                                   BAN.EXE, NDISBAN.EXE, REDIR5.EXE

     After having loaded the lan manager files PROTMAN.DOS, MACWD.DOS and
     the so called drivers IPCUST.SYS and IFCUST.SYS in my CONFIG.SYS,
     I invoke a batch file when I want to LOGON to the NETWORK. This way
     I have a LARGE chunk of my conventional memory available when I need
     it, equally I dont need to be permenantly LOGGED on to the NETWORK.
     I also have the added security, that I am not left LOGGED ON while
     away from my station or with a LOGIN prompt awaiting some unwarranted
     user to try and hack into the NETWORK.

     For these reasons, in my batch file I invoke a dos utility such as
     POPDROP (or MARK and RELEASE) before invoking the NETWORK programs,
     i.e

 rem [1]   When I wish to LOGON to the NETWORK

 ----  appropriate MARK  (or PD ) command
       BAN.EXE /nc
       NDISBAN.EXE
       REDIR5.EXE

 rem   I see the following messages corresponding to the above three progs :

      No Network Communications interface.
      Ver 410.0[2] Multi Protocol NDIS Ethernet interface 2/2/91
      MS DOS Lan Manager Netbind V1.1

 rem   After which my drive Z: is available, and I can invoke :

      Z:\login.exe


 rem [2] When I wish to unload the NETWORK software, have a LARGER
 rem     conventional memory made available, having first LOGGED of my
 rem     USERID on the NET

 ----  appropriate RELEASE (or PD S)

    This all works well, except when I re-invoke the BATCH file to LOGON to
    the NETWORK, as per [1] above, but now I see the following messages

    No Network Communications interface.
    Ver 410.0[2] Multi Protocol NDIS Ethernet interface 2/2/91
    MS DOS Lan Manager Netbind V1.1

    PRO0024W NETBIND already executed.

 rem my Z: drive letter though available, when I list this drive i.e DIR
 rem I get the a status message to the effect

    File Volume NOT available.


    Clearly I cant access the NETWORK, without re-boot. I have listed the
    memory with DOS command :
                             mem /c (and mem /p)
    But I do not see anything unusal.


   So the questions are :

   1) What is the cause of this and Why ?

   2) Can I get away without Loading Lan managers PROTMAN.DOS and MACWD.DOS ?

      i.e What exactly is the purpose of these ?

   3) What exactly dictates the type of ethernet DRIVER to LOAD ?

      i.e With the configuration given at the beginning of this article,
          Do I have any other option instead of using NDISBAN ?

   4) I want to use KERMIT 3.11 (3.12) with its built in TCP/IP calls
      What are the correct drivers and LAN managers (if required) to install ?


------------------------------------------------------------------------------
Mr Tarang Kumar Patel            |      snailmail : Jet Joint Undertaking,
Hunterskil ltd,                  |                  Abingdon,
Project House,                   |                  Oxfordshire OX14 3EA,
110/113 Tottenham Court Road,    |                  England.
London W1P 9HG                   |
                                 |      Email    : tp@jet.uk
 { o'| `0 }                      |
    -~~-                         |      Tel      : (+44) (0235) 464533
     uu                          |      Fax      : (+44) (0235) 464766
------------------------------------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU