Re: EOL for Windows 95/86/Me

I have not run cygwin for a long while on my win98. I think the only real use I have had of the dll was with clamav. I usually scan the windows from by Debian boot. However, keeping a win9* dll available for such applications is desirable I think. I guess once support for Win98 is gone, I will

Re: EOL for Windows 95/86/Me, PS

As the basis of an opensource X windows that will work on win9*, the dll version would also be desirable. Use it with ssh, colinux, etc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.c

Re: commands not found

I cured it when I had to, for other reasons, reinstall. Place the setups in one directory and should be OK. Having a separate setup in a "package" directory caused the problem. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.ht

Re: startup problem // no longer works // profile not called

I nuked and restored the Windows disk from partimage saves (attempting to correct a problem unrelated to Cygwin). Partimage is a bit too finicky about the size of the destination partition, test full size and aborts even if the "used data" fill fit! As I was unable to recreate the partition I ha

Re: startup problem // no longer works // profile not called

All of these posters are complaining about the same thing. Not at all a bad idea to read the bash man page, the helps, everything. But the fact is once clicking the Cygwin icon gave one an operating shell. It no longer does. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Pro

Re: Startup problem

There must be something wrong with recent setups. Once upon a time, running the cygwin.bat brought up bash, went through a series of startup/login scripts and then it worked. Now, as the poster said, bash and nothing works. One is NOT in the home directory but actually in the /usr/bin but no pa

Re: No longer works.

Some more results: 1. The reason why the bash terminal window flashes and aborts is that it was referencing the setup cygwin.bat!!!. Changing the command line to the cygwin folder as it should be yields a window that stays open. 2. The startup sequence that once set up the paths and other stuff

Re: No longer works.

OK -- here is the result of cygcheck: Cygwin Win95/NT Configuration Diagnostics Current System Time: Wed Oct 13 15:39:28 2004 Windows 98 Ver 4.10 Build 1998 Path: C:\ C:\WIN98 C:\WIN98\COMMAND C:\WIN98\SYSTEM32 C:\WIN98\SYSTEM C:\PROGRA~1\EXECUT~1\DISKEE~5 C:\PROGRA~1\INTERAD\BUILDI~1 C

Re: No longer works.Igor Pechtchanski

On Monday 04 October 2004 19:09, Igor Pechtchanski wrote: > You have apparently missed the part of the Cygwin problem reporting > guidelines () that asks you to attach (as > an uncompressed text *attachment*) the output of "cygcheck -svr" from your > Cygwin installa

Re: No longer works.Igor Pechtchanski

On Monday 04 October 2004 16:37, Igor Pechtchanski wrote: > On Mon, 4 Oct 2004, David Baron wrote: > > After an errant upgrade using the one cited "don't use", after upgrading > > sequesuently to good version, Cygwin no longer works. The "login > > sequ

No longer works.

(Sorry if this has been hashed out before. Searching the archives yielded too much forest to find my sapling :-) Thanks in advance for any help.) After an errant upgrade using the one cited "don't use", after upgrading sequesuently to good version, Cygwin no longer works. The "login sequence" t