Does anyone know how to deal with case sensitive clients and a case insensitive server? We're running an NT server, mostly NT clients, and I have a Solaris client.

Here's the problem. The depot looks like this

//depot/TEST/one //depot/TEST/two //depot/TEST/three

then from a Windows NT client someone adds

//depot/test/four

which is fine if the client is case insensitive. The problem is with my Solaris client when I synchronize to the depot I end up with

~/TEST/one ~/TEST/two ~/TEST/three ~/test/four

on my local drive. Which is not what person who added the file to the depot meant, nor what I want to see on my local drive.

I checked our depot on the server and there's only one directory named 'TEST' and that directory has the case of the first addition, in this case 'TEST'. Somewhere in the rest of the metadata it is recorded that the case of the second addition is different than the case of the first. From listening to this list it seems that modifying a checkpoint behind perforce's back and then recovering it would be one possible solution. But is there a better way? And more importantly a way to prevent it from happening in the first place?

-Bill bill.wishon at digintelligence.com