wine-devel

wine-devel@winehq.org

10 participants
84459 discussions

Re: vsnprintf: glibc and win32 not compatible
by Jesse Allen 09 Mar '04

09 Mar '04

On Tue, Mar 09, 2004 at 01:45:59PM +0800, Jonathan Wilson wrote: > >Discovered an issue with null pointer passed for %s (Warcraft III likes to > >do that it seems). I handle it by printing "(null)". Other than that, it > >will > Have you made it do something usefull if the user passes a null for a wide > char string? (i.e. passes %S and a null string?) > (A reply to the list this time) OK, I have added %S and %C. They pretty much copy %s and %c. I have started to read through dlls/user/wsprintf.c to show me how it's really done. Though, it is not finished. So in the case if something asks for %S and gives a null pointer, it will do the same as %s and print "(null)". glibc does the same thing for %s and %ls. If anyone would like try the updated version they can download snprintf.c and snprintf.h, renamed since it implements snprintf now, from ftp://narf.dnip.net/ and copy it into dlls/msvcrt. Update Makefile.in and msvcrt.spec and it should work after that. But it it still very experimental and there is more to do. Jesse

1 0

Re: Contribution offer: Localization work
by Ivan Leo Murray-Smith 09 Mar '04

09 Mar '04

> Important: I did not want to change the sense of the original file. > Personally I think even bugs should be persistant between different > translations. ;-) Otherwise they would drift away from each other too > much (my opinion). On the other hand, I had to change some sections > slightly, as they would not make too much sense in german, could be > miss-interpreted or simply would sound ugly if translated very close to > the original. I don't know how the other translators handle this issue. As any latin student knows, you simply can't translate word by word, also you mustn't make a translation that sounds ugly. The important thing is that the file look as if it was written in the language you're translating to, not adapted from another one. Also, in computers it's important to use the same words that are already being used. For example, the italian translation of "Save file as" is "Salva file con nome" that literally means "Save the file with a name", so you can't translate literally, you have to use what is usually used for that functionality in other programs. Just go on as you have up to now. If you think something is wrong, send a patch that updates both the original and the translation. > If there is a translated Readme shouldn't there also be a translated licence > file? I'm sure there is already one translated available from GNU.org. Then > this should say LIZENZ instead of LICENSE. The GPL is licensed only for distribution without modification, you can't touch the GPL or the license information in any way shape or from. What you can do is add the translations released by the FSF, as long as you specify that the legally valid version is the english one.

1 0

unsubscribe banana67
by Andrew de Quincey 09 Mar '04

09 Mar '04

2 1

Re: Implement Drag List Control
by Dimitrie O. Paun 09 Mar '04

09 Mar '04

On March 9, 2004 2:20 pm, Robert Shearman wrote: > This patch adds full support for drag list common controls. There are no > known bugs, so as far as I am concerned this is 100% complete compared > to ComCtl32 v5.81 and probably v6.0 too. Nice! Now, to keep track of these things, I've added the following note to each of the controls that I have audited/fixed: * NOTE * * This code was audited for completeness against the documented features * of Comctl32.dll version 6.0 on Sep. 9, 2002, by Dimitrie O. Paun. * * Unless otherwise noted, we believe this code to be complete, as per * the specification mentioned above. * If you discover missing features, or bugs, please note them below. It would be nice to add something like this to the drag control as well (also, now that you have it fresh in your mind, maybe you can audit it against v6.0, as this is the version that I used for other controls). Take a look at dlls/comctl32/updown.c, dlls/comctl32/comboex.c, etc. for examples. -- Dimi.

1 0

Re: Wine as shared library patch
by Peter Dennis Bartok 09 Mar '04

09 Mar '04

