September 2003 - Wine-Devel

Re: error installing ikernel.exe
by eric Sept. 12, 2003

Sept. 12, 2003

On Thursday 11 September 2003 15:40, Sylvain Petreolle wrote: > this problem is known, see > http://www.winehq.org/hypermail/wine-users/2003/05/0075.html > > Dear Sylvain: Thanks your pointout, I download cvs rpm from http://wine.dataparty.no latest normal build but when I run, it have error as segmentation fault --------------------- [root(a)localhost root]# rpm -vhi wine-cvs* Preparing... ########################################### [100%] 1:wine-cvs-unstripped ########################################### [100%] Be sure to edit /etc/wine/config to match your system, and copy it to ~<user>/.wine/ before using Wine. Run 'man wine.conf' for information. ------ [root(a)localhost x86]# wine 123* Segmentation fault ------------------------------------- highly appreciate your help again, if that need to modify /etc/wine/config my platform is rh9 -2.4.20-20.9 amd xp Sincerely Eric

1 0

compiling mfc
by Deji Akinyemi Sept. 12, 2003

Sept. 12, 2003

Hi! Does anyone have a set of directives on how one goes about generating an MFC library for winelib from the sources? I just started the process, and got pass the mfc/atl configuration hic-ups. Now I am trying to get things to compile and that is another story. I am presently getting an error while compiling that atl that goes: LD_LIBRARY_PATH=":$LD_LIBRARY_PATH" /usr/bin/wrc -I. -I/usr/local/include/wine/windows -o atl.res atl.rc atl.rc:54:58: Error: Cannot open file atl.tlb make: *** [atl.res] Error 1 from http://www.winehq.org/hypermail/wine-users/2001/03/0301.html I am inferring that atl.tlb may not be needed. I may be wrong. It appears that it is going to be a very long series of trial and error. I've looked for information to help but it has been very scanty. Is there a script or Makefile that automates this process? At this point any information helps. Thanks in advance for any pointers. Deji.

2 1

error installing ikernel.exe
by eric Sept. 12, 2003

Sept. 12, 2003

Dear wine users: in my rh9, I try to run a video conference program, it first ask me to install DCOM95 from microsoft's site, I did it(with some error message, I did not fully mention) then I try my video conference program under wine, it soon pop out a window complain error installing ikernel.exe highly appreciate any suggestion and thanks in advance Sincerely Eric

1 0

ReactOS and WINE development on AlphaAXP and others
by Steven Edwards Sept. 12, 2003

Sept. 12, 2003

Hello, HP has recently extended the loan I requested on this alpha pws500 workstation for another year. If anyone is interested in working on porting WINE or ReactOS to the alpha email me privatly and I can setup a account for you on the system. I have another system a friend has let me borrow for atleast a few months if anyone is interested in doing some porting work on it. Its a SGI Indigo 2 IMPACT 10000. I still need to load linux on it and get it up on the network though it will be a few weeks before anyone can use it if they are interested in starting a MIPS port. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

[cvs compile error in for MSI dll]
by Evalet Olivier Sept. 11, 2003

Sept. 11, 2003

I have to modify the *.c files (from the MSI dll) by adding this: #include <stdarg.h> Is this my configuration which is wrong? Olivier ------------------ www.programmers.ch

1 0

header problems
by Dimitrie O. Paun Sept. 11, 2003

Sept. 11, 2003

Hi folks, In each of the include/{pshpack[1248],poppack}.h headers we have checks like this: # if defined(__GNUC__) || defined(__SUNPRO_C) || defined(__SUNPRO_CC) || defined(_MSC_VER) # pragma pack(1) # elif !defined(RC_INVOKED) # error "Adjusting the alignment is not supported with this compiler" # endif Problem is that __GNUC__ is not defined when the standalone preprocessor (cpp) includes the headers, resulting in an error. Needless to say, this is Not Good (TM), as the standard headers can be used by cpp (I think :)). How do we solve this? Maybe change the last condition to: -# elif !defined(RC_INVOKED) +# elif defined(WINE_HEADER_DEBUG_ON) or +# elif defined(__WINESRC__) or some such? -- Dimi.

2 2

TextOut text removed if hbrBackground is set
by Igor Grahek Sept. 11, 2003

