Perforce down?

[Paul S. Person]

I am getting

ERROR: Connect to server failed; check $P4PORT.
TCP connect to perforce.openwatcom.org:3488 failed.
connect: perforce.openwatcom.org:3488: WSAECONNREFUSED

when I try to start P4Win.

Any thoughts?
--
"Nature must be explained in
her own terms through
the experience of our senses."

[Frank Beythien]

Am 12.01.2012 20:40, schrieb Paul S. Person:
Hello Paul,

> I am getting
>
> ERROR: Connect to server failed; check $P4PORT.
> TCP connect to perforce.openwatcom.org:3488 failed.
> connect: perforce.openwatcom.org:3488: WSAECONNREFUSED
>
> when I try to start P4Win.
>
> Any thoughts?

Same procedure as every year, the renewal of the annual subscription is
missing.

[Paul S. Person]

I got the same thing with p4 -- just now.

Looks like whoever has been doing the renewals is missing as well.

I really like Perforce. I shudder when I read about the problems of
the alternatives. But an alternative that works continually is
beginning to appear better than a superior solution that stops working
on a regular recurring basis.

Good thing I'm in a Wiki-rewrite and research mode, have the source
files I need checked out so I can get the tabs working a bit closer to
how wgml 4.0 treats them, and have SourceNavigator to edit the source
files with!

[Marty Stanquist]

Yes, P4 is also down. I like Perforce as well. If needed, I could assist
with some of the administrative tasks.

Marty

"Paul S. Person" wrote in message
news:bc56h79fof75djsh3...@4ax.com...

[Leif Ekblad]

I have nothing against Perforce, but there seems to be several issues with
it. Not only the issue with
renewing the license, but the current server also doesn't work with current
versions of Perforce. You
need to download an ancient client version to make it work.

Leif Ekblad



"Marty Stanquist" <mart...@att.net> skrev i meddelandet
news:jf1sc8$vem$1...@www.openwatcom.org...

[Marty Stanquist]

I am satisfied with the P4 client, it's quite adequate. However, recent
Perforce releases are much more powerful and would be really nice to use.
I'm for doing an upgrade, but this will take time and we may break something
in the process.

Marty

"Leif Ekblad" wrote in message news:jf1ueq$1o5$1...@www.openwatcom.org...

[Frank Beythien]

Am 16.01.2012 20:40, schrieb Leif Ekblad:
> I have nothing against Perforce, but there seems to be several issues with
> it. Not only the issue with
> renewing the license, but the current server also doesn't work with current
> versions of Perforce. You
> need to download an ancient client version to make it work.
>
> Leif Ekblad

I'm against upgrading the perforce server if this breaks using my latest
AFAIK OS/2 cli client (Rev. P4/OS2/2002.2/41879 (2003/02/24) ). It does
all I expect from it. For graphical filecompare and other tasks I have
local OS/2 tools so I don't miss the extended features of a newer P4.

Frank

[Mat Nieuwenhoven]

On Tue, 17 Jan 2012 10:08:07 +0100, Frank Beythien wrote:

>Am 16.01.2012 20:40, schrieb Leif Ekblad:
>> I have nothing against Perforce, but there seems to be several issues with
>> it. Not only the issue with
>> renewing the license, but the current server also doesn't work with current
>> versions of Perforce. You
>> need to download an ancient client version to make it work.
>>
>> Leif Ekblad
>
>I'm against upgrading the perforce server if this breaks using my latest
>AFAIK OS/2 cli client (Rev. P4/OS2/2002.2/41879 (2003/02/24) ). It does
>all I expect from it. For graphical filecompare and other tasks I have
>local OS/2 tools so I don't miss the extended features of a newer P4.

I wonder what you use for graphical file compare for OS/2. I find gfc very
much lacking compared to BeyondCompare which I use at work. I don't know
the new Perforce or how it compares in this.

Mat Nieuwenhoven

[Frank Beythien]

I use gfc because I like the quick overview bars on the right side, and
kdiff3 from sourceforge.
CU/2
Frank

>

[Roald Ribe]

On Wed, 18 Jan 2012 09:12:06 -0300, Frank Beythien <fbey...@gmx.de> wrote:

