From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tsuyoshi Tada To: cygwin@sourceware.cygnus.com Subject: Re: Cywgin + XEmacs + Tcsh: error messages. Date: Wed, 31 Mar 1999 19:45:00 -0000 Message-ID: <19990308121359I.tsuyoshi_tada@ihi.co.jp> References: <19990303153208.10413.rocketmail@send101.yahoomail.com> X-SW-Source: 1999-03n/msg00210.html Message-ID: <19990331194500.n9rkJDtuJ0zYuHbttjNVeQ_AFCLa778GzV5o7MWfSrE@z> Earnie Boyd wrote: > ---Tsuyoshi Tada wrote: > 8< > > 733k 1999/02/17 C:\usr\cygwin-b20\H-i586-cygwin32\bin\cygwin1.dll > - os=4.0 img=1.0 sys=4.0 > > "cygwin1.dll" v0.0 ts=1999/2/17 10:48 > > 733k 1999/02/17 C:\usr\local\bin\cygwinb19.dll - os=4.0 img=1.0 > sys=4.0 > > "cygwin1.dll" v0.0 ts=1999/2/17 10:48 > 8< > > Do you need the copy of cygwinb19.dll? Although it was reported to be > safe I've seen occasions where it did cause problems. I suggest > renaming the cygwinb19.dll to see if it is getting in the way. If > you're still using binaries that require it then use a binary editor > to change the occurrence of cygwinb19.dll in the .exe to > cygwin1.dll being careful not to change the length of the > file. I removed cygwinb19.dll temporally and restarted my system, but it didn't solve the problem. Since the cygwinb19.dll on my system is the exact copy of the recent cygwin1.dll I made from snapshot source, I think it doesn't have to do with the problem. -- Tsuyoshi TADA Advanced Launch Vehicle Development Group Space Development Division, IHI Tel: 042-568-7875 Fax: 042-568-7575 -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com