July 2001 - Wine-Devel - list.winehq.org

Re: winapi update

by Alexandre Julliard

Patrik Stridvall <ps(a)leissner.se> writes: > A full install is largely meaningless since the winapi tools are made > for work on a Wine source tree, so making them independant of such > a tree is largely meaningless. Agreed. > In short, please apply it, they facillitates using the > winapi tools alot and might make more people actually > use them. They don't hurt anything. The problem is if we make it part of the default make install all Wine distributions will include these non-functional (from the user POV) scripts, and I don't think this is a good idea. So I have applied it but it doesn't run by default; developers who want it should run make install in the tools/winapi directory. -- Alexandre Julliard julliard(a)winehq.com

July 30, 2001

broken misc/version.c (patch 1.43 -> 1.44) WIN95 value in version16

by Ladislav Sladecek

Two days ago a 16 bit application, which I use, started to complain about unknown windows version. After I rgressed to 1.43 of misc/version.c, everything was OK. I found the problem in the GetVersionInfo value that you changed at line 75 of the file. My windows 95 returns 0xC0000004 in WIN32 and 0x07005F03 in WIN16. You changed the 16bit value from 0x7005F03 to 0x7000304. Can you please check this? Do you have some docs? I think that we that we are both right; the value probably depends on longitude, altitude, and Windows language version. Mine iWindows 95 is Czech Edition, SR2. Regards Ladislav Sladecek

July 30, 2001

RE: winapi update

by Patrik Stridvall

> Patrik Stridvall <ps(a)leissner.se> writes: > > > I have resent winapi_install patch. > > > > While it probably that you didn't apply > > it because of lack of time I resend > > for your convinience. If not please > > explain. > > Correct me if I'm wrong, but it seems you are not actually installing > anything, only a script that needs the Wine source tree to work. That is a correct conclusion. > I don't really see the point. The point is that when you are in some sub directory of a wine tree, you can just write winapi_check or make_filter and whatever and it will call the correct version of the tool. Instead of having to type, if you are in dlls/winsock. ../../tools/winapi_check Sure you can currently do make winapi_check or make filter and adding winapi_{extract,fixup} is trivial but giving arguments through make is a little awkward. That why I wrote a few script to fix this and now when I have a tool (make_filter) that could possibly enjoy a wider use I decided to make a formalized "install" for them. > If you want to install something it should > be a complete installation that works without external files (not that > I suggest doing that for winapi_check, at least not by default). A full install is largely meaningless since the winapi tools are made for work on a Wine source tree, so making them independant of such a tree is largely meaningless. Well they actually are indendent of the specific tree they where install from. They do not reference to it at all. They use the current directory to find the real winapi tools in that tree. They will work equally well with any tree (of a later date than your hopefull application of the patch that is). They are as they are by design, not by mistake, and complete installation of them is almost completly meaningless. Sure there might be future winapi tools worthy of a complete install, a future tool for automatical generation of .spec files from any Winelib application, that we talked about some time ago, comes to mind, but I'm not there quite yet. I have begun to implement simple typedef parsing but it doesn't work 100% yet. In short, please apply it, they facillitates using the winapi tools alot and might make more people actually use them. They don't hurt anything.

July 30, 2001

Re: winapi update

by Alexandre Julliard

Patrik Stridvall <ps(a)leissner.se> writes: > I have resent winapi_install patch. > > While it probably that you didn't apply > it because of lack of time I resend > for your convinience. If not please > explain. Correct me if I'm wrong, but it seems you are not actually installing anything, only a script that needs the Wine source tree to work. I don't really see the point. If you want to install something it should be a complete installation that works without external files (not that I suggest doing that for winapi_check, at least not by default). -- Alexandre Julliard julliard(a)winehq.com

July 30, 2001

Re: Relocatoion and ExceptionFilter problem?

by Francois Gouget