> Am 18.01.2012 06:06, schrieb Mat Nieuwenhoven:
>> On Tue, 17 Jan 2012 10:08:07 +0100, Frank Beythien wrote:
>>
>>> Am 16.01.2012 20:40, schrieb Leif Ekblad:
>>>> I have nothing against Perforce, but there seems to be several issues with
>>>> it. Not only the issue with
>>>> renewing the license, but the current server also doesn't work with current
>>>> versions of Perforce. You
>>>> need to download an ancient client version to make it work.
>>>>
>>>> Leif Ekblad
>>>
>>> I'm against upgrading the perforce server if this breaks using my latest
>>> AFAIK OS/2 cli client (Rev. P4/OS2/2002.2/41879 (2003/02/24) ). It does
>>> all I expect from it. For graphical filecompare and other tasks I have
>>> local OS/2 tools so I don't miss the extended features of a newer P4.

Have you tried to run the latest cli with the HXDOS extender?
It runs a lot of WIN32 compilers/cli tools on DOS, so why not on OS/2?

Roald

[Paul S. Person]

On Tue, 17 Jan 2012 10:08:07 +0100, Frank Beythien <fbey...@gmx.de>
wrote:

>Am 16.01.2012 20:40, schrieb Leif Ekblad:
>> I have nothing against Perforce, but there seems to be several issues with
>> it. Not only the issue with
>> renewing the license, but the current server also doesn't work with current
>> versions of Perforce. You
>> need to download an ancient client version to make it work.
>>
>> Leif Ekblad
>
>I'm against upgrading the perforce server if this breaks using my latest
>AFAIK OS/2 cli client (Rev. P4/OS2/2002.2/41879 (2003/02/24) ). It does
>all I expect from it. For graphical filecompare and other tasks I have
>local OS/2 tools so I don't miss the extended features of a newer P4.

Have you tried installing the latest-and-greatest Perforce (no license
needed, it appears, for up to 20 users) on, say, the Windows machine
and seeing if your OS/2 client can work with it?

I mean, that would produce a definitive answer!

[Frank Beythien]

Am 18.01.2012 18:26, schrieb Paul S. Person:

Hello Paul,

> On Tue, 17 Jan 2012 10:08:07 +0100, Frank Beythien <fbey...@gmx.de>
> wrote:
>
>> Am 16.01.2012 20:40, schrieb Leif Ekblad:
>>> I have nothing against Perforce, but there seems to be several issues with
>>> it. Not only the issue with
>>> renewing the license, but the current server also doesn't work with current
>>> versions of Perforce. You
>>> need to download an ancient client version to make it work.
>>>
>>> Leif Ekblad
>>
>> I'm against upgrading the perforce server if this breaks using my latest
>> AFAIK OS/2 cli client (Rev. P4/OS2/2002.2/41879 (2003/02/24) ). It does
>> all I expect from it. For graphical filecompare and other tasks I have
>> local OS/2 tools so I don't miss the extended features of a newer P4.
>
> Have you tried installing the latest-and-greatest Perforce (no license
> needed, it appears, for up to 20 users) on, say, the Windows machine
> and seeing if your OS/2 client can work with it?

No, my winxp notebook is out of disk space to play with. If the OS/2 cli
P4 does not work any more, I think I'll switch to linux completely.

But we drifted away from the thread subject. I hope Peter will soon take
care of the perforce server...

CU/2
Frank

[Frank Beythien]

No, newer version of win32, ... don't run anymore in winos/2.
And I'm happy with the current p4 functionality.

CU/2
Frank

[Marty Stanquist]

Peter, I have time available to assist with Perforce if this would help.

Marty

"Frank Beythien" wrote in message news:jf73on$2p1$1...@www.openwatcom.org...

[Peter C. Chapin]

On 2012-01-16 14:04, Marty Stanquist wrote:

> Yes, P4 is also down. I like Perforce as well. If needed, I could assist
> with some of the administrative tasks.

I'm the person who usually renews the license and, yes, I'm a bit tardy
this year due to many other obligations, etc. I sent a message to
Perforce and received the necessary forms. I should have the system back
up and running in a couple more days.

As far as Perforce client version goes. I'm using p4 2010.1 and it works
with the current server. I'm not sure I'd classify that as ancient, but
I suppose that's a matter of perspective. Leif, which version are you
having problems with?

Marty, are you serious about helping with administrative tasks? Be
careful what you wish for... :)

Peter

[Leif Ekblad]

> I suppose that's a matter of perspective. Leif, which version are you
> having problems with?

All the current distributions of Perforce, unless the server version has
been updated. Last I installed it on a new computer, I needed to pick a
Windows 2000 or somehing version that they no longer support.

