wine-devel

wine-devel@winehq.org

4 participants
84402 discussions

File names and Wine.
by Insyde 01 Apr '02

01 Apr '02

Hi, I was looking at th wine source and I couldn't find any support to long file names under wine (yet). I was reading the DOSFS part and there is a lot of code that handles 8.3 file names, but wine support long file names. Can anyone show me where is it? or long names depend on Linux? thanks, Ricardo.

1 0

error: no implementation for WININET.dll.102(InternetGetConnectedState)
by Jason M Bell 01 Apr '02

01 Apr '02

hey everybody, I'm trying to debug a windows application - the Paradise Poker client program. I keep getting an error when it runs: -------------- err:win32:PE_fixup_imports No implementation for WININET.dll.102(InternetGetConnectedState) imported from C:\Program Files\ParadisePoker\client.exe, setting to 0xdeadbeef wine: Unhandled exception, starting debugger... err:seh:start_debugger Couldn't start debugger ("/usr/bin/winedbg 134662856 112") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger -------------- The source in dlls/wininet/internet.c clearly shows a (simple) implementation for InternetGetConnectedState, but Wine isn't importing it for some reason. I've turned on other debug traces, but haven't gotten any other useful information. What are some other ways of attacking the problem? I'm pretty new at Wine development - any tips you have would be greatly appreciated. thanks in advance, Jason

3 4

wineconf 2002 summary
by Andreas Mohr 01 Apr '02

01 Apr '02

Hi all, I just added a link to my final wineconf 2002 summary page at http://home.arcor.de/andi.mohr/wine/wineconf2002/ to the WineHQ News. If anyone else has anything to contribute, then feel free to tell me NOW :) BTW, Michael, what about your photos ? Are they supposed to get published somewhere ? Thanks for listening ! -- Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany Tel. +49 7159 800604 http://home.arcor.de/andi.mohr/

2 1

make test leaves 2 wine processes running
by Sylvain Petreolle 01 Apr '02

01 Apr '02

Hi, Running make test with a desktop window leaves ok but 2 processes are still running and the desktop windows not closed. They cannot be closed when I use the cross or the close command, i must kill them. (don't have to use -9 parameter) Running processes are : /home/wine/wine tests/vartest.c /home/wine/wine tests/sysparams.c (wineserver is here) I tried to winedbg them, but got error when I typed attach : error 5 (ERROR_ACCESS_DENIED). ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

3 5

problems with the alt button and window switching
by Rizsanyi Zsolt 31 Mar '02

31 Mar '02

Hi! If I change the window with keyboard (eg with ALT-TAB), then when I switch back to the wine window wine still thinks that the ALT button is depressed. I happens, because the key event of pressing ALT arrives to the wine window before the switch. And I see in the console (with --debugmsg +key) the next lines: trace:key:X11DRV_KeyEvent state = 10 trace:key:X11DRV_KeyEvent KeyPress : keysym=FFE9 (Alt_L), ascii chars=0 / 0 / '' trace:key:X11DRV_KeyEvent keycode 0x40 converted to vkey 0x12 trace:key:X11DRV_KeyEvent bScan = 0x38. trace:key:queue_kbd_event wParam=0012, lParam=20380001, InputKeyState=81 trace:key:TranslateMessage (WM_SYSKEYDOWN, 0012, 20380001) trace:key:TranslateMessage Translating key VK_MENU (0012), scancode 38 trace:key:X11DRV_ToUnicode (0012, 2038) : faked state = 10 trace:key:X11DRV_ToUnicode ToUnicode about to return 0 with char bbc6 trace:key:queue_kbd_event wParam=0012, lParam=c0000001, InputKeyState=1 That is the key state has been changed. And when I return to the wine window (by keyboard or mouse) it acts like if the ALT button were depressed. The solution is that the key states should be reset when the wine gets back the focus or loses the focus. That is more exactly in windows/winpos.c in the function WINPOS_SetActiveWindow when the hWnd is NULL ! That is the case when switching from a wine window to an non-wine window. So I have found the place :), just I dont know whats the preferred way to reset all the key states to not pressed. I have added the next few lines: --- oldwinpos.c Fri Mar 29 16:54:59 2002 +++ winpos.c Fri Mar 29 16:55:08 2002 @@ -1217,6 +1217,12 @@ if ((wndPtr = WIN_FindWndPtr(hWnd))) hWnd = wndPtr->hwndSelf; /* make it a full handle */ + /* reset key states when switching to a non-wine window */ + if (hWnd == 0) + { + InputKeyStateTable[VK_MENU] &= ~0x80; + goto CLEANUP_END; + } + /* paranoid checks */ if( hWnd == GetDesktopWindow() || (bRet = (hWnd == hwndActive)) ) goto CLEANUP_END; And now my problem is fixed. But I have experienced the same problem with the Control button (altough it is harder to reproduce). So maybe all the key states should be reset. So I would like to have this patch or something similar in wine. Best regards Zsolt Rizsanyi

