wine-devel March 2005

wine-devel@winehq.org

178 participants
443 discussions

Re: MSI: Radio Buttons
by Alexandre Julliard 03 Mar '05

03 Mar '05

Ulrich Czekalla <ulrich.czekalla(a)utoronto.ca> writes: > const static WCHAR szStatic[] = { 'S','t','a','t','i','c',0 }; > +const static WCHAR szButton[] = { 'B','U','T','T','O','N', 0 }; > + > +const static WCHAR szButtonData = { 0 }; Did you really intend to use an empty string here for the button property? That doesn't seem right; though if you really need to redefine the winproc it would be much cleaner IMO to define a proper window class. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: riched20 and test app
by Mike McCormack 03 Mar '05

03 Mar '05

Hi Krzysztof, Krzysztof Foltman wrote: > This is an attempt at starting a RichEdit 2.0 clone, plus a test app for > it (which I, for some reason, decided to call Wine WordPad). Cool. Looks like you've done alot of good work. > It lacks most essential functionality, and source formatting is not > exactly standard, but it has enough functionality to make a couple of > Wine developers convince me to release it now. Or weeks ago. Well, you wrote it, so you get to choose the formatting. I like that you've used lots of small functions, rather than monolithic 200 line globs. I like the asserts too. > The test app uses the Mike McCormack's test snippet to fill the control > with some fancy formatted text. > > Hope the patch is OK. Adding new DLL's and EXE's isn't an easy process. OK, now some suggestions: * submitting riched20 and the new wordpad program seperately would be a good idea. The bigger the patch, the longer it tends to hang round before it's committed. * instead of #ifndef __WINESRC__ ... printf ... #endif, how about using wine's debug macros TRACE, ERR, etc? Then you can just #define TRACE to printf when __WINESRC__ isn't defined * instead of XXXFK how about FIXME? * you probably should get rid of the _int3 macro in wrap.c, and replace it with DebugBreak() * ME_DumpParaStyle isn't used... maybe change it to use MESSAGE() rather than a message box. You can dump stuff by checking the condition WINE_TRACE_ON(richedit). You'll need to declare a WINE_DEFAULT_DEBUG_CHANNEL for that.. * maybe you want to add LGPL licenses on your header files? * keep the formatting in your Makefile.in the same as the other dlls. Julliard's a bit fussy about that, so he's probably going to change it anyway. Might as well save him the time. Mike

1 0

World of Warcraft - crash in game
by Alex Woods 03 Mar '05

03 Mar '05

Hi, World of Warcraft is working beautifully now apart from a crash that occurs seemingly randomly. The application is catching the crash, and giving a message like this: This application has encountered a critical error: ERROR #132 (0x85100084) Program: C:\Program Files\World of Warcraft\WoW.exe Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:557102CD EAX=00000000 EBX=55BDFCA8 ECX=00000000 EDX=55BDFBB8 ESI=5E320308 EDI=00000000 EBP=55BDFC08 ESP=55BDFB9C EIP=557102CD FLG=00010212 CS =0023 DS =002B ES =002B SS =002B FS =005B GS=0063 I know this isn't really much use on it's own. I've tried turning on +relay logging, but it's proved futile - it seems to end up freezing up my system before a crash occurs. One thing that might be useful is that the access violation always seems to be around the same small area of memory each time, eg: Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:557103CD Exception: 0xC0000005 (ACCESS_VIOLATION) at 0023:5571025D Over the course of 13 (unlucky for me ;)) crashes, these are the only 3 addresses it has given. My question is what can I do to debug this? +relay logging is probably infeasible, but I'd be happy to hack around to get it to only log certain things - I'm not sure what I'd need to log. Also, the last time it crashed, I was lucky enough to have it leave me in winedbg, which I've left open. Is there anything worth my while poking around with in there while I have the chance? I guess I'll be running memtest on my machine too, but I'd like to do what I can in winedbg first ;) Cheers. -- Alex

4 6

MSI trouble with ALLUSERPROFILE
by Vitaly Lipatov 03 Mar '05

03 Mar '05

I get err with %ALLUSERPROFILE during install program: trace:msi:MSI_FormatRecordW (L"[%ALLUSERSPROFILE]") trace:msi:deformat_string_internal Starting with L"[%ALLUSERSPROFILE]" trace:msi:find_next_outermost_key Found Key L"%ALLUSERSPROFILE" trace:msi:deformat_string_internal Current (null) .. L"%ALLUSERSPROFILE" err:msi:deformat_environment Unknown environment variable trace:msi:deformat_string_internal after everything (null) Where I will set this env variable? (I know I can do it in shell, but what is the right way?) -- Vitaly Lipatov, ALT Linux Team Russia, Saint-Petersburg, www.etersoft.ru

1 0

%Fp printf format specifier
by Uwe Bonnes 03 Mar '05

03 Mar '05

Hallo, http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore98/H… uses a "%Fp" format spezifier. Running with native msvcrt, this seems to be the same as "%p". However builtin msvcrt stumbles about the "superfluous" 'F". Does anybody know what the meaning of the "F" is? I didn't find anything on the net. And b.t.w., how do I get Google to not ignore the '%' in a search for "%Fp"? And mingw/malloc.h has the definitions of _USEDENTRY and _FREEENTRY excahnged and misses more entries... Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