Leif Ekblad

[Marty Stanquist]

Yes, something may come up unexpectedly, like during exam week. I don't mind
assisting.

Marty

"Peter C. Chapin" wrote in message news:jfjhu0$mqp$1...@www.openwatcom.org...

[Paul S. Person]

On Mon, 23 Jan 2012 19:14:16 +0100, "Leif Ekblad" <le...@rdos.net>
wrote:

And the version number is?

[Peter C. Chapin]

On 2012-01-23 13:14, Leif Ekblad wrote:

> All the current distributions of Perforce, unless the server version has
> been updated. Last I installed it on a new computer, I needed to pick a
> Windows 2000 or somehing version that they no longer support.

I'll probably have to set myself up on Windows XP sometime fairly soon
so I'll see how it goes for me. My inclination would be to use the
latest client. :)

Peter

[Johannes]

The latest Windows Version which work's with the Server is "P4 Client 2010
Dezember 01 (Rev. Perforce Visual Client/NTX86/2010.1/276058)"
Newer P4 Version need a newer Server Version.

Johannes

"Peter C. Chapin" <PCh...@vtc.vsc.edu> schrieb im Newsbeitrag
news:jforsp$ouj$2...@www.openwatcom.org...

[Paul S. Person]

On Wed, 25 Jan 2012 16:40:14 +0100, "Johannes" <JDie...@t-online.de>
wrote:

>The latest Windows Version which work's with the Server is "P4 Client 2010
>Dezember 01 (Rev. Perforce Visual Client/NTX86/2010.1/276058)"
>Newer P4 Version need a newer Server Version.

That is P4V, not the command line client. It shouldn't matter, of
course, but then, perhaps it does if P4V requires the new features to
be present.

Yesterday, I downloaded and installed the p4 server and command-line
client.

It took some doing (I am used to P4Win, not the command line p4), but
I managed to establish these facts:

1) p4d -V shows that the local server version is 2011.1.
2) If pointed at "3488", P4Win connects to the local server well
enough to detect that the my user is not defined and to pop up a
wizard to let me define one.
3) P4Win is version 2004.2.
4) p4 version 2011.1 has no trouble connecting with version 2006.1,
which is what Open Watcom is running.

Expanding 2) by actually creating a local server repository for p4d
and and local client repository for p4Win can be done, I suppose,
although it would take some research as the command-line help does not
appear to address designating a server repository, if that is needed
to settle the issue of whether P4Win 2004.2 can, in fact, work with
p4d 2011.1.

Similarly, 4) can be further explored by actually defining the
environment variables or whatever is actually needed to verify that
"p4 sync", for example, will work. This might take even more time as
using both P4V and p4 on the same account on the same machine has, in
the past, proven difficult, that is, it may not be as simple as
defining environment variables because p4 is still too stupid to find
them in the Registry (where P4Win finds them with no trouble at all).

Of course, such explorations will take time and so be restricted to
small steps.

Note: the 2011.1 versions appear (from the bumf on the website) to
have added additional capabilities. I would not expect older clients
to be able to use the new features, but, provided all the old features
are still present in the 2011.1 server, I would expect those features
to work just as they do now.

[Peter C. Chapin]

On 2012-01-25 14:16, Paul S. Person wrote:

> 4) p4 version 2011.1 has no trouble connecting with version 2006.1,
> which is what Open Watcom is running.

Considering the age of the Perforce server we are using with Open Watcom
it does make sense to attempt to upgrade it. Of course we are struck
with a truly ancient version of the p4 client for OS/2 since Perforce is
no longer maintaining that client. Thus it would be good to know if that
client can work with the latest server.

Peter

[Paul S. Person]

Obvious searches on the Perforce site do not produce any information
on OS/2. Mostly, I suspect, because it is searching for "OS" and
treating that as "OS X", and producing far more pages than I am
willing to go through.

There is a CygWin version. CygWin in a Linux environment that runs on
Windows. I have no idea if this is a source distribution (for the
command-line client only, of course) or not but, if it is, it might be
compilable under Linux. A decade or more ago I investigate CygWin and
another translated Linux compiler and, IIRC, with compilable source
and the correct tool chain, an OS/2 version might be producible.

Of course, it could make sense to produce an executable that runs
under a Linux environment that is being hosted on Windows. I, myself,
can't see that it would, but I suppose it is possible.

