[p4] Is anyone using Perforce on Win2K?

[Daniel Neades]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We have been using Perforce with Windows 2000 server and clients for several
months. We recently updated to the 2000.1 release from the previous one. It
seems a stable, robust and reliable solution and it is working well for us.

My only negative comment about the server would be that the case
insensitivity causes problems when one wishes to rename a file or folder by
changing only the case of the filename. In these circumstances, Perforce
does not recognize that a change has occurred and therefore does not store
the change. I've had to jump through hoops to sort this out on several
occasions, and I don't have a workaround which preserves history information
for the files affected.

- --
Daniel Neades
Director, Araxis Ltd
Wellington House, East Road, Cambridge CB1 1BH, UK

Tel +44 (0)1223 451 054
Fax +44 (0)1223 451 154

www.araxis.com

> -----Original Message-----
> From: perforce-user-admin at perforce.com
> [mailto:perforce-user-admin at perforce.com]On Behalf Of Martin Ellison
> Sent: 23 October 2000 08:21
> To: perforce-user at perforce.com
> Subject: RE: [p4] Is anyone using Perforce on Win2K?
>
>
> I asked, "Is anyone using the Perforce server on MS Windows 2000?"
>
> And I received several responses on the lines of "Win2000 on client,
> <something else> on Server."
>
> What we are considering is using MS Win2000 as the platform for
> the Perforce
> *server*. So our question is whether anyone else has done this
> successfully.
>
>
> The reason, by the way, has to do with the options available to us for
> support. Other platforms are at present less possible alternatives for us
> for various reasons.
>
> Regards,
> Martin Ellison
> Perforce administrator
> Bullant Technology Ltd.
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0

iQA/AwUBOfWQR88UlgdvEmWUEQJHvwCfa26dHzJiAjl8km7IKV8UsKpgGC0AniEg
ET5bQ7uSaSZ8MzQxnbBU1lk8
=9ogs
-----END PGP SIGNATURE-----