[comp.protocols.tcp-ip.ibmpc] NFS & Windows & Clarkson

sw@goanna.cs.rmit.oz.au (Simon Wail) (12/19/90)

G'day,

	I'm attempting to establish a small network of 386 PCs running MS-DOS 
	& Windows 3.00 connected to an HP-9000 running HP-UX and PC-NFS. I
	also have the FTP PC-TCP/Idrive product. I'm a neophyte at NFS, so a
	few questions have arisen.

	1) I can get the FTP stuff up and running, but the memory usage is 
	abhorrent!!  Is there anyway to cut down on the usage by the WD8003
	kernel or Idrive itself?

	2) I also have the PD Clarkson driver and the QVTNET Windows VT200
	emulator. I can also get this to work, but when it does, I lose the
	Idrives. Can these products all work together in peace and harmony?

				Thanks,

				Ron Wail (using his brother's account)

Email: sw@goanna.oz.au
UUCP:  uunet!munnari!goanna!sw

fks@FTP.COM (Frances Selkirk) (12/19/90)

>1) I can get the FTP stuff up and running, but the memory usage is 
>abhorrent!!  Is there anyway to cut down on the usage by the WD8003
>kernel or Idrive itself?

We can't make the kernel much smaller and still offer the features that
we do (multiple TCP connections, etc.), but both the kernel and InterDrive
can be loaded into extended memory with a number of memory managers. 
	
Btw, did you receive the letter I sent you? I got one bounce message,
but the second try didn't return to me, so I assumed it went through.
If not, I will send it snail.
	

dsc3rjs@NMDSC20.NMDSC.NNMC.NAVY.MIL (Bob Stratton) (12/20/90)

   >From pcip-request@louie.udel.edu Wed Dec 19 15:17:31 1990
   Date: Wed, 19 Dec 90 10:17:06 -0500
   From: Frances Selkirk <fks@ftp.com>

   We can't make the kernel much smaller and still offer the features that
   we do (multiple TCP connections, etc.), but both the kernel and InterDrive
   can be loaded into extended memory with a number of memory managers. 

When you say "extended memory"', do you mean "high DOS" memory, or
extended memory above 1 Meg?? I have used 386MAX to shove some of the
kernel high on occasion, but I thought that it only worked in memory
below 1MB (C800h to FFFFh).

I have your third party s/w list, but I didn't see any mention of 
relocating the kernel to extended memory. I currently use RYBS
Hi-Cards in some machines, but it would be great to just keep the
stuff in my users' (usually unused) extended memory.

Bob Stratton 		| dsc3rjs@nmdsc20.nmdsc.nnmc.navy.mil [DDN/Internet]
NAVMEDATASERVCEN	| dsc3rjs@vmnmdsc		      [BITNET]
(Innova Comms. / AT&T)	| 295-3503 [AV]    +1 301 295 3322    [PSTNet]
Disclaimer: The above opinions are mine alone - Who else would want them?

romkey@ASYLUM.SF.CA.US (John Romkey) (12/20/90)

   Date: Wed, 19 Dec 90 15:26:13 EST
   From: Bob Stratton <dsc3rjs@nmdsc20.nmdsc.nnmc.navy.mil>

   When you say "extended memory"', do you mean "high DOS" memory, or
   extended memory above 1 Meg??

I believe Frances meant 386MAX-type memory managers.
		- john romkey			Epilogue Technology
USENET/UUCP/Internet:  romkey@asylum.sf.ca.us	FAX: 415 594-1141

jbvb@FTP.COM ("James B. Van Bokkelen") (12/21/90)

   2) I also have the PD Clarkson driver and the QVTNET Windows VT200
   emulator. I can also get this to work, but when it does, I lose the
   Idrives. Can these products all work together in peace and harmony?

Both IP modules (PC/TCP and Clarkson) are trying to get the same packets.
If the Idrives go away, that means Clarkson won.  No way to fix it other
than to reduce the number of TCP/IP modules to one, by either making
Clarkson offer our INT 61h kernel API to Interdrive, or by making Clarkson
call INT 61h to do its TCP reads and writes.  Clarkson did the latter for
Sun's PC-NFS, but their administrative policies have so far prevented
anyone's doing the same thing for PC/TCP.

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901

david@monymsys.uucp (David Kozinn) (12/28/90)

In article <9012192026.AA15017@nmdsc20.nmdsc.nnmc.navy.mil> dsc3rjs@NMDSC20.NMDSC.NNMC.NAVY.MIL (Bob Stratton) writes:
>
>When you say "extended memory"', do you mean "high DOS" memory, or
>extended memory above 1 Meg?? I have used 386MAX to shove some of the
>kernel high on occasion, but I thought that it only worked in memory
>below 1MB (C800h to FFFFh).

We've been using QEMM 5.1 here and are quite pleased with the results. I've
got the kernel loaded into the memory space below 1MB along with a bunch of
other stuff (my BUFFERS, IPCUST, drivers for a Novell network and token ring
card, cache drivers, vdis drivers, etc.) and I have 604K free in DOS. (I don't
normally have idrive loaded). If you're interested, I can send you some
samples of config.sys and autoexec.bat files that we use here.

If there's enough interest, I'll sumarize to the net.
-- 
David Kozinn                     | UUCP:   uupsi!vmp!monymsys!david
MONY Financial Services MD 75-14 | Domain: david@monymsys.vmp.com
Glenpointe Centre West           | GEnie:  D.KOZINN 
Teaneck, NJ 07666-6888           | Phone:  +1-201-907-6990