Discussion:
P4Win -P Problem
(too old to reply)
Paul S. Person
2016-02-09 18:38:16 UTC
Permalink
Raw Message
P4Win, running under Windows 8.1, is now showing a minor problem.

I invoke P4Win with a shortcut using this command line:

"C:\Program Files (x86)\Perforce\P4win.exe" -P ug17pq53

This worked with the old server.

With the new server, P4Win responds with an "enter password" dialogue
box.

The informational message is

WARNING: Perforce password (P4PASSWD) invalid or unset.

When I copy the password into the dialogue box, I am logged on.

It seems unlikely that Perforce has removed the -P option, although I
suppose anything is possible.

I was wondering if the other old clients (particularly OS/2) have the
same problem.

Or if there is a setting that would fix this.

Still, it does work and it is usable.
--
"Nature must be explained in
her own terms through
the experience of our senses."
Paul S. Person
2016-02-09 19:00:52 UTC
Permalink
Raw Message
On Tue, 09 Feb 2016 10:38:16 -0800, Paul S. Person
Post by Paul S. Person
P4Win, running under Windows 8.1, is now showing a minor problem.
"C:\Program Files (x86)\Perforce\P4win.exe" -P ug17pq53
Ooops! I have since changed my password, so the one shown is no
longer valid.
Post by Paul S. Person
This worked with the old server.
With the new server, P4Win responds with an "enter password" dialogue
box.
The informational message is
WARNING: Perforce password (P4PASSWD) invalid or unset.
When I copy the password into the dialogue box, I am logged on.
It seems unlikely that Perforce has removed the -P option, although I
suppose anything is possible.
I was wondering if the other old clients (particularly OS/2) have the
same problem.
Or if there is a setting that would fix this.
Still, it does work and it is usable.
--
"Nature must be explained in
her own terms through
the experience of our senses."
Frank Beythien
2016-02-09 21:38:10 UTC
Permalink
Raw Message
Post by Paul S. Person
P4Win, running under Windows 8.1, is now showing a minor problem.
"C:\Program Files (x86)\Perforce\P4win.exe" -P ug17pq53
This worked with the old server.
With the new server, P4Win responds with an "enter password" dialogue
box.
The informational message is
WARNING: Perforce password (P4PASSWD) invalid or unset.
When I copy the password into the dialogue box, I am logged on.
It seems unlikely that Perforce has removed the -P option, although I
suppose anything is possible.
I was wondering if the other old clients (particularly OS/2) have the
same problem.
NO, with the old p4 cmdline client on OS/2 I don't see any difference.
I'm using the environment var P4PASSWD for pw.

CU/2
Frank
Paul S. Person
2016-02-10 17:11:04 UTC
Permalink
Raw Message
Post by Frank Beythien
Post by Paul S. Person
P4Win, running under Windows 8.1, is now showing a minor problem.
"C:\Program Files (x86)\Perforce\P4win.exe" -P ug17pq53
This worked with the old server.
With the new server, P4Win responds with an "enter password" dialogue
box.
The informational message is
WARNING: Perforce password (P4PASSWD) invalid or unset.
When I copy the password into the dialogue box, I am logged on.
It seems unlikely that Perforce has removed the -P option, although I
suppose anything is possible.
I was wondering if the other old clients (particularly OS/2) have the
same problem.
NO, with the old p4 cmdline client on OS/2 I don't see any difference.
I'm using the environment var P4PASSWD for pw.
Past experimentation, IIRC, showed that P4Win pays no attention to
that variable. Nor does it store the password in the registry, as it
claims to do -- or rather, if it does, it makes no use of it.

Which is why I am interested in the status of -P.

But I am glad to hear that the OS/2 client works!
--
"Nature must be explained in
her own terms through
the experience of our senses."
Loading...