On Mon, 30 Jul 2001, EriK W wrote: > Now I finally made a wine , :) > But I can't get any program to excute so far, mostly It is like > > bash-2.03# wine --winver win95 sol.exe > err:seh:UnhandledExceptionFilter Couldn't start debugger (debugger/winedbg > 134639312 24) > (2) > Read the Wine Developers Guide on how to set up winedbg or another debugger What we need are the lines that come before. See: http://wine.codeweavers.com/docs/wine-user/bugs.shtml#BUG-REPORTING > bash-2.03# wine --winver win98 icq2000b.exe > err:win32:do_relocations Standard load address for a Win32 program not > available - patched kernel ? > err:win32:do_relocations FATAL: Need to relocate > F:\export\home\ericw\system\icq2000b.exe, but no relocation records present > (stripped during link). Try to run that file directly ! > wine: can't exec 'icq2000b.exe': error=21 Many windows executables must be loaded at a specific address. Unfortunately it seems that on your system this address is already in use so that we cannot load the executable there. In the past this happened regularly because we were loading all programs in a single address space. So after loading the first program we were unable to load any other program at that same address. Hence the suggestion to "Try to run that file directly !" in the error message. But this is all a thing of the past as now each application is loaded in its own address space. So there must be something else using the address that Wine wants. It's strange because I don't remember people having this problem on Solaris before. What you can do is run Wine in gdb and then type 'info sharedlibrary' to get a map of the process memory and see what is using the address Wine needs. So you will also need to fid out where Wine is trying to load the exe. You can probably get this info by looking at the loader source, activating the relevant debug channels, or running dumpbin (comes with VC++) on the app. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Hiroshima '45 - Czernobyl '86 - Windows '95

July 30, 2001

Re: Prevent excessive clipping in SysListView32

by Ulrich Weigand

Bill Medland wrote: > Ulrich Weigand <weigand(a)immd1.informatik.uni-erlangen.de> wrote in article > <200107262124.XAA25786(a)faui11.informatik.uni-erlangen.de>... > > No, 'inline' must not change the semantics of the routine in any way, > > including static variables. > > > > If the app behaves differently when 'perfect_graphics' is inlined, this > > is a compiler bug. Which compiler version are you using? > > Excuse my ignorance. rpm says it is 2.96-81. How do I ask gcc what > version IT thinks it is? > (Running on RH7.1; how do I get the kernel version? rpm says 2.4.2-2) gcc 2.96 is the version RedHat is currently using; it is not an 'official' version supported by the gcc folks ... However, RedHat has been fixing quite a bunch of bugs in their compiler; it might be worthwhile to check whether this inlining bug is fixed in the most recent RedHat update. (Check the RPM sublevel to find out whether you have the most recent update, that's the -81 in your case. AFAIK, bugfix updates can be downloaded from the RedHat FTP site ...) Bye, Ulrich -- Dr. Ulrich Weigand weigand(a)informatik.uni-erlangen.de

July 30, 2001

Relocatoion and ExceptionFilter problem?

by EriK W

Now I finally made a wine , :) But I can't get any program to excute so far, mostly It is like bash-2.03# wine --winver win95 sol.exe err:seh:UnhandledExceptionFilter Couldn't start debugger (debugger/winedbg 134639312 24) (2) Read the Wine Developers Guide on how to set up winedbg or another debugger or bash-2.03# wine --winver win98 icq2000b.exe err:win32:do_relocations Standard load address for a Win32 program not available - patched kernel ? err:win32:do_relocations FATAL: Need to relocate F:\export\home\ericw\system\icq2000b.exe, but no relocation records present (stripped during link). Try to run that file directly ! wine: can't exec 'icq2000b.exe': error=21 This wine seems taste not good, :) Francois Gouget wrote: > On Thu, 26 Jul 2001, EriK W wrote: > > > > What does not work? Do you have unicode/libwine_unicode.so or not? > > > Does the following command run or does it say it cannot find > > > libwine_unicode.so? > > > > > I does have the libwine_unicode.so > > but it just don't go to ~unicode directory to search for it, it always > > report " can't find it in /usr/local/lib" I don't know why, I am using bash, > > so I just simply copied libwine_unicode.so over to make it happy. > > I was wondering if it was the shell not exporting the environment > variable or something. Since you're using bash it should be all fine. > So you have to figure out why setting LD_LIBRARY_PATH does not work. > It's supposed to work. I'm 99.9% sure I did use it on Sparc Solaris so I > really don't see why it would not work on Solaris x86. Plus > LD_LIBRARY_PATH is such an important thing that it would be very > surprising if it really did not work and nothing else was broken in your > system. > > Did you try specifying an absolute path like: > LD_LIBRARY_PATH=/export/home/system/wine-20010629/unicode ./tools/winebuild/winebuild > > What does 'echo $LD_LIBRARY_PATH' normally say? Is it empty? > > [...] > > take it out? > > Can I do that by commenting " > > LIBPROGRAMS = \ > > debugger/winedbg" ? > > The following patch should do that nicely: > > --- cut here --- > Index: Makefile.in > =================================================================== > RCS file: /home/wine/wine/debugger/Makefile.in,v > retrieving revision 1.24 > diff -u -r1.24 Makefile.in > --- Makefile.in 2000/12/29 05:38:00 1.24 > +++ Makefile.in 2001/07/27 01:39:15 > @@ -3,7 +3,7 @@ > TOPOBJDIR = .. > SRCDIR = @srcdir@ > VPATH = @srcdir@ > -MODULE = winedbg > +MODULE = #winedbg > > C_SRCS = \ > break.c \ > --- Makefile.orig Thu Jul 26 19:03:36 2001 > +++ Makefile Thu Jul 26 19:00:53 2001 > @@ -3,7 +3,7 @@ > TOPSRCDIR = .. > TOPOBJDIR = .. > SRCDIR = . > -MODULE = winedbg > +MODULE = #winedbg > > C_SRCS = \ > break.c \ > --- cut here --- > > -- > Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ > Broadcast message : fin du monde dans cinq minutes, repentez vous !

