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

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

Sept. 10, 2003

Francois Gouget wrote: >Changelog: > > >- The following will list the x86 operating systems supported by >+ The following lists the x86 operating systems supported by > > Should be. The following list are the x86 operating systems supported by Tom

7 15

Re: [DSHOW-08] Implementation of IMemAllocator and IMediaSample (REVISED2)
by Dimitrie O. Paun Sept. 10, 2003

Sept. 10, 2003

On September 9, 2003 07:37 pm, Robert Shearman wrote: > --- /dev/null Mon Jun 24 01:53:01 2002 > +++ wine/dlls/quartz/list.h Mon Sep 8 00:48:58 2003 The list.h stuff seems to be fairly popular, why not stick a copy in wine/list.h? -- Dimi.

2 1

Re: [winegcc08] Handle -L in a separate array
by Dimitrie O. Paun Sept. 10, 2003

Sept. 10, 2003

On Tue, 9 Sep 2003, Richard Cohen wrote: > ...rather than adding -L<libpath> to both the DLLs and static libraries > No functional changes. I'm not sure this is correct, as the order of -L and -l may be significant. That is to say, if I do -LdirA -la -LdirB -lb then the system will search for a only in A, not in B, which is not the case if I do: -LdirA -LdirB -la -lb -- Dimi.

2 1

Re: BuildCommDCBAndTimeouts patch
by Jakob Eriksson Sept. 10, 2003

Sept. 10, 2003

Could you also make test.c into a regression test for inclusion into Wine? That is almost more important than the actual patch to Wine - if we have the conformance test, it ensures changes to Wine in the future does not destroy functionality. regards, Jakob

4 3

Re: Resend: Shlwapi ordinal fixes (Dave Miller)
by Robert Shearman Sept. 10, 2003

Sept. 10, 2003

On Wednesday 10 September 2003 5:32 am, Dave Miller wrote: > > Remove about a dozen ordinals we have defined which do not seem to be > important. (They vary from one windows version to another) Alexandre, please don't apply. I am doing a big update on the ordinals of Shlwapi and will incorporate these changes into my patch. Rob

1 0

FAQ update
by Tom Sept. 10, 2003

Sept. 10, 2003

Hi, Thanks for the update.. I got occupied with something and it took me a little longer than I thought. But I have the sync of lostwages to docs faq in my tree. I will now rm -rf it Regards, Tom

6 28

Re: widl: oleidl.h problem
by Jon Griffiths Sept. 10, 2003

Sept. 10, 2003

Hi, <snip> >Can some of the widl gurus look at this one please? This is a known problem with widl, see http://www.winehq.org/hypermail/wine-devel/2003/03/0359.html. I sent a patch to fix this issue, but it wasn't the right fix and probably won't apply unmodified now. 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! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

Relocate error
by Fabian Cenedese Sept. 10, 2003

Sept. 10, 2003

Hi I worked with wine about six months ago. Except some minor errors my app worked quite good in wine. Then I didn't have time anymore. Now I tried again with the newest wine from cvs. But now I can't even start my app anymore. Wine gives me this error: err:virtual:map_image FATAL: Need to relocate module from addr 40000000, but there are no relocation records wine: could not load 'C:\IMD\Bin\Imd.exe' as Win32 binary I looked in the archives and the only messages concerning this error were at least two years old stating that this error has been fixed long ago. I didn't change this link address in my app (VC6), it has been there even before I started with wine at all. But when I change this address to say 0x48000000 then it works. So is there something else on this address? I know six months is a long time and a lot happened this year. But does anybody know if this is a real error? What could have introduced this behaviour as it worked a few months ago? Thanks Fabi

3 5

Word-splitting in the FAQ
by Francois Gouget Sept. 10, 2003

Sept. 10, 2003

