Hi Scott,
 SL> I have a 486DX4/100 w/ 16meg. I have installed IBM Peer and TCP/IP on
 SL> Connect.
 SL> Does anyone have any speed tips? Once REQUESTER is started, the system 
s
 SL> like a dog compared to before. Perhaps cache settings (fully HPFS 
ystem,
 SL> DISKCACHE is REMed out), or something.
One of the machines I run is a 486DX2-66 with 16MB, IBM Peer and TCP/IP on 
Warp Connect. This machine also runs a 3 line Fidonet BBS, Binkley/Maximus on 
3 lines, 8 Port Digiboard, 6 disc SCSI CD changer, 3GB SCSI HD, 200MB SCSI 
HD, (4 HPFS partitions) and it all runs fine. It used to be 4 lines but calls 
have dropped off over the past year so the 4th line was removed about 6 
months ago.
There is no obvious cause for your problem that I can see, however if 
everything else is OK then it probably means that you are memory constrained. 
One quick thing you can do is to check that the HD CACHE size is not too 
large if your system is memory constrained. About 512KB (or even down to 
256KB) is worth trying on an 16MB machine if it is currently set larger than 
this. Enabling LAN services on Warp does grab a fairly large chunk of memory, 
however the real performance areas depend heavily on the APPS you run. The 
BBS machine performs well because the same executable is loaded for each line 
so in reality only 1 copy of the S/W is actually loaded. A normal machine 
would have a different application mix so would probably be impacted more.
Generally, I find that Warp Connect with LAN activities enabled performs well 
with 24MB on any CPU, it seems to stop some of the swapping. Extra memory 
over that is just icing on the cake (32MB is nice, 48MB is really 
good.....;-)).
Sorry I can't be more specific about your problem.............pk.
--- Maximus/2 3.01
---------------