Mail Archives: cygwin/2003/04/26/20:29:49
On Saturday, April 26, 2003 4:39 PM, Igor Pechtchanski [SMTP:pechtcha AT cs DOT nyu DOT edu] wrote:
> On Sat, 26 Apr 2003, Max Bowsher wrote:
>
> > Phil Bewig wrote:
> > > Setup version 2.340.2.5, downloaded earlier today.
> > >
> > > On one occasion I left it hanging for several hours. For a while
> > > it would still respond to system messages, for instance I could
> > > drag the title bar to move the window to a different part of the
> > > screen. Then it stopped doing even that, and the task window
> > > sait "not responding." I was previously aware of the "long
> > > minute" thread, having searched the mailing list, but not of the
> > > "rush job" thread.
> > >
> > > Since posting I have made another attempt, getting farther. I
> > > was able to select packages on the chooser screen, and
> > > setup.exe began installing sh.exe. I let it work for over an
> > > hour, with no other programs running (other than the normal
> > > background processes). When I came back to my machine,
> > > setup.exe responded to an attempt to drag the title bar. But
> > > then I could do nothing else with the machine. Even trying
> > > to load solitaire gave me the message "insufficient memory;
> > > try unloading other programs." So obviously something was
> > > going on with setup.exe consuming memory. There was no
> > > disk thrashing. I waited another fifteen minutes then killed
> > > setup.exe.
> > >
> > > I assume that what setup.exe is doing at this point is
> > > extracting sh.exe from the ash-20020731-1.tar.bz2 archive.
> > > Is that correct? How does the extract process work? What
> > > program does the extraction? Setup.exe? Or something
> > > else? And why isn't there a setup log somewhere?
> >
> > Yes, correct. Setup does the extraction itself - no external programs.
> > There's no log, because setup buffers the log entries and only writes them
> > to disc when it exits.
> >
> > This is a hard problem. I'd be really interested in some of the info you
> > could get from gdb - but since setup isn't working, you can't install gdb!
> > Ouch.
> >
> > Max.
>
> Phil,
>
> Did you try the snapshot?..
> Igor
> --
> http://cs.nyu.edu/~pechtcha/
> |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu
> ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com
> |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
> '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
>
> Knowledge is an unending adventure at the edge of uncertainty.
> -- Leto II
I downloaded the snapshot of setup.exe version 2.358. Setup
runs, calculating the MD5 checksums and giving me a screen
to choose packages. I did nothing on the chooser screen, just
accepting the default installation. Now I have a progress screen
that indicates it is installing ash-20020731-1 /bin/sh.exe; the
progress bar is blue all the way across, the total bar is gray all
the way across, and the disk bar is blue about one-tenth of the
way across, indicating over 900MB of disk space remaining on
d:. The screen has been sitting here unchanged for about 20
minutes now, but still responds when I drag the title bar to move
the window. This is exactly the same situation I experienced
earlier with the 2.340 version of setup.exe.
I notice that there seems to be some flicker in the setup.exe
window, as if it is being redrawn. The flicker is intermittent,
about every 30 seconds, when there are several brief flickers,
then the screen is steady until the next set of flickers. Why?
I assume because the progress bar is blue all the way across
that the sh.exe file has been extracted; is that correct? The
file is not present when I look at the drive contents with
Explorer. Can someone tell me exactly what should be
happening at this point?
I'll let this keep running and report what happens.
Once again, many thanks to everyone for their kind help.
Phil
--
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/
- Raw text -