Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3A1310D1.6B1FCFF2@lineo.com> Date: Wed, 15 Nov 2000 14:40:17 -0800 From: jfaith AT lineo DOT com X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en,ja MIME-Version: 1.0 To: Scott Wallace CC: cygwin AT cygwin DOT com Subject: Re: Error: Initializing USER32.dll References: X-MIMETrack: Itemize by SMTP Server on lnseat/Lineo(Release 5.0.5 |September 22, 2000) at 11/15/2000 02:42:37 PM, Serialize by Router on lnseat/Lineo(Release 5.0.5 |September 22, 2000) at 11/15/2000 02:43:10 PM, Serialize complete at 11/15/2000 02:43:10 PM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sometimes problems loading DLLs are due to missing symbols or mismatched DLL, DLL/EXE versions. One way to see if this is the case is to use Dependency Walker (http://www.dependencywalker.com/). It will show you if an executable cannot find a DLL, or if a required entry point in a DLL is missing. Also, what path is being used for inetd? For debugging purposes, I wonder if you could wrap inetd in a script to "echo %PATH% > tmpFile" before running inetd? -- John Faith Lineo Scott Wallace wrote: > Both "advapi32.dll and user32.dll are in c:\WINNT\system32 and that is in my > path. Any other ideas? > > thanks, > Scott > > -----Original Message----- > From: cygwin-owner AT sources DOT redhat DOT com > [mailto:cygwin-owner AT sources DOT redhat DOT com]On Behalf Of Larry Hall (RFK > Partners, Inc) > Sent: Wednesday, November 15, 2000 2:21 PM > To: Scott Wallace; cygwin AT cygwin DOT com > Subject: Re: Error: Initializing USER32.dll > > At 03:13 PM 11/15/2000, Scott Wallace wrote: > >Hello everyone, > > I've searched the archives and found no answer to this, so... > >I have Cygwin setup on a WinNT 4.0 Workstation as well as Exceed. When I > >telnet into the NT box and get a command prompt and attempt to run any > >Cygwin app (even an 'ls') it locks at the client side. At the NTW side, it > >has brought up an error box saying: > > > >Initialization of the dynamic lynk library C:\WINNT\system32\USER32.dll > >failed. The process is terminating abnormally. > > > >(Here's a pic of it: http://swallace.iol-12.net/error.gif) > >Then when I click OK on that error box and go back to my client telnet > >session, it has given the following error: > > > >C:\WINNT\system32>ls > >D:\cygwin\bin\ls.exe: *** could not load advapi32.dll, Win32 error 1114 > > 0 [unknown (0x161)] ? 0 lock_pinfo_for_update: rc 0, pinfo_mutex > >0xFFFFFFF > >F, Win32 error 6 > > > >Any idea how to fix this? It only does this on certain usernames. I tried > >creating a new user at the Domain controller and connecting through the > >telnet session as that user, but still had the same results. I don't know > >what makes some logins work and others not. > > > >Thank you for any help you can give! > >Scott Wallace > >Ternion Corporation > >saw AT ternion DOT com > > Sounds like your telnet session doesn't have these DLLs in the path... > -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com