Tom, you submitted a patch that splits many words in two. I assume that's because they're not in the dictionary but I'm not sure it's appropriate. Here are some examples: - Make sure you have all the VB runtime libraries installed. + Make sure you have all the VB run time libraries installed. - (using a DOS filename). + (using a DOS file name). - the UNIX kernel supports the DOS/MS Windows filesystem type). + the UNIX kernel supports the DOS/MS Windows file system type). And some I am absolutely sure are wrong: - ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs/</ulink> + ftp://metalab.unc.edu/pub/Linux/system/file systems/dosfs/</ulink> - when running an InstallShield 6 installer. + when running an Install shield 6 installer. - program work (there must be a downloadable version or demo for + program work (there must be a download able version or demo for Also I'm not sure why you changed the Lycos URL: - <ulink url="http://search.lycos.com/">Lycos</ulink>. Some of + <ulink url="http://www.compucan.com/Lycos.htm">lycos</ulink> Some of Actually I'm not sure why we have this link to Lycos at all. How does one find Wine using it? So I'm submitting a patch fixing the second type of changes directly to wine-patches. And here is a patch that reverts most of the word splitting. Maybe it goes too far. What do you think? Index: documentation/faq.sgml =================================================================== RCS file: /home/wine/wine/documentation/faq.sgml,v retrieving revision 1.21 diff -u -r1.21 faq.sgml --- documentation/faq.sgml 8 Sep 2003 19:38:45 -0000 1.21 +++ documentation/faq.sgml 9 Sep 2003 19:02:31 -0000 @@ -424,11 +424,11 @@ <ulink url="http://www.winehq.com/download.shtml">the Download page</ulink> for some of these choices), you can make sure that you are getting the latest version by watching the version numbers in the distribution - file name. For instance, the distribution released on August 13, 2003 + filename. For instance, the distribution released on August 13, 2003 was called Wine-20030813.tar.gz. Patch files are also available. If you are current to the previous version, you can download and apply just the current patch file rather than the entire new distribution. - The patch file names follow the same conventions as the monthly + The patch filenames follow the same conventions as the monthly distribution. <ulink url="http://www.winehq.org/site/cvs"> Read-only CVS</ulink> access is also available. </para> @@ -824,8 +838,8 @@ <answer> <para> Yes, but only if the operating system supports mounting those types - of drives. There is a Linux file system driver called dmsdos that + of drives. There is a Linux filesystem driver called dmsdos that will allow read/write access to Doublespaced and Drivespace 1.0 drives. More specifically, it supports mounting DOS 6.0 and 6.2 Doublespaced, DOS 6.22 Drivespaced, and Windows 95 Doublespaced @@ -859,13 +873,13 @@ <answer> <para> Many folks have successfully installed and run programs - in their UNIX file system without having a DOS partition or MS + in their UNIX filesystem without having a DOS partition or MS Windows. However, in many cases you need a directory and file infrastructure that is similar to an existing Windows installation. Some applications' installation programs want to distribute some of the package's files into the /windows and /windows/system directories in order to run, and unless these exist on your UNIX - file system, those programs will not install correctly and probably + filesystem, those programs will not install correctly and probably will not run well, if at all. Most packages will set that up for you as part of the install process. </para> @@ -905,7 +919,7 @@ machine. If you have DOS/MS Windows installed on your system, you can mount that partition at bootup by modifying the file <filename>/etc/fstab</filename> in your UNIX partition (assuming that - the UNIX kernel supports the DOS/MS Windows file system type). + the UNIX kernel supports the DOS/MS Windows filesystem type). </para> <para> If you edit this file by hand, it should contain something similar @@ -935,7 +949,7 @@ DLLs and APIs that are needed by these Windows applications. This means that Wine will not provide replacements for DLLs that are not shipped with Windows or are always shipped with Windows - application (e.g. the Visual Basic run time). This also + application (e.g. the Visual Basic runtime). This also means that implementing an API that no application ever uses is not a priority. Similarly, until there are applications out there that use the Win64 API, it will not be a priority. That being said, @@ -970,13 +984,13 @@ <question id="Will-I-install-on-any-UNIX-file-system"> <para> Will I be able to install MS Windows applications in any flavor of a - UNIX file system? + UNIX filesystem? </para> </question> <answer> <para> - Wine is written to be file system independent, so MS Windows - applications will install and run under virtually any file system + Wine is written to be filesystem independent, so MS Windows + applications will install and run under virtually any filesystem supported by your brand of UNIX. </para> </answer> @@ -1080,12 +1094,12 @@ <para> It should also be available from any other site that mirrors ibiblio.org. For more download locations, see - <ulink url="http://www.compucan.com/Lycos.htm">lycos</ulink> Some of + <ulink url="http://search.lycos.com/">Lycos</ulink>. Some of these ftp sites may archive previous versions of Wine as well as the current one. To determine which is the latest one, look at the - distribution file name, which will take the form + distribution filename, which will take the form Wine-YYYYMMDD.tar.gz. Simply replace YYYYMMDD in the distribution - file name with the numbers for year, month and date, respectively. + filename with the numbers for year, month and date, respectively. The latest one is the one to get. </para> <para> @@ -1313,7 +1327,7 @@ </question> <answer> <para> - Make sure you have all the VB run time libraries installed. You may + Make sure you have all the VB runtime libraries installed. You may need to use the native DLL vbrun60.dll. You can get some from dll-files.com. </para> </answer> @@ -1347,7 +1361,7 @@ </question> <answer> <para> - Try to re login into bash. That might fix it. + Try to logout and login again into bash. That might fix it. </para> <para> If it doesn't, then make sure the wine binary is in your @@ -1405,14 +1419,14 @@ Make sure that you specify the exact path when using the powerful <command>rm -fR</command> command. If you are afraid that you might delete something important, or might otherwise delete other files - within your file system, <command>cd</command> into each Wine + within your filesystem, <command>cd</command> into each Wine sub directory singly and delete the files found there manually, one file or directory at a time. </para> <para> Neither the Wine developers and programmers, nor the Wine FAQ author/maintainer, can be held responsible for your deleting any - files in your own file system. + files in your own filesystem. </para> </answer> </qandaentry> @@ -1427,7 +1441,7 @@ <answer> <para> When invoking Wine, you must specify the entire path to the - executable, or by file name only. For example to run Windows' + executable, or by filename only. For example to run Windows' solitaire, type any of the following: </para> <itemizedlist> @@ -1440,19 +1454,19 @@ <listitem> <para> <command>wine c:\\windows\\sol.exe</command> - (using a DOS file name). + (using a DOS filename). </para> </listitem> <listitem> <para> <command>wine /usr/windows/sol.exe</command> - (using a UNIX file name). + (using a UNIX filename). </para> </listitem> <listitem> <para> <command>wine "c:\windows\sol.exe"</command> - (using quoted DOS file name). + (using quoted DOS filename). </para> </listitem> </itemizedlist> -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Stolen from an Internet user: "f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng !"