My OS/2 4 FP 15 machine can ping my XP machine, so, if I had the OS/2
p4 client in question, I might be able to test it. Eventually.

[Rugxulo]

Hi,
I hope I'm not intruding too much into this conversation, but
anyways ....

On Jan 18, 12:41 pm, Frank Beythien <fbeyth...@gmx.de> wrote:
> Am 18.01.2012 18:26, schrieb Paul S. Person:
>

> > On Tue, 17 Jan 2012 10:08:07 +0100, Frank Beythien <fbeyth...@gmx.de>
> > wrote:
>
> >> I'm against upgrading the perforce server if this breaks using my latest
> >> AFAIK OS/2 cli client (Rev. P4/OS2/2002.2/41879 (2003/02/24) ).
>

> > Have you tried installing the latest-and-greatest Perforce (no license
> > needed, it appears, for up to 20 users) on, say, the Windows machine
> > and seeing if your OS/2 client can work with it?
>
> No, my winxp notebook is out of disk space to play with. If the OS/2 cli
> P4 does not work any more, I think I'll switch to linux completely.

I know I'm not an OpenWatcom developer, but I sympathize with your
efforts (also because I prefer DOS, and OS/2 is related, though sadly
I've never actually used OS/2 before).

It seems a bit drastic to change OS just for this. I'm probably
misunderstanding, though, as maybe you meant "switch to Linux" host
for Perforce.

http://os2ports.smedley.id.au/index.php?mact=News,cntnt01,detail,0&cntnt01articleid=10&cntnt01origid=57&cntnt01returnid=39

This guy seems big on porting to OS/2, and he recently seems to have
switched to Ubuntu x64 host with eCS guest via VirtualBox (presumably
needing VT-X). It seems 2x faster compiles too. Maybe that's what you
meant? Or perhaps you could run the (circa 2008) OS/2 VirtualBox atop
eCS running Linux guest and run the Linux Perforce client there??

This ...

http://www.openwatcom.org/index.php/Configure_Perforce_client

... points to this ...

http://www.perforce.com/perforce/loadprog.html

... which isn't found! (And no WayBack copy due to robots.txt, doh.)

A quick attempt to find the OS/2 version shows these two URLs, and I'm
not sure if these are latest or what:

ftp://ftp.perforce.com/perforce/r02.2/bin.os2/ (dated 9.9.2004)

EDIT: Seems I should have searched the newsgroup first. "r02.2" is
indeed latest (according to Frank circa last June)

http://www.os2site.com/sw/dev/util/index.html (only old from
2002)

Though interesting that the latter also has (experimental port of) Git
1.6.2 from 2009, but anyways, that's useless here (unless someone
wants to setup a test repo for it, and I'd be of no help).

Anyways, I really dislike it when old working software is thrown away
or obsoleted even when it works. Oh well. Sorry if this post wasn't
more help, but I don't know what else to tell you. I guess you'll
figure it out. Godspeed!

[Frank Beythien]

Am 26.01.2012 18:55, schrieb Paul S. Person:

[...]

>
> Obvious searches on the Perforce site do not produce any information
> on OS/2. Mostly, I suspect, because it is searching for "OS" and
> treating that as "OS X", and producing far more pages than I am
> willing to go through.

No, you can only find it via perforce downloads completelist others...

>
> There is a CygWin version. CygWin in a Linux environment that runs on
> Windows. I have no idea if this is a source distribution (for the
> command-line client only, of course) or not but, if it is, it might be
> compilable under Linux. A decade or more ago I investigate CygWin and
> another translated Linux compiler and, IIRC, with compilable source
> and the correct tool chain, an OS/2 version might be producible.
>
> Of course, it could make sense to produce an executable that runs
> under a Linux environment that is being hosted on Windows. I, myself,
> can't see that it would, but I suppose it is possible.
>
> My OS/2 4 FP 15 machine can ping my XP machine, so, if I had the OS/2
> p4 client in question, I might be able to test it. Eventually.

Try (worked for me in June 2011)

ftp://ftp.perforce.com/perforce/r02.2/bin.os2/p4.exe
CU
Frank

[Frank Beythien]

Am 26.01.2012 19:59, schrieb Rugxulo:
> Hi,
> I hope I'm not intruding too much into this conversation, but
> anyways ....

The thread subject has changed a lot since start...

