March 2006 - Wine-Devel - list.winehq.org

Re: wglMakeCurrent

by Wino Rojo

Hi Raphael, >No it's use the "best visual" who match asked capacities - is this "best visual" the same as the one returned by "glxinfo -b" ? - the capacities asked by who? at this point we haven't call ChoosePixelFormat or SetPixelFormat yet >No your problem don't seems to be here. >can you send you glxinfo output. I presume you don't have glx1.3 support >In this case wine don't be able to get a fb config compatible with wine >window >(one day we'll fix the wine init ...) > This is the output of my glxinfo: name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.3 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, GLX_ARB_multisample, GLX_NV_float_buffer, GLX_ARB_fbconfig_float client glx vendor string: NVIDIA Corporation client glx version string: 1.3 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync, GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_NV_float_buffer, GLX_ARB_fbconfig_float GLX extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, GLX_ARB_multisample, GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NV41/PCI/SSE2/3DNOW! OpenGL version string: 2.0.0 NVIDIA 76.76 OpenGL extensions: GL_ARB_color_buffer_float, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, GL_ARB_half_float_pixel, GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shadow, GL_ARB_shader_objects, GL_ARB_shading_language_100, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3, GL_ARB_texture_float, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle, GL_ARB_transpose_matrix, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_window_pos, GL_ATI_draw_buffers, GL_ATI_texture_float, GL_ATI_texture_mirror_once, GL_S3_s3tc, GL_EXT_texture_env_add, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_compiled_vertex_array, GL_EXT_Cg_shader, GL_EXT_depth_bounds_test, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_framebuffer_object, GL_EXT_multi_draw_arrays, GL_EXT_packed_pixels, GL_EXT_pixel_buffer_object, GL_EXT_point_parameters, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_specular_color, GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_texture3D, GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod, GL_EXT_texture_lod_bias, GL_EXT_texture_mirror_clamp, GL_EXT_texture_object, GL_EXT_vertex_array, GL_HP_occlusion_test, GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, GL_KTX_buffer_region, GL_NV_blend_square, GL_NV_copy_depth_to_color, GL_NV_depth_clamp, GL_NV_fence, GL_NV_float_buffer, GL_NV_fog_distance, GL_NV_fragment_program, GL_NV_fragment_program_option, GL_NV_fragment_program2, GL_NV_half_float, GL_NV_light_max_exponent, GL_NV_multisample_filter_hint, GL_NV_occlusion_query, GL_NV_packed_depth_stencil, GL_NV_pixel_data_range, GL_NV_point_sprite, GL_NV_primitive_restart, GL_NV_register_combiners, GL_NV_register_combiners2, GL_NV_texgen_reflection, GL_NV_texture_compression_vtc, GL_NV_texture_env_combine4, GL_NV_texture_expand_normal, GL_NV_texture_rectangle, GL_NV_texture_shader, GL_NV_texture_shader2, GL_NV_texture_shader3, GL_NV_vertex_array_range, GL_NV_vertex_array_range2, GL_NV_vertex_program, GL_NV_vertex_program1_1, GL_NV_vertex_program2, GL_NV_vertex_program2_option, GL_NV_vertex_program3, GL_NVX_conditional_render, GL_SGIS_generate_mipmap, GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow, GL_SUN_slice_accum glu version: 1.3 glu extensions: GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat ---------------------------------------------------------------------- 0x21 24 tc 0 32 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x22 24 dc 0 32 0 r y . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x23 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x24 24 tc 0 32 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x25 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x26 24 tc 0 32 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x27 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x28 24 tc 0 32 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x29 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x2a 24 tc 0 32 0 r y . 8 8 8 0 4 16 0 16 16 16 16 0 0 None 0x2b 24 tc 0 32 0 r y . 8 8 8 8 4 16 0 16 16 16 16 0 0 None 0x2c 24 tc 0 32 0 r . . 8 8 8 0 4 16 0 16 16 16 16 0 0 None 0x2d 24 tc 0 32 0 r . . 8 8 8 8 4 16 0 16 16 16 16 0 0 None 0x2e 24 tc 0 32 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x2f 24 tc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x30 24 tc 0 32 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x31 24 tc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x32 24 tc 0 32 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x33 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x34 24 tc 0 32 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x35 24 tc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x36 24 tc 0 32 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x37 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x38 24 tc 0 32 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x39 24 tc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x3a 24 tc 0 32 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x3b 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x3c 24 tc 0 32 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x3d 24 tc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x3e 24 tc 0 32 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x3f 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x40 24 tc 0 32 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x41 24 tc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x42 24 tc 0 32 0 r y . 8 8 8 0 4 16 0 16 16 16 16 2 1 Ncon 0x43 24 tc 0 32 0 r y . 8 8 8 8 4 16 0 16 16 16 16 2 1 Ncon 0x44 24 tc 0 32 0 r y . 8 8 8 0 4 16 0 16 16 16 16 4 1 Ncon 0x45 24 tc 0 32 0 r y . 8 8 8 8 4 16 0 16 16 16 16 4 1 Ncon 0x46 24 tc 0 32 0 r . . 8 8 8 0 4 16 0 16 16 16 16 2 1 Ncon 0x47 24 tc 0 32 0 r . . 8 8 8 8 4 16 0 16 16 16 16 2 1 Ncon 0x48 24 tc 0 32 0 r . . 8 8 8 0 4 16 0 16 16 16 16 4 1 Ncon 0x49 24 tc 0 32 0 r . . 8 8 8 8 4 16 0 16 16 16 16 4 1 Ncon 0x4a 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x4b 24 dc 0 32 0 r . . 8 8 8 0 4 24 8 16 16 16 16 0 0 None 0x4c 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 0 0 None 0x4d 24 dc 0 32 0 r y . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x4e 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x4f 24 dc 0 32 0 r . . 8 8 8 0 4 24 0 16 16 16 16 0 0 None 0x50 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 0 0 None 0x51 24 dc 0 32 0 r y . 8 8 8 0 4 16 0 16 16 16 16 0 0 None 0x52 24 dc 0 32 0 r y . 8 8 8 8 4 16 0 16 16 16 16 0 0 None 0x53 24 dc 0 32 0 r . . 8 8 8 0 4 16 0 16 16 16 16 0 0 None 0x54 24 dc 0 32 0 r . . 8 8 8 8 4 16 0 16 16 16 16 0 0 None 0x55 24 dc 0 32 0 r y . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x56 24 dc 0 32 0 r y . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x57 24 dc 0 32 0 r . . 8 8 8 0 4 0 0 16 16 16 16 0 0 None 0x58 24 dc 0 32 0 r . . 8 8 8 8 4 0 0 16 16 16 16 0 0 None 0x59 24 dc 0 32 0 r y . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x5a 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x5b 24 dc 0 32 0 r y . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x5c 24 dc 0 32 0 r y . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x5d 24 dc 0 32 0 r . . 8 8 8 0 4 24 0 16 16 16 16 2 1 Ncon 0x5e 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 2 1 Ncon 0x5f 24 dc 0 32 0 r . . 8 8 8 0 4 24 0 16 16 16 16 4 1 Ncon 0x60 24 dc 0 32 0 r . . 8 8 8 8 4 24 0 16 16 16 16 4 1 Ncon 0x61 24 dc 0 32 0 r y . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x62 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x63 24 dc 0 32 0 r y . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x64 24 dc 0 32 0 r y . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x65 24 dc 0 32 0 r . . 8 8 8 0 4 24 8 16 16 16 16 2 1 Ncon 0x66 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 2 1 Ncon 0x67 24 dc 0 32 0 r . . 8 8 8 0 4 24 8 16 16 16 16 4 1 Ncon 0x68 24 dc 0 32 0 r . . 8 8 8 8 4 24 8 16 16 16 16 4 1 Ncon 0x69 24 dc 0 32 0 r y . 8 8 8 0 4 16 0 16 16 16 16 2 1 Ncon 0x6a 24 dc 0 32 0 r y . 8 8 8 8 4 16 0 16 16 16 16 2 1 Ncon 0x6b 24 dc 0 32 0 r y . 8 8 8 0 4 16 0 16 16 16 16 4 1 Ncon 0x6c 24 dc 0 32 0 r y . 8 8 8 8 4 16 0 16 16 16 16 4 1 Ncon 0x6d 24 dc 0 32 0 r . . 8 8 8 0 4 16 0 16 16 16 16 2 1 Ncon 0x6e 24 dc 0 32 0 r . . 8 8 8 8 4 16 0 16 16 16 16 2 1 Ncon 0x6f 24 dc 0 32 0 r . . 8 8 8 0 4 16 0 16 16 16 16 4 1 Ncon 0x70 24 dc 0 32 0 r . . 8 8 8 8 4 16 0 16 16 16 16 4 1 Ncon According to this, I do have glx 1.3 Thanks, W. PS. Guys, I'm sorry if I'm asking too many basic questions. I know about OpenGL and some X-Window programming, but I'm just learning wine, and I'd like to contribute to this amazing project, especially with the OpenGL/3D graphics stuff. _________________________________________________________________ Scan and help eliminate destructive viruses from your inbound and outbound e-mail and attachments. http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht… Start enjoying all the benefits of MSN® Premium right now and get the first two months FREE*.