2 1

WineLib newbie question
by Boris Buegling 31 Mar '02

31 Mar '02

Hi all. I'm wondering how difficult it is to port an application to Linux with WineLib. There are quite a few N64 emulators with source code on Windoze and I want to port one of them to Linux, because there is no decent native emulator, First, is it possible that things which don't work well with Wine, work when they are ported using WineLib ? Second, how much work is involved ? Regards, -- Boris Buegling <boris(a)icculus.org> "Sleep less - live longer." - "Ok good, 1 down... Now all I need is beer, video games and hacking to be linked to living longer and I'm set." "If it stinks, it's chemistry. If it moves, it's biology. If it does not work, it's computer science."

1 0

DIB engine
by Francois Gouget 31 Mar '02

31 Mar '02

The DIB engine was discussed quite a lot at WineConf. I am now trying to summarize these discussions to update bug 421 - Implement a DIB engine. http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=421 Is the following accurate, complete, etc? Comments? Other ideas? Any volunteers? This was discussed quite a bit at WineConf. Ideas that were floated around are: 1. Have X export the required API --------------------------------- XFree86 4 has all the needed code, for all bit depths and layouts we care about. We could try to have the X guys export this in the form of an API ala Xft. Wine could then link with this library to implement the DIB engine (or dlopen that library). * Is the needed API already available? * If not, are the XFree86 guys willing to export it? * Almost everyone is using XFree86, but what about people who don't (embedded devices, Wine on Solaris...). We need a fallback. * We won't have to maintain that code which is a good thing, although it is not supposed to change much once written. * Will we be able to do all that we need with that API? Probably yes since it can be expected to match the X API quite closely and we are abel to use the X API. 2. Copy the relevant X code into Wine ------------------------------------- Since X has all the code and that code is under the X11 license we could copy it all into Wine. * This means we will have to maintain the code ourselves, although it is not supposed to change much once written. 3. Copy the relevant code from MicroWindows/NanoGUI to Wine ----------------------------------------------------------- MicroWindows/NanoGUI also has code that could help us bootstrap our DIB engine. We probably don't want Wine to depend on these projects but we could copy their code into Wine. * Are the licenses compatible? * Do they support all the bit depths and layouts we care about? * This means we will have to maintain the code ourselves, although it is not supposed to change much once written. 4. Copy the relevant code from GGI to Wine ------------------------------------------ GGI also has similar code. Again we probably don't want to introduce a dependency on GGI so the same questions apply: * Are the licenses compatible? * Do they support all the bit depths and layouts we care about? * This means we will have to maintain the code ourselves, although it is not supposed to change much once written. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ "Utilisateur" (nom commun) : Mot utilisé par les informaticiens en lieu et place d'"idiot".

4 4

problem creating/finding files
by Insyde 30 Mar '02

30 Mar '02