>
> On Jan 18, 12:41 pm, Frank Beythien <fbeyth...@gmx.de> wrote:
>> Am 18.01.2012 18:26, schrieb Paul S. Person:
>>
>>> On Tue, 17 Jan 2012 10:08:07 +0100, Frank Beythien <fbeyth...@gmx.de>
>>> wrote:
>>
>>>> I'm against upgrading the perforce server if this breaks using my latest
>>>> AFAIK OS/2 cli client (Rev. P4/OS2/2002.2/41879 (2003/02/24) ).
>>
>>> Have you tried installing the latest-and-greatest Perforce (no license
>>> needed, it appears, for up to 20 users) on, say, the Windows machine
>>> and seeing if your OS/2 client can work with it?
>>
>> No, my winxp notebook is out of disk space to play with. If the OS/2 cli
>> P4 does not work any more, I think I'll switch to linux completely.
>
> I know I'm not an OpenWatcom developer, but I sympathize with your
> efforts (also because I prefer DOS, and OS/2 is related, though sadly
> I've never actually used OS/2 before).
>
> It seems a bit drastic to change OS just for this. I'm probably
> misunderstanding, though, as maybe you meant "switch to Linux" host
> for Perforce.
>

I have looked at other solutions for some time. When (perhaps due to
playing with linux in Virtualbox 1.5.6? and trying to mount the JFS eCS
partitions) the eCS PC partitions got corrupted, I decided to switch to
Ubuntu and run eCS in Virtualbox. That was not as ṕainless as expected.
So I'm not dropping eCS but trying other solutions, too. And continuing
work at reinventing WGML.

> http://os2ports.smedley.id.au/index.php?mact=News,cntnt01,detail,0&cntnt01articleid=10&cntnt01origid=57&cntnt01returnid=39
>
> This guy seems big on porting to OS/2, and he recently seems to have

Yes, this australian guy is doing a great job with porting linux SW to OS/2.

> switched to Ubuntu x64 host with eCS guest via VirtualBox (presumably
> needing VT-X). It seems 2x faster compiles too. Maybe that's what you

The new box is the main speed gain. When I got the quad core Q8300,
which replaced my old Pentium 500Mhz, the build time for OW dropped from
12 hours to 1 hour.

[Paul S. Person]

On Thu, 26 Jan 2012 10:59:29 -0800 (PST), Rugxulo <rug...@gmail.com>
wrote:

<snippo>

Thanks for finding these!

>ftp://ftp.perforce.com/perforce/r02.2/bin.os2/ (dated 9.9.2004)

I downloaded it.

XP confirms that it is, in fact, a 32-bit OS/2 executable.

When run under OS/2, it does nothing. Well, the help system (p4 -h, at
least) works, but p4 -p <xp computer ip address>:3488 produces ...
nothing. I can /ping/ the XP computer, but p4 won't contact the p4d on
the XP computer.

Is there some secret here? I suppose I could try creating a CMD file
to set the environment variables and see if I can reach the OW server.

On a happier note, I appear to have downloaded a manual on configuring
the server so, if necessary, I can probably do more testing. Even if
it doesn't apply to the current version, the equivalent manual for the
current version is surely available on the website.

>EDIT: Seems I should have searched the newsgroup first. "r02.2" is
>indeed latest (according to Frank circa last June)
>
>http://www.os2site.com/sw/dev/util/index.html (only old from
>2002)

These turned out to be two more copies of the exact same version
(2002.2).

The ZIP had the "Release Notes" in it. Nothing specific to OS/2
(except a change involving temporary file name length), but it did
state that, in updating from 98.2 and later, the 2003.1 server will
automatically upgrade the databases if they have fewer than 1000
changes. So, if we do update to 2011.1 or whatever, there may extra
hassle if that limit applies to our version (2006.1), as I am sure we
have way more than 1000 changes! It also warns that considerable space
(disk space, presumably) may be needed -- three times the space of the
affected .db files.

Of course, it is the release notes for the version being upgraded to
that would have to be checked, but this does suggest that there is a
possibility of actual work having to be done (as opposed to just
installing the new p4d, starting it, and waiting for it to finish
updating the database).

>Anyways, I really dislike it when old working software is thrown away
>or obsoleted even when it works. Oh well. Sorry if this post wasn't
>more help, but I don't know what else to tell you. I guess you'll
>figure it out. Godspeed!