March 16, 2006

Re: [RESEND] riched20: Fixed crash when the window procedure is called with NULL hWnd

by Alexandre Julliard

Phil Krylov <phil(a)newstar.rinet.ru> writes: > > ChangeLog: > > riched20: Fixed crash when the window procedure is called with NULL hWnd. You should check that you got a valid pointer from GetWindowLong, NULL is not the only invalid window handle you can get here. -- Alexandre Julliard julliard(a)winehq.org

March 16, 2006

Re: My two cents about winetools and the suggestions I read in Issue 308

by Tony Lambregts

Philip V. Neves wrote: > What I'm seeing here with the whole debate with wine and winetools is > that its a configuration management issue. The project is getting into > the stage where testing needs to be accomodated and so does getting > things working. I think whats currently available for managing > configurations to wine is innadequate. Even winecfg provides an > interface that is innadequate for making many changes in terms of dll > overrides. Plus it doesn't provide a mechanism for rolling those > changes back. Or even managing multiple configurations or modes so that > problems can be issolated. I think whats is comming out of the > winetools debate is better tools are needed for configuration > management. This isn't very revolutionary. Its a natural part of the > software development life cycle. As a project starts emerging from the > development phase ways to provide better configuration management start > showing themselves. > > Something that interfaces with the AppDB would be good. It would make > things easier. I think, given the complaints given by the developers are > also valid but so are the complaints made by the people trying to use > the program and even the testers. Most other projects don't need such > tools but this one does given what its trying to accomplish and the > complexity of whats being accomplished. Besides even windows XP has a > roll back feature now to fix problems. Why doesn't wine considering its > attempting a bug for bug compatibility with windows. This would be a > wise thing to implement just for sanities sake. > [Snip] > Something that allows the AppDB maintainers to distribute tweeks to > the configuration changes in the AppDB to users. So that even if we > aren't installing the programs on the system. The tweeks can still be > made on the fly. This would eliminate having to blow away the .wine > directory all the time. Blowing away the .wine directory is not a > desirable. A way for wine developers to distribute a test configuration > would also be a useful thing. That way we can test the software with > what the developers want us to test rather then shooting in the dark > only to see that the bug we reported is the same as some other bug we > reported. > > Such tools would be useful in debugging the entire framework and speed > up development. These are suggestions. I hope they help a bit. > I grudgingly have to agree that winecfg is at least partly inadequate. One of the things it is lacking is an export and and import function. I do not know how many times I have "blown away" my .wine directory. It would certainly save me some time if I could export the settings for a program and import them later. If we had the ability to import and export the settings for a program then it would also be possible for someone to upload that file somewhere (lets say the AppDB) and someone else could download it and use the same settings. The one problem that I can see with this is in the DLL overrides section. That is: if the import file contains a DLL override and the person does not have that dll installed we have a problem. Probably the best idea would be to search in the windows directories and warn the user if it could not find that file. Of course this does not address actually getting these dlls which is part of what WineTools does. Tony Lambregts

