wine-devel

wine-devel@winehq.org

2 participants
84469 discussions

RE: Running United Devices Agent
by Roger Olson 04 Jul '04

04 Jul '04

Hi All, Since this is my first attempt to submit a patch coupled with the fact that I am sooo new to win32 C, I thought I would offer my proposal before the wine developers. This does 3 things for me: 1) See if I am in left or the right field :) and if 'half step' patches to full implemetation are ok. 2) Check to see if my patch submission procedure/format is correct (did I follow directions correctly?). 3) Best of all, implementation of this patch nearly made my UD Agent function 100% without even adding any code. Sending via Mozilla e-mail client out of RH9 hopefully set up properly. Feedback more than welcome! Thanks, Roger ********** Proposed Patch ************ Change CreateRemoteThread() from an unhandled exception to a fixme. Index: dlls/kernel/kernel32.spec =================================================================== RCS file: /home/wine/wine/dlls/kernel/kernel32.spec,v retrieving revision 1.136 diff -u -u -r1.136 kernel32.spec --- dlls/kernel/kernel32.spec 15 Jun 2004 00:52:03 -0000 1.136 +++ dlls/kernel/kernel32.spec 4 Jul 2004 20:23:01 -0000 @@ -221,7 +221,7 @@ @ stdcall CreatePipe(ptr ptr ptr long) @ stdcall CreateProcessA(str str ptr ptr long long ptr str ptr ptr) @ stdcall CreateProcessW(wstr wstr ptr ptr long long ptr wstr ptr ptr) -@ stub CreateRemoteThread +@ stdcall CreateRemoteThread(long ptr long ptr long long ptr) @ stdcall CreateSemaphoreA(ptr long long str) @ stdcall CreateSemaphoreW(ptr long long wstr) @ stdcall CreateSocketHandle() Index: dlls/kernel/thread.c =================================================================== RCS file: /home/wine/wine/dlls/kernel/thread.c,v retrieving revision 1.18 diff -u -u -r1.18 thread.c --- dlls/kernel/thread.c 14 Jun 2004 17:04:35 -0000 1.18 +++ dlls/kernel/thread.c 4 Jul 2004 20:23:01 -0000 @@ -157,6 +157,32 @@ } +/*************************************************************************** + * CreateRemoteThread (KERNEL32.@) + * + * Creates a thread that runs in the address space of another process + * + * PARAMS + * + * RETURNS + * Success: Handle to the new thread. + * Failure: NULL. Use GetLastError() to find the error cause. + * + * BUGS + * Unimplemented + */ +HANDLE WINAPI CreateRemoteThread( HANDLE hProcess, SECURITY_ATTRIBUTES *sa, SIZE_T stack, + LPTHREAD_START_ROUTINE start, LPVOID param, + DWORD flags, LPDWORD id ) +{ + /* make this a fixme */ + FIXME("(): stub, Write Me.\n"); + + SetLastError(ERROR_CALL_NOT_IMPLEMENTED); + return NULL; +} + + /*********************************************************************** * OpenThread [KERNEL32.@] Retrieves a handle to a thread from its thread id */

1 0

Building Wine on a 64 Bit Machine
by Gamel, Matthew R 04 Jul '04

04 Jul '04

Hello, I am currently attempting to build Wine-20040615 on an AMD Athlon 64 system. When I attempt to actually build the software, I am told that I need to implement interlocked functions for my CPU - I am not sure how to implement them myself but am wondering if anyone else has done so. Any help or advice would be appreciated. Thanks! matt

3 2

Error building CVS
by wine-devel＠kievinfo.com 04 Jul '04

04 Jul '04

