Summary: The Perforce command line p4
does not work correctly unless I open the shell from P4V. How/where do I edit things to fix my configuration so that it always works?
Details
On Windows 7x64, if I run cmd.exe
and then use the p4 command line it attempts to connect to an old server that no longer exists:
C:\>p4 info
Perforce client error:
Connect to server failed; check $P4PORT.
TCP connect to p4proxy-bdr:2006 failed.
connect: p4proxy-bdr:2006: WSAETIMEDOUT
C:\>echo %P4PORT%
%P4PORT%
However, if I launch P4V (which is connecting to the correct server), right-click on any file in my Workspace and choose "Open Command Window Here", the same commands work correctly:
C:\>p4 info
User name: gkistner
Client name: gkistner-dt2
Client host: gkistner-dt2
Client root: C:/p4/p4sw
Current directory: c:\
Peer address: <redacted>
Client address: <redacted>
Server address: <redacted>
Server root: <redacted>
Server date: 2013/08/13 10:05:09 -0700 PDT
Server uptime: 1512:04:23
Server version: <redacted>
Server license: <redacted>
Server license-ip: <redacted>
Case Handling: sensitive
C:\>echo %P4PORT%
p4sw:2006
Where is P4 getting the configuration when I launch it from a vanilla cmd.exe
, and how do I change that to be the same as what P4V sets up?