Sept. 11, 2003

I have problem with following example. If wc.hbrBackground is set (line 16) text printed with TextOut is overpainted with that color. If I comment out that line everything is OK. Under windows this works fine. ----- code begin ----------- WNDCLASS wc; HWND hWineTest2Wnd; HDC hWineTest2WndDC; HFONT hFont, hOldFont; COLORREF OldTextColor; int nOldBkMode; POINT CursorPos; int XPosition,YPosition; static char cszWineTest2WndCls[] = "WineTest2WndClass"; static char cszWineTest2Wnd[] = "WineTest2Wnd"; char *szTestStr = "WineTest Text"; memset( &wc, 0, sizeof( wc ) ); wc.hInstance = hInst; wc.style = CS_OWNDC; wc.hbrBackground = (HBRUSH)( COLOR_BACKGROUND +1 ); //Works OK if this line is removed wc.lpszClassName = (LPSTR)cszWineTest2WndCls; wc.lpfnWndProc = (WNDPROC)DefWindowProc; if ( !RegisterClass( &wc ) ) return NULL; GetCursorPos( &CursorPos ); XPosition = CursorPos.x; YPosition = CursorPos.y; hWineTest2Wnd = CreateWindow( (LPCTSTR)cszWineTest2WndCls, (LPCTSTR)cszWineTest2Wnd, WS_POPUPWINDOW, ( XPosition + 2), ( YPosition + 20 ), 250, 50, hwndParent, 0, hInst, NULL ); if ( !hWineTest2Wnd ) { UnregisterClass( (LPSTR)cszWineTest2WndCls, hInst ); return NULL; } hFont = (HFONT)GetStockObject( DEFAULT_GUI_FONT ); hWineTest2WndDC = GetDC( hWineTest2Wnd ); hOldFont = (HFONT)SelectObject( hWineTest2WndDC, hFont ); nOldBkMode = SetBkMode( hWineTest2WndDC, TRANSPARENT ); OldTextColor = SetTextColor( hWineTest2WndDC, RGB( 0,0,0 ) ); ShowWindow( hWineTest2Wnd, SW_SHOWNOACTIVATE ); TextOut( hWineTest2WndDC, 1, 1, (LPCTSTR)szTestStr, strlen( szTestStr ) ); SelectObject( hWineTest2WndDC, hOldFont ); DeleteObject( hFont ); SetBkMode( hWineTest2WndDC, nOldBkMode ); ReleaseDC( hWineTest2Wnd, hWineTest2WndDC ); return hWineTest2Wnd; ----- code end -------- Igor

1 0

Re: [resend 3rd] additional NULL parameter checks within winmm.c
by Alexandre Julliard Sept. 11, 2003

Sept. 11, 2003

Oleg Prokhorov <xolegpro(a)rbcmail.ru> writes: > Changelog: > Add more NULL parameter checks to winmm.c When adding NULL checks you have to explain why you think they are needed, and how you made sure you are not simply hiding another bug. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Indent to get Avisynth working with Wine/Winelib
by Dan Kegel Sept. 11, 2003

Sept. 11, 2003

Kevin wrote: > BTW: You can find my C API at http://kevin.atkinson.dhs.org/avisynth_c/. > Avisynth: http://www.avisynth.org/. And a dead simple program as the > test case for the bug http://bugs.winehq.org/show_bug.cgi?id=1707 . That test case involves compiling a program with mingw. Can you compile that program with vc++ instead, and if so, does it then work? Let's make sure avisynth and your API work with 100% microsoft tools under Wine before we dive in to making it work with gcc. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

2 1

Indent to get Avisynth working with Wine/Winelib
by Kevin Atkinson Sept. 11, 2003

Sept. 11, 2003