Hi, I'm getting this error running a system under WINE: 0806faa8:Call kernel32.CreateFileA(405b63ec "C:\\WIN\\IY032097.DAT",80000000,00000003,00000000,00000003,08000001,0000000 0) ret=6002912b 0806faa8:trace:file:CreateFileA C:\WIN\IY032097.DAT GENERIC_READ FILE_SHARE_READ FILE_SHARE_WRITE OPEN_EXISTING 0806faa8:trace:dosfs:DOSFS_GetFullName C:\WIN\IY032097.DAT (last=1) 0806faa8:trace:string:lstrcpynA (0x405b5a4c, "/mnt/c", 1024) 0806faa8:trace:dosfs:DOSFS_FindUnixName /mnt/c,WIN\IY032097.DAT 0806faa8:trace:heap:RtlAllocateHeap (40360000,00000002,00010bfc): returning 403a9e6c 0806faa8:trace:heap:RtlAllocateHeap (40360000,00000002,00000018): returning 403a7d10 0806faa8:trace:dosfs:DOSFS_FindUnixName (/mnt/c,WIN\IY032097.DAT) -> win (WIN) 0806faa8:trace:heap:RtlFreeHeap (40360000,00000002,403a7d10): returning TRUE 0806faa8:trace:heap:RtlFreeHeap (40360000,00000002,403a9e6c): returning TRUE 0806faa8:trace:dosfs:DOSFS_FindUnixName /mnt/c/win,IY032097.DAT 0806faa8:trace:heap:RtlAllocateHeap (40360000,00000002,00010bfc): returning 403a9e6c 0806faa8:trace:heap:RtlAllocateHeap (40360000,00000002,00000018): returning 403a7d10 0806faa8:warn:dosfs:DOSFS_FindUnixName 'IY032097.DAT' not found in '/mnt/c/win' 0806faa8:trace:heap:RtlFreeHeap (40360000,00000002,403a7d10): returning TRUE 0806faa8:trace:heap:RtlFreeHeap (40360000,00000002,403a9e6c): returning TRUE 0806faa8:warn:file:CreateFileA Unable to get full filename from 'C:\WIN\IY032097.DAT' (GLE 2) ......... 08079370:RET MFRTS32.1199: _mFfindp() retval = 409c5e90 ret=0042b3b7 08079370:CALL MFRTS32.1425: mF_fh_set_fe_stat(00000000) ret=0042b3c8 08079370:RET MFRTS32.1425: mF_fh_set_fe_stat() retval = 00000000 ret=0042b3c8 08079370:RET MFRTS32.1202: _mFg2star_fast() retval = 00000000 ret=0042889a 08079370:RET MFRTS32.1400: ixfile() retval = 00000000 ret=60025e45 08079370:RET MFRTS32.145: EXTFH() retval = 00000000 ret=0044095a 08079370:Call user32.MessageBoxA(00000000,004472de "External Path string <UPCW56-DEV-DATA-DIR> not found. File IYF029. "...,004471c8 "IYP139 ",00002010) ret=00404c01 08079370:warn:dialog:MessageBoxA Messagebox 08079370:trace:resource:RES_FindResource2 (4067a000, 00000005, 40718554"MSGBOX", 0000, A, PE) 08079370:trace:heap:RtlAllocateHeap (40360000,00000002,00000018): returning 403af734 08079370:trace:heap:RtlFreeHeap (40360000,00000002,403af734): returning TRUE 08079370:trace:resource:RES_LoadResource (4067a000, 407234f8, PE) ......... Seems like the file isn't being created. (Uwe Bonnes helped me with this). But we disagree what part of WINE (or outside WINE) is wrong. The first part of the log shows a CreateFileA that is unable to create a file. This API works fine when the file is in the same dir as the application (had tested it). The second part of the log shows the last screen I get after start the program (MessageBox API). MFRTS32 is a .dll the program calls. We thougth of there too. But this program works under Windows. Everything is in the path. Both wine.conf and Linux. I could reproduce the error in Win2k this way: Created a set of programs (L1, L2 and L3) that will run one after one with conditions. If the field in L1 is fulfilled then we jump directly to L3. Else We fulfill the field in L2 and then jump to L3. In details: L1 would creates a file with a name if the filed is fulfilled an L3 NEEDS to know that name. If we had to run L2 then the file will be with another name and L3 will get data from that file. But the file ins't created in neither of the cases. So a screen shows up: "External path string <G-PATH> not found. File FILE-LINUX." That message is the same I get under WINE: "External path string <UPCW56-DEV-DATA-DIR> not found. File IYF029." Refers to a file (IYF029), that exists (located in the ./data dir) but was not filled with data it need to work, or incorretly filled. Both G-PATH and UPCW56-DEV-DATA-DIR are variables of a file that has a number of them inside. As here we use APIs I'll list 2 of them that are used within the function and their definiton, took from MSDN: CreateProcess CreateProcess( LPCWSTR lpszImageName, LPCWSTR lpszCmdLine, LPSECURITY_ATTRIBUTES lpsaProcess, LPSECURITY_ATTRIBUTES lpsaThread, BOOL fInheritHandles, DWORD fdwCreate, LPVOID lpvEnvironment, LPWSTR lpszCurDir, LPSTARTUPINFOW lpsiStartInfo, LPPROCESS_INFORMATION lppiProcInfo); ........ StartupInfo.dwFillAttribute dwFillAttribute Ignored unless dwFlags specifies STARTF_USEFILLATTRIBUTE. Specifies the initial text and background colors if a new console window is created in a console application. These values are ignored in GUI applications. This value can be any combination of the following values: FOREGROUND_BLUE, FOREGROUND_GREEN, FOREGROUND_RED, FOREGROUND_INTENSITY, BACKGROUND_BLUE, BACKGROUND_GREEN, BACKGROUND_RED, and BACKGROUND_INTENSITY. For example, the following combination of values produces red text on a white background: FOREGROUND_RED| BACKGROUND_RED| BACKGROUND_GREEN| BACKGROUND_BLUE OBS.: We do NOT use this to send this kind of attributes. We DO send more data as we saw that it handles well. We also DO use this in gui applications. typedef struct _STARTUPINFO { DWORD cb; LPTSTR lpReserved; LPTSTR lpDesktop; LPTSTR lpTitle; DWORD dwX; DWORD dwY; DWORD dwXSize; DWORD dwYSize; DWORD dwXCountChars; DWORD dwYCountChars; DWORD dwFillAttribute; DWORD dwFlags; WORD wShowWindow; WORD cbReserved2; LPBYTE lpReserved2; HANDLE hStdInput; HANDLE hStdOutput; HANDLE hStdError; } STARTUPINFO, *LPSTARTUPINFO; ............... CreateFile HANDLE CreateFile( LPCTSTR lpFileName, // file name DWORD dwDesiredAccess, // access mode DWORD dwShareMode, // share mode LPSECURITY_ATTRIBUTES lpSecurityAttributes, // SD DWORD dwCreationDisposition, // how to create DWORD dwFlagsAndAttributes, // file attributes HANDLE hTemplateFile // handle to template file ); .................. Any thoughs? Thanks, Ricardo.

2 1

Improving the regression testing infrastructure
by Geoffrey Hausheer 30 Mar '02

30 Mar '02

I know regression testing isn't as interesting as doing real development, and so I appologize with once again spamming the list with regression questions... As I've been writing tests (only for the last week or so), I realized that as we get a lot more tests, it will be very difficult to keep track of what is being tested, and what is not. I'd like to propose a list of which functions for each DLL are being tested, which file tests it, as well as any comments on the current tests. Currently, there is no great way to do this. I may use several functions in a directed test which I am not actually testing (for instance I've found it necessary to retrieve the page-size using GetSystemInfo, but my tests have nothing to do with this function, and so writing a directed test for it is a task for another day). Thus just grepping for which functions are used in a test is not sufficient. Also, I have found that some functions, or even specific task functions are very difficult to test, and so I've been leaving these out so that perhaps people ore skilled than myself could take a crack at them late (A good example is testing inheritance with CreateThread. It is a task that is beyond my capabilities at the moment, at least until I can find a good way to test CreateProcess...this would be much easier if Windows had something equivalent to 'fork'). In any case, I've tried to be thorough about commenting what I do and don't test, but it would be a lot more convenient if this information was more easily parsed than trying to find my comments intersperesed through the tests. So does anyone thing that creating a easily parsable list with the state of the current tests is this a reasonable thing to do, and would creating a simple file in each /tests directory with the information be good enough? If so, I can add one to my next test, and update it with what I've done so far. In general, while Francois' presentation is a good place to get started, I think it'd be a lot easier if there was a document off of winehq with recommendations on how to build, test, and document tests. Lowering the difficulty threshold, is more likely to draw more people to do so. Thanks, .Geoff