2 1

Latest CVS doesnt compile
by Sylvain Petreolle Sept. 10, 2003

Sept. 10, 2003

After updating to the latest CVS via cvs update (the only patch involved was the header dependancies fix), wine doesnt compile.I tried to rerun './configure' but there is no change.What I get is : (make depend runs fine.)[syl(a)snoop tests]$ LANG=en_US makegcc -c -I. -I. -I../../../include -I../../../include -D_REENTRANT -fPIC -Wall -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o testlist.o testlist.cIn file included from testlist.c:6:../../../include/winbase.h:1323: parse error before "va_list"../../../include/winbase.h:1324: parse error before "va_list"make: *** [testlist.o] Error 1[syl(a)snoop tests]$Running with :RH 9 updated, gcc 3.2.2. Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net) ICQ #170597259 Say NO to software patents Dites NON aux brevets logiciels "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". --------------------------------- Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Testez le nouveau Yahoo! Mail

8 10

Re: [winegcc06] Delayed import
by Dimitrie O. Paun Sept. 10, 2003

Sept. 10, 2003

On August 13, 2003 10:08 pm, Richard Cohen wrote: > --- tools.5/winegcc.c 2003-08-14 00:55:07.000000000 +0100 > +++ tools/winegcc.c 2003-08-14 01:21:41.000000000 +0100 > @@ -193,7 +193,8 @@ > } > argv[j] = 0; > break; > - case 'l': > + case 'l': /* import/static library */ > + case 'd': /* delayed import library */ This is not cool -- winegcc is supposed to be command line compatible with mingw-gcc, and -d conflicts with gcc's -d: -dletters Says to make debugging dumps during compilation at times specified by letters. This is used for debugging the compiler. The file names for most of the dumps are made by appending a pass number and a word to the dumpname. dumpname is generated from the name of the output file, if explicitly specified and it is not an executable, otherwise it is the basename of the source file. In both cases any suffix is removed (e.g. foo.00.rtl or foo.01.sibling). Here are the possible letters for use in letters, and their meanings: ..... Having the option in winewrap is OK, there we control the options. If this feature is useful in Windows, gcc must/will support it, right? If they don't already, we better get in touch with them so we end up with the same option name/syntax. -- Dimi.

