Re: Windowmaker not open bash properly

2007-06-27 Thread Scott Mohnkern



Larry Hall (Cygwin X) wrote:

Scott Mohnkern wrote:



Larry Hall (Cygwin X) wrote:

Scott Mohnkern wrote:
Apologies, I was following the format of other questions I'd seen 
here.


Attached is cygcheck.out

The other server was Xvision, which was part of an automatic 
install of Cradle 5.5.x





You (no longer?) have Cygwin in your path.  You're picking up the
Nutcracker/MKS tools now.  Fix your path and give a quick run 
through of
the rest of your environment to clean up any issues.  Two that 
caught my

eye are $HOME and $TERM are now incorrectly set.  If you can find where
Nutcracker/MKS sets these and remove/avoid them, you'll have better 
luck

working with Cygwin.




That appears to have solved most of it.  Removing the nutcracker 
entries and putting cygwin and cygwin bin in the path got me up and 
running.  It doesn't appear to be pulling my profile up correctly 
when I open up bash (It's defaulting to a different $HOME but I can 
probably figure out where that is set)



It's probably in your system-level environment, which you can access from
the Windows control panel "System" applet.  Good luck.


That's definitely it I'm pretty sure it's an environment variable that 
got messed with.  Cradle during install set $SHELL to "nutc" without 
telling me, and I'm 90% sure that's what caused Windowmaker  to choke.  
Now I just need to figure out which of these other system variables need 
to go, and which ones I need to put back in.



Scott


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



Re: Windowmaker not open bash properly

2007-06-26 Thread Larry Hall (Cygwin X)

Scott Mohnkern wrote:



Larry Hall (Cygwin X) wrote:

Scott Mohnkern wrote:

Apologies, I was following the format of other questions I'd seen here.

Attached is cygcheck.out

The other server was Xvision, which was part of an automatic install 
of Cradle 5.5.x





You (no longer?) have Cygwin in your path.  You're picking up the
Nutcracker/MKS tools now.  Fix your path and give a quick run through of
the rest of your environment to clean up any issues.  Two that caught my
eye are $HOME and $TERM are now incorrectly set.  If you can find where
Nutcracker/MKS sets these and remove/avoid them, you'll have better luck
working with Cygwin.




That appears to have solved most of it.  Removing the nutcracker entries 
and putting cygwin and cygwin bin in the path got me up and running.  It 
doesn't appear to be pulling my profile up correctly when I open up bash 
(It's defaulting to a different $HOME but I can probably figure out 
where that is set)



It's probably in your system-level environment, which you can access from
the Windows control panel "System" applet.  Good luck.


--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 429-6305 - FAX
Holliston, MA 01746

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



Re: Windowmaker not open bash properly

2007-06-26 Thread Scott Mohnkern



Larry Hall (Cygwin X) wrote:

Scott Mohnkern wrote:

Apologies, I was following the format of other questions I'd seen here.

Attached is cygcheck.out

The other server was Xvision, which was part of an automatic install 
of Cradle 5.5.x





You (no longer?) have Cygwin in your path.  You're picking up the
Nutcracker/MKS tools now.  Fix your path and give a quick run through of
the rest of your environment to clean up any issues.  Two that caught my
eye are $HOME and $TERM are now incorrectly set.  If you can find where
Nutcracker/MKS sets these and remove/avoid them, you'll have better luck
working with Cygwin.




That appears to have solved most of it.  Removing the nutcracker entries 
and putting cygwin and cygwin bin in the path got me up and running.  It 
doesn't appear to be pulling my profile up correctly when I open up bash 
(It's defaulting to a different $HOME but I can probably figure out 
where that is set)


Thanks for your time. 



Scott Mohnkern


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



Re: Windowmaker not open bash properly

2007-06-26 Thread Larry Hall (Cygwin X)

Scott Mohnkern wrote:

Apologies, I was following the format of other questions I'd seen here.

Attached is cygcheck.out

The other server was Xvision, which was part of an automatic install of 
Cradle 5.5.x





