home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!uvaarpa!darwin.sura.net!paladin.american.edu!auvm!SVM.VETMED.WISC.EDU!CRAMERB
- Return-Receipt-To: cramerb@svm.vetmed.wisc.edu
- Message-ID: <9301271032.A00729@svm.vetmed.wisc.edu>
- Newsgroups: bit.listserv.banyan-l
- Date: Wed, 27 Jan 1993 10:32:13 CST
- Sender: Banyan Networks Discussion List <BANYAN-L@AKRONVM.BITNET>
- From: Bob Cramer <cramerb@SVM.VETMED.WISC.EDU>
- Subject: Re: Banyan w/ Novell
- Lines: 107
-
- We are doing pretty much the same thing here. We have a 386sx that is logged
- into both Novell & Vines at all times. In there Windows they have an icon for
- their Novell application and another for a Vines one. They can both be running
- at the same time, in fact the Novell application is printing to the Vines print
- service. We are doing this by using packet drivers and a memory manager (Qemm).
- I have recently written up something on how to do this, and I will include it
- below. The one item that I left out if you intend to use Windows, is that you
- must setup windows to think there is a Novell network, then manually go into the
- system.ini and change the "network.drv=vines.drv" and in the 386Enh section add
- the "vvinesd.386" to the "network=" line. This way all the requirement are
- filled for both Novell & Vines under Windows. Without this last step, everytime
- you run a DOS program under Windows it loses the environment (no path, no
- comspec, not prompt, .....). Listed below is how I have done it. Any questions
- can be sent to me directly at:
-
- cramerb@svm.vetmed.wisc.edu
- Bob Cramer
-
- Are you tired of re-booting every time you need to
- switch from a VINES application to one that's on NetWare?
- Now you can be logged into both VINES and NetWare at the
- same time. You can have your NetWare applications printing
- to a VINES print service. The best of both worlds. If you
- expect to have enough memory left over to run an application,
- you will need a 386sx or better with a memory manager. We
- will be using packet drivers to gain access to both operating
- systems, so the first step is to get each operating system
- ready.
- For VINES, you need to be running 5.0, and you will
- need to apply the Site-Specific Patch 5.00(5)-AW-1. Once
- this is applied, you can run Z:\PCCOPY and copy the
- Cabletron drivers. Now you must run the PCCONFIG for the
- new drivers. Set all your options as you normally would.
- Under the option Network Card Settings, set the correct
- interrupt for your network card, and enter N for the multi-
- protocol option.
- For NetWare, you will need to get an IPX.COM that is
- able to handle packet drivers (frequently renamed
- IPXPKT.COM for clarity). If your NetWare folks don't have
- one handy, it's no problem. You can get IPXPKT.COM by
- anonymous FTP to novell.macc.wisc.edu in the DRIVERS
- directory. If your NetWare operator wants, they can get the
- PDSHELL.OBJ and PDSHELL.LAN by anonymous FTP to
- oak.oakland.edu and downloading the file
- pub/msdos/pktdrvr/novell.zip. Then they can create their own
- IPX.COM using WSGEN that comes with NetWare. These
- files are public domain and are available in most places that
- you can get packet drivers.
- The last item that you will need is the packet driver for
- your specific Network Interface Card. This comes with your
- NIC and is also available at the above mentioned FTP sites
- (and many others). You now have all the ingredients, it's just
- a matter of combining them. I will give an example using a
- Western Digital card with QEMM386 as my memory
- manager.
-
- CONFIG.SYS
- DEVICE=C:\DOS\SETVER.EXE
- FILES=80
- BUFFERS=10
- SHELL=C:\DOS\COMMAND.COM C:\DOS\ /e:1024 /p
- DEVICE=C:\QEMM\QEMM386.SYS RAM FRAME=C000
- X=D000-D400 ST:M
- DOS=HIGH
- device=c:\dos\smartdrv.sys 1024 512
- Device=c:\qemm\loadhi.sys c:\dos\ansi.sys
-
- AUTOEXEC.BAT
- PROMPT $P$G
- PATH C:\DOS;c:\qemm;c:\windows;c:\u
- set temp=c:\windows\temp
- SET MOUSE=C:\MSMOUSE
- loadhi C:\MSMOUSE\MOUSE
- loadhi /r:1 doskey
- cd\vines
- loadhi wd8003e 0x60 5 0x280 0xd000
- ban /nc
- loadhi csiban
- loadhi redir4
- z:login
- c:
- cd\novell
- loadhi ipxpkt
- net5
- [:login
-
- There are a few items that need to be pointed out. When
- loading a memory manager, you must be sure to exclude the
- area in high memory the NIC is using. Not all NICs use high
- memory, but for this example D000-D400 was excluded.
- When loading the network drivers, Banyan's redir4 must be
- loaded before NetWare's net5. In my example, I have
- completely loaded and logged into VINES before I even think
- about NetWare. Once you have loaded the NetWare drivers,
- you will have to go to drive [: to login. This is due to the
- fact that Novell notices a Z: drive, so they pick the next
- available ascii character, which is [:. Once you have logged
- into NetWare, you will probably need to re-map any drives
- that both Operating Systems are trying to access. You can do
- this by adding the [:\public\map commands to the end of your
- AUTOEXEC.BAT.
- You may have to play around with deciding what to
- loadhigh to get the best results with your setup. For the
- configuration above, I am logged into both NetWare and
- Banyan and still have about 550K of free memory along with
- 2 Meg of expanded memory for those applications that can
- use it. Enjoy!
-