This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: Win2003 periodic failures
- From: "Allan Yates" <allan dot yates at signiant dot com>
- To: <cygwin at cygwin dot com>
- Date: Wed, 25 Jun 2003 13:23:02 -0400
- Subject: RE: Win2003 periodic failures
This is definitely the string coming out. Performing a 'strings' on the
DLL shows this 'dynamically determine load address' error message,
though with a %s for the actual module name.
Win 2003 is released. If you have enough money - Microsoft will be happy
to sell it to you :)
Thanks,
Allan.
-----Original Message-----
From: Christopher Faylor [mailto:cgf-rcm@cygwin.com]
Sent: Wednesday, June 25, 2003 12:05 PM
To: cygwin@cygwin.com
Subject: Re: Win2003 periodic failures
On Wed, Jun 25, 2003 at 03:21:21PM +0100, Elfyn McBratney wrote:
>On Wed, 25 Jun 2003, Allan Yates wrote:
>>I have been running Cygwin on WinNT and Win2000 platforms with no
>>issues for a year or so. I recently installed the latest (1.3.22-1)
>>version on a Win2003 machine. Running the same code (very simple
shell
>>scripts) I am see the following error 12-25% of the time:
>>
>>couldn't dynamically determine load address for RegCreateKeyUxA'
>>(handle 0x77DA0000), Win32 error 127
>>
>>Searches of the Cygwin archive and Google came up negative.
>>
>>Has anybody seen this before? Or is there a specific version of
Cygwin
>>for Win2003 that I haven't found yet?
>
>I think this means that RegCreateKeyUxA is no longer exported or
>supported (in Windows 2003).
I don't know why cygwin would be loading something called
RegCreateKeyUxA. It
certainly isn't intentional. It should be using RegCreateKeyExA. I
can't find
any reference to the UxA version anywhere in the source.
Has Windows 2003 been officially released? If not, this falls into the
"only works
on non-beta versions of Windows" category.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/