February 2008 - Wine-Devel - list.winehq.org

Re: OUTB() and friends on Win32 and .sys files(Resent)

by Marcus Meissner

On Thu, Feb 14, 2008 at 01:55:45PM +0100, Uwe Bonnes wrote: > Hallo, > > some programm with source uses giveio.sys to access the parallel port. You > can find the source for giveio.sys e.g. in the avrdude package. We > have code in dlls/winedos/ppdev.c to emulate the directed access on the > parallel port to accesses to /dev/ppdev. > > However this code is not called for WIN32 code. So after starting giveio > with loaddrv.exe supplied with giveio > > wine loaddrv.exe start giveio > starting giveio... ok. > > wine javr.exe > crashes when the outb access happens: > =>1 0x004014b6 outb+0x6(value=0x0, port=0x378) [/spare/bon/jtagprog/win/javr-2.8/ppiwin.c:311] in javr (0x0072fe50) > > MS msvcrt.dll also supplies outb(). > > What is the policy to handle outb() and friends? We can handle such privileged opcodes in Win32 mode too, we do for some kernel drivers already. For outb (or the specific exception code) it is probably not hooked correctly. Ciao, Marcus

Feb. 14, 2008

Re: Google's support for Wine in 2007

by Dan Kegel

On Thu, Feb 14, 2008 at 7:11 AM, Marcus Meissner <meissner(a)suse.de> wrote: > > Thanks, everybody! I'm really looking forward to Wine 1.0 > > (which, according to Alexandre, is planned for sometime in 2008). > > I hope you have not forgotten that you volunteered to be Release Manager ;) Not at all. Just being realistic about how much influence I can really have! - Dan

Feb. 14, 2008

Re: Google's support for Wine in 2007

by Marcus Meissner

On Wed, Feb 13, 2008 at 10:03:21PM -0800, Dan Kegel wrote: > As you might know, I work for Google, and part of my > day job is to help improve Wine. Here's a little report > about what we've been up to. ... Nice work :) > All that may sound like a lot, and perhaps it is, but it pales > compared to the work put in on Wine by the rest of the Wine developers. > Thanks, everybody! I'm really looking forward to Wine 1.0 > (which, according to Alexandre, is planned for sometime in 2008). I hope you have not forgotten that you volunteered to be Release Manager ;) Ciao, Marcus

Feb. 14, 2008

Re: Google's support for Wine in 2007

by Dan Kegel

On Thu, Feb 14, 2008 at 1:50 AM, Austin English <austinenglish(a)gmail.com> wrote: > What's the status of getting the win16 tests into wine? 16 bit support > broke a while back for many apps and is still broken. The sticking point is that most people don't have a 16 bit C compiler installed. The only good free one is Open Watcom. Unfortunately, you still can't just do 'sudo apt-get install openwatcom' on most distributions (see http://openwatcom.org/index.php/Installing_Open_Watcom_on_Linux ), and there were some hitches using the Linux version anyway, so win16test provides a shell script that installs the Windows version under Wine. (See http://code.google.com/p/win16test/source/browse/trunk/src/README ) And that's kind of heavyweight, so we can't just jam it into the Wine build system. Potentially, though, the Wine build system could notice whether openwatcom was available, and if so, it could build the win16 tests. For now, they're kept out of tree in http://code.google.com/p/win16test/ and I encourage others to try them out and fix problems they find. - Dan

Feb. 14, 2008

Re: [RFC] winecfg enhancements

by Frank Richter

On 13.02.2008 10:15, Reece Dunn wrote: > * Pre-populate the Theme list with themes in > WINDOWS/Resources/Themes and with other *.theme files added by the > user. I dimly recall this is already the case. winecfg lets uxtheme enum installed themes, which in turn should look into said directory. > * Rename "Install theme..." to "Add...". > > The rationale is that we are not installing a theme, but setting > it as the theme being used. Having the theme appear in the Themes list > in the future further supports this name change and workflow. Well but it really installs. It copies the selected file to Themes dir. See on_theme_install() in winecfg. -f.r.

Feb. 14, 2008

Re: Weird failure in kernel32 volume test

by Francois Gouget

On Thu, 14 Feb 2008, Jeremy White wrote: > > Anyone else has some tests that consistently fail on make test? > > As of last nights git tip, I still had four failures: Five actually. > http://test.winehq.org/data/20080213/#Wine -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Research is the transformation of money to knowledge. Innovation is the transformation of knowledge to money. -- Dr. Hans Meixner