Hi, I am the developer of the C interface for Avisynth. Avisynth is a very popular Open Source tool for for video post-production for Win32. More information can be found at http://www.avisynth.org/. My intent is to get Avisynth working under Linux with the help of Wine/Winelib. Since it normal interface is VC++ recompiling it under Winelib is not really an option as that will mean that existing plugins for Avisynth will no longer work without a recompile. My main purpose of the C API I am developing is to act as a bridge so that GCC compiled programs can communicate with it. This will allow it to be used as a filter in Linux programs, and should even allow Linux specific plugins to work with Avisynth under Linux. But first I need to get Avisynth working under wine. I filed a bug report on the matter, http://bugs.winehq.org/show_bug.cgi?id=1707 , and would really appreciate if someone could look into it. After I get Avisynth working I need to be able to call the DLL from Linux. I believe that is possible but I can't seam to find out how after looking over the winelib docks. After that I might want to avoid having to use the full blown wine emulator by only proving the API calls Avisynth really needs much like the method used to get windows codec working under Linux. But first I need to get Avisynth working under wine. I know very little about Windows development or wine so I really can't fix the bug on my own. Thanks in advance. -- http://kevin.atkinson.dhs.org

6 18

Re: TreeView control - set correct hwndNotify
by Dimitrie O. Paun Sept. 11, 2003

Sept. 11, 2003

On September 8, 2003 03:52 pm, Igor Grahek wrote: > ChangeLog: - TreeView control set Notify window correctly in case that > window style is WS_POPUP. Please send unidiff patches: http://www.winehq.org/site/sending_patches > ! if ((infoPtr->dwStyle & (WS_CHILD|WS_POPUP)) == WS_POPUP && > IsWindow(((LPCREATESTRUCTW)lParam)->hwndParent )) > ! infoPtr->hwndNotify = ((LPCREATESTRUCTW)lParam)->hwndParent; > ! else > ! infoPtr->hwndNotify = GetParent(hwnd); > ! I'm curious, can't we always use lpcs->hwndParent here? Or maybe do a GetParent(hwnd) when ->hwndParent is NULL? We should propage this to the other controls as well... -- Dimi.

4 6

Wine repeated unhandled exptions
by Shachar Shemesh Sept. 11, 2003

Sept. 11, 2003

Hi list, I have just performed an upgrade to my Debian Sid Linux. During the upgrade, libc was replaced. I can now not get Wine to work on the new install. Previously, I would use Wine without --with-nptl. This no longer works. Wine sigsegv on startup (whether there are parameters or not). compiling with --with-nptl gets me slightly further. Running wine without parameters produces the help printout. However, when I try to actually run something, this does not work. It doesn't matter what I try to run (whether winelib or Windows). I get a series of "unhandled expection". This happens even for the regedit that is supposed to install my default registry via tools/wineinstall Any ideas? Anyone? -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/

5 11

Compilation errors when compiling without optimizations
by Shachar Shemesh Sept. 10, 2003

Sept. 10, 2003

Hi, When trying to compile Wine without optimizations, the compilation fails. I'm trying clean sources, with the "--with-nptl" flag. The failure (so far, I'm still trying to figure these things out) are when compiling ntdll and the wine executable itself. Both cases, the problem is that same. The linker complains that "InterlockedCompareExchange" cannot be found. Adding kernel32 to the IMPORTS Makefile at dlls/ntdll and miscemu/wine seem to solve these problems, but I'm somewhat worried, and would like to get a second opinion before I submit a patch about this. Shachar p.s. For me (P-IV 1600MHZ) complete build compile takes 25 minutes. I've now switched to ccache, hoping I can bring it down even lower. Sh. -- Shachar Shemesh Open Source integration consultant Home page & resume - http://www.shemesh.biz/

4 3

newbie - question: compiling winelib's winemine
by Deji Akinyemi Sept. 10, 2003

Sept. 10, 2003

Hi there! I am trying to get up to speed on developing applications using wine. The winelib-user documentation recommends getting started by taking a look at the winemine (wine-xxxxxx/programs/winemine) code packaged with the library. I seem to be having different outcomes when I compile the code with the original Makefile and when I do so with the Makefile generated with winemaker. The original winemine makefile compiles the code without a problem and the program runs, however when I run the makefile generated by winemaker I get the following error: LD_LIBRARY_PATH=":$LD_LIBRARY_PATH" /usr/bin/wrc -I. -I/usr/local/include/wine/windows -o En.res En.rc En.rc:23:22: Error: parse error The wine-lib documentation mentions editing the Makefile.in file, I have looked at it and compared it with the original winmine Makefile. The winemaker makefile includes the files En.rc and Pt.rc in it RC_SRCS which is absent from the original Makefile. I removed the two entries with the result that the code compiles, but however fails to run. I do not get any error messages. Apart from those RC_SRCS entries I haven't noticed anything semantically that would result in the different behaviors that I am getting, granted, I may be missing some things. What parameters do I need to pass to winemaker to get this program to run, or are there certain changes I need to make to the Makefile that I a missing? Thanks for any help or advice. Deji. P.S. Any recommendations on winelib primers would also be much appreciated.

