public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* cygwin64 - installation problem - installed by administrator account
@ 2014-01-27  6:29 Flower, Martin
  2014-01-27 20:56 ` Larry Hall (Cygwin)
  0 siblings, 1 reply; 12+ messages in thread
From: Flower, Martin @ 2014-01-27  6:29 UTC (permalink / raw)
  To: cygwin

Please excuse my newby-ignorance, but I can't work out how to progress this without some help

Steps taken
- Downloaded setup-x86_64.exe
- Run setup-x86_64.exe using admflma (administrator account)
- Logged in as netflma (my usual windows login)
- Unable to start Cygwin from desktop icon 
  - unable to find mintty.exe
- Able to start Cygwin from command line
  - (C:\cygwin64\Cygwin.bat)
- Error message is Your group is currently "mkpasswd" .. ..
- mkpasswd -l  > /etc/passwd
  - bash: /etc/passwd: Permission denied
- drwxr-xr-x+ 1 admflma mkpasswd      0 22 jan 13.39 etc
- If I run the console as user admflma, then no errors are reported
- Log in to windows as admflma and start Cygwin from desktop icon
  - unable to find mintty.exe
- The objective is that any user on the computer can run Cygwin, but particularly netflma (user without admin rights)
- My guess is that the windows permissions are wrong for C:\cygwin64. I have attempted to give all rights to all users, but this has not solved the problem

/Martin


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: cygwin64 - installation problem - installed by administrator account
  2014-01-27  6:29 cygwin64 - installation problem - installed by administrator account Flower, Martin
@ 2014-01-27 20:56 ` Larry Hall (Cygwin)
  2014-01-28  0:55   ` Mark Geisert
  0 siblings, 1 reply; 12+ messages in thread
From: Larry Hall (Cygwin) @ 2014-01-27 20:56 UTC (permalink / raw)
  To: cygwin

On 1/27/2014 1:29 AM, Flower, Martin wrote:
> Please excuse my newby-ignorance, but I can't work out how to progress
> this without some help
>
> Steps taken
> - Downloaded setup-x86_64.exe
> - Run setup-x86_64.exe using admflma (administrator account)
> - Logged in as netflma (my usual windows login)
> - Unable to start Cygwin from desktop icon
>    - unable to find mintty.exe
> - Able to start Cygwin from command line
>    - (C:\cygwin64\Cygwin.bat)
> - Error message is Your group is currently "mkpasswd" .. ..
> - mkpasswd -l  > /etc/passwd
>    - bash: /etc/passwd: Permission denied
> - drwxr-xr-x+ 1 admflma mkpasswd      0 22 jan 13.39 etc
> - If I run the console as user admflma, then no errors are reported
> - Log in to windows as admflma and start Cygwin from desktop icon
>    - unable to find mintty.exe
> - The objective is that any user on the computer can run Cygwin, but
>   particularly netflma (user without admin rights)
> - My guess is that the windows permissions are wrong for C:\cygwin64. I
>    have attempted to give all rights to all users, but this has not
>   solved the problem

Can you *attach* the output of 'cygrunsrv -srv' to a follow-up
mail with the output of 'id'?


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: cygwin64 - installation problem - installed by administrator account
  2014-01-27 20:56 ` Larry Hall (Cygwin)
@ 2014-01-28  0:55   ` Mark Geisert
  2014-02-04  7:43     ` Flower, Martin
  0 siblings, 1 reply; 12+ messages in thread
From: Mark Geisert @ 2014-01-28  0:55 UTC (permalink / raw)
  To: cygwin

> Can you *attach* the output of 'cygrunsrv -srv' to a follow-up
> mail with the output of 'id'?

That should read 'cygcheck -srv'.  Everything else still applies.

..mark


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 12+ messages in thread

