Re: wine in the press :)
On Tue, Aug 05, 2003 at 11:49:54AM -0400, Tom wrote: > I just seen this on /. I though I would post the link here. > http://www.eweek.com/article2/0,3959,1210083,00.asp "Brooks said it took some time to convince Disney attorneys that he wanted to pay for the development of the porting solution but did not want to own it. However, Disney's legal department has developed a policy that enables Disney to protect its intellectual property while keeping within the statutes of the GNU General Public License, he said." Any idea, what that second sentence ist about (However...)?o Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: Licensing Question
On Thu, Jul 31, 2003 at 07:52:40PM +0200, Roderick Colenbrander wrote: > Likely a vote for it would be needed since I think > all people who worked on the headers need to approve it. Well, as you mention correctly in the second part: Everyone who submitted patches under a LGPL license only *must* agree to have their code reclicensed. Calling that a vote reminds me of some pseudo democracies Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: WWN idea.....
On Thu, Jul 03, 2003 at 05:44:05PM -0700, Dustin Navea wrote:
> What if we put a link to the relevant item in the headline.. (i.e. if it is
> a thread, make it a link to the start of the thread in the winehq archives,
> and if it is something else, like an interview, make it a link to the actual
> interview)
Good idea! kt does the linking to the threads too - and I like that feature.
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
Re: WWN: wn20030704_177.xml
Brian, On Thu, Jul 03, 2003 at 04:02:47PM -0700, Brian Vincent wrote: > I'm going to include something new with this issue. From > now on I'll send a copy of the XML file to wine-patches as well. > > wn20030704_177.xml Good idea :-) but could you please send this in the format the attachment states it is (aka text/plain) - the way you post it now is very unpleasant to read. In case you think the xml-version is preferrable, then posting a link should be sufficient. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: Alsa driver status
On Thu, May 29, 2003 at 10:02:03AM +0100, Mike Hearn wrote: > Aren't they planning perhaps another small API break for ALSA 1.0? If I read the alsa list correctly, then no, nothing is planned. AFAIK they think they have the "final" api, i.e. the library interface will hopefully stay compatible. But then, they did change the API in an incompatible way between two release candidates - but as documentation progresses, theses changes are going to be documented at least :) Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology.
Re: fix compiling of libs/wine/loader.c on NetBSD
On Thu, Mar 27, 2003 at 09:12:58PM +0200, Yorick Hardy wrote: > It seems the stdint. header file should be included for > compiling on NetBSD. This reminds me: Into which deep hole did Patrik disappear? Ciao Jörg -- Joerg Mayer<[EMAIL PROTECTED]> We are stuck with technology when what we really want ist just stuff that works. Some say that should read Microsoft instead of technology.
Re: WineHQ redesign - TODO
On Sun, Mar 23, 2003 at 12:21:04AM -0500, Dimitrie O. Paun wrote: > Correct. However, I was referring to new releases of CrossOffice, > CrossOver Plugin, WineX, etc. Which I hope you agree they fit in > very nicely. Some months ago, I proposed that I'd like to see these announcements on the wine-announce mailing list, but it did look like there was no real interest. Ciao Jörg -- Joerg Mayer<[EMAIL PROTECTED]> We are stuck with technology when what we really want ist just stuff that works. Some say that should read Microsoft instead of technology.
Re: WineHQ.com - redesign
On Thu, Mar 20, 2003 at 04:59:19PM -0600, Jeremy Newman wrote: > Let me know of oddities you find, and if your browser croaks completely > or something on that order. Looking at the entry page using links (a text browser, see links.browser.org) there are some irritating '-' on the page. Otherwise: Things look good with links. Ciao Jörg -- Joerg Mayer<[EMAIL PROTECTED]> We are stuck with technology when what we really want ist just stuff that works. Some say that should read Microsoft instead of technology.
Paypal and website
Can you please add alt, height and width statements to the paypal button? It's completely invisible with konqueror otherwise (yes, I do have image loading diabled :-). The same is true for most pictures on the winehq pages. On a related topic: When will the new web pages be moved to winehq? Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: RPC marshalling patch
On Thu, Jan 30, 2003 at 05:44:35PM +0100, Ove Kaaven wrote: > does not conform > to the DCE RPC wire protocol (mostly because I don't have a description of > it... You could take a look at the Ethereal sniffer software (www.ethereal.com). It has dissectors for some of Microsofts rpc stuff. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Some more thoughts on khtml
Just two things for those thinking about khtml: 1) The kdebindings package contains C-language bindings for khtml (kde_HTML*), so C++ wouldn't be a requirement for calling khtml (this does not affect the qt-replacement api of course). 2) There is a project to port KWC to win32: KHTML Win32 Native, see http://sourceforge.net/projects/khtml-win32/ Maybe it is possible to use that. ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: VirtualDub cannot find its codecs
On Sun, Jan 19, 2003 at 08:12:02AM -0800, Duane Clark wrote:
> Please supply as diff -u, or better, create a ~/.cvsrc file that contains:
>
> cvs -z 3
> update -PAd
> diff -u
or
diff -uNRp
rdiff -uNRp
cvs -z4 -q
update -Pd
checkout -AP
status -v
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Re: Fixing include quotes
On Tue, Dec 31, 2002 at 01:30:10PM -0500, Dimitrie O. Paun wrote: > [dimi@dimi wine.src]$ find -name "*.h" | sed 's%.*/%%' | sort -u | uniq -c | sort >-rn | head -1 Isn't the result of sort -u | uniq -c always either 1 or nothing at all? ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Update to patches sgml
On Thu, Dec 19, 2002 at 12:47:51PM -0600, Jeff Smith wrote: > Leading spaces are getting dropped when I inline and even when I attach > as a TXT file. The only way it will let all my patches through > unharmed is by leaving the extension as DIFF. I have several patches > in my queue, but have been reluctant to send them out until I get this > resolved. I don't think that resolving the problems should be a requirement to actually sned patches. Send them out now and just write a short note about currently not being able to "properly" attach them. The attachment requirement is intended to increase the speed of development, not slow it down. ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Update to patches sgml
On Thu, Dec 19, 2002 at 10:36:14AM -0700, Tony Lambregts wrote: > Joerg Mayer wrote: > >Maybe you should include a step by step instruction for outlook users > >how to do that. It seems that outlook is the leading misattachment generator, > >so instead of just telling people what NOT to do, maybe you can tell > >people how to do it right. > > Well I suppose I could if I had those instructions. I jsut dug out the following mail: Message-ID: <01f801c27fc4$3060c100$c4823bd5@dmitry> From: "Dmitry Timoshkov" <[EMAIL PROTECTED]> To: "Patrik Stridvall" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Subject: Re: winapi update X-Spam-Level: "Patrik Stridvall" <[EMAIL PROTECTED]> wrote: > > On October 29, 2002 11:27 am, Patrik Stridvall wrote: > > > Anyway, I can't inline my patches the because Microsoft > > Outlook wraps > > > the lines and I sure a lot of other people that use attachments have > > > similar problems. > > > > And can't be turned off?!? Hmmm, anyway, just attach them as > > text/plain. > > I have no idea how or if it is possible to do either. This is a part of my mail sent to Guy in order to help him to send patches using Outlook Express. I hope that it will be helpful for Outlook users too. Since I was using OE to send patches, I have found a way to send diffs as attachments and without \n vs. \r\n problem. You need following two things to make it work. 1. Make sure that .diff files have \r\n line ends, because if OE detects that there is no \r\n line endings it switches to quoted-printable format attachments. 2. Using regedit add key "Content Type" with value "text/plain" to the .diff extension under HKEY_CLASSES_ROOT (same as for .txt extension). This tells OE to use Content-Type: text/plain instead of application/octet-stream. Item #1 is important. After you hit "Send" button, go to "Outbox" and using "Properties" verify the message source to make sure that the mail has correct format. You might want to send several test e-mails to yourself too. -- Dmitry. > However it seems out of scope for a style section. You are right, but only in theory. The reality is, that people easily do the "wrong" thing while trying to do the "right" thing. And that's not because they didsomething stupid, but because but because M$ products tend to know better what the users needs to do thatn the user himself :-/ > AFAIK just giving the patch a .txt > extention and attaching will solve the problem for most mailers > including outlook. Then this should be tested by people who have access to O and OE and added afterwards. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Update to patches sgml
On Thu, Dec 19, 2002 at 01:10:52AM -0500, Dimitrie O. Paun wrote: > This should read "Patches should be inlined (if you can configure your email > client to not wrap lines), or attached as text/plain attachements" Maybe you should include a step by step instruction for outlook users how to do that. It seems that outlook is the leading misattachment generator, so instead of just telling people what NOT to do, maybe you can tell people how to do it right. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: How long does it take *you* to build wine?
On Sun, Dec 15, 2002 at 10:51:59PM -0800, Dan Kegel wrote: > So how long does it take *you* to do a clean build > (just the 'make' part after 'make depend', say) of > Wine-20021125? current cvs on an athlon 550 with 192 M Ram and gcc 3.2: real47m40.902s user40m25.200s sys 3m1.410s Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Wineboot
On Thu, Dec 12, 2002 at 11:14:43AM -0500, Dimitrie O. Paun wrote: > Hmm, that message is a bit out of contest. It _is_ an external utility that > does the reboot (it's the wineboot utility), the problem is when to invoke > it. Just wondering: Why is the reboot needed? Just because M$ does it or are there valid reasons for Wine to reboot as well? What are these reasons? Can they be fixed? Should they be fixed? Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: [RFC] wrc & windres
On Thu, Dec 05, 2002 at 09:51:18AM -0600, Jeff Smith wrote: > Here is an alternative idea for dealing with command-line > incompatibility: create a link 'windres' pointing to 'wrc'. > In the program, we could determine how the program was > invoked and handle the command-line options accordingly. I like this hack much better than the previous one :) Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Reducing the header maze (warning: long, unsuitable for children)
> Now, here's my question: couldn't we build a script to automatically fix > some of these problems? Imagine this pseudocode as a bash script, > makefile, or something along those lines: > > o gather and create a table of all .c -> .h and .h -> .h dependencies > > o for each file: > o one by one, try removing each reference to a header, and see if the > affected units still compile. If they all do, permanently > remove that reference, but remember it was there Last step: Add everything back for systems that are on a different os (xbsd, x86solaris, reactos) use older/newer glibcs whatever I've forgotten While the idea is good, I think a few people won't be happy with the result - and correctly so. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: HTML Help and IWebBrowser status
On Tue, Dec 03, 2002 at 04:46:00AM -0600, Ender wrote: > That brings me to my other WIP, de-QT'ing KHTML and turning it into a > working browser implementation for WINE. So far this is actually coming > along quite well, and besides a few points it definatly makes an effective > browser and IE compatability seems to generally be good enough to keep the > majority of IWebBrowser using applications happy. I've since abandoned my > earlier hopes to keep the changes minor (in order to make it easier to > backport fixes from the main KDE cvs), simply because it was making the > code quite messy. > > Hopefully I'll have some beta code ready in a week or two, depending on > how my free time goes. I just told Dirk (one of the people putting quite a lot of time into kde) about your work and he told be the following (translated from German): > > lustiges Projekt: "de-QT'ing KHTML"... > > erzähl ihm mal von kdenox - im prinzip kdelibs dropins mit limitierter > funktionalität für khtml only. [Tell him about kdenox - which is basically a kdelibs replacement with limited functionality for khtml only] > Ausserdem gibt es then Atheos port, der einfach die (wenigen) verwendeten Qt > Klassen durch eigene Implementierung ersetzt und somit einen fast > unmodifizierten khtml tree übernehmen kann. [Then there is the Atheos port, which simply replaces the (few) used Qt classes by its own implemetation and is thus able to use an almost unmodified khtml tree] Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: strcat+strcat+strcat == baaad
On Sat, Nov 30, 2002 at 10:49:34AM -0800, Alexandre Julliard wrote: > > It's more efficient to do: > > > > sprintf(foo, "%s%s%s%s%s%s", bar1,bar2,bar3,bar4,bar5,bar6); In case you cannot be 100% sure of the lengths, it might still be worth it with snprintf, but otherwise, it's a matter of taste. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: [Fwd: [Bug 688] - make documentation produces only files as 'x6772.html']
ically use FILE.dsl as a driver style if it is found in the same directory as FILE.sgml. DocBook XML version 4 input files will be properly processed, too. Please, report bugs to Karl Eichwalder <[EMAIL PROTECTED]>. -- Ciao JÖrg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Filesystem change notifications
On Thu, Nov 14, 2002 at 01:53:46AM -0600, Ian Pilcher wrote: > but doing something -- albeit imperfect -- seems better than doing > nothing. This statement is true in many cases, but it is dead wrong when security comes into play. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Wine 0.8 TODO v0.2
On Thu, Nov 07, 2002 at 01:41:43PM -0500, Dimitrie O. Paun wrote: > To avoid proliferation of badly built packages. Hello? Iff the spec file is bad, then I'd rather fix it then hide it somewhere. I think I've heard that arguement before - was it one for open source perhaps? ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Wine 0.8 TODO v0.2
On Thu, Nov 07, 2002 at 09:30:10AM -0800, Alexandre Julliard wrote: > The spec files etc. should not be in the tree, that's right Why shouldn't thy be in the tree? Actually, I prefer to install Software (including self compiled sw) via rpm - it makes it much more comfortable to switch versions and you can be sure that there are no old versions lying around after an update - so I'd be happy if there was a file called suse-8.1.spec or so that I could use to build an rpm from the wine package. ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Wine 0.8 TODO v0.2
On Thu, Nov 07, 2002 at 11:30:40AM -0500, Dimitrie O. Paun wrote: > I don't think this is important, all we need is for Alexandre > to let them know where he wants the packages placed (via ftp in > a dir, via email, etc.) I think there is some misunderstanding as to what I intended with my remark: Maintaining a package for a distro includes a spec file, specific patches (e.g. to paths, configure, makefiles, other build tools specific stuff), Icons, desktop files etc Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Wine 0.8 TODO v0.2
On Wed, Nov 06, 2002 at 10:10:59AM +0100, Gerald Pfeifer wrote: > You wrote: > > 4. Enlist some 'official' distribution maintainers > > (at the minimum RedHat, Suse, Mandrake, Debian) ... > Many contributors (including myself) have been providing patches to > improve portability or support FreeBSD-specific features which differ > from GNU/Linux and the port should be in a decent shape. How about providing a distributions directory where the (in)official maintainers for the distributions can just check in whatever they want once they are found/named? cvs allows to give someone write permissions for just a sub-tree, so that might me a comfortable way for the maintainers to provide easy and up to date spec, dep, whatever files/patches for their distros? Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Lost Wages (round 2)
On Tue, Nov 05, 2002 at 07:00:11PM -0600, Jeremy Newman wrote: > > -- menus still don't render right in Kongy 3.0.3: > > http://www.dssd.ca/bad-konqy2.png > > Ach mein got! I blame the Konq people, it couldn't possible be MY code. > Under the very specific circumstances that things look fine with the current cvs of kde3.1 I thend to agree with you :-) > > -- maybe the rounded rectangles are a bit too oval? me too , me too, me too > picky, picky. oops > Yeah. Seems that Konq is REALLY having trouble with my style sheet. The > default theme should have sans-serif fonts. In yours it's serif. More > fodder for me to not recommend Konq. Heck, my 2.2 version renders the > site beter than your 3.0 ver. My default theme is sans serif, I'm only complaining about the classic one Keep up the good work - and in order to make we won't complain any more, you'll just have to outlive everyone on the list ;-> Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Lost Wages (round 2)
On Tue, Nov 05, 2002 at 02:38:43PM -0600, Jeremy Newman wrote: > On the home page, use one of the three theme links. I've made the > skinning engine pretty simple so more themes/skins could be added in the > future. I'd be happy with the classic theme if it wasn't for the serif font: Classic != Hard to read In the non classic themes: The headings of the boxes at the right look quite funny when there is not sufficient space to render them in one line. Thanks! Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: WineHQ menu (take 3)
On Tue, Nov 05, 2002 at 03:37:54PM -0600, Jeremy White wrote: > Well, Jeremy Newman has already fallen; if you check the latest > round of lostwages, he's already gone over to the 'dark' side . Great news... OK, so I currently have only one or two minor requests: - Please add HEIGTH and WIDTH tags to all images, as konquError currently only shows ALT-Tags if these values are there (and image loading is off of course). - Make sure the html and css code validate ok, they don't at the moment. Ciao Jörg PS: I decided to be a spoilsport and removed the everincreasing cc-list -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: WineHQ menu (take 3)
On Tue, Nov 05, 2002 at 09:37:59AM -0500, Dimitrie O. Paun wrote: > OK, we can wait for now, but being on the subject, I _really_ hope > Jeremy will give the expanded menus a chance: they are so much more > explicit, they just make the site more 'open'. And that is Good! I definitely second that: Francois Layout was *way* more usable than the folded menus. ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: WineHQ menu (take 3)
On Mon, Nov 04, 2002 at 08:07:39PM -0600, Igor Izyumin wrote: > > Yes. I use RH 8.0 (KDE 3.0.3), but these menus _always_ failed to properly > > render in Konqy. Check it out: > > > > http://24.103.156.204/bad-konqy.png > > OK, now I see what the problem is. Something is set in the HTML so that the > text makes the table wider instead of wrapping. However, Konqueror > apparently miscalculates font sizes. I can't reproduce this Problem with Konqueror CVS post KDE-3.1rc1. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Today wine's compatibility with 20 popular apps from tucows
On Sat, Nov 02, 2002 at 04:54:47PM +, Keith Matthews wrote: > Do we really want things which have serious native alternatives. The make good test cases and are good as demo applications too, because people who use Windows may know theses already and the list is obviously not a list put together for that purpose because the apps have been selected by Downloaders at tocows. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Today wine's compatibility with 20 popular apps from tucows
On Sat, Nov 02, 2002 at 04:53:03PM +0100, Carlos Lozano wrote: > Comments, improves, ... are welcomed :)) Great idea! I think you should differentiate the "Run:" line though into builtin/pure and natvie/tainted: > 4. WinZip - The most popular compression utility for Windows just got better. > >VERSION 8.1. >* Install: Yes. (Dlls installed none) >* Run: No, it needs riched20.dll to shown the text in zipped files what > includes a message, zipped files without messages works fine. * Run builtin: No, it needs riched20.dll to shown the text in zipped files what includes a message, zipped files without messages works fine. * Run native: [riched20.dll] Yes (just guessing) Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: dlls/msvcrt: msvcrt-popen-1.1
On Fri, Nov 01, 2002 at 03:16:58PM +0200, Jaco Greeff wrote:
> +/* FIXME: Don't know what this value should be, 10 seems enough as
> + * the maximum number of simultaneous _popen'ed processes
> + */
> #define POPEN_MAX_FILES 10
...
> +INT POPEN_getOpenFileSlotPos(VOID)
> +{
> +INT i = 0;
> +for (i = 0; i < POPEN_MAX_FILES; i++)
> +{
> +if (!POPEN_Files[i].fProcess)
> +{
> +POPEN_Files[i].fProcess = (MSVCRT_FILE *)POPEN_FILE_IN_USE;
> +return i;
> +}
> +}
Please output an ERR here to ask people to report that POPEN_MAX_FILES
needs to be increased.
> +return -1;
Re: Wine 0.8 TODO v0.1
On Thu, Oct 31, 2002 at 05:38:10PM -0500, Dimitrie O. Paun wrote:
> 4. Enlist some 'official' distribution maintainers
> (at the minimum RedHat, Suse, UnitedLinux, Debian)
Add Mandrake, remove UnitedLinux: UnitedLinux is a SERVER distro
(or, to be more precise: the core of several server distros).
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Re: EMF bug
On Wed, Oct 30, 2002 at 09:46:55PM -0600, Jeremy White wrote: > Near future, by the way, means that we're shipping on Friday, I'd like to see an annoucement on wine-announce when it's out. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: winapi update
On Tue, Oct 29, 2002 at 07:22:21PM +0100, Lionel Ulmer wrote: > If you name your patch files '.txt', it should detect the text/plain MIME > type and attach them accordingly, no ? According to a test someone did for me a few weeks ago, the ending is what counts, so if you name your file .txt, it IS a text file - outlook is absolutely sure of that, even if that file was previously named wine.tar.gz and puts the obviously correct type into the attachment type: text/plain Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: interrupts in when in NT version
On Thu, Oct 24, 2002 at 12:26:15PM +0200, Zsolt Rizsanyi wrote: > But the recent interrupt changes tend to cause cvs conflicts and to break it. > This patch is supposed to work only if winver is nt40 so very probably this > applies only to NT. ... > I would like if this could be fixed properly and that would work with the > safedisk patch, if thats possible. and on 28 May 2002 18:58:51 -0700, Alexandre wrote: >Laurent Pinchart <[EMAIL PROTECTED]> writes: > >> There are two patches in there. The first one sets a fault handler for the >> SharedUserData. This looks fine to me, and will probably be applied when >> memory/emulate.c will be applied. > >It still isn't clear to me why you need a fault handler at all. You >could simply put the right data into it at allocation time. > >> The second one has been written by Alexandre to fix the process suspension at >> creation time. Once again I'd like to hear from him to know what he doesn't >> like about the code, as he's the one who wrote it :-) > >The main problem is that it isn't generic enough, it only applies to >the create process request but other requests have the same problem >and should be fixed too. I'll work on a more general solution. I looks like the more general solution was never done due to time/lack of nagging reasons? Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: wine/programs/wcmd wcmdmain.c
On Thu, Oct 10, 2002 at 10:30:40AM -0700, Alexandre Julliard wrote:
> There is no way to prevent a Windows application running under Wine
> from doing everything a Unix application could do. Even if you don't
> let CreateProcess launch Unix programs the Windows app can always do a
> straight system call
This leaves just two options for the paranoid: Don't run untrusted
applications - yeah I know that comes as a surprise :-) or run Wine
inside UserModeLinux.
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Re: Registry problem
On Wed, Oct 09, 2002 at 01:01:37PM -0400, [EMAIL PROTECTED] wrote:
> Unhandled exception: unimplemented function msvcrt.dll._i64toa called in 32-bit code
>(0x40cb0052).
well, look at that:
~/work/wine/wine/dlls/ntdll> grep i64toa ../msvcrt/msvcrt.spec
@ stub _i64toa #(long str long)
@ stub _ui64toa #(long str long)
~/work/wine/wine/dlls/ntdll>
if you look at itoa (i64toa's 32 bit equivalent?) in that same file, you can
find them redirected to ntll and their actual implementation in ntdll/string.c
Looks like a trivial case of copy/paste/modify to me.
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Re: [Controversial] Developper only CVS sandbox
On Wed, Sep 25, 2002 at 10:14:26PM +0200, Lionel Ulmer wrote: > This sandbox would be closed (ie it would be a developper only Wine tree) to > NOT start another Wine fork and all development on this sandbox would be > merged back in Wine when they are ready (and then would still go the > Alexandre way of course). IMHO it should be open and be jsut another branch of winehq. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
[Alsa-devel] update of "known bugs" list (forw)
- Forwarded message from Takashi Iwai <[EMAIL PROTECTED]> - From: Takashi Iwai <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: [Alsa-devel] update of "known bugs" list Date: Thu, 19 Sep 2002 17:46:58 +0200 Hi Patrick, the following is the update of known bugs list on the web. could you update the page? * OSS emulation on WINE --> works the following workaround is necessary on some cards/chips, which support only 16bit samples. you need to set the operation mode by writing a configuration onto /proc/asound/card0/pcm0p/oss, i.e. # echo "wine 0 0 direct" > /proc/asound/card0/pcm0p/oss * intel8x0 --> fixed all three entries are solved. * ice1712 --> changed DMX-6fire frontbox is partially working (no spdif yet) * via8233 --> fixed no problems now (on cvs it's merged together with via686 as snd-via82xx driver) New entries: * es1968 capture doesn't work. * ymfpci pcm playback is not audible on toshiba tecra8100. Takashi --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel - End forwarded message - -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Heap overruns
On Mon, Sep 02, 2002 at 12:22:44AM +0300, Shachar Shemesh wrote: [many lines of history deleted] > Implementing my suggested system will: Maybe there's another solution: Someone with very intricate knowledge of wine and the x86 processor could get valgrind to work - this would provide a very powerful tool. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Problems compiling wine with Intel Compiler
On Mon, Aug 26, 2002 at 05:40:01PM +0200, Patrik Stridvall wrote:
> The Intel compiler like the Microsoft compiler probably already supports
> __int{8,16,32,64}.
>
> This will have to be changed to
>
> #if !defined(_MSC_VER) && !defined(XXX)
Or maybe a HAVE_xxx configure check?
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Re: [Bug 934] - Cpu usage is always 100%
On Thu, Aug 01, 2002 at 02:58:58PM -0500, [EMAIL PROTECTED] wrote: > We should list some cases of programs here doing this, If you don't mind downloading 16 MBytes, I have an app (actually a video turned executable) that seems to exhibit this behaviour: http://www-agrw.informatik.uni-kl.de/~jmayer/summonergeeks.exe Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: PATCH: temp fixes, again
On Sat, Jul 27, 2002 at 09:13:09AM -0700, Alexandre Julliard wrote: > The bug is that the temp file is created with mode 0666. But you can't > do a configure check for a run-time feature/bug anyway. Well, this bug doesn't really matter. If it matters, people will long have installed a fixed libc, if they don't care, it doesn't matter. There are tons of programs out there that use this function, why should wine be the one application that cares about the existence of old bugs. You are right about checking for runtime bugs, though. ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: PATCH: temp fixes, again
On Fri, Jul 26, 2002 at 01:21:05PM -0700, Alexandre Julliard wrote: > I'm not sure this is a good idea, mkstemp() is apparently buggy in old > libc versions. What do you mean by buggy? Is the result wrong or are the security features not working correctly? What are "old" libc versions? > tmpnam() is actually pretty reasonable assuming it is > used correctly, which of course is not the case everywhere but that > could be fixed. Depending on your answer to the questions above, I think the approach Marcus took was the right one. If need be, there could always be a configure check for the buggy implementation. ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Added support for APPMODE=[:]
On Tue, Jul 02, 2002 at 04:06:56PM -0400, Gregg Mattinson wrote: > - .spec files can't be compiled with -g when using Forte C. This causes static > variables to have a "random" prefix attached to their name, and prevents the > assembly code from linking to them correctly. > - Forte C has linker issues, so cui executables with main() conflicted with > main() in $WINELOADER. Renaming main() to main2() solved the issue, so I added > support to winebuild to allow the main function name to be optionally specified > in the makefile. > - Forte C does not support .previous It was replaced with a .section statement > for the appropriate section > - '.section .text' is incorrect. It should be '.section ".text"' You omitted: - Replace constants by numeric values (aka magic numbers). > -fprintf( outfile, " rec.code= 0x%08x;\n", EXCEPTION_WINE_STUB ); > +fprintf( outfile, " rec.code= 0x%08x;\n", 0x8100 ); - Inserted compiler specific compilation (as opposed to feature specific compilation) > +#ifndef __SUNPRO_C > fprintf( outfile, "\n#include \"pshpack1.h\"\n" ); > +#endif - Removed some unneeded includes. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Void functions can't return a value
On Tue, Jul 02, 2002 at 03:34:44PM -0400, Gregg Mattinson wrote:
> - void functions can't return a value, even if it is the return value from
>another void function.
Just looking at the patch a bit. This looks wrong to me. If you want to
make the changes, you should convert return xxx() into { xxx(); return }
> void WINAPI PathStripPathAW(LPVOID lpszPath)
> {
> if (SHELL_OsIsUnicode())
> - return PathStripPathW(lpszPath);
> - return PathStripPathA(lpszPath);
> + PathStripPathW(lpszPath);
> + PathStripPathA(lpszPath);<- should not be executed if condition is
>met
> }
This pattern is repeated several times.
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Re: winedefault.reg: FirstInstallDateTime value
On Sat, Jun 29, 2002 at 08:37:53PM +0200, Andreas Mohr wrote: > this adds the FirstInstallDateTime key, which is required by a program > some guy tested in the newsgroup. > +"FirstInstallDateTime"=hex:21,81,7c,23 How about adding a comment which date that is? Thanks Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Open up wine-announce to wine-related/using projects
I just found a link to xmms-winamp (http://www.emulinks.de/xmms-winamp/), a project to allow the use of winamp plugins in xmms. This is done with the help of wine or winex. Personally, I'd like to see announcements such as this, crossover and winex on wine-announce. Maybe that way a bit more awareness for the projects using wine can be gained (not to talk about my lazyness to look for such things :-) Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: How big is the Direct3D stuff?
Please move the License part of this thread to wine-license Thanks Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: linux kernel thoughts
On Mon, Jun 03, 2002 at 05:43:11PM +0200, Michael Stefaniuc wrote:
> And Linus dosn't oppose the
> idea of having a wine/windows support in the kernel:
> http://lists.insecure.org/linux-kernel/2000/Sep/1504.html .
Umm, to be more precise: Linus wasn't opposed to someting like
that at the time of the writing. He has been known to change his
mind from time to time.
ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Re: SafeDisc-1
Alexandre, there were two files in this patch. Is there a specific reason, why they were not completely applied? It looks to me that only parts of the first file were applied. Thanks Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Winelib apps and PATH
On Tue, May 14, 2002 at 09:44:07PM +0200, Sylvain Petreolle wrote: > Shouldn't we provide a default drive for /usr or > /usrlocal/bin in the config file ? This would solve > the "can't load winedbg 123456" issue that users > usually include in their first reports. > (the debugger cannot be launched because it's in > /usr/local/bin) While I think that doing something like this should really be done, I don't like mixing windows/wine executables and linux (aka native os) executables. Maybe some directory like /usr/local/win (or winebin) would be better. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: strange errors to me
On Sat, May 11, 2002 at 07:56:15PM +0200, Sylvain Petreolle wrote: > put a drive for /usr, it will leave many error > messages. > couldn't we put one in the sample config file ? I don't feel too comfortable with this, but I haven't been to happy with the current "solution" of mixing wine executables with linux executables either (I just failed to voice my discomfort then). IMHO, the proper solution would be a directory dedicated to such binaries/scripts and the assignment of a drive letter in the config file as well as an addtion to the path statement. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: DPMI RawModeSwitch, return to protected mode fix
On Sat, May 11, 2002 at 05:23:39PM +0300, Jukka Heinonen wrote:
> + /*
> + * FIXME: This routine will not work if it is called
> + *from 32 bit DPMI program and the program returns
> + *to protected mode while ESP or EIP is over 0x.
> + * FIXME: This routine will not work if it is not called
> + *using 16-bit-to-Wine callback glue function.
> + */
Shouldn't these be FIXME("...") or an ERR()? That way people would know
immediatly why their program failed.
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Re: wine/ ./configure ./configure.ac include/confi ...
On Fri, May 10, 2002 at 07:18:41AM -0700, Steven Edwards wrote: > I thought they were the same save this : > > The _snprintf vs. snprintf alternative seems to be > caused by conflicting standards: AFAIK Ansi/ISO C > requires all non-standard functions added > by the compiler to start with "_" , whereas POSIX > requires all its standard functions not to start with > "_". You are right. I misread what the patch does. Sorry. ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: wine/ ./configure ./configure.ac include/confi ...
On Thu, May 09, 2002 at 08:33:41PM -0500, Alexandre Julliard wrote: > Log message: > Steven Edwards <[EMAIL PROTECTED]> > Detect snprintf && _snprintf, use _snprintf on stupid platforms > (windows). I'm afraid that this is the wrong solution to this problem: People using sNprintf do this sometimes for security reasons. Just ignoring the length is very likely to cause some problems with applications that would have been otherwise secure (I'm thinking of chatclients etc). snprintf should either be implemented or the application simply should not work, but making a secure app insecure is not the way to go. ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: More MSVC fixes
On Sat, May 04, 2002 at 02:19:59PM -0700, Alexandre Julliard wrote: > The main problem is that you can't generate diffs for them, so > everybody has to download the full tarball every time a binary file > changes. You are right - but mainly on theory. In the real cases that have affected changes to images in wine, the diff has problably been larger than a complete gif/bmp/jpg in most cases. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: More MSVC fixes
On Sat, May 04, 2002 at 09:57:26AM +0200, Patrik Stridvall wrote: > > > > However Alexandre doesn't like binary files in the CVS > > for good reasons ... > > CVS can handle binary files no problem. Can someone please refresh my > > memory on why storing binary _images_ in CVS is such a bad idea? > > I think it is because CVS can't store the diffs between binary files. > It stores the whole file even if only one byte change. So it takes > a lot of space to store the history of the file. When you change an image, then the file changes completely in many cases anyway, so storing it in binary form just *saves* storage and bandwidth in the normal case. It's just a bit inconvenient for cvs -t fans, but that's all I can come up with right now (and there's a workaround for that). Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: patch for cups printers
Just a very late addition to this discussion: I'm using cups 1.1.12 from
Suse 8.0 and "cat file | lpr -Pprintername" works fine.
ciao
Jörg
> -if (!strncmp("LPR:",pszOutput,4))
> +if (!strncmp("CUPS:",pszOutput,5))
> + sprintf(psCmd,"|lp -d%s",pszOutput+5);
> +else if (!strncmp("LPR:",pszOutput,4))
> sprintf(psCmd,"|lpr -P%s",pszOutput+4);
> else
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Re: comm.c:COMM_BuildOldCommDCB err...
On Tue, Apr 23, 2002 at 05:43:32PM -0700, Duane Clark wrote: > Forwarded for [EMAIL PROTECTED] > + if (!strncasecmp(device,"COM",3)) strcpy(temp,device+5); > + else strcpy(temp,device); What happens, if device is "COM\0" ? Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: ALSA driver
On Sat, Apr 20, 2002 at 09:42:12PM +0200, Eric Pouech wrote: > > BTW, It's been quite a while that I'm using ALSA 0.9, so I can try to > > port your code to it. > ok, but keep both 0.5 and 0.9 inside and also protect 0.9 code when only > the 0.5 headers will be available. I don't think that this is the right way. IMHO, there should be one 0.5 and "current" alsa module for wine - they really have different apis. They have common features and an almost identical name, but that's it. It would be cleaner to copy you code completely into a separate alsa-0.9 ( or current or whatever) module and compile and install it separately. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: ALSA driver
On Sat, Apr 20, 2002 at 09:40:31PM +0200, Eric Pouech wrote: > > OK, that is mostly the disappointment speaking > > that I still won't be able to run wine with Alsa. > The point is on the current installed base of ALSA drivers ... > It just means that 0.9 installed base is almost 0 (in percentage). With Suse 8.0 now shipping 0.9 and 0.9 being in the 2.5 development kernels, the userbase will start to grow fast. > So, spending time right now on 0.9 is not the top priority (at least for > me). That is your privilege as author :-) So there is one more sound module for wine to be written, as the api has changed significantly between 0.5 and 0.9. > OTOH, since the OSS emulation in ALSA 0.5 is broken, the point is whether > we fix it (using a pure ALSA 0.5 driver in Wine), or let users live with > that (TG has disabled the HAL support Yeah, I guess I automatically assumed that alsa 0.9 would be broken with respect to mmap too :-/ Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: ALSA driver
> then, an ALSA final should be written. As the ALSA interface has greatly
> evolved between 0.5 and 0.9, the ongoing ALSA driver will need to be
> rewritten for ALSA 1.0 (aka final). Until Linux 2.6 is out, there will
> be no need for ALSA 1.0, as most of the current distros ship with either
> OSS or ALSA 0.5.
Sigh, Suse 8.0 just moved fom 0.5 to 0.9 - the Alsa developers regard
0.9 as more stable and having less bugs than 0.5. Why spend all that
time on an obsolete driver? OK, that is mostly the disappointment speaking
that I still won't be able to run wine with Alsa.
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Additional warnings (-W) revisited
Hello,
a year or more ago I started an attempt to turn on additional warnings
with gccs -W switch. The amount of additional warnings created made any
warnings useless (the current count is >2700). I've just thought about
the problem again and come up with a divide and conquer approach:
Why not turn -W on and disable the additional warnings on a per directory
basis? The idea is to turn on the additional warnings and then disable
them on a per directory/type basis by putting a file into each directory
turning off one or both of the additional warnings that occur very often
(signed/unsigned comparisons and unused parameters/variables). If both
warnings should be shown in a directory, the file may be removed.
I've attached an example patch and the initial look of the .nowarn file.
What do you think of the idea in general and this particular solution?
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Index: wine/Make.rules.in
===
RCS file: /home/wine/wine/Make.rules.in,v
retrieving revision 1.106
diff -u -r1.106 Make.rules.in
--- wine/Make.rules.in 2 Apr 2002 02:58:45 - 1.106
+++ wine/Make.rules.in 16 Apr 2002 23:04:02 -
@@ -112,7 +112,7 @@
.SUFFIXES: .mc .rc .mc.rc .res .spec .spec.c .spec.def .glue.c .pl .ok
.c.o:
- $(CC) -c $(ALLCFLAGS) -o $@ $<
+ $(CC) -c $(ALLCFLAGS) `test -f .nowarn && cat .nowarn` -o $@ $<
.s.o:
$(AS) -o $@ $<
Index: wine/configure
===
RCS file: /home/wine/wine/configure,v
retrieving revision 1.276
diff -u -r1.276 configure
--- wine/configure 12 Apr 2002 01:04:32 - 1.276
+++ wine/configure 16 Apr 2002 23:04:05 -
@@ -9310,7 +9310,7 @@
if test "x${GCC}" = "xyes"
then
- CFLAGS="$CFLAGS -Wall"
+ CFLAGS="$CFLAGS -Wall -W"
echo "$as_me:$LINENO: checking for gcc strength-reduce bug" >&5
echo $ECHO_N "checking for gcc strength-reduce bug... $ECHO_C" >&6
if test "${ac_cv_c_gcc_strength_bug+set}" = set; then
-Wno-unused -Wno-sign-compare
Re: Artilcle - loading Windows DLL's under Linux
Please move this thread to wine-license! Thank you very much! Jörg On Mon, Feb 25, 2002 at 02:25:18PM -0700, Brett Glass wrote: > At 03:41 PM 2/25/2002, Nick Temple wrote: > > >I am working on an article about how to load Windows DLL's under Linux. This >system is for stand-alone Linux applications that only need to use some of the logic >in a single Windows DLL, not a full WINE implementation. > > > >The code has been "borrowed" and tweaked from the avifile distribution (which is >GPL'd), originally borrowed from WINE (BSD license), and will be re-released under >the GPL or LGPL once the article is published. > > It is not legal to do this. You can't change the license on existing code. > If it was originally licensed under the WINE X11 license, you cannot legally > change that. Which is a good thing. No one should be allowed to stamp a > virulent license on someone else's work without permission. > > --Brett Glass > > -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Wine, enthusiasts, businesses and the agony of the license
On Sat, Feb 09, 2002 at 10:12:28PM +0100, Fredrik Ohrn wrote: > > Result: The group 2 only companies *can't* release their sources any more > > if they want to stay in business. > > > > I assume you mean the other way round? Of course - sorry. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Wine, enthusiasts, businesses and the agony of the license
Fredrik,
very nice writeup. It actually shows where the current discussion has gone
wrong. Finding out the *requirements* first, then comparing them with the
current situation and only as a next to last step decide on a license (be
it an already written license or a completely new one or a modification of
an existing license). The last step would be the license change itself.
On Sat, Feb 09, 2002 at 11:40:54AM +0100, Fredrik Ohrn wrote:
> Another observation is that companies in group 1 are in direct competition
> with each other, so they want closed source. If TransGaming released their
> DirectX work BSD style, Lindows would quickly be there to appropriate it.
You miss one case here: Companies in group 1 that also want to make money
with group 2s business model. They could do that easily and it would give
them a distinct competitive advantage over the group 2 only type enterprises.
Result: The group 2 only companies *can't* release their sources any more
if they want to stay in business.
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Re: Wine license change
On Wed, Feb 06, 2002 at 07:51:04PM -0500, Dimitrie O. Paun wrote: > Yeah, that could work. But I still don't understand your objections about > the proprietary drivers: LGPL would work just fine with that. What's your > concern? Look at the copy protection stuff that transgaming have added to their tree: they licensed it and thus quite likely can't publish the source for this - but I still want to see this in the binary only releases they make :-) Other scenarios I can imagine: drivers for hardware - think of a company that wants to port their software to Linux via wine but continue using a dongle or something like that: the dongle code is quite likely to go into the kernel itself (and may need some support for that by the wineserver). Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Wine license change
On Wed, Feb 06, 2002 at 04:54:05PM -0600, Jeremy White wrote: > Some recent events have occurred that have made me change my opinion > about a Wine license change. ... > However, with some recent events I cannot disclose, it is clear to me > that the opportunity for Wine to be used in a proprietary product is > too tempting and has caused some harm to the Wine project. Based on > experience, I feel strongly that the potential for harm is great > enough that CodeWeavers needs to take two actions. First, we would > like to release all new code we develop under an LGPL style license. > Second, I would like to open another call for a license change and > thereby strongly add my voice to Alexandre's. OK, when the last discussion was going on, I started out with the opinion that the change would be good and changed it to not so good, because if proprietary stuff that *is* part of the windows kernel (or drivers) needs to be implemented, this can't be done with an LGPLed wine. My final idea (which I never mailed) was, that maybe a X11-licensed kernel (including wineserver and driver emulation) and LGPLed dlls for the rest would be the best solution. ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: (FWD) Announcing wineconf 2002
First the huge Office 2000 patch from Codeweavers, now the wineconf invitation from lindows. So we might call it official that lindows is using wine and they DO give back their patches? ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Another Potential Slave... I mean Programmer
On Sat, Feb 02, 2002 at 03:52:32PM -0600, Steve Langasek wrote: > If people have issues with the existing sound daemons, their time could > almost certainly be better spent working on the implementations /behind/ > the APIs instead of creating the sound library du jour. It seems a > terrible waste of programmer time to try to maintain as many as four > library layers interposed between Wine programs and the audio hardware. IIRC, gstreamer is a audio video framework, that provides data in and *synchronized* audio and video out. So you should not compare it with esound, alsa etc but with xine-lib or something like that. They just provide autio out for those drivers. ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: DESTDIR support for make install
On Thu, Jan 31, 2002 at 02:33:53PM -0800, Alexandre Julliard wrote: > But "make install prefix=/home/myaccount/rpms/tmp" should do exactly > the same thing, unless I missed something. You can run make with one > prefix and make install with another one, that's a feature. I didn't know about this feature, but it works fine :) Thanks! Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: ROTD (Rant Of The Day): patches
Hmm, looks like after the failed attempt for a flame war on version numbering,
you are trying to start one on mail clients 8-=)
On Thu, Jan 31, 2002 at 03:52:19PM -0500, Dimitrie O. Paun wrote:
> I've come to _hate_ diffs attached as Application/OCTET-STREAM. Can you
> please, Please, PLEASE, attach them as Text/PLAIN?
I'd like to see properly labeled attachment types too, be they text/plain,
mime, gzip or whatever.
> I use Pine over a ssh connection to read wine-{devel,patches}, and I can
> simply view the Text/PLAIN attachments, whereas I have to:
Hmm, the problem you mentioned is one of the two major reasons that drove
me away from pine towards mutt. I'm now running a (n almost) properly
configured mutt and don't have these problems any more because app/o-s
are just viewed with the text viewer after pressing v and selecting the
attachment (which takes maybe 2 seconds). I don't like your idea of
1 patch per mail, as this would probably take me 2-3 additional seconds
per mail (poor me).
ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Re: DESTDIR support for make install
On Thu, Jan 31, 2002 at 01:09:28PM -0800, Alexandre Julliard wrote: > > wine currently doesn't support the DESTDIR flag commonly used by > > packagers. The patch I've attached fixes this. > > Could you explain this a bit more? Why can't you use the existing > $prefix to do the same thing? When creating a spec file for rpms, you basically prepare the source (unpack, apply patches), then run configure, make and --->make install Because the result is intended not to be run but to be packaged, you don't install into e.g. /usr/local directly, but into something like /home/myaccount/rpms/tmp/usr/local. Later, when you *install* the package, you want the binaries to be installed into /usr/local and all paths compiled into the binaries to point to /usr/local/... too. So changing prefix is not the way to go. DESTDIR allows to do the install via "DESTDIR=/home/myaccount/rpms/tmp make install" instead of doing all the steps from "make install" manually. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: How about sponsoring from IBM?
On Fri, Jan 11, 2002 at 03:47:56PM -0200, Roland wrote:
> If the assumption is true I think those 10 Million would be the best spent
> part of that 1 Billion.
It looks like IBM spends its money on the products they themselvs use
heavily, as well as training and making the name of Linux more popular
(aka advertising/PR). I may have missed it but I haven't seen IBM spend
money on a Linux(related) project just to further the project. If they
wanted to spend $10e7 just to improve programs/tools just for the "good"
of it I would be sad to see this money spent on wine. I'd like to see
it spent on the development/improvement of *native* Linux apps that
fulfill the need of current Windows users.
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Re: We *really* need a development model change !
On Wed, Dec 26, 2001 at 10:26:27AM -0800, Andriy Palamarchuk wrote:
> C Unit test frameworks I found after a quick search:
> http://check.sourceforge.net/
> http://people.codefactory.se/~spotty/cunit/
> http://freshmeat.net/projects/autounit/
>
> C++:
> http://sourceforge.net/projects/cppunit/
Seen on /. two days ago:
http://www.codesourcery.com/qm/qmtest
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
T@x2001: Linuxport via Wine
Just found the following at the SuSE portal pages (German only): http://portal.suse.de/de/content/reports/tax2001.html Rough translation on the introductory paragraph: The program t@x by Buhl Data has been around for the Windows platform for some years. This year, the current version T@x2001 has been made available for the Linux OS for a first time. In order to do this the Windows emulator Wine was used. Wine allows using Windows applications running Linux. This emulator has been modified to work with t@x2001. The summary as far as Wine is concerned: The program should be more stable and faster. Does anyone know which modifications were made to wine? Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Speeding up wineserver synchronization objects with shared memory
Ove, On Sat, Feb 24, 2001 at 12:06:07PM +0100, Ove Kaaven wrote: > There's no such thread, and will never be such a thread (having the > wineserver calling into client threads is an inherently unstable design). I think I've read this before, when the topic was FindWindow. IIRC that thread never came to any conlusion/solution. Will the same happen to this topic too? If it looks like these problems could be solved by some sort of server calling into the client then why not do this until someone finds a better solution? On the other hand, if this mechanism doesn't work on a technical basis, that is something I can live with. "inherently unsable design" could be both: People simply not liking the idea of this and the corresponding design implications or it could be just another variant of "it won't work any better than the solution proposed so far". Which one is it? Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
AFM-Handling problem
Moin, Marcus last patch to add default paths for afm files triggered a bug: Inside my font dirs, there is a directory that contains gzipped afm files. After I unzipped these files, wine started up again. Not nice. Ciao Jörg PS: This is the directory *after* decompression of the .afm.gz files: jmayer@alice:/usr/X11R6/lib/X11/fonts/Type1 > ls UTBI.afm c0419bt_.afm c0632bt_.afm cour.afmcursor.pfa lcdxro.afm UTBI.pfa c0419bt_.pfb c0632bt_.pfb cour.pfaencodings.dir lcdxro.pfa UTB_.afm c0582bt_.afm c0633bt_.afm courb.afm fonts.dir lcdxrr.afm UTB_.pfa c0582bt_.pfb c0633bt_.pfb courb.pfa fonts.scalelcdxrr.pfa UTI_.afm c0583bt_.afm c0648bt_.afm courbi.afm lcdxmo.afm lcdxso.afm UTI_.pfa c0583bt_.pfb c0648bt_.pfb courbi.pfa lcdxmo.pfa lcdxso.pfa UTRG.afm c0611bt_.afm c0649bt_.afm couri.afm lcdxmr.afm lcdxsr.afm UTRG.pfa c0611bt_.pfb c0649bt_.pfb couri.pfa lcdxmr.pfa lcdxsr.pfa jmayer@alice:/usr/X11R6/lib/X11/fonts/Type1 > -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: PATCH: afm loader
Moin Marcus, you codeed some thing like this in a few places: > + char afmfn[256]; > + strcpy(afmfn,afmdir); directories and filenames may be longer than 256 charaters. If you use such a value you should at least use strncpy or use FILENAME_MAX from stdio.h (if that's the right one). Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: documentation patch
On Fri, Jan 19, 2001 at 11:44:43AM -0800, Alexandre Julliard wrote: > You could use a configure variable, like we do with @XFILES@ for > conditional X11 compilation. In this case I don't think it is > justified though; the doc is not built by default, so there is no > point in making it conditional. People who don't have the docbook > tools simply shouldn't run 'make' in the doc directory. Maybe I understand you incorrectly, but a plain text or html version of the documentation should be provided with the normal tarball, just like we provide not only configure.in but also configure because there would be so many more questions/help requests from people who have problems with autoconf. How can we point people to the documen- tation if it is hard to read? Pointing them to an external source isn't really helpful: a readable documentation should go with the package. Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: documentation patch
On Thu, Jan 18, 2001 at 09:09:35AM -0600, Jeremy White wrote: > then documentation/wine-doc contains a nice set of HTML pages that > can be used by the user (or tarballed into an RPM ). I've had problems building the documentation on a SuSE 7.0 (not solved). I think providing a Text version with the Sources would be nice - IMO it's comparable to providing configure in addition to configure.in Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Xine - another app using wine code
Another application using some wine code: http://xine.sourceforge.net/ 08.01.2001: release of xine 0.3.4, bringing you win32 video codec support (via mechanisms provided by wine and projects like MPlayer ), improved debian packages, gui bugfixes, build improvements on k6/k7 cpus, a teletux video output driver and minor speedups via new compiler flags and 3Dnow! support. -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Orphaned .c files?
Hello, I was just checking for undocumented wine.conf(5) options and found two files in the process that seem to be no longer compiled. So I looked at the tree after a complete build. Here's a list of all files that don't have a matching .o or executable and are not in libtest/ or programs/: ./dlls/opengl32/opengl_norm.c ./dlls/opengl32/opengl_ext.c ./dlls/opengl32/wgl.c ./dlls/ddraw/mesa.c ./dlls/ddraw/d3ddevice/mesa.c ./dlls/ddraw/d3ddevice/main.c ./dlls/ddraw/dga2.c ./dlls/ddraw/dga.c ./dlls/ddraw/d3dmaterial.c ./dlls/ddraw/d3dtexture.c ./dlls/ddraw/d3dlight.c ./dlls/ddraw/d3dexecutebuffer.c ./dlls/ddraw/d3dviewport.c ./dlls/ddraw/d3dcommon.c ./dlls/ddraw/direct3d/mesa.c ./dlls/ddraw/direct3d/main.c ./library/checklink.c ./tools/cvdump/cvload.c ./tools/cvdump/cvdump.c ./tools/cvdump/cvcrunch.c ./tools/wmc/language.c ./debugger/dbgmain.c Which of these files are still needed, which can go? ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Avifile library
Hello, I just stumbled on the avifile library on freshmeat (http://divx.euro.ru/). It's a library that loads the native Windows decoders (with some code from Wine and Twin). IIRC AVI support in Wine is still in the "use the native libs" state. Maybe we can use some of the code of avifile? (haven't really looked at it though). ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: PATCH: INT13 (READ/WRITE SECTORS)
On Fri, Nov 17, 2000 at 12:57:18PM +0100, Frank Cornelis wrote: > I wrote a little patch to support INT 13 read/writing of sectors on a > floppy disk. > If it's OK, please merge it with the CVS tree. ... > + sprintf (dev_name, "/dev/fd%d", drive_nr); ... > + sprintf (dev_name, "/dev/fd%d", drive_nr); ... Is there a reason why you don't use the devices from the wine.conf file? (Sometimes it might be helpful to work with a loop device instead of the real drive). Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: FindWindow warning
On Sat, Nov 11, 2000 at 02:54:55AM +0100, gerard patel wrote: > That's a following of the address space separation. I knew that far. > Although the Wine processes > are separated, the windows handles are still generated by each Wine process > through a local mechanism based on memory allocation. The Wine server does not > generate them, and as such these handles have no meaning for another process. > > For example, it can happen that 2 windows of different processes have the same >handle. Hmm, I was not aware of this, but now that I read it it sounds "trivial". > So it does not make sense to do a FindWindow for a window in another process > in current Wine. > The main problem for fixing that is probably to not having performance going > down the drain :-) I wanted to add the fixme 1) to remind people about this open prolbem. 2) Inform users about a probable reason for problems (specially with installers) and 3) find out how often this FIXME occurs. If it rarely occurrs we might think of a way to fix this in an expensive way if the only case that is really affected by this is this case. That's why I wanted to know whether this is the only place where I need to add the FIXME. While I'm typing this I have the following ideas (and followup questions): When we run into this FIXME, call the wineserver to find out. So we need to a) add a mechanism that allows the wineserver to call FindWindow for each process. If it is given a positive response (HWND != 0), then it will add it to some internal translation table and return a HWND that can always be identified as coming from the server. b) find out which operations are used/allowed to operate on other processes HWNDs c) add handling of the special functions in both directions (calling to the server and being called by the server). Does the above make sense? Ciao Jörg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
FindWindow warning
Is the following FIXME correct (and the comment as well)?
Ciao
Jörg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Index: wine/windows/win.c
===
RCS file: /home/wine/wine/windows/win.c,v
retrieving revision 1.104
diff -u -r1.104 win.c
--- wine/windows/win.c 2000/11/02 20:08:59 1.104
+++ wine/windows/win.c 2000/11/10 21:36:28
@@ -1576,6 +1576,10 @@
}
}
retvalue = 0;
+/* In this case we need to check whether other processes
+ own a window with the given paramters on the Desktop,
+ but we don't, so let's at least warn about it */
+FIXME("Returning 0 without checking other processes\n");
end:
WIN_ReleaseWndPtr(pWnd);
return retvalue;
Re: docu/wine update *sigh*
Alexandre, while talking about documentation. Your last patches broke the "--debugmsg help" feature. How should we handle this? a) write a tool to collect the info and add it in the old place? b) add it to the manpage (maintainance problems) c) ??? Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Re: Warning fixes - please review
On Sun, Nov 05, 2000 at 09:34:13PM -0800, Alexandre Julliard wrote: > Changing variables to unsigned when they are clearly never negative is > OK; but renaming 'i' to 'n' and adding unnecessary type casts are not > good ideas IMO. I basically renamed the i -> n to make sure that I have definitely looked at all instances of the variable. In at least 1 case adding a new variable was actually necessary. It is just an aid for me, so if you want, I can rename them back before actually sending further patches. Just tell me. To the second comment: I would never add "unnecessary" type casts :-) but that's based on my very limited programming experience. If you have something specific in mind, please let me know. Thanks Joerg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
Warning fixes - please review
Hello,
I'm trying to get rid of some of the signed/unsigned comparison and
unused initializer warnings that you get when compiling with -Wall -W.
So I thought that tools/ would be a good start - oh well... please
have a look at the attached results of this attempt and let me know
whether you think that what I did is correct (aka doesn't add errors)
and where you think I should have done things differently.
The following things were left unresolved for now:
- tools/spec32.c: 110 unused 'nr_names': It looks like some of the
nb_names should be nr_names, but I don't know which.
- tools/wrc/readres.c: 374ff the alignment calculation looks a bit
weird to me (in case ressize & 3 == 0)
Any hints / improvements for the points above?
Ciao
Joerg
PS: Earlier this evening there were 3260 warnings (2357 unused params,
864 signed/unsigned comparison, 39 others). I'm trying to take up
the task to reduce that number and reveal some bug in doing so :-)
So if you don't agree with what I'm doing and how I'm doing it:
Now is the best time to let me know.
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
Changelog: <[EMAIL PROTECTED]>
First try to get rid of all warnings in the tools/ subtree.
Index: wine/configure.in
===
RCS file: /home/wine/wine/configure.in,v
retrieving revision 1.155
diff -u -r1.155 configure.in
--- wine/configure.in 2000/10/23 21:32:05 1.155
+++ wine/configure.in 2000/11/05 23:47:10
@@ -435,7 +435,7 @@
if test "x${GCC}" = "xyes"
then
- CFLAGS="$CFLAGS -Wall"
+ CFLAGS="$CFLAGS -Wall -W"
AC_CACHE_CHECK( "for gcc strength-reduce bug", ac_cv_c_gcc_strength_bug,
AC_TRY_RUN([
int main(void) {
Index: wine/tools/bin2res.c
===
RCS file: /home/wine/wine/tools/bin2res.c,v
retrieving revision 1.6
diff -u -r1.6 bin2res.c
--- wine/tools/bin2res.c2000/02/26 13:17:59 1.6
+++ wine/tools/bin2res.c2000/11/05 23:47:14
@@ -102,7 +102,7 @@
int insert_hex (char * infile, FILE * outfile)
{
- int i;
+ unsigned int n;
int fd;
struct stat st;
@@ -119,12 +119,12 @@
}
fprintf (outfile, "{\n '");
- i = 0;
+ n = 0;
while (1)
{
- fprintf(outfile, "%02X", p_in_file[i]);
- if (++i >= st.st_size) break;
- fprintf(outfile, "%s", (i == (i & 0xfff0)) ? "'\n '" :" ");
+ fprintf(outfile, "%02X", p_in_file[n]);
+ if ((int)++n >= st.st_size) break;
+ fprintf(outfile, "%s", (n == (n & 0xfff0)) ? "'\n '" :" ");
}
fprintf (outfile, "'\n}");
munmap(p_in_file, st.st_size);
Index: wine/tools/fnt2bdf.c
===
RCS file: /home/wine/wine/tools/fnt2bdf.c,v
retrieving revision 1.9
diff -u -r1.9 fnt2bdf.c
--- wine/tools/fnt2bdf.c2000/07/25 12:25:41 1.9
+++ wine/tools/fnt2bdf.c2000/11/05 23:47:14
@@ -493,7 +493,7 @@
size -= s;
offset = s + return_data_value(dfShort, &mz_header.e_lfanew);
-if( size <= sizeof(NE_TYPEINFO) ) return FILE_ERROR;
+if( size <= (int)sizeof(NE_TYPEINFO) ) return FILE_ERROR;
retval = FILE_DLL;
}
else if( s == 0x300 || s == 0x200 ) /* maybe .fnt ? */
@@ -575,7 +575,7 @@
}
lseek( fd, offset, SEEK_SET );
- if( read(fd, lpfont, length) != length )
+ if( read(fd, lpfont, length) != (int)length )
{
fprintf(stderr, errorDLLRead );
exit(1);
Index: wine/tools/winebuild/main.c
===
RCS file: /home/wine/wine/tools/winebuild/main.c,v
retrieving revision 1.9
diff -u -r1.9 main.c
--- wine/tools/winebuild/main.c 2000/11/05 04:49:13 1.9
+++ wine/tools/winebuild/main.c 2000/11/05 23:47:15
@@ -147,12 +147,12 @@
/* parse options from the argv array and remove all the recognized ones */
-static void parse_options( char *argv[] )
+static void parse_options( int argc, char *argv[] )
{
const struct option *opt;
int i;
-for (i = 1; argv[i]; i++)
+for (i = 1; i < argc; i++)
{
for (opt = option_table; opt->name; opt++)
if (!strcmp( argv[i], opt->name )) break;
@@ -175,7 +175,7 @@
int main(int argc, char **argv)
{
output_file = stdout;
-parse_options( argv );
+parse
Expressions always evaluate to true/false
Hello, I just finished compiling wine with an additional -W flag. From the 18273 warnings this generated, at least 16 are probably of interest: dispdib.c:75: warning: comparison of unsigned expression < 0 is always false hglobalstream.c:595: warning: comparison of unsigned expression < 0 is always false oleobj.c:279: warning: comparison of unsigned expression < 0 is always false oleobj.c:638: warning: comparison of unsigned expression < 0 is always false event.c:541: warning: comparison of unsigned expression >= 0 is always true listview.c:1593: warning: comparison of unsigned expression >= 0 is always true listview.c:1596: warning: comparison of unsigned expression >= 0 is always true typelib.c:2630: warning: comparison of unsigned expression >= 0 is always true typelib.c:2863: warning: comparison of unsigned expression >= 0 is always true variant.c:3957: warning: comparison of unsigned expression < 0 is always false variant.c:4057: warning: comparison of unsigned expression < 0 is always false internet.c:796: warning: comparison of unsigned expression < 0 is always false internet.c:844: warning: comparison of unsigned expression < 0 is always false sync.c:36: warning: comparison of unsigned expression < 0 is always false resource.c:212: warning: comparison of unsigned expression >= 0 is always true services.c:57: warning: comparison of unsigned expression >= 0 is always true OK, maybe I can find something else of interest. Ciao Joerg -- Joerg Mayer <[EMAIL PROTECTED]> I found out that "pro" means "instead of" (as in proconsul). Now I know what proactive means.
16-bit App Crash (maybe in SWITCHSTACKTO)
Hello,
I tried to run a 16 bit app and it crashed. The famous last words are
in SWITCHSTACKTO. I did a --debugmsg +all but I've included only a few
lines, as the location seems obvious. Ideas anyone?
Thanks
Joerg
--
Joerg Mayer eMail: <[EMAIL PROTECTED]>
Give an engineer a problem and a curious form of time dilation occurs /AC
trace:selector:SELECTOR_FreeBlock (228f,1)
trace:ldt:LDT_SetEntry entry=0451 base= limit=0 bytes 16-bit flags=rw-
trace:global:GlobalHandle16 00ff
Ret KERNEL.185: GLOBALDOSFREE() retval=0x ret=1eef:15f9 ds=1ef7
trace:global:GlobalHandle16 00ff
Call KERNEL.18: GLOBALLOCK(0x2297) ret=1eef:22f2 ds=1ef7
trace:global:WIN16_GlobalLock16 (2297) -> 2297
trace:global:GlobalHandle16 00ff
Ret KERNEL.18: GLOBALLOCK() retval=0x2297 ret=1eef:22f2 ds=1ef7
trace:global:GlobalHandle16 024f
RET NL.235: _SNLMAL() retval = 2297:0012 ret=1abf:9629
trace:heap:HeapFree (4047,0002,41fa2830): returning TRUE
trace:global:GlobalHandle16 024f
trace:global:GlobalHandle16 00ff
Call KERNEL.15: GLOBALALLOC(0x0040,0x4e20) ret=1abf:98bd ds=1c6f
trace:global:GLOBAL_Alloc 2 flags=0040
trace:virtual:VirtualAlloc 41fb 0001 1000 0040
trace:virtual:VIRTUAL_SetProt 41fb-41fb c-rWx
View: 41eb - 41fb -1
41eb - 41fb c-rWx
trace:heap:HeapAlloc (4047,0002,4e20): returning 41fae92c
trace:ldt:LDT_SetEntry entry=0438 base= limit=1 bytes 16-bit flags=rw-
trace:ldt:LDT_SetEntry entry=0438 base=41fae92c limit=04e1f bytes 16-bit flags=rw-
trace:global:GlobalHandle16 00ff
Ret KERNEL.15: GLOBALALLOC() retval=0x21c7 ret=1abf:98bd ds=1c6f
trace:global:GlobalHandle16 00ff
Call KERNEL.18: GLOBALLOCK(0x21c7) ret=1abf:98c8 ds=1c6f
trace:global:WIN16_GlobalLock16 (21c7) -> 21c7
trace:global:GlobalHandle16 00ff
Ret KERNEL.18: GLOBALLOCK() retval=0x21c7 ret=1abf:98c8 ds=1c6f
trace:global:GlobalHandle16 00ff
Call KERNEL.108: SWITCHSTACKTO(0x21c7,0x4e20,0x) ret=1abf:98ed ds=1c6f
trace:task:SwitchStackTo16 old=0607:7f08 new=21c7:4e20
trace:global:GlobalHandle16 00ff
Ret KERNEL.108: SWITCHSTACKTO() retval=0xe92c ret=1abf:98ed ds=1c6f
trace:seh:EXC_RtlRaiseException code=c0fd flags=0
08203830: exception_event(
record={code=c0fd,flags=0,rec=(nil),addr=0x98ed,params={}, first=1,
context={flags=,eax=e92c,ebx=0012,ecx=,edx=,esi=,edi=a242,ebp=7f84,eip=98ed,esp=40ec4dda,eflags=00010202,cs=1abf,ds=1c6f,es=2297,fs=,gs=,dr0=,dr1=,dr2=,dr3=,dr6=,dr7=,float={,,,,,,,,,,,,,,,,,,,,,,,,,,,}}
)
08203830: exception_event() = 0 { status=0 }
trace:seh:EXC_CallHandler calling handler at 0x4017b1f0 code=c0fd flags=008203830:
exception_event( record={code=c0fd,flags=0,rec=(nil),addr=0x98ed,params={},
first=0,
context={flags=,eax=e92c,ebx=0012,ecx=,edx=,esi=,edi=a242,ebp=7f84,eip=98ed,esp=40ec4dda,eflags=00010202,cs=1abf,ds=1c6f,es=2297,fs=,gs=,dr0=,dr1=,dr2=,dr3=,dr6=,dr7=,float={,,,,,,,,,,,,,,,,,,,,,,,,,,,}}
)08203830: exception_event() = 0 { status=0 }
Re: debugstr.c patch
On Wed, 14 Jun 2000, Dmitry Timoshkov wrote:
> Print full ansi char set (from 32 to 255), not only from 32 to 126,
> print other values in hex.
Umm, would that print the characters from 128 to 128+31 too? If so,
I don't think that should be done.
Ciao
Jörg
--
Joerg Mayer eMail: <[EMAIL PROTECTED]>
Give an engineer a problem and a curious form of time dilation occurs /AC
debugstr.c.diff
Freshmeat hits
Hello, someone posted to the ethereal developers list, that Ethereal is currently ranked 6th. Now guess the ranking of wine. (http://freshmeat.net/about.php) - Spoiler ahead - :-) top 50 application hits 01: Wine 101223 02: cdrecord 97942 03: Licq 87029 04: ssh 86579 05: Gnapster 78615 06: Ethereal 70292 07: Netscape Communicator 68867 08: Linuxconf 66197 09: BladeEnc 61975 10: nmap 61433 It looks like I have definitely underestimated the interest in wine so far. Ciao Joerg
