Performance issues -- xdvi
Running: cygwin 1.5.5-1, XFree 4.3.0 on WinXP in rootless or fullscreen mode; xwin.log file below. I have been playing around with xdvi from the latest tetex distribution, mainly to see if whizzytex (an almost-instant preview package for emacs/latex/xdvi) could be made to work under Cygwin. I have found xdvi to be vastly slower under Cygwin/Xfree than under Linux/Xfree. Displaying a new page takes about 1--1.5 seconds on my P4 2.8 Ghz / 512MB PC. You can see text being displayed almost line by line. This happens both in rootless and fullscreen mode. Under Linux/Xfree, it's almost instantaneous. Under Linux Xfree, xdvi is known to be pretty fast (faster than Yap under Win32, say). I should emphasize that, although my goal was to get whizzytex to work, speed considerations arise when simply previewing a DVI file, by typing xdvi file.dvi at the bash prompt and then paging through the file with the keyboard. I first thought this was due to the Cygwin port of xwin, or to Cygwin proper, not Cygwin/Xfree. However, I eventually tried the Xwin32 X server, and was surprised to find out that performance is greatly improved, very close to native. So, the issue seems to be with Cygwin/Xfree. Indeed, I also found out that other X clients (xterm, emacs) are much snappier under Xwin32 than under Cygwin/Xfree. Now, this could be a misconfiguration issue. My xwin.log file is attached below. I also export DISPLAY=my machine' IP address:0 before running clients. [I have also tried DISPLAY=127.0.0.1:0, but observed no change in performance, although I recall seeing a thread on the ML concerning possible differneces] Otherwise, does anybody have any thoughts? This is probably not a huge issue for many clients, but the instant-preview nature of whizzytex makes speed essential (basically, you need to refresh a DVI file every few keystrokes). Thanks! Marciano. xwin.log file: (running in rootless mode) 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 NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Multi Window = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 994 1280 winAdjustForAutoHide - Adjusted WorkArea: 0 0 994 1280 winCreateBoundingWindowWindowed - WindowClient w 1280 h 994 r 1280 l 0 b 994 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 994 depth: 32 winAllocateFBShadowGDI - Dibsection width: 1280 height: 994 depth: 32 size image: 5089280 winAllocateFBShadowGDI - Created shadow stride: 1280 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () null screen fn ReparentWindow null screen fn RestackWindow winFinishScreenInitFB - Calling winInitWM. InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitWM - Returning. winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () (==) winConfigKeyboard - Layout: 0409 (0409) (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = xfree86 Model = pc101 Layout = us Variant = (null) Options = (null) winPointerWarpCursor - Discarding first warp: 640 497 winBlockHandler - Releasing pmServerStarted winInitMultiWindowWM - pthread_mutex_lock () returned. DetectUnicodeSupport - Windows NT/2000/XP winInitMultiWindowWM - Calling setlocale () winBlockHandler - pthread_mutex_unlock () returned winInitMultiWindowWM - setlocale () returned winInitMultiWindowWM - XInitThreads () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winDeinitClipboard - Noting shutdown
Re: XWin --query
On Thu, 2003-10-16 at 12:28, Greg Freemyer wrote: On Wed, 2003-10-15 at 16:49, Sylvain Petreolle wrote: Just to be sure: are you using the correct option : XWin -query dmcphost (good) not XWin --query dmcphost (bad) ? I invoke this via a shell script, and yes the script had a single -. Greg I upgraded to the latest cygwin xfree-bin and xfree-progs. All works again. Must have been a problem relating to the cygwin 1.5 transition. Greg
Re: Performance issues -- xdvi
Marciano, XWin.exe is not as fast as Exceed or XWin-32. Harold Marciano Siniscalchi wrote: Running: cygwin 1.5.5-1, XFree 4.3.0 on WinXP in rootless or fullscreen mode; xwin.log file below. I have been playing around with xdvi from the latest tetex distribution, mainly to see if whizzytex (an almost-instant preview package for emacs/latex/xdvi) could be made to work under Cygwin. I have found xdvi to be vastly slower under Cygwin/Xfree than under Linux/Xfree. Displaying a new page takes about 1--1.5 seconds on my P4 2.8 Ghz / 512MB PC. You can see text being displayed almost line by line. This happens both in rootless and fullscreen mode. Under Linux/Xfree, it's almost instantaneous. Under Linux Xfree, xdvi is known to be pretty fast (faster than Yap under Win32, say). I should emphasize that, although my goal was to get whizzytex to work, speed considerations arise when simply previewing a DVI file, by typing xdvi file.dvi at the bash prompt and then paging through the file with the keyboard. I first thought this was due to the Cygwin port of xwin, or to Cygwin proper, not Cygwin/Xfree. However, I eventually tried the Xwin32 X server, and was surprised to find out that performance is greatly improved, very close to native. So, the issue seems to be with Cygwin/Xfree. Indeed, I also found out that other X clients (xterm, emacs) are much snappier under Xwin32 than under Cygwin/Xfree. Now, this could be a misconfiguration issue. My xwin.log file is attached below. I also export DISPLAY=my machine' IP address:0 before running clients. [I have also tried DISPLAY=127.0.0.1:0, but observed no change in performance, although I recall seeing a thread on the ML concerning possible differneces] Otherwise, does anybody have any thoughts? This is probably not a huge issue for many clients, but the instant-preview nature of whizzytex makes speed essential (basically, you need to refresh a DVI file every few keystrokes). Thanks! Marciano. xwin.log file: (running in rootless mode) 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 NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Multi Window = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 994 1280 winAdjustForAutoHide - Adjusted WorkArea: 0 0 994 1280 winCreateBoundingWindowWindowed - WindowClient w 1280 h 994 r 1280 l 0 b 994 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 994 depth: 32 winAllocateFBShadowGDI - Dibsection width: 1280 height: 994 depth: 32 size image: 5089280 winAllocateFBShadowGDI - Created shadow stride: 1280 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () null screen fn ReparentWindow null screen fn RestackWindow winFinishScreenInitFB - Calling winInitWM. InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitWM - Returning. winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () (==) winConfigKeyboard - Layout: 0409 (0409) (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = xfree86 Model = pc101 Layout = us Variant = (null) Options = (null) winPointerWarpCursor - Discarding first warp: 640 497 winBlockHandler - Releasing pmServerStarted winInitMultiWindowWM - pthread_mutex_lock () returned. DetectUnicodeSupport - Windows NT/2000/XP winInitMultiWindowWM - Calling setlocale () winBlockHandler - pthread_mutex_unlock () returned winInitMultiWindowWM - setlocale () returned winInitMultiWindowWM - XInitThreads () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winInitMultiWindowWM -
Sun Workshop debugger hangs
Hello Cygwin-Xfree masters, I have a programmer using Sun Workshop6.0 debugger running on a Solaris8 server and displayed back to his Win2K PC via Cygwin 1.5.4 Xfree from an XDCMP login. I have monitored system resources both on the PC and the server and it is normal. The problem is that at a random times the debugger will lock up, first the function keys will stop working, forcing the programmer to use the mouse on the GUI buttons, then a several operations later the mouse will stop responding. The PC and the server are still normal but the debugger is locked. He can use the debugger on a Sun workstation displayed back from the same server with no problems. Any ideas what I do to solve this problem? TIA, Tim
Re: Sun Workshop debugger hangs
Tim, Just so you get a reply: I have no ideas. There are lots of weird problems that occur when using Cygwin/XFree86 with Solaris. Check the FAQ. Most of the issues relate to fonts and using a font server, other than that I can only say that I hope someone else has already encountered and solved your particular problem. Harold [EMAIL PROTECTED] wrote: Hello Cygwin-Xfree masters, I have a programmer using Sun Workshop6.0 debugger running on a Solaris8 server and displayed back to his Win2K PC via Cygwin 1.5.4 Xfree from an XDCMP login. I have monitored system resources both on the PC and the server and it is normal. The problem is that at a random times the debugger will lock up, first the function keys will stop working, forcing the programmer to use the mouse on the GUI buttons, then a several operations later the mouse will stop responding. The PC and the server are still normal but the debugger is locked. He can use the debugger on a Sun workstation displayed back from the same server with no problems. Any ideas what I do to solve this problem? TIA, Tim
Xfig and printer
I found some problems running Xfig under Cygwin, I cannot save and/or save as a new picture because in the Save window the keyboard seems to be disabled. The only way I found is to create a void file .fig (i.e. using Vi) and then try to save the new picture clicking this dummy name. The second problem I found is the printer, I don't found a way to set the defult printer. May someone kindly help me? Thank you in advance Lorenzo
Re: Error linking against libXt
/ Lou Losee [EMAIL PROTECTED] wrote: | Thanks, I will try that. Is there any way to determine what the default | search libs are for gcc/ld? I was not able to find anything in the | man/info pages other than there was a default search path. Run gcc with -v and it will show you where it searches and so on /Andy -- From the other side of the screen it looked so easy - Tron Please note, new email, @telia.com - @comhem.se
Re: Xfig and printer
Lorenzo, The keyboard isn't disabled, as far as I know. I have had problems with xfig being finicky regarding keyboard focus in various dialogs. Just try cliking the mouse in a few more places around where the text caret is... you won't get a visual indication that the keyboard focus is in that field, but you will be able to type eventually. xfig has a terrible interface, get used to it. Harold Lorenzo Travaglio wrote: I found some problems running Xfig under Cygwin, I cannot save and/or save as a new picture because in the Save window the keyboard seems to be disabled. The only way I found is to create a void file .fig (i.e. using Vi) and then try to save the new picture clicking this dummy name. The second problem I found is the printer, I don't found a way to set the defult printer. May someone kindly help me? Thank you in advance Lorenzo
Installation Problems: XFree-icons-bin
When installing the complete cygwin package, the install frezees at XFree-icons-bin post install. I have tried this a few times. When I dont choose to install this package and X it installs everything else fine but I cant use X. I am running Win2000 fully service packed. Is there something I am missing or do I have manually install it. I am highly literate in UNIX been using RedHat linux for over 9 years. Thought I'd give cygwin a go on my home PC ( I run windows at home because my wife only knows windows) Cygwin was the only option because I want to use a UNIX shell and run Sims while she can still use windows Can any one give me a hand Thanks in advance Brett Wildermoth Lecturer Griffith University Brisbane, Australia
Re: Installation Problems: XFree-icons-bin
On Thu, 24 Oct 2003, Brett Wildermoth wrote: When installing the complete cygwin package, the install frezees at XFree-icons-bin post install. Please search the archives before posting. This issue has been beaten to death. If you are using a reasonably up to date mirror, it should already have the new version of bash that fixes this problem. See the following thread and its thread link for more information if you really want to: http://www.cygwin.com/ml/cygwin/2003-10/msg01309.html -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