You (no longer?) have Cygwin in your path.  You're picking up the
Nutcracker/MKS tools now.  Fix your path and give a quick run through of
the rest of your environment to clean up any issues.  Two that caught my
eye are $HOME and $TERM are now incorrectly set.  If you can find where
Nutcracker/MKS sets these and remove/avoid them, you'll have better luck
working with Cygwin.


--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 429-6305 - FAX
Holliston, MA 01746

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



Re: Windowmaker not open bash properly

2007-06-26 Thread Scott Mohnkern

Apologies, I was following the format of other questions I'd seen here.

Attached is cygcheck.out

The other server was Xvision, which was part of an automatic install of 
Cradle 5.5.x



Scott


Larry Hall (Cygwin X) wrote:

Scott Mohnkern wrote:
I had Cygwin with Windowmaker running just beautifully, then another 
application came in and installed another xserver (which I've since 
disabled) but now inside windowmaker, whenever I try to open up an 
Xterm window the window opens but I get no bash prompt.


I can type an ls and get a file listing, and a ps gives me processes.

However whenever I try to ssh -Y to another machine, it tells me

"Pseudo-terminal will not be allocated because stdin is not a terminal."


Anyone ever seen this before, and a solution?



I'd suggest reading the problem reporting guidelines outlined at the link
below:


Problem reports:   http://cygwin.com/problems.html


You've given us some information about how the problem manifests itself
but it would be helpful to know what other Xserver you installed as well
as basic boot-strap information (i.e. cygcheck output - *attached* not
included/inlined).


Cygwin Configuration Diagnostics
Current System Time: Tue Jun 26 15:17:46 2007

Windows XP Professional Ver 5.1 Build 2600 Service Pack 2

Path:   C:\WINDOWS\SYSTEM32\NUTCROOT\bin
C:\WINDOWS\SYSTEM32\NUTCROOT\bin\x11
C:\WINDOWS\SYSTEM32\NUTCROOT\mksnt
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
C:\Program Files\Common Files\Adaptec Shared\System
C:\Program Files\QuickTime\QTSystem\
C:\PROGRA~1\Vision
C:\PROGRA~1\Vision\SYSTEM
C:\PROGRA~1\COMMON~1\Vision

Output from D:\cygwin\bin\id.exe (nontsec)
UID: 28004(MohnkernS)GID: 10513(Domain Users)
544(Administrators)  545(Users)   10513(Domain Users)
15811(OHD-11)15776(OHD-Users)

Output from D:\cygwin\bin\id.exe (ntsec)
UID: 28004(MohnkernS)GID: 10513(Domain Users)
544(Administrators)  545(Users)   10513(Domain Users)
15811(OHD-11)15776(OHD-Users)

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

CYGWIN = 'server'
HOME = 'H:\'
Path = 
'C:\WINDOWS\SYSTEM32\NUTCROOT\bin;C:\WINDOWS\SYSTEM32\NUTCROOT\bin\x11;C:\WINDOWS\SYSTEM32\NUTCROOT\mksnt;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program
 Files\Common Files\Adaptec Shared\System;C:\Program 
Files\QuickTime\QTSystem\;C:\PROGRA~1\Vision;C:\PROGRA~1\Vision\SYSTEM;C:\PROGRA~1\COMMON~1\Vision'

