wine-devel October 2002

131 participants
357 discussions

by Nick

Hi, fixme:cursor:create_cursor Currently no support for cursors with 10 bits per pixel and similar messages are (seemingly) the only things preventing Heroes of Might and Magic 2 from being fully playable. Is this function really uncommonly used or something? It looks so basic... Just wondering, Nick

21 years, 7 months

RE: winaspi+libscg

by Patrik Stridvall

> Szombathelyi György <gyurco(a)freemail.hu> writes: > > > And how about a configure option to enable it? Default > option would be only > > the platform specific code, but a user can enable libscg > with a compile time > > option, and will receive a warning message about the license. Is it > > acceptable? If it is, I will make a patch. > > I don't think that would necessarily solve the issue. Some would argue > that the source itself is a derivative work that has to be under the > GPL. But the SOURCE is already under the LGPL which is compatible with the GPL so it doesn't matter if some part (whatever part) of the source might be required to be under the GPL. BINARIES might be required to be GPL:ed if and ONLY IF you enable the option. So it not really a problem for Wine AFAICS. > I don't want to debate the merits of that legal theory, Yes, we have debated this before. I know what you are going to answer, and you probably know what I'm going to say in return, so let us save the time and don't bother. :-) > but I > think it's better to avoid the issue completely. SIGH. As you wish.

21 years, 7 months

Re: winaspi+libscg

by Alexandre Julliard

Szombathelyi György <gyurco(a)freemail.hu> writes: > Here's my winaspi patches that uses libscg for the scsi transport layer. It > statically links libscg, which is the part of the cdrtools package (all > distribution have it). As far as I can tell libscg is under the GPL, not the LGPL. So we cannot use it in Wine. -- Alexandre Julliard julliard(a)winehq.com

21 years, 7 months

Wine installation troubles on Solaris

by Juraj Hercek

Hi, We have problem installing wine on solaris running on sparc. After some troubles we were able to compile and then partially install wine. Partially because, _$(WINE_ROOT)/tools/wineinstall_ script uses winelib's _regedit_ to register some entries in wine registry. But _regedit_ crashes. Here goes part of the output from _wineinstall_ script which tries to run _regedit_: ===========BEGIN OUTPUT=========== ... Created /home/user/.wine/config using default Wine configuration. You probably want to review the file, though. Compiling regedit... make: Nothing to be done for `all'. Preparing to install default Wine registry entries... Installing default Wine registry entries... err:heap:HEAP_GetPtr Invalid heap 00000000! Registry install failed. ===========END OUTPUT=========== Running wine alone (just to get help output) ends up in the same way - heap crash. Running "wine --debugmsg", the same... We used binutils-2.11.2 and gcc-2.95.3-toolchain for build process. Some information you could be interested in: ===========BEGIN OUTPUT=========== user% uname -a SunOS spruce.company 5.8 Generic_111433-02 sun4u sparc SUNW,Sun-Blade-1000 user% ldd miscemu/wine libntdll.dll.so => /usr/local/lib/libntdll.dll.so libwine.so => /usr/local/lib/libwine.so libwine_unicode.so => /usr/local/lib/libwine_unicode.so libresolv.so.2 => /usr/lib/libresolv.so.2 libsocket.so.1 => /usr/lib/libsocket.so.1 libnsl.so.1 => /usr/lib/libnsl.so.1 libm.so.1 => /usr/lib/libm.so.1 libc.so.1 => /usr/lib/libc.so.1 libdl.so.1 => /usr/lib/libdl.so.1 libmp.so.2 => /usr/lib/libmp.so.2 /usr/platform/SUNW,Sun-Blade-1000/lib/libc_psr.so.1 ===========END OUTPUT=========== My questions are: 1) Do you know the reason of the crash? (If so, please explain.) 2) Do you have any idea how to solve this problem? (If so, please explain) I'm asking because I'd like to avoid debugging... Thanks for reply! Juraj Hercek

21 years, 7 months

[Fwd: [BUGZILLA] Security Advisory]

by Shachar Shemesh

Who is maintaining our Bugzilla system? Shachar

21 years, 7 months

VB app broke again

by Fabian Cenedese

Hi I recently had a problem with a simple VB app, available as project and exe: http://www.winehq.com/hypermail/wine-devel/2002/09/0627.html I tried again with today's cvs and now the app doesn't even start. There is just an error "not enough memory" and the program quits again. So some recent changes must have broken something. bye Fabi

21 years, 7 months

Re: some rpcrt4 stuff

by Ove Kaaven