preloader.o(.text+0x219): In function `wld_printf': /usr/local/src/wine/loader/preloader.c:338: undefined reference to `strlen' preloader.o(.text+0x260): In function `fatal_error': /usr/local/src/wine/loader/preloader.c:349: undefined reference to `strlen' collect2: ld returned 1 exit status make[1]: *** [wine-preloader] Error 1 make: *** [loader] Error 2 Here is offending patch: http://cvs.winehq.org/patch.py?id=12698 This part: Index: wine/loader/Makefile.in diff -u wine/loader/Makefile.in:1.15 wine/loader/Makefile.in:1.16 --- wine/loader/Makefile.in:1.15 Sun Jul 4 16:02:15 2004 +++ wine/loader/Makefile.in Sun Jul 4 16:02:15 2004 @@ -28,7 +28,7 @@ $(CC) -o $@ glibc.o $(LIBWINE) $(LIBPORT) $(LIBPTHREAD) $(EXTRALIBS) $(LDFLAGS) wine-preloader: preloader.o Makefile.in - $(CC) -o $@ -static -nostartfiles -Wl,-Ttext=0x78000000 preloader.o $(LIBPORT) $(LDFLAGS) + $(CC) -o $@ -static -nostartfiles -nodefaultlibs -Wl,-Ttext=0x78000000 preloader.o $(LIBPORT) $(LDFLAGS) wine-kthread: $(KTHREAD_OBJS) Makefile.in $(CC) -o $@ $(LDEXECFLAGS) $(KTHREAD_OBJS) $(LIBWINE) $(LIBPORT) $(EXTRALIBS) $(LDFLAGS) Any ideas? -- Best regards, Vitaliy

1 0

Wierd wine threading crash
by Andrei Barbu 04 Jul '04

04 Jul '04

I'm trying to get Alpha Centauri working on wine. I've fixed some bugs, but I've hit a wall with this one: 0011:trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 addr=0x4fb13f 0011:trace:seh:EXC_RtlRaiseException info[0]=00000000 0011:trace:seh:EXC_RtlRaiseException info[1]=00a63834 0011:trace:seh:EXC_RtlRaiseException eax=000362a2 ebx=00000001 ecx=00000001 edx=00000000 esi=00000000 edi=00000320 0011:trace:seh:EXC_RtlRaiseException ebp=4073a920 esp=40738a98 cs=0073 ds=007b es=007b fs=0033 gs=0007 flags=00010246 First chance exception: page fault on read access to 0x00a63834 in 32-bit code (0x004fb13f). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:0007 EIP:004fb13f ESP:40738a98 EBP:4073a920 EFLAGS:00010246( - 00 -RIZP1) EAX:000362a2 EBX:00000001 ECX:00000001 EDX:00000000 ESI:00000000 EDI:00000320 Stack dump: 0x00000000: 00000000 00000000 00000000 00000000 0x00000010: 00000000 00000000 00000000 00000000 0x00000020: 00000000 00000000 00000000 00000000 0x00000030: 00000000 00000000 00000000 00000000 0x00000040: 00000000 00000000 00000000 00000000 0x00000050: 00000000 00000000 00000000 00000000 0x00000060: Backtrace: =>1 0x004fb13f (0x4073a920) 2 0x004e5cd0 (0x4073a94c) 3 0x004ef883 (0x4073fda4) 4 0x004f5ae1 (0x4073fdc0) 5 0x005206d8 (0x4073fde0) 6 0x0052091f (0x4073fe00) 7 0x00520d07 (0x4073fe1c) 8 0x00522a1b (0x4073fe90) 9 0x0064dd06 (0x4073ff20) 10 0x4057f352 start_process+0xf2(arg=0x0) [process.c:980] in kernel32 (0x4073fff4) 11 0x40044091 wine_switch_to_stack+0x11 in libwine.so.1 (0x00000000) 0x004fb13f: movb 0x98adac(,%eax,4),%dl The error happens regularly every time the 1st turn is ended (it's turn based, which makes things simpler in this case) Any ideas? By the way, the above only happens once in a while, it's more common for the stack to be full of ??s or winedbg failing to get any backtraces.

2 1

16-bit application fails due to regression in NE-module handling
by Saulius Krasuckas 03 Jul '04

03 Jul '04

I've entered new bug #2332 [1] recently, where I've described my problem. I think the application was compiled with some BC compiler for win16 platforms. 32 here at "last error" means some sharing violation, I hope: [s2@katleriai wine]$ cat include/winerror.h | grep ' \+32$' #define ERROR_SHARING_VIOLATION 32 The quick analysis of the patch [1] revealed me two points: + handle = FILE_CreateFile( full_name.long_name, GENERIC_READ|GENERIC_WRITE, 0, + NULL, OPEN_EXISTING, 0, 0, TRUE, + GetDriveTypeW( full_name.short_name ) ); ... /* Open file */ - if ((hFile = OpenFile16( name, &ofs, OF_READ )) == HFILE_ERROR16) + if ((hFile = OpenFile16( name, &ofs, OF_READ|OF_SHARE_DENY_WRITE )) == HFILE_ERROR16) return (HMODULE16)2; /* File not found */ which confused me a bit. By doing some wild guess I tried to revert last mentioned change. Heh, reversing this line really lets the app to succeed. My discovery may imply I should write some additional wine-tests, but I'd like to ask in such case: do I need the test (for example of OpenFile16() function) to be 16-bit style? I mean doing some NE-module-over-ELF and compiling 16-bit app within Wine(lib). If yes, then how it should be done? If no, then what should I do else to make Wine happy or even to submit the correct patch? Yes, I was a bit too lazy to RSFM. TIA.

1 1

Pango for BiDi
by Mike Hearn 03 Jul '04

03 Jul '04

Hi Shachar, I am reading your interview and a few words jumped out at me, mostly "BiDi", "shaping" and "unicode" - very vague I know, but if I understand correctly Pango is a library with advanced support for shaping and laying out all kinds of different scripts. Only stopper I can think of would be that it uses UTF-8 not UTF-16. Have you looked at this, or am I talking smack? thanks -mike

2 5

Assertion in dlls/ntdll/loader.c
by Jon Griffiths 03 Jul '04

03 Jul '04

Hi, I'm experimenting with native vs builtin comctl32 for an app and whenever I set this dll to native I hit this assert in init_system_dir(): assert( mod->Flags & LDR_WINE_INTERNAL ); This happens on a 2.6 and a 2.4 system. I suspect its not related to comctl32 per-se, but merely loading a native dll at all (since this is the only native dll I'm using). Using all builtins does not hit this assert. I don't really grok what this function is doing, but commenting it out allows the app the start up with no ill efects. Any ideas? Cheers, Jon ===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live jon_p_griffiths(a)yahoo.com __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail

1 0

Re: Pango for BiDi
by Shachar Shemesh 03 Jul '04

03 Jul '04

Jonathan Wilson wrote: >> Maybe we can get our supplied packages to be BiDi enabled, but so >> long as we use ICU, and ICU has this horrible linking policy, we >> can't really > > What linking policy? > > I checked the IBM ICU website (http://oss.software.ibm.com/icu/ and > specifically > http://oss.software.ibm.com/cvs/icu/~checkout~/icu/license.html and it > appears to be under the X11 licence which is GPL compatible. > > IANAL but unless there is something I missed, I see no reason why > debian couldnt include ICU (and hence WINE with ICU support) in the > debian package system. > The problem is not a legal one. The problem is a technological one. ICU is mangling the library's version into the symbols, making it impossible to dynamically link the library. As a result, most distros don't carry ICU as a package. Shachar

1 0

Re: [Mono-winforms-list] Fw: [Mono-list] System.Windows.Forms plans.
by Peter Dennis Bartok 03 Jul '04

03 Jul '04

May I remind you that this thread was started by you, asking why we are abandoning Wine, not by me complaining about Wine. All I did was give you the reasons why we are no longer using Wine. You may not like them, you may disagree with them, but the decision has been made. And there is really nothing to be gained in nitpicking or pointing fingers. I don't understand the comment about managed Quake, but we don't have to create managed Wine. We simply have to create the SWF controls in managed code and the underlying SWF framework. Wine doesn't have anything to do with the framework, anyway, so it's down to the controls. And even by using the Wine controls we still would have to either modify Wine to support the additional functionality required by SWF, or subclass them, basically recreating the drawing code for those controls and just using the WndProc messages from Wine. So, you can see it's really just a small step to then drop Wine and handle the management of Windows ourselves instead of using Wine for it. Not trying to be rude either. You asked, I answered. Peter -----Original Message----- From: "Steven Edwards" <steven_ed4153(a)yahoo.com> To: "Peter Dennis Bartok" <peter(a)novonyx.com>; <mono-winforms-list(a)ximian.com> Cc: <wine-devel(a)winehq.com> Date: Thursday, 01 July, 2004 21:03 Subject: Re: [Mono-winforms-list] Fw: [Mono-list] System.Windows.Forms plans. >Hello Peter, > >I am not trying to be rude but... > >--- Peter Dennis Bartok <peter(a)novonyx.com> wrote: >> >Rather than spending a whole lot of time rewritting things wouldnt >> it >> >be better to help the Wine project get stable and move to the 1.0 >> goal? >> >There is a roadmap and TODO on Winehq of things that are needed for >> >1.0. >> No, it wouldn't. Even if Wine already was 1.0 we still would not have >> the >> portability we're trying to get (ie. run on Solaris Sparc, Mac OS, >> etc) and > >Well Winelib does run on PPC and the port to Sparc is mostly done. 99% >of Wine even compiles on Alpha here for me. See > >http://www.winehq.com/site/status_porting > >> debugging would still be almost impossible (Wine does funky stuff >> with >> register for thread storage, special stuff would be required to setup >> Mono-created threads before they'd be able to call Wine functions, >> etc). >> Also, there doesn't seem to be much interest from the Wine community >> to do >> anything that helps using Wine with SWF/Mono. We've had to resort to >> some >> quite complicated mechanisms to even be able to use Wine as a shared, >> runtime attached library, after Alexandre rejected a patch that only >> touched >> six lines of existing Wine code and added a new library to Wine, to >> allow >> straightforward use of Wine as a library. Having to take instead the >> complicated route it now means that many people are having problems >> getting >> SWF to run at all, with due to strict path dependencies. > >I was there when Miguel came online to ask why the patch was not merged >and I also seem to recall Alexandre proposed a fix the would work and >seemed to make Miguel happy. > >See: >http://www.winehq.org/hypermail/wine-devel/2004/03/0150.html > >> Another problem was that we had to spend way too much time tracking >> what >> changed from one Wine version to the next. For example from April to >> May, >> the wine_get_unix_file_name() function arguments were changed (I'm >> not even >> asking why it was changed instead of introducing a new function with >> different arguments and leaving the old one for those people who >> might use >> it). Since I can't require always the latest Wine version, I have to >> come up >> with code figuring out what Wine version might be running, and write >> code to >> make version dependent Wine calls. I'd rather spend that time >> improving SWF. > >Once again how can you fuss about unstable interfaces on a project that >does not have a stable release? You could work with Winehq to create >those stable interfaces. > >Besides how can you blame the Wine project for tracking changes when >the first patch Mono submitted was this? > >http://primates.ximian.com/~duncan/mono-wine/sources/mono-wine.patch > >A whole bunch of #ifdefs and other kludges that violates Winehq coding >standards. > >> Notice how people complain on this mailing that they're having >> problems >> getting even basic stuff going? The SWF code works, it's the >> interaction >> with Wine that's mostly causing the problems. Again, as I said, it >> will >> become much easier for the regular user once the Wine dependency is >> removed >> and the controls are all in managed code. > >Alright well I am not claiming to know very much about the project. >Like I said I only lurk here because I care about how its going to run >on ReactOS. I guess my final though on the matter is that if Vertigo >Software could make a mananged Quake2, how hard can it be for you to >make a managed Wine? > >Thanks >Steven > > > > >__________________________________ >Do you Yahoo!? >Yahoo! Mail - 50x more storage than other providers! >http://promotions.yahoo.com/new_mail >_______________________________________________ >Mono-winforms-list maillist - Mono-winforms-list(a)lists.ximian.com >http://lists.ximian.com/mailman/listinfo/mono-winforms-list > >

8 9

IE6 installation error. would you please give me a suggession
by Shiva Ram Krishna 03 Jul '04

03 Jul '04

Dear Sir/Madam, I downloaded the latest cvs of wine and compiled it. All went well but it seems that the regsvr32.exe.so file wasn't created properly. If check the dependency o f expand.exe.so, winver.exe.so, winepath.exe.so, I can see all the proper files that it needs but if I do it on regsvr32.exe.so, it says "regsvr32.exe.so: Not a dynamic executable". I have that his problem for the last 3-4 months. I used a text editor and it seems that the header is the regsvr 32.exe.so looks like an msdos .exe file (ex, first 2 characters have "MZ") but e xpand,winver, and winepath start with "^^". The reason I have notified it is when I run ie 5/6, It stops at the point saying "/usr/local/bin/wine: cannot open builtin library for 'C:\windows\system\regsvr32.exe': /usr/local/lib/wine/regsvr32.exe.so: invalid ELF header". would you please suggest me what I have to do ________________________________________________________________________ Yahoo! India Careers: Over 50,000 jobs online Go to: http://yahoo.naukri.com/

4 3

Re: collation tables
by Dmitry Timoshkov 03 Jul '04

03 Jul '04

"Vitaly Lipatov" <lav(a)altlinux.ru> wrote: > > What app is it? In which way it depends on the collation table > > being MS compatible? > It is 1C, an accounting system, widely used in Russia. > It keep a copy "right" collation table in exe file and compare it > with gotten from system. > > > Crossover Office has a patched version > > libs/unicode/collation.c, could you try it with your > > aplication? > If I have not Crossover Office, how I can try it? There is a Wine tar ball somewhere on the Codeweavers site which is used in the CX Office. It's freely available, since Wine is LGPL'ed. > > > Does anyone knows what is the better way to fix this tables, > > > in which place? Can I fix libs/unicode/cpmap.pl for it? > > > > Yes, that was an idea. > I see it idea is implemented in CrossOver Office already? No, nothing has been done yet, just a bit of thoughts. -- Dmitry.

2 4

taskmgs hangs on edit debug channels
by Andrei Barbu 02 Jul '04

02 Jul '04

The taskmanager dies when trying to edit the debug channels of any programs with the newest CVS (checked out 2 days ago) It just sits there with this: 002e:Ret x11drv.MsgWaitForMultipleObjectsEx() retval=00000102 ret=409cd43c 002e:Call kernel32._ConfirmSysLevel(40a08ac0) ret=409a3f15 002e:Ret kernel32._ConfirmSysLevel() retval=00000000 ret=409a3f15 002e:Call kernel32.GlobalLock16(0000116f) ret=40999b70 002e:Ret kernel32.GlobalLock16() retval=404326d0 ret=40999b70 002e:Call kernel32.ReleaseThunkLock(41625f7c) ret=409cd30f 002e:Ret kernel32.ReleaseThunkLock() retval=00000000 ret=409cd30f 002e:trace:msg:GetMessageW (116f) mask=0000007f, bits=00000000, changed=00000000, waiting 002e:Call kernel32.ReleaseThunkLock(41625fe4) ret=409cd684 002e:Ret kernel32.ReleaseThunkLock() retval=00000000 ret=409cd684 002e:Call x11drv.MsgWaitForMultipleObjectsEx(00000001,404326d4,ffffffff,00000000,00000000) ret=409cd6c6 002e:Call ntdll.RtlEnterCriticalSection(40d76680) ret=40d54902 002e:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=40d54902 002e:Call ntdll.RtlLeaveCriticalSection(40d76680) ret=40d54932 002e:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=40d54932 002e:Call ntdll.RtlEnterCriticalSection(40d76680) ret=40d54902 002e:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=40d54902 002e:Call ntdll.RtlLeaveCriticalSection(40d76680) ret=40d54932 002e:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=40d54932 002e:Call kernel32.WaitForMultipleObjectsEx(00000002,41625dac,00000000,ffffffff,00000000) ret=40d383db 002e:Call ntdll.NtWaitForMultipleObjects(00000002,41625ba0,00000000,00000000,00000000) ret=40591c85 If I move the mouse it spits out the correct mouse messages which indicate that wine itself is running just fine. The taskmanager window doesn't get redrawn (the black backround around it does). The backtrace from that point is: =>1 0x400636a9 (0x41b2be48) 2 0x402335c2 NTDLL_wait_for_multiple_objects+0x122(count=0x1, handles=0x41b2bf38, flags=0x4, timeout=0x0) [sync.c:587] in ntdll (0x41b2beec) 3 0x40233636 NtWaitForMultipleObjects+0x66(count=0x1, handles=0x41b2bf38, wait_all=0x0, alertable=0x0, timeout=0x0) [sync.c:605] in ntdll (0x41b2bf14) 4 0x40591c85 WaitForMultipleObjectsEx+0xb5(count=0x1, handles=0x41b2c06c, wait_all=0x0, timeout=0xffffffff, alertable=0x0) [sync.c:171] in kernel32 (0x41b2c044) 5 0x40591b1a WaitForSingleObject+0x3a(handle=0x6c, timeout=0xffffffff) [sync.c:99] in kernel32 (0x41b2c064) 6 0x40656867 ProcessPageRefreshThread+0x87(lpParameter=0x0) [procpage.c:511] in taskmgr (0x41b2c1a4) 7 0x40598fba THREAD_Start+0x11a(ptr=0x40450220) [thread.c:107] in kernel32 (0x41b2c27c) 8 0x40234fe9 start_thread+0x199(info=0x40450240) [thread.c:198] in ntdll (0x41b2cacc) 9 0x4005df70 (0x41b2cbcc) 10 0x4017e40a (0x00000000) Any ideas? I'm not quite versed enough in wine to know what's happening too well. I realise it's a thread waiting for another that apparently never finishes.. or I think it is, and I'm kind of lost from there. Thanks, Andrei

2 1

Delayed breakpoints in winedbg
by Adrian Rees 02 Jul '04

02 Jul '04

Hi all, Apologies in advance for what is probably a dumb question... I'm trying to debug a windows application by breaking on a call to a DLL function - in fact it's the NtCreateKey function within the ntdll library. I must be missing something fundamental because the debugger indicates that it has set a delayed breakpoint, but the breakpoint is never reached, although turning on debugging messages clearly indicates that the function is being called. Here's a typical attempt: $ WINDEBUG=reg winedbg MSMONEY.EXE ... (lots of startup calls to reg) ... In 32 bit mode. Wine-dbg>break NtCreateKey fixme:dbghelp:elf_new_wine_thunks Duplicate in midimap.drv<elf>: _edata<5b828a10 -00000000> completed.1<5b828a10-00000000> ... (snip) ... No symbols found for NtCreateKey Unable to add breakpoint, will check again when a new DLL is loaded Wine-dbg>info break No breakpoints No watchpoints Delayed breakpoints: 0: NtCreateKey Wine-dbg>cont trace:reg:NtCreateKey(0x28,L"Software\\Microsoft\\Windows\\CurrentVersion\\AppPaths\\MSMONEY.EXE",L"",1,1,0xb9fd04) trace:reg:NtCreateKey <- 0x50 trace:reg:RegQueryValueExA(0x50,"Path",(nil),0xb9fcf8,0xb9f318,0xb9fd00=260) ... (etc till program ends) ... I've spent a couple of hours searching for more information on how to use this capability of the debugger, but with no luck - can anyone tell me what I'm doing wrong? Thanks, Adrian

2 3

Re: collation tables
by Dmitry Timoshkov 02 Jul '04

02 Jul '04

"Jonathan Wilson" <jonwil(a)tpgi.com.au> wrote: > Given that simply calling whatever the locale functions are on windows and > using their results is considered too legally risky (because the results > are almost certainly covered under a MS copyright), the best solution is to > simply take the best possible implementation we have now then build a > testcase. Build a testcase that calls the locale functions and checks that > the output matches. From there, you can fix WINE untill it passes the tests. > > This is how it is done for most other things in WINE, so why not this? Look at the dlls/kernel/tests/locale.c,test_CompareStringA/test_LCMapStringA > Another way is to look at what ReactOS has, do they have collation tables? > Are they good? Can WINE use them? (I would assume they would need to be > relicenced but other than that...) I don't think ReactOS has anything except .nls and case mapping files generated with the tool I wrote. Even those files aren't used AFAIK. -- Dmitry.

1 0

Re: winedbg crashes
by Jon Griffiths 02 Jul '04

02 Jul '04

Hi Eric, <cc'd to wine-devel so anyone with a similar problem can google for the fix> > no, it's normal you get this. In fact, we should simply abort the > loading. > Does this work better ? I can't test it unfortunately, but it looks like the right thing to do. I asked on bugs@binutils and was told to upgrade to binutils 2.15 to fix the bad stab generation. Sure enough, this fixes the issue (which means I can't duplicate this behaviour any more). It also fixed a bunch of other random crashes in my app; There were obviously some needed fixes for huge (40 MB in this case) .so generation. So perhaps printing a message to upgrade binutils to >=2.15 when the stabs are found to be corrupted would be appropriate? I'm not sure how prevalent this version is in the wild (my mdk 10 community uses 2.13). I'm investigating now to see if debugging works as expected (so far, so good) Thanks, Jon ===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live jon_p_griffiths(a)yahoo.com __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail

1 0

IE6 installation error. would you please give me a suggession
by Shiva Ram Krishna 02 Jul '04

02 Jul '04

Dear Sir/Madam, I downloaded the latest cvs of wine and compiled it. All went well but it seems that the regsvr32.exe.so file wasn't created properly. If check the dependency of expand.exe.so, winver.exe.so, winepath.exe.so, I can see all the proper files that it needs but if I do it on regsvr32.exe.so, it says "regsvr32.exe.so: Not a dynamic executable". I have that his problem for the last 3-4 months. I used a text editor and it seems that the header is the regsvr32.exe.so looks like an msdos .exe file (ex, first 2 characters have "MZ") but expand,winver, and winepath start with "^^". The reason I have notified it is when I run ie 5/6, It stops at the point saying "/usr/local/bin/wine: cannot open builtin library for 'C:\windows\system\regsvr32.exe': /usr/local/lib/wine/regsvr32.exe.so: invalid ELF header". would you please suggest me what I have to do ________________________________________________________________________ Yahoo! India Careers: Over 50,000 jobs online Go to: http://yahoo.naukri.com/

1 0

Re: [Mono-winforms-list] Fw: [Mono-list] System.Windows.Forms plans.
by Peter Dennis Bartok 02 Jul '04

02 Jul '04

>You are asking for stable interfaces and those can only come once there >is a Wine 1.0. Its not here and dont get me wrong I think the Wine TODO >list is way to long and things should be close to frozen by now but >thats not the case. All you are doing is pointing out that its not >stable which is well known. I wish it was stable now but its not and >until the TODO is done its not going to be. Paul's message was very specific, asking about a versioning interface (which I would have loved to have, too, instead of trying to guess in code what version of Wine I might be dealing with). If very reasonable API requests are being refused while it is still under heavy development why would those be granted once 1.0 is reached? And, thus, how is working down the TODO going to help his request? With SWF we luckily have a choice whether or not use use Wine, we tried with and it didn't quite work out, so now we're gonna try without. Paul isn't as lucky, his code is dependent on the Win32 API. I would have thought that Alexandre is exited that his code is being put to new, cool uses even he never imagined... With that I should probably stop participating in this thread, since it's really not contributing to SWF development :-) Regards, Peter

1 0

Re: [Mono-winforms-list] Fw: [Mono-list] System.Windows.Forms plans.
by Steven Edwards 02 Jul '04

02 Jul '04

Hello Peter, I am not trying to be rude but... --- Peter Dennis Bartok <peter(a)novonyx.com> wrote: > >Rather than spending a whole lot of time rewritting things wouldnt > it > >be better to help the Wine project get stable and move to the 1.0 > goal? > >There is a roadmap and TODO on Winehq of things that are needed for > >1.0. > No, it wouldn't. Even if Wine already was 1.0 we still would not have > the > portability we're trying to get (ie. run on Solaris Sparc, Mac OS, > etc) and Well Winelib does run on PPC and the port to Sparc is mostly done. 99% of Wine even compiles on Alpha here for me. See http://www.winehq.com/site/status_porting > debugging would still be almost impossible (Wine does funky stuff > with > register for thread storage, special stuff would be required to setup > Mono-created threads before they'd be able to call Wine functions, > etc). > Also, there doesn't seem to be much interest from the Wine community > to do > anything that helps using Wine with SWF/Mono. We've had to resort to > some > quite complicated mechanisms to even be able to use Wine as a shared, > runtime attached library, after Alexandre rejected a patch that only > touched > six lines of existing Wine code and added a new library to Wine, to > allow > straightforward use of Wine as a library. Having to take instead the > complicated route it now means that many people are having problems > getting > SWF to run at all, with due to strict path dependencies. I was there when Miguel came online to ask why the patch was not merged and I also seem to recall Alexandre proposed a fix the would work and seemed to make Miguel happy. See: http://www.winehq.org/hypermail/wine-devel/2004/03/0150.html > Another problem was that we had to spend way too much time tracking > what > changed from one Wine version to the next. For example from April to > May, > the wine_get_unix_file_name() function arguments were changed (I'm > not even > asking why it was changed instead of introducing a new function with > different arguments and leaving the old one for those people who > might use > it). Since I can't require always the latest Wine version, I have to > come up > with code figuring out what Wine version might be running, and write > code to > make version dependent Wine calls. I'd rather spend that time > improving SWF. Once again how can you fuss about unstable interfaces on a project that does not have a stable release? You could work with Winehq to create those stable interfaces. Besides how can you blame the Wine project for tracking changes when the first patch Mono submitted was this? http://primates.ximian.com/~duncan/mono-wine/sources/mono-wine.patch A whole bunch of #ifdefs and other kludges that violates Winehq coding standards. > Notice how people complain on this mailing that they're having > problems > getting even basic stuff going? The SWF code works, it's the > interaction > with Wine that's mostly causing the problems. Again, as I said, it > will > become much easier for the regular user once the Wine dependency is > removed > and the controls are all in managed code. Alright well I am not claiming to know very much about the project. Like I said I only lurk here because I care about how its going to run on ReactOS. I guess my final though on the matter is that if Vertigo Software could make a mananged Quake2, how hard can it be for you to make a managed Wine? Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail

1 0

collation tables
by Vitaly Lipatov 01 Jul '04

01 Jul '04

In test dlls/kernel/tests/locale.c I see comment /* this requires collation table patch to make it MS compatible */ I get trouble with one program it needed collation table to be identical to MS table. Does anyone knows what is the better way to fix this tables, in which place? Can I fix libs/unicode/cpmap.pl for it? Any suggestions? -- Lav Vitaly Lipatov Saint-Petersburg GNU! ALT Linux Team! LaTeX! LyX!

2 1

Re: fix bug in GetCPInfo
by Uwe Bonnes 01 Jul '04

01 Jul '04

>>>>> "Vitaly" == Vitaly Lipatov <lav(a)altlinux.ru> writes: Vitaly> Bug: When call GetCPInfo with CP_ACP for example, in returned Vitaly> structure field CodePage filled with CP_ACP constant, not real Vitaly> codepage of current ACP. The attached patch fix this bug. I Vitaly> have compared behavior of this functions with Win2003. This implies, that you have written a test. Please provide the test for our test suite. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

2 1

psapi.dll tests
by Ferenc Wagner 01 Jul '04

01 Jul '04

Hi, please somebody enlighten me! How does this test work once psapi_test.exe is linked with -lpsapi? How can a program start at all without one of its hard dependencies? START_TEST(module) { dll = LoadLibrary("psapi.dll"); if (!dll) { trace("LoadLibraryA(psapi.dll) failed: skipping tests with target module\n"); return; } The above seems to be a common idiom which I don't understand as opposed to using GetProcAddress and invoking functions through pointers. What am I missing here? -- Feri.

2 2

Bad Icon display with native comctl32
by Uwe Bonnes 01 Jul '04

01 Jul '04

Hallo, running with native comctl32, some programs show a bad icon display in treeviews. E.g. Xilinx ISE shows this behaviour. A JPG of the treeview with Icons is appended. A debug log with +relay,+bitmap,+x11drv is about 400 MByte. Any hints how to tackle that problem? Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

Cleaning up W->A calls
by James Hawkins 01 Jul '04

01 Jul '04

I recently decided to help with the development of Wine, and seeing as how I am new to the process, I have chosen menial tasks to take on. This way I can learn more about Wine while contributing. I am currently working on the janitorial task of getting rid of W->A calls and I have a few questions about how I should implement these changes. I'll start the question with an example: dlls/advapi32/crypt.c line 255, 482 BOOL WINAPI CryptAcquireContextA (HCRYPTPROV *phProv, LPCSTR pszContainer, LPCSTR pszProvider, DWORD dwProvType, DWORD dwFlags) { ... complete implementation } BOOL WINAPI CryptAcquireContextW (HCRYPTPROV *phProv, LPCWSTR pszContainer, LPCWSTR pszProvider, DWORD dwProvType, DWORD dwFlags) { PSTR pProvider = NULL, pContainer = NULL; BOOL ret = FALSE; TRACE("(%p, %s, %s, %ld, %08lx)\n", phProv, debugstr_w(pszContainer), debugstr_w(pszProvider), dwProvType, dwFlags); if ( !CRYPT_UnicodeToANSI(pszContainer, &pContainer, -1) ) CRYPT_ReturnLastError(ERROR_NOT_ENOUGH_MEMORY); if ( !CRYPT_UnicodeToANSI(pszProvider, &pProvider, -1) ) { CRYPT_Free(pContainer); CRYPT_ReturnLastError(ERROR_NOT_ENOUGH_MEMORY); } ret = CryptAcquireContextA(phProv, pContainer, pProvider, dwProvType, dwFlags); if (pContainer) CRYPT_Free(pContainer); if (pProvider) CRYPT_Free(pProvider); return ret; } Initially CryptAcquireContextW converts all of its arguments to ansi then calls CryptAcquireContextA (which is intuitively not what we're wanting and thus the cleanup.) The question is, what exactly is the best way to clean this up? It seems to me that there are two main options as to what can be done: A) convert the W->A calls in the wide-char functions to A->W calls in the asci functions and implement the wide-char functions instead, or B) implement both asci and wide-char functions separately ie asci functions only call asci functions etc. If we are to choose plan A, I have seen several different methods of converting asci to wide-char, and I am wondering which method is best. for example: dlls/advapi32/crypt.c lines 133-141 wcount = MultiByteToWideChar(CP_ACP, 0, str, -1, NULL, 0); wcount = wcount < wstrsize/sizeof(WCHAR) ? wcount : wstrsize/sizeof(WCHAR); if (wstrsize == -1) *wstr = CRYPT_Alloc(wcount * sizeof(WCHAR)); if (*wstr) { MultiByteToWideChar(CP_ACP, 0, str, -1, *wstr, wcount); return TRUE; } and, dlls/advapi32/registry.c lines 1626-1636 LONG WINAPI RegSaveKeyA( HKEY hkey, LPCSTR file, LPSECURITY_ATTRIBUTES sa ) { UNICODE_STRING *fileW = &NtCurrentTeb()->StaticUnicodeString; NTSTATUS status; STRING fileA; RtlInitAnsiString(&fileA, file); if ((status = RtlAnsiStringToUnicodeString(fileW, &fileA, FALSE))) return RtlNtStatusToDosError( status ); return RegSaveKeyW(hkey, fileW->Buffer, sa); } Which method is better/more efficient? I would have to argue that implementing both the asci functions and wide-char functions separately would be the most efficient way to solve the W->A problem. Throughout all the wine libs, many conversion calls are being made from W->A and A->W, when most of these calls could be left out. I think performance would improve without all of the conversion calls. Granted the size of the code would increase, but speed would also increase. There are a couple snags when it comes to implementing asci and wide-char functions independently, but that can be discussed later. If I'm totally off the mark, let me know, and if there are other jobs I could be doing, let me know as well because I would like to contribute, but I'm not exactly sure what to do yet. Thankyou for your time. James Hawkins truiken(a)comcast.net

4 4

Re: dlls/shell32 W->A cleanup of systray.c
by Marcelo Duarte 30 Jun '04

30 Jun '04

Danny Hawkins wrote: >Hi, > >Converted all wide-char->ansi calls to ansi->wide-char in systray.c > > > The TTM_UPDATETIPTEXTA should be converted to TTM_UPDATETIPTEXTW and TTM_ADDTOOLA -> TTM_ADDTOOLW >@@ -272,13 +272,13 @@ > ti.rect.bottom = ICON_SIZE+2*ICON_BORDER; > > if(modify) >- SendMessageA(ptrayItem->hWndToolTip, TTM_UPDATETIPTEXTA, 0, (LPARAM)&ti); >+ SendMessageW(ptrayItem->hWndToolTip, TTM_UPDATETIPTEXTA, 0, (LPARAM)&ti); > else >- SendMessageA(ptrayItem->hWndToolTip, TTM_ADDTOOLA, 0, (LPARAM)&ti); >+ SendMessageW(ptrayItem->hWndToolTip, TTM_ADDTOOLA, 0, (LPARAM)&ti); > } > > Here, you should'nt cast (WCHAR *)"". Please define: static const WCHAR emptyW[] = {0}; Or modify the function to accept NULL. >@@ -297,15 +297,15 @@ > (*ptrayItem)->notifyIcon.hWnd = pnid->hWnd; /* only needed for callback message */ > SYSTRAY_ItemSetIcon (*ptrayItem, (pnid->uFlags&NIF_ICON) ?pnid->hIcon :0); > SYSTRAY_ItemSetMessage(*ptrayItem, (pnid->uFlags&NIF_MESSAGE)?pnid->uCallbackMessage:0); >- SYSTRAY_ItemSetTip (*ptrayItem, (pnid->uFlags&NIF_TIP) ?pnid->szTip :"", FALSE); >+ SYSTRAY_ItemSetTip (*ptrayItem, (pnid->uFlags&NIF_TIP) ?pnid->szTip :(WCHAR *)"", FALSE); > > The old code should be eliminated, not commented: >+/*{ > BOOL flag=FALSE; > TRACE("enter %p %d %ld\n", pnid->hWnd, pnid->uID, dwMessage); > switch(dwMessage) { >@@ -377,13 +390,30 @@ > } > TRACE("leave %p %d %ld=%d\n", pnid->hWnd, pnid->uID, dwMessage, flag); > return flag; >-} >+}*/ > > > >+/*{ > BOOL ret; > > PNOTIFYICONDATAA p = HeapAlloc(GetProcessHeap(),0,sizeof(NOTIFYICONDATAA)); >@@ -395,4 +425,4 @@ > > HeapFree(GetProcessHeap(),0,p); > return ret; >-} >+}*/ > >

1 0

Scrollbars, an application bug or a wine regression ? (#2314)
by Gabriele Giorgetti 30 Jun '04

30 Jun '04

Hello, I've noticed a problem with scrollbars in the latest Wine's release (20040615). With wine version 20040505 everything was just fine. I've attacched a zip file with two screenshots (pls. see wine BUG #2314 @ bugs.winehq.org ) the first one is the correct behavior of the app using wine 20040505 the second one is wine 20040615 and the app in its wrong behavior. Trying to describe the problem: The application show up with a bottom scrollbar and a right scrollbar even if they are not needed. When executing the very same application, with the very same settings and size with wine 20040505 the scrollbars are not there. I hope you get it Thanks. NB: BUG #2314 at bugs.winehq.org

5 9

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