2 6

Re: for Red Hat packager
by Ivan Leo Murray-Smith Sept. 10, 2003

Sept. 10, 2003

>The latest Wine >RPMs are compiled without BiDi support the Red Hat rpms may be, but I can assure you that your help to get bidi into the mdk rpms wasn't invane.

7 14

Setupapi include fixes and a few more MS_VC problems
by Steven Edwards Sept. 10, 2003

Sept. 10, 2003

This first patch should not break the Unix build. This patch fixes building most of the source files on MS_VC. I tested building under Mingw and we can still build and link but one of you guys on *nix may want to double check. After this patch you will still get the following errors with MS_VC and the PSDK headers. I figured I would wait and ask for comments on how to move forward to fix the following problems as there has been a little work in setupapi recently. Thanks Steven Changelog: Setupapi porting fixes --------------------Configuration: setupapi - Win32-------------------- Compiling... devinst.c F:\src\wine-dev\wine\dlls\setupapi\devinst.c(41) : error C2146: syntax error : missing ')' before identifier 'DeviceInterfaceDetailData' F:\src\wine-dev\wine\dlls\setupapi\devinst.c(41) : error C2081: 'PSP_DEVICE_INTERFACE_DETAIL_DATAA' : name in formal parameter list illegal F:\src\wine-dev\wine\dlls\setupapi\devinst.c(41) : error C2061: syntax error : identifier 'DeviceInterfaceDetailData' F:\src\wine-dev\wine\dlls\setupapi\devinst.c(41) : error C2059: syntax error : ';' F:\src\wine-dev\wine\dlls\setupapi\devinst.c(41) : error C2059: syntax error : ',' F:\src\wine-dev\wine\dlls\setupapi\devinst.c(44) : error C2059: syntax error : ')' F:\src\wine-dev\wine\dlls\setupapi\devinst.c(56) : error C2146: syntax error : missing ')' before identifier 'DeviceInterfaceDetailData' F:\src\wine-dev\wine\dlls\setupapi\devinst.c(56) : error C2081: 'PSP_DEVICE_INTERFACE_DETAIL_DATAW' : name in formal parameter list illegal F:\src\wine-dev\wine\dlls\setupapi\devinst.c(56) : error C2061: syntax error : identifier 'DeviceInterfaceDetailData' F:\src\wine-dev\wine\dlls\setupapi\devinst.c(56) : error C2059: syntax error : ';' F:\src\wine-dev\wine\dlls\setupapi\devinst.c(56) : error C2059: syntax error : ',' F:\src\wine-dev\wine\dlls\setupapi\devinst.c(59) : error C2059: syntax error : ')' setupcab.c F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(257) : error C2065: 'FILE_IN_CABINET_INFOA' : undeclared identifier F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(257) : error C2146: syntax error : missing ';' before identifier 'fici' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(257) : error C2065: 'fici' : undeclared identifier F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(258) : error C2275: 'PSC_HSC_A' : illegal use of this type as an expression F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(64) : see declaration of 'PSC_HSC_A' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(258) : error C2146: syntax error : missing ';' before identifier 'phsc' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(258) : error C2065: 'phsc' : undeclared identifier F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(259) : error C2065: 'CABINET_INFOA' : undeclared identifier F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(259) : error C2146: syntax error : missing ';' before identifier 'ci' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(259) : error C2065: 'ci' : undeclared identifier F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(260) : error C2275: 'FILEPATHS_A' : illegal use of this type as an expression C:\Program Files\Microsoft SDK\include\setupapi.h(439) : see declaration of 'FILEPATHS_A' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(260) : error C2146: syntax error : missing ';' before identifier 'fp' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(260) : error C2065: 'fp' : undeclared identifier F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(261) : error C2275: 'UINT' : illegal use of this type as an expression C:\Program Files\Microsoft SDK\include\windef.h(162) : see declaration of 'UINT' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(261) : error C2146: syntax error : missing ';' before identifier 'err' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(261) : error C2065: 'err' : undeclared identifier F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(263) : error C2275: 'CHAR' : illegal use of this type as an expression C:\Program Files\Microsoft SDK\include\winnt.h(265) : see declaration of 'CHAR' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(263) : error C2146: syntax error : missing ';' before identifier 'mysterio' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(263) : error C2065: 'mysterio' : undeclared identifier F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(263) : error C2109: subscript requires array or pointer type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(265) : error C2109: subscript requires array or pointer type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(265) : error C2102: '&' requires l-value F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(265) : error C2198: 'memset' : too few actual parameters F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(270) : warning C4047: '=' : 'int ' differs in levels of indirection from 'struct SC_HSC_A *' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(285) : error C2224: left of '.CabinetFile' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(285) : error C2223: left of '->most_recent_cabinet_name' must point to struct/union F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(286) : error C2224: left of '.CabinetPath' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(287) : error C2224: left of '.DiskName' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(288) : error C2224: left of '.SetId' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(289) : error C2224: left of '.CabinetNumber' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(290) : error C2223: left of '->msghandler' must point to struct/union F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(290) : error C2223: left of '->context' must point to struct/union F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(303) : error C2224: left of '.NameInCabinet' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(304) : error C2224: left of '.FileSize' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(305) : error C2224: left of '.Win32Error' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(306) : error C2224: left of '.DosDate' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(307) : error C2224: left of '.DosTime' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(308) : error C2224: left of '.DosAttribs' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(309) : error C2224: left of '.FullTargetName' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(309) : error C2198: 'memset' : too few actual parameters F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(310) : error C2223: left of '->msghandler' must point to struct/union F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(310) : error C2223: left of '->context' must point to struct/union F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(313) : error C2224: left of '.FullTargetName' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(313) : error C2198: 'debugstr_a' : too few actual parameters F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(314) : error C2224: left of '.FullTargetName' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(319) : error C2224: left of '.FullTargetName' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(319) : warning C4047: 'function' : 'char *' differs in levels of indirection from 'const int ' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(319) : warning C4024: 'sc_cb_open' : different types for formal and actual parameter 1 F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(319) : error C2198: 'sc_cb_open' : too few actual parameters F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(329) : error C2224: left of '.Source' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(329) : error C2223: left of '->most_recent_cabinet_name' must point to struct/union F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(330) : error C2224: left of '.Target' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(331) : error C2224: left of '.Win32Error' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(332) : error C2224: left of '.Flags' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(335) : error C2223: left of '->msghandler' must point to struct/union F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(335) : error C2223: left of '->context' must point to struct/union F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(350) : error C2224: left of '.CabinetFile' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(351) : error C2224: left of '.CabinetPath' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(352) : error C2224: left of '.DiskName' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(353) : error C2224: left of '.SetId' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(354) : error C2224: left of '.CabinetNumber' must have struct/union type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(356) : error C2223: left of '->most_recent_cabinet_name' must point to struct/union F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(356) : error C2198: 'strcpy' : too few actual parameters F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(357) : error C2223: left of '->msghandler' must point to struct/union F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(357) : error C2223: left of '->context' must point to struct/union F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(357) : error C2109: subscript requires array or pointer type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(357) : error C2102: '&' requires l-value F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(362) : error C2109: subscript requires array or pointer type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(364) : error C2109: subscript requires array or pointer type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(364) : error C2106: '=' : left operand must be l-value F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(365) : error C2109: subscript requires array or pointer type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(365) : error C2102: '&' requires l-value F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(365) : warning C4047: 'function' : 'const char *' differs in levels of indirection from 'const int ' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(365) : warning C4024: 'strncpy' : different types for formal and actual parameter 2 F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(365) : error C2198: 'strncpy' : too few actual parameters F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(366) : error C2109: subscript requires array or pointer type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(366) : error C2106: '=' : left operand must be l-value F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(378) : error C2065: 'FILE_IN_CABINET_INFOW' : undeclared identifier F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(378) : error C2146: syntax error : missing ';' before identifier 'fici' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(379) : error C2275: 'PSC_HSC_W' : illegal use of this type as an expression F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(73) : see declaration of 'PSC_HSC_W' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(379) : error C2146: syntax error : missing ';' before identifier 'phsc' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(380) : error C2065: 'CABINET_INFOW' : undeclared identifier F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(380) : error C2146: syntax error : missing ';' before identifier 'ci' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(381) : error C2275: 'FILEPATHS_W' : illegal use of this type as an expression C:\Program Files\Microsoft SDK\include\setupapi.h(446) : see declaration of 'FILEPATHS_W' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(381) : error C2146: syntax error : missing ';' before identifier 'fp' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(382) : error C2275: 'UINT' : illegal use of this type as an expression C:\Program Files\Microsoft SDK\include\windef.h(162) : see declaration of 'UINT' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(382) : error C2146: syntax error : missing ';' before identifier 'err' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(383) : error C2143: syntax error : missing ';' before 'type' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(385) : error C2275: 'WCHAR' : illegal use of this type as an expression C:\Program Files\Microsoft SDK\include\winnt.h(275) : see declaration of 'WCHAR' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(385) : error C2146: syntax error : missing ';' before identifier 'mysterio' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(385) : error C2109: subscript requires array or pointer type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(386) : error C2275: 'WCHAR' : illegal use of this type as an expression C:\Program Files\Microsoft SDK\include\winnt.h(275) : see declaration of 'WCHAR' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(386) : error C2146: syntax error : missing ';' before identifier 'buf' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(386) : error C2065: 'buf' : undeclared identifier F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(386) : error C2109: subscript requires array or pointer type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(386) : error C2065: 'buf2' : undeclared identifier F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(386) : error C2109: subscript requires array or pointer type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(387) : error C2275: 'CHAR' : illegal use of this type as an expression C:\Program Files\Microsoft SDK\include\winnt.h(265) : see declaration of 'CHAR' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(387) : error C2146: syntax error : missing ';' before identifier 'charbuf' F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(387) : error C2065: 'charbuf' : undeclared identifier F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(387) : error C2109: subscript requires array or pointer type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(389) : error C2109: subscript requires array or pointer type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(389) : error C2102: '&' requires l-value F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(389) : error C2198: 'memset' : too few actual parameters F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(390) : error C2109: subscript requires array or pointer type F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(390) : error C2102: '&' requires l-value F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(390) : error C2198: 'memset' : too few actual parameters F:\src\wine-dev\wine\dlls\setupapi\setupcab.c(390) : fatal error C1003: error count exceeds 100; stopping compilation Generating Code... Error executing cl.exe. setupapi.dll - 114 error(s), 5 warning(s) WINE_DEFAULT_DEBUG_CHANNEL(setupapi);