July 30, 2001

Re: Possible printer driver bug

by Huw D M Davies

On Sun, Jul 29, 2001 at 05:31:05PM +0300, Jukka Heinonen wrote: > Wine compiled from CVS crashes since file "wine/dlls/gdi/driver.c" > passes a NULL pointer to function CreateICA. The following > patch stops crashing, but since I have no idea how Wine > printer drivers work, this patch might be plain wrong. > > After this patch, Wine no longer crashes, but I haven't > been able to test whether printing works or not. > > Index: wine/dlls/gdi/driver.c > =================================================================== > RCS file: /home/wine/wine/dlls/gdi/driver.c,v > retrieving revision 1.2 > diff -u -r1.2 driver.c > --- wine/dlls/gdi/driver.c 2001/07/28 00:18:02 1.2 > +++ wine/dlls/gdi/driver.c 2001/07/29 14:10:18 > @@ -376,7 +376,7 @@ > > if(!DRIVER_GetDriverName( lpszDevice, buf, sizeof(buf) )) return -1; > > - if (!(hdc = CreateICA( buf, NULL, lpszPort, NULL ))) return -1; > + if (!(hdc = CreateICA( buf, lpszDevice, lpszPort, NULL ))) return -1; > > if ((dc = DC_GetDCPtr( hdc ))) > { > Looks good. There's also another one in GDI_CallDeviceCapabilities16 (line 424) that needs the same fix. Could you fix them both and send the patch to wine-patches ? Huw.

July 30, 2001

Hi There

by Robert Laverick

Hi, I'm new to wine and while I've been messing about with it I've not acctualy done anything significant. I'm mostly into Java but picked up some C recently doing some parallel comutational stuff as part of my Final year project as part of my degree. Now I'm officaly Unemployed as apposed to a Student I can give of my time freely. I'd love to get into this, if someone could give me a point at something that needs a good looking at then I'll start there. My biggest motivation is to get to understand this whole thing better and (if I'm luck) get Diablo II running so I don't have to reboot out of linux each time my Girlfriend comes round and demmands to kick my ass. :-) Well thanks in advance and I hope I can prove usefull. Rob PS anyone who want's to be nice enough to offer me a job DO IT NOW PLEASE I'M SKINT!

July 30, 2001

Wine Unreal and a strange old problem

by FT Rathore

Hi I have been using wine to play Unreal for a long time, but it would always crash in the start when I play as root or when I have my /dos filsystem mounted rw. It would always blow my mind, but I would fail to catch it. (been happenning for years too). I copied the whole Unreal tree to my ext2 filesystem and tried with different file permissions. I came to reallize that wine will allways crash if the file Unreal.log in Unreal/System is writeable. If I make that file read only, wine works flawlessly and I can do everything including save/load games. I tried to debug it, but the clues were very strange. There is only one message I see before the crash: err:seh:EXC_DefaultHandling Exception frame is not in stack limits => unable to dispatch exception. Besides that there is not much different between the good and the bad traces. I am attaching last 2000 lines of "-debugmsg +all" with this message. Someone might be able to get some sense from the trace. Anything else I sould do? FT

July 29, 2001