ADSM-L

Windows client

1994-06-20 14:29:16
Subject: Windows client
From: "Amy Lim Weaver (408) 256-0284 t/l 276-0284" <alim AT VNET.IBM DOT COM>
Date: Mon, 20 Jun 1994 11:29:16 PDT
>> I had a user complain of failures in trying to restore LARGE files
>> but no problems with SMALL files.  A little simple research of IBMLINK
>> turned up the answer right away.  In Tech Q & A there's a recommendation
>> to change MinimumCopySpace from the default of 12 to 32.  IT WORKED!

>> So then I send a note out to all my Windows ADSM clients recommending they
>> make the change to (at least) 32.   But I get a reply back that one user
>> is using Windows for Workgroups(3.11) and there is no MinimumCopySpace but
>> there's NetHeapSize and he thinks that's the equivalent.

>> Is that true?  Any suggestions?  thanks .. joe.f.


MinimumCopySpace tells the device driver how many kilobytes of copy space
memory to request.  FTP PC/TCP recommend this value to be 32.  This is
a field in the [vpctcp] section in the system.ini file.

NetHeapSize specifies the size (in kilobytes) of the data transfer buffer in
conventional memory that Windows for Workgroups allocates for transfering data
over the network.  This setting is needed only if you are using real-mode
protocols.  It is not required if you are using the NETBEUI.386 protocol.
All values are rounded up to the nearest 4K.  The default is 16K.
Large buffer size improves performance, but uses up more memory.
NetHeapSize is specified in the sysini.wri file.

Hope this helps!


Amy L. Weaver
ADSM Client Development
<Prev in Thread] Current Thread [Next in Thread>
  • Windows client, Amy Lim Weaver (408) 256-0284 t/l 276-0284 <=