wine-devel November 2003

wine-devel@winehq.org

121 participants
276 discussions

More DLL spec forwarding issues
by Shachar Shemesh 07 Nov '03

07 Nov '03

Hi, I got no reponse for the previous issue I posted (where placing forwards in a spec file did not perform as expected). I have tried to create actual functions that perform the forwards. This works great when I use my own program. However, whem I try to use another program, it tries to call "GetProcAddress". Unfortunetly, there is no way to reimplement GetProcAddress in Wine, as the .spec.c file generated needs that function! This is a very problematic thing for me. I tried forwarding GetProcAddress to GetProcAddress_unicows, but that did not help either. I get linker error (function redefined). Please, can anyone help? Shachar -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/

2 3

X11 resize event compression
by Mike Hearn 07 Nov '03

07 Nov '03

Hi, When I resize windows using opaque resizing, the contents of the window take several seconds to "catch up" with the borders. It feels like X resize event compression isn't being done, so we rerender the window for every single motion of the border. Does anybody know if my hunch is correct or not ? I know modern toolkits are supposed to do this, but does Wine? thanks -mike

1 0

Help with forwarding .spec and DLL overrides for a new DLL
by Shachar Shemesh 07 Nov '03

07 Nov '03

Hi list, I'm having trouble with my unicows.dll implementation. I can trace this problem down to forwarding entries not working, but I can't understand why. I am attaching the diffs for my current unicows patch (not working though it is). I'm trying to run it with a program I wrote. This program is the plain "Hello world" Visual Studio 6 produces when you ask for a Win32 application, with two changes. I changed the link order according to the instructions for using MSLU (http://msdn.microsoft.com/msdnmag/issues/01/10/MSLU/default.aspx), so that the app will use unicows.dll on win98. The second is that I modified the LoadString and DrawText to specifically call LoadStringW and DrawTextW. The application is, otherwise, an ANSI application (only two Unicode functions called). The resulting app works ok on Windows 2000 and on Windows 98 (the later only when unicows.dll is in the same directory as the application - as it should). When trying to run the app on Wine with os=nt4, or with os=win98 and the native unicows.dll in the same directory as the app, everything works. So far, so good. Now comes the part things stop to work. First - I couldn't get my DLL overrides to take effect. I tried adding "UNICOWS.DLL"=b, but it wouldn't load my winelib dll over the standard one. I eventually created a symbolic link from a file called "unicows.dll" in the apps' dir to my unicows.dll.so file. That caused my dll to load. The second had to do with the forwarding call. I generated (using a small perl script) the spec file for the DLL. It forwards all Unicode calls to the relevant Unicode call. Strangely, when the entries for LoadStringW and DrawTextW were pointing to the corresponding calls in user32, the program wouldn't run correctly. When I replaced them with explicit loading of user32.dll and GetProcAddress, everything works (that's the way it's currently in the diff). This suggests, to me, that the spec file is incorrectly set up. Can anyone please point me to my mistake? Shachar -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/

2 4

Re: buildmetrics error
by Ivan Leo Murray-Smith 07 Nov '03

07 Nov '03

Sorry wrong list.

1 0

Re: buildmetrics error
by Ivan Leo Murray-Smith 07 Nov '03

07 Nov '03

>20030115 This is a very old build of wine, please try wine-20031016

1 0

Re: Question: Is secdrv.sys a "Protection Mechanisim"
by Ivan Leo Murray-Smith 07 Nov '03

07 Nov '03

>an Access Control Measure is something that prevents unauthorized access >to a Copyrighted work If wine just gives interoperability in between the game and a newrly created computer program (Linux), there isn't any violation. If this was the case m$ could sue openoffice for "cracking" the proprietary office document formats.

1 0

Re: [wineinstall] make nice value
by Ivan Leo Murray-Smith 07 Nov '03

07 Nov '03

It was on the italian news, it's an optical processor, so it may or may not be x86 compatible, I dont know the name of the company but I can try and find out. - - - - - > Ivan Leo Murray-Smith wrote: > > >This depends, it can go from 15-20 minutes to over 4 hours. > >A company in Israel has built a 8000 Ghz (Not a typo, it's Ghz) processor, that > >may take it down to a few seconds. > > > > > I think you just pointed to the local technology press being negligent > to a degree never before seen. This is the first I have heared about > such a thing (these things usually make it all the way into the > mainstream press). > > Do you know the company's name? > > Shachar > > -- > Shachar Shemesh > Open Source integration consultant > Home page & resume - http://www.shemesh.biz/ > > >

2 1

Re: [wineinstall] make nice value
by Ivan Leo Murray-Smith 07 Nov '03

07 Nov '03

This depends, it can go from 15-20 minutes to over 4 hours. A company in Israel has built a 8000 Ghz (Not a typo, it's Ghz) processor, that may take it down to a few seconds.

3 2

Re: tools/winapi/msvcmaker trouble
by Steven Edwards 07 Nov '03

07 Nov '03

I have been having trouble with it but on Windows. I would really like to have it work on Windows as I dont always have access to a running linux system. Cygwin, Active Perl and Msys perl all give this error: Administrator@REACTOS-LAPTOP /e/source/winehq/wine $ tools/winapi/msvcmaker Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmak er line 52. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmak er line 116. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmak er line 440. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmak er line 1031. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmak er line 1091. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmak er line 1141. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmak er line 1180. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmak er line 1217. Global symbol "$wine_dir" requires explicit package name at tools/winapi/msvcmak er line 1234. Execution of tools/winapi/msvcmaker aborted due to compilation errors. Administrator@REACTOS-LAPTOP /e/source/winehq/wine __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree

1 0

wine-20031016/include/msvcrt/limits.h
by Ralf Juengling 07 Nov '03

07 Nov '03

To get rid of a gcc compiler warning... (cf. http://gcc.gnu.org/ml/gcc-bugs/2001-10/msg00764.html) --- wine-20031016/include/msvcrt/limits.h 2003-09-01 17:58:21.000000000 -0700 +++ /local/include/wine/msvcrt/limits.h 2003-11-06 17:58:59.000000000 -0800 @@ -2,7 +2,7 @@ #define __WINE_LIMITS_H #define INT_MAX 2147483647 -#define INT_MIN (-2147483648) +#define INT_MIN (-INT_MAX-1) #define SHRT_MAX 32767 #define SHRT_MIN (-32768) -- Ralf Juengling <juenglin(a)cse.ogi.edu>

1 0

← Newer
1
...
20
21
22
23
24
25
26
27
28
Older →

Jump to page:

2025

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 November 2003