RE: setup.exe: Woe is me!

RE: setup.exe: Woe is me!

[Phil Bewig]

On Saturday, April 26, 2003 7:47 PM, Phil Bewig [SMTP:pbewig@swbell.net] wrote:
> On Saturday, April 26, 2003 7:28 PM, Phil Bewig [SMTP:pbewig@swbell.net] wrote:
> > On Saturday, April 26, 2003 4:39 PM, Igor Pechtchanski [SMTP:pechtcha@cs.nyu.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@cs.nyu.edu
> > > ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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
> 
> Setup.exe has now been running for about 45 minutes
> with no change.
> 
> I notice that something is consuming much disk space,
> about 65MB of disk space since I cleaned up some
> unneeded files earlier this afternoon, and about 15MB
> in the last 15 minutes.  The only processes currently
> active are device drivers, setup.exe, MS Outlook, and
> MSIE, which has been browsing www.cygwin.com.
> The firewall is active and reports two blocked attempts
> to access my system while setup.exe has been
> running.  Would setup.exe consume disk space at
> that rate?  Why?
> 
> Thanks again,
> 
> Phil

I notice in the task window that a program called
mapisp32 is running.  Find reports that it is located
at c:\windows\system\mapisp32.exe.  I do not recall
having seen mapisp32 in the task list previously.
Can anyone tell me what this program does?  Is
this program somehow related to the setup.exe
problem?

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/

RE: setup.exe: Woe is me!

[Robert Collins]

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

On Mon, 2003-04-28 at 05:23, Igor Pechtchanski wrote:


> I don't know how much extra effort it'll be, but wouldn't a
> "log-on-the-spot" command-line option make sense anyway?  Or is that what
> you meant?

Actually, I just meant building setup with the extant patch to change
the logging behaviour.

A command line option we can include for releases would be neat. The
patch Max has just reposted would be a good basis for that..

Rob

-- 
GPG key available at: <http://users.bigpond.net.au/robertc/keys.txt>.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

RE: setup.exe: Woe is me!

[Igor Pechtchanski]

On 28 Apr 2003, Robert Collins wrote:

> On Sun, 2003-04-27 at 11:13, Phil Bewig wrote:
> > I just killed setup.exe after over an hour of inactivity.  A total
> > of over 125MB of disk space has disappeared in the last few
> > hours while I have been running setup.exe, reading and
> > replying to email on the cygwin mailing list in this thread
> > using MS Outlook, and searching the cygwin mailing list
> > archives with MSIE.  When I killed setup.exe (using the
> > "cancel" button on the progress screen), I received a popup
> > message "Cannot open log file d:\/var/log/setup.log for
> > writing."  Are there any additional clues here?  What is
> > consuming disk?  And how do I get it back?
>
> my WAG:
> setup is looping: trying to create a file, failing, and trying again.
>
> Here's what I'd like you to do:
> Check your registry for cygwin mount points, both per user and per
> machine. There may be a decompressed cygcheck you can download to do
> this. If there isn't, then have a look on this list for other references
> to the mount point data. (It's not supported to make registry changes
> manually, which is why I'm *not* putting the keys in this email).
>
> If, as I suspect, you have some broken mount points, just delete the
> entire cygwin keys in both user and machine subtrees.
>
> Now, run setup again, and when you are installing, be very very sure to
> install to somewhere like "D:\cygwin", not to "D:\".
>
> If that doesn't work, then I'll brew up a log-on-the-spot version of
> setup.exe for you, which will let us see whats going on.
>
> Cheers,
> Rob

Rob,

I don't know how much extra effort it'll be, but wouldn't a
"log-on-the-spot" command-line option make sense anyway?  Or is that what
you meant?
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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


--
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: setup.exe: Woe is me!

[Phil Bewig]

On Sunday, April 27, 2003 11:49 AM, Robert Collins [SMTP:rbcollins@cygwin.com] wrote:
> On Sun, 2003-04-27 at 11:13, Phil Bewig wrote:
> > I just killed setup.exe after over an hour of inactivity.  A total
> > of over 125MB of disk space has disappeared in the last few
> > hours while I have been running setup.exe, reading and
> > replying to email on the cygwin mailing list in this thread
> > using MS Outlook, and searching the cygwin mailing list
> > archives with MSIE.  When I killed setup.exe (using the
> > "cancel" button on the progress screen), I received a popup
> > message "Cannot open log file d:\/var/log/setup.log for
> > writing."  Are there any additional clues here?  What is
> > consuming disk?  And how do I get it back?
> 
> my WAG:
> setup is looping: trying to create a file, failing, and trying again.
> 
> Here's what I'd like you to do:
> Check your registry for cygwin mount points, both per user and per
> machine. There may be a decompressed cygcheck you can download to do
> this. If there isn't, then have a look on this list for other references
> to the mount point data. (It's not supported to make registry changes
> manually, which is why I'm *not* putting the keys in this email).
> 
> If, as I suspect, you have some broken mount points, just delete the
> entire cygwin keys in both user and machine subtrees.
> 
> Now, run setup again, and when you are installing, be very very sure to
> install to somewhere like "D:\cygwin", not to "D:\".
> 
> If that doesn't work, then I'll brew up a log-on-the-spot version of
> setup.exe for you, which will let us see whats going on.
> 
> Cheers,
> Rob
> -- 
> GPG key available at: <http://users.bigpond.net.au/robertc/keys.txt>.
>  << File: signature.asc >> 

Hooray!

Installing in d:\cygwin ran fine, and I now have a working cygwin
system.  However, I would still prefer to have d:\ as the cygwin
root, rather than d:\cygwin.  Is there any way to arrange that?
If not, is there some reason why?  And if d:\ isn't allowed to be
the cygwin root, why did setup allow me to select it as the root?

Thanks to everyone for their 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/

RE: setup.exe: Woe is me!

[Robert Collins]

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

On Sun, 2003-04-27 at 11:13, Phil Bewig wrote:
> I just killed setup.exe after over an hour of inactivity.  A total
> of over 125MB of disk space has disappeared in the last few
> hours while I have been running setup.exe, reading and
> replying to email on the cygwin mailing list in this thread
> using MS Outlook, and searching the cygwin mailing list
> archives with MSIE.  When I killed setup.exe (using the
> "cancel" button on the progress screen), I received a popup
> message "Cannot open log file d:\/var/log/setup.log for
> writing."  Are there any additional clues here?  What is
> consuming disk?  And how do I get it back?

my WAG:
setup is looping: trying to create a file, failing, and trying again.

Here's what I'd like you to do:
Check your registry for cygwin mount points, both per user and per
machine. There may be a decompressed cygcheck you can download to do
this. If there isn't, then have a look on this list for other references
to the mount point data. (It's not supported to make registry changes
manually, which is why I'm *not* putting the keys in this email).

If, as I suspect, you have some broken mount points, just delete the
entire cygwin keys in both user and machine subtrees.

Now, run setup again, and when you are installing, be very very sure to
install to somewhere like "D:\cygwin", not to "D:\".

If that doesn't work, then I'll brew up a log-on-the-spot version of
setup.exe for you, which will let us see whats going on.

Cheers,
Rob
-- 
GPG key available at: <http://users.bigpond.net.au/robertc/keys.txt>.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: setup.exe: Woe is me!

[Elfyn McBratney]

> On some of the attempts I started by rebooting the machine, not
> enabling the DSL connection or the firewall, and running setup.  I
> have no problem downloading the data; it is stored in d:\package,
> from where I do a local install.  The problem happens after the
> MD5 checksum.

Phil, would you be able to try one of the latest setup snapshots? There's an
option to disable MD5 checks. If you start setup.exe from the start menu/DOS
box just add '--no-md5' at the end.

Setup snapshots are available at <http://cygwin.com/setup-snapshots/>.

Elfyn


--
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: setup.exe: Woe is me!

[Phil Bewig]

On Saturday, April 26, 2003 8:57 PM, Igor Pechtchanski [SMTP:pechtcha@cs.nyu.edu] wrote:
> On Sat, 26 Apr 2003, Phil Bewig wrote:
> 
> > I just killed setup.exe after over an hour of inactivity.  A total
> > of over 125MB of disk space has disappeared in the last few
> > hours while I have been running setup.exe, reading and
> > replying to email on the cygwin mailing list in this thread
> > using MS Outlook, and searching the cygwin mailing list
> > archives with MSIE.  When I killed setup.exe (using the
> > "cancel" button on the progress screen), I received a popup
> > message "Cannot open log file d:\/var/log/setup.log for
> > writing."  Are there any additional clues here?  What is
> > consuming disk?  And how do I get it back?
> >
> > Thanks again,
> > Phil
> 
> Phil,
> 
> Setup.exe first downloads the tarballs of the Cygwin packages from your
> chosen mirror to your local disk, into a subdirectory of the "Local
> Installation Directory".  If you're on a dial-up connection, it may take
> quite a while, depending on the number of packages you chose to install.
> Once all the packages are downloaded, setup.exe switches to the
> installation phase, where it installs the files contained in those
> packages (by unpacking them).  The third phase runs whatever postinstall
> scripts were in those packages.
> 
> My guess is that the space has been taken up by the local cache directory.
> Setup.exe runs in multiple threads.  The files are downloaded in a
> separate thread from the main thread (that handles Windows messages and
> updates the main window).  If the main thread is hung, downloads will
> still continue, giving the impression of disappearing disk space.  The
> fact that the "Cancel" button works means that the main thread is not
> truly hung, but something is probably screwed up with the sequencing logic
> somewhere...  It would be really nice to get a gdb backtrace, since it's
> so reproducible for you.
> 	Igor
> P.S.  FYI, larger packages (e.g., tetex) easily run into tens of megabytes
> -- 
> 				http://cs.nyu.edu/~pechtcha/
>       |\      _,,,---,,_		pechtcha@cs.nyu.edu
> ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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 think my situation is different.  I have already downloaded the
files and am installing from the copy of the *.bz2 files under the
d:\package directory.  All of the activity should be confined to
the d: drive, which has over 900MB free.  The space is being
consumed on the c: drive.  I assume the space is going into
the swap file at c:\windows\system\win386.swp, which is
currently at 78MB, although I don't know that for sure.  I could
verify that by resetting the swap file to zero bytes and running
setup again, but I don't know how to reset the swap file.

Besides the large space consumption on c:, my other question
is the error message, which implies a problem writing on d:.
There is certainly plenty of space.  Does anyone know what
combination of events could cause that error message?

I said earlier, but it may have been forgotten, that I had cygwin
installed on this machine about a year ago.  I uninstalled it
using the instructions in the faq.  Could anything be left over
from that old installation that is causing problems now?

Many thanks,

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/

RE: setup.exe: Woe is me!

[Phil Bewig]

On Saturday, April 26, 2003 8:49 PM, Greg McCrory [SMTP:greg@coolbrew.com] wrote:
> At 4/26/2003 08:13 PM -0500, Phil Bewig wrote:
> >I just killed setup.exe after over an hour of inactivity.  A total
> >of over 125MB of disk space has disappeared in the last few
> >hours while I have been running setup.exe, reading and
> >replying to email on the cygwin mailing list in this thread
> >using MS Outlook, and searching the cygwin mailing list
> >archives with MSIE.  When I killed setup.exe (using the
> >"cancel" button on the progress screen), I received a popup
> >message "Cannot open log file d:\/var/log/setup.log for
> >writing."  Are there any additional clues here?  What is
> >consuming disk?  And how do I get it back?
> >
> >Thanks again,
> >
> >Phil
> 
> 
> My firewall has gotten in the way many times with cygwin setup.  Try 
> disabling your firewall just during setup.  Also, maybe try using a 
> different mirror, you may be experiencing long network delays.  My cygwin 
> install dir currently contains 145 mb of downloaded data.
> 
> GMc
> 

On some of the attempts I started by rebooting the machine, not
enabling the DSL connection or the firewall, and running setup.  I
have no problem downloading the data; it is stored in d:\package,
from where I do a local install.  The problem happens after the
MD5 checksum.

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/

RE: setup.exe: Woe is me!

[Hannu E K Nevalainen (garbage mail)]

D:\> dir /s /o-s /a-d | more

 or maybe

D:\> dir /s /o-d /a-d | more

 might help a little...

/Hannu E K Nevalainen, Mariefred, Sweden 

--END OF MESSAGE-- 


--
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: setup.exe: Woe is me!

[Max Bowsher]

Phil Bewig wrote:
> I just killed setup.exe after over an hour of inactivity.  A total
> of over 125MB of disk space has disappeared in the last few
> hours while I have been running setup.exe, reading and
> replying to email on the cygwin mailing list in this thread
> using MS Outlook, and searching the cygwin mailing list
> archives with MSIE.  When I killed setup.exe (using the
> "cancel" button on the progress screen), I received a popup
> message "Cannot open log file d:\/var/log/setup.log for
> writing."  Are there any additional clues here?  What is
> consuming disk?  And how do I get it back?

OK, I'm taking a wild guess here, but just in case setup doesn't like the
'\/' in the install path, try setting your cygwin root to "d:\cygwin".


Also, where is the discspace disappearing? C: or D:? If D:, then if all you
have on that drive is Cygwin stuff, it should be easy to track down where
the space is going to?



Max.


--
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: setup.exe: Woe is me!

[Igor Pechtchanski]

On Sat, 26 Apr 2003, Phil Bewig wrote:

> I just killed setup.exe after over an hour of inactivity.  A total
> of over 125MB of disk space has disappeared in the last few
> hours while I have been running setup.exe, reading and
> replying to email on the cygwin mailing list in this thread
> using MS Outlook, and searching the cygwin mailing list
> archives with MSIE.  When I killed setup.exe (using the
> "cancel" button on the progress screen), I received a popup
> message "Cannot open log file d:\/var/log/setup.log for
> writing."  Are there any additional clues here?  What is
> consuming disk?  And how do I get it back?
>
> Thanks again,
> Phil

Phil,

Setup.exe first downloads the tarballs of the Cygwin packages from your
chosen mirror to your local disk, into a subdirectory of the "Local
Installation Directory".  If you're on a dial-up connection, it may take
quite a while, depending on the number of packages you chose to install.
Once all the packages are downloaded, setup.exe switches to the
installation phase, where it installs the files contained in those
packages (by unpacking them).  The third phase runs whatever postinstall
scripts were in those packages.

My guess is that the space has been taken up by the local cache directory.
Setup.exe runs in multiple threads.  The files are downloaded in a
separate thread from the main thread (that handles Windows messages and
updates the main window).  If the main thread is hung, downloads will
still continue, giving the impression of disappearing disk space.  The
fact that the "Cancel" button works means that the main thread is not
truly hung, but something is probably screwed up with the sequencing logic
somewhere...  It would be really nice to get a gdb backtrace, since it's
so reproducible for you.
	Igor
P.S.  FYI, larger packages (e.g., tetex) easily run into tens of megabytes
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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


--
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: setup.exe: Woe is me!

[Greg McCrory]

At 4/26/2003 08:13 PM -0500, Phil Bewig wrote:
>I just killed setup.exe after over an hour of inactivity.  A total
>of over 125MB of disk space has disappeared in the last few
>hours while I have been running setup.exe, reading and
>replying to email on the cygwin mailing list in this thread
>using MS Outlook, and searching the cygwin mailing list
>archives with MSIE.  When I killed setup.exe (using the
>"cancel" button on the progress screen), I received a popup
>message "Cannot open log file d:\/var/log/setup.log for
>writing."  Are there any additional clues here?  What is
>consuming disk?  And how do I get it back?
>
>Thanks again,
>
>Phil


My firewall has gotten in the way many times with cygwin setup.  Try 
disabling your firewall just during setup.  Also, maybe try using a 
different mirror, you may be experiencing long network delays.  My cygwin 
install dir currently contains 145 mb of downloaded data.

GMc



--
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: setup.exe: Woe is me!

[Phil Bewig]

I just killed setup.exe after over an hour of inactivity.  A total
of over 125MB of disk space has disappeared in the last few
hours while I have been running setup.exe, reading and
replying to email on the cygwin mailing list in this thread
using MS Outlook, and searching the cygwin mailing list
archives with MSIE.  When I killed setup.exe (using the
"cancel" button on the progress screen), I received a popup
message "Cannot open log file d:\/var/log/setup.log for
writing."  Are there any additional clues here?  What is
consuming disk?  And how do I get it back?

Thanks again,

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/

RE: setup.exe: Woe is me!

[Phil Bewig]

On Saturday, April 26, 2003 7:28 PM, Phil Bewig [SMTP:pbewig@swbell.net] wrote:
> On Saturday, April 26, 2003 4:39 PM, Igor Pechtchanski [SMTP:pechtcha@cs.nyu.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@cs.nyu.edu
> > ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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

Setup.exe has now been running for about 45 minutes
with no change.

I notice that something is consuming much disk space,
about 65MB of disk space since I cleaned up some
unneeded files earlier this afternoon, and about 15MB
in the last 15 minutes.  The only processes currently
active are device drivers, setup.exe, MS Outlook, and
MSIE, which has been browsing www.cygwin.com.
The firewall is active and reports two blocked attempts
to access my system while setup.exe has been
running.  Would setup.exe consume disk space at
that rate?  Why?

Thanks again,

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/

RE: setup.exe: Woe is me!

[Phil Bewig]

On Saturday, April 26, 2003 4:39 PM, Igor Pechtchanski [SMTP:pechtcha@cs.nyu.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@cs.nyu.edu
> ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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/

RE: setup.exe: Woe is me!

[Phil Bewig]

On Saturday, April 26, 2003 5:00 PM, Martin Gainty [SMTP:mgainty@hotmail.com] wrote:
> how much memory do you have available?
> M
> ----- Original Message -----
> From: "Max Bowsher" <maxb@ukf.net>
> To: <pbewig@swbell.net>; <cygwin@cygwin.com>
> Sent: Saturday, April 26, 2003 3:32 PM
> Subject: Re: setup.exe: Woe is me!
> 
> 
> > 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.
> >
> >
> >
> > --
> > 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/
> >
> >

96MB RAM.  The only processes active when performing the
installation, as reported by the ctrl-alt-delete task manager, were
device drivers for mouse, scanner, and Palm hotsync, as well as
Explorer.


--
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: setup.exe: Woe is me!

[Martin Gainty]

how much memory do you have available?
M
----- Original Message -----
From: "Max Bowsher" <maxb@ukf.net>
To: <pbewig@swbell.net>; <cygwin@cygwin.com>
Sent: Saturday, April 26, 2003 3:32 PM
Subject: Re: setup.exe: Woe is me!


> 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.
>
>
>
> --
> 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/
>
>

--
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: setup.exe: Woe is me!

[Igor Pechtchanski]

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@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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


--
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: setup.exe: Woe is me!

[Max Bowsher]

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.



--
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: setup.exe: Woe is me!

[Phil Bewig]

On Saturday, April 26, 2003 3:20 PM, Igor Pechtchanski [SMTP:pechtcha@cs.nyu.edu] wrote:
> On Sat, 26 Apr 2003, Phil Bewig wrote:
> 
> > I am having trouble installing cygwin on a machine running Win98.  I have
> > downloaded setup.exe to my machine, the latest version currently available.
> 
> Which is?..  Numbers help...
> 
> >  I have run setup.exe and downloaded the default selection of packages.
> >  Setup.exe has properly computed checksums.  Then setup.exe hangs.  I am
> > able to press ctrl-alt-delete to access the task window, which shows
> > setup.exe is not responding, and end the task.  I have tried several times
> > and setup.exe won't go past this point.  I never see the list of packages
> > available to select which ones to install.  There is no anti-virus software
> > running on the computer during installation.  No files are written in
> > /var/log.  My primary hard drive is c:, my cygwin directory is d:\ and my
> > package directory is d:\package.  I had cygwin installed on this machine
> > about a year ago, then uninstalled it, following the directions in the faq;
> > is it possible that something is left from the prior installation that is
> > causing the problem?  I don't know what to do next.  Can anyone help?
> >
> > Phil
> 
> How long did you leave setup "hanging" for?  If you haven't downloaded a
> snapshot from <http://cygwin.com/setup-snapshots/>, you are likely to be
> the victim of a "rush job" traversal algorithm for the package list (see
> <http://cygwin.com/ml/cygwin/2003-04/msg01150.html>).  This should be
> fixed in the 2.358 snapshot.  Or you could simply wait "a minute"
> (<http://cygwin.com/ml/cygwin/2003-04/msg02256.html>).
> 	Igor
> -- 
> 				http://cs.nyu.edu/~pechtcha/
>       |\      _,,,---,,_		pechtcha@cs.nyu.edu
> ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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

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?

Many thanks for your kind assistance.

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/

Re: setup.exe: Woe is me!

[Igor Pechtchanski]

On Sat, 26 Apr 2003, Phil Bewig wrote:

> I am having trouble installing cygwin on a machine running Win98.  I have
> downloaded setup.exe to my machine, the latest version currently available.

Which is?..  Numbers help...

>  I have run setup.exe and downloaded the default selection of packages.
>  Setup.exe has properly computed checksums.  Then setup.exe hangs.  I am
> able to press ctrl-alt-delete to access the task window, which shows
> setup.exe is not responding, and end the task.  I have tried several times
> and setup.exe won't go past this point.  I never see the list of packages
> available to select which ones to install.  There is no anti-virus software
> running on the computer during installation.  No files are written in
> /var/log.  My primary hard drive is c:, my cygwin directory is d:\ and my
> package directory is d:\package.  I had cygwin installed on this machine
> about a year ago, then uninstalled it, following the directions in the faq;
> is it possible that something is left from the prior installation that is
> causing the problem?  I don't know what to do next.  Can anyone help?
>
> Phil

How long did you leave setup "hanging" for?  If you haven't downloaded a
snapshot from <http://cygwin.com/setup-snapshots/>, you are likely to be
the victim of a "rush job" traversal algorithm for the package list (see
<http://cygwin.com/ml/cygwin/2003-04/msg01150.html>).  This should be
fixed in the 2.358 snapshot.  Or you could simply wait "a minute"
(<http://cygwin.com/ml/cygwin/2003-04/msg02256.html>).
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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


--
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/

setup.exe: Woe is me!

[Phil Bewig]

I am having trouble installing cygwin on a machine running Win98.  I have 
downloaded setup.exe to my machine, the latest version currently available. 
 I have run setup.exe and downloaded the default selection of packages. 
 Setup.exe has properly computed checksums.  Then setup.exe hangs.  I am 
able to press ctrl-alt-delete to access the task window, which shows 
setup.exe is not responding, and end the task.  I have tried several times 
and setup.exe won't go past this point.  I never see the list of packages 
available to select which ones to install.  There is no anti-virus software 
running on the computer during installation.  No files are written in 
/var/log.  My primary hard drive is c:, my cygwin directory is d:\ and my 
package directory is d:\package.  I had cygwin installed on this machine 
about a year ago, then uninstalled it, following the directions in the faq; 
is it possible that something is left from the prior installation that is 
causing the problem?  I don't know what to do next.  Can anyone 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/