* cygwin64 - installation problem - installed by administrator account
  2014-01-28  0:55   ` Mark Geisert
@ 2014-02-04  7:43     ` Flower, Martin
  2014-02-04 14:25       ` Larry Hall (Cygwin)
  0 siblings, 1 reply; 12+ messages in thread
From: Flower, Martin @ 2014-02-04  7:43 UTC (permalink / raw)
  To: cygwin

[-- Attachment #1: Type: text/plain, Size: 846 bytes --]

C:\cygwin64\bin>cygcheck -srv > cygcheck.text

C:\cygwin64>Cygwin.bat
$ id
uid=400(netflma) gid=401(mkpasswd) grupper=401(mkpasswd),555(Remote Desktop Users),545(Users),10513(Domain Users)

Hope this is what you have asked for.

/Martin


-----Original Message-----
From: cygwin-owner 
Sent: Tuesday, January 28, 2014 1:55 AM
To: cygwin
Subject: Re: cygwin64 - installation problem - installed by administrator account

> Can you *attach* the output of 'cygrunsrv -srv' to a follow-up mail 
> with the output of 'id'?

That should read 'cygcheck -srv'.  Everything else still applies.

..mark


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


[-- Attachment #2: cygcheck.text --]
[-- Type: application/octet-stream, Size: 15290 bytes --]


Cygwin Configuration Diagnostics
Current System Time: Tue Jan 28 10:15:41 2014

Windows 7 Enterprise Ver 6.1 Build 7601 Service Pack 1

Path:	c:\tools\Java\jdk1.7.0_45\bin
	C:\WINDOWS\system32
	C:\WINDOWS
	C:\WINDOWS\System32\Wbem
	C:\WINDOWS\System32\WindowsPowerShell\v1.0\
	c:\tools\ant\apache-ant-1.9.1\bin
	c:\Users\netflma\bin
	c:\tools\groovy-2.2.1\bin
	c:\tools\gradle-1.10\bin
	c:\tools\apache-maven-3.1.1\bin
	c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\
	c:\Program Files\Microsoft SQL Server\100\Tools\Binn\
	c:\Program Files\Microsoft SQL Server\100\DTS\Binn\
	c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\
	c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\
	c:\tools\Java\jdk1.7.0_45\bin
	C:\WINDOWS\system32
	C:\WINDOWS
	C:\WINDOWS\System32\Wbem
	C:\WINDOWS\System32\WindowsPowerShell\v1.0\
	c:\tools\ant\apache-ant-1.9.1\bin
	c:\Users\netflma\bin
	c:\tools\groovy-2.2.1\bin
	c:\tools\gradle-1.9\bin
	c:\tools\apache-maven-3.1.1\bin
	C:\Tools\Git\cmd
	C:\Tools\Git\bin

Output from C:\cygwin64\bin\id.exe
UID: 400(netflma)         GID: 401(mkpasswd)
401(mkpasswd)             555(Remote Desktop Users) 545(Users)
10513(Domain Users)

SysDir: C:\WINDOWS\system32
WinDir: C:\WINDOWS

HOME = 'C:\Users\netflma'
Path = 'c:\tools\Java\jdk1.7.0_45\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;c:\tools\ant\apache-ant-1.9.1\bin;c:\Users\netflma\bin;c:\tools\groovy-2.2.1\bin;c:\tools\gradle-1.10\bin;c:\tools\apache-maven-3.1.1\bin;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;c:\tools\Java\jdk1.7.0_45\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;c:\tools\ant\apache-ant-1.9.1\bin;c:\Users\netflma\bin;c:\tools\groovy-2.2.1\bin;c:\tools\gradle-1.9\bin;c:\tools\apache-maven-3.1.1\bin;C:\Tools\Git\cmd;C:\Tools\Git\bin'

ALLUSERSPROFILE = 'C:\ProgramData'
ANT_HOME = 'c:\tools\ant\apache-ant-1.9.1'
APPDATA = 'C:\Users\netflma\AppData\Roaming'
CommonProgramFiles = 'C:\Program Files\Common Files'
CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files'
CommonProgramW6432 = 'C:\Program Files\Common Files'
COMPUTERNAME = 'SENWK-D-57CTM'
ComSpec = 'C:\WINDOWS\system32\cmd.exe'
FP_NO_HOST_CHECK = 'NO'
GRADLE_HOME = 'c:\tools\gradle-1.10'
GROOVY_HOME = 'c:\tools\groovy-2.2.1'
HOMEDRIVE = 'C:'
HOMEPATH = '\Users\netflma'
JAVA_HOME = 'c:\tools\Java\jdk1.7.0_45'
LOCALAPPDATA = 'C:\Users\netflma\AppData\Local'
LOGONSERVER = '\\SENWK-VS-DC01'
M2_HOME = 'c:\tools\apache-maven-3.1.1'
NUMBER_OF_PROCESSORS = '8'
OS = 'Windows_NT'
PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC'
PROCESSOR_ARCHITECTURE = 'AMD64'
PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 60 Stepping 3, GenuineIntel'
PROCESSOR_LEVEL = '6'
PROCESSOR_REVISION = '3c03'
ProgramData = 'C:\ProgramData'
ProgramFiles = 'C:\Program Files'
ProgramFiles(x86) = 'C:\Program Files (x86)'
ProgramW6432 = 'C:\Program Files'
PROMPT = '$P$G'
PSModulePath = 'C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\'
PUBLIC = 'C:\Users\Public'
SecSpecialMode = '710916'
SESSIONNAME = 'Console'
SystemDrive = 'C:'
SystemRoot = 'C:\WINDOWS'
TEMP = 'C:\Users\netflma\AppData\Local\Temp'
TMP = 'C:\Users\netflma\AppData\Local\Temp'
UATDATA = 'C:\WINDOWS\CCM\UATData\D9F8C395-CAB8-491d-B8AC-179A1FE1BE77'
USERDNSDOMAIN = 'PAPYRUS.LAN'
USERDOMAIN = 'PAPYRUS'
USERNAME = 'netflma'
USERPROFILE = 'C:\Users\netflma'
windir = 'C:\WINDOWS'
windows_tracing_flags = '3'
windows_tracing_logfile = 'C:\BVTBin\Tests\installpackage\csilogfile.log'

HKEY_CURRENT_USER\Software\Cygwin
HKEY_CURRENT_USER\Software\Cygwin\Installations
  (default) = '\??\C:\cygwin64'
HKEY_CURRENT_USER\Software\Cygwin\Program Options
HKEY_CURRENT_USER\Software\Cygwin\setup
  (default) = 'C:\cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
  (default) = '\??\C:\cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup
  (default) = 'C:\cygwin64'

obcaseinsensitive set to 1

Cygwin installations found in the registry:
  System: Key: e022582115c10879 Path: C:\cygwin64
  User:   Key: e022582115c10879 Path: C:\cygwin64

c:  hd  NTFS    243895Mb  30% CP CS UN PA FC     OSDisk
d:  cd             N/A    N/A                    
g:  net NTFS   1228792Mb  94% CP CS UN PA FC     SAN
h:  net NTFS   1228792Mb  94% CP CS UN PA FC     SAN
r:  net NTFS   1228792Mb  94% CP CS UN PA FC     SAN

C:\cygwin64      /          system  binary,auto
C:\cygwin64\bin  /usr/bin   system  binary,auto
C:\cygwin64\lib  /usr/lib   system  binary,auto
cygdrive prefix  /cygdrive  user    binary,posix=0,auto

Found: C:\Tools\Git\bin\awk
Found: C:\Tools\Git\bin\bash.exe
Found: C:\Tools\Git\bin\cat.exe
Found: C:\Tools\Git\bin\cp.exe
Not Found: cpp (good!)
Not Found: crontab
Found: C:\WINDOWS\system32\find.exe
Found: C:\WINDOWS\system32\find.exe
Found: C:\Tools\Git\bin\find.exe
Warning: C:\WINDOWS\system32\find.exe hides C:\Tools\Git\bin\find.exe
Not Found: gcc
Not Found: gdb
Found: C:\Tools\Git\bin\grep.exe
Found: C:\Tools\Git\bin\kill.exe
Not Found: ld
Found: C:\Tools\Git\bin\ls.exe
Not Found: make
Found: C:\Tools\Git\bin\mv.exe
Found: C:\Tools\Git\bin\patch.exe
Found: C:\Tools\Git\bin\perl.exe
Found: C:\Tools\Git\bin\rm.exe
Found: C:\Tools\Git\bin\sed.exe
Found: C:\Tools\Git\bin\ssh.exe
Found: C:\Tools\Git\bin\sh.exe
Found: C:\Tools\Git\bin\tar.exe
Not Found: test
Found: C:\Tools\Git\bin\vi
Found: C:\Tools\Git\bin\vim

   16k 2013/03/26 .\cygattr-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygattr-1.dll" v0.0 ts=2013-03-26 18:26
   64k 2013/03/07 .\cygbz2-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygbz2-1.dll" v0.0 ts=2013-03-07 03:54
   53k 2013/05/06 .\cygformw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygformw-10.dll" v0.0 ts=2013-05-06 09:10
   67k 2013/10/26 .\cyggcc_s-seh-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyggcc_s-seh-1.dll" v0.0 ts=2013-10-26 11:14
  443k 2013/10/12 .\cyggmp-10.dll - os=4.0 img=0.0 sys=5.2
                  "cyggmp-10.dll" v0.0 ts=2013-10-12 12:26
   29k 2013/03/14 .\cyghistory7.dll - os=4.0 img=0.0 sys=5.2
                  "cyghistory7.dll" v0.0 ts=2013-03-14 11:14
  998k 2013/03/07 .\cygiconv-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygiconv-2.dll" v0.0 ts=2013-03-07 04:03
   38k 2013/06/24 .\cygintl-8.dll - os=4.0 img=0.0 sys=5.2
                  "cygintl-8.dll" v0.0 ts=2013-06-24 05:36
    6k 2013/12/09 .\cyglsa64.dll - os=4.0 img=0.0 sys=5.2
                  "cyglsa64.dll" v0.0 ts=2013-12-09 11:53
  129k 2013/03/07 .\cyglzma-5.dll - os=4.0 img=0.0 sys=5.2
                  "cyglzma-5.dll" v0.0 ts=2013-03-07 11:20
  102k 2013/03/19 .\cygmagic-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygmagic-1.dll" v0.0 ts=2013-03-19 14:27
   28k 2013/05/06 .\cygmenuw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygmenuw-10.dll" v0.0 ts=2013-05-06 09:10
  319k 2013/05/05 .\cygmpfr-4.dll - os=4.0 img=0.0 sys=5.2
                  "cygmpfr-4.dll" v0.0 ts=2013-05-05 14:40
   52k 2013/05/06 .\cygncurses++w-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygncurses++w-10.dll" v0.0 ts=2013-05-06 09:14
  295k 2013/05/06 .\cygncursesw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygncursesw-10.dll" v0.0 ts=2013-05-06 09:08
   13k 2013/05/06 .\cygpanelw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygpanelw-10.dll" v0.0 ts=2013-05-06 09:09
  289k 2013/08/04 .\cygpcre-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygpcre-1.dll" v0.0 ts=2013-08-05 00:51
   41k 2013/10/21 .\cygpopt-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpopt-0.dll" v0.0 ts=2013-10-21 22:52
  193k 2013/03/14 .\cygreadline7.dll - os=4.0 img=0.0 sys=5.2
                  "cygreadline7.dll" v0.0 ts=2013-03-14 11:14
  892k 2013/10/26 .\cygstdc++-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygstdc++-6.dll" v0.0 ts=2013-10-26 10:01
   51k 2013/05/06 .\cygticw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygticw-10.dll" v0.0 ts=2013-05-06 09:08
   79k 2013/05/09 .\cygz.dll - os=4.0 img=0.0 sys=5.2
                  "cygz.dll" v0.0 ts=2013-05-09 23:20
 3072k 2013/12/09 .\cygwin1.dll - os=4.0 img=0.0 sys=5.2
                  "cygwin1.dll" v0.0 ts=2013-12-09 11:54
    Cygwin DLL version info:
        DLL version: 1.7.27
        DLL epoch: 19
        DLL old termios: 5
        DLL malloc env: 28
        Cygwin conv: 181
        API major: 0
        API minor: 271
        Shared data: 5
        DLL identifier: cygwin1
        Mount registry: 3
        Cygwin registry name: Cygwin
        Program options name: Program Options
        Installations name: Installations
        Cygdrive default prefix: 
        Build date: 
        Shared id: cygwin1S5

   16k 2013/03/26 C:\cygwin64\bin\cygattr-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygattr-1.dll" v0.0 ts=2013-03-26 18:26
   64k 2013/03/07 C:\cygwin64\bin\cygbz2-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygbz2-1.dll" v0.0 ts=2013-03-07 03:54
   53k 2013/05/06 C:\cygwin64\bin\cygformw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygformw-10.dll" v0.0 ts=2013-05-06 09:10
   67k 2013/10/26 C:\cygwin64\bin\cyggcc_s-seh-1.dll - os=4.0 img=0.0 sys=5.2
                  "cyggcc_s-seh-1.dll" v0.0 ts=2013-10-26 11:14
  443k 2013/10/12 C:\cygwin64\bin\cyggmp-10.dll - os=4.0 img=0.0 sys=5.2
                  "cyggmp-10.dll" v0.0 ts=2013-10-12 12:26
   29k 2013/03/14 C:\cygwin64\bin\cyghistory7.dll - os=4.0 img=0.0 sys=5.2
                  "cyghistory7.dll" v0.0 ts=2013-03-14 11:14
  998k 2013/03/07 C:\cygwin64\bin\cygiconv-2.dll - os=4.0 img=0.0 sys=5.2
                  "cygiconv-2.dll" v0.0 ts=2013-03-07 04:03
   38k 2013/06/24 C:\cygwin64\bin\cygintl-8.dll - os=4.0 img=0.0 sys=5.2
                  "cygintl-8.dll" v0.0 ts=2013-06-24 05:36
    6k 2013/12/09 C:\cygwin64\bin\cyglsa64.dll - os=4.0 img=0.0 sys=5.2
                  "cyglsa64.dll" v0.0 ts=2013-12-09 11:53
  129k 2013/03/07 C:\cygwin64\bin\cyglzma-5.dll - os=4.0 img=0.0 sys=5.2
                  "cyglzma-5.dll" v0.0 ts=2013-03-07 11:20
  102k 2013/03/19 C:\cygwin64\bin\cygmagic-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygmagic-1.dll" v0.0 ts=2013-03-19 14:27
   28k 2013/05/06 C:\cygwin64\bin\cygmenuw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygmenuw-10.dll" v0.0 ts=2013-05-06 09:10
  319k 2013/05/05 C:\cygwin64\bin\cygmpfr-4.dll - os=4.0 img=0.0 sys=5.2
                  "cygmpfr-4.dll" v0.0 ts=2013-05-05 14:40
   52k 2013/05/06 C:\cygwin64\bin\cygncurses++w-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygncurses++w-10.dll" v0.0 ts=2013-05-06 09:14
  295k 2013/05/06 C:\cygwin64\bin\cygncursesw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygncursesw-10.dll" v0.0 ts=2013-05-06 09:08
   13k 2013/05/06 C:\cygwin64\bin\cygpanelw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygpanelw-10.dll" v0.0 ts=2013-05-06 09:09
  289k 2013/08/04 C:\cygwin64\bin\cygpcre-1.dll - os=4.0 img=0.0 sys=5.2
                  "cygpcre-1.dll" v0.0 ts=2013-08-05 00:51
   41k 2013/10/21 C:\cygwin64\bin\cygpopt-0.dll - os=4.0 img=0.0 sys=5.2
                  "cygpopt-0.dll" v0.0 ts=2013-10-21 22:52
  193k 2013/03/14 C:\cygwin64\bin\cygreadline7.dll - os=4.0 img=0.0 sys=5.2
                  "cygreadline7.dll" v0.0 ts=2013-03-14 11:14
  892k 2013/10/26 C:\cygwin64\bin\cygstdc++-6.dll - os=4.0 img=0.0 sys=5.2
                  "cygstdc++-6.dll" v0.0 ts=2013-10-26 10:01
   51k 2013/05/06 C:\cygwin64\bin\cygticw-10.dll - os=4.0 img=0.0 sys=5.2
                  "cygticw-10.dll" v0.0 ts=2013-05-06 09:08
   79k 2013/05/09 C:\cygwin64\bin\cygz.dll - os=4.0 img=0.0 sys=5.2
                  "cygz.dll" v0.0 ts=2013-05-09 23:20
 3072k 2013/12/09 C:\cygwin64\bin\cygwin1.dll - os=4.0 img=0.0 sys=5.2
                  "cygwin1.dll" v0.0 ts=2013-12-09 11:54
    Cygwin DLL version info:
        DLL version: 1.7.27
        DLL epoch: 19
        DLL old termios: 5
        DLL malloc env: 28
        Cygwin conv: 181
        API major: 0
        API minor: 271
        Shared data: 5
        DLL identifier: cygwin1
        Mount registry: 3
        Cygwin registry name: Cygwin
        Program options name: Program Options
        Installations name: Installations
        Cygdrive default prefix: 
        Build date: 
        Shared id: cygwin1S5

Warning: There are multiple cygwin1.dlls on your path

Can't find the cygrunsrv utility, skipping services check.


Cygwin Package Information
Last downloaded files to: C:\Users\netflma\Downloads
Last downloaded files from: http://ftp.hawo.stw.uni-erlangen.de/cygwin/

Package              Version         Status
_autorebase          000076-1        OK
_update-info-dir     00256-1         OK
alternatives         1.3.30c-10      OK
base-cygwin          3.3-1           OK
base-files           4.1-1           OK
bash                 4.1.11-2        OK
bzip2                1.0.6-2         OK
coreutils            8.15-3          OK
cygutils             1.4.14-1        OK
cygwin               1.7.27-2        OK
dash                 0.5.7-4         OK
editrights           1.02-1          OK
file                 5.13-1          OK
findutils            4.5.11-1        OK
gawk                 4.1.0-1         OK
grep                 2.16-1          OK
groff                1.22.2-2        OK
gzip                 1.4-1           OK
hostname             3.13-1          OK
ipc-utils            1.0-2           OK
less                 458-1           OK
libattr1             2.4.46-1        OK
libbz2_1             1.0.6-2         OK
libgcc1              4.8.2-1         OK
libgmp10             5.1.3-1         OK
libiconv2            1.14-1          OK
libintl8             0.18.1.1-3      OK
liblzma5             5.0.4-1         OK
libmpfr4             3.1.2-1         OK
libncursesw10        5.9-4           OK
libpcre1             8.33-1          OK
Empty package libpopt0
libpopt0             1.16-1          OK
libreadline7         6.2-1           OK
libstdc++6           4.8.2-1         OK
login                1.10-10         OK
man                  1.6g-2          OK
mintty               1.2-beta1-1     OK
popt                 1.16-1          OK
rebase               4.4.1-1         OK
run                  1.3.0-1         OK
sed                  4.2.2-3         OK
tar                  1.26-1          OK
terminfo             5.9-4           OK
texinfo              5.2-1           OK
tzcode               2013c-1         OK
vim-minimal          7.4.135-1       OK
which                2.20-2          OK
xz                   5.0.4-1         OK
zlib0                1.2.8-1         OK
Use -h to see help about each section

[-- Attachment #3: Type: text/plain, Size: 218 bytes --]

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: cygwin64 - installation problem - installed by administrator account
  2014-02-04  7:43     ` Flower, Martin