Alexandre, et. al, Our WinMain doesn't get called because our patch prevents it. If it were to get called, we'd be on a different (Wine-created) stack, with all kinds of things that are hard to undo, like the exception handling, etc. The goal of my patch was to have minimal impact on Wine, and allow the *same* wine code/binaries to be used for regular use as well as shared library, so any future Wine version you create will automatically also support shared library use. I modeled the global __wine_shared_lib variable after the __wine_main_argX globals you introduced last year, assuming that following that style would create the least resistance of getting my patch accepted. Having Wine set up the TEB and stack environment and actually call our WinMain and us then trying to 'undo' that in WinMain creates potential for future breakage of our library, in case you change something related to the TEB & stack. Having a variable in kernel that prevents creation of these, on the other hand, is easy to maintain, and really has no impact on performance or coding. I will be happy to implement any suggestions you may have on how to solve it another way in a single codebase that doesn't intruce the potential of breaking it in the future. I may very well have overlooked something. Regards, Peter -----Original Message----- From: "Alexandre Julliard" <julliard(a)winehq.org> To: "Miguel de Icaza" <miguel(a)ximian.com> Cc: "Peter Dennis Bartok" <peter(a)novonyx.com>; "Robert Shearman" <R.J.Shearman(a)warwick.ac.uk>; <wine-devel(a)winehq.org> Date: 07 March, 2004 17:37 Subject: Re: Wine as shared library patch >Miguel de Icaza <miguel(a)ximian.com> writes: > >> Well, the issue is that our WinMain is never called, and we would >> rather not depend on this in our patch, but instead get the small >> global that says `Hey Wine, just return'. > >The global variable thing is ugly; we could export a different entry >point instead, but I'm not sure it's really necessary. Why doesn't >your WinMain get called? > >-- >Alexandre Julliard >julliard(a)winehq.org > > >

6 12

statvfs breakage
by Gerald Pfeifer 09 Mar '04

09 Mar '04