1 0

different approach to resolution switching
by Rok Mandeljc Sept. 10, 2003

Sept. 10, 2003

I've been thinking recently about resolution changes in wine/X. As I understand, this now works with UseXVidMode enabled, but I sometimes find it ugly; I run X at 1280x1024 and when I run game in 640x480 (fullscreen), X switches resolution. But as mouse cursor can escape from 640x480 "box", I can see the rest of my desktop (enlarged). I believe this is not how Win do it. Even worse is when you run a game in desktop mode (let's say 1024x768) and game uses different resolutions (e.g. game: 1024x768, intro & main menu: 640x480). So I've been wondering if you guys have already considered use of scaler. It would probably (in my opinion) look much nicer than current res switching and it would fill those black places in desktop mode. -- Rok Mandeljc <rok.mandeljc(a)gimb.org> "Hold your position! Leave doubt for the dying!" -- Tahngarth of the Weatherlight

4 3

Re: Use a css file for the doc
by Dimitrie O. Paun Sept. 9, 2003

Sept. 9, 2003

On Tue, 9 Sep 2003, Francois Gouget wrote: > * documentation/Makefile.in, > documentation/default.dsl, > documentation/winedoc.css > > Don't hardcode the look and feel in default.css. Use a css file > instead. For that, we should just completely remove documentation/default.dsl and use the site-wide one. -- Dimi.

