Re: XFree86: Removing dummy root window on Rootless/Multiwindow mode
There isn't a dummy root window when you run with -rootless. There is, however, a dummy root window when you run with -multiwindow. Search the mailing list archives to my multiple responses on how easy/hard removing that dummy window may be. Harold ed wrote: To The Esteemed List: I've been using Cygwin ever since the release of the multiwindow test server. It's been excellent! Thanks for all the hard work, especially Kensuke Matsuzaki for putting it all together in the beginning. My question is this: Is it possible to run Cygwin Xfree -rootless without having to have the dummy root window? If not, why not?
compiling gv
Hi, I am trying to compile gv-3.5.8 on cygwin 1.3.20-1, and have the following problems: ld complains when I compile the source with --enable-auto-imports, and the compile went through when i turned on --enable-runtime-pseudo-reloc, but gv exits with "Error: Unresolved inheritance operation" when I run it. I suspect this is related to the problem discussed in this thread on this list: http://www.cygwin.com/ml/cygwin-xfree/2002-12/msg00189.html Could someone help me find a way to fix this without having to compile cygwin/Xfree86 myself? Did the proposed code (to redefine _XtInherit to a constant) not make it into the release yet? thanks in advance, -ram
Re: Building/running GIMP under Cygwin
On Tue, 25 Feb 2003, Chris Olive wrote: > Well, I've searched the 'net high and low for information on this, and > have found nothing that fully resolves the issue, but... Has anyone > successfully built and run GIMP under Cygwin? I know there exists a > Win32 version of GIMP, but I want to run under Cygwin in XFree. > > GIMP uses GTK+, glib and who knows what else. I've visited a few pages > that purport GIMP's ability to run under Cygwin (with the supposed > dependances), but normal ./configure's and ./make's of the packages > involved end up returning errors. If anyone has worked through all this > and has a STEP BY STEP w/success, I'd be glad to see it. A few days of > dinking with it have not produced success on my part. There's gotta be > a secret incantation... > > chris Chris, You may get a better answer from the list, which is intended for discussing all things X-related (on Cygwin). I've redirected this message there, and reset the Reply-To: for your convenience. Please remove from follow-up messages. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk! -- /usr/games/fortune
Re[4]: XFree86-cygwin & KDE & national keybord layouts
Hello, Alexander! Saturday, February 22, 2003, 3:24:37 PM, you wrote: AG> Can you please run xev during this test and mail me the output? And here is third logs: xev-kdeswt.log: (1) xev started in background (2) startkde started (3) xev clicked (4) "qaz" typed (without quotes, of course) (5) KDE switch icon clicked (layout change) (6) "qaz" typed (three Russian letters, really) (7) KDE switch icon clicked (layout change) (8) "qaz" typed I've removed all mouse and mapping events from logs. Lev Serebryakov /---\ | FIDONet: 2:5030/661.0 | | E-Mail: [EMAIL PROTECTED] | | Page:http://lev.serebryakov.spb.ru/ | | ICQ UIN: 3670018 | | Phone: You know, if you have world nodelist | \===/ xev-kdeswt.log Description: Binary data
Re[4]: XFree86-cygwin & KDE & national keybord layouts
Hello, Alexander! Saturday, February 22, 2003, 3:24:37 PM, you wrote: AG> Can you please run xev during this test and mail me the output? Here it is. Here are two logs: xev-nokde.log: (1) xev started (2) xev clicked (3) "qaz" typed (without quotes, of course) (4) Ctrl+Shift pressed (layout change) (5) "qaz" typed (three Russian letters, really) (6) Ctrl+Shift pressed (layout change) (7) "qaz" typed xev-kde.log: (1) xev started in background (2) startkde started (3) xev clicked (4) "qaz" typed (without quotes, of course) (5) Ctrl+Shift pressed (layout change) (6) "qaz" typed (three Russian letters, really) (7) Ctrl+Shift pressed (layout change) (8) "qaz" typed I've removed all mouse and mapping events from logs. It seems, it is KDE 3.1 problem, not XFree86/cygwin :( Lev Serebryakov /---\ | FIDONet: 2:5030/661.0 | | E-Mail: [EMAIL PROTECTED] | | Page:http://lev.serebryakov.spb.ru/ | | ICQ UIN: 3670018 | | Phone: You know, if you have world nodelist | \===/ xev-nokde.log Description: Binary data xev-kde.log Description: Binary data
Problem with installing XFree86 on Win 2000
Hi everybody. When I try to install XFree86-base (and, consequently, the files that option selects), the installation process hangs. Specifically, the two options that cause the installation to hang are XFree86-fenc and XFree86-fnts (both versions of these two options fail to install). The version of the installer is 2.249.2.5 (which, I believe, is the latest version). When installing XFree86-fenc, the installations hangs on the file /usr/X11R6/lib/X11/fonts/encodings/adobe-dingbats.enc.gz When installing XFree86-fnts, the installations hangs on the file /usr/X11R6/lib/X11/fonts/75dpi/charB08.pcf.gz If it's of any help, my machine is a Pentium 3, running Windows 2000. If there is any more additional info I can provide, please let me know. Andrew Chizhik
XFree86: Removing dummy root window on Rootless/Multiwindow mode
To The Esteemed List: I've been using Cygwin ever since the release of the multiwindow test server. It's been excellent! Thanks for all the hard work, especially Kensuke Matsuzaki for putting it all together in the beginning. My question is this: Is it possible to run Cygwin Xfree -rootless without having to have the dummy root window? If not, why not?
Re: multiwindow crash on resolution 1280
JS, That doesn't make any sense. There should not be any difference at all when running with ``-engine 1'' instead of ``-multiwindow'', as far as the DIB creation is concerned. The only thing I can think of is that this is perhaps running on a system with very little available memory at the time of startup... multiwindow mode might take just enough memory to make the allocation of memory for the DIB fail. That is the only thing that makes any sense. Oh yeah, and I ask you to send in the log file from -engine 1, which would help in diagnosing this problem. Harold J S wrote: Harold, Sorry to reply to this so late. If he starts xwin with -engine 1 that works fine. The problem is that multiwindow seems to be the only mode that works with his application and it has to be run with this resolution. JS, What happens if he runs in 1280x1024 with "-engine 1" instead of "-multiwindow"? Please send in a log from that run. I suspect it will be the same. Is 1280x1024 the maximum resolution that he can run in, or is there a higher resolution that works just fine with -multiwindow? I am just trying to figure out if this is a problem where the largest size is not possible but anything smaller than that is okay, or if it is just that one size in the middle has problems but all the rest are okay. Oh yeah, and this was done with 4.2.0-25, right? Thanks for testing, Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of J S Sent: Thursday, January 30, 2003 4:30 AM To: [EMAIL PROTECTED] Subject: multiwindow crash on resolution 1280 Hi, I have a customer trying out multiwindow mode on windows 95. He usually has his resolution set to 1280 x 1024, but for some reason multiwindow won't work with this. If I change his display settings to anything else though, it does work. Here is the log: ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 (EE) Unable to locate/open config file InitOutput - Error reading config file winDetectSupportedEngines - Windows 95/98/Me winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Returning, supported engines 0013 InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Multi Window => ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 1024 1280 winAdjustForAutoHide - Adjusted WorkArea: 0 0 1024 1280 winCreateBoundingWindowWindowed - WindowClient w 1280 h 1024 r 1280 l 0 b 1024 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1024 depth: 16 winAllocateFBShadowGDI - Dibsection width: 1280 height: -1024 depth: 16 size image: 2621440 winAllocateFBShadowGDI - Shadow blit failure winFinishScreenInitFB - Could not allocate framebuffer winScreenInit - winFinishScreenInit () failed Fatal server error: InitOutput - Couldn't add screen 0 Thanks for any help, JS. _ Stay in touch with MSN Messenger http://messenger.msn.co.uk _ MSN Messenger - fast, easy and FREE! http://messenger.msn.co.uk
RE: multiwindow crash on resolution 1280
Harold, Sorry to reply to this so late. If he starts xwin with -engine 1 that works fine. The problem is that multiwindow seems to be the only mode that works with his application and it has to be run with this resolution. JS, What happens if he runs in 1280x1024 with "-engine 1" instead of "-multiwindow"? Please send in a log from that run. I suspect it will be the same. Is 1280x1024 the maximum resolution that he can run in, or is there a higher resolution that works just fine with -multiwindow? I am just trying to figure out if this is a problem where the largest size is not possible but anything smaller than that is okay, or if it is just that one size in the middle has problems but all the rest are okay. Oh yeah, and this was done with 4.2.0-25, right? Thanks for testing, Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of J S Sent: Thursday, January 30, 2003 4:30 AM To: [EMAIL PROTECTED] Subject: multiwindow crash on resolution 1280 Hi, I have a customer trying out multiwindow mode on windows 95. He usually has his resolution set to 1280 x 1024, but for some reason multiwindow won't work with this. If I change his display settings to anything else though, it does work. Here is the log: ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 (EE) Unable to locate/open config file InitOutput - Error reading config file winDetectSupportedEngines - Windows 95/98/Me winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Returning, supported engines 0013 InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Multi Window => ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 1024 1280 winAdjustForAutoHide - Adjusted WorkArea: 0 0 1024 1280 winCreateBoundingWindowWindowed - WindowClient w 1280 h 1024 r 1280 l 0 b 1024 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1024 depth: 16 winAllocateFBShadowGDI - Dibsection width: 1280 height: -1024 depth: 16 size image: 2621440 winAllocateFBShadowGDI - Shadow blit failure winFinishScreenInitFB - Could not allocate framebuffer winScreenInit - winFinishScreenInit () failed Fatal server error: InitOutput - Couldn't add screen 0 Thanks for any help, JS. _ Stay in touch with MSN Messenger http://messenger.msn.co.uk _ MSN Messenger - fast, easy and FREE! http://messenger.msn.co.uk