August 2004 - Wine-Devel - list.winehq.org

RE: iostream and msvcrt?

by Scott Snell

Is that simpler than fixing the MSVCRT headers? I have used STLport before so the idea sounds feasable to me. I imagine I have to change the gcc-linux.mak by: replacing the call to gcc with winegcc, removing references to GLIBC, adding a path pointing to /include/wine/MSVCRT. Anything else? regards, Scott. > -----Original Message----- > From: Boaz Harrosh [SMTP:boaz(a)hishome.net] > Sent: Tuesday, 17 August 2004 18:18 > To: Scott Snell > Cc: Wine-Devel (E-mail) > Subject: Re: iostream and msvcrt? > > Using gcc's c++ libraries will not work with msvcrt. If it will compile > (which it doesn't) it will not load. (Some circular linking) > Your best bet is STLPort. Check it out. What I have done is a special > makefiles set with special config.h that compiles and links STLPort over > msvcrt. I have written to STLPort if they want my changes as support for > another platform but I never got a response from them. Do you need me to > dig out the old HD and pack you an STLPort compiled over msvcrt? > You might need to make some changes because it is from before winegcc > times,. Going strait for gcc. and maybe some wine stuff changed since > than. > > Scott Snell wrote: >

Aug. 18, 2004

Re: WineSetupTk...

by Tom

Ivan Leo Puoti wrote: >>winesetuptk is still maintained? I thought the recent config file changes > > broke it! > I've recently removed it from the sourceforge download page. > > Ivan. Hello All, I sent a patch to remove (winesetuptk) from the status pages see: http://www.winehq.org/hypermail/wine-patches/2004/08/0185.html As it will be depreciated by winecfg in the near future. Ivan, do we need to remove links to sourceforge since its no longer available? I would guess so.. So do you want to do it or me? Jeremey anything wrong with that patch? Tom

Aug. 18, 2004

Re: winealsa dsound capture message patch

by Alexandre Julliard

Robert Reif <reif(a)earthlink.net> writes: > Adds missing wine specific dsound capture message support. This patch causes the dsound capture test to hang for me. Here's the output I get before killing it: capture.c:230:Testing Primary Sound Capture Driver - winealsa.drv fixme:wave:widDsCreate DirectSoundCapture not implemented The (slower) DirectSound HEL mode will be used instead. capture.c:256: DirectSoundCapture Caps: size=16 flags=0x00000020 formats=fffff channels=2 capture.c:331: Testing the capture buffer at 8000x8x1 PCM capture.c:123: Caps: size = 16 flags=0x00000000 buffer size=8000 capture.c:142: tag=0x0001 8000x8x1 avg.B/s=8000 align=1 capture.c:154: status=0x0000 -- Alexandre Julliard julliard(a)winehq.org

Aug. 18, 2004

Re: Different X Displays and Wine

by Alexandre Julliard

"Eric Frias" <efrias(a)syncad.com> writes: > I'm curious how much work would be involved in fixing this correctly. I've > never looked at the wineserver code, so I don't know if this would just be a > matter of adding another variable to a data structure that gets passed > around to all of the windowing code, or if this would require major changes > to the way wineserver works. If it's reasonably easy, I might be able to > make the fix or lend some assistance; if it is a large amount of work, we'll > probably be happy with the workaround we have. Basically you need to change the window management code in the server to support multiple window hierarchies, and create one hierarchy per display; then you need to associate related things like clipboard or window classes to the proper hierarchy. It basically boils down to implementing the Windows concept of desktops and window stations. It's not very hard, but it's still a bit of work. -- Alexandre Julliard julliard(a)winehq.org

Aug. 18, 2004

Re: Do more tests in non-interactive mode (resubmit)

by Alexandre Julliard

