[Xpert]Re: unsuscribe xpert
Oh no! The unsuscribe virus has propagated from [EMAIL PROTECTED] into the wild! Sorry everyone! ;o) Sorry.. couldn't resist. ;o) James, you can unsubscribe from the mailing list, by going to the following URL if you like: http://XFree86.Org/mailman/listinfo/xpert If you don't remember your password, there is a button there to have it mailed to you. Alternatively, you can send requests to the [EMAIL PROTECTED] address. To unsubscribe from the list, you'd put unsubscribe password in the subject. Or to get your password mailed to you, you can send password in the subject. Hope this helps. TTYL P.S. Wow, look at that. I did full justification above without even trying to do so. Ok, this goofball is going back to work. ;o) -- -- Mike A. Harris Shipping/mailing address: OS Systems Engineer 190 Pittsburgh Ave., Sault Ste. Marie, XFree86 maintainer Ontario, Canada, P6C 5B3 Red Hat Inc.Phone: (705)949-2136 http://www.redhat.com ftp://people.redhat.com/mharris Red Hat XFree86 mailing list: [EMAIL PROTECTED] General open IRC discussion:#xfree86 on irc.openprojects.net -- ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]i810, XFree86: vertical bars on screen
Stuart, This is a watermark issue. The watermark is the set of delays etc. that control the flow of data into and out of a FIFO that feeds the dac. Your FIFO is probably running out of data when memory bandwidth isn't available to fill the screen and blit at the same time. Hmm. Especially considering that I'm running an i810 (*spit*), this could very well be the issue. *starts browsing the Green Guide for a new Matrox* :) Your video mode is probably to blame. Either run at a lower refresh rate, Eeew. 75 Hz (the current refresh rate), for me, is the bare minimum for a reasonable display; I'd actually prefer to be playing at 85 Hz. Anything less, and I can pick up on the flicker. or a smaller resolution. That's even worse. :-) On a 19 screen, 1024x768 (the next resolution down) isn't what I'd call fun. And to think that I've been intending to bump the resolution *up*... :) Additionally there were some systems that had a incorrect bios setting in the MEMMODE register. This was fixed in XFree sometime recently but I don't recall when. If your system suffers from that issue upgrading to 4.2.0 may provide better results. I'll look into that, then. Additionally if you are using a non standard Modeline in XF86Config... don't do that. It looks like I'm using the default modes, rather than a user-supplied mode. Thanks to all who responded.. food for thought. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]An question about StopVideo on ATI AiW r128
Title: Hello everyone : I encounter a strange problem and can't figure out why. I have a ATI AiW r128 video card his new Xv supported driver. When I use DVD player to play mpeg2 file move other window to clip the video window, the driver doesn't call StopVideo. But in it's VideoInit function, it sets flag VIDEO_OVERLAID_IMAGES as below : VAR[i].type |= XvWindowMask | XvVideoMask | XvStillMask | XvImageMask; VAR[i].name = "R128"; VAR[i].flags=VIDEO_OVERLAID_IMAGES|VIDEO_CLIP_TO_VIEWPORT; According to XFree86 X server "New Design"(DRAFT): The XFree86 X Video Extension(Xv) Device Dependent Layer chapter, it mentions that if we set VIDEO_OVERLAID_IMAGES, StopVideo will be called whenever the destination gets clipped or moved so that theimage can be left up until then. My confusion is that how ATI does that it can prevent the driver to call StopVideo when we clip the video window. Does anybody know this give me a help, Thanks a lot !! Sincerely, Kevin Huang
[Xpert]How to determine local vs. remote X connection?
How do I determine if my X connection is local (on the same machine) or remote (on a different machine)? I'd like to use the shared memory extension, but it would be pointless if the connection is not local. -- Dave Williss--Meddle not in the affairs of dragons, for you are crunchy and taste good with catsup
Re: [Xpert]How to determine local vs. remote X connection?
1 On Thu, 21 Feb 2002, Dave Williss wrote: How do I determine if my X connection is local (on the same machine) or remote (on a different machine)? I'd like to use the shared memory extension, but it would be pointless if the connection is not local. One way would be to try initializing it and if it fails then it does not work.. ;) Vladimir Dergachev -- Dave Williss -- Meddle not in the affairs of dragons, for you are crunchy and taste good with catsup ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]xgamma not working with second head of MGA G400 AGP
On Wed, 20 Feb 2002, Don Armstrong wrote: I have a 3 (well, trying to make it 4 if I can get the second voodoo to soft boot) head system, and for some odd reason, xgamma won't change the gamma of the second MGA head, while it will change the gamma of the first head no problem. Their hardware doesn't support that (no palettes on the second head). Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]An question about StopVideo on ATI AiW
On Thu, 21 Feb 2002, [big5] Kevin Huang wrote: Hi Mark : Thanks for your answer in advance!! :) I'm working on Xv driver for my company's graphic chip, but I encounter an problem can't fint out the reason. Everytime I use other window to clip the video window or move it, StopVideo will be called makes the video flicker. This doesn't happen in ATI AiW r128. That's because the other drivers don't stop the video then. They stop it in a few seconds if PutImage doesn't get called again. When I check the XFree86.0.log of ATI AiW, only PutImage is called. Does any special flags need to set in the driver ? No. StopVideo still gets called. It certainly would if you moved the window. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]2xRadeon VE PCI in one machine, progress and help wanted. (4.2.0)
I have a machine with 2 Raedon PCI VE in it. I can currently get X 4.2.0 to come up on the primary board, or the second board depending on which screen I activate in the ServerLayout. But when I try to activate both of them, it's reporting that one of the two (the secondary board) is not valid. I know that the ATI/Raedon driver realizes that both boards are there, and are viable, but why isn't the system allowing both of them to co-exist. I have the log of the setup with both boards posted at http://www.wakeful.net/~ira/XFree86/ and the XF86Config file. If there is interest, I'll post logs of both boards working independantly. I can probably arrange remote access to the machine if people are interested in such things, and think it would help. Thanks, -Ira ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]How to determine local vs. remote X connection?
On Thu, 21 Feb 2002, Dave Williss wrote: How do I determine if my X connection is local (on the same machine) or remote (on a different machine)? I'd like to use the shared memory extension, but it would be pointless if the connection is not local. I don't think any functions to do that are exported, though there are functions internal to Xlib that do that (like __X11TransIsLocal). You could probably use that with some nasty kludges, but generally I think people just try to see if they can attach or not and suppy a error handler to trap the failure. Attaching could fail on a system that didn't have shm support even if you were local so checking for local isn't foolproof. Mark ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Help with the mouse interface...
...on my laptop. It is one of those scratch pad units. A tap on the surface seems to be reported as a mouse left click. I am no typist, or keyboardist, and I would like to disable the tap feature. I haven't seen how to accomplish this on my Linux box running XFree86. Is there a clue running around out there? dlg ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]A big confusion over here - XFree 4.2 - and rage 128
On Mit, 2002-02-20 at 18:11, Gustavo Alberto Homem wrote: I can only guess why 4.0.3 worked better than 4.1.0; I guess it's because the r128 driver in 4.0.3 didn't properly support 420 video (or was it 422? I forget :) yet. I don't know exactly what are those 420 and 422 ? Image formats ? Yes. How does that justify the fact that mpeg2 overlay performance degraded ? I was going to suggest that the better performance might have been at the cost of image quality, but I'm even less sure now... What I complain about (with XFree 4.1 and XFree 4.2 DRI disabled) is a very high cpu load when using XV output, which causes frame dropping. With Xshm output I get no frame drops and Xv was supposed to provide better performance, so I have to conclude that Xv output is broke in either 4.1 and 4.2 , in the latter case it is broke in 2 different ways (but only for mpeg). Other reports seem to back your suspicion that something is badly broken; unfortunately, I have no idea what. Someone will have to track it down. 2 - The KDM login screen is completely messed (widgets are garbaged, not drawn properly) I have fixed this in DRI CVS and submitted the fix to XFree86. Both 1) and 2) are due to the fact that the r128 driver does 2D acceleration differently with DRI enabled now. I'm sure you've also noticed the better 2D performance. :) I read that the 2d acceleration mode had to be changed because it was incompatible with the use of bttv, but why have two diferent implmentations ? There are two ways to program the chip which don't mix well. There's apparently a way to simulate one using the other though, which could indeed be used to unify the code. What I noticed was that with DRI enabled Xv ouput was smooth again before crashing (colors were wrong though), but that was the usual situation with 4.03 regardless of DRI beeing enabled or disabled. It was smooth because the DRM was used to transfer the image data using DMA. What is exactly the relation of Xvideo and dri ? They are conceptually independent, however as of 4.2.0, the r128 driver tries to take advantage of the DRM to accelerate Xv image transfer. Unfortunately, this doesn't work well with some chips, and there are also problems coordinating this with the new 2D acceleration yet. hmm, I had a very quick look at dri.sf.net info, and I think I read drm was 3d only and that 2d data would allways go to the X server (they have a picture :) ). Did this change ? Is drm going to be used for 2d in the future ? The DRM is a generic resource manager. It was traditionally only used by the DRI, but that seems to be changing. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]S3 TRIO 3D system hang from PCI violation
Bradley Thomas wrote: Hello everyone, Recently, we discovered a PCI violation occuring using ATI Rage XL chipsets, which Marc Aurele La France was kind enough to provide a fix for us. We have also discovered that the same PCI violation is occuring with S3 TRIO 3D (as well as the PERMEDIA) chipset. I was hoping to find a kind S3 soul that could help us create a similar fix as to what Marc provided us with ATI. Marc's patch is attached for reference. Please CC me on any responses, as I am not subscribed to this list. Hi Bradley, What version of the s3virge driver/XFree86 are you seeing the lockup with? Also, could you give a more detail on what you mean by a PCI Violation? And how you know it is similar to the ATI failure? Marc, can you give a little more detail on what the ATI problem was? The attached patch doesn't mean a whole lot to me. -- Kevin ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Problem with ATI Mobility Radeon LY on IBM A30p
On Die, 2002-02-19 at 23:40, Tobias Engel wrote: - glxgears is very slow. Max 390 FPS. Are you really using direct rendering? glxinfo and/or running glxgears with LIBGL_DEBUG=verbose should tell. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]restart of X server kills /dev/dri/card0 ???
On Die, 2002-02-19 at 18:13, Armin Lambacher wrote: [drm] failed to load kernel module radeon Is the radeon kernel module available? If I have a look at /dev/dri, the directory is empty. Upon searching on the net I found that there should be a /dev/dri/card0 entry. I created that entry with cd /dev/dri mknod card0 c 226 1 I admit that I do not know whether the parameters are really correct. A further ls -l showed that the entry was there. Then I restarted the X server. Then again the /dev/dri directory was empty. I do not understand why. The X server creates and removes the nodes under /dev/dri/ as appropriate. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]How to make /dev/dri/card0?
On Die, 2002-02-19 at 05:30, Matthew Hagerty wrote: I'm trying to get X started with hardware support for my Voodoo-3 3000 (AGP). I'm running FreeBSD4.5-Release, X 4.2 compiled and installed from source and KDE 2.2.2 from the ports/pagkages. I don't know if DRI in 4.2.0 works on BSD out of the box, maybe you need to use the BSD branch in DRI CVS? drmOpenDevice: node name is /dev/dri/card14 drmOpenDevice: open result is -1, (Unknown error: 999() drmOpenDevice: Open failed (II) TDFX(0): [drm] drmOpen failed (EE) TDFX(0): [dri] DRIScreenInit failed, disabling DRI. When I look in /dev/dri the directory is empty. Everything else seems to load without error and I have checked and rechecked that I have all the Load commands in my XF86Config. Can anyone give me some info on how these cardx devices are supposed to come into existence? The X server creates and removes them. Your problem seems to be related to the DRM kernel module. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]An question about StopVideo on ATI AiW
Hi Mark : Thanks for your answer in advance!! :) I'm working on Xv driver for my company's graphic chip, but I encounter an problem can't fint out the reason. Everytime I use other window to clip the video window or move it, StopVideo will be called makes the video flicker. This doesn't happen in ATI AiW r128. That's because the other drivers don't stop the video then. They stop it in a few seconds if PutImage doesn't get called again. How does the AiW driver make it ? I trace the code of PutImage StopVideo in r128_video.c but find nothing special. The StopVideo seems be called by X Server the AiW driver seems cannot control when StopVideo will be called. the driver only provide the StopVideo function call for X Server. Thanks a lot! Kevin When I check the XFree86.0.log of ATI AiW, only PutImage is called. Does any special flags need to set in the driver ? No. StopVideo still gets called. It certainly would if you moved the window. Mark. - ¨C¤Ñ³£ Yahoo!©_¼¯ www.yahoo.com.tw ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]An question about StopVideo on ATI AiW
On Fri, 22 Feb 2002, [big5] Kevin Huang wrote: Hi Mark : Thanks for your answer in advance!! :) I'm working on Xv driver for my company's graphic chip, but I encounter an problem can't fint out the reason. Everytime I use other window to clip the video window or move it, StopVideo will be called makes the video flicker. This doesn't happen in ATI AiW r128. That's because the other drivers don't stop the video then. They stop it in a few seconds if PutImage doesn't get called again. How does the AiW driver make it ? I trace the code of PutImage StopVideo in r128_video.c but find nothing special. The StopVideo seems be called by X Server the AiW driver seems cannot control when StopVideo will be called. the driver only provide the StopVideo function call for X Server. Are you saying that the ATI driver's StopVideo is not called? It should be called when the window moves. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]An question about StopVideo on ATI AiW
--- Mark Vojkovich [EMAIL PROTECTED] ªº°T®§¡G On Fri, 22 Feb 2002, [big5] Kevin Huang wrote: Hi Mark : Thanks for your answer in advance!! :) I'm working on Xv driver for my company's graphic chip, but I encounter an problem can't fint out the reason. Everytime I use other window to clip the video window or move it, StopVideo will be called makes the video flicker. This doesn't happen in ATI AiW r128. That's because the other drivers don't stop the video then. They stop it in a few seconds if PutImage doesn't get called again. How does the AiW driver make it ? I trace the code of PutImage StopVideo in r128_video.c but find nothing special. The StopVideo seems be called by X Server the AiW driver seems cannot control when StopVideo will be called. the driver only provide the StopVideo function call for X Server. Are you saying that the ATI driver's StopVideo is not called? It should be called when the window moves. Mark. Yes, ATI's StopVideo is not called when the video window moves, so it's video doesn't flicker during window moving. The StopVideo is only called at the end of playing mpeg2 video file with cleanup = 1. I attach part of the XFree86.0.log for reference. Kevin XFree86 Version 4.1.0 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 2 June 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Build Operating System: Linux 2.4.9-13custom i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Fri Feb 22 14:16:39 2002 (==) Using config file: /etc/X11/XF86Config Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor My Monitor (**) | |--Device ATI All-in-Wonder (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (.skip) (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=56 drw_y=100 drw_w=720 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=257 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=271 drw_y=134 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=356 drw_y=203 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=357 drw_y=203 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=357 drw_y=203 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0):
Re: [Xpert]An question about StopVideo on ATI AiW
On Fri, 22 Feb 2002, [big5] Kevin Huang wrote: --- Mark Vojkovich [EMAIL PROTECTED] ªº°T®§¡G On Fri, 22 Feb 2002, [big5] Kevin Huang wrote: Hi Mark : Thanks for your answer in advance!! :) I'm working on Xv driver for my company's graphic chip, but I encounter an problem can't fint out the reason. Everytime I use other window to clip the video window or move it, StopVideo will be called makes the video flicker. This doesn't happen in ATI AiW r128. That's because the other drivers don't stop the video then. They stop it in a few seconds if PutImage doesn't get called again. How does the AiW driver make it ? I trace the code of PutImage StopVideo in r128_video.c but find nothing special. The StopVideo seems be called by X Server the AiW driver seems cannot control when StopVideo will be called. the driver only provide the StopVideo function call for X Server. Are you saying that the ATI driver's StopVideo is not called? It should be called when the window moves. Mark. Yes, ATI's StopVideo is not called when the video window moves, so it's video doesn't flicker during window moving. The StopVideo is only called at the end of playing mpeg2 video file with cleanup = 1. I attach part of the XFree86.0.log for reference. I see some confusion going on here.. There are two different StopVideo functions: one inside the driver and one in Xv library. The library function instructs X to call StopVideo function in the driver, but the latter can also be called by Xserver without request. For example, if you open a window and make a single PutImage or PutVideo call and then destroy the window Xserver will call StopVideo in the driver even though you did not make StopVideo call through Xv library. Does this help ? Vladimir Dergachev Kevin XFree86 Version 4.1.0 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 2 June 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Build Operating System: Linux 2.4.9-13custom i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Fri Feb 22 14:16:39 2002 (==) Using config file: /etc/X11/XF86Config Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) ServerLayout Simple Layout (**) |--Screen Screen 1 (0) (**) | |--Monitor My Monitor (**) | |--Device ATI All-in-Wonder (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (.skip) (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=56 drw_y=100 drw_w=720 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=257 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=258 drw_y=114 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0): R128PutImage src_x=0 src_y=0 src_w=719 src_h=479 (II) r128(0): drw_x=271 drw_y=134 drw_w=640 drw_h=480 width=720 height=480 sync=0 (II) r128(0): R128QueryImageAttributesG (II) r128(0):