@ 2014-02-04 14:25       ` Larry Hall (Cygwin)
  2014-02-05  9:38         ` Flower, Martin
  0 siblings, 1 reply; 12+ messages in thread
From: Larry Hall (Cygwin) @ 2014-02-04 14:25 UTC (permalink / raw)
  To: cygwin

On 2/4/2014 2:43 AM, Flower, Martin wrote:
> C:\cygwin64\bin>cygcheck -srv > cygcheck.text
>
> C:\cygwin64>Cygwin.bat
> $ id
> uid=400(netflma) gid=401(mkpasswd) grupper=401(mkpasswd),555(Remote Desktop Users),545(Users),10513(Domain Users)
>
> Hope this is what you have asked for.

Yes, thank you.  Looks like all the packages are installed OK.  My guess is
that the post-install scripts didn't run properly because the GIT tools you
have in your path took precedence over the Cygwin ones.  I'd suggest
temporarily removing C:\Tools\Git\bin and C:\Tools\Git\cmd from your path,
deleting C:\cygwin64, and rerunning setup.  See if that helps.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 12+ messages in thread

* RE: cygwin64 - installation problem - installed by administrator account
  2014-02-04 14:25       ` Larry Hall (Cygwin)
@ 2014-02-05  9:38         ` Flower, Martin
  2014-02-05 16:01           ` Larry Hall (Cygwin)
  0 siblings, 1 reply; 12+ messages in thread
From: Flower, Martin @ 2014-02-05  9:38 UTC (permalink / raw)
  To: cygwin

Thank you Larry.

I have uninstalled GIT. I have deleted C:\cygwin64. I have rerun setup-x86_64.exe as admflma. In the start menu I click on the Cygwin icon and continue to have the same symptoms.

Windows cannot find mintty. I can browse for mintty.exe, and then nothing happens.

I open a command window and type C:\cygwin64\bin\mintty.exe and a shell window appears with prompt sh-4.15$

I have rebooted and there is no difference.

If the post-install scripts ran successfully, how would I know? I don't see any changes to my windows PATH environment.

Thanks for your help.

/Martin


-----Original Message-----
From: cygwin-owner
Sent: Tuesday, February 04, 2014 3:25 PM
To: cygwin 
Subject: Re: cygwin64 - installation problem - installed by administrator account

On 2/4/2014 2:43 AM, Flower, Martin wrote:
> C:\cygwin64\bin>cygcheck -srv > cygcheck.text
>
> C:\cygwin64>Cygwin.bat
> $ id
> uid=400(netflma) gid=401(mkpasswd) grupper=401(mkpasswd),555(Remote 
> Desktop Users),545(Users),10513(Domain Users)
>
> Hope this is what you have asked for.

Yes, thank you.  Looks like all the packages are installed OK.  My guess is that the post-install scripts didn't run properly because the GIT tools you have in your path took precedence over the Cygwin ones.  I'd suggest temporarily removing C:\Tools\Git\bin and C:\Tools\Git\cmd from your path, deleting C:\cygwin64, and rerunning setup.  See if that helps.

--
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: cygwin64 - installation problem - installed by administrator account
  2014-02-05  9:38         ` Flower, Martin