Francois Gouget <fgouget(a)codeweavers.com> writes: > That's strange. Could you run it (with or without the patch but without > the -q flag) and send me the output? I guess it's either that Alsa has > multiple capture devices or that there's a bug somewhere. > > If needed we can still speed up the test by reducing the capture time, > e.g. from 0.1 second to 0.05 seconds. This is what I get without the patch: capture.c:341:found 1 WaveIn devices capture.c:265: 0: "SB16 Wave In" (winealsa: default) 1.0 (2:260): channels=2 formats=fffff capture.c:310:Testing invalid format: 2 MHz sample rate capture.c:265: WAVE_MAPPER: "Wine wave in mapper" (not supported) 0.1 (255:1): channels=2 formats=fffff capture.c:310:Testing invalid format: 2 MHz sample rate capture.c: 1375 tests executed, 0 marked as todo, 0 failures. With the patch I get a bunch of "Recording for 0.1 second" traces that seem to appear at about 1 second intervals, so I guess the problem is that the specified duration is not handled correctly. >> It also fails with the OSS driver: >> capture.c:128: Test failed: WaitForSingleObject failed for header >> capture.c:129: Test failed: WHDR_DONE not set in frag.dwFlags >> capture.c:130: Test failed: frag.dwBytesRecorded=512, should be 800 > [...] > > This looks like a bug that needs to be fixed. To confirm, could you run > the test in interactive mode without the patch? > If you get the same errors then it means there's a bug in wineoss. Yes, I get the same errors without the patch. -- Alexandre Julliard julliard(a)winehq.org

Aug. 18, 2004

Re: Backtrace Dumps

by Alexandre Julliard

Robert Shearman <rob(a)codeweavers.com> writes: > I propose the addition of this new debug tool that will allow > developers to output backtraces to the console, without having to > interact with a debugger. It can give a useful indication of how > functions are being called in situations where a break point is not > appropriate. I think it's better to let the debugger take care of that. If you don't want a real breakpoint you could define a custom exception to tell winedbg to just dump the backtrace and continue. -- Alexandre Julliard julliard(a)winehq.org

Aug. 17, 2004

RE: iostream and msvcrt?

by Scott Snell

Hi Mike, Even if I change my command to be: winegcc -c -mno-cygwin -I/usr/local/include/wine/msvcrt -o test.o test.cpp I get the same spread of errors. I am converting an MSVC project that uses both these header files and I'm trying to understand why the MSVCRT header files provided with wine wont work with my project. regards, Scott. > -----Original Message----- > From: Mike Hearn [SMTP:m.hearn(a)signal.QinetiQ.com] > Sent: Tuesday, 17 August 2004 18:38 > To: Scott Snell > Cc: Wine-Devel (E-mail) > Subject: Re: iostream and msvcrt? > > Why are you trying to use G++ with the MSVCRT (Microsoft Visual C++ > runtime) ? That can surely never work: even if the headers were > compatible, the ABI used is not.

Aug. 17, 2004

Re: don't kill the destktop

by Ferenc Wagner

"Dmitry Timoshkov" <dmitry(a)baikal.ru> writes: > "Ferenc Wagner" <wferi(a)afavant.elte.hu> wrote: > >> ChangeLog: The desktop process is not automatically >> restarted under Win95, so stop killing it. > > This patch causes test_shell_window tests fail under win2k SP4. > Please either fix the failures or revert the patch. Sorry, I didn't notice it was adding to the errors, I only aimed at keeping the desktop usable. Whatever those tests do, it's voodoo magic for me, so my fix could only be removing the test_shell_window tests. Not very creative, so I'd rather shut up. -- Feri.

Aug. 17, 2004

Re: ADVAPI32: implement and test BuiltTrusteeWithName

by Alexandre Julliard

Mike McCormack <mike(a)codeweavers.com> writes: > + pTrustee->TrusteeForm = NO_MULTIPLE_TRUSTEE; > + pTrustee->TrusteeType = TRUSTEE_IS_NAME; > + ok( trustee.TrusteeForm == TRUSTEE_IS_NAME, "TrusteeForm wrong\n"); > + ok( trustee.TrusteeType == TRUSTEE_IS_UNKNOWN, "TrusteeType wrong\n"); So which one is correct, the code or the test? <g> -- Alexandre Julliard julliard(a)winehq.org

Aug. 17, 2004

Re: More winecfg todos

by Saulius Krasuckas

On Tue, 17 Aug 2004, Mike Hearn wrote: > > 256 /home/s2/.wine/config > > 4946 /home/s2/.wine/system.reg ... > Maybe we should fork the Wine/Config branch into a separate .reg file to > appease those who want to edit it using a text editor. That would make > the switch from config file -> registry less obvious. Not exactly the > same of course, no comments for one, no defaults to show you what they > are for another, Right, the clear Wine REG-file format only (in a separate file). > but it might be an improvement? I think yes, for me it would an improvement. The only bad thing here is my lack of the ideas on how to implement such forking. If it is a not very trivial stuff to code and if only a very few users would become pleased with it, then the idea is dead already, right? Whatever it be, I vote for the forking offered by Mike: config-to-registry-through-a-separate-regfile, eg.: ~/.wine/config.reg . PS I know, my english isn't OK. Hope I can be understood in right way.

