home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!spool.mu.edu!umn.edu!news.cs.indiana.edu!mikes@moose.cs.indiana.edu
- From: mikes@moose.cs.indiana.edu (Michael Squires)
- Newsgroups: comp.protocols.tcp-ip.ibmpc
- Subject: Re: PCTCP 2.05 and Windows 3
- Summary: It works
- Keywords: PCTCP MS Windows
- Message-ID: <1992Sep8.233649.29709@news.cs.indiana.edu>
- Date: 9 Sep 92 04:36:42 GMT
- References: <1992Sep7.110452.16477@impmh.uucp>
- Organization: Indiana University, Bloomington
- Lines: 27
-
- In article <1992Sep7.110452.16477@impmh.uucp> cm@impmh.uucp (Colin Manning) writes:
- >
- >What is the state of play as far as using PC/TCP 2.05 and windows together ?
-
- It works; this message is being entered on a 486/33 running MS Windows 3.1,
- HCL eXceedW 3.1.1, and PC/TCP 2.05 pachlevel 5. There are some replacement
- files from ftp that are apparently required for Windows 3.1 (HCL includes
- them) and some hand editing of WIN.INI and SYSTEM.INI are required. I have
- not been able to get our SMC cards to work properly with ODI/ODIPKT but
- the 10.7 WD8003E packet driver works fine. (X sessions time out on lost
- packets, apparently; it's not yet clear if this is my mistake, a problem
- with ODIPKT (current hypothesis), or whatever)
-
- PCTCP received a poor review in SunWorld recently but I was unable to
- duplicate the results here, they looked almost identical to the top-rated
- Wollongong product.
-
- There is a set of files from ftp for setting up 2.05 with Windows 3.1 which
- would probably be necessary.
-
- The main problem is that I can no longer load ETHDRV in high memory as I
- could with Windows 3.0, which greatly increases the amount of low memory
- used by PCTCP. With QEMM, however, I can get 520/540K on our machines.
- --
-
- Mike Squires (mikes@iuvax.cs.indiana.edu) 812 855 3974 (w) 812 333 6564 (h)
- mikes@iuvax.cs.indiana.edu 546 N Park Ridge Rd., Bloomington, IN 47408
-