January 2004 - Wine-Bugs - list.winehq.org

[Bug 1902] Dashed lines print incorrectly
by Wine Bugs Jan. 22, 2004

Jan. 22, 2004

http://bugs.winehq.org/show_bug.cgi?id=1902 bleverett(a)att.net changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #491 is|0 |1 obsolete| | ------- Additional Comments From bleverett(a)att.net 2004-21-01 23:02 ------- Created an attachment (id=499) --> (http://bugs.winehq.org/attachment.cgi?id=499&action=view) Second attempt at patch This patch does not use a static local. It will emit a dash specification for each line sent out to wineps. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

Re: [Bug 1872] New: Wine networking apears to be broken with Linux Kernel 2.6
by Jonathan A. Zdziarski Jan. 22, 2004

Jan. 22, 2004

Still broken in 2.6.1. Has anyone looked at this yet? On Tue, 2003-12-09 at 11:16, Wine Bugs wrote: > http://bugs.winehq.com/show_bug.cgi?id=1872 > > Summary: Wine networking apears to be broken with Linux Kernel > 2.6 > Product: Wine > Version: 20030911 > Platform: PC > OS/Version: Linux > Status: UNCONFIRMED > Severity: major > Priority: P2 > Component: wine-net > AssignedTo: wine-bugs(a)winehq.com > ReportedBy: jonathan(a)nuclearelephant.com > > > Wine networking apears to be broken with Linux Kernel 2.6. I upgraded to > 2.6.0-0.test11.1.99 and things work OK except my Quicken application fails every > time I try and connect to my bank with an OL-261-B. I booted up into the old > 2.4 kernel and it downloaded just fine.

1 0

[Bug 1952] half-life, unreal tournament: video runs too 1.5x too fast
by Wine Bugs Jan. 22, 2004

Jan. 22, 2004

http://bugs.winehq.org/show_bug.cgi?id=1952 ------- Additional Comments From lesha(a)netman.ru 2004-21-01 18:47 ------- Just verified that the native apps do run at proper speeds. Hence, definitely a wine bug. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 1952] half-life, unreal tournament: video runs too 1.5x too fast
by Wine Bugs Jan. 21, 2004

Jan. 21, 2004

http://bugs.winehq.org/show_bug.cgi?id=1952 ------- Additional Comments From lesha(a)netman.ru 2004-21-01 17:58 ------- Oh, almost forgot. This may depend on bug 1537. I will test that patch too. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 1952] New: half-life, unreal tournament: video runs too 1.5x too fast
by Wine Bugs Jan. 21, 2004

Jan. 21, 2004

http://bugs.winehq.org/show_bug.cgi?id=1952 Summary: half-life, unreal tournament: video runs too 1.5x too fast Product: Wine Version: 20031212 Platform: PC OS/Version: other Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-multimedia AssignedTo: wine-bugs(a)winehq.org ReportedBy: lesha(a)netman.ru I have a P4 1.7 with a GeForce2Go, nvidia drivers, ker 2.4.1, xfree 4.3.0. After a bit of pain, I got both HL and UT to work with wine. However, I later noticed that both games run 1.5 times as fast as they should, which is causing many problems. The ways I can tell they're running too fast: 0) The movemement is noticeably faster than normal. 1) In the half-life intro, the various voice messages overlap because one doesn't finish before the other. In the UT intro, the voice/sound track gets behind the video (like car noises) 2) In multiplayer (HL), if I act as the server, I can outrun and outshoot every other player by about 1.5 times. Being the multiplayer client doesn't work at all. In multiplayer UT, being a server doesn't work, being a client one runs very fast and stops to catch up with the server every once in a while. The other players see continuous movement. 3) I timed a straight run across a level in wine UT and on windows UT, the wine ones is 1.5 times faster. Prboom (native) and quake3 demo (native) both seem to run at proper speeds (I ought to do numeric test too, just to be sure). I did a wine --debugmsg +all run on half-life's introduction, and there are no messages containing "time" in the part corresponding to the intro at all. There are some wmtimer & getimeofday messages earlier though. I am getting the CVS at the moment, and will also test an older version. However, I'd appreciate hearing any thoughts people have on the subject. By the way, the component is probably wrong. Sorry, I don't know what the problem area really is. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 1898] Half-Life fails in 20031212 release
by Wine Bugs Jan. 21, 2004

