The Fatal Error is a general error message. More specific information what caused this is available in /tmp/XWin.log. Please check the common error messages in the Section called Error and Warning Messages. If you're error is not mentioned proceed with Q: 7.4.

Below is a list of the main error messages you will see while searching the Wayback Machine. If you see an error message that does not have the Internet Archive Wayback Machine logo in the upper left corner, you are most likely looking at an archived page or the live web. Failed Connection: The server that the particular piece of information lives on is down. Generally these clear up within two weeks. Robots.txt Query Exclusion: A robots.

This error message means that a Cyclic Redudancy Check failed during some operation, most likely while gzip'ing or un-gzip'ing a file. Possible causes of this error include an incomplete gzip operation, and hardware failure. A brute-force way to recover from this error is to remove the rdiff-backup-data directory. However, this will remove all of your past increments. A better approach may be to delete the particular file that is causing the problem. A command like: will find the failing file.

Cygwin/X is a port of the X Window System to Cygwin. Cygwin provides a UNIX-like API on the Win32 platform.

Cygwin/X supports Windows 95, Windows 98, Windows Me, Windows NT 4.0, Windows 2000, Windows XP, and Windows Server 2003 as of 2003-12-29. Cygwin/X requires Cygwin to compile and run. Cygwin is not, as of 2003-12-29, available on Microsoft Windows CE, therefore Cygwin/X is not currently available on Microsoft Windows CE.

Zone Alarm 5 is known to break Cygwin/X. As a result you'll see this line (or a similar) as last output in /tmp/XWin.log Rules = "xorg" Model = "pc101" Layout = "us" Variant = "(null)" Options = "(null)" Disabling Zone Alarm will not solve this problem. You can only uninstall Zone Alarm 5 and switch to an earlier version (4.5 is known to work) or use a different personal firewall. Another reason is /tmp mounted in textmode.

Cygwin/X uses the gcc compiler from the Free Software Foundation. Cygwin/X source code is mostly ANSI C compliant, but we cannot guarantee that Cygwin/X will compile with any other compiler, nor can we afford the time to support compilers other than gcc.

Starting with OpenSSH 3.8 you will need to set "ForwardX11Trusted yes" in the client configuration to allow remote clients full access to the xserver.

Yes, Cygwin/X has a mailing list, namely, cygwin-xfree@cygwin.com. Visit the Cygwin Mailing Lists page to subscribe to cygwin-xfree@cygwin.com as well as to read and search an online archive of the mailing list traffic. Tip: Post your X-related inquires to cygwin-xfree@cygwin.com only; do not post nor cross post your inquires to the cygwin@cygwin.com mailing list. Cygwin's mailing list is only for Cygwin related inquires that are not handled by another more-specific list.

The Cygwin/X User's Guide thoroughly documents the installation process. Installation is performed through Cygwin's setup.exe program.

Only submit patches that have UNIX end of line characters. See Q: 10.2. for information on editors for Windows that are aware of UNIX end of line characters. Generally it is better for us if you generate your patches against the X.org CVS tree. For example, run cvs -z4 diff -U3 hw/xwin/ from xc/programs/Xserver/ to generate a diff file for all the modified files in hw/xwin/.

A : When GCC reports a "signal", it really means that an error occurred trying to run one of the compiler passes. The "signal" number is the DOS error code, and 2 means "file not found" (dig out your DOS reference for other error codes). This means GCC couldn't find some program it needs to run to compile your source. Check the COMPILER_PATH environment variable or what the COMPILER_PATH line in the DJGPP.ENV file says, and make sure they point to the directory where DJGPP programs reside.

The problem is most likely a wrong DNS (Network name resolution). Make sure your windows host has a hostname which is valid from linux too and an IP address which linux can resolve to that hostname. myhost to /etc/hosts on the XDMCP server with the IP address and the hostname of your windows host the name resolution should work. Mika Laitio] For security reasons, XDMCP is not enabled by default on most Linux/UNIX/*NIX/*BSD distributions (RedHat, Mandrake, SuSE, FreeBSD, NetBSD, etc.) by default.

Perl: If you think this is right, and you still get this error, it may mean your server is not passing the DOCUMENT_URI environment variable, in which case the script probably won't work. However, one way to tell if you have the @valid_uri variable set right is to change this to:

This means that when the TextCounter CGI script tried to automatically create your count file for the new web page, it was unable to do so, possibly due to a permissions problem. Make sure that the data_dir is chmoded 666 so that the web server has access to write to it. Also make sure that data_dir contains the correct path to this directory.

This means that the TextCounter program found the file but couldn't open it up and write to it. Try chmoding it 666.

Turn on the auto-create option, generate the count files for the pages you want to allow to have textcounters, then turn off the auto-create option afterwards. If you are not the owner of this script, the administrator of the script has the option to disallow auto-creating of counters. Talk to the person who owns the script if you don't have access to modify the auto-create variable.