wine-devel August 2003

wine-devel@winehq.org

124 participants
293 discussions

GetLastError strangeness with FindClose
by Alex Pasadyn 21 Aug '03

21 Aug '03

Hi all, I observed a program that was bailing out with an absolutely baffling error message. I have traced it to its cause, but now I'm stuck. Basically, it was telling me that it had an error in FindNextFile of "success". I did a relay trace and found out that it was calling FindFirstFile, FindNextFile a bunch of times, FindClose, and then GetLastError. So, I put together a little test: #include <windows.h> #include <stdio.h> WIN32_FIND_DATA fd; HANDLE h; int main(int argc, char *argv[]) { h = FindFirstFile("*", &fd); if (h == INVALID_HANDLE_VALUE) { printf("Error finding first file: %d\n", GetLastError()); return 1; } printf("found file: %s\n", fd.cFileName); while (FindNextFile(h, &fd)) { printf("found file: %s\n", fd.cFileName); } FindClose(h); switch (GetLastError()) { case ERROR_NO_MORE_FILES: printf("all done!\n"); return 0; default: printf("Error finding next file: %d\n", GetLastError()); return 1; } return 1; } Now, on Windows, the output is: G:\testfnf>testfnf found file: . found file: .. found file: testfnf.cpp found file: testfnf.exe all done! And with Wine the output is: [ajp@toaster testfnf]$ ~/wine/wine testfnf.exe found file: . found file: .. found file: testfnf.cpp found file: testfnf.exe Error finding next file: 0 So, it looks like somewhere in FindClose Wine is resetting the last error. I started digging through there and the functions it calls but I was unable to find where it was getting reset. Can anyone shed some light on this? Is there any way to break on that value changing? Thanks, -ajp

6 10

Directx 8.1 sound bug
by puoti＠inwind.it 21 Aug '03

21 Aug '03

Anybody intrested may want to look at this http://bugs.winehq.com/show_bug.cgi?id=1670

1 0

Re: FAQ: When will Wine integrate an x86 CPU emulator?
by Mike Hearn 21 Aug '03

21 Aug '03

On Wed, 2003-08-20 at 21:42, Francois Gouget wrote: > + environment, Wine should only need minimal modifications. What > + performance you loose due to Wine running inside the emulator > + rather than natively, you gain in complexity inside of Wine. s/loose/lose/ - I'm not sure the second part of that sentance makes sense. What you lose in performance, you gain in complexity inside of wine? Shouldn't that be simplicity? Random tangent: at some point somebody needs to write an "msinterop" program that simply looks at the environment, the type of EXE file and then invokes: 1) Wine 2) Mono 3) Wine in QEMU 4) Wine and Mono in QEMU 5) Offers to download and install these programs if need be. Especially as we'll start seeing more and more programs that are partly unmanaged and partly managed (.net) code floating about, it's going to be harder to figure out what programs you need in order to make the exe run.

1 0

Re: stub for (undocumented) SHCreateLinks
by Dmitry Timoshkov 21 Aug '03

21 Aug '03

"Mike McCormack" <mike(a)codeweavers.com> wrote: > + 172 stdcall SHCreateLinks(long long long long long) > +HRESULT WINAPI SHCreateLinks( HWND hWnd, LPCSTR lpszDir, LPDATAOBJECT lpDataObject, > + UINT uFlags, LPITEMIDLIST *lppidlLinks) Then the spec entry should be 172 stdcall SHCreateLinks(long ptr ptr long ptr) -- Dmitry.

2 2

Re: patch 6
by Tom 21 Aug '03

21 Aug '03

puotiinwindit wrote: >this patch is licensed under the LGPL only (patch 5 is also LGPL only). >ChangeLog >Added Italian support to avifil32.dll >Fixed a typo in the english rc file in avifil32.dll > > > > > > Hi, umm.. the patches? :) Tom

1 0

Re: spec file syntax and automated generation
by Jon Griffiths 21 Aug '03

21 Aug '03

Hi Martin, > thanks for your info. I just wanted to forward my problem I posted on > wine-users - I do not know if wine-devel is the right place for this, so wine-devel is the place for any development issues, including problems with Winelib. Since someone may have the same problem(s) in the future, I'm also sending this to wine-devel (it serves as an issues archive for common problems). >I am currently having trouble building the DLLs of an application ported >from Win32 to Winelib - compiling, thanks to some hints from Dimi O. >Paun, now works fine, only(?) the final link __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

Re: PATCH - some build fixes for w32api headers
by Alexandre Julliard 21 Aug '03

21 Aug '03

Steven Edwards <steven_ed4153(a)yahoo.com> writes: > Changelog: Fixes for building with w32api headers on Mingw Why do you need to add stdarg.h everywhere? AFAICS it should be already included by the headers that require it. As a general note, it's a very good thing to test with other headers, but make sure that the problem is really on the Wine side before making changes. Being compatible with w32api is not a goal in itself for Wine, we have to be compatible with Microsoft; and if the Wine code works with the Microsoft headers but not with w32api then the bug is in w32api and should be fixed there. And in the case where the bug is really in Wine, this means there's an incompatibility in the Wine headers, since it builds fine with them and it shouldn't. So this means we have to fix the Wine headers too, not only the C files. -- Alexandre Julliard julliard(a)winehq.com

2 2

Re: Small spanish keyboard fix
by Dmitry Timoshkov 21 Aug '03

21 Aug '03

"José Manuel Ferrer Ortiz" <jmfo1982(a)yahoo.es> wrote: > Hi again, attached you have a patch to the spanish > keyboard that adds support to write the Euro sign > using <Alt-GR> + <E>, as seen in newer spanish > keyboards. XFree86 4.3.0 has no this, which however should not prevent the Euro sign to work. Moreover, XFree86 project tends to leave only two characters per keysym for all keyboard layouts, not to add new ones. -- Dmitry.

1 0

uClibc and wine
by Felipe Wilhelms Damasio 20 Aug '03

20 Aug '03

Hi, I couldn't compile wine using the latest (0.9.20) version of uClibc. I installed the devel stuff and am using the /usr/i386-uClibc/gcc on my path, and then I get: gcc -c -I. -I. -I../include -I../include -g -O2 -Wall -mpreferred-stack-boundary=2 -gstabs+ -fPIC -D__WINESRC__ -DDLLDIR="\"/mnt/usr/lib/wine\"" -D_REENTRANT -o port.o port.c port.c:597: warning: type defaults to `int' in declaration of `wchar_t' port.c:597: syntax error before '*' token port.c: In function `wine_rewrite_s4tos2': port.c:601: `str4' undeclared (first use in this function) port.c:601: (Each undeclared identifier is reported only once port.c:601: for each function it appears in.) make[1]: *** [port.o] Error 1 make[1]: Leaving directory `/home/felipewd/elipse/cvs/wine-20030115/library' make: *** [library] Error 2 If I change my path to use the default gcc location, it compiles fine. Does anybody have any ideas? Thanks in advance, Felipe

2 1

Re: winegcc
by puoti＠inwind.it 20 Aug '03

20 Aug '03

I'm trying to compile the bidi test progam posted on this list by Shachar Shemesh, you can find his post and his program here: http://www.winehq.org/hypermail/wine-devel/2003/08/0175.html this mail also got to wine-users, sorry about that.

2 1

← Newer
1
...
12
13
14
15
16
17
18
...
30
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 August 2003