Jan. 21, 2004

http://bugs.winehq.org/show_bug.cgi?id=1898 mike(a)theoretic.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From mike(a)theoretic.com 2004-21-01 16:53 ------- Not really sure what to do with this bug, but considering that over the Christmas holidays I bought halflife and ended up wasting most of the last week playing it on Wine I can say it works pretty well here, modulo the following known issues: * Intro video doesn't play. MikeM fixed this a few days ago in CVS though it shows up another WinMM bug which causes the game to hang shortly after. Hopefully it'll be nailed soon. * Flickering on menus. I wrote a patch for this but unfortunately the rest of the painting code can't cope with it yet. Blocking on inter-process invalidation. It's just a cosmetic issue anyway. * Slowness on menu. Not looked at this yet. * Colour palette corruption on animated logo on the menu. Not investigated. * For CD music you need "Device" to be defined. In the future we want this to be autodetected but for now it's manual. The game works perfectly in OpenGL mode though. I also have an i810 audio chip and noticed no real issues with it. The keyboard focus issues are a generic, well known problem with fullscreen apps in Wine :( There's no point having this bug held open for that, we have some ideas for what we need to do there. Running in Desktop mode can help for now. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 1951] New: running ldraw.exe gives: unprotecting the first 64KB of memory to allow real-mode calls.
by Wine Bugs Jan. 21, 2004

Jan. 21, 2004

