In retrospect I thought I should provide just a little more information on the first partition size in case you're not really familiar with the pitfalls. Microsoft made particularly useful and critical changes to the ntfs.sys file and other aspects of the OS in SP3 or SP4 or both. I'm sorry I'm a little vague on the precise history. It has been a while, and I didn't use NT4 much.
One of the worst things about using NT4 these days is the size of the applications you may have to use on a pretty skimpy boot partition. Don't make things worse by using an older base version of NT4 for the installation. If you go with at least NT4 SP4 you'll be able to get the maximum possible first partition size (NTFS only, please) with the standard installation procedures (boot from diskette or boot from CD). But that is still going to get you only a 4 gigabyte combination system-boot partition. (If I remember accurately the system partition is the one with NTLDR on it, and the boot partition is the one with the \WINNT directory on it. I've always thought it was best to have them be one and the same, the C: drive.) The partition gets created first as a FAT partition, t hen gets converted to NTFS during reboot. That's really not the optimum way to get this job done. That's true especially if you need lots of space for applications that really, really want to sit on the C: drive. There are ways to surmount many of the problems that come with apps that are set up to install on C:, but some of the solutions are tricky and can backfire. If you need the space on C:, make sure you have it right from the start.
If you partition and format drives for these machines as slaves in other systems, you can maximize the size of the first partition to a top figure of 7.8 gigabytes. You don't have to go right to the edge and hang your toes over it, but it's nice to be standing in a high place when the sea level starts rising.
The 7.8 gigabyte limit is pretty dangerous to exceed, though I've seen people do it without suffering many consequences. But all it takes is some process or another to come around and shuffle some of the boot file locations to render the partition unbootable. I guess a lot of us have heard stories about somebody who installed a new service pack (no more of these after 6a) or ran a defragger and never booted again. Well, if he didn't have an ERD.
I'm sure there are people here who know a lot more about this than I do. Maybe they know slicker ways to deal with all of this, but I wanted to try to help you do as good a job as possible. You and the people who will be using these computers may need all of the advantages you can figure out how to provide.
Good luck!
Ernie