@ 2014-02-05 16:01           ` Larry Hall (Cygwin)
  2014-02-05 17:28             ` A device driver as BLODA? Richard
  2014-02-06  6:42             ` cygwin64 - installation problem - installed by administrator account Flower, Martin
  0 siblings, 2 replies; 12+ messages in thread
From: Larry Hall (Cygwin) @ 2014-02-05 16:01 UTC (permalink / raw)
  To: cygwin

On 2/5/2014 4:38 AM, Flower, Martin wrote:
> Thank you Larry.
>
> I have uninstalled GIT. I have deleted C:\cygwin64. I have rerun
> setup-x86_64.exe as admflma. In the start menu I click on the Cygwin icon
> and continue to have the same symptoms.
>
> Windows cannot find mintty. I can browse for mintty.exe, and then nothing
> happens.
>
> I open a command window and type C:\cygwin64\bin\mintty.exe and a shell
> window appears with prompt sh-4.15$
>
> I have rebooted and there is no difference.
>
> If the post-install scripts ran successfully, how would I know? I don't
> see any changes to my windows PATH environment.

The scripts live in /etc/postinstall.  Any that have run will have a
".done" suffix.  More importantly, any that haven't won't.  If you see
ones that haven't run, you can try running them manually from a bash
shell and see if that helps.  But really, even if some or all the
scripts have the ".done" suffix, it doesn't mean that they ran correctly.
It just means that they ran.  To determine if there were any problems
during the run, you need to find and look at the setup.log.full and/or
setup.log files.  These should reside in the directory you ran setup
from.  If there are complaints there about any post-install scripts,
then that's where you should focus your investigation.  setup should
have reported any post-install complaints to you at the end of the
install too.

You may also find that you're a victim of BLODA -
<http://cygwin.com/acronyms/#BLODA>.  You can investigate this avenue as
well as something is clearly getting in the way of the post-install
script process.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 12+ messages in thread

* A device driver as BLODA?
  2014-02-05 16:01           ` Larry Hall (Cygwin)