3 3

Re: FAQ: Update the ports section
by John Freed Sept. 10, 2003

Sept. 10, 2003

Ah, the difference between British English and American English. <lang=en-uk>ManU are crushing Arsenal.</lang> <lang=en-us>ManU is crushing Arsenal.</lang> UK English insists on plural verbs for collective nouns (family, team, list, etc.), while US English generally uses singular verbs. (An exception is "couple" referring to a romantic pair -- "The couple are going to the store" would be acceptable on both sides of the Atlantic, although many Americans would say "is" even here.) John Freed ---original message follows--- You must send me some of the stuff you're smoking! "The list are now up to date" doesn't exist in english, you must choose "The lists are now up to date" for a plural "The list is now up to date" for a singular

2 1

Segmentation fault after new wine update and install
by Juraj Hercek Sept. 10, 2003

Sept. 10, 2003

Hello, I've updated today from wine and got into troubles after installing it - got Segmentation fault. I dig in it and figured the problem is my environment variable WINEDLLPATH which was set to "." (current directory). The back trace of stack during the crash was similar to this (just the frames 5,6,7,8 were repeating many times - until stack overflow): #0 __pthread_rwlock_unlock (rwlock=0x4032b600) at ../../scheduler/pthread.c:669 #1 0x40220ea7 in gettext () from /lib/i686/libc.so.6 #2 0x40220885 in dcgettext () from /lib/i686/libc.so.6 #3 0x4021f667 in __assert_fail () from /lib/i686/libc.so.6 #4 0x400903d7 in __pthread_rwlock_unlock (rwlock=0x4032b600) at ../../scheduler/pthread.c:671 #5 0x40220ea7 in gettext () from /lib/i686/libc.so.6 #6 0x40220885 in dcgettext () from /lib/i686/libc.so.6 #7 0x4021f667 in __assert_fail () from /lib/i686/libc.so.6 #8 0x400903d7 in __pthread_rwlock_unlock (rwlock=0x4032b600) at ../../scheduler/pthread.c:671 #9 0x40220ea7 in gettext () from /lib/i686/libc.so.6 #10 0x40220885 in dcgettext () from /lib/i686/libc.so.6 #11 0x40278059 in strerror_r () from /lib/i686/libc.so.6 #12 0x40277ea5 in strerror () from /lib/i686/libc.so.6 #13 0x4035513a in dlerror () from /lib/libdl.so.2 #14 0x400f7c00 in wine_dlopen (filename=0x3c001862 "./ntdll.dll.so", flag=0x2, error=0xbffff244 "", errorsize=0x400) at loader.c:452 #15 0x400f745b in dlopen_dll (name=0x400f80cb "ntdll.dll", error=0xbffff244 "", errorsize=0x400, test_only=0x0, exists=0xbffff21c) at loader.c:151 #16 0x400f7b48 in wine_init (argc=0x1, argv=0xbffff694, error=0xbffff244 "", error_size=0x400) at loader.c:424 #17 0x3c000550 in main (argc=0x1, argv=0xbffff694) at main.c:33 #18 0x402137f7 in __libc_start_main () from /lib/i686/libc.so.6 So, I guess wine pthread functions table should be initialized before any (system) library get's chance to throw error, otherwise we have SIGSEGV. I've fixed the error on my side with WINEDLLPATH="/usr/local/lib/wine:.". Anyways I think it's a workaround not a solution... Since I don't know much about initialization, I would leave the real fix for someone more skillful. Best Regards, Juraj

3 6

Re: FAQ: Update the ports section
by Ivan Leo Murray-Smith Sept. 10, 2003

Sept. 10, 2003

