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

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

Re: More winecfg todos

by Mike Hearn

> 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? > 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. Even an "advanced" button is bad: this sort of UI thinking is not one we wish to copy IMHO. 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).

Aug. 17, 2004

Re: iostream and msvcrt?

by Boaz Harrosh

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: >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: > >// test.cpp module >#include <process.h> >#include <iostream> > >int test() >{ > return 1; >} > > >If I compile it using: > >wineg++ -c -mno-cygwin -I/usr/local/include/wine/msvcrt -o test.o test.cpp > >or > >wineg++ -c -I/usr/local/include/wine/msvcrt -o test.o test.cpp > >I get a multitude of errors such as: > >In file included from /usr/include/c++/3.3.2/iosfwd:46, > from /usr/include/c++/3.3.2/ios:44, > from /usr/include/c++/3.3.2/ostream:45, > from /usr/include/c++/3.3.2/iostream:45, > from test.cpp:2: >/usr/include/c++/3.3.2/i386-redhat-linux/bits/c++locale.h:53: error: >`uselocale' was not declared in this scope >In file included from >/usr/include/c++/3.3.2/i386-redhat-linux/bits/c++io.h:35, > from /usr/include/c++/3.3.2/bits/fpos.h:44, > from /usr/include/c++/3.3.2/iosfwd:49, > from /usr/include/c++/3.3.2/ios:44, > from /usr/include/c++/3.3.2/ostream:45, > from /usr/include/c++/3.3.2/iostream:45, > from test.cpp:2: >/usr/include/c++/3.3.2/cstdio:167: error: `snprintf' not declared >/usr/include/c++/3.3.2/cstdio:168: error: `vfscanf' not declared >/usr/include/c++/3.3.2/cstdio:169: error: `vscanf' not declared >/usr/include/c++/3.3.2/cstdio:171: error: `vsscanf' not declared > > >So whats my newbie mistake? > >thanks, > >Scott. > >

Aug. 17, 2004

Re: More winecfg todos

by Saulius Krasuckas

Sorry for being a bit unclear: On Tue, 17 Aug 2004, Saulius Krasuckas wrote: > On Mon, 16 Aug 2004, Alexandre Julliard wrote: > > and if an app needs a different PATH the installer for that app will > > change the registry itself. If users really need to change them, IMO we > > are doing something wrong. .. > but there are some console win32 utilities, made by me and such which > have no installer. So, if I need to run them from the batch file at > wcmd, I basically need to modify %PATH%. That's because there are quite a lot of utilities and I am hardly going to rewrite the batch file to call the programs using their full path.

Aug. 17, 2004

Threading issues? [ck-request@vds.kolivas.org: ck Digest, Vol 3, Issue 16]

by Andreas Mohr

Hi all, this is a nice little posting from the Con Kolivas Linux interactivity patches list. Note that it is about Cedega, not Wine, but it might easily affect Wine, too. Are we doing some big no-nos in the threading area here? (or maybe it's just done the way it is because we cannot do it a different, better way?) For the whole discussion, please see http://bhhdoa.org.au/pipermail/ck/2004-August/000428.html Andreas Mohr ----- Forwarded message from ck-request(a)vds.kolivas.org ----- Message: 12 Date: Mon, 16 Aug 2004 21:31:59 +1000 From: Con Kolivas <kernel(a)kolivas.org> Subject: Re: [ck] 2.6.8.1-ck1, cedega-cvs, ALSA sound (choppy) To: greblus(a)poczta.onet.pl Cc: ck(a)vds.kolivas.org Message-ID: <41209B2F.4030207(a)kolivas.org> Content-Type: text/plain; charset="us-ascii" Wiktor Grebla wrote: > On Mon, Aug 16, 2004 at 08:16:08PM +1000, Con Kolivas wrote: > > >>It wont be a preempt threshold problem. >>See if it's a priority issue on the part of wine*. Be absolutely certain >>that wineserver, wine and the game are all run the _same_ priority and >>not a better priority than X. Send me the output of 'top -b -n 1' during >>the sound being choppy. Then try running _all_ the wine things at nice >>+19. This is a simple sanity check to see where the problem lies. > > > It's in fact as you say, all parts of wine have different priorities, and > some of them are higher than X: > > greblus(a)greblus:~$ top -n 1 -b | grep wine > 1630 greblus 23 0 471m 230m 164m R 92.8 45.9 1:54.63 wine > 1666 greblus 20 0 471m 230m 164m S 2.0 45.9 0:01.64 wine > 1629 greblus 20 0 2400 1192 2176 S 0.0 0.2 0:00.00 winex > 1633 greblus 20 0 6864 5056 6756 S 0.0 1.0 0:01.10 wineserver > 1634 greblus 20 0 6864 5056 6756 S 0.0 1.0 0:00.15 wineserver > 1659 greblus 20 0 471m 230m 164m S 0.0 45.9 0:00.00 wine > 1660 greblus 21 0 471m 230m 164m S 0.0 45.9 0:00.00 wine > 1662 greblus 20 0 471m 230m 164m S 0.0 45.9 0:00.06 wine > 1663 greblus 33 0 471m 230m 164m R 0.0 45.9 0:00.41 wine > > greblus(a)greblus:~$ top -b -n 1 | grep X > 621 root 20 0 88092 18m 75m S 0.0 3.8 1:02.96 X > > After renicing all of them there is no problem with choppy sound in all of time > wasting programs I've on my disk :>, and overall (subjective) performance is > better of course. > > Full output of top -b -n 1 is here: > http://unixforge.org/~greblus/ck/top_-b_-n_1.txt > > Kindest Regards, > W. Thanks for details. You do not have different nice levels; that is PRI that is different, which is the "dynamic" priority that constantly changes by the scheduler. It is as I suspected, though - if you renice everything +19 and the problem goes away it is bad programming on the wine developers' part that use what's called sched_yield instead of proper locking between their threads. Don't concern yourself over the details, but at least you have a simple workaround... sigh Cheers, Con

Aug. 17, 2004

iostream and msvcrt?

by Scott Snell

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: // test.cpp module #include <process.h> #include <iostream> int test() { return 1; } If I compile it using: wineg++ -c -mno-cygwin -I/usr/local/include/wine/msvcrt -o test.o test.cpp or wineg++ -c -I/usr/local/include/wine/msvcrt -o test.o test.cpp I get a multitude of errors such as: In file included from /usr/include/c++/3.3.2/iosfwd:46, from /usr/include/c++/3.3.2/ios:44, from /usr/include/c++/3.3.2/ostream:45, from /usr/include/c++/3.3.2/iostream:45, from test.cpp:2: /usr/include/c++/3.3.2/i386-redhat-linux/bits/c++locale.h:53: error: `uselocale' was not declared in this scope In file included from /usr/include/c++/3.3.2/i386-redhat-linux/bits/c++io.h:35, from /usr/include/c++/3.3.2/bits/fpos.h:44, from /usr/include/c++/3.3.2/iosfwd:49, from /usr/include/c++/3.3.2/ios:44, from /usr/include/c++/3.3.2/ostream:45, from /usr/include/c++/3.3.2/iostream:45, from test.cpp:2: /usr/include/c++/3.3.2/cstdio:167: error: `snprintf' not declared /usr/include/c++/3.3.2/cstdio:168: error: `vfscanf' not declared /usr/include/c++/3.3.2/cstdio:169: error: `vscanf' not declared /usr/include/c++/3.3.2/cstdio:171: error: `vsscanf' not declared So whats my newbie mistake? thanks, Scott.

Aug. 17, 2004