4 11

Re: Wine List Control compatibility
by Tony Lambregts 30 Mar '02

30 Mar '02

Peter Quax wrote: >Hello, > >>>Some things will break if you start trying to use a bunch of native >>>DLLs. And especially trying to use the native comctrl is likely to break >>>things. >>> >>>That said, I downloaded and tried out the program. To get it to run, I >>>used these native DLLs: >>> > >>>With that, the listview appears to be working for me just fine, assuming >>>you are talking about the one with the labels Oefening, Titel, and Item. >>>This is with current CVS. >>> >>I get about the same thing with the same problems (except I havent >>crashed) but I have some time.It would be much easier if there is an >>english version of this program.I don't have a soundcard.(maybe thats >>why I havnt crashed yet). I probably could get one. Does anyone want to >>recommend a cheep one that works well with linux? >> > >Both of you, thanks very much for your help. > >First of all I forgot to mention that the use of sound is not an issue (we >don't use that at our school), so that is not a problem whatsoever. > >I tried using the dll configuration as given and indeed it shows the list >control (just as it did before), but as I mentioned the image lists are >incorrect. To demonstrate this, I've taken a couple of screen shots to give >you an idea of what it should look like : > >http://alpha.luc.ac.be/~lucp1313/juniorwin.jpg : this is the windows version >that shows the correct icons in the list control (at the bottom) > >http://alpha.luc.ac.be/~lucp1313/juniorwine.jpg : this is the wine version >which demonstrates the incorrect behaviour of the icons > >You can clearly see that there is a difference. Now, when I doubleclick for >example 4-1 in the 'oefening' column to start this exercise, the window that >comes up doesn't show all of the text. A second anomaly is that from time to >time, the cursor will disappear. This is shown in the next 2 screenshots : > >http://alpha.luc.ac.be/~lucp1313/juniorwin2.jpg : this is the windows >version that shows the correct text > >http://alpha.luc.ac.be/~lucp1313/juniorwine2.jpg : this is the wine version >which demonstrate the lack of text in the upper left corner > >I hope this made my problems a bit more clear ? Also, I'm afraid that there >isn't an english version of this package available. I tried contacting the >authors but they don't seem to respond to any of my emails. > >Again, thanks for all your help > >Regards, >Peter Quax. > It looks like its not translating the color palet correctly. What color depth are you running at? My guess is that it is 16. If this is correct then try increasing it. It may be that the text is just not showing up because of this problem. I have CC:ed the Wine development list in order that the real wine gurus can have a look at this. How long do you have before you have to subject the little children to the "Windows Solution". Tony Lambregts

1 0

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