From: larry@dprmpt.UUCP (Larry)
Newsgroups: comp.os.ms-windows.misc,comp.protocols.tcp-ip.ibmpc
Subject: CUTE/TCP under Windows 4 Workgroups
Keywords: tcpip ndis windows workgroups packet
Date: 28 Jan 93 18:29:53 GMT
Followup-To: poster
Organization: Data-Prompt

I have been trying to get Windows for Workgroups (W4W) and TCP/IP to
co-exist on my PC for a few weeks now, with no luck.  I've followed
the threads that discussed QVTNET, and FTP Software's TCP/IP, and have
tried just about any recommendation I've seen.  My configuration is:
	Clone 386/25
	Windows 3.1 with Windows for Workgroups User Kit add-on
	Intel EtherExpress (came bundled with W4W)
	Clarkson Univ. Terminal Emulator [CUTD:2.2D/TC-D]
	a variety of packet driver "shims"
I've gotten to the point where I CAN telnet to the UNIX host and run
for a while, but suddenly, for no apparent reason, Windows completely
"evaporates" and I'm thrown back to a "C:>" prompt.  I talked to MS
Tech support and the techie suggested that I try adding a "/n" to the
"device=d:\lan\workgroup.sys" statement in config.sys (which prevents
the starting of the NETBEUI protocol stack), and this seems to prolong
the amount of time before Windows evaporates; however, I then cannot
use any network functionality of W4W ;-(  BTW, this seems to happen in
other apps under windows (e.g. control panel/desktop).

I also tried changing the IRQ to 11 and the I/O base to 320 (per MS
Tech support), and I tried excluding upper memory.

I tried "dis_pkt9.dos" Ver 1.09 from Joe Doupnik at Utah State, 
"dis_pkt.dos" Ver 1.11 from Dan Lanciani at Harvard, and "dis_pkt.gup" 
Ver 1.31 from FTP Software.  I get similar results using all 3, although 
the latter two seem to run longer before aborting.  Note that this 
setup works FINE unless Windows is active.

The pertinent sections of my Config, autoexec and protocol.ini files:
config.sys:
	DEVICE=C:\HIMEM.SYS
	DEVICE=C:\EMM386.EXE x=EE00-F000 noems
	DOS=HIGH,UMB
	devicehigh=C:\DOS\SETVER.EXE
	devicehigh=C:\DOS\ansi.sys
	FILES=30
	BUFFERS=30
	STACKS=9,256
	fcbs=1
	SHELL=C:\DOS\COMMAND.COM c:\dos /e:768 /p
	device=D:\lan\protman.dos /i:D:\lan
	device=D:\lan\workgrp.sys 
	device=D:\lan\exp16.dos
	device=D:\lan\dis_pkt.gup
autoexec.bat:
	D:\SMARTDRV.EXE 1024 1024
	SET CONFIGTEL=c:\cutcp\config.lgj
	c:\windows\net start
Protocol.ini:
	[network.setup]
	version=0x3100
	netcard=ms$ee16,1,MS$EE16
	transport=ms$netbeui,MS$NETBEUI
	lana0=ms$ee16,1,ms$netbeui
	
	[protman]
	DriverName=PROTMAN$
	PRIORITY=MS$NETBEUI
	
	[pktdrv]
	DriverName=pktdrv$
	BINDINGS=MS$EE16
	intvec=0x60
	chainvec=0x66
	novell=n
	
	[MS$EE16]
	DriverName=EXP16$
	IOADDRESS=0x300
	IRQ=5
	IOCHRDY=Late
	TRANSCEIVER=Thin Net (BNC/COAX)
	
	[MS$NETBEUI]
	DriverName=netbeui$
	SESSIONS=10
	NCBS=32
	BINDINGS=MS$EE16
	LANABASE=0

Oh, BTW, I also started Dr.Watson but all I get is "No faults found".
Any help would be appreciated.  I've run out of ideas, and there must
be something I've missed or overlooked.  Thanks in advance.
-- 
* - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - *
* Larry Johnson                         VOICE:  (301) 622-0900          *
* INTERNET: larry@dataprompt.com        UUCP:   ...!uunet!dprmpt!larry  *
* - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - *
Newsgroups: comp.os.ms-windows.misc,comp.os.msdos.misc