6 12

Re: Use IsWindowVisible instead of GetWindowLong(GWL_STYLE) & WS_VISIBLE as a test for desktop visibility
by Ferenc Wagner 03 Mar '05

03 Mar '05

Dmitry Timoshkov <dmitry(a)baikal.ru> writes: > let's see if IsWindowVisible() better detects a not visible desktop. Ah, fine, this may put some momentum into the situation! -- Feri.

3 2

Printing in Wine (using "ttydrv" device)...
by Juergen Hammelmann 03 Mar '05

03 Mar '05

Hi All, we are developing a windows/wine app for automation of MS Word (serial printing in background to PS files with the WINEPS driver on SuSE 9.2 platform, wine-20050211). We want to run this application and Word in background as server, no graphical output should occur in this environment, we don't like to install a X11-/VNC-Server on the server: Using "ttydrv" device I found out that all graphical output is disabled and wine can run without a X11 Server / VNC Server, this is prefered: but here graphical output of printing is disabled, too! The PS files created are blank! Is there any way to configure functioning printing with "ttydrv" device? Ferenc Wagner told me, that printing and graphical output is done through GDI both, so ttydrv as GDI backend disable this all!? Is this the right explanation? Is there any way to enable this for printing again? Best Regards, Jürgen

1 0

Visual C++ 6.0 as a Winelib IDE?
by Ira Krakow 03 Mar '05

03 Mar '05

I have Visual C++ 6.0 running under Crossover Office 4.1, which of course means it's running under Wine. For one of the examples in the Wine/Winelib book, I decided to take the code produced by the VC++ Win32 "Hello World" wizard and see how to port it to Wine. Turns out, it's almost trivial. Create an empty directory, copy the *.c, *.rc, *.h, and *.ico files to it. VC++ produces tons of other files, but they're either used to maintain the Visual Studio environment, or are intermediate compilation files that aren't needed. Then run: $ winemaker . The Makefile that Winemaker generates _almost_ works. You need to delete the references to the mfc library and mfc.dll. After doing that, running make generates the .so file. Wine runs it flawlessly. I got to thinking - can I convert the code from the MFC application as easily? Seems like it's doable, because the generated code runs in VC++/Crossover Office 4.1. I tried the same steps as before, with Winemaker, but I couldn't figure out what Makefile modifications were needed. All of this got me to thinking - could Wine running Visual C++ be a viable IDE for porting? Maybe just linking VC++ with the Winelib libraries would do it. Maybe after tweaking Winemaker and publishing a HOWTO we could show that this is a viable path? It's certainly easier than for Visual Studio developers and could help attract them to Wine. Another benefit - we could use the Visual C++ sample programs as tests for Wine. The programs might exercise areas that haven't been tested thoroughly. What do you think? Ira

5 6

wine-user.pdf feedback
by Dan W. 02 Mar '05

02 Mar '05

I think I have the answer why feedback to the wine-user.pdf has so far been disappointing: It's too well written. No questions to ask, almost. Actually, probably 90% of users try to get by without reading it. I saw a posting somwhere today, someone advising someone else about running the wine install, without mentioning uninstalling any old versions. The blind leading the blind. You need to put a big README!!!.TXT file somewhere, where it should say: "You choose: Spend 1 day reading wine-user.pdf, and another day setting it up; or spend a week trying to set it up, a month asking questions at the forums, a year in depression, then finally a day reading wine-user.pdf, and another day setting it up." But probably, the lucky 10% who read it never have any questions, so you don't hear from them. In my case, though, combining a high IQ and being a complete helpless newbie to Linux, is a powerful combination that produces questions out of nowhere. In the chapter about installing and un-installing, one small detail got left out: "How does one KNOW whether wine is installed, and if so what version it is?" I'm sure it must sound like typical newbie crap questions to you, but to me it's a solid and tangible one. Well, I do know that I do have wine installed, because when I installed Fedora Core 2, I said "install everything". Besides, I tried.. "wine /mnt/C/windows/notepad.exe" and it worked!!!! :-) :-) :-) But as for the version of wine I have, I have no idea how to find out. In Windows, I'd check the Add/remove programs, to see if it mentions the version, or I'd look in the installation folder for a readme.txt file. In Linux, not so easy: Even after doing a file search for "wine", I still can't tell what folder it is installed in, if indeed it is installed in ONE folder, and not many. Looks like many, by the looks of it... Or at least two: One under /usr/local, which only contains two files, another for documentation, elsewhere, and I saw a folder somewhere with alotof.dll.so files. Anyways, thank you for the great work you've done and are doing. Some day Historians will remember you like today we remember Leonardo, or whoever: How Humanity rid itself of a great monopoli threat. As newbie as I am in Linux, I'm the expert here at work. If I can get our Windows apps to run on Linux, I might succeed at having the company switch over. Wish me luck.

3 2

vartest.c - major pain in the build process
by Krzysztof Foltman 02 Mar '05

02 Mar '05

Is there any reason for gcc 3.3.1 to spend several minutes on compiling dlls/oleaut32/tests/vartest.c ? I guess it can be explained by optimization stage going nuts on compiling long functions with many branches (contained in the macros), but there must be a way to speed this up. It's barely tolerable now, and upgrading gcc is not an option for everyone. Krzysztof

9 23

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 March 2005