Re: Incorrect version in packages names
- Original Message - From: Christopher Faylor [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 08, 2002 4:16 PM and in setup.ini : @ kdelibs-2 Get rid of this. I suspect that it is confusing setup.exe. It should certainly do the right thing without it. Doh!. Good catch Chris. Yes, foo-bar is allowable as a package name, foo-2 is not. I'll see what I can do for a future setup.exe release to address this, but don't expect anything soon. It'll require altering the installed.db database format, which results in a non-backwards compatible local environment. Rob
Re: Incorrect version in packages names
- Original Message - From: Christopher Faylor [EMAIL PROTECTED] To: [EMAIL PROTECTED] upset would probably do the right thing with the above but I really don't see any reason to use it, regardless. I don't see any reason why a user would need to know that these are kdelibs-2 when it is pretty obvious from the version number. One possibility is if the version number reflects the ABI, not the software release. This is actually quite likely with libtool packages. Anyway, it's low priority however one approaches it. Rob
Re: Cross Compiling
On Mon, 8 Jul 2002, Harold Hunt wrote: Yup, cross compiling is toroughly broken right now. It will take awhile to get it working properly. I'd appreciate it if anyone that is cross compiling the current XFree86 cvs would send in their host.def, any modification they made to cygwin.cf, etc. and their build command. I will send it on Thursday. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
RE: xf86config patch
On Mon, 8 Jul 2002, Harold Hunt wrote: Could you send me a sample and/or skeleton (containing commented versions of each config option) config file? http://www-user.tu-chemnitz.de/~goal/xfree/test-config-1/X-Server.tar.bz2 contains a sample config file. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Using only the X server of Cygwin
On Mon, 8 Jul 2002 5:05 am, Rhialto wrote: Hi, I am not subscribed to this mailing list but I would like to give some feedback anyway. Please Cc: any responses to me. I am testing the Cygwin/XFree server to use it as a remote display for my Unix box which runs xdm: XWin -broadcast. So in the installer I choose to de-install All, and to install *only* XFree86-xserv. I noted that the installer installed a lot of things that are not necessary for that, such as header files, info files, terminfo stuff, static link libraries, xterm, sh, twm, etc. And it downloaded a lot more which it apparently did not even install, such as bash, diff, diffutils, fileutils, etc. I could also do without all those megabytes of fonts, since I have a perfectly ok font server, but apparently no way to specify it for the X server. I got a XDMCP session going on Cygwin-XFree86 around September 2001 using nothing but bash.exe cut.exe cygpath.exe cygwin1.dll cygz.dll grep.exe mkdir.exe mount.exe pwd.exe rgb.txt rm.exe SecurityPolicy sleep.exe test.exe touch.exe umount.exe XWin.exe and a bash script called winxterm.sh. You can do without the script (and therefore bash, cut, grep, sleep, test, touch and mkdir and so on) but the script automatically uses the next display number available (ie, if there is already a display on port 6000, it would try 6001, etc). The script is available at http://www.webone.com.au/~rasjidw/winxterm.sh NOTE: The script *will* need updating to deal with changes to XWin.exe that have occured since September last year. I have not got around to doing this, and probably will not do so. Last year I got part way through creating a nice GUI interface, but decided to wait until the setup.exe process was finished (which it now is), and have not got back to it yet. Others have had similar ideas. See http://xlauncher.sourceforge.net for example. My GUI was being written in Python/wxWindows. It is not really at the point of being worth sharing, as it has to be largely redone due to the setup.exe thing being finished. (Yay!) Given a recent discussion on the list, I will probably try and resurrect my Python/wxWindows code, unless someone wants to take up the challenge of a c / c++ version. Rasjid.
Re: Using only the X server of Cygwin
A while back I did some work creating a standalone XDMCP client, more as a test than anything. Xwin depends on cygz.dll cygwin1.dll as ago said. Xwin complains if it doesn't have rgb.txt, this can be put anywhere though and its location specified in the Xwin command line (needs a cygwin style path to the file though). Xwin still needs a /tmp. If cygwin isnt installed properly, then / will default to the root of the drive Xwin is running from (normally c:). It needs this folder for several reasons, it creates Xwin.log here, and a local socket .X11-unix (can be stopped passing '-nolisten local' to Xwin). It also needs /tmp if loading xkb keymaps. /tmp can be mounted whereever you like using cygwins mount command, this will be remembered for when you then run Xwin (hence xkb's and Xwin.log can go where you like). Mount only depends on cygwin1.dll fonts aren't required if you specify a font server using Xwin cmdline parameters. I've found out most of this since I wrote my XDMCP client, but its available at http://www.jeremywilkins.freeserve.co.uk/eXtend/ warning this is a VB6 app so probably isn't gpl'd. Hope this helps. Jeremy
Re: Cross Compiling
--- Harold Hunt [EMAIL PROTECTED] wrote: Yup, cross compiling is toroughly broken right now. It will take awhile to get it working properly. I'd appreciate it if anyone that is cross compiling the current XFree86 cvs would send in their host.def, any modification they made to cygwin.cf, etc. and their build command. Harold I did a little research and indeed it is those damn SuSE people who broke the cross compiling system! Take a look at: http://www.xfree86.org/~keithp/xconf2001/cc-imake.pdf and see if that doesn't seem like it fits the current case. Note their desire to modify the imake source file instead of cross.def. This might explain why the build fails when it tries to compile imake. P.S. - Did that CVS command to remove stickiness work for you? __ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com
RE: New xlauncher (was: Re: Success with Java prog in XFree)
Actually, I am just about to add per-user registry support, so you might as well use the registry. Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rasjid Wilcox Sent: Monday, July 08, 2002 6:33 AM To: Tim Thomson; [EMAIL PROTECTED] Subject: Re: New xlauncher (was: Re: Success with Java prog in XFree) On Mon, 8 Jul 2002 7:08 am, Tim Thomson wrote: snip I would prefer that xlauncher, or a variant be installable via setup.exe, so it can be used by anyone. If it means porting/rewriting, I'll give it a shot :) (There isn't all that much code there, most is just writing to registry, and reading it back. Which is another thing, would it be better to use a config file rather than registry? Currently, I'm writing to HKEY Local Machine, but should be writing to current user, so that people with few rights on an NT style box can use it. If I were to use a config file, where to put it?) Personally, I would go for a config file. As mentioned in another post of mine, I was working on a Python/wxWindows GUI. I can send you what I've done if you are interested. My most recent thoughts was to create a generic 'Remote X desktop' launcher, which would run on Windows (with Cygwin-XFree86 backend) and on Linux/Unix (with a XNest backend), and possibly Mac. Further plans were to include support for other remote display tools like VNC. I was also considering switching to Java (due to better IDE's available), although the discussion here as left me unsure. Is the GNU compiler able to deal with Java/Swing, or is Python/wxWindows a better 'pure open source' option? Anyway, Tim, if you want to do it in C/C++, I'll help test/debug, but I can't really help code. OTOH, if Python/wxWindows interests you, I'd help with the coding too. If you know C, Java and Pascal, I'd say you could pick up Python in a day. :-) Rasjid.
Re: Cross Compiling
On Mon, 8 Jul 2002, Nicholas Wourms wrote: I did a little research and indeed it is those damn SuSE people who broke the cross compiling system! Take a look at: http://www.xfree86.org/~keithp/xconf2001/cc-imake.pdf Interesting article. I'll check what is needed to get current CVS cross- compile in that build environment. and see if that doesn't seem like it fits the current case. Note their desire to modify the imake source file instead of cross.def. This might explain why the build fails when it tries to compile imake. I made the following changes to build imake (the diff I'll send Thursday will show this in complete) - set BOOTSTRAPCFLAGS to -Ulinux -D__CYGWIN__ - pass IMAKE_DEFINES=-Ulinux -D__CYGWIN__ to imake also there are a lot of changes need where some programs are build as ProgramTarget but should be HostProgramTarget and another big problem in cygwin.rules where all: tries to build $(addsuffix .exe,PROGRAMS) instead of $(PROGRAMS). This results in No rule to make target bitmap.exe.exe and so on. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Cross Compiling
Alexander, Interesting article. I'll check what is needed to get current CVS cross- compile in that build environment. Okay. I made the following changes to build imake (the diff I'll send Thursday will show this in complete) - set BOOTSTRAPCFLAGS to -Ulinux -D__CYGWIN__ - pass IMAKE_DEFINES=-Ulinux -D__CYGWIN__ to imake also there are a lot of changes need where some programs are build as ProgramTarget but should be HostProgramTarget and another big problem in cygwin.rules where all: tries to build $(addsuffix .exe,PROGRAMS) instead of $(PROGRAMS). This results in No rule to make target bitmap.exe.exe and so on. Unfortunately, the new cross compile system doesn't really use BOOTSTRAPCFLAGS or IMAKE_DEFINES anymore. You're supposed to pass the make variable CROSSCOMPILEDIR=/cygwin/i686-pc-cygwin/bin, for example. This flag in turn causes CrossCompiling to be set and it causes certain new macros for the name of the CC program, etc. to be set. However, all of these macro names are different than what we used to use in our host.def, so we've got to figure out what to do now. It is going to be a real pain. I estimate that it will take about 5 hours to fix properly. Harold
Problem with cygwin1.dll and xfree
The last two version of cygwin1.dll ( 1.13.12 and 1.13.11 ) seem not to work with the xfree release code. It appears that the code fails when run under the list DLLs. If I switch back to the version prior to 1.13.11, all works as advertised. Does anyone else have the same problem? Does anyone know if a patch exists to allow the xfree code to run under the latest cygwin1.dll? Sanford Sandy Zelkovitz (ZeroChaos) EDS - GWH Web Engineering 750 Tower Dr, M/C 5291 Troy, MI 48098 * phone: +01-248-265-2277 (8-365) * mailto:[EMAIL PROTECTED] www.eds.com
Re: Incorrect version in packages names
Christopher Faylor wrote: upset would probably do the right thing with the above but I really don't see any reason to use it, regardless. I don't see any reason why a user would need to know that these are kdelibs-2 when it is pretty obvious from the version number. The naming was probably inherited from linux, where it is possible to have both kde (1) and kde (2) and kde (3) all installed on the same machine. Therefore, each needs different basename. If the kde-cygwin folks want to maintain that package-name distinction, then they should just use kdelibs_2 instead of kdelibs-2 as their basename. Then upset and setup will be happy -- and end users will be able to install both kdelibs_2 and kdelibs_3. --Chuck
Re: [PATCH] -scrollbars option
Jehan, Excellent. I'll try to merge this tonight. Harold Jehan [EMAIL PROTECTED] said: Harold Hunt wrote: However, there are a bunch of ^M's showing up in the patch file for winwndproc.c starting at about line 496 (in the patch file). Could you clean that up and resubmit? Hmm, I wonder were they are coming from, I was editing the file in Unix mode. Anyway, here it is. Jehan
RE: Emailing: XWin.log
Robert, The Windows dump file won't be of any help. However, you could send in /etc/setup/installed.db. That way we know what versions of things you have. There have been several significant Cygwin/XFree86 updates since the 26 of June. I highly advise that you update. Harold Robert Taylor [EMAIL PROTECTED] said: Would the setup.log file help? How about the Windows dump file? My installation was 6/26/2002 from setup.exe via redhat -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 9:40 AM To: [EMAIL PROTECTED]; Robert Taylor; [EMAIL PROTECTED] Subject: Re: Emailing: XWin.log Robert, [For others: this is a followup to a post on ./ where Robert said that Windows XP rebooted when he ran XWin.exe] There doesn't seem to be any error recorded, at all. Try downloading the latest setup.exe (http://cygwin.com/setup.exe) and update your XFree86-xserv package. Make sure that you get version 4.2.0-10. Perhaps this was just a bug in some earlier version. Thanks for the log file, Harold Robert Taylor [EMAIL PROTECTED] said: Harold, I hope this is helpful. Robert J. Taylor
problems with remote display
I'm sorry for my poor english but i don't kwown it very well .I'm a programmer and I'd like unix but unfortunately j have to work on windows paltform so i have installed cygwin on my windows 2000 workstation. Actualy i have the latest version of cygwin (1.3.12-1) and Xwin (4.2.0-7) installed. If i run the X-server locally with the command startx from a bash shell all seems function correctly but if i try to run a remote dislplay on aHP_UX unix server whit the command startx -- -query ip-of-remote-machine the following message appear on the console : .. Xlib: connection to :0.0 refused by server Xlib: No protocol specified Here follow the content of the file Xwin.log found in /tmp ddxProcessArgument () - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winDetectSupportedEngines () - Windows NT/2000 winDetectSupportedEngines () - DirectDraw installed winDetectSupportedEngines () - Allowing PrimaryDD winDetectSupportedEngines () - DirectDraw4 installed winDetectSupportedEngines () - Returning, supported engines 001f winSetEngine () - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL () - Using Windows display depth of 24 bits per pixel winAdjustForAutoHide - Original WorkArea: 0 0 768 1024 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 767 1024 winCreateBoundingWindowWindowed () - WindowClient w 1018 h 742 r 1018 l 0 b 742 t 0 winCreateBoundingWindowWindowed () - Returning winAllocateFBShadowDDNL () - lPitch: 3056 winInitVisualsShadowDDNL () - Masks 00ff ff00 00ff BPRGB 8 d 24 winCreateDefColormap () - Deferring to fbCreateDefColormap () winScreenInit () - returning AUDIT: Mon Jul 8 09:16:54 2002: 1320 X: client 1 rejected from local host AUDIT: Mon Jul 8 09:16:56 2002: 1320 X: client 1 rejected from local host AUDIT: Mon Jul 8 09:16:58 2002: 1320 X: client 1 rejected from local host AUDIT: Mon Jul 8 09:17:00 2002: 1320 X: client 1 rejected from local host AUDIT: Mon Jul 8 09:17:02 2002: 1320 X: client 1 rejected from local host AUDIT: Mon Jul 8 09:17:04 2002: 1320 X: client 3 rejected from local host AUDIT: Mon Jul 8 09:17:06 2002: 1320 X: client 4 rejected from local host winCloseScreenShadowDDNL () - Freeing screen resources If i use a commercial product like X-reflection j obtain a remote display correctly. Can someone help me ?
Re: Incorrect version in packages names
and in setup.ini : kdelibs-2 Get rid of this. I suspect that it is confusing setup.exe. Found in /etc/setup/installed.db : kde-x-1.2 kde-x-1.2-1.2-1.2-1.2-1.2-1.2-1.2-1.2-1.2.tar.bz2 0 kde-x-1.3 kde-x-1.3-1.3-1.3-1.3-1.3-1.3-1.3-1.3-1.3.tar.bz2 0 kdebase-2 kdebase-2-2-2-2-2-2-2-2-2.2.2-b1.tar.bz2 0 kdelibs-2 kdelibs-2-2-2-2-2-2-2-2-2.2.2-b1.tar.bz2 0 ___ Do You Yahoo!? -- Une adresse yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Re: problems with remote display
Claudio, You can use ``startx -- -query ip_of_remote_machine'' unless you have modified the startx scripts to stop launching local X clients. I recommend instead that you make a copy of startxwin.bat and edit the `start XWin' line for your platform (Windows 95/98/Me or Windows NT/2000/XP) to use the -query parameter. Be sure to REM out the lines that start the local clients (xterm, twm, and xsetroot). By the way, 4.2.0-10 is the latest version of XFree86-xserv. Harold Claudio Tamietto [EMAIL PROTECTED] said: I'm sorry for my poor english but i don't kwown it very well .I'm a programmer and I'd like unix but unfortunately j have to work on windows paltform so i have installed cygwin on my windows 2000 workstation. Actualy i have the latest version of cygwin (1.3.12-1) and Xwin (4.2.0-7) installed. If i run the X-server locally with the command startx from a bash shell all seems function correctly but if i try to run a remote dislplay on aHP_UX unix server whit the command startx -- -query ip-of-remote-machine the following message appear on the console : .. Xlib: connection to :0.0 refused by server Xlib: No protocol specified Here follow the content of the file Xwin.log found in /tmp ddxProcessArgument () - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winDetectSupportedEngines () - Windows NT/2000 winDetectSupportedEngines () - DirectDraw installed winDetectSupportedEngines () - Allowing PrimaryDD winDetectSupportedEngines () - DirectDraw4 installed winDetectSupportedEngines () - Returning, supported engines 001f winSetEngine () - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL () - Using Windows display depth of 24 bits per pixel winAdjustForAutoHide - Original WorkArea: 0 0 768 1024 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 767 1024 winCreateBoundingWindowWindowed () - WindowClient w 1018 h 742 r 1018 l 0 b 742 t 0 winCreateBoundingWindowWindowed () - Returning winAllocateFBShadowDDNL () - lPitch: 3056 winInitVisualsShadowDDNL () - Masks 00ff ff00 00ff BPRGB 8 d 24 winCreateDefColormap () - Deferring to fbCreateDefColormap () winScreenInit () - returning AUDIT: Mon Jul 8 09:16:54 2002: 1320 X: client 1 rejected from local host AUDIT: Mon Jul 8 09:16:56 2002: 1320 X: client 1 rejected from local host AUDIT: Mon Jul 8 09:16:58 2002: 1320 X: client 1 rejected from local host AUDIT: Mon Jul 8 09:17:00 2002: 1320 X: client 1 rejected from local host AUDIT: Mon Jul 8 09:17:02 2002: 1320 X: client 1 rejected from local host AUDIT: Mon Jul 8 09:17:04 2002: 1320 X: client 3 rejected from local host AUDIT: Mon Jul 8 09:17:06 2002: 1320 X: client 4 rejected from local host winCloseScreenShadowDDNL () - Freeing screen resources If i use a commercial product like X-reflection j obtain a remote display correctly. Can someone help me ?
RE: Emailing: XWin.log
Robert, You are running cygwin-1.3.11-3 and XFree86-xserv-4.2.0-7. Please upgrade as I requested by getting the latest Cygwin setup.exe (http://cygwin.com/setup.exe) and running it. It will only upgrade packages that have been updated, so the download will not take long. By the way, are you able to reproduce this reboot-on-launch behavior every time? Have you tried to do this lately? How are you starting Cygwin/XFree86, are you using startxwin.bat (recommended)? Thanks, Harold Robert Taylor [EMAIL PROTECTED] said: Please find the inastalled.db file attached. Thanks for your dircect support--I look forward to being a regular user of cygwin. Robert Taylor, CTO Dispensing Solutions, Inc. [EMAIL PROTECTED] Office: (714)437-0330 ext 119 Mobile: (949)677-3864 -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 9:56 AM To: [EMAIL PROTECTED]; Robert Taylor; Harold L Hunt Cc: [EMAIL PROTECTED] Subject: RE: Emailing: XWin.log Robert, The Windows dump file won't be of any help. However, you could send in /etc/setup/installed.db. That way we know what versions of things you have. There have been several significant Cygwin/XFree86 updates since the 26 of June. I highly advise that you update. Harold Robert Taylor [EMAIL PROTECTED] said: Would the setup.log file help? How about the Windows dump file? My installation was 6/26/2002 from setup.exe via redhat -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 9:40 AM To: [EMAIL PROTECTED]; Robert Taylor; [EMAIL PROTECTED] Subject: Re: Emailing: XWin.log Robert, [For others: this is a followup to a post on ./ where Robert said that Windows XP rebooted when he ran XWin.exe] There doesn't seem to be any error recorded, at all. Try downloading the latest setup.exe (http://cygwin.com/setup.exe) and update your XFree86-xserv package. Make sure that you get version 4.2.0-10. Perhaps this was just a bug in some earlier version. Thanks for the log file, Harold Robert Taylor [EMAIL PROTECTED] said: Harold, I hope this is helpful. Robert J. Taylor
Fwd: RE: Emailing: XWin.log
Looks like we fixed another one :) Harold P.S. Robert - notice that I'm cc'ing [EMAIL PROTECTED] on all replies. Please start doing so in future replies. Forwarded From: Robert Taylor [EMAIL PROTECTED] Just installed the latest setup.exe and asked for all to be installed. It's running fine without rebooting or BSOD'ing. -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 9:56 AM To: [EMAIL PROTECTED]; Robert Taylor; Harold L Hunt Cc: [EMAIL PROTECTED] Subject: RE: Emailing: XWin.log Robert, The Windows dump file won't be of any help. However, you could send in /etc/setup/installed.db. That way we know what versions of things you have. There have been several significant Cygwin/XFree86 updates since the 26 of June. I highly advise that you update. Harold Robert Taylor [EMAIL PROTECTED] said: Would the setup.log file help? How about the Windows dump file? My installation was 6/26/2002 from setup.exe via redhat -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 9:40 AM To: [EMAIL PROTECTED]; Robert Taylor; [EMAIL PROTECTED] Subject: Re: Emailing: XWin.log Robert, [For others: this is a followup to a post on ./ where Robert said that Windows XP rebooted when he ran XWin.exe] There doesn't seem to be any error recorded, at all. Try downloading the latest setup.exe (http://cygwin.com/setup.exe) and update your XFree86-xserv package. Make sure that you get version 4.2.0-10. Perhaps this was just a bug in some earlier version. Thanks for the log file, Harold Robert Taylor [EMAIL PROTECTED] said: Harold, I hope this is helpful. Robert J. Taylor
RE: Problem with cygwin1.dll and xfree
You are ABSOLUTELY correct! I found another copy in /winnt/system. I deleted that one and, yes, it does work just fine with cygwin1.dll version 1.13.12-1 in \cygwin\bin. Sorry for causing trouble because of my own stupidity! Sandy -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 1:27 PM To: [EMAIL PROTECTED], Sanford J (ZERO CHAOS) Cc: [EMAIL PROTECTED] Subject: RE: Problem with cygwin1.dll and xfree Sanford, Do a search for `cygwin1.dll' on your system using the Windows file search utility. Tell us (at [EMAIL PROTECTED]) how many copies you find. Harold Zelkovitz, Sanford J (ZERO CHAOS) [EMAIL PROTECTED] said: Actually, when it fails, it does not generate an Xwin.log file. It does, however, generate numerous stackdump files. Attached are ones that were generated with the cygwin1.dll version 1.13.12-1. I also included a script which I use to get things started. Thanks, Sandy -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 12:42 PM To: [EMAIL PROTECTED], Sanford J (ZERO CHAOS); '[EMAIL PROTECTED]' Subject: Re: Problem with cygwin1.dll and xfree Sanford, We are not aware of any problems with Cygwin/XFree86 on the latest versions of cygwin1.dll. In fact, I've been running Cygwin/XFree86 all day on 1.3.12-2 without any problems, whatsoever. Send in your /tmp/XWin.log file and we will tell you if it has any relevant information. Thanks, Harold Zelkovitz, Sanford J (ZERO CHAOS) [EMAIL PROTECTED] said: The last two version of cygwin1.dll ( 1.13.12 and 1.13.11 ) seem not to work with the xfree release code. It appears that the code fails when run under the list DLLs. If I switch back to the version prior to 1.13.11, all works as advertised. Does anyone else have the same problem? Does anyone know if a patch exists to allow the xfree code to run under the latest cygwin1.dll? Sanford Sandy Zelkovitz (ZeroChaos) EDS - GWH Web Engineering 750 Tower Dr, M/C 5291 Troy, MI 48098 * phone: +01-248-265-2277 (8-365) * mailto:[EMAIL PROTECTED] www.eds.com
Re: Problem with cygwin1.dll and xfree
Nicholas Wourms wrote: If I'm not mistaken, I believe WinCVS does tell them to put the dll in system. If so, then they should be vigorously insulted, and possibly shunned. Think of the frenchmen in Monty Python's The Holy Grail. However, I can't find anything prominent on their site that says put cygwin1.dll in naughty places. --Chuck
Re: Problem with cygwin1.dll and xfree
I know I have run into problems a couple of times with programs that have windows installers that somehow like to assume that you don't already have Cygwin on your machine. The first time I installed Octave, it replaced my Cygwin with some minimal installation it needed to support itself. Something not as severe happended when I ran an Windows installation program for Ruby. EventuallyI learned to just go ahead and build things myself within Cygwin. So, one message that probably should leak out is to avoid Windows binaries that mention anything about Cygwin. :-) Wayne Keen
Upgrading to latest version
What's the recommended upgrade procedure now that XFree is in Cygwin setup? I'm still downloading the latest Server Test Series build from xfree86.cygwin.com and copying it over /usr/X11R6/bin/XWin. Will I miss something by not running setup? - Bradey -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 10:41 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Fwd: RE: Emailing: XWin.log Looks like we fixed another one :) Harold P.S. Robert - notice that I'm cc'ing [EMAIL PROTECTED] on all replies. Please start doing so in future replies. Forwarded From: Robert Taylor [EMAIL PROTECTED] Just installed the latest setup.exe and asked for all to be installed. It's running fine without rebooting or BSOD'ing. -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 9:56 AM To: [EMAIL PROTECTED]; Robert Taylor; Harold L Hunt Cc: [EMAIL PROTECTED] Subject: RE: Emailing: XWin.log Robert, The Windows dump file won't be of any help. However, you could send in /etc/setup/installed.db. That way we know what versions of things you have. There have been several significant Cygwin/XFree86 updates since the 26 of June. I highly advise that you update. Harold Robert Taylor [EMAIL PROTECTED] said: Would the setup.log file help? How about the Windows dump file? My installation was 6/26/2002 from setup.exe via redhat -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 9:40 AM To: [EMAIL PROTECTED]; Robert Taylor; [EMAIL PROTECTED] Subject: Re: Emailing: XWin.log Robert, [For others: this is a followup to a post on ./ where Robert said that Windows XP rebooted when he ran XWin.exe] There doesn't seem to be any error recorded, at all. Try downloading the latest setup.exe (http://cygwin.com/setup.exe) and update your XFree86-xserv package. Make sure that you get version 4.2.0-10. Perhaps this was just a bug in some earlier version. Thanks for the log file, Harold Robert Taylor [EMAIL PROTECTED] said: Harold, I hope this is helpful. Robert J. Taylor
[ANNOUNCEMENT] Server Test 64
Links: I just posted Test 64 to the server development page: http://xfree86.cygwin.com/devel/shadow/ You can install the Test 64 package via setup.exe by selecting the 'test' package (and be sure to check the 'Bin' box): XFree86-xserv-4.2.0-11 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-Test64.exe.bz2 (1100 KiB) Server source, direct link: http://www.msu.edu/~huntharo/xwin/shadow/xwin-20020708-2212.tar.bz2 (81 KiB) xc/programs/Xserver/Imakefile diff against 20020708 XFree86 CVS: http://www.msu.edu/~huntharo/xwin/shadow/xc-programs-Xserver-Imakefile-20020 708-2212.diff (2 KiB) xc/programs/Xserver/hw/xwin (all files) diff against 20020708 XFree86 CVS: http://www.msu.edu/~huntharo/xwin/shadow/xwin-20020708-2212.diff.bz2 (3 KiB) xc/programs/Xserver/hw/xwin new files: http://www.msu.edu/~huntharo/xwin/shadow/xwin-newfiles-20020708-2212.tar.bz2 (8 KiB) Changes: 1) winconfig.c, winconfig.h, winmsg.c, winmsg.h, InitOutput.c, winkeybd.c - Add support for using XF86Config-style configuration files. (Alexander Gottwald) Enjoy, Harold