Aug. 17, 2004

Re: WineSetupTk...

by Ivan Leo Puoti

> winesetuptk is still maintained? I thought the recent config file changes broke it! I've recently removed it from the sourceforge download page. Ivan.

Aug. 17, 2004

Re: GetFontLanguageInfo patch.

by Shachar Shemesh

Leib Moscovitz wrote: > Shachar Shemesh wrote: > >> Leib Moscovitz wrote: >> >>> Dear Shachar, >>> >>> Yes, there is Pmail for Windows (version 4.2 already), and the >>> problem is that it doesn't handle Hebrew RTL correctly - I was >>> wondering whether there's any solution to this that you know of. >>> >>> Thanks, >>> >>> Leib Moscovitz >>> >> Is it only on Wine that it doesn't, or also on Windows? >> >> Please keep posts on list. >> >> Shachar >> > I only know about Windows - I am just an amateur, and as such I don't > even know what Wine is. Wine cannot solve incomplete functionality Windows applications have. It will not help you. Wine is aimed at making Windows applications run on Linux and other Unixes. It has nothing to do with what a given application does or does not know how to do on Windows. More info on http://www.winehq.org. Please CC the list (wine devel) when replying. Shachar -- Shachar Shemesh Lingnu Open Source Consulting ltd. http://www.lingnu.com/

Aug. 17, 2004

Re: Different X Displays and Wine

by Eric Frias

Alexandre Julliard (julliard_at_winehq.org) wrote:> We don't support having the same user run from different displays at> the same time. I don't think that's a common setup at all. It probably is not a common setup, but Boaz isn't the only person to have been bitten by this. It has happened both to us and to people who use our software. In our development environment, we usually use one or two common user accounts to do all development and testing in. I know this isn't ideal, but I don't have any power to change this. Anyway, with this setup, it is very easy to have two people developing or testing from the same account but displaying on separate machines. Right now we have been doing what was suggested earlier -- we have a script to launch our application and this script creates a .wine-$DISPLAY directory and points WINEPREFIX to that directory. This works well enough for now. It's inconvenient that the config file and registry aren't shared, so doing things like changing printer settings is a bit of a chore, but this hasn't bothered us too much yet. We're also making the assumption that not many users will be running this on multiple displays, so things will just work for most users and the few that do try to run on multiple displays will at least be able to do it. I'm curious how much work would be involved in fixing this correctly. I've never looked at the wineserver code, so I don't know if this would just be a matter of adding another variable to a data structure that gets passed around to all of the windowing code, or if this would require major changes to the way wineserver works. If it's reasonably easy, I might be able to make the fix or lend some assistance; if it is a large amount of work, we'll probably be happy with the workaround we have. Eric

Aug. 17, 2004

Re: GetFontLanguageInfo patch.

by Shachar Shemesh

Leib Moscovitz wrote: > Dear Shachar, > > Yes, there is Pmail for Windows (version 4.2 already), and the problem > is that it doesn't handle Hebrew RTL correctly - I was wondering > whether there's any solution to this that you know of. > > Thanks, > > Leib Moscovitz > Is it only on Wine that it doesn't, or also on Windows? Please keep posts on list. Shachar -- Shachar Shemesh Lingnu Open Source Consulting ltd. http://www.lingnu.com/

Aug. 17, 2004

Re: GetFontLanguageInfo patch.

by Shachar Shemesh

Rein Klazes wrote: >On Tue, 17 Aug 2004 18:05:44 +0200, you wrote: > > > >>Dear Sir, >> >>I am searching for a way to make Pegasus Mail for Windows (4.x) display >>Hebrew correctly, from right to left, and I came across a post of yours via >>Google which seems to deal with this issue. >> >>Have you developed any solution to this problem, and if so, is it publicly >>available? >> >>Many thanks, >> >>Leib Moscovitz >> >> >> > >Unfortunately the issue that you refer to was fixing some left-to-right >problem. I do not know if or how it works for right-to-left writing. > >I have cc' ed this message to the wine developers list, perhaps the >developer that is working on/with this, Shachar Shemesh, can shine a bit >of light on the issue. > >Rein. > > Oooh, pmail. Haven't touched it since I was a Novel sysadmin, back in 1996. So, there is a Windows version now? What is, exactly, the problem you are experiencing with pmail? What version of Wine? Shachar P.s. People, if you want to make sure I read mail addressed to me, please CC me specifically. Sh. -- Shachar Shemesh Lingnu Open Source Consulting ltd. http://www.lingnu.com/