On Tue, 1 Oct 2002, Greg Turner wrote: > > CHANGELOG: > > * dlls/rpcrt4/rpcrt4.spec: Greg Turner <gmturner007(a)ameritech.net> > - flesh out some stubs. Implementations of these and much more can be found in this patch submission, which was apparently never applied: http://www.winehq.com/hypermail/wine-patches/2002/06/0103.html You can probably try to extract what you need from that patch if you want more rpcrt4 stuff.

21 years, 7 months

wine ToDo's Final

by Thomas Wickline

Hello, Here is the ToDo's to put on the status page. If anyone is aware of something that is wrong or out of place please let me know .. If everything looks good I will call it Final.......... Tom Wine ToDo's as of 10/01/02 Contact : twickline2(a)triad.rr.com Wine ToDo OverView Window management: * Window management needs proper inter-process handling of activation, focus, repaint. National Language Support: * Make sure ASCII functions call the Unicode one and not the other way around. * BiDi support * Add support for Hebrew and Arabic * Add support for more keyboard layouts to x11drv * Figure out what should be done for better support of Chinese, Korean, Japanese Winsock: * Winsock1 calls,in particular select(),use direct system calls instead of using related wine APIs * More unit tests need to be written * Make sure OOB data is handled properly. Check client-size blocking. * WS2: Support other kind of services, like IrDA. * Fix stubs left in ws2_32.spec. DirectSound: * Make the latency configurable (tunable). * More intelligent prebuffering. * Complete support for hardware secondary buffers through the HAL (for a future ALSA multimedia wave audio driver). * 3D sound buffers. * Sound capture (recording). Sound drivers: * Alsa driver (on final 0.9 interface) Video: * Implement native codecs (RLE...) GDI: * Write a DIB engine * DIB engine to do 32-bit graphics manipulation GDB: * Add the MSC/PDB info support to gdb Winedbg: * Speed up PDB support DDE: * Enhance memory management issues (interprocess sending) Wineconsole: * Add a (n)curse backend so that we can run CUI programs without using USER32 (and X11 behind) Native programs: * Winhelp: fix invocation thru WinHelp * Winedbg: make winedbg use dbghelp DLL File management: * Implement NT file namespace * UNC support * Allow flexibility in FS "mounting" (for example, SMB shares) Fonts: * Support for non-TT fonts (eg Type1, bitmap, ...) * Support for client side rendering on non-RENDER enabled XServers * Subpixel rendering - a.k.a. ClearType. * Integration with libfontconfig * Reduce per font startup time. * Libfontconfig support Printers: * Write a printer configuation applet * Fix the Type1 font downloader for HP4000 printers Tools: * Wine installation process should install and configure wine * Winemaker fixes * Run C regression tests on Windows with MSVC * Compile Wine with -DSTRICT * Work on WRC as it does not find system headers Instructions: * Write a proper Users Guide Introduction * Documentation updates Aspect or Component: * More DLL Separation * Review of Wine Server Protocol * Finalize Server Protocol * PAM (Pluggable Authentication Modules) * Visual C++'s native COM support * Create replacement of browser component (Internet Explorer/I Porting issues for Mingw/Cygwin/MS_VC * Better seperation of win16/32 code. * Remove/rewite win16/9x api dependancy on newer code * Remove/rewrite wineisms from code * Rewrite/fix unixisms in most WINE dlls * Documentation fixes low priority items: * VxD support with dynamic loading Add links to: Tasklets: http://bugs.winehq.com/buglist.cgi?keywords=tasklet tasklist: http://bugs.winehq.com/buglist.cgi?keywords=tasklist For a full list of .9/1.0 task's

21 years, 7 months

Re: winapi: new tool winapi_test for generating tests (again)

by Alexandre Julliard

Patrik Stridvall <ps(a)leissner.se> writes: > You have not applied it or replied. > > I would very must like an answer and > that you at the very least apply the > nocontroversial parts (winapi.*). Sorry, I have applied it now. The only change is that I don't think we should have multiple generated_xxx.c files for each dll, we should put all generated tests for a dll into the same file, so I have renamed the file to just generated.c. I'll let you change the corresponding winapi part. BTW as discussed recently, if you could please do diffs against /dev/null instead of attaching tar files, that would make it easier for me (and may prevent your patches from getting forgotten...) -- Alexandre Julliard julliard(a)winehq.com

21 years, 7 months

Re: Care for write protected resource in propsheet

by Alexandre Julliard

Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: > Changelog: > dlls/comctrl32/propsheet.c: > Hack around write protected in-memory resources Please let's not add more hacks on top of the existing ones. This thing needs to be fixed properly once and for all. -- Alexandre Julliard julliard(a)winehq.com

21 years, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel October 2002