If I recall, Warp Server 4 is based on the older Warp 3 code. So a few things you may want to look at.
First, (assuming it is based on the Warp 3 code - run syslevel or type ver /r and it should tell you), you will probably want to update to the latest fixpak for Warp Server - currently Fixpak 43:
There's also the Device Driver Fixpak 2 at:
Also, install the latest fixpaks for TCP/IP, MPTS, the lan server stuff, etc. Also, if your hard disk is an IDE, then you'll probably see better performance with the DANIS506.ADD driver then you'll get from IBM's driver.
As for MPTS, I can't recall if Version 8621 (with the 32 bit TCP/IP stack) is licensed for use on Warp Server 4 or not. It should run okay (I know a number of people who have run it on the Warp 3 code base without problem), but I just am not clear on the licensing. I *think* the license allows for it to be installed on Warp Server 4, but best to check the info for yourself. Anyways, if you chose to check it out, you'll need to first run the main install and then the update.
Some of the Warp 3 kernels had trouble seeing memory above 64 Megs, you may want to check and make sure that the system is seeing all your memory. Grab one of the utilities off hobbes to check this:
And if your system only sees 64 megs, install the loader patch tool which will allow most systems to see all the memory available:
As for config.sys - it all depends on what you're using the machine for. If you're going to use it as a server, you'll probably want to put the following in your config.sys:
Essentially, the Priority=absolute statement sets up OS/2 to not give a priority boost to whatever the "active" program is on the screen. For a server setting, this is ideal because it essentially means that stuff will be served out on a smoother basis - without the user interface getting a priority boost. However if you're using the machine as a desktop machine, you'll want it to read:
This will allow the system to give the user interface and applications which are "active" a bit of a priority boost - allowing for a smooth response of the GUI and apps you're using, at a slight expense to stuff running in the background.
Timeslice and Maxwait - I've found that on pretty much any Pentium based computer (anything above a 486) these settings work well and give maximum performance. On older systems (486, 386, etc), you could play around with these to get a smoother responding system. Consult the online help system for more info on these settings.
Also, if you have Warp Server Advanced, you'll want to use HPFS386 for maximum performance, and increase the cache to soemthing fairly big. Although one comment - some users have reported they experience slower disk performance when they set the cache to larger then 64 Megs, even on systems with over 1 gig. And its been found that reducing the cache to 64 Megs (or less) offers a better performance then going above 64. I can't comment further on this.
If you don't have the "advanced" version, then the best you can do with HPFS is up the cache (the /CACHE switch in the IFS line) to the 2 MB limit. Some users have also found that playing around with the /CRCREL: and other options can improve response time.
Also, with 2 gigs you'll still want a swap file, but you probably won't need to start out with an initially big file. When you get the system up and running, I'd suggest starting off with a small swap file, and keep an eye on it to see if it grows. Consult the SWAPPATH= setting (its documented in the Help stuff) for this. One machine that I use as a server on plain old Warp 4 (with FP15) that I only have 512 MB in has an initial swap setting of 20 MB, and the file has yet to grow.
Or, if you have a machine with JFS and LVM, I believe it can be installed and made to work on Warp Server 4, although I have never tried this. If you chose to try this, do so with caution.
Hope this helps!