>Thats the problem! >You have your fine dictonary in hand, so you think you know how to speak >english... but when you visit a english speaking country the people >you speak to look like a deer caught in a spot light! So you want a png of my british passport? (BTW it's dictionary, not dictonary, or is that just your american english?) >Shachar don't get mad or pissed.. I had to find someone for my >eniligey.. :) so "eniligey" is american english? Never heard it from Bush, fox tv, NPR... Shachar is right, and at least he uses english on this list, while you >ba bing, bing, bing, BING! speak what for me is a unknown language >As far as slang goes.. I can speak three different versions of slang >NE slang, African American, SE Hill Billy, take your pick. So you want to add slang support to wine? updated is not slang, whatever you may say >Just come for a visit :) I have decss on my site, I don't like the idea of ending up in a US prison (Any american wanting to violate the DMCA go here http://digilander.libero.it/winehqitalia/dvd.html ) Anyway, I have no problems with US english, so I don't see why you should have problems understanding UK english, and I don't see why we shouldn't have grammar in the wine docs.

1 0

adding structures to headers
by Geoff Thorpe Sept. 10, 2003

Sept. 10, 2003

Hi there, Quick licensing/copyright question before I submit something I regret: when adding missing functions and structure types to wine headers, to what extent can we copy-n-paste structure definitions from the documentation at msdn.microsoft.com web? IANAL. Cheers, Geoff -- Geoff Thorpe geoff(a)geoffthorpe.net http://www.geoffthorpe.net/

3 5

compile time
by Ivan Leo Murray-Smith Sept. 10, 2003

Sept. 10, 2003

>p.s. >For me (P-IV 1600MHZ) complete build compile takes 25 minutes. I've now >switched to ccache, hoping I can bring it down even lower. And my 1.4GHZ AMD Athlon XP takes 18:45, and some people still think intel can compete with AMD...

2 1

Re: FAQ: Update the ports section
by Ivan Leo Murray-Smith Sept. 10, 2003

Sept. 10, 2003

> Purely academic, I know, but m-w doesn't know "updated" as an adjective. > To the best of my knowledge, "the list is now updated" is slang. Am I > wrong here? >From the Cambridge Advanced Learner's Dictionary update verb [T] 1 to make something more modern or suitable for use now by adding new information or changing its design: an updated version of the software http://dictionary.cambridge.org/define.asp?key=87314&dict=CALD It definitely isn't slang.

6 7

Re: compile time
by Ivan Leo Murray-Smith Sept. 10, 2003

Sept. 10, 2003

> Without knowing the rest of the systems (RAM, HD speed, present libs, > compiler used, etc.) it's rather meaningless to compare compile times. 512MB ddr, gcc 3.3.1, all optional wine stuff compiled in, 7200rpms hd.

1 0

something I found that might help GDI hackers
by Jonathan Wilson Sept. 10, 2003

Sept. 10, 2003

struct GDIHandleBitFields { unsigned long Index:0:10; unsigned long Type:10:5; unsigned long AltType:15:2; unsigned long Stock:17:1; unsigned long Unique:18:8; }; This might help people trying to understand the inner workings of GDI... Its current as of windows XP SP1.

2 1

Re: FAQ: Update the ports section
by Ivan Leo Murray-Smith Sept. 10, 2003

Sept. 10, 2003

I happen to be from the UK, and can tell you that >The following lists the x86 operating systems supported by >the list is now updated >the list is now up to date are all correct.

2 1

Re: FAQ: Update the ports section
by Ivan Leo Murray-Smith Sept. 10, 2003

Sept. 10, 2003

You must send me some of the stuff you're smoking! "The list are now up to date" doesn't exist in english, you must choose "The lists are now up to date" for a plural "The list is now up to date" for a singular

1 0

Re: [Resend winegcc03] winewrap can handle the default output name
by Dimitrie O. Paun Sept. 10, 2003

Sept. 10, 2003

On Tue, 9 Sep 2003, Richard Cohen wrote: > Slightly different from last time. > > > Default name that mingw uses is a.exe > > This also stops winewrap from segfaulting when passed no arguments. > > Changelog > Handle default linker output name (a.exe) in winewrap instead of > winegcc I'm still not sure I like this one, as I said, a.out is a gccism, and should be handled in winegcc. winewrap does not have to be command line compatible to the GNU tool (as it currently stands), we can require an output name for it. -- Dimi.

3 4