http://bugs.winehq.org/show_bug.cgi?id=1951 Summary: running ldraw.exe gives: unprotecting the first 64KB of memory to allow real-mode calls. Product: Wine Version: 20031118 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-user AssignedTo: wine-bugs(a)winehq.org ReportedBy: coenblok(a)dse.nl coen(a)cabdeb:~$ wine --debugmsg +int .wine/c/ldraw027.exe Could not stat /mnt/fd0 (No such file or directory), ignoring drive A: Fontconfig warning: line 245: invalid edit binding "same" Fontconfig warning: line 257: invalid edit binding "same" Warning: unprotecting the first 64KB of memory to allow real-mode calls. NULL pointer accesses will no longer be caught. trace:int:DOSVM_Loop waiting for action trace:int:DOSVM_Loop calling 0x406a349c with arg 00010000 trace:int:TIMER_DoSetTimer setting timer tick delay to 55 ms trace:int:DOSVM_Loop done, signalling event 5c trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_SetRMHandler Set real mode interrupt vector 00 <- 00d5:015f trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_Loop waiting for action trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_SetRMHandler Set real mode interrupt vector 23 <- 00d5:2cfe trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_HardwareInterruptRM builtin interrupt 21 has been invoked (through vector 21) trace:int:DOSVM_QueueEvent new event queued, signalling (time=478078) trace:int:DOSVM_SendQueuedEvents Called in real mode with events pending (time=478078) trace:int:DOSVM_SendQueuedEvents cs:ip=0000:00000000, ss:sp=0515:0000ff3a trace:int:DOSVM_SendOneEvent Dispatching IRQ 0. trace:int:DOSVM_HardwareInterruptRM builtin interrupt 08 has been invoked (through vector 08) warn:int:DOSVM_GetBuiltinHandler int1c not implemented, returning dummy handler trace:int:DOSVM_PIC_ioport_out Received EOI for current IRQ 0, clearing event trace:int:DOSVM_Loop waiting for action trace:int:DOSVM_QueueEvent new event queued, signalling (time=478133) trace:int:DOSVM_SendQueuedEvents Called in real mode with events pending (time=478133) trace:int:DOSVM_SendQueuedEvents cs:ip=0000:00000000, ss:sp=0515:0000ff3a trace:int:DOSVM_SendOneEvent Dispatching IRQ 0. trace:int:DOSVM_HardwareInterruptRM builtin interrupt 08 has been invoked (through vector 08) warn:int:DOSVM_GetBuiltinHandler int1c not implemented, returning dummy handler trace:int:DOSVM_PIC_ioport_out Received EOI for current IRQ 0, clearing event trace:int:DOSVM_Loop waiting for action trace:int:DOSVM_QueueEvent new event queued, signalling (time=478188) trace:int:DOSVM_SendQueuedEvents Called in real mode with events pending (time=478188) trace:int:DOSVM_SendQueuedEvents cs:ip=0000:00000000, ss:sp=0515:0000ff3a trace:int:DOSVM_SendOneEvent Dispatching IRQ 0. trace:int:DOSVM_HardwareInterruptRM builtin interrupt 08 has been invoked (through vector 08) warn:int:DOSVM_GetBuiltinHandler int1c not implemented, returning dummy handler trace:int:DOSVM_PIC_ioport_out Received EOI for current IRQ 0, clearing event trace:int:DOSVM_Loop waiting for action trace:int:DOSVM_QueueEvent new event queued, signalling (time=478243) trace:int:DOSVM_SendQueuedEvents Called in real mode with events pending (time=478243) trace:int:DOSVM_SendQueuedEvents cs:ip=0000:00000000, ss:sp=0515:0000ff3a trace:int:DOSVM_SendOneEvent Dispatching IRQ 0. trace:int:DOSVM_HardwareInterruptRM builtin interrupt 08 has been invoked (through vector 08) warn:int:DOSVM_GetBuiltinHandler int1c not implemented, returning dummy handler trace:int:DOSVM_PIC_ioport_out Received EOI for current IRQ 0, clearing event trace:int:DOSVM_Loop waiting for action trace:int:DOSVM_QueueEvent new event queued, signalling (time=478298) trace:int:DOSVM_SendQueuedEvents Called in real mode with events pending (time=478298) trace:int:DOSVM_SendQueuedEvents cs:ip=0000:00000000, ss:sp=0515:0000ff3a trace:int:DOSVM_SendOneEvent Dispatching IRQ 0. trace:int:DOSVM_HardwareInterruptRM builtin interrupt 08 has been invoked (through vector 08) warn:int:DOSVM_GetBuiltinHandler int1c not implemented, returning dummy handler trace:int:DOSVM_PIC_ioport_out Received EOI for current IRQ 0, clearing event trace:int:DOSVM_Loop waiting for action trace:int:DOSVM_QueueEvent new event queued, signalling (time=478353) trace:int:DOSVM_SendQueuedEvents Called in real mode with events pending (time=478353) trace:int:DOSVM_SendQueuedEvents cs:ip=0000:00000000, ss:sp=0515:0000ff3a trace:int:DOSVM_SendOneEvent Dispatching IRQ 0. trace:int:DOSVM_HardwareInterruptRM builtin interrupt 08 has been invoked (through vector 08) warn:int:DOSVM_GetBuiltinHandler int1c not implemented, returning dummy handler trace:int:DOSVM_PIC_ioport_out Received EOI for current IRQ 0, clearing event trace:int:DOSVM_Loop waiting for action trace:int:DOSVM_QueueEvent new event queued, signalling (time=478408) trace:int:DOSVM_SendQueuedEvents Called in real mode with events pending (time=478408) trace:int:DOSVM_SendQueuedEvents cs:ip=0000:00000000, ss:sp=0515:0000ff3a trace:int:DOSVM_SendOneEvent Dispatching IRQ 0. trace:int:DOSVM_HardwareInterruptRM builtin interrupt 08 has been invoked (through vector 08) warn:int:DOSVM_GetBuiltinHandler int1c not implemented, returning dummy handler trace:int:DOSVM_PIC_ioport_out Received EOI for current IRQ 0, clearing event trace:int:DOSVM_Loop waiting for action trace:int:DOSVM_QueueEvent new event queued, signalling (time=478465) trace:int:DOSVM_SendQueuedEvents Called in real mode with events pending (time=478465) trace:int:DOSVM_SendQueuedEvents cs:ip=0000:00000000, ss:sp=0515:0000ff3a trace:int:DOSVM_SendOneEvent Dispatching IRQ 0. trace:int:DOSVM_HardwareInterruptRM builtin interrupt 08 has been invoked (through vector 08) warn:int:DOSVM_GetBuiltinHandler int1c not implemented, returning dummy handler trace:int:DOSVM_PIC_ioport_out Received EOI for current IRQ 0, clearing event trace:int:DOSVM_Loop waiting for action trace:int:DOSVM_QueueEvent new event queued, signalling (time=478518) trace:int:DOSVM_SendQueuedEvents Called in real mode with events pending (time=478518) trace:int:DOSVM_SendQueuedEvents cs:ip=0000:00000000, ss:sp=0515:0000ff3a trace:int:DOSVM_SendOneEvent Dispatching IRQ 0. trace:int:DOSVM_HardwareInterruptRM builtin interrupt 08 has been invoked (through vector 08) warn:int:DOSVM_GetBuiltinHandler int1c not implemented, returning dummy handler trace:int:DOSVM_PIC_ioport_out Received EOI for current IRQ 0, clearing event trace:int:DOSVM_Loop waiting for action [4]+ Stopped wine --debugmsg +int .wine/c/ldraw027.exe -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 1950] New: Regression - MDI Failure in 16-Bit Program
by Wine Bugs Jan. 21, 2004