2 6

Re: [DSHOW-08] Implementation of IMemAllocator and IMediaSample (REVISED)
by Alexandre Julliard Sept. 9, 2003

Sept. 9, 2003

Robert Shearman <R.J.Shearman(a)warwick.ac.uk> writes: > + struct list * pFreeList; > + struct list * pUsedList; You are not using the list functions the right way; these should be a struct list, not a struct list *. The rest of the code then gets a lot cleaner, you don't need any special cases for empty lists etc. -- Alexandre Julliard julliard(a)winehq.com

2 1

RE: Using limits.h
by Robert Shearman Sept. 9, 2003

Sept. 9, 2003

> -----Original Message----- > From: Alexandre Julliard [mailto:julliard(a)winehq.com] > Sent: 09 September 2003 03:13 > To: Robert Shearman > Cc: wine-devel(a)winehq.com > Subject: Re: Using limits.h > > "Robert Shearman" <R.J.Shearman(a)warwick.ac.uk> writes: > > > I'm trying to use the default limits.h installed on my Debian > Woody system, > > so that I can use either LLONG_MAX or LONG_LONG_MAX in Wine. Does anyone > > know of anything special I have to define so that these are > defined? I have > > tried __USE_ISOC99, but no joy. > > If you have to do some special magic to get them, it's a clear sign > that these symbols are not portable and should not be used. Should I just use the constant that LONG_LONG_MAX equates to and put this into the source file then? Is this portable (i.e. is long long 64bits on all platforms) ? On another note, how would you feel to adding a new debugging function (say debugstr_lld) to print out the decimal value of long longs? Rob

