Hi Bret,

Writing data is always slower than reading it (on any drive). Writing data to your C: drive, will be faster than writing to the L: drive because c: is local and L: is on the network (the pipe is about 10 times slower).

Copies between network drives take longer because the data is read BY YOUR COMPUTER (going through the network), and then written again BY YOUR COMPUTER (going through network again).

Novell has a command called NCOPY that will copy files WITHIN a server, so if both drives N: and L: are in the same server, NCOPY N:somefile L: will really fly.

Another thing worth considering in order to speed up a server would be a scsi drive. Supposedly they handle multi-user environment better. I have never had a chance to run benchmarks myself in this regard, but it does seem reasonable.

Alex


>It seems we are having a little problem with our Novell Network here. Since I am not the Network guy, but the ones we have have not solved the problem, I thought I would post it here to see if anyone else has seen the problem before.
>
>I have my developer files (project, classes, etc) on the Novell mapped drive of L. When I build an exe say to my C drive for testing. The project builds it in a rapid fashion (30-45 seconds). Placing the new exe on my C drive in very little time at all, the exe size is 14MB. Now when I decide to build an exe to the Novell Network K drive (where users operate), the build will take approx 2 to 3 minutes to build.
>
>So I tested a few other things. A copy from the Novell Network drive to my C drive goes much faster than a copy from a Novell Mapped drive to another Novell mapped drive.
>
>Has anyone seen this before, or maybe give me some ammo to send to the Network boys to fix this problem or maybe this is normal for Novell.
>
>TIA