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.
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.
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.
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@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.
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.
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.
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.
http://bugs.winehq.org/show_bug.cgi?id=1670
puoti(a)inwind.it changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #351 is|0 |1
obsolete| |
------- Additional Comments From puoti(a)inwind.it 2004-21-01 11:36 -------
Created an attachment (id=498)
--> (http://bugs.winehq.org/attachment.cgi?id=498&action=view)
Current crash log with backtrace.
After the recent changes in wine, mafia crashes in more or less the same way,
there is still a first chance exception in c0000025, but the backtrace is
different, all messages from MSVCRT and VORBISFILE are gone, and you have
messages about NTDLL.DLL and LS3DF.DLL instead. Let me know if any extra
-debugmsg traces are needed.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=1450
tjawatts(a)yahoo.co.uk changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From tjawatts(a)yahoo.co.uk 2004-21-01 10:11 -------
As of 12.12.2003 version this program works fine.
Never did get to the root of the problem but it seems to have disappeared.
Tony
--
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.
http://bugs.winehq.org/show_bug.cgi?id=1948
mike(a)theoretic.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
------- Additional Comments From mike(a)theoretic.com 2004-21-01 05:57 -------
This function is implemented in latest CVS. Please open a new bug if you have
problems.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=1947
marcus(a)jet.franken.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
------- Additional Comments From marcus(a)jet.franken.de 2004-20-01 17:09 -------
yes, I agree with your last comment. Now someone would need to write such
a script ;)
--
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.
http://bugs.winehq.org/show_bug.cgi?id=1949
------- Additional Comments From tazdev(a)punkass.com 2004-20-01 16:58 -------
ho yes, i'm using latest cvs, today is 20040120
--
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.
http://bugs.winehq.org/show_bug.cgi?id=1949
Summary: mouse cursor always recentered
Product: Wine
Version: CVS
Platform: Other
URL: http://www.pouet.net/prod.php?which=7090
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: tazdev(a)punkass.com
when i play this little game, i cant use the mouse,
after every movement, the cursor is centered again on the screen.
reproducible at 100%
--
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.
http://bugs.winehq.org/show_bug.cgi?id=1948
------- Additional Comments From marcus(a)jet.franken.de 2004-20-01 10:58 -------
WINEDLLOVERRIDES=rpcrt4=n
you probably are using oleaut32 native already, so either use
that builtin or both oleaut32,rpcrt4 native.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=1945
------- Additional Comments From marcus(a)jet.franken.de 2004-20-01 03:39 -------
can you capture relay debug output to a file?
wine ... -debugmsg +relay 2>&1 | tee logfile
make sure you have XXX MB free.
If it dumps, attach the last 2000 lines before fixme:msvcrt:_XcptFilter
(-1073741819,0x406cf63c)semi-st line...
--
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.
http://bugs.winehq.org/show_bug.cgi?id=1944
------- Additional Comments From marcus(a)jet.franken.de 2004-20-01 03:37 -------
reporter, can you also compile with debug info
and get some line numbers?
also the place of the bus error would be of itnerest.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=1074
------- Additional Comments From the_riddlr(a)hotmail.com 2004-20-01 02:48 -------
I have the same error report on this bug.. Any resolution yet?
-James
--
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.
http://bugs.winehq.org/show_bug.cgi?id=1947
------- Additional Comments From rklazes(a)xs4all.nl 2004-20-01 01:53 -------
Marcus, the problem is that Linux applications do not understand
DOS style contents of the TEMP variable.
This what is happening:
$ TEMP=C:\\TEMP ps2pdf -
**** Unable to open the initial device, quitting.
A solution within wine would be to unset all such variables before
launching the Unix executable. My guess is that it is unlikely to
be accepted, similar changes for DOS paths in the program arguments
where dropped in favour of the tool "winepath". The external
solution (script) is the way to go.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=1948
Summary: Unhandled exception: unimplemented function
rpcrt4.dll.RpcNetworkIsProtseqValidA called in 32-bit
code
Product: Wine
Version: 20031212
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: altaykirecci(a)yahoo.com
CC: altaykirecci(a)yahoo.com
fixme:seh:EXC_RtlRaiseException call to unimplemented function
rpcrt4.dll.RpcNetworkIsProtseqValidA
wine: Unhandled exception (thread 0017), starting debugger...
WineDbg starting on pid 16
Loaded debug information from ELF 'wine' ((nil))
No debug information in 32bit DLL 'C:\Program Files\Microsoft
Office\Office\OUTLOOK.EXE' (0x30000000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\NTDLL.DLL' (0x401c0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\KERNEL32.DLL' (0x40450000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSVCRT.DLL' (0x78000000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\ADVAPI32.DLL' (0x408d0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\GDI32.DLL' (0x40a50000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\USER32.DLL' (0x40920000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\RPCRT4.DLL' (0x40ad0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLE32.DLL' (0x40870000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMCTL32.DLL' (0x40b10000)
No debug information in 32bit DLL 'C:\PROGRAM FILES\MICROSOFT
OFFICE\OFFICE\MSO9.DLL' (0x308c0000)
No debug information in 32bit DLL 'C:\PROGRAM FILES\MICROSOFT
OFFICE\OFFICE\OUTLLIB.DLL' (0x3a420000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\X11DRV.DLL' (0x40e30000)
No debug information in 32bit DLL 'C:\PROGRAM FILES\MICROSOFT
OFFICE\OFFICE\1033\OUTLLIBR.DLL' (0x3a950000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHLWAPI.DLL' (0x418a0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHELL32.DLL' (0x41820000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MPR.DLL' (0x418e0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\LZ32.DLL' (0x41910000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\VERSION.DLL' (0x41900000)
No debug information in 32bit DLL
'C:\PROG~FBU\COMM~CP1\SYSTEM\MAPI\1033\95\GAPI32.DLL' (0x3ff30000)
No debug information in 32bit DLL 'C:\PROGRAM FILES\COMMON
FILES\SYSTEM\MAPI\1033\95\MSMAPI32.DLL' (0x62100000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSI.DLL' (0x3f000000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINMM.DLL' (0x41d70000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSVFW32.DLL' (0x41d40000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINEOSS.DRV' (0x41de0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSACM32.DLL' (0x41e20000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSACM.DRV' (0x41e10000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MIDIMAP.DRV' (0x40dc0000)
No debug information in 32bit DLL 'C:\PROGRAM FILES\COMMON
FILES\SYSTEM\MAPI\1033\95\EMSABP32.DLL' (0x626f0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLEAUT32.DLL' (0x41fd0000)
No debug information in 32bit DLL
'C:\PROG~FBU\COMM~CP1\SYSTEM\MAPI\1033\95\OUTEX.DLL' (0x62030000)
No debug information in 32bit DLL 'C:\PROGRAM FILES\COMMON
FILES\SYSTEM\MAPI\1033\95\EMSUI32.DLL' (0x625d0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\RICHED20.DLL' (0x48000000)
Unhandled exception: unimplemented function rpcrt4.dll.RpcNetworkIsProtseqValidA
called in 32-bit code (0x40ad4056).
In 32-bit mode.
0x40ad4056 (RPCRT4.DLL..text+0x3056 in RPCRT4.DLL): jmp 0x40ad4050
(RPCRT4.DLL..text+0x3050 in RPCRT4.DLL)
how can i fix this problem.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=1944
gerald(a)pfeifer.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
------- Additional Comments From gerald(a)pfeifer.com 2004-19-01 17:24 -------
I can confirm this issue. Unfortunately, FreeBSD 4.x really has have had this
kind of problems for several months now.
As far as I can tell, this is not due to FreeBSD bugs, but rather to the fact
that Wine makes certain (implicit) assumptions about the underlying threading
model which are satisfied by current glibcs but not FreeBSD's libc.
What I strongly recommend in FreeBSD-land is to use a current version of GCC
(from the 3.2 or 3.3 series) to address some linking issues you may encounter
with libc_r. And you may want to give FreeBSD 5.x a try, whose threading model
is more similiar to the glibc one, I believe.
I'll try to get access to a FreeBSD 5.2-CURRENT system and see how Forte Agent,
which currently won't work on FreeBSD 4.9-STABLE with the failure mode described
in this bug, behaves.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=1945
marcus(a)jet.franken.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|gerald(a)pfeifer.com |
------- Additional Comments From marcus(a)jet.franken.de 2004-19-01 16:48 -------
argh. the last comment does not belong here. please ignore.
--
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.