I just upgraded our NW3.12 server from a P3-500 w/128 MB to a P4-2.8 w/512 ECC. The old hard drives were 9 gig and the new hard drives are 80 gigs. There are three volumes on the server that were extended to 25-35 gigs each. The sys volume is 500 MB. The short term memory was increased to 32 MB. The old server typically has 50 open connections w/ roughly 175 open files. It rarely hits 90% utilization. The new server hits 90+% utilization any time files are copied. Additionally, when copying files several work stations lose their network connection to the server. I've also noticed that the server console is frozen and the HDD light is on solid while files are being copied. Does anyone know why the faster machine is running slower than the original machine and why the utilization is so high when copying files? Are there additional parameters I should change? Thanks.

> Does anyone know why the faster machine is > running slower than the original machine > and why the utilization is so high when > copying files? Old Drives = SCSI / New Drives = IDE ? If so SCSI is that much faster, but I'm not sure if its the case. Even if the old drive was IDE, the OS would stumble over the obese volumes, as it was never initially made to handle it. I've seen NW 3.12 SCREAM on a 386 16Mhz/40MB HD, then CRAWL on a P3-850/8GB HD. If DOS is on a 486 then moved to a pentium 4, its faster. Its faster because it doesn't try to optimize the performance of the machine, it simply does its thing. NetWare v3.12, on the other hand, was made to make the most out of what its given. The max that was expected was around a 486/40Mhz. As a simple test, I'de turn off all CMOS control of the hard drives (No Ultra DMA, No PIO) I'm not saying they can't be used, but the motherboard could have a conflicting BIOS to the OS. Barring that, if there is a fix, I would look at caching read/writes in advance. My advice is to alter the OS parameters to see if the new hardware can be controlled. But since this is way BEYOND any intentions of the OS, it may not help. All parameters can be changed from the console (SET) or just edit the autoexec.ncf. I suggest the console so you can RECORD the current value in-case it trashes the server. Tweak each one, then tweak another, staying consistant. Once you find a difference, back track to verify the answer: File Caching: Minimum File Cache Buffers = 1000 Maximum Concurrent Disk Cache Writes = 1000 Dirty Disk Cache Delay Time = 10 seconds Read Ahead = Off Directory Caching: Dir. Cache Buffer NonReferenced Delay = 5 min Maximum Directory Cache Buffers = 4000 Minimum Directory Cache Buffers = 2000 Dirty Directory Cache Delay Time = 10 seconds Dir. Cache Allocation Wait Time = 2 minutes File System: Max. % of Volume Used by Directory = 5% Max. % of Vol. for Extended Attributes = 5% NCP File Commit = OFF (also make sure the client's True Commits are Off. Depending on the client version and OS, they could be tweaked as well.) Overall, I think that's all 3.12 has for anything that would affect "copying". There could be other concerns, for instance if the NIC speed is faster, but this I think would be the right place to start. GL - HTH, -J