Feb. 14, 2008

Re: Weird failure in kernel32 volume test

by Jeremy White

> Anyone else has some tests that consistently fail on make test? As of last nights git tip, I still had four failures: http://test.winehq.org/data/20080213/#Wine Cheers, Jeremy

Feb. 14, 2008

OUTB() and friends on Win32 and .sys files(Resent)

by Uwe Bonnes

Hallo, some programm with source uses giveio.sys to access the parallel port. You can find the source for giveio.sys e.g. in the avrdude package. We have code in dlls/winedos/ppdev.c to emulate the directed access on the parallel port to accesses to /dev/ppdev. However this code is not called for WIN32 code. So after starting giveio with loaddrv.exe supplied with giveio > wine loaddrv.exe start giveio starting giveio... ok. > wine javr.exe crashes when the outb access happens: javr [<filename>] [-p<port>] [-f<fusefilename>] [-e<eepromfilename>] [-L] [-V] Allocated flash buffer of 128K Using giveio.sys to gain port access to 0x378 trace:seh:raise_exception code=c0000096 flags=0 addr=0x4014b6 trace:seh:raise_exception eax=00000000 ebx=00000000 ecx=00000378 edx=00000378 esi=00000378 edi=00110388 trace:seh:raise_exception ebp=0072fe50 esp=0072fe50 cs=0073 ds=007b es=007b fs=0033 gs=003b flags=00010246 trace:seh:call_stack_handlers calling handler at 0x7eddc5bc code=c0000096 flags=0 trace:seh:MSVCRT_signal (4, (nil)) wine: Unhandled privileged instruction at address 0x4014b6 (thread 0011), starting debugger... trace:seh:start_debugger Starting debugger "winedbg --auto 16 56" trace:seh:call_stack_handlers handler at 0x7eddc5bc returned 1 Unhandled exception: privileged instruction in 32-bit code (0x004014b6). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:004014b6 ESP:0072fe50 EBP:0072fe50 EFLAGS:00010246( - 00 -RIZP1) EAX:00000000 EBX:00000000 ECX:00000378 EDX:00000378 ESI:00000378 EDI:00110388 Stack dump: 0x0072fe50: 0072fe58 0040151a 0072fe88 00406ccf 0x0072fe60: 00000378 00000000 00000000 00403411 0x0072fe70: 00000001 00110388 0072fe88 0040a3ef 0x0072fe80: 0040a3ef 00000001 0072fec8 004025e4 0x0072fe90: 00000378 00000378 00110048 0040255c 0x0072fea0: 7ed5ff48 7ffdf000 0072fec8 7ed30f5c Backtrace: =>1 0x004014b6 outb+0x6(value=0x0, port=0x378) [/spare/bon/jtagprog/win/javr-2.8/ppiwin.c:311] in javr (0x0072fe50) MS msvcrt.dll also supplies outb(). What is the policy to handle outb() and friends? Thanks -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

Feb. 14, 2008

Re: [RFC] winecfg enhancements

by Austin English

How about a keyword/wiki page tracking the requests. -Austin On Thu, Feb 14, 2008 at 5:36 AM, Dmitry Timoshkov <dmitry(a)codeweavers.com> wrote: > "Reece Dunn" <msclrhd(a)googlemail.com> wrote: > > > > Does anyone know how to set up the meta bug/group to track these? > > We decided to avoid meta bugs in Wine. I'd suggest to discuss the things > first on wine-devel, and make sure that there is an agreement to what you > are planning to change. Only then start adding features, change functionality. > > -- > Dmitry. > > >

Feb. 14, 2008

Re: [RFC] winecfg enhancements

by Reece Dunn

On 14/02/2008, Dmitry Timoshkov <dmitry(a)codeweavers.com> wrote: > "Reece Dunn" <msclrhd(a)googlemail.com> wrote: > > > Does anyone know how to set up the meta bug/group to track these? > > We decided to avoid meta bugs in Wine. I'd suggest to discuss the things > first on wine-devel, and make sure that there is an agreement to what you > are planning to change. Only then start adding features, change functionality. Ok. I was trying to find a better way of tracking planned changes - what I am planning, the changes that Ubuntu are interested in and other usability issues from other sources. Perhapse the wiki is a better place for tracking planned changes, provided that there is a more consistent way of tracking feature requests/requirements, analysis and design documentation. - Reece

Feb. 14, 2008