@ 2014-02-05 17:28             ` Richard
  2014-02-05 18:12               ` Larry Hall (Cygwin)
  2014-02-06  6:42             ` cygwin64 - installation problem - installed by administrator account Flower, Martin
  1 sibling, 1 reply; 12+ messages in thread
From: Richard @ 2014-02-05 17:28 UTC (permalink / raw)
  To: cygwin


Hello All,

For weeks I've been pondering all the troubles I've had with setup, 
spurred by all the conversations that have happened recently about 
packaging, etc, and the occasional comments about BLODA. I have sometimes 
figured Cygwin's setup program is a member of BLODA - it certainly has 
been anything but reliable in my personal experience. And all too often 
it's between me and my enjoyment of Cygwin. (I maintain a fleet of Windows 
boxes with Cygwin, no two of which are identical.)

I've forgotten who wrote it, but I especially appreciated the email in my 
in-box this morning about how to tell when Cygwin installation scripts go 
wrong, where the list of scripts is, etc, because, frankly, when a Cygwin 
installation goes wrong (and when doesn't it?) I seldom have time to track 
down exactly why - I just try, try again, with different versions until it 
works or I give up and try another day. (One MAJOR headache here is the 
download process, no fixed starting point to know you got everything.) 
...And so it was this morning I decided to re-convince myself I didn't 
have any BLODA problems... MAYBE all those issues "weren't Cygwin's 
fault?"

I was surprised to find "ATI Catalyst", and even MORE surprised to find 
"NVIDIA GeForce" on the list, both as "some versions".

I haven't any idea why the Catalyst product would want to hook into things 
that would interfere with Cygwin, but I did have problems with it - it 
would crash the machine sometimes! - so I deleted it.

But the description, "NVIDIA GeForce" has me a bit confused because I 
thought that was the maker's name for a series of video cards (hardware) 
and possibly the device drivers that enable them to do magic things, like 
provide a display consisting of six monitors as my "desktop." ...I use 
this hardware! And, certainly, I use the NVIDIA drivers for it.

This raises two primary questions (and a few related ones):

1) How can I confirm I do or don't have an NVIDIA GeForce BLODA issue? (Is 
there really a device driver level issue?) And;

2) Might "we, the community" develop a BLODA-checker to help the 
installation process? I'm thinking that whenever a new item is discovered 
to put on the BLODA list, a small "here's how you know you have this 
software" script is written that could become a part of the Cygwin install 
process. There's already a script walker for scripts in a directory - 
maybe it could be harnessed to run a list of BLODA-checkers. Sure, there's 
a back-log of already known BLODA, most of which I have never even heard 
of before (probably not alone on that!), but if we can have scripts 
created on an on-going basis - say, when new BLODA are discovered and put 
on the list - eventually the backlog would get caught up...

Given all the complaints out there about the installation / setup process, 
I have to believe that I'm far from alone in thinking that there's likely 
a strong link between installation troubles and BLODA.....

Regards,
Richard

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: A device driver as BLODA?
  2014-02-05 17:28             ` A device driver as BLODA? Richard