March 16, 2006

build stand alone binaries

by Benjamin Zeller

Hi there, is it possible to build real elf binaries with winelib? If i go through the tutorial on winehq.org i get only a appname.exe.so and i have to invoke wine to start the application. Is it possible to compile a binary wich can run stand alone? (Sorry for maybe posting this message twice i had some trouble with my email programm) regards benjamin z.

March 16, 2006

build stand alone binaries

by Benjamin Zeller

Hi there, is it possible to build real elf binaries with winelib? If i go through the tutorial on winehq.org i get only a appname.exe.so and i have to invoke wine to start the application. Is it possible to compile a binary wich can run stand alone? regards benjamin z.

March 16, 2006

Re: opengl32: make the old code before the "sync the dibsection to its pixmap" patch be selectable at runtime

by Leon Freitag

> I don't see any other way to speed this up the way it's being synced now, the > question is however, whether the apps really _should_ modify the bitmap on > windows too (don't know whether they would try to draw controls onto the > window and then it would be overdrawn by the opengl image; application like > Steam are trying to achieve similar, but they seemed to work well before) > Does this very rough&ready patch work any better? I'm getting undefined references to `___tls_get_addr' when trying to build with this patch. However my ld has this symbol for sure... $ nm /lib/ld-2.3.5.so | grep __tls_get_addr 0000dfc0 T ___tls_get_addr 0000d9d0 T __tls_get_addr 0000dfc0 t ___tls_get_addr_internal > If this patch improves performance I'll fix it to use Win32 TLS instead > of ELF TLS, it'll be interesting to see if that changes makes a > difference too. perhaps it will compile on my machine then... Leon

March 16, 2006

Re: May be a bad idea to have Winetools in the next SUSE release

by Joachim von Thadden

Am Fri, Mar 10, 2006 at 12:55:20AM +0100 schrieb Sven Paschukat: > Marcus Meissner schrieb: > >Hmm, I have some kind of recommendation here. > > > >What about winetools using ".winetools" as WINEPREFIX setting? > > > >This would make it possible to keep a ".wine" for the purists, and > >".winetools" for the "just get things done" people. > > > >Up to now winetools does not seem to honor a WINEPREFIX setting > >(also a bug I think). > > > >Ciao, Marcus > > Hey, you steal Joachim's ideas ;-) > > That's one point we have discussed in similar form. One directory for > the present winetools mode and another for a new builtin mode where > winetools just acts as a menu driven loader and installer. Sorry for the delay: I have been on CeBIT computer fair. To come to an end with that: Sven and I are doing the following for WineTools at the moment: - change WineTools to use WINEPREFIX - using a standard WINEPREFIX="$HOME/.winetools" if not set otherwise - change * to builtin,native - change version to WinXP - run as many apps as possible without tweaking The last one is the annoying one as it needs many testing *and* I know of no way to say "do not use the default" in winecfg or the registry. If there is a way, please mail me. I think using the AppDB for getting install and execution infos for programs is very hard to accomplish. We were already thinking about a way to send data of successful installations or executions automatically into a DB but dropped that. It would be very nice to have but it has to be - repeated for every version of wine - checked for correctness - if there are competing entries they have to be manually resolved - probably many other problems Regards Joachim von Thadden -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"

March 16, 2006

Re: My two cents about winetools and the suggestions I read in Issue 308

by Joachim von Thadden

Am Thu, Mar 16, 2006 at 10:48:06AM +0900 schrieb Mike McCormack: > > Philip V. Neves wrote: > > >Something that interfaces with the AppDB would be good. It would make > >things easier. I think, given the complaints given by the developers are > >also valid but so are the complaints made by the people trying to use > >the program and even the testers. Most other projects don't need such > >tools but this one does given what its trying to accomplish and the > >complexity of whats being accomplished. Besides even windows XP has a > >roll back feature now to fix problems. Why doesn't wine considering its > >attempting a bug for bug compatibility with windows. This would be a > >wise thing to implement just for sanities sake. > > IMO, the best thing for Wine would be to have a simple front end with a > list of freely downloadable applications that work "out of the box" with > no configuration changes. > > Click -> Download application -> Install -> Run This is exactly what we try to have with the next version of WineTools. Regards Joachim von Thadden -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"

March 16, 2006

Re: My two cents about winetools and the suggestions I read in Issue 308

by Mike McCormack

Philip V. Neves wrote: > Something that interfaces with the AppDB would be good. It would make > things easier. I think, given the complaints given by the developers are > also valid but so are the complaints made by the people trying to use > the program and even the testers. Most other projects don't need such > tools but this one does given what its trying to accomplish and the > complexity of whats being accomplished. Besides even windows XP has a > roll back feature now to fix problems. Why doesn't wine considering its > attempting a bug for bug compatibility with windows. This would be a > wise thing to implement just for sanities sake. IMO, the best thing for Wine would be to have a simple front end with a list of freely downloadable applications that work "out of the box" with no configuration changes. Click -> Download application -> Install -> Run This would make it easy to for users to get applications working, find and report regressions, and fully test Wine, and would fully support developers in our quest to build a fully free environment for running Windows applications. Mike

March 16, 2006

Yet Another MS Windows API Emulation - SanOS, an small OS

by agaro

I don't know if somebody already found this, but may be relevant to wine-devel comunity (google don't found nothing about in this list): http://www.jbox.dk/sanos/ And the code (I haven't really looked much there): http://www.jbox.dk/sanos/source/index.html The code is released under an "BSD style" license. The win32 exception handling implementation is based on Wine code: http://www.jbox.dk/sanos/contributions.htm []s Augusto Arcoverde da Rocha

March 16, 2006

re: More dogfood tests

by Dan Kegel

> I have found very few problems, mainly just images being color-reversed, > and only on PNG of certain types. That sounds like the .gif bug here: http://bugs.winehq.org/show_bug.cgi?id=4529 Can you give the URL of one of the busted PNG's? - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv

March 16, 2006

More dogfood tests

by Segin

I have also started using Firefox in Wine for everything, namely because native lost a lib, old mozilla and opera and native firefox cause X to malloc() like mad (pkill -9 the broswer to cause X to free() ). I have found very few problems, mainly just images being color-reversed, and only on PNG of certain types. Also, Wine is MUCH faster if you have NPTL as your only threading method in glibc. (think a 15x improvement in speed here...) Wine also seems to know about the XDND X extension, cause it knows what GTK+2 widgets can be dragged and dropped onto, but otherwise the actual drag-and-drop procedure is a null effect. Ahh to hell with it, let's get to the speed tests. time wine firefox.exe, cold cache: real 0m48.895s (about 45s, really) user 0m4.116s sys 0m1.589s hot cache: real 0m9.287s (about 7.5s, really) user 0m3.966s sys 0m1.026s (Please note that the "real" time is off by about 1-2 seconds, to allow for me to quit Firefox.) Here we do the 7-Zip File Manager. Errors: err:listview:LISTVIEW_WindowProc unknown msg 2005 wp=00000001 lp=00000000 err:rebar:REBAR_AdjustBands Phase 1 failed, x=1000, maxx=-4, start=1, end=1 time wine 7zFM.exe, cold cache: real 0m34.815s (about 30s) user 0m1.044s sys 0m0.672s and with a hot cache: real 0m5.105s (about 4s, actually) user 0m0.997s sys 0m0.378s And now we do PuTTY: (no errors) Cold cache: real 0m39.382s (37s) user 0m1.023s sys 0m0.868s Hot cache: real 0m3.170s (no ajustment) user 0m0.978s sys 0m0.395s On a normal Windows system, the cache is always hot (all the core DLLs are always loaded), so the hot cache times actually rival a real Windows system, especially the one for PuTTY (which beats every test on a real Windows box I have done except those on more powerful hardware)

March 16, 2006

Re: wglMakeCurrent

by Raphael

Sorry for my late response but i haven't much time now > I'm not familiar at all with wine, so I'm not sure how we should fix this > (but it seems this would fix a lot of opengl related problems) > > When we first call X11DRV_setup_opengl_visual, I guess it's using the first > visual ID. No it's use the "best visual" who match asked capacities > But later, when we create a pixelformat descriptor, maybe we > should select a better visual (one equal or similar to the description > given in pixelformat), so when we later call wlgMakeCurrent, both visuals > will be the same No your problem don't seems to be here. can you send you glxinfo output. I presume you don't have glx1.3 support In this case wine don't be able to get a fb config compatible with wine window (one day we'll fix the wine init ...) Regards, Raphael

March 16, 2006

Re: Francois Gouget : user32: Handle WM_ENDSESSION in DefWinProc().

by James E. Lang

Francois Gouget wrote at 0:06 on 12 Mar 2006: > Rein Klazes wrote: > [...] > > This patch is causing a problem in Pegasus Mail. Closing some dialogs > > cause termination of the complete program. [...] I see that this is still a problem in 0.9.10 so I've fallen back again to 0.9.8. -- Jim

March 16, 2006

Re: Vista compatibility page

by Stefan Dösinger

> I mean .... 5 years! FIVE YEARS! And this is what they have to show for > it? A bunch of .NET APIs that they intend to backport to XP, and which > require a runtime nobody seems to be using for desktop apps anyway. An > improved file protection hack. Some improved security, and a display > rewrite equivalent to what David Reveman was able to produce on his own > in only 2 years? Not to forget the Digital Rights Management stuff. But thats definitly something I don't want. Improved security with a lot of "backdoors" for Windows Installer to stay user-friedly. It doesn't look like Vista will enlarge Wines ToDo list noticeable ;)

March 15, 2006

Re: wglMakeCurrent

by Wino Rojo

>See if you can tell from my log: >http://www.chez.com/alors/logfile > Jesse, I can't access your log at that page (I got an error). Could you please send it to me? Thanks, W _________________________________________________________________ MSN® Calendar keeps you organized and takes the effort out of scheduling get-togethers. http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht… Start enjoying all the benefits of MSN® Premium right now and get the first two months FREE*.

March 15, 2006

My two cents about winetools and the suggestions I read in Issue 308

by Philip V. Neves

What I'm seeing here with the whole debate with wine and winetools is that its a configuration management issue. The project is getting into the stage where testing needs to be accomodated and so does getting things working. I think whats currently available for managing configurations to wine is innadequate. Even winecfg provides an interface that is innadequate for making many changes in terms of dll overrides. Plus it doesn't provide a mechanism for rolling those changes back. Or even managing multiple configurations or modes so that problems can be issolated. I think whats is comming out of the winetools debate is better tools are needed for configuration management. This isn't very revolutionary. Its a natural part of the software development life cycle. As a project starts emerging from the development phase ways to provide better configuration management start showing themselves. Something that interfaces with the AppDB would be good. It would make things easier. I think, given the complaints given by the developers are also valid but so are the complaints made by the people trying to use the program and even the testers. Most other projects don't need such tools but this one does given what its trying to accomplish and the complexity of whats being accomplished. Besides even windows XP has a roll back feature now to fix problems. Why doesn't wine considering its attempting a bug for bug compatibility with windows. This would be a wise thing to implement just for sanities sake. So I'd like to provide an addition to Jason Greens brain dump * AppDB would have to be extended to be able to get and report this data, and it would make sense for each App's maintainer to be able to manage that information. * Biggest issue here is that this information could have a tendency to change very rapidly, so it might overload the app maintainers if they had to track this for each version of wine. What I think would make sense is to have regular snapshots (every 3 months?) and release a new version of "Winetools Plus" or whatever you want to call this thing a month later to give the maintainers time to update each of their apps based on the frozen version. (I think multiple versions of the AppDB would be useful. Similar to the Release and Release candidate type way of doing things.) * Data needed: AppID, AppVersionID, WineVersionID, Window Version, DLL Overrides, Window settings (fullscreen/windowed - sometimes and issue), Sound options, Video acceleration required, General notes or HOWTO's, etc. You would need separate overrides/settings for Installing vs. Running the app. * AppDB could dump this information to an xml format which "Winetools Plus" could be distributed with. Maybe have an option to download the latest xml file directly from winehq.org. * The 'Winetools Plus' front-end would just be a menu which would query all of the apps in the xml dump. The user picks they app they want to install, and it reads the necessary information, verifies the source installation media, and goes at it. * Applying patches to apps might get tricky (e.g., where wine only successfully runs version 1.5 of the app, but 1.0 is on the CD), but I'm sure it could be worked out. * A Way to roll back DLL overrides. * A Way store roll multiple registry configurations so that we establish a base reference configuration and a test configuration. Or even multiple test configurations. * An AppDB tool that allows changes to the DLL configuration in the AppDB to be made easily. * A way to detect the version of wine and provide configuration changes given that version of wine. * A way to report bugs to the appDB maintainers about configuration problems. A nice to have would be Something that allows the AppDB maintainers to distribute tweeks to the configuration changes in the AppDB to users. So that even if we aren't installing the programs on the system. The tweeks can still be made on the fly. This would eliminate having to blow away the .wine directory all the time. Blowing away the .wine directory is not a desirable. A way for wine developers to distribute a test configuration would also be a useful thing. That way we can test the software with what the developers want us to test rather then shooting in the dark only to see that the bug we reported is the same as some other bug we reported. Such tools would be useful in debugging the entire framework and speed up development. These are suggestions. I hope they help a bit.

March 15, 2006

Re: wglMakeCurrent

by Wino Rojo

so, in your system the default visual ID is 0x28, and later my app create contexts with visual ID 0x23 but everything works fine for you... ok, back to square one :-( _________________________________________________________________ Powerful Parental Controls Let your child discover the best the Internet has to offer. http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht… Start enjoying all the benefits of MSN® Premium right now and get the first two months FREE*.

March 15, 2006

Re: wglMakeCurrent

by Jesse Allen

On 3/15/06, Wino Rojo <winorojo(a)hotmail.com> wrote: > Ok, so now we know what's is going on here :-) > > I'm not familiar at all with wine, so I'm not sure how we should fix this > (but it seems this would fix a lot of opengl related problems) > > When we first call X11DRV_setup_opengl_visual, I guess it's using the first > visual ID. Hold on, the log shows it picking another in your test program: trace:opengl:X11DRV_setup_opengl_visual Visual ID 28 Chosen >From glxinfo: 0x23 24 tc 0 32 0 r . . 8 8 8 8 0 24 0 0 0 0 0 0 0 None 0x28 24 tc 0 32 0 r y . 8 8 8 8 0 24 8 0 0 0 0 0 0 None > But later, when we create a pixelformat descriptor, > maybe we > should select a better visual (one equal or similar to the description given > in pixelformat), so when we later call wlgMakeCurrent, both visuals will be > the same > > I hope this makes sense... > > Cheers, > > Wino > See if you can tell from my log: http://www.chez.com/alors/logfile Someone that knows wgl want to comment? Jesse

March 15, 2006

Re: wglMakeCurrent

by Wino Rojo

Ok, so now we know what's is going on here :-) I'm not familiar at all with wine, so I'm not sure how we should fix this (but it seems this would fix a lot of opengl related problems) When we first call X11DRV_setup_opengl_visual, I guess it's using the first visual ID. But later, when we create a pixelformat descriptor, maybe we should select a better visual (one equal or similar to the description given in pixelformat), so when we later call wlgMakeCurrent, both visuals will be the same I hope this makes sense... Cheers, Wino _________________________________________________________________ Don't just Search. Find! http://search.sympatico.msn.ca/default.aspx The new MSN Search! Check it out!

March 15, 2006

Re: wglMakeCurrent

by Jesse Allen

On 3/15/06, Wino Rojo <winorojo(a)hotmail.com> wrote: > Hi Jesse, > > That's very interesting... Yes, I'm using a nvidia card. I think I know the > reason why is working for you but not for me > > glxinfo tells me that my first visual ID is 0x21. However, on some ATI cards > glxinfo reports 0x23 as the first visual, which is the same visual ID of the > contexts I create. > > So maybe my program works fine for you because, just by coincidence, the > visual ID of my contexts are the same as the first visual ID reported by > X-Window > > Please, let me know the first visual ID reported by glxinfo is 0x23 in your > system. This will confirm my theroy :-) > > Thanks, > > Wino > Yes, you are correct that 0x23 is the first one.

March 15, 2006

Re: wglMakeCurrent

by Wino Rojo

Hi Jesse, That's very interesting... Yes, I'm using a nvidia card. I think I know the reason why is working for you but not for me glxinfo tells me that my first visual ID is 0x21. However, on some ATI cards glxinfo reports 0x23 as the first visual, which is the same visual ID of the contexts I create. So maybe my program works fine for you because, just by coincidence, the visual ID of my contexts are the same as the first visual ID reported by X-Window Please, let me know the first visual ID reported by glxinfo is 0x23 in your system. This will confirm my theroy :-) Thanks, Wino _________________________________________________________________ Take advantage of powerful junk e-mail filters built on patented Microsoft® SmartScreen Technology. http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=ht… Start enjoying all the benefits of MSN® Premium right now and get the first two months FREE*.

March 15, 2006

Re: wglMakeCurrent

by Jesse Allen

On 3/15/06, Wino Rojo <winorojo(a)hotmail.com> wrote: > Hi guys > > I send a reply to the list a couple of days ago, but I attached my exe file > and it seems it was blocked but hotmail... > > First, thanks a lot for all your replies... Jesse, I've made the changes > proposed in those patches, but it didn't work :-( > > After further inspection, it seems the problem is when I call wglMakeCurrent > for a context which shares display lists with another context. I've attached > the program and the source code, so you can try it. > > > As I said, this program works just fine in Windows, so we must be doing > something differente in wine > > Any ideas/hints? > > Thanks > > Hi I tried your test program. I have the same results as with War3. Your program worked for me. I can't reproduce the same problem using DRI (Radeon 9200). So there is something specific about your configuration. I think you are using an nvidia card. Anyways, those patches didn't work either so 4604 is likely not a duplicate of 4143. Jesse

March 15, 2006

Re: ie6sp1 install failure

by James Hawkins

On 3/15/06, Samium Gromoff <_deepfire(a)mail.ru> wrote: > I tried to install IE6SP1 under wine 0.9.9, in order to allow .NET > framework to be installed, and it failed like this: > I'll look into this soon. I'm on vacation right now though. -- James Hawkins

March 15, 2006

Re: wglMakeCurrent

by Wino Rojo

Hi guys I send a reply to the list a couple of days ago, but I attached my exe file and it seems it was blocked but hotmail... First, thanks a lot for all your replies... Jesse, I've made the changes proposed in those patches, but it didn't work :-( After further inspection, it seems the problem is when I call wglMakeCurrent for a context which shares display lists with another context. I've attached the program and the source code, so you can try it. This is the output of the trace+opengl: trace:opengl:has_opengl GLX is up and running error_base = 77 trace:opengl:X11DRV_setup_opengl_visual Visual ID 21 Chosen trace:opengl:X11DRV_ChoosePixelFormat (0x403a28a8,0x406afdac) trace:opengl:dump_PIXELFORMATDESCRIPTOR - size / version : 40 / 1 trace:opengl:dump_PIXELFORMATDESCRIPTOR - dwFlags : PFD_DOUBLEBUFFER PFD_DRAW_TO_WINDOW PFD_SUPPORT_OPENGL trace:opengl:dump_PIXELFORMATDESCRIPTOR - iPixelType : PFD_TYPE_RGBA trace:opengl:dump_PIXELFORMATDESCRIPTOR - Color : 24 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Red : 8 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Green : 8 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Blue : 8 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Alpha : 8 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Accum : 0 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Depth : 24 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Stencil : 0 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Aux : 0 trace:opengl:dump_PIXELFORMATDESCRIPTOR - iLayerType : PFD_MAIN_PLANE trace:opengl:X11DRV_SetPixelFormat (0x403a28a8,3,0x406afdac) trace:opengl:X11DRV_SetPixelFormat FBConfig have : trace:opengl:X11DRV_SetPixelFormat - FBCONFIG_ID 0x73 trace:opengl:X11DRV_SetPixelFormat - VISUAL_ID 0x23 trace:opengl:X11DRV_SetPixelFormat - DRAWABLE_TYPE 0x7 trace:opengl:X11DRV_GetPixelFormat (0x403a28a8): returns 3 trace:opengl:wglCreateContext (0x1cc)->(PF:3) trace:opengl:wglCreateContext creating context 0x403a2a40 (GL context creation delayed) trace:opengl:X11DRV_ChoosePixelFormat (0x403a2cc0,0x406afdac) trace:opengl:dump_PIXELFORMATDESCRIPTOR - size / version : 40 / 1 trace:opengl:dump_PIXELFORMATDESCRIPTOR - dwFlags : PFD_DOUBLEBUFFER PFD_DRAW_TO_WINDOW PFD_SUPPORT_OPENGL trace:opengl:dump_PIXELFORMATDESCRIPTOR - iPixelType : PFD_TYPE_RGBA trace:opengl:dump_PIXELFORMATDESCRIPTOR - Color : 24 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Red : 8 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Green : 8 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Blue : 8 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Alpha : 8 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Accum : 0 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Depth : 24 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Stencil : 0 trace:opengl:dump_PIXELFORMATDESCRIPTOR - Aux : 0 trace:opengl:dump_PIXELFORMATDESCRIPTOR - iLayerType : PFD_MAIN_PLANE trace:opengl:X11DRV_SetPixelFormat (0x403a2cc0,3,0x406afdac) trace:opengl:X11DRV_SetPixelFormat FBConfig have : trace:opengl:X11DRV_SetPixelFormat - FBCONFIG_ID 0x73 trace:opengl:X11DRV_SetPixelFormat - VISUAL_ID 0x23 trace:opengl:X11DRV_SetPixelFormat - DRAWABLE_TYPE 0x7 trace:opengl:X11DRV_GetPixelFormat (0x403a2cc0): returns 3 trace:opengl:wglCreateContext (0x1dc)->(PF:3) trace:opengl:wglCreateContext creating context 0x403a2e58 (GL context creation delayed) trace:opengl:wglShareLists (0x403a2a40, 0x403a2e58) trace:opengl:describeContext Context 0x403a2a40 have (vis:0x7c1782d0): trace:opengl:describeContext - FBCONFIG_ID 0x73 trace:opengl:describeContext - VISUAL_ID 0x23 trace:opengl:wglShareLists created a delayed OpenGL context (0x7c190318) for Wine context 0x403a2a40 trace:opengl:describeContext Context 0x403a2e58 have (vis:0x7c18a4d0): trace:opengl:describeContext - FBCONFIG_ID 0x73 trace:opengl:describeContext - VISUAL_ID 0x23 trace:opengl:wglShareLists created a delayed OpenGL context (0x7c1b1590) for Wine context 0x403a2e58 sharing lists with OpenGL ctx 0x7c190318 trace:opengl:wglGetCurrentDC () trace:opengl:wglGetCurrentDC no Wine context found for GLX context 0x7c096448 trace:opengl:wglGetCurrentContext () trace:opengl:wglGetCurrentContext returning (nil) (GL context 0x7c096448) trace:opengl:wglMakeCurrent (0x1dc,0x403a2e58) trace:opengl:wglMakeCurrent make current for dis 0x7c0657f0, drawable 0x3800002, ctx 0x7c1b1590 X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 144 (GLX) Minor opcode of failed request: 5 (X_GLXMakeCurrent) Serial number of failed request: 120 Current serial number in output stream: 120 My guess is that when we call wglMakeCurrent for the context with the shared lists, it has a VISUAL_ID of 0x23, but X11DRV_setup_opengl_visual chosed a Visual ID of 0x21, and hence the BadMatch error. As I said, this program works just fine in Windows, so we must be doing something differente in wine Any ideas/hints? Thanks _________________________________________________________________ Don't just Search. Find! http://search.sympatico.msn.ca/default.aspx The new MSN Search! Check it out!

March 15, 2006