3 4

winbase.h: STILL_ACTIVE
by Dimitrie O. Paun Sept. 9, 2003

Sept. 9, 2003

We have the following definition: /usr/local/include/wine/windows/winbase.h:#define STILL_ACTIVE STATUS_PENDING This fails to compile under visual-mingw. Is this how it is defined under the MS headers? Does this mean that any app using STILL_ACTIVE must also include ntstatus.h? -- Dimi.

2 1

Re: lostwages/. .htaccess
by Dimitrie O. Paun Sept. 9, 2003

Sept. 9, 2003

On Tue, 9 Sep 2003, Jeremy Newman wrote: > Log message: > regex was causing hypermail archives to 404 Do you know why? -- Dimi.

2 1

Re: winedefault.reg
by David.Goodenough＠DGA.co.uk Sept. 9, 2003

Sept. 9, 2003

A further problem with the Debian install is that winedefault.reg is delivered packed (.gz). Perhaps as a further addition to regedit (or what ever command line version is to be used) should be to unpack it as well as read it - otherwise please can the Debian version be shipped ungziped. David Paul McNett <p(a)ulmcnett.com> To: wine-devel(a)winehq.org Sent by: cc: wine-devel-admin@ Subject: Re: winedefault.reg winehq.org 08/09/2003 14:34 Please respond to p Ivan Leo Murray-Smith writes: > Some people on wine-users are complaining that regedit > winedefault.reg doesn' t always work correctly, somebody > posted this solution > http://www.winehq.org/hypermail/wine-users/2003/09/0062.html > but it would be a very nice thing if regedit winedefault.reg > exited with no output and just worked like it has always done > with the command line version. Yes I just realized, only last night, that my latest Wine install didn't include the winedefault.reg, even though I always install Wine with ./tools/wineinstall, and it is advertised that it will install the winedefault.reg. Instead what happens is the new graphical regedit is displayed. -- Paul McNett