ALLUSERSPROFILE = 'C:\Documents and Settings\All Users'
APPDATA = 'C:\Documents and Settings\MohnkernS\Application Data'
CLASSPATH = '.;C:\Program Files\Java\jre1.6.0_01\lib\ext\QTJava.zip'
CLIENTNAME = 'Console'
CommonProgramFiles = 'C:\Program Files\Common Files'
COMPUTERNAME = 'OHD11-7222A'
ComSpec = 'C:\WINDOWS\system32\cmd.exe'
CRADLEHOME = 'C:\Program Files\Cradle'
CRADLE_CDS_HOST = 'frisky'
DEFLOGDIR = 'C:\Documents and Settings\All Users\Application 
Data\McAfee\DesktopProtection'
DISPLAY = ':0.0'
FP_NO_HOST_CHECK = 'NO'
HOMEDRIVE = 'H:'
HOMEPATH = '\'
HOMESHARE = '\\nws-fs1\MohnkS$'
LOGONSERVER = '\\NWS-AD2'
NUMBER_OF_PROCESSORS = '1'
NUTCROOT = 'C:\WINDOWS\SYSTEM32\NUTCROOT'
OS = 'Windows_NT'
PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
PROCESSOR_ARCHITECTURE = 'x86'
PROCESSOR_IDENTIFIER = 'x86 Family 15 Model 2 Stepping 9, GenuineIntel'
PROCESSOR_LEVEL = '15'
PROCESSOR_REVISION = '0209'
ProgramFiles = 'C:\Program Files'
PROMPT = '$P$G'
QTJAVA = 'C:\Program Files\Java\jre1.6.0_01\lib\ext\QTJava.zip'
ROOTDIR = 'C:\WINDOWS\SYSTEM32\NUTCROOT'
SESSIONNAME = 'Console'
SHELL = 'C:\WINDOWS\SYSTEM32\NUTCROOT\mksnt\sh.exe'
SystemDrive = 'C:'
SystemRoot = 'C:\WINDOWS'
TEMP = 'C:\DOCUME~1\MOHNKE~1\LOCALS~1\Temp'
TERM = 'nutc'
TERMCAP = 'C:\WINDOWS\SYSTEM32\NUTCROOT\etc\termcap'
TERMINFO = 'C:\WINDOWS\SYSTEM32\NUTCROOT\usr\lib\terminfo'
TMP = 'C:\DOCUME~1\MOHNKE~1\LOCALS~1\Temp'
TMPDIR = 'C:\DOCUME~1\MOHNKE~1\LOCALS~1\Temp'
USERDNSDOMAIN = 'NWS.NOAA'
USERDOMAIN = 'NWS'
USERNAME = 'mohnkerns'
USERPROFILE = 'C:\Documents and Settings\MohnkernS'
VSEDEFLOGDIR = 'C:\Documents and Settings\All Users\Application 
Data\McAfee\DesktopProtection'
windir = 'C:\WINDOWS'
POSIXLY_CORRECT = '1'

HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
  (default) = '/cygdrive'
  cygdrive flags = 0x0022
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/
  (default) = 'D:\cygwin'
  flags = 0x000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
  (default) = 'D:\cygwin/bin'
  flags = 0x000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
  (de

Re: Windowmaker not open bash properly

2007-06-26 Thread Larry Hall (Cygwin X)

Scott Mohnkern wrote:
I had Cygwin with Windowmaker running just beautifully, then another 
application came in and installed another xserver (which I've since 
disabled) but now inside windowmaker, whenever I try to open up an Xterm 
window the window opens but I get no bash prompt.


I can type an ls and get a file listing, and a ps gives me processes.

However whenever I try to ssh -Y to another machine, it tells me

"Pseudo-terminal will not be allocated because stdin is not a terminal."


Anyone ever seen this before, and a solution?



I'd suggest reading the problem reporting guidelines outlined at the link
below:


Problem reports:   http://cygwin.com/problems.html


You've given us some information about how the problem manifests itself
but it would be helpful to know what other Xserver you installed as well
as basic boot-strap information (i.e. cygcheck output - *attached* not
included/inlined).

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 429-6305 - FAX
Holliston, MA 01746

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



Windowmaker not open bash properly

2007-06-26 Thread Scott Mohnkern
I had Cygwin with Windowmaker running just beautifully, then another 
application came in and installed another xserver (which I've since 
disabled) but now inside windowmaker, whenever I try to open up an Xterm 
window the window opens but I get no bash prompt.


I can type an ls and get a file listing, and a ps gives me processes.

However whenever I try to ssh -Y to another machine, it tells me

"Pseudo-terminal will not be allocated because stdin is not a terminal."


Anyone ever seen this before, and a solution?


Scott Mohnkern


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