I'm afraid the following change date: 2004/03/05 21:03:46; author: julliard; state: Exp; Use statvfs instead of statfs, and provide a default implementation in libwine_port if necessary. is not portable, as seen on FreeBSD 4.8: acrux[71]:/sw/test/wine/libs/port% make /sw/gcc-3.3.2/bin/gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o statvfs.o statvfs.c statvfs.c: In function `statvfs': statvfs.c:60: error: structure has no member named `f_namelen' Would you mind adding an autoconf test for that? (I saw that there are already a couple of those for statvfs.) Gerald -- Gerald Pfeifer (Jerry) gerald(a)pfeifer.com http://www.pfeifer.com/gerald/

1 1

Re: Warn If GetProcAddress Fails
by Kevin Koltzau 09 Mar '04

09 Mar '04

Many apps dynamically bind to entry points to determine if features in Windows are available as well, This may cause quite a few apps to report huge numbers of warnings when there is actually nothing wrong On Monday 08 March 2004 08:44 pm, Robert Shearman wrote: > Many applications dynamically bind to entry points and can fail in > strange ways if they are not found. This patch enables users to see any > failing GetProcAddress calls that could be responsible for bad > behaviour.

2 1

vsnprintf: glibc and win32 not compatible
by Jesse Allen 09 Mar '04

09 Mar '04

Hi, Here I have filed a bug on vsnprintf: http://bugs.winehq.org/show_bug.cgi?id=2075 Basically it says, without repeating, that vsnprintf called from glibc is not quite a suitable replacement for an actual msvcrt vsnprintf. An example is given to highlight a specific issue. I have a question on how should one approach fixing this? I have thought of two different ways: 1) Create our own vsnprintf version from scratch (fairly difficult) or 2) Create a wrapper for glibc's vsnprintf that translates win32ish format statements into a glibc friendly one. (not too bad and smaller patch) We could later move in a better or complete version to improve performance. The issue intrigues me, and I find that it should be resolved at some point. I'd like to get on the right path, so I'd at least start on something that will later be accepted. Thanks, Jesse

7 9

Cygwin under Wine
by Erik de Castro Lopo 08 Mar '04

08 Mar '04

Hi all, I'm interested in running Cygwin under Wine. When trying to run the cygwin bash.exe I get the following: fixme:console:SetConsoleCtrlHandler (0x61025d10,0) - no error checking or testing yet fixme:console:SetConsoleCtrlHandler (0x61025d10,1) - no error checking or testing yet fixme:ntdll:NtQueryInformationToken (0x60,5,0x6167010c,44,0x4078ef5c): stub fixme:ntdll:NtQueryInformationToken (0x60,1,0x616700a4,44,0x4078ef5c): stub fixme:advapi:SetTokenInformation (0x60, TokenOwner, 0x616700a4, 44): stub fixme:ntdll:NtQueryInformationToken (0x60,6,0x4078ef68,3076,0x4078ef5c): stub fixme:ntdll:NtQueryObject Unsupported information class 1 fixme:ntdll:NtQueryObject Unsupported information class 1 fixme:psapi:GetProcessMemoryInfo (hProcess=0x30, 0x4078ecb0, 40): stub I've tried hacking the Wine version of GetProcessMemoryInfo and I've had a look at the Cygwin sources to see what they are actually doing with this function. Unfortunately, I am still at a loss as to whay Cygwin expects. Anybody got any ideas on how to fix this? Cheers, Erik -- +-----------------------------------------------------------+ Erik de Castro Lopo nospam(a)mega-nerd.com (Yes it's valid) +-----------------------------------------------------------+ Linux: Because rebooting is for adding new hardware

1 0

Re: Contribution offer: Localization work
by Ivan Leo Murray-Smith 08 Mar '04

08 Mar '04

Look at the programs directory, most programs can be translated. You're usually looking for a De.rc file, if it's missing, make a second copy of the En.rc file, and call it De.rc. Now translate the strings in the file. You then have to edit the header file, this may be another rc file. In can case you can find the file by running grep En.rc * in the programs directory. Open the file, and add #include "De.rc" in alphabetical order in the list of language rc files. Once you've done this, make a patch, so your work can be easily applied to the wine source tree, a howto is at http://www.winehq.com/site/sending_patches. Also note that quite a few dlls need translating too. The file may not always be En.rc, for example in dlls/commdlg it's called cdlg_En.rc Finally, one important thing is keeping the translations up to date, so you should update the translation every time there is a change in the english resource file. Don't forget to check that the existing translations are up to date and correct. Once you've done a patch, send it, in the email body or as an attachment, to wine-patches(a)winehq.com This should give you plenty of work for now :-) Ivan.

3 2

Re: _ftime patch
by Hans Leidekker 08 Mar '04

08 Mar '04

On Monday 08 March 2004 07:56, Johannes Gajdosik wrote: > I found that the _ftime-function only returns seconds, not milliseconds. > Therefore I would like to send you a patch that uses gettimeofday(). Your efforts are appreciated but an implementation that uses Win32 API's would be better since that would make msvcrt (and thus Wine) more portable. Right now msvcrt uses only two unix API's, times() and localtime(), and I was planning to get rid of those in order to make it build on MinGW. -Hans

2 1

RtlGetDaclSecurityDescriptor crash on NULL pointer
by Bobby Bingham 08 Mar '04

08 Mar '04

Installing winamp5 with winver=winxp reveals that the wma installer calls GetSecurityDescriptorDacl with pSecurityDescriptor == NULL, which then calls RtlGetDaclSecurityDescriptor, which immediately dereferences it and crashes. Reading MSDN indicates that pSecurityDescriptor may be NULL, but I don't know the first thing about NT security descriptors, and so I'm not sure what the right way to handle it is. But I thought I'd at least point it out so someone who does know could take a look. -- Bobby Bingham

1 0

ccache gives winebuild errors?
by Rein Klazes 08 Mar '04

08 Mar '04

Hallo, Since a couple of days make fails without giving much reason why: | make[3]: Entering directory `/usr/home/projects/wine/mywine/dlls/ddraw/tests' | WINEBUILD=../../../tools/winebuild/winebuild ../../../tools/winegcc/winegcc -mconsole ddrawmodes.o testlist.o -o ddraw_test.exe.so -L../../../libs/port -lwine_port -L../../../dlls -L../../../libs -lddraw -luser32 -lgdi32 -lkernel32 -lm | Error: ccache gcc failed. | make[3]: *** [ddraw_test.exe.so] Error 2 | make[3]: Leaving directory `/usr/home/projects/wine/mywine/dlls/ddraw/tests' | make[2]: *** [tests] Error 2 | make[2]: Leaving directory `/usr/home/projects/wine/mywine/dlls/ddraw' | make[1]: *** [ddraw] Error 2 | make[1]: Leaving directory `/usr/home/projects/wine/mywine/dlls' | make: *** [dlls] Error 2 This is after a "make clean". Wine is configured to use ccache by setting CC="ccache gcc" before the ./configure && make depend && make. After another make clean and setting CC=gcc, the make succeeds. Any idea? Rein. -- Rein Klazes rklazes(a)xs4all.nl

4 6

RE: Wine as shared library patch
by Robert Shearman 08 Mar '04

08 Mar '04

