[Cvsnt] CVS.EXE Incompatibility with Win2K?
Gates, Donald T
DONALD.T.GATES at saic.com
Wed Mar 13 16:12:43 GMT 2002
>From: Brian Smith <brian-l-smith at uiowa.edu>
>Subject: Re: [Cvsnt] Path Length Problem with CVS.EXE or WS2HELP.DLL
>Date: Tue, 12 Mar 2002 19:24:41 -0600
>Organization: cvsnt.org news server
>To: cvsnt at cvsnt.org
>I just tried it with a working directory of:
>And it seems like it is working fine. I am using Windows 2000 SP2 and
>the 18.104.22.168 beta. Looking up "WahReferenceContextByHandle" and
>WS2HELP.DLL on Usenet indicates that this is a problem with Windows NT
>4.0 prior to service pack 6 and occurs with many network-enabled
>applications. What version of Windows are you using?
Windows 2000 SP2 workstation and server (with all other current applicable
And path length doesn't appear to be the problem.
Interesting to note (don't know if it matters), but the WS2HELP.DLL I have
is dated 12/7/1999, version number 5.0.2134.1.
Also, this morning on SearchWin2000 I found this article,
which would seem to suggest that cvs.exe is not 100% compatible with Win2K.
The pertinent part of the article is below:
Many .DLLs depend on function calls in the kernel (that's what the error
message refers to as a "procedure entry point") to accomplish certain tasks.
Some of these functions exist only in specific versions of Windows, such as
Windows 98 or Windows Me. In Windows 2000, these "missing" functions may be
rolled into other functions, or may simply not exist. The .DLL usually has
no way of knowing this and will simply put the call through, yielding this
error. The SetHandleContext() API is one such function call.
Generally this happens when an application is written and compiled for
Windows 9x, without proper regard for compatibility with other versions of
Windows. In some instances this is unavoidable, but generally speaking, it
is possible to write the vast majority of generic applications to run
transparently on all 32-bit versions of Windows. Often what will happen is a
.DLL written specifically for another version of Windows will come packaged
with a particular application, and the installer will not correctly sense
that the host OS requires a different edition of the DLL. Many games written
for Win98 will yield this error when run on Win2K, and some network
applications written for Win98 will also return it if they came bundled with
an older version of Winsock.DLL.
The solution is usually to find an upgraded version of the program that is
written to run on Win2K as well as Win98, or to replace the offending .DLL,
making the function call with one that works with Win2K APIs.
Cvsnt mailing list
Cvsnt at cvsnt.org
More information about the cvsnt