Hi,
while installing cygwin using setup.exe and set http proxy-name and
port. Re-running setup later remember all my settings from the first
session but the proxy port is set to 80 and I always have to enter the
correct port number manually.
Best regards.
--
Unsubscribe info: http://cygwin
Hi,
I just installed the default Cygwin components using the latest
setup.exe from a local install directory. The target machine runs
WinXP SP2 English with German MUI pack. The installation as local
administrator via setup.exe did not show any errors. The computer is
only a workgroup member and
On 7/14/07, Stephen Barclay <[EMAIL PROTECTED]> wrote:
Probably a type on the OP's part but...
mkpasswd -l > /etc/passwd
*mkgroup -l > /etc/passwd
*
Shouldn't the above be mkgroup -i > /etc/groups ???
What do you think shall -i do? For me there is no -i option in mkgroup:
$ mkgroup -i
mkgrou
On 7/14/07, Christopher Faylor
<[EMAIL PROTECTED]> wrote:
On Sat, Jul 14, 2007 at 07:07:15AM -0500, Ren? Berber wrote:
>Bernd Bartmann wrote:
>
>> On 7/14/07, Stephen Barclay <[EMAIL PROTECTED]> wrote:
>>> Probably a type on the OP's part but...
>>>
On 7/15/07, Dave Korn <[EMAIL PROTECTED]> wrote:
On 13 July 2007 19:12, Bernd Bartmann wrote:
> Now comes the weird part. I created a new file hello.c in my home dir
> with vim. ls -al shows that the file exists, but "more hello.c" gives
> no output at all. I just ge
On 7/16/07, Dave Korn wrote:
Bernd, please abide by the list etiquette of not quoting people's email
addresses in the raw, as they end up on the web archive and get harvested by
spammers. (See http://cygwin.com/acronyms#PCYMTNQREAIYR for justification).
Dave, thanks for the hint. I'll try to
On 7/16/07, Dave Korn wote:
Well, the first thing to do is check whether libintl3 is there in the
downloaded packages directory. It should be in
//release/gettext/libintl3, and the md5sum of it
should match what's listed in the related setup.ini in
/. If that's the case, no need to redownload;
Hi,
I just updated my old cygwin installation to the new version 1.7.1.
I'm running it on a German WinXP SP3. The installation process went
without any problem or error message, but now if I try to start cygwin
using the desktop icon a command window appears for a short time and
then goes away aga
> That may be the symptom of two different versions of the DLL existing on
> your system.
>
> See: http://cygwin.com/problems.html for more information on how to track
> down Cygwin problems.
Ok, one step closer but still no go. There was indeed a second version
of the cygwin dll in the default se
On Sun, Dec 27, 2009 at 12:35 AM, Christopher Faylor
wrote:
> What happens if you just
>
> cd c:\cygwin\bin
> .\bash
>
> In a command shell?
After starting a cmd window I get:
C:\> cd cygwin\bin
C:\cygwin\bin> .\bash
C:\cygwin\bin>
So after trying to start bash I just get back to the cmd comman
On Sun, Dec 27, 2009 at 4:19 PM, Christopher Faylor
wrote:
> What does:
>
> c:\cygwin\bin\cygcheck c:\cygwin\bin\bash.exe
>
> show? It will probably show that you're missing some basic dlls
> which, for some reason, will need to be (re)installed.
>
> You can find the packages which hold the missi
On Sun, Dec 27, 2009 at 6:56 PM, Andy Koppe wrote:
> Except for cygwin1.dll of course. Try reinstalling the cygwin package
> itself as well.
Reinstalling cygwin-1.7.1-1 doesn't help either.
Best regards,
Bernd.
--
Problem reports: http://cygwin.com/problems.html
FAQ: htt
On Mon, Dec 28, 2009 at 11:30 AM, Bernd Bartmann wrote:
> On Mon, Dec 28, 2009 at 12:31 AM, Christopher Faylor
> wrote:
>> I'd suggest at this point that you run sysinternals procmon to see if
>> you can figure out why bash isn't starting. You might also try running
Obviously my last post didn't make it through the mailing list
probably because of a .csv attachment. So, here's the original text
again:
Setting the PATH to C:\cygwin\bin only doesn't help either. So I tried
procmon to monitor what bash is actually doing. As it seems it stops
because it can't fin
On Tue, Dec 29, 2009 at 6:05 PM, Dave Korn wrote:
> We have a suspect:
>
>> "11:09:08,3362588","bash.exe","3396","CreateFileMapping","C:\Programme\BitDefender\BitDefender
>> 2010\Active Virus Control\midas32-v2_58\PLUGIN_NT.M32","SUCCESS","SyncType:
>> SyncTypeOther"
>
> That's listed on BLODA.
On Tue, Dec 29, 2009 at 7:08 PM, Dave Korn wrote:
> Take a look in /etc/postinstall. If you see lots of files named "*.sh",
> then you can simply re-run setup.exe and click right through it without
> changing any of the settings from last time and it will finish off running any
> scripts that it
16 matches
Mail list logo
