home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.tcp-ip.ibmpc:4741 comp.os.ms-windows.apps:1978
- Path: sparky!uunet!caen!rphroy!kocrsv01!swlodin
- From: swlodin@kocrsv01.delcoelect.com (Steve Lodin)
- Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.os.ms-windows.apps
- Subject: Novell and WinQVT/Net (Argggghhhh)
- Message-ID: <1992Aug14.194534.14216@kocrsv01.delcoelect.com>
- Date: 14 Aug 92 19:45:34 GMT
- Sender: news@kocrsv01.delcoelect.com (Usenet News Account)
- Organization: Delco Electronics Corp.
- Lines: 37
- Originator: swlodin@kocrsw15
-
-
- **** Posting for a friend who can't get his PC to work ****
-
- I am trying to set up an AST 486/33 to run on an existing Novell network
- (v3.11) WITH the ability to run WinQVT/Net. I, like others in the past
- and present, am having difficulty making IPX and TCP/IP coexist. I
- remember a posting several months ago on this subject which suggested
- the following additions to autoexec.bat:
-
- lsl.com
- 3c507.com -n -w 0x60
- odipkt.com
- winpkt 0x60 0x63
- pktint
- ipxodi.com
- netx.com
-
- When I run this, it seems everything loads into RAM except winpkt, which
- gives a message similar to "packet driver is at segment xxxx,
- there is no packet driver at 0x63". When I run windows 3.1 after this
- sequence, my machine hangs.
-
- If anyone out there has any experience with Novell NetWare and WinQVT/NET
- simultaneous usage, please respond with a sample .bat file and/or
- explanation of what's going on. I can get each protocol to work separately,
- but not together.
-
- Thanks in advance for any assistance in lowering my blood pressure.
-
- Mike Thoeny
- Delco Electronics Corp
- thoeny@kocrsv01.delcoelect.com
- --
- Steve Lodin Internet: swlodin@kocrsv01.delcoelect.com UUCP: deaes!swlodin
-
-
- Thanks Tom for the nifty signature thingy.
-