Aug. 17, 2004

Interesting bug

by Mike Hearn

From the appdb: ----------------------------------------------------------------------- * SAVE FOR WEB Solution* : Well, after a fair amount of trail-and-error testing, I have FINALLY found what WILL or WONT allow Save-For-Web to work... It actually is how you execute Photoshop.exe ... if you try to run it with forward slashes in the path, Save for Web will NOT work. If you execute with backslashes, Save for Web WILL work. So... Save for Web works with: wine "c:\program files\adobe\Photoshop 7.0\Photoshop.exe" Save for Web WILL NOT work with: wine "c:/program files/adobe/Photoshop 7.0/Photoshop.exe" Enjoy! Hiji ----------------------------------------------------------------------- I don't have Photoshop here, but perhaps we should ensure that argv[0] and equivalents always use backslashes?

Aug. 17, 2004

Re: WineSetupTk...

by Mike Hearn

winesetuptk is still maintained? I thought the recent config file changes broke it! These days Wine is a lot more self configuring than it once was anyway, we just have a few things that still need to be done (better drive detection and such) ... what do you want to configure? -mike Tashlan wrote: > Dear Oh Glorious Developers, > (without which none of this would be possible) > > I have decided to try Wine for the first time and I'm trying to keep it > simple. You have a link for WineSetupTk but I can't seem to find the file > anywhere! Not sure where it is, but it sounded really helpful. > > Link appears on this page with description of WineSetupTk... > http://www.winehq.com/site/docs/wine-user/config-helper-programs > > The Link points here... > http://sourceforge.net/project/showfiles.php?group_id=6241 > > Thanks in advance, > Tashlan > > >

Aug. 17, 2004

Re: GetFontLanguageInfo patch.

by Rein Klazes

On Tue, 17 Aug 2004 18:05:44 +0200, you wrote: > Dear Sir, > > I am searching for a way to make Pegasus Mail for Windows (4.x) display > Hebrew correctly, from right to left, and I came across a post of yours via > Google which seems to deal with this issue. > > Have you developed any solution to this problem, and if so, is it publicly > available? > > Many thanks, > > Leib Moscovitz > Unfortunately the issue that you refer to was fixing some left-to-right problem. I do not know if or how it works for right-to-left writing. I have cc' ed this message to the wine developers list, perhaps the developer that is working on/with this, Shachar Shemesh, can shine a bit of light on the issue. Rein. -- Rein Klazes rklazes(a)xs4all.nl

Aug. 17, 2004

Re: don't kill the destktop

by Dmitry Timoshkov

"Ferenc Wagner" <wferi(a)afavant.elte.hu> wrote: > ChangeLog: The desktop process is not automatically > restarted under Win95, so stop killing it. This patch causes test_shell_window tests fail under win2k SP4. Please either fix the failures or revert the patch. -- Dmitry.

Aug. 17, 2004

Re: More winecfg todos

by Saulius Krasuckas

(Sorry, wrong key-press) On Tue, 17 Aug 2004, Saulius Krasuckas wrote: > Or in a bash-awk code: > > #!/bin/bash > PATH_REG=tmp.reg > PATH_BRANCH='HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment' > AWK_APPEND_NPATH='{if (match($0,/^"PATH"=/)) sub(/"\r/, ";"ENVIRON["NPATH"]"\""); print}' > NPATH='a:\\new\\path' ... > And this is kind of messy. But nevermind, I am sure I am one of those exceptional users, so.. Thanks for the feedback.

Aug. 17, 2004

Re: More winecfg todos

by Saulius Krasuckas