@ 2014-02-05 18:12               ` Larry Hall (Cygwin)
  0 siblings, 0 replies; 12+ messages in thread
From: Larry Hall (Cygwin) @ 2014-02-05 18:12 UTC (permalink / raw)
  To: cygwin

On 2/5/2014 12:39 PM, Richard@KarmannGhia.org wrote:
>
> Hello All,
>
> For weeks I've been pondering all the troubles I've had with setup, spurred
> by all the conversations that have happened recently about packaging, etc,
> and the occasional comments about BLODA. I have sometimes figured Cygwin's
> setup program is a member of BLODA - it certainly has been anything but
> reliable in my personal experience. And all too often it's between me and my
> enjoyment of Cygwin. (I maintain a fleet of Windows boxes with Cygwin, no
> two of which are identical.)
>
> I've forgotten who wrote it, but I especially appreciated the email in my
> in-box this morning about how to tell when Cygwin installation scripts go
> wrong, where the list of scripts is, etc, because, frankly, when a Cygwin
> installation goes wrong (and when doesn't it?) I seldom have time to track
> down exactly why - I just try, try again, with different versions until it
> works or I give up and try another day. (One MAJOR headache here is the
> download process, no fixed starting point to know you got everything.)
> ...And so it was this morning I decided to re-convince myself I didn't have
> any BLODA problems... MAYBE all those issues "weren't Cygwin's fault?"

Toiling in obscurity and the occasional vent here and at other outlets
is fine but if you're having some problems you can't figure out,
it could be worth your while to post specifics of your problem
and/or search the email archives for similar problems/solutions, ideas,
etc.  In addition, if you have allot of machines on which you've installed
Cygwin, you may have some interesting observations to report about the
kinds of problems you see on which OSs, mirrors, software versions, etc.
Your observations and details may be useful input for someone else searching
for a solution to the same problem.

> I was surprised to find "ATI Catalyst", and even MORE surprised to find
> "NVIDIA GeForce" on the list, both as "some versions".
>
> I haven't any idea why the Catalyst product would want to hook into things
> that would interfere with Cygwin, but I did have problems with it - it would
> crash the machine sometimes! - so I deleted it.

Yes, this can be cranky and isn't a required install so it's often better
to just avoid it.

> But the description, "NVIDIA GeForce" has me a bit confused because I
> thought that was the maker's name for a series of video cards (hardware) and
> possibly the device drivers that enable them to do magic things, like
> provide a display consisting of six monitors as my "desktop." ...I use this
> hardware! And, certainly, I use the NVIDIA drivers for it.
>
> This raises two primary questions (and a few related ones):
>
> 1) How can I confirm I do or don't have an NVIDIA GeForce BLODA issue? (Is
> there really a device driver level issue?) And;

If Cygwin is running and you're not seeing complaints (generally
fork-related) while you're using it, then it's a pretty good indication
that you don't have BLODA.  For more information on BLODA symptoms,
see the FAQ - <http://cygwin.com/faq/faq.html#faq.using.bloda>.

> 2) Might "we, the community" develop a BLODA-checker to help the
> installation process? I'm thinking that whenever a new item is discovered to
> put on the BLODA list, a small "here's how you know you have this software"
> script is written that could become a part of the Cygwin install process.
> There's already a script walker for scripts in a directory - maybe it could
> be harnessed to run a list of BLODA-checkers. Sure, there's a back-log of
> already known BLODA, most of which I have never even heard of before
> (probably not alone on that!), but if we can have scripts created on an
> on-going basis - say, when new BLODA are discovered and put on the list -
> eventually the backlog would get caught up...

This is a very fluid area as the list of software that can cause these
problems varies over time.  Generally speaking, the list contains apps
that are installed on the system and show up in the Windows list of
installed apps (i.e. "Add/Remove Programs" or "Programs and Features").
But I'm certain no one would object to someone supplementing the current
list with more information and/or utilities to make this all easier for
users that run across this issue.  Ideally, we'd really like it if this
list would shrink and disappear but I doubt we're going to see that.

> Given all the complaints out there about the installation / setup process, I
> have to believe that I'm far from alone in thinking that there's likely a
> strong link between installation troubles and BLODA.....

Certainly if there is BLODA on your system, the installation process has the
potential to trip over it because there are scripts run as part of the
process that use Cygwin utilities.  In addition, there's the potential
problem of DLL address-space collisions which becomes more noticeable as
the number of packages you install grows.  The symptoms of this are similar
(see <http://cygwin.com/faq/faq.html#faq.using.fixing-fork-failures>),
particularly in an install, as the scripts could again trip up as a result.
Conventional wisdom for getting a successful first install suggests that
you pick the minimum number of additional packages you need (or don't
pick any at all).  Let the install do its thing and then come back for
more if you need it.  This can help.  64-bit Cygwin has the potential
to ameliorate the address-space collision issue too but wouldn't obviously
be a way to combat BLODA unfortunately.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 12+ messages in thread

* RE: cygwin64 - installation problem - installed by administrator account
  2014-02-05 16:01           ` Larry Hall (Cygwin)
  2014-02-05 17:28             ` A device driver as BLODA? Richard
@ 2014-02-06  6:42             ` Flower, Martin
  2014-02-06 14:49               ` Larry Hall (Cygwin)
  1 sibling, 1 reply; 12+ messages in thread
From: Flower, Martin @ 2014-02-06  6:42 UTC (permalink / raw)
  To: cygwin

The scripts live in /etc/postinstall.  Any that have run will have a ".done" suffix.  More importantly, any that haven't won't.  If you see ones that haven't run, you can try running them manually from a bash shell and see if that helps.  But really, even if some or all the scripts have the ".done" suffix, it doesn't mean that they ran correctly.
It just means that they ran.  To determine if there were any problems during the run, you need to find and look at the setup.log.full and/or setup.log files.  These should reside in the directory you ran setup from.  If there are complaints there about any post-install scripts, then that's where you should focus your investigation.  setup should have reported any post-install complaints to you at the end of the install too.

You may also find that you're a victim of BLODA - <http://cygwin.com/acronyms/#BLODA>.  You can investigate this avenue as well as something is clearly getting in the way of the post-install script process.

--
Larry

===============================

Thank you Larry

All scripts have .done.

Setup.log.full shows an error. I see the word McShield, and I link it to BLODA. File C:\cygwin64\etc\setup\setup.rc exists - although I assume it didn't exist when setup was started.

2014/02/05 10:05:28 Starting cygwin install, version 2.831
2014/02/05 10:05:28 User has backup/restore rights
2014/02/05 10:05:28 io_stream_cygfile: fopen(/etc/setup/setup.rc) failed 2 No such file or directory
2014/02/05 10:05:28 Current Directory: C:\Users\netflma\Downloads
2014/02/05 10:05:28 Could not open service McShield for query, start and stop. McAfee may not be installed, or we don't have access.
2014/02/05 10:05:38 source: network install
2014/02/05 10:05:42 source: download
2014/02/05 10:05:51 source: download
2014/02/05 10:05:52 Selected local directory: C:\Users\netflma\Downloads
2014/02/05 10:06:20 net: Proxy
Cached mirror list unavailable
get_url_to_membuf http://cygwin.com/mirrors.lst
getUrlToStream http://cygwin.com/mirrors.lst
2014/02/05 10:06:22 Ending cygwin install

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: cygwin64 - installation problem - installed by administrator account
  2014-02-06  6:42             ` cygwin64 - installation problem - installed by administrator account Flower, Martin
