home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!jvnc.net!netnews.upenn.edu!msuinfo!msuinfo!news
- From: carter@cemvax.cem.msu.edu (Tom Carter)
- Newsgroups: comp.os.ms-windows.setup
- Subject: re: setting up QVTNET with Wind. for work
- Message-ID: <1ifgvsINNiub@msuinfo.cl.msu.edu>
- Date: 6 Jan 93 20:55:24 GMT
- References: <aksurf-050193174533@131.215.9.51>
- Organization: Michigan State University, Chemistry Dept., E. Lansing, MI
- Lines: 101
- NNTP-Posting-Host: photon.cem.msu.edu
-
- In article <aksurf-050193174533@131.215.9.51> aksurf@caltech.edu (Axel) writes:
- >In article <wstuartj.725817837@lucky.ecn.purdue.edu>,
- >wstuartj@lucky.ecn.purdue.edu (W Stuart Jones) wrote:
- >>
- >> Has anyone had success configuring Windows for Work Groups for use with both
- >> telnet capabilities and Novell 3.11 connectivity? I'm hoping to use either
- >> NCSA telnet and QVNET with in Windows for Work Groups. Any advice or sample
- >> configuration files would be greatly appreciated.
- >>
- >STUFF DELETED....
- >
- >
- >Hey, I too am looking for some information on how to do that. I am trying
- >to run windows for workgroups and qvtnet. I have discovered that when I
- >load the packet driver for NCSA telnet (In my case, it's called 8003pkdr
- >for an SMC Elite 16 series ethernet card) and the interface TSR called
- >pktint, QVTNET takes control of the network, i.e. it doesn't allow ms
- >windows to access the network. If anyone out there knows of a TCP/IP NDIS
- >configuaration compatible protocol, please let me know. Please E-mail me at
- >aksurf@caltech.edu, and post on the network, since I am shure there will be
- >others who need this info.
- >
- > Thanks,
- >
- >
- > Axel
-
-
- I'm running Windows for Workgroups, DEC PathWorks, and WinQVT/Net, all at
- the same time. Here's a fragment of config.sys:
-
- devicehigh=C:\WIN31\protman.dos /i:C:\WIN31 <== WFWG NDIS protocol manager
- DEVICEHIGH=\DECNET\DISPKT\DIS_PKT9.DOS <== NDIS to packet shim
- DEVICEHIGH=C:\WIN31\depca.dos <== NDIS driver for
- Pathworks & WFWG
- devicehigh=C:\WIN31\workgrp.sys <== WFWG
-
-
- and my PROTOCOL.INI from the windows directory:
-
- [network.setup] <== WFWG
- version=0x3100
- netcard=ms$ewtrb,1,MS$EWTRB
- transport=ms$netbeui,MS$NETBEUI
- lana1=ms$ewtrb,1,ms$netbeui
-
- [protman] <== Protocol manager
- DriverName=PROTMAN$
- PRIORITY=MS$NETBEUI
-
- [MS$EWTRB] <== NDIS driver settings
- DriverName=DEPCA$
- RamAddress=0xD000
- Interrupt=5
- MaxMulticast=8
- MaxTransmits=16
- AdapterName=DE200
-
- [MS$NETBEUI] <== Transport (NETBEUI)
- DriverName=netbeui$
- SESSIONS=10
- NCBS=32
- BINDINGS=MS$EWTRB
- LANABASE=1 <== changed this from LANABASE=0
- for Pathworks connectivity
-
- [PKTDRV] <== packet driver specs
- drivername = PKTDRV$
- bindings = MS$EWTRB
- intvec = 0x7b <== use this int. vector in QVT
- (or choose one of your own)
-
- [DATALINK] <== lifted out of the PathWorks
- DRIVERNAME = DLL$MAC protocol.ini
- LG_BUFFERS = 16
- SM_BUFFERS = 6
- OUTSTANDING = 32
- HEURISTICS = 0
- BINDINGS = MS$EWTRB
- NI_IRQ = 5
-
- I needed to alter the Pathworks STARTNET.BAT file to:
- - Replace the NETBIND line with c:\windows\net start
- - disable the redir.exe line
-
- and rem out the NET START line WFWG put in autoexec.bat.
-
- Then, after booting, I start the network, start PKTINT and then windows.
-
- I don't really know what I'm doing, but I got it to work by talking to
- Microsoft. I already had Pathworks and QVT running together when I added
- WFWG. I don't know how Netware fit's in, but I think if you add the
- DIS_PKT9.DOS line to your config.sys and the [PKTDRV] stuff to protocol.ini
- it should work.
-
- HTH
- ===========================================================================
- | Tom Carter | carter@cemvax.cem.msu.edu |
- | Michigan State University | carter@msucem.bitnet |
- | Chemistry Department | |
- ===========================================================================
-