I agree (my brother, who believes any software whose website hasn't
been updated in the last 6 months is clearly out of date, no matter
how well it works, would not). One of the best parts of the Internet
is that it is actually easier to leave antiquated software and drivers
on-line than it is to remove them (removing them takes effort; leaving
them does not). Of course, over time, they will become unusable: thus,
my orphaned Acer scanner, supported by Benla (IIRC), had a final
driver update before XP arrived; XP did install it (it didn't want to)
but I don't know that Windows 7 would even allow it to be installed --
or if I would want to install it anyway. Even with XP I have had
problems installing drivers that it objected to and which turned out
not to work with it.

[Paul S. Person]

On Thu, 26 Jan 2012 20:43:03 +0100, Frank Beythien <fbey...@gmx.de>
wrote:

>Try (worked for me in June 2011)
>
>ftp://ftp.perforce.com/perforce/r02.2/bin.os2/p4.exe

As I noted, I tried it but it just sits there, Even when pointed
explicitly at the same IP address that ping is using (the one assigned
by my router), it does nothing -- just drops down one line, as if
waiting for me to type something in, but doesn't actually allow
anything to be typed in, responding only to Ctl-C. -h works and -V
works but help does not (apparently that is on the server).

So apparently it is not connecting. I guess my next test is to write a
cmd file to set the environment variables.

[Frank Beythien]

Am 27.01.2012 19:58, schrieb Paul S. Person:
> On Thu, 26 Jan 2012 20:43:03 +0100, Frank Beythien <fbey...@gmx.de>
> wrote:
>
>> Try (worked for me in June 2011)
>>
>> ftp://ftp.perforce.com/perforce/r02.2/bin.os2/p4.exe
>
> As I noted, I tried it but it just sits there, Even when pointed
> explicitly at the same IP address that ping is using (the one assigned
> by my router), it does nothing -- just drops down one line, as if
> waiting for me to type something in, but doesn't actually allow
> anything to be typed in, responding only to Ctl-C. -h works and -V
> works but help does not (apparently that is on the server).
>
> So apparently it is not connecting. I guess my next test is to write a
> cmd file to set the environment variables.

You need to set some envvars. My commands look like:

Modify p4set.cmd with your values.

--- p4set.cmd
@echo off
@echo Setup environment variables for Perforce + p4 sync
set path=E:\p4;%path%
set P4PORT=perforce.openwatcom.org:3488
set P4USER=xxx
set P4CLIENT=yyy
set P4PASSWD=zzz
set P4Editor=e:\x2\x.exe
set l=2^>^&1^|tee -a p4.log
call p4h.cmd
@echo on
@call p4sl.cmd

--- p4h.cmd just to remember some cmds
@echo off
echo file with path: bld/...
echo p4 describe chno -- changes of this changeno
echo p4 annotate -a file -- print file with revisions + deleted
echo p4 changes file -- changenos for file
echo p4 revert file -- rollback changes for file
echo p4 counters -- highest changeno e.a.
echo p4s -- p4 sync -- sync
echo p4sl -- p4 sync -- sync using tee
echo p4sub -- revert -a + submit

--- p4sl.cmd
@call p4s.cmd %1 %2 %3 %4 %5 %l%

--- p4s.cmd
/* REXX execute sync command and output duration*/
parse arg a
bef=strip("p4 sync" a)
/* say "'"bef"'"*/
/* start=time() */
/* say "Anf" start*/
rr=time("E")
address cmd "@"bef
dauer=time("E")
say format(dauer,8,2) "Sek " time() date("S") "'"bef"'"

--- p4sub.cmd
p4 revert -a
p4 submit %1 %2 %3 %4 %5 %6 %7 %8 %9

Paul, I hope this gets you going!

[Paul S. Person]

On Wed, 25 Jan 2012 16:40:14 +0100, "Johannes" <JDie...@t-online.de>
wrote:

>The latest Windows Version which work's with the Server is "P4 Client 2010
>Dezember 01 (Rev. Perforce Visual Client/NTX86/2010.1/276058)"
>Newer P4 Version need a newer Server Version.

I downloaded and installed the latest-and-greatest p4 (command line
client) and P4V.

The command-line client appears to have no problems.

P4V, in contrast, clearly states:

Only 2006.2 or later servers supported by P4V.

Which clearly verifies your report, so far af P4V is concerned.

[Paul S. Person]

On Fri, 27 Jan 2012 20:38:51 +0100, Frank Beythien <fbey...@gmx.de>

wrote:

>Am 27.01.2012 19:58, schrieb Paul S. Person:
>> On Thu, 26 Jan 2012 20:43:03 +0100, Frank Beythien <fbey...@gmx.de>
>> wrote:
>>
>>> Try (worked for me in June 2011)
>>>
>>> ftp://ftp.perforce.com/perforce/r02.2/bin.os2/p4.exe
>>
>> As I noted, I tried it but it just sits there, Even when pointed
>> explicitly at the same IP address that ping is using (the one assigned
>> by my router), it does nothing -- just drops down one line, as if
>> waiting for me to type something in, but doesn't actually allow
>> anything to be typed in, responding only to Ctl-C. -h works and -V
>> works but help does not (apparently that is on the server).
>>
>> So apparently it is not connecting. I guess my next test is to write a
>> cmd file to set the environment variables.
>
>You need to set some envvars. My commands look like:
>
>Modify p4set.cmd with your values.

Later on, while working on wgml, I had an idea, and popped up the
Windows Firewall and opened port 3488 (on the LAN only).

This was not enough. I actually copied the batch file I am using under
Windows 7 Starter and edited it to produce a p4set.cmd on the OS/2
machine. Running that allowed me to connect to OW's server, albeit as
my Windows 7 client.

OK, now I can connect to the server, I presume: p4 info produces the
usual response (server version, licence, user name, cleint info, etc,
etc.

Is this enough or do I really need to set up my local server with its
own repository, accounts, etc, etc? Keep in mind that the whole
purpose of this exercise is to see if the OS/2 client will work with
the latest-and-greatest Perforce server (2011.1); what further tests
would be needed to be certain this works?

[Frank Beythien]

From the perforce knowledge base

http://kb.perforce.com/article/46/upgrading-a-perforce-server

------------------------------
Upgrading from earlier versions

If you are upgrading the Perforce server from a release prior to 2001.1,
there may be additional considerations. To ensure a successful upgrade
from releases prior to 2001.1, please send an email to sup...@perforce.com.

Remote depot support requires all your Perforce Servers to use release
98.2 or later. 2005.1 and later servers can be used as remote depots
from only 99.2 and later servers.

For upgrades to release 2005.1 and later, p4 verify -u must be run at
least once following the upgrade to generate file length data for any
files in your depot before the upgrade. For more information, see:
Important Notes for 2005.1 and later.

For upgrades to release 2009.2 and later, note that Perforce type
unicode files can no longer be submitted to a non-Unicode enabled
Perforce Server. For details, see: Unicode File Type Handling Changes In
2009.2.

In general, older Perforce client programs (p4, P4V, and P4SCC) work
with newer server versions with no trouble. Please note, however, that
legacy products (for example, P4DTI) and maintenance mode products (for
example, P4Win) are not guaranteed to work with newer server versions.
Some features in a new server release require a client upgrade to access
the new features; users with older client programs cannot use such features.
--------------------------

So, it looks a test with P4 sync, submit, ... against the new server
could show whether a P4 2002.2 OS/2 client still works with it.

But even if this doesn't work any more, I have other solutions:
Use a client from a supported platform.

a) Linux and then fiddle with the CR CRLF line endings when copying
between Linux / OS/2.
b) Win xx.