On Tue, 17 Aug 2004, Mike Hearn wrote: > > Again, this may be need by power-win32-users, who basically can't stand > > the GUI of "regedit". :-P > > By definition, Windows power users are comfortable with the registry, as > how else did they get to be power users in the first place? Ughm, maybe I meant not-so-power users? :-/ Yes they are comfortable with browsing the registry, but they aren't such with editing it. At least I am not. > > PS maybe an alternative for the "winecfg" may be some cmd-line option like > > the "/advanced" to make such functionality available to user at run-time? > > No, a totally undiscoverable "advanced" mode is worse than just regedit. Ok, I agree. That is a M$ way. It is not nice. > Even an "advanced" button is bad: this sort of UI thinking is not one we > wish to copy IMHO. Button is wrong definitely, it is not needed for the most of the users. And some additional edit-boxes > Sorry, but I don't see what your hangup over the registry is. Remember > the .reg files are plain text! You can edit them in whatever editor you > like (as long as no wine processes are running at the time, of course). Right, I am forgetting about this. And the difference is in the size of the files: [s2(a)katleriai SRPMS]$ wc -l ~/.wine/config ~/.wine/system.reg 256 /home/s2/.wine/config 4946 /home/s2/.wine/system.reg 5202 total Text editor for the registry tweaking isn't an easy choice for me, because I don't like searching for one particular line through the 5000 of others. What then should I do walking this way is: 1, to export file; 2, to edit it; 3, import it back. Or in a bash-awk code: #!/bin/bash PATH_REG=tmp.reg PATH_BRANCH='HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment' AWK_APPEND_NPATH='{if (match($0,/^"PATH"=/)) sub(/"\r/, ";"ENVIRON["NPATH"]"\""); print}' NPATH='a:\\new\\path' if [[ "$1" == "" ]]; then { echo Example of a usage : $0 \'$NPATH\' exit 1 } fi if regedit /E $PATH_REG "$PATH_BRANCH"; then { export NPATH="$1" if cat $PATH_REG | awk "$AWK_APPEND_NPATH" > $PATH_REG; then { regedit $PATH_REG cat $PATH_REG | grep ^\"PATH | xargs echo "Setting this: " rm $PATH_REG } fi unset NPATH } fi

Aug. 17, 2004

Re: More winecfg todos

by Mike Hearn

> Right, I am forgetting about this. And the difference is in the size of > the files: > > [s2(a)katleriai SRPMS]$ wc -l ~/.wine/config ~/.wine/system.reg > 256 /home/s2/.wine/config > 4946 /home/s2/.wine/system.reg > 5202 total > > Text editor for the registry tweaking isn't an easy choice for me, because > I don't like searching for one particular line through the 5000 of others. > > What then should I do walking this way is: > > 1, to export file; > 2, to edit it; > 3, import it back. Maybe we should fork the Wine/Config branch into a separate .reg file to appease those who want to edit it using a text editor. That would make the switch from config file -> registry less obvious. Not exactly the same of course, no comments for one, no defaults to show you what they are for another, but it might be an improvement?

Aug. 17, 2004

Wine Status - User Interface

by Tom

Hello, I have been working on a update for the Status UI page over the last couple day's and i'm attaching a copy of what I have. I've re-named the template to .html so you can view it in your e-mail program or browser of choice. I haven't done the changelog so just view this againt http://www.winehq.org/site/status_ui for changes or diff. commits, suggestions, and flames are welcomed Regards, Tom

Aug. 17, 2004

Re: iostream and msvcrt?

by Boaz Harrosh

Mike Hearn wrote: > Why are you trying to use G++ with the MSVCRT (Microsoft Visual C++ > runtime) ? That can surely never work: even if the headers were > compatible, the ABI used is not. > He meant in a winelib when a winelib links against msvcrt (-nocygwin on the winegcc command line). Only the C symbols and a few C++ (new & delete) are exported from wine's msvcrt.spec so only these get linked. The rest of the C++ symbols are looked for else where. His current problem, though, is Header compatibility. When you don't use "-nocygwin" than lots of Windows originating code (like MFC) does not compile. Free Life Boaz

Aug. 17, 2004

Re: iostream and msvcrt?

by Mike Hearn

Scott Snell wrote: > Hi All, > > Thanks to everyone who has helped me with winelib, so far most things are > going really well! However here is an issue I cant solve - iostream and > msvcrt. Here is an example file: Why are you trying to use G++ with the MSVCRT (Microsoft Visual C++ runtime) ? That can surely never work: even if the headers were compatible, the ABI used is not.

Aug. 17, 2004