The initial Warp Server boot floppies were unable to auto-detect the SCSI controllers of either our Compaq Computer Corp. Proliant or HP NetServer file servers. Because the generic floppies were already crammed with drivers, we had to delete files to make space, guessing at what wasn't needed. On more than one occasion, we found it simpler to reinstall Warp Server in its entirety than to try to modify the configuration files to accept new SCSI cards or network protocol configurations. Security and performance Just as we expect a NOS should do, Warp Server gives administrators a great many options in controlling access to network data. User access can be set by time and location.
Parameters governing password length, frequency of changes, and uniqueness are also available.
An SMP version of Warp Server isn't available, so our performance testing was restricted to single CPU tests. IBM officials said SMP support will be made available for free to Warp Server 4 customers late this year. Warp Server nonetheless produced excellent performance in file and print services, but proved mediocre as an applications server. Running on a Compaq Proliant 4000 server equipped with a single 133MHz Pentium, Warp Server held its own against Windows NT 3.51 Server and NetWare 4.10 SMP as both an applications server and a file and print server. When running these three NOSes on a single CPU, the applications-server performance variance between them was so small that most users will likely never notice the difference.