Jan. 21, 2004

http://bugs.winehq.org/show_bug.cgi?id=1950 Summary: Regression - MDI Failure in 16-Bit Program Product: Wine Version: CVS Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gui AssignedTo: wine-bugs(a)winehq.org ReportedBy: Andrew.Talbot(a)talbotville.com Patch http://cvs.winehq.com/patch.py?id=10783 introduces a reversion whereby instead of a child window opening, an 'Error' dialog appears giving the pathname of the program's executable file. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 1898] Half-Life fails in 20031212 release
by Wine Bugs Jan. 21, 2004

Jan. 21, 2004

http://bugs.winehq.org/show_bug.cgi?id=1898 ------- Additional Comments From lesha(a)netman.ru 2004-21-01 13:18 ------- My troubles with Half-Life (and Wine in general) on 20031212 are as follows: I used a working, existing install of 1.1.0.8 on kv 2.4.21/xf 4.3.0 with nvidia drivers. a) Half-Life fails miserably when played in software mode. b) I had to delete the valve/media directory -- the menu transition sounds were causing the aforementioned hangs, I think. c) Keyboard does not work at all in single-player (I can't even escape out to the menus). However, it works fine in multiplayer. d) Multiplayer is unstable -- crash soon after connecting to a server. Works better when I serve the game, however. e) I have ALSA with an i810 chip, and neither the ALSA nor the OSS output driver works in wine in DirectX games. That said, sound kind of works (very crappily and unreliably) when played through the plain windows API (like in the HL menus, and in Pinball). I can use the ARTS driver, but the latency or CPU overhead is not acceptable in general. f) Playing at 1024x768 doesn't work either, nor is DXGrab & similar functional in some games. The best way to go for me is to xrandr to whatever resolution the game will use, and the resolution has to be 800x600 or less. g) JHexen 0.9.6 runs in opengl mode, but the frame-rate is awful (1 fps), and wine-pthread takes all the CPU time. OpenGL works fine in Half-Life. A similar situation (wine-pthread eating all CPU) occurs in some other games, and in all DOS ones that I tried. I'll gladly give more details about any of these problems. Hope at least some merit attention. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 1780] InstallShield: Error 0x80040706 when trying to install apps.
by Wine Bugs Jan. 21, 2004

Jan. 21, 2004

http://bugs.winehq.org/show_bug.cgi?id=1780 ------- Additional Comments From crazyr2(a)shaw.ca 2004-21-01 12:38 ------- I encountered this problem with IS6. Ended up removing the C:\Windows\System32\Dllcache directory and IS6 worked flawlessly the next time it was initialized. The Dllcache directory then reappeared and so did the problem. Anyone else care to try this and see if it works for them as well? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0