wine-devel February 2006

wine-devel@winehq.org

142 participants
259 discussions

Re: Server Requirements
by Tony Lambregts 24 Feb '06

24 Feb '06

Gomez, Felix wrote: > Hello... > > Does Wine run on CentOS 4 (RHEL4) for IBM zSeries/s390? > You may be able to compile wine on this architecture and run Winelib applications ( http://www.winehq.org/site/docs/winelib-guide/index ) but running regular windows applications is a different matter ( http://www.winehq.org/site/docs/wine-faq/index#UNDER-WHAT-PLATFORMS-WILL-WI… ). Bochs ( http://bochs.sourceforge.net/ ) is your best bet for getting windows applications running I am not sure if anyone has actually tried to get Wine to compile on IBM zSeries/s390, you may be the first. I for one am curious about the results of an attempt. If you do try to compile wine on this machine please let us know the results. -- Tony Lambregts

1 0

Re: advpack [1/3]: Factor out loading the advpack API [RESEND]
by Alexandre Julliard 24 Feb '06

24 Feb '06

"James Hawkins" <truiken(a)gmail.com> writes: > @@ -256,21 +268,9 @@ static void translateinfstring_test() > > START_TEST(advpack) > { > - HMODULE hdll; > - > - hdll = LoadLibraryA("advpack.dll"); > - if (!hdll) > - return; > - > - pGetVersionFromFile = (void*)GetProcAddress(hdll, "GetVersionFromFile"); > - pDelNode = (void*)GetProcAddress(hdll, "DelNode"); > - pTranslateInfString = (void*)GetProcAddress(hdll, "TranslateInfString"); > - if (!pGetVersionFromFile || !pDelNode || !pTranslateInfString) > - return; > + init_function_pointers(); Why are you removing the pointer checks? -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Debugging
by Juan Lang 24 Feb '06

24 Feb '06

> I appreciate the tip about falling back on the relay debug channel, > but may I ask how you know the problem is with BlockInput not existing? > Is there something from the output that I'm not understanding, or do > you just know that because you're familiar with the kernel32.dll > code? Molle's right--it just looks suspicious, since it's the last thing that's called before ExitProcess. I didn't copy-paste any more of the log, but there were a whole bunch of GetProcAddress calls prior to this that succeeded, which raises the probability that this was the cause. And, as Molle suggested, a quick glance at the kernel32 code shows that BlockInput is missing. As far as how did I spot this in the log--well, that's just experience. You can learn it pretty quickly though, especially when an app dies early. I just scroll through a log from the end toward the beginning, and look for a change in pattern on the screen. Different things are starting to happen there, so I slow down for a closer look. If it looks like normal shutdown code--and there's usually hundreds of lines of this stuff--I ignore it and move on. As far as how to deal with this, try modifying kernel32.spec to add a stub for BlockInput, like: @ stub BlockInput and see if the program gets any further. Chances are it'll crash somewhere else down the line, so you'll have to do the usual wash-rinse-repeat. You should also take a look through KeePass's source code and try to find out what's going on. --Juan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Re: Debugging
by Juan Lang 24 Feb '06

24 Feb '06

Hi Rich, the key one to use is relay. WINEDEBUG=relay tells you every API function that's called. It can be a bit overwhelming, but it's what you fall back on when nothing else is working. I downloaded and tried it, and scanned backwards in my relay trace a good distance till I saw some failure. Here's what I think it is: 0009:Call kernel32.GetProcAddress(20290000,0052b895 "BlockInput") ret=0052cc6a 0009:Call ntdll.RtlInitAnsiString(73ccfe20,0052b895 "BlockInput") ret=201d2c3e 0009:Ret ntdll.RtlInitAnsiString() retval=00000000 ret=201d2c3e 0009:Call ntdll.LdrGetProcedureAddress(20290000,73ccfe20,00000000,73ccfe1c) ret=201d2c4d 0009:Ret ntdll.LdrGetProcedureAddress() retval=c000007a ret=201d2c4d 0009:Call ntdll.RtlNtStatusToDosError(c000007a) ret=201d2c7d 0009:Ret ntdll.RtlNtStatusToDosError() retval=0000007f ret=201d2c7d 0009:Ret kernel32.GetProcAddress() retval=00000000 ret=0052cc6a 0009:Call kernel32.ExitProcess(0052cb10) ret=0052cc7b That is, somebody's trying to get the function BlockInput from kernel32.dll, and it isn't there, so the program exits. I don't know if this is in MFC somewhere, or in the program's source. Luckily the source is available, so you might be able to proceed. Hope that helps, --Juan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 2

Hotkey
by Christian Gmeiner 24 Feb '06

24 Feb '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all. I want to fix the hotkey stuff in user.dll. Now i have asked at xorg mail list and thy told me that i should use acpid to do hotkey stuff. Now i think we should to hotkey stuff internal in wine: Have a hash list to save hotkeys and check every time a user presses a button, if there are some pressed other too. If this is also true, look if it is a hotkey and send to the correct window the correct message. What do you think about this? Thanks, Christian - -- Christian Gmeiner - student of computer science http://dxr3plugin.sf.net http://itb04.ath.cx http://javamill.ath.cx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD/mWCDwe2AbwGBA8RArAOAJ9mfjNBHsdyafLp2exPmY5idH/iFwCfQUjV 4volZ4aoTZNXNxQUtLQCszw= =W3ub -----END PGP SIGNATURE-----

1 0

Guitar Rig 2 in Linux/Wine
by Michael Ost 23 Feb '06

23 Feb '06

We are interested in getting the new Guitar Rig 2 USB foot controller supported in Linux/Wine. It's described here: http://www.native-instruments.com/index.php?id=guitarrig2_us I assume from looking at it, that a USB driver would be required and then perhaps some Wine tweaks to let the plugin open the USB driver. Anyone interested in taking this on? We are hoping to do this as a trade --- like you do this work and get a Receptor and/or some VST plugins for your time. BTW, we also have a job opening, posted here: http://www.craigslist.org/pen/sof/132110028.html Thanks ... mo =================================== Michael Ost, Software Architect Muse Research, Inc. most(a)museresearch.com

2 2

Idea for reducing the number of duplicate bugs
by Tom Spear 23 Feb '06

23 Feb '06

---------- Forwarded message ---------- From: Tom Spear <speeddymon(a)gmail.com> Date: Feb 23, 2006 3:46 PM Subject: Re: Idea for reducing the number of duplicate bugs To: n0dalus <n0dalus+wine(a)gmail.com> Ok ok, maybe not an alert. I still think something saying to check the appdb would help, cause then when they read the appdb, they can see that there is already a bug filed for that specific issue, and can post notes to that bug instead of filing a new one.. Sure some users will still file a new one, not paying attention, but it will cut down.. Another thing I think we should do, for the users that do read the docs, is to put a comprehensive guide to searching for a bug in either the FAQ and/or the wine/developer userguide(s), as the bug search form does look a little intimidating. Tom On 2/23/06, n0dalus <n0dalus+wine(a)gmail.com> wrote: > > On 2/24/06, Tom Spear <speeddymon(a)gmail.com> wrote: > > > > Something like <h2><font color=red>Please check the AppDB to see if > there is > > a workaround for a problem you are encountering with a specific > > program.</font></h2> should work for all but the main bug submit page, > and > > there we should put javascript:alert('Please check the AppDB to see if > there > > is a workaround for a problem you are encountering with a specific > > program.'); into the body so that it shows each time they load the > page.. > > Maybe we could make is a question pop up when they hit the submit button > > instead, and if thye hit yes, then it submits the bug, if not, it either > > redirects them to the appdb, or back to the bug submit page. > > > > Hopefully most of you will agree and it will get put in. > > > > I really don't think this would reduce bug duplicates. For one thing, > bugs are bugs and should be filed in the database. Even if there's a > workaround in the AppDB that says how to get a program working, it > doesn't mean that the underlying issue shouldn't be fixed. > > I also think that having any kind of popup in the way will just annoy > people, and most people will ignore it anyway > > n0dalus. >

1 0

Problems with Sockets and TCL
by Ryan Miller 23 Feb '06

23 Feb '06

Hello, I have an app running under Wine called Auctionpay Event Software. It's currently using TCL to implement a SOAP interface. I've found a bug that can be reproduced with two lines of TCL: package require http http::geturl http://www.google.com <http://www.google.com/> -timeout 0 -query "asdf" 9 times out of 10 this command will fail to return a page. Sometimes the command works. I've traced it down the write event not being received by TCL. Looking into Wine, it appears upon connecting to a socket a user message is sent (WM_USER+2). In the handler WSAAsyncSelect is being called. WSAAsyncSelect somehow is triggering the message loop again (possibly in a different thread?!), and the write event seems to be processed before the original WM_USER+2 is completed. This leads to no write event, which leads to no query being posted to the socket, and finally leading to both computers just sitting there until the server drops the socket. Yet 1/10, it seems that the interrupting message processor interrupts the main message loop as WM_USER+2 message handler has exited/is exiting, and the write message is properly processed and the operation works fine. I have been having a terrible time working with winedbg and setting breakpoints (seems to cause crashes). Is there someone interested in working on this bug or possible just shedding some light on just what might be going on to cause the main message loop to be interrupted in a race condition like this? Thanks, Ryan

1 0

Idea for reducing the number of duplicate bugs
by Tom Spear 23 Feb '06

23 Feb '06

Hi guys, I just wanted to share an idea I just had that could reduce the number of duplicate bugs and ones that have a workaround in the appdb. Many people dont read the documentation, as much as we ask them to, so why dont we, on several pages throughout the website put something that is fairly noticable saying to check the appdb for a workaround/fix before posting a problem to bugzilla, or any of the mailing lists? I think the most helpful places, if we agree to do this, would be the main wine page, the main bugzilla page, the bug submit page, and the main mailing list page.. Something like <h2><font color=red>Please check the AppDB to see if there is a workaround for a problem you are encountering with a specific program.</font></h2> should work for all but the main bug submit page, and there we should put javascript:alert('Please check the AppDB to see if there is a workaround for a problem you are encountering with a specific program.'); into the body so that it shows each time they load the page.. Maybe we could make is a question pop up when they hit the submit button instead, and if thye hit yes, then it submits the bug, if not, it either redirects them to the appdb, or back to the bug submit page. Hopefully most of you will agree and it will get put in. Tom

2 1

wine-0.9.8 and Lotus Notes 6.5.1
by Rainer Dorsch 23 Feb '06

23 Feb '06

Hello, just wanted to report my wine experience with Lotus Notes 6.5.1: I run Lotus Notes with wine since a long time. What I notices with wine-0.9.8 (though this was present in a few releases before but not in all releases): -> Wine is noticalby faster than the snapshot 200412xx -> I need to select win98 to get the file select box working -> I need to set WINEDLLOVERRIDES="usp10=n" -> Cut and paste between X and wine applications works only when selecting the appropriate entry in KDE's klipper. Previously, that worked transparently, when specifying "UsePrimary" = "1" in the [Clipboard] config stanza -> The file select box shows for folders the symbol of files, e.g. Compare rd@silverboxy:~/test$ ls -l insgesamt 4 drwxr-xr-x 2 rd rd 4096 2006-02-23 17:08 dir -rw-r--r-- 1 rd rd 0 2006-02-23 17:08 file rd@silverboxy:~/test$ with the attachment, which shows a screenshot of the file select box. Regards, Rainer -- Rainer Dorsch Alzentalstr. 28 D-71083 Herrenberg 07032-919495 Icq: 32550367

2 1

← Newer
1
2
3
4
5
6
7
8
9
...
26
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel February 2006