Peter Dennis Bartok wrote: > This patch allows to use Wine as a shared library. It will allow the > Mono project to use Wine as the backend for it's System.Windows.Forms > implementation. It looks as though Alexandre has done a good job with kernel32 and ntdll since the last time using Wine with Mono was mentioned on this list. > ChangeLog: > * Alters initialization code to return control to caller instead of > executing application if __wine_shared_lib flag is set. Perhaps this could be changed to a static variable in process.c > * Adds winelib executable (wine-sharedlib) that a consumer can use > to initialize Wine as a shared library, to load Wine DLLs and to import > functions from DLLs. wine-sharedlib doesn't look very clean at the moment. Tabs are inconsistent and you forgot to change MonoWineInit to SharedWineInit in one of the comments. Why do you link to kernel32 and user32 and then use dlsym to get the function address? What is VideoDLL supposed to be for? Why does the comment for WinMain say it is never called and then have a load of junk in it? If you can resolve these issues then we can have a single Wine for Win32 and S.W.F! Rob

4 7

RE: Add support for TB_GETMETRICS and TB_SETMETRICS messages
by Robert Shearman 07 Mar '04

07 Mar '04

Dmitry Timoshkov wrote: > > Hello, > > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > Add support for TB_GETMETRICS and TB_SETMETRICS messages. > > diff -u cvs/hq/wine/dlls/comctl32/toolbar.c wine/dlls/comctl32/toolbar.c > --- cvs/hq/wine/dlls/comctl32/toolbar.c 2004-03-07 > 17:24:46.000000000 +0800 > +++ wine/dlls/comctl32/toolbar.c 2004-03-07 18:12:44.000000000 +0800 > @@ -5871,6 +5871,60 @@ TOOLBAR_SysColorChange (HWND hwnd) > } > > > +static LRESULT TOOLBAR_GetMetrics(HWND hwnd, LPTBMETRICS lpMetrics) > +{ > + TOOLBAR_INFO *infoPtr = TOOLBAR_GetInfoPtr (hwnd); > + > + if (lpMetrics->cbSize != sizeof(TBMETRICS)) > + return 0; > + > + if (lpMetrics->dwMask & TBMF_PAD) > + { > + lpMetrics->cxPad = infoPtr->nButtonWidth; > + lpMetrics->cyPad = infoPtr->nButtonHeight; > + } > + if (lpMetrics->dwMask & TBMF_BARPAD) > + { > + lpMetrics->cxBarPad = infoPtr->nWidth; > + lpMetrics->cyBarPad = infoPtr->nHeight; > + } > + if (lpMetrics->dwMask & TBMF_BUTTONSPACING) > + { > + lpMetrics->cxButtonSpacing = infoPtr->szPadding.cx; > + lpMetrics->cyButtonSpacing = infoPtr->szPadding.cy; I don't think this is quite right. MSDN says that cxButtonSpacing is "Width of the space between toolbar buttons", where as padding is "used to create a blank area between the edge of the button and the button's image and/or text". If experimentation proves that they are the same then a nice comment saying MSDN is wrong would be appropriate. Rob

2 4

wine-20040213 doesn't compile on Linux w/ 2.6.3 kernel and gcc-3.3.3
by Tom Williams 07 Mar '04

07 Mar '04

I had successfully built wine-20040213 before upgrading to the 2.6.3 Linux kernel and XFree86 4.4.0. After upgrading to XFree86 4.4.0 (from source distribution), wine would crash when I would try to run a Windows app so I decided to rebuild wine so it would use the XFree86 4.4.0 headers and libs, etc. Now, when I compile wine-20040213, it stops with this compile error: make[2]: Leaving directory `/build/wine-20040213/dlls/newdev' make[2]: Entering directory `/build/wine-20040213/dlls/ntdll' gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_NTSYSTEM_ -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o cdrom.o cdrom.c In file included from /usr/include/linux/cdrom.h:14, from cdrom.c:63: /usr/include/asm/byteorder.h:14: error: syntax error before "__u32" /usr/include/asm/byteorder.h:28: error: syntax error before "__u64" In file included from /usr/include/linux/byteorder/little_endian.h:11, from /usr/include/asm/byteorder.h:57, from /usr/include/linux/cdrom.h:14, from cdrom.c:63: /usr/include/linux/byteorder/swab.h:133: error: syntax error before "__u16" /usr/include/linux/byteorder/swab.h:146: error: syntax error before "__u32" /usr/include/linux/byteorder/swab.h:160: error: syntax error before "__u64" make[2]: *** [cdrom.o] Error 1 make[2]: Leaving directory `/build/wine-20040213/dlls/ntdll' make[1]: *** [ntdll] Error 2 make[1]: Leaving directory `/build/wine-20040213/dlls' make: *** [dlls] Error 2 tom@linux:~/build/wine-20040213$ Based on this discussion on the gcc-help mailing list: http://gcc.gnu.org/ml/gcc-help/2004-03/msg00057.html it looks like the "__KERNEL__" option needs to be specified so that __attribute_const__ can be properly defined and cdrom.c can then be compiled. I haven't tried it yet but I'm guessing adding __KERNEL__ to the "extradefs" macro in the dlls/ntdll/Makefile.in file might do the trick. I'm going to try that now and see what happens. Has this problem already been encountered and addressed? Thanks... Peace... Tom

2 2

Wine and Macromedia in (Heise) News
by Stefan Leichter 06 Mar '04

06 Mar '04

Hello, in http://www.heise.de/newsticker/meldung/45275 (german only) it is states that Macromedia currently modifies their Web-Authoring-System Flash MX to run with wine. After that they like to port it to linux. Bye Stefan

2 1

winegcc and wrc
by Chris Seaton 06 Mar '04

06 Mar '04

I'm having problems with winegcc and wrc. Both were working great on my system but then I had to move to a different setup. wrc seems to work (it doesn't complain at all and produces an object file) but when I link the generated object file to all my program I get "Error: winewrap failed": ... winegcc -I../../library --debug -c -o obj/utilities.o utilities.c wrc -o obj/resources.o resources.rc winegcc -mwindows -o bin/cspassword.exe obj/*.o -L../../library/bin -lcspassword -lcomctl32 Error: winewrap failed. make: *** [bin/cspassword.exe] Error 2 I'm using the latest snapshot. As I said it was all working fine before I moved system. What could be causing this? Thanks, Chris Seaton

2 2

Crash running MS Word '97
by Dan Kegel 05 Mar '04

05 Mar '04

Yesterday's CVS crashes when I run Word '97 with it, load a (largish) document, and quit. I guess Wine is passing back a null pointer and Word doesn't like it. Here's the stack: Unhandled exception: page fault on read access to 0x00000004 in 32-bit code (0x505be71e). Symbol hack_digit (0000:4007c890) is invalid In 32-bit mode. 0x505be71e (MSSP232.DLL.SpellCloseUdr+0x1b595 in MSSP232.DLL): movl 0x4(%esi),%ecx Wine-dbg>bt Backtrace: =>0 0x505be71e (MSSP232.DLL.SpellCloseUdr+0x1b595 in MSSP232.DLL) (ebp=4060dc94) 1 0x505b1db7 (MSSP232.DLL.SpellCloseUdr+0xec2e in MSSP232.DLL) (ebp=4060dcc4) 2 0x505a3ea8 (MSSP232.DLL.SpellCloseUdr+0xd1f in MSSP232.DLL) (ebp=40470002) 3 0x83c68900 (MSSP232.DLL..reloc+0x336a1900) (ebp=05bb11e8) *** Invalid address 0x05bb11e8 - Dan -- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change

1 0

Rel.: Calmira.org
by RadchenkoSG＠yukos.ru 05 Mar '04

05 Mar '04

Please, fix this-> http://www.calmira.org (@Wine User Guide, p.53). This domain has been hijacked by a domain harvester. Calmira-team asks to remove all links to calmira.org from related pages and update them to it's new domain: calmira.net (<-http://www.calmira.de/, news). Respectfully, Sergey Radchenko.

1 0

Followup on Borland C++ 5.5
by Michael Pyne 05 Mar '04

05 Mar '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, If it helps, the patch that I was referred to a week or so ago regarding the linker for Borland C++ 5.5 hanging did work, after some modifications. It is attached to this message. Basically, I translated the VirtualAlloc() call into it's NtAllocateVirtualMemory() equivalent to solve the unresolved symbol errors, and just plain left out the check at the end of the function for the region size. Hope that's OK. Obviously this patch isn't suitable for inclusion into Wine proper since it seems to merely patch over a different problem. I've recompiled Wine with full debug information and such, and if someone knows what I should look for or do, I'd be more than willing to provide debug output to nail down the error. I've tracked down the infinite loop to NTDLL_wait_for_multiple_objects() in dlls/ntdll/sync.c. For some reason, whatever the program is waiting on doesn't ever seem to occur (unless, of course, the above patch is applied?!?). Please let me know if there's anything I can do to help close this bug permanently. :-) Regards, - Michael Pyne -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFASCZaqjQYp5Omm0oRAvWBAJ9M26Gct10rxLdPKJm5fHl3JPzDTQCgypIW NQ2wE4FNElbm5ohhuXvu7eA= =JcS+ -----END PGP SIGNATURE-----

1 0

Patch Status Check
by Mike Kost 05 Mar '04

05 Mar '04

Alexandre, Can you report on the status of the following patches. I havn't spotted them in CVS and they've been out there for almost 2 weeks now. Austerlitz patch #1 - play audio file with + in filename http://www.winehq.org/hypermail/wine-patches/2004/02/0287.html Austerlitz patch #2 - Calculate the DIB size http://www.winehq.org/hypermail/wine-patches/2004/02/0286.html The patches were tested and appear to solve bug #2011 http://bugs.winehq.org/show_bug.cgi?id=2011 Mike Kost mike at tashcorp dot net

2 1

Re: Fix for programs that store VirtualQueryEx results in signed integers (eg. The Borland Linker)
by Alexandre Julliard 05 Mar '04

05 Mar '04

Troy Rollo <wine(a)troy.rollo.name> writes: > + * The problem with emulating this is that on Linux the top of the stack is at > + * 0xbfffffff and below, so reserving even the balance of this range would > + * artificially limit stack growth. We could move the stack, but it's too late > + * to do that here because there will be pointers to things on the stack > + * that will be affected - moving the stack would need to be done in main() in > + * loader/main.c, which would then be responsible for moving it back (this would > + * be done with mremap and subsequent adjustment to the stack pointer). Actually we don't run on the main stack, so allocating the space above 0x80000000 would definitely be possible, the stack doesn't need to grow there. -- Alexandre Julliard julliard(a)winehq.org

3 8

WinCE application support for WINE and ReactOS
by Steven Edwards 04 Mar '04

04 Mar '04

Hello All, This is all very experimental. I am working on in the ReactOS tree and it might not even work for larger apps but I am happy with the results so far. I was thinking the other day that ReactOS and WINE/Linux might get a big boost if we can push support in the embedded enviroment so I started taking a look at WinCE and Microsoft Embedded Visual C++ 4.0 .BTW: Its a free download now. http://www.microsoft.com/downloads/details.aspx?FamilyID=1dacdb3d-50d1-41b2… I started looking at WinCE and thought it would be nice if we could be source compatible with WinCE apps and binary compatbile on x86. Well it seems that WinCE apps dont differ much from standard Win32 apps execpt the subsystem ID is differnt. If you attempt to run a WinCE application on Windows it will say that its not able to run. Ok no problem, we just run "editbin /subsystem:windows blah.exe" and check it out. Now the app is looking for coredll.dll. No problem there I have created a stub coredll.dll that just forwards all calls to the proper Win32 dlls such as user32, kernel32, etc..... .....and check it out. My little messagebox test works on Windows. Ok soon then I go and run the same test on ReactOS but this time I run a copy of messagebox without changing the subsystem ID...Hey what do you know. It works =). I talked with Alexandre about it a bit and he said that WINE like ReactOS also shouldnt care about the subsystem ID so if someone is interested in testing just drop the messagebox programs and coredll.dll in to a directory and give it a shot. I am having trouble getting more complex apps (hello world) to work atm so I think i am just going to take a break and clear my head for a few days. Some of the WinCE API and Win32 is not 100% compatible so we cant just forward all parts to the Win32 implementation but I think we can do it for most of it. If anyone is interested in helping out the source is in the ROS CVS tree and attached to this email...... binary.zip messagebox.exe - wince messagebox program msgbox.exe - wince messagebox program with subsystem id changed to Windows. wincehel.exe - Hello World WinCE app wincehelw.exe - Hello World WinCE app with subsystem id changed to Windows. coredll.dll - WinCE Win32 API commctl.dll - WInCE common controls API. source.zip coredll - dummy forwarder dll commctl - dummy stub dll for common controls Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com

1 0

WinCE application support for WINE and ReactOS
by Steven Edwards 04 Mar '04

04 Mar '04

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel