Re: Still getting Signal 11 error msg
Attaching cygcheck output is something that Fergus has seemed reluctant to do. The cygwin problems page also has a lot of tips for reporting problems, one of which is to not send email with vague subjects. Sorry -- I was at fault on both counts. Thank you Chris, Harold and Jan for picking this up. You have helped greatly, as follows: Start - Run - start XWin -multiwindow Start - Run - run rxvt -display localhost:0.0 -e bash --login -i xdvi a4.dvi Signal 11 xdvi.bin a4.dvi ** successful presentation to screen of a4.dvi ** My reluctance to attach cygcheck output stems from not knowing what's best to send. So here (two attachments) is the output from cygcheck -c (I understand some or all Incompletes not to matter) and from cygcheck -srv. Thanks again for all your help. I appreciate it. Fergus cygcheck.srv Description: Binary data cygcheck.c Description: Binary data
Re: XFree86 goes into stasis when NetMeeting is running
Try adding -engine 1 to the XWin command line which should use GDI calls instead of DirectX calls to draw. NetMeeting probably grabs the surface and doesn't release it until you quit. I'll try it. What are the pros and cons of using GDI instead of DirectX? Thanks. Jeff -- Jeffrey C. Honig [EMAIL PROTECTED] http://www.honig.net/jch GnuPG ID:14E29E13 http://www.honig.net/jch/key.shtml
Re: Still getting Signal 11 error msg
On Sun, Sep 14, 2003 at 12:21:27PM +0100, [EMAIL PROTECTED] wrote: My reluctance to attach cygcheck output stems from not knowing what's best to send. So here (two attachments) is the output from cygcheck -c (I understand some or all Incompletes not to matter) and from cygcheck -srv. Thanks again for all your help. I appreciate it. http://cygwin.com/problems.html shows the correct cygcheck options to provide.
Re: Latest CVS Compilation error
Colin Harrison wrote:
To build I had to remove typedef MessageType; from winmsg.h in Xwin.
Clashes with defs in os/log.c after latest mods to move log handling to DIX.
The patch is attached.
This patch is _only_ for the xfree86 HEAD. _Not_ for the 4_3_Branch.
It forwards the winMsg functions to the LogMessage functions which were
introduces short time ago.
bye
ago
NP: Wumpscut - Embryodead
--
[EMAIL PROTECTED]
http://www.gotti.org ICQ: 126018723Index: winmsg.h
===
RCS file: /cvs/xc/programs/Xserver/hw/xwin/winmsg.h,v
retrieving revision 1.1
diff -u -r1.1 winmsg.h
--- winmsg.h17 Oct 2002 08:18:22 - 1.1
+++ winmsg.h14 Sep 2003 18:47:49 -
@@ -32,31 +32,6 @@
#ifndef __WIN_MSG_H__
#define __WIN_MSG_H__
-
-#define __msg_name(name,string) name
-#define __msg(name,string) __msg_name(name,string)
-#define _msg(name,string) __msg(name,string),
-
-#define MESSAGE_STRINGS \
-_msg(X_PROBED,(--)/* Value was probed */)\
-_msg(X_CONFIG,(**)/* Value was given in the config file */)\
-_msg(X_DEFAULT,(==) /* Value is a default */)\
-_msg(X_CMDLINE,(++) /* Value was given on the command line */)\
-_msg(X_NOTICE,(!!)/* Notice */) \
-_msg(X_ERROR,(EE) /* Error message */) \
-_msg(X_WARNING,(WW) /* Warning message */) \
-_msg(X_INFO,(II) /* Informational message */) \
-_msg(X_UNKNOWN,(??) /* Unknown, trigraph fix */) \
-_msg(X_NONE,NULL/* No prefix */) \
-__msg(X_NOT_IMPLEMENTED,(NI) /* Not implemented */)
-
-typedef enum
-{
- MESSAGE_STRINGS
-}
-MessageType;
-
-
/*
* Function prototypes
*/
Index: winmsg.c
===
RCS file: /cvs/xc/programs/Xserver/hw/xwin/winmsg.c,v
retrieving revision 1.1
diff -u -r1.1 winmsg.c
--- winmsg.c17 Oct 2002 08:18:22 - 1.1
+++ winmsg.c14 Sep 2003 18:47:49 -
@@ -45,26 +45,7 @@
winVMsg (int scrnIndex, MessageType type, int verb, const char *format,
va_list ap)
{
- const char *prefix = NULL;
-
- if (verb verb VERBOSE_LEVEL)
-return;
-
-#undef __msg
-#define __msg(name,string) case name: prefix = string; break;
-#undef _msg
-#define _msg(name,string) __msg(name,string)
- switch (type)
-{
- MESSAGE_STRINGS default:prefix = NULL;
- break;
-}
-#undef __msg
-#undef _msg
-
- if (prefix != NULL)
-ErrorF (%s , prefix);
- VErrorF (format, ap);
+ LogVMessageVerb(type, verb, format, ap);
}
@@ -73,7 +54,7 @@
{
va_list ap;
va_start (ap, format);
- winVMsg (scrnIndex, type, 0, format, ap);
+ LogVMessageVerb(type, 0, format, ap);
va_end (ap);
}
@@ -83,7 +64,7 @@
{
va_list ap;
va_start (ap, format);
- winVMsg (0, type, 0, format, ap);
+ LogVMessageVerb(type, 0, format, ap);
va_end (ap);
}
@@ -94,7 +75,7 @@
{
va_list ap;
va_start (ap, format);
- winVMsg (scrnIndex, type, verb, format, ap);
+ LogVMessageVerb(type, verb, format, ap);
va_end (ap);
}
@@ -104,7 +85,7 @@
{
va_list ap;
va_start (ap, format);
- winVMsg (0, type, verb, format, ap);
+ LogVMessageVerb(type, verb, format, ap);
va_end (ap);
}
@@ -114,6 +95,6 @@
{
va_list ap;
va_start (ap, format);
- winVMsg (0, X_NONE, verb, format, ap);
+ LogVMessageVerb(X_NONE, verb, format, ap);
va_end (ap);
}
Re: Latest CVS Compilation error
Colin Harrison wrote: My XWin.log no longer shows config file output e.g. lines like:- (==) winConfigKeyboard - Layout: 0809 (==) Using preset keyboard for English (United Kingdom) (0809), type 4 Is this as intended? No, I think I'll have to initialize the logging somehow. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: XFree86 goes into stasis when NetMeeting is running
Jeffrey, Netmeeting and Cygwin/XFree86 in fullscreen mode both need an exclusive lock on DirectDraw. At least, that is what makes sense to me. One way around this is to use the -engine 1 command-line parameter for XWin.exe. This will tell XWin.exe to use the GDI based (i.e. non-DirectDraw) engine to draw its graphics. You will notice it is a little more sluggish than the DirectDraw engine (which is used by default), but it will solve your problems with NetMeeting. Let us know if this works for you, Harold Jeffrey C Honig wrote: I've recently switched back to Cygwin/XFree86 from Exceed (ugh) and rediscovered a problem. I'm running XFree86 with -fullscreen on my Win2k laptop. Whenever I start NetMeeting to join a call, XFree86 will no longer display until I exit NetMeeting. If I use Alt-Tab to switch to XFree86, it will not be restored. As soon as I exit NetMeeting I am able to switch to XFree86 again. What gives? Thanks. Jeff
Re: Latest CVS Compilation error
Alexander Gottwald wrote: No, I think I'll have to initialize the logging somehow. I'll adjust the error handling (including our own VErrorF function) to use new log functions. The new log functions do use a buffer, so redirecting the messages to another file (or stdout) is now possible too. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
[ANNOUNCEMENT] Server Test 99
Links: I just posted Test 99 to the server development page: http://xfree86.cygwin.com/devel/shadow/ You can install the Test 99 package via setup.exe by selecting the following version of the XFree86-xserv package: 4.3.0-9 Server Test Series binary and source code releases are now available via the sources.redhat.com ftp mirror network (http://cygwin.com/mirrors.html) in the pub/cygwin/xfree/devel/shadow/ directory. You may wish to note the desired filename in the links below, then download from your closest mirror (http://cygwin.com/mirrors.html). Server binary, direct link: http://www.msu.edu/~huntharo/xwin/shadow/XWin-Test99.exe.bz2 (1265 KiB) Server source, direct link: http://www.msu.edu/~huntharo/xwin/shadow/xwin-20030914-1740.tar.bz2 (127 KiB) xc/programs/Xserver/hw/xwin (all files) diff against Test98 source code: http://www.msu.edu/~huntharo/xwin/shadow/xwin-Test98-to-Test99.diff (12 KiB) Changes: 1) winmultiwindowwm.c - Add handling for WM_CHANGE_STATE IconicState messages; minimize the associated Windows window when these messages are received. (Harold L Hunt II) Harold
Updated on sourceware: XFree86-xserv-4.3.0-9
The XFree86-xserv-4.3.0-9 package has been updated in the Cygwin distribution. Changes: 1) winmultiwindowwm.c - Add handling for WM_CHANGE_STATE IconicState messages; minimize the associated Windows window when these messages are received. (Harold L Hunt II) -- Harold Hunt To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'XFree86-xserv' from the 'XFree86' category. You may need to click the Full button if it doesn't show up. Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update. In the US, ftp://archive.progeny.com/cygwin/ is a reliable high bandwidth connection. In Japan, ftp://ftp.u-aizu.ac.jp/pub/gnu/gnu-win32/ is usually up-to-date. In DK, http://mirrors.sunsite.dk/cygwin/ is usually up-to-date. If one of the above doesn't have the latest version of this package you can either wait for the site to be updated or find another mirror. Please send questions or comments to the Cygwin/XFree86 mailing list at: [EMAIL PROTECTED] . If you want to subscribe go to: http://cygwin.com/lists.html I would appreciate if you would use this mailing list rather than emailing me directly. This includes ideas and comments about the setup utility or Cygwin/XFree86 in general. If you want to make a point or ask a question the Cygwin/XFree86 mailing list is the appropriate place.
Re: Latest CVS Compilation error
Sounds good. Please resubmit your earlier patch when you have this completed. It doesn't look like it would be a good idea to implement it one half at a time. However, we can certainly wait on trying to make the log either output to stdout or to a file... that could take some time to get right. Harold Alexander Gottwald wrote: Alexander Gottwald wrote: No, I think I'll have to initialize the logging somehow. I'll adjust the error handling (including our own VErrorF function) to use new log functions. The new log functions do use a buffer, so redirecting the messages to another file (or stdout) is now possible too. bye ago
Re: Setup bug --- probably already reported and fixed, of course[Scanned]
On Sat, 2003-08-02 at 01:30, Harold L Hunt II wrote: FYI --- In further testing, archive.progeny.com is the mirror that has not been updated yet. Selecting only archive.progeny.com gives me the warning about setup.ini being older than when I last installed Cygwin. Selecting only mirrors.rcn.net does not give such a warning and correctly indicates that the XFree86-bin tarball is roughly 10500 KiB and downloads it and all other tarballs with no problems. Thus, this does not so far appear to be entirely my fault. When you updated the X tarballs, did you bump the version number for the tarballs? (i.e. did they have -unique- file names compared to the existing tarballs?) Cheers, Rob -- GPG key available at: http://members.aardvark.net.au/lifeless/keys.txt. --- signature.asc Description: This is a digitally signed message part