[Paul S. Person]

On Sun, 29 Jan 2012 10:48:33 +0100, Frank Beythien <fbey...@gmx.de>
wrote:

>Am 28.01.2012 19:58, schrieb Paul S. Person:

<snippo>

>> OK, now I can connect to the server, I presume: p4 info produces the
>> usual response (server version, licence, user name, cleint info, etc,
>> etc.
>>
>> Is this enough or do I really need to set up my local server with its
>> own repository, accounts, etc, etc? Keep in mind that the whole
>> purpose of this exercise is to see if the OS/2 client will work with
>> the latest-and-greatest Perforce server (2011.1); what further tests
>> would be needed to be certain this works?

<snippo>

>In general, older Perforce client programs (p4, P4V, and P4SCC) work
>with newer server versions with no trouble. Please note, however, that
>legacy products (for example, P4DTI) and maintenance mode products (for
>example, P4Win) are not guaranteed to work with newer server versions.
>Some features in a new server release require a client upgrade to access
>the new features; users with older client programs cannot use such features.

That is, I suggest, generally to be expected: older clients are not
aware of and so cannot be expected to use newer features.

>So, it looks a test with P4 sync, submit, ... against the new server
>could show whether a P4 2002.2 OS/2 client still works with it.

Well, I got started: made the cmd files more robust, set up the
directories, used P4Win to create a user for the test (I'll need to
use p4 to do the same for the OS/2 test). Unfortunately, p4d then
failed to respond to the -r option (which may be a good thing, I'm not
sure it is needed or appropriate) and, although I defined and
populated the server's depot, it doesn't recognize the files in it.
This may be related to the problems found when I first used p4 and P4V
under Windows 7 Starter. It may be that P4Win isn't releasing its hold
on port 3488.

I'll work on this again. Anybody out there know how to add contents to
a depot under Perforce? Or how to hide/remove the default depot so I
only see the one I create somewhere else? The guide I downloaded is
remarkably uninformative, being far more interested in more obscure
topics than mere basic setup (it, however, quite well written and
should be very useful to those interested in those topics).

>But even if this doesn't work any more, I have other solutions:
>Use a client from a supported platform.
>
>a) Linux and then fiddle with the CR CRLF line endings when copying
>between Linux / OS/2.

