RE: Cygwin Installation Problems on Windows Vista (killing sh.exe helps)

2007-12-14 Thread Quip11


lent wrote:
 
 
 On the semi-broken installation: 
 Actually, the problem was that the whatever vital job that
 /etc/postinstall/gnuplot.sh was doing
 never completed.  30 minutes of wait time by multiple Vista users on
 multiple brands of spanking new
 laptops indicates some sort of interaction bug of these shell scripts (or
 the programs they run) with the wonders of Vista. 
 
 This hang at 99% forever symptom persists even with setting the
 Properties of
 setup.exe to run in Windows XP(SP2) compatibility mode. 
 
 It's a very disappointing installation experience for novice programmers.
 
 Our XP and Windows 2000 users do not have these problems as setup.exe
 completes just fine.
 
 Thanks again for your attention to this annoying bug.
 Chris Lent
 
 


Actually I'm having this same problem right now with good ol' Windows XP. 
If it doesn't hang in /etc/postinstall/update-info-dir.sh, it hangs
somewhere else.  I've walked away and let it run for hours.

There's something wrong with the scripts.  And this is three months later.

-Q
-- 
View this message in context: 
http://www.nabble.com/Cygwin-Installation-Problems-on-Windows-Vista-tp9889324p14339689.html
Sent from the Cygwin list mailing list archive at Nabble.com.


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



Re: Cygwin Installation Problems on Windows Vista (killing sh.exe helps)

2007-09-19 Thread lent

For getting the installation to keep going, killing off an sh.exe process via
Task Manager's End Process, moves things along.  This also seems to need to
be done for texf (I think that was the name) package.

At least we get to the final setup screen this way :-)
Chris Lent




Kevin Hilton-3 wrote:
 
 Here are the two files I found broken on the installation:
 gnuplot.sh
 postinstall-ec-fonts-mftraced.sh
 
 And just for kicks
 How do I manually change the passwd and group files.  Although under
 windows Im listed as an administrator, cygwin states my group as none.
   And Im unable to chmod chgroup these two files.  Never had this
 problem with XP.
 
 -- 
 Kevin Hilton
 
 --
 Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
 Problem reports:   http://cygwin.com/problems.html
 Documentation: http://cygwin.com/docs.html
 FAQ:   http://cygwin.com/faq/
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Cygwin-Installation-Problems-on-Windows-Vista-tf3542482.html#a12780123
Sent from the Cygwin Users mailing list archive at Nabble.com.


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



RE: Cygwin Installation Problems on Windows Vista (killing sh.exe helps)

2007-09-19 Thread Dave Korn
On 19 September 2007 16:42, lent wrote:

 For getting the installation to keep going, killing off an sh.exe process
 via 
 Task Manager's End Process, moves things along.  This also seems to need to
 be done for texf (I think that was the name) package.

  Hell, you can make the whole thing move along even better, by simply
killing 'setup.exe' instead of sh.exe.  Sure, it may not be correct, but at
least it's fast, eh?

  Or you could wait for it to finish doing whatever vital job it was doing.
Your choice.

 At least we get to the final setup screen this way :-)

  Works my way too, *and* with the added advantage you don't end up with a
semi-broken installation.


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


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



RE: Cygwin Installation Problems on Windows Vista (killing sh.exe helps)

2007-09-19 Thread lent


Dave Korn wrote:
 
 On 19 September 2007 16:42, lent wrote:
 Hi Dave, thanks for the quick reply.
 
 Sorry, but I wasn't able to find the solution you refer to for the problem
 of setup.exe hanging in Windows Vista.  Where can I find it?
 
 For getting the installation to keep going, killing off an sh.exe
 process
 via 
 Task Manager's End Process, moves things along.  This also seems to need
 to
 be done for texf (I think that was the name) package.
 
  Hell, you can make the whole thing move along even better, by simply
killing 'setup.exe' instead of sh.exe.  Sure, it may not be correct, but
at
least it's fast, eh?
 
  Or you could wait for it to finish doing whatever vital job it was
 doing.
Your choice.
 
 At least we get to the final setup screen this way :-)
 
  Works my way too, *and* with the added advantage you don't end up with a
semi-broken installation.
 
 I'm new to the cygwin development community and would love to chase this
 problem down and resolve it once and for all.  Is there a way to log the
 shell scripts as they are run from setup.exe?
 
 On the semi-broken installation: 
 Actually, the problem was that the whatever vital job that
 /etc/postinstall/gnuplot.sh was doing
 never completed.  30 minutes of wait time by multiple Vista users on
 multiple brands of spanking new
 laptops indicates some sort of interaction bug of these shell scripts (or
 the programs they run) with the wonders of Vista. 
 
 This hang at 99% forever symptom persists even with setting the
 Properties of
 setup.exe to run in Windows XP(SP2) compatibility mode. 
 
 It's a very disappointing installation experience for novice programmers.
 
 Our XP and Windows 2000 users do not have these problems as setup.exe
 completes just fine.
 
 Do I want to kill any part of a carefully crafted installation process? Of
 course not :-)
 
 The problem is if the user kills setup.exe, they wind up with a more
 broken installation, and lack the Cygwin Desktop icon  and the Cygwin
 Start Menu entry. Killing sh.exe (hopefully the right one) moves the
 installation process past the block of /etc/postinstall/gnuplot.sh.  
 
 Our reason for using Cygwin is to teach young engineering students about C
 programming in a command line environment.  If they can't install it on
 their brand new laptop, I have a difficult time having them use it :-)
 
 Thanks again for your attention to this annoying bug.
 Chris Lent
 
cheers,
  DaveK
 
 

-- 
View this message in context: 
http://www.nabble.com/Cygwin-Installation-Problems-on-Windows-Vista-tf3542482.html#a12786663
Sent from the Cygwin Users mailing list archive at Nabble.com.


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