1 0

Re: Request for help - byacc problem building on Mandrake 9.1
by Dimitrie O. Paun Sept. 9, 2003

Sept. 9, 2003

On Tue, 9 Sep 2003, Bill Medland wrote: > > I have just installed Mandrake 9.1 and tried to build Wine. I am getting an > error when byacc runs in dlls/msi > > byacc: e - line 73 of "./sql.y", syntax error > > %pure-parser > ^ > > Any idea what I am doing wrong or what I have failed to do? What yacc/bison are you using? It seems to be an old one... -- Dimi.

2 1

widl: oleidl.h problem
by Dimitrie O. Paun Sept. 9, 2003

Sept. 9, 2003

Folks, When compiling visual-mingw under Winelib, I get the following error: In file included from /usr/local/include/wine/windows/ole2.h:27, from /usr/local/include/wine/windows/shlobj.h:22, from ../include/browsdlg.h:19, from browsdlg.cpp:14: /usr/local/include/wine/windows/oleidl.h:294: ISO C++ forbids defining types within in a parameter list Error: g++ failed. The offending code is: #if defined(__cplusplus) && !defined(CINTERFACE) struct IOleInPlaceActiveObject : public IOleWindow { virtual HRESULT STDMETHODCALLTYPE TranslateAccelerator( struct tagMSG { HWND hwnd; UINT message; WPARAM wParam; LPARAM lParam; DWORD time; POINT pt; }* lpmsg) = 0; ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ virtual HRESULT STDMETHODCALLTYPE OnFrameWindowActivate( BOOL fActivate) = 0; virtual HRESULT STDMETHODCALLTYPE OnDocWindowActivate( BOOL fActivate) = 0; virtual HRESULT STDMETHODCALLTYPE ResizeBorder( LPCRECT prcBorder, IOleInPlaceUIWindow* pUIWindow, BOOL fFrameWindow) = 0; virtual HRESULT STDMETHODCALLTYPE EnableModeless( BOOL fEnable) = 0; }; #else Can some of the widl gurus look at this one please? -- Dimi.

1 0

for Red Hat packager
by Ivan Leo Murray-Smith Sept. 9, 2003

Sept. 9, 2003

Could the Red Hat packager please take care of this http://www.winehq.org/hypermail/wine-users/2003/09/0081.html I don't know if it's a rpm packaging error or a problem with the users system setup, but I suppose the creator of the rpm can solve the issue quite easily.

3 2

More stuff about the headers
by Steven Edwards Sept. 9, 2003

Sept. 9, 2003

Hello, First thanks Dimi and Alexandre for the header fixes. I have been outa town till lastnight so I have not had a chance to do much testing of the MS_VC build yet. I will start working on this soon as I want to get these dlls imported in to ReactOS. First thing is first. Whats up with the *_must_be_suffixed_with_W_or_A_in_this_context error? To build comctl32 with the Mingw/PSDK headers we need to do something about this. Almost every file is expecting IDC_ARROWA and the PSDK/w32api dont define a A/W suffix. I think once we fix this comctl32 should build out of the box with the PSDK or w32api. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

4 9

RE: MSVCP60.DLL missing, please help
by Rolf Kalbermatter Sept. 9, 2003

Sept. 9, 2003

eric lin <fsshl(a)luxmail.com> wrote: > Thanks your reply and point out. I will try to search web somewhere >to get it for running my.exe file by wine. (or point me some place >in web I can get it) > > or anyone have other alternative, please inform me. Well if you have written that program and compiled it using a legal version of Visual C, you are allowed to redistribute that DLL with your app. Otherwise most modern MS apps, including their freebies, will probably install it anyhow. Rolf Kalbermatter CIT Engineering Nederland BV tel: +31 (070) 415 9190 Treubstraat 7H fax: +31 (070) 415 9191 2288 EG Rijswijk http://www.citengineering.com Netherlands mailto:rolf.kalbermatter(a)citeng.com

1 0