Or maybe not.

The "relnotes.txt" file in perforce20022.zip, when displayed by
Notepad under XP, shows a complete lack of line ends.

But under OS/2 the lines end just fine. It is, then, possible that
OS/2 (System Editor) handles this situation correctly.

>b) Win xx.

p4, itself, isn't very large (960 KB). Of course, the installer may
install other stuff; it will install the server if you don't tell it
not to (you want a red "X" for everything except the client).

[Paul S. Person]

On Sun, 29 Jan 2012 10:20:24 -0800, Paul S. Person
<pspe...@ix.netscom.com.invalid> wrote:

>Well, I got started: made the cmd files more robust, set up the
>directories, used P4Win to create a user for the test (I'll need to
>use p4 to do the same for the OS/2 test). Unfortunately, p4d then
>failed to respond to the -r option (which may be a good thing, I'm not
>sure it is needed or appropriate) and, although I defined and
>populated the server's depot, it doesn't recognize the files in it.
>This may be related to the problems found when I first used p4 and P4V
>under Windows 7 Starter. It may be that P4Win isn't releasing its hold
>on port 3488.

I barely submitted this when the correct approach occurred to me (you
don't put files into the server depot, you put them into a client
depot and add them to the server depot) and, after some testing, I
managed, with the 2011.1 server,

1) set up clients for both P4Win on XP and p4 on OS/2
2) add files from the P4Win Client depot to the 2011.1 server depot
3) hide the default depot (removed the mapping from the client)
4) modify a file under OS/2, submit it, and sync it with P4Win
5) modify a file under P4Win, submit it, and sync it with p4 on OS/2

I had to copy the OS/2 version of vi from rel2 so that p4 could launch
it to add the temporary files it uses. Interestingly, when I use
P4Win, I can /select/ the OS/2 Client but I cannot /work/ with it: I
am told I have to be working from the raw IP address of my OS/2
computer. That's sounds perfectly reasonable to me.

I /think/ that should be enough. Anybody have any more tests that
should be done to be certain that P4Win and the OS/2 p4 command-line
client will work with the 2011.1 server? I did not give my User a
password; do I need to test that?

[Peter C. Chapin]

On 2012-01-29 14:35, Paul S. Person wrote:

> I /think/ that should be enough. Anybody have any more tests that
> should be done to be certain that P4Win and the OS/2 p4 command-line
> client will work with the 2011.1 server? I did not give my User a
> password; do I need to test that?

Thanks for your work on this. And thanks also to Frank for locating that
page on the Perforce web site about upgrading the server. The procedure
does not look too difficult and it should probably be done in the
somewhat near future.

Peter

[Frank Beythien]

Am 29.01.2012 20:35, schrieb Paul S. Person:

> 1) set up clients for both P4Win on XP and p4 on OS/2
> 2) add files from the P4Win Client depot to the 2011.1 server depot
> 3) hide the default depot (removed the mapping from the client)
> 4) modify a file under OS/2, submit it, and sync it with P4Win
> 5) modify a file under P4Win, submit it, and sync it with p4 on OS/2

Great!

> I had to copy the OS/2 version of vi from rel2 so that p4 could launch
> it to add the temporary files it uses. Interestingly, when I use
> P4Win, I can /select/ the OS/2 Client but I cannot /work/ with it: I
> am told I have to be working from the raw IP address of my OS/2
> computer. That's sounds perfectly reasonable to me.

I think that is an option for p4 client: restrict access to a specific
host, editing the client and deleting the host: xxxx line should allow
access from other computers or VMs.