@ 2014-02-06 14:49               ` Larry Hall (Cygwin)
  2014-02-06 15:02                 ` Flower, Martin
  0 siblings, 1 reply; 12+ messages in thread
From: Larry Hall (Cygwin) @ 2014-02-06 14:49 UTC (permalink / raw)
  To: cygwin

On 2/6/2014 1:42 AM, Flower, Martin wrote:

<snip>

> All scripts have .done.
>
> Setup.log.full shows an error. I see the word McShield, and I link it to
> BLODA. File C:\cygwin64\etc\setup\setup.rc exists - although I assume it
> didn't exist when setup was started.
>
> 2014/02/05 10:05:28 Starting cygwin install, version 2.831
> 2014/02/05 10:05:28 User has backup/restore rights
> 2014/02/05 10:05:28 io_stream_cygfile: fopen(/etc/setup/setup.rc) failed 2 No such file or directory
> 2014/02/05 10:05:28 Current Directory: C:\Users\netflma\Downloads
> 2014/02/05 10:05:28 Could not open service McShield for query, start and stop. McAfee may not be installed, or we don't have access.
> 2014/02/05 10:05:38 source: network install
> 2014/02/05 10:05:42 source: download
> 2014/02/05 10:05:51 source: download
> 2014/02/05 10:05:52 Selected local directory: C:\Users\netflma\Downloads
> 2014/02/05 10:06:20 net: Proxy
> Cached mirror list unavailable
> get_url_to_membuf http://cygwin.com/mirrors.lst
> getUrlToStream http://cygwin.com/mirrors.lst
> 2014/02/05 10:06:22 Ending cygwin install

This all looks fine to me.  Anything interesting in setup.log?


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 12+ messages in thread

* RE: cygwin64 - installation problem - installed by administrator account
  2014-02-06 14:49               ` Larry Hall (Cygwin)
@ 2014-02-06 15:02                 ` Flower, Martin
  0 siblings, 0 replies; 12+ messages in thread
From: Flower, Martin @ 2014-02-06 15:02 UTC (permalink / raw)
  To: cygwin

-----Original Message-----
From: cygwin-owner [mailto:cygwin-owner] On Behalf Of Larry Hall (Cygwin)
Sent: Thursday, February 06, 2014 3:49 PM
To: cygwin
Subject: Re: cygwin64 - installation problem - installed by administrator account

On 2/6/2014 1:42 AM, Flower, Martin wrote:

<snip>

> All scripts have .done.
>
> Setup.log.full shows an error. I see the word McShield, and I link it 
> to BLODA. File C:\cygwin64\etc\setup\setup.rc exists - although I 
> assume it didn't exist when setup was started.
>
> 2014/02/05 10:05:28 Starting cygwin install, version 2.831
> 2014/02/05 10:05:28 User has backup/restore rights
> 2014/02/05 10:05:28 io_stream_cygfile: fopen(/etc/setup/setup.rc) 
> failed 2 No such file or directory
> 2014/02/05 10:05:28 Current Directory: C:\Users\netflma\Downloads
> 2014/02/05 10:05:28 Could not open service McShield for query, start and stop. McAfee may not be installed, or we don't have access.
> 2014/02/05 10:05:38 source: network install
> 2014/02/05 10:05:42 source: download
> 2014/02/05 10:05:51 source: download
> 2014/02/05 10:05:52 Selected local directory: 
> C:\Users\netflma\Downloads
> 2014/02/05 10:06:20 net: Proxy
> Cached mirror list unavailable
> get_url_to_membuf http://cygwin.com/mirrors.lst getUrlToStream 
> http://cygwin.com/mirrors.lst
> 2014/02/05 10:06:22 Ending cygwin install

This all looks fine to me.  Anything interesting in setup.log?


--
Larry

_____________________________________________________________________

Here is setup.log

2014/02/05 10:05:28 Starting cygwin install, version 2.831
2014/02/05 10:05:28 User has backup/restore rights
2014/02/05 10:05:28 io_stream_cygfile: fopen(/etc/setup/setup.rc) failed 2 No such file or directory
2014/02/05 10:05:28 Current Directory: C:\Users\netflma\Downloads
2014/02/05 10:05:28 Could not open service McShield for query, start and stop. McAfee may not be installed, or we don't have access.
2014/02/05 10:05:38 source: network install
2014/02/05 10:05:42 source: download
2014/02/05 10:05:51 source: download
2014/02/05 10:05:52 Selected local directory: C:\Users\netflma\Downloads
2014/02/05 10:06:20 net: Proxy
2014/02/05 10:06:22 Ending cygwin install

----

In my opinion, this has taken up enough of your time, so I suggest we leave the investigation there. I have reinstalled Git for Windows (MINGW32), and that seems to work ok.

/Martin


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2014-02-06 15:02 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-01-27  6:29 cygwin64 - installation problem - installed by administrator account Flower, Martin
2014-01-27 20:56 ` Larry Hall (Cygwin)
2014-01-28  0:55   ` Mark Geisert
2014-02-04  7:43     ` Flower, Martin
2014-02-04 14:25       ` Larry Hall (Cygwin)
2014-02-05  9:38         ` Flower, Martin
2014-02-05 16:01           ` Larry Hall (Cygwin)
2014-02-05 17:28             ` A device driver as BLODA? Richard
2014-02-05 18:12               ` Larry Hall (Cygwin)
2014-02-06  6:42             ` cygwin64 - installation problem - installed by administrator account Flower, Martin
2014-02-06 14:49               ` Larry Hall (Cygwin)
2014-02-06 15:02                 ` Flower, Martin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).