http://bugs.winehq.com/show_bug.cgi?id=1239
------- Additional Comments From winebug(a)flonet.net 2003-23-06 12:52 -------
Bug comments restored from Gmane.org:
I am a newbie. I have run into a problem in changing the gamma ramp due to the
size of my gamma ramp on my video card. There is a check in
xvidmode.c which disables the get/setgammaramp functions if the size of the
gamma ramp reported by the hardware is not 256. My gamma ramp size is
1024. I have made it work by modifying (defeating) the check and interpolating
the 256 size gamma ramp from the Windows program to the larger size
1024 gamma ramp in get/setgammaramp functions. Should learn how to submit my
ham fisted modification?
------- Additional Comments From tony_lambregts <at> telusplanet.net 2003-01-24
22:42 -------
Yes. Ham fisted or not.
The following link gives general information on submitting Patches.
http://www.winehq.org/docs/wine-devel/patches.shtml
This will allow others to see your HACK^H^H^H^H patch and hopefully someone will
be able to give some constructive critisism so you can put together a patch that
can be acceptable.
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1240
------- Additional Comments From winebug(a)flonet.net 2003-23-06 12:48 -------
Bug comments restored from Gmane.org:
As shown in the URL image, what should be an invisible child window has the
WS_CAPTION style set.
trace:win:CreateWindowExW classname=#8002 stylehex=40c00440
trace:win:WIN_CreateWindowEx L"" L"#32770" ex=00000000 style=40c00440 -3,-22
456x253 parent=0x10021 menu=(nil) inst=0x400000 params=(nil)
trace:win:WIN_CreateWindowEx Styles before adjustment:
trace:win:dump_window_styles style: WS_CHILD WS_CAPTION 00000440
trace:win:dump_window_styles exstyle:
trace:win:WIN_CreateWindowEx winproc type is 3 (WIN_PROC_32W)
trace:class:CLASS_FindClassByAtom 0x00008002 0x400000
trace:class:CLASS_FindClassByAtom -- found global 0x40388118
0807a218:Call ntdll.RtlAllocateHeap(40360000,00000000,000000a2) ret=408be1fd
0807a218:Ret ntdll.RtlAllocateHeap() retval=403a0458 ret=408be1fd
trace:win:WIN_CreateWindowEx Styles after adjustment:
trace:win:dump_window_styles style: WS_CHILD WS_CAPTION 00000440
trace:win:dump_window_styles exstyle: WS_EX_WINDOWEDGE
trace:win:WIN_SetWindowLong 0x1002f -12 0 3
0807a218:Call x11drv.CreateWindow(0001002f,406b2884,00000001) ret=408bfffc
The app I'm testing with is at http://rhymbox.com/download/start.pl
The installer itself appears to set the WS_CAPTION flag when calling
CreateWindowEx. In Windows, spy++ shows that this flag isn't set, but the usage
of vc++ lazy bindings mean I can't get an API trace under windows :(
------- Additional Comments From andi <at> rhlx01.fht-esslingen.de 2003-01-26
18:36 -------
The only place in Wine to fix up WS_CAPTION is:
/* Correct the window style - stage 2 */
if (!(cs->style & WS_CHILD))
{
wndPtr->dwStyle |= WS_CLIPSIBLINGS;
if (!(cs->style & WS_POPUP))
{
wndPtr->dwStyle |= WS_CAPTION;
wndPtr->flags |= WIN_NEED_SIZE;
}
}
in windows/win.c/WIN_CreateWindowEx()
Checking windows/win.c cvs log, I'm thinking about:
----------------------------
revision 1.214
date: 2003/01/08 19:53:47; author: julliard; state: Exp; lines: +2 -2
Duane Clark <dclark <at> akamail.com>
WS_CAPTION is a two bit field, so test appropriately.
----------------------------
Hmm, could it be that this recent change caused you to notice the WS_CAPTION
problem ?
The WS_CAPTION fixup has been in windows/win.c since its CVS beginnings, BTW.
I think we can safely confirm this bug.
So the question is: what exactly should be corrected in that function and how ?
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1243
------- Additional Comments From winebug(a)flonet.net 2003-23-06 12:44 -------
Bug comments restored from Gmane.org:
Wine Version 20021031:
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMDLG32.DLL' (0x42600000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLEDLG.DLL' (0x428d0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLEPRO32.DLL' (0x5f300000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINMM.DLL' (0x42e00000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINEOSS.DRV' (0x42e60000)
Unhandled exception: unimplemented function shlwapi.dll.419 called in 32-bit
code (0x41564059).
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLEDLG.DLL' (0x428d0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLEPRO32.DLL' (0x5f300000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINMM.DLL' (0x42e00000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINEOSS.DRV' (0x42e60000)
Unhandled exception: unimplemented function shlwapi.dll.419 called in 32-bit
code (0x41564059).
In 32-bit mode.
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLEPRO32.DLL' (0x5f300000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINMM.DLL' (0x42e00000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINEOSS.DRV' (0x42e60000)
Unhandled exception: unimplemented function shlwapi.dll.419 called in 32-bit
code (0x41564059).
In 32-bit mode.
0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.so):
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINMM.DLL' (0x42e00000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINEOSS.DRV' (0x42e60000)
Unhandled exception: unimplemented function shlwapi.dll.419 called in 32-bit
code (0x41564059).
In 32-bit mode.
0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.so):
addl $12,%esp
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINEOSS.DRV' (0x42e60000)
Unhandled exception: unimplemented function shlwapi.dll.419 called in 32-bit
code (0x41564059).
In 32-bit mode.
0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.so):
addl $12,%esp
Unable to open file shlwapi.spec.c
Unhandled exception: unimplemented function shlwapi.dll.419 called in 32-bit
code (0x41564059).
In 32-bit mode.
0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.so):
addl $12,%esp
Unable to open file shlwapi.spec.c
Wine-dbg>backtrace
e (0x41564059).
In 32-bit mode.
0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.so): addl
$12,%esp
Unable to open file shlwapi.spec.c
Wine-dbg>backtrace
Backtrace:
In 32-bit mode.
0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.so): addl
$12,%esp
Unable to open file shlwapi.spec.c
Wine-dbg>backtrace
Backtrace:
=>0 0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.
0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.so): addl
$12,%esp
Unable to open file shlwapi.spec.c
Wine-dbg>backtrace
Backtrace:
=>0 0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.so)
(ebp=41e81eb0)
$12,%esp
Unable to open file shlwapi.spec.c
Wine-dbg>backtrace
Backtrace:
=>0 0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.so)
(ebp=41e81eb0)
1 0x4156513e (__wine_stub_shlwapi_dll_419+0x22 in shlwapi.dll.so) (ebp=4
Unable to open file shlwapi.spec.c
Wine-dbg>backtrace
Backtrace:
=>0 0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.so)
(ebp=41e81eb0)
1 0x4156513e (__wine_stub_shlwapi_dll_419+0x22 in shlwapi.dll.so)
(ebp=41e81ee0)
Wine-dbg>backtrace
Backtrace:
=>0 0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.so)
(ebp=41e81eb0)
1 0x4156513e (__wine_stub_shlwapi_dll_419+0x22 in shlwapi.dll.so)
(ebp=41e81ee0)
2 0x70265515 (WININET.DLL.112+0x9c5 in
C:\WINDOWS\SYSTEM\WININET.DLL) (e
Backtrace:
=>0 0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.so)
(ebp=41e81eb0)
1 0x4156513e (__wine_stub_shlwapi_dll_419+0x22 in shlwapi.dll.so)
(ebp=41e81ee0)
2 0x70265515 (WININET.DLL.112+0x9c5 in
C:\WINDOWS\SYSTEM\WININET.DLL) (ebp=41e822cc)
=>0 0x41564059 (__wine_unimplemented+0x59 [shlwapi.spec.c] in shlwapi.dll.so)
(ebp=41e81eb0)
1 0x4156513e (__wine_stub_shlwapi_dll_419+0x22 in shlwapi.dll.so)
(ebp=41e81ee0)
2 0x70265515 (WININET.DLL.112+0x9c5 in
C:\WINDOWS\SYSTEM\WININET.DLL) (ebp=41e822cc)
3 0x70235ff8
(WININET.DLL.EntryPoint+0xb540 in C:\WINDOWS\SYSTEM\WININET
bp=41e81eb0)
1 0x4156513e (__wine_stub_shlwapi_dll_419+0x22 in shlwapi.dll.so)
(ebp=41e81ee0)
2 0x70265515 (WININET.DLL.112+0x9c5 in
C:\WINDOWS\SYSTEM\WININET.DLL) (ebp=41e822cc)
3 0x70235ff8
(WININET.DLL.EntryPoint+0xb540 in C:\WINDOWS\SYSTEM\WININET.DLL) (ebp=41e82a50)
1 0x4156513e (__wine_stub_shlwapi_dll_419+0x22 in shlwapi.dll.so)
(ebp=41e81ee0)
2 0x70265515 (WININET.DLL.112+0x9c5 in
C:\WINDOWS\SYSTEM\WININET.DLL) (ebp=41e822cc)
3 0x70235ff8
(WININET.DLL.EntryPoint+0xb540 in C:\WINDOWS\SYSTEM\WININET.DLL) (ebp=41e82a50)
4 0x7021c30a
(WININET.DLL.InternetSetCookieExW+0x2baf in C:\WINDOWS\SYST
0)
2 0x70265515 (WININET.DLL.112+0x9c5 in C:\WINDOWS\SYSTEM\WININET.DLL)
(ebp=41e822cc)
3 0x70235ff8 (WININET.DLL.EntryPoint+0xb540 in
C:\WINDOWS\SYSTEM\WININET.DLL) (ebp=41e82a50)
4 0x7021c30a
(WININET.DLL.InternetSetCookieExW+0x2baf in C:\WINDOWS\SYSTEM\WININET.DLL)
(ebp=702790b4)
2 0x70265515 (WININET.DLL.112+0x9c5 in C:\WINDOWS\SYSTEM\WININET.DLL)
(ebp=41e822cc)
3 0x70235ff8 (WININET.DLL.EntryPoint+0xb540 in
C:\WINDOWS\SYSTEM\WININET.DLL) (ebp=41e82a50)
4 0x7021c30a
(WININET.DLL.InternetSetCookieExW+0x2baf in C:\WINDOWS\SYSTEM\WININET.DLL)
(ebp=702790b4)
822cc)
3 0x70235ff8 (WININET.DLL.EntryPoint+0xb540 in C:\WINDOWS\SYSTEM\WININET.DLL)
(ebp=41e82a50)
4 0x7021c30a (WININET.DLL.InternetSetCookieExW+0x2baf in
C:\WINDOWS\SYSTEM\WININET.DLL) (ebp=702790b4)
Wine-dbg>
3 0x70235ff8 (WININET.DLL.EntryPoint+0xb540 in C:\WINDOWS\SYSTEM\WININET.DLL)
(ebp=41e82a50)
4 0x7021c30a (WININET.DLL.InternetSetCookieExW+0x2baf in
C:\WINDOWS\SYSTEM\WININET.DLL) (ebp=702790b4)
Wine-dbg>
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1244
winebug(a)flonet.net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |winebug(a)flonet.net
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1244
------- Additional Comments From winebug(a)flonet.net 2003-23-06 12:40 -------
Bug comments restored from Gmane.org:
I'm trying to run Garmin's "UPDATER.EXE", which is supposed to load a new
firmware image into a GPS device. Communication is done over a serial port.
If I run the program without any debugmsg flags, it fails immediately,
complaining that it can't find the GPS. However, if I run with:
--debugmsg +comm,+file,+serial
then it gets a bit further. The first thing it does is get the model number and
current firmware version from the device. But it soon fails again before
beginning the upload. Here's an annotated debug log:
trace:comm:COMM_Init COM1 = /dev/ttyS0
trace:comm:COMM_Init LPT1 = /dev/lp0
trace:comm:COMM_Init COM2 = /dev/ttyS1
trace:comm:COMM_Init COM3 = /dev/ttyS2
trace:comm:COMM_Init COM4 = /dev/ttyS3
trace:file:CreateFileW L"COM2" GENERIC_READ GENERIC_WRITE OPEN_EXISTING
attributes 0x0
trace:file:CreateFileW opening device L"COM2"
trace:file:DOSFS_CreateCommPort L"COM2" c0000000 0
trace:file:CreateFileW returning 0x4c
trace:comm:GetCommState handle 0x4c, ptr 0x41222858
trace:comm:GetCommState OK
trace:comm:GetCommState bytesize 8 baudrate 9600 fParity 0 Parity 0 stopbits 1
trace:comm:GetCommState ~IXON ~IXOFF
trace:comm:GetCommState ~CRTSCTS
trace:comm:SetCommState handle 0x4c, ptr 0x41222858
trace:comm:SetCommState bytesize 8 baudrate 9600 fParity 0 Parity 0 stopbits 1
trace:comm:SetCommState ~IXON ~IXOFF
trace:comm:GetCommTimeouts (0x4c,0x41222844)
trace:comm:SetCommTimeouts (0x4c,0x41222844)
fixme:comm:SetupComm insize 4096 outsize 4096 unimplemented stub
trace:comm:PurgeComm handle 0x4c, flags f
trace:comm:ClearCommError handle 0x4c cbInQue = 0 cbOutQue = 0
trace:file:WriteFile 0x4c 0x40f01851 6 0x41222670 (nil)
trace:comm:ClearCommError handle 0x4c cbInQue = 0 cbOutQue = 0
(this line is repeated many times, presumably while it waits for input)
trace:comm:ClearCommError handle 0x4c cbInQue = 8 cbOutQue = 0
trace:file:ReadFile 0x4c 0x41222a70 8 0x41222530 (nil)
trace:file:FILE_TimeoutRead 0x4c 0x41222a70 8 0x41222530
trace:file:FILE_ReadFileEx file 0x4c to buf 0x41222a70 num 8 0x41222488 func (nil)
trace:file:GetOverlappedResult (0x4c 0x41222488 0x41222530 1)
trace:file:GetOverlappedResult waiting on 0x41222488
trace:file:FILE_AsyncReadService 0x41222488 0x41222a70
trace:file:FILE_AsyncReadService read 8 more bytes 8/8 so far
trace:file:GetOverlappedResult wait on 0x41222488 returned 192
trace:file:GetOverlappedResult waiting on 0x41222488
trace:file:GetOverlappedResult wait on 0x41222488 returned 0
It then continues to do this several times, reading 8 or 16 bytes at a time from
the serial port. There is then one more write/read exchange, then this:
trace:file:WriteFile 0x4c 0x40f01851 8 0x4122256c (nil)
trace:comm:ClearCommError handle 0x4c cbInQue = 0 cbOutQue = 0
trace:file:WriteFile 0x4c 0x40f01851 8 0x41222670 (nil)
trace:comm:ClearCommError handle 0x4c cbInQue = 0 cbOutQue = 0
This last line then repeats about 10,000 times before the program times out and
gives up on hearing anything.
I'm guessing that since it works slightly better with debugging enabled, that
there is a race condition at work here. Maybe the last packet never actually
got written to the serial port, or a response came and Wine lost it.
------- Additional Comments From keldon <at> ont.com 2003-02-02 19:52 -------
I got this to work using an ugly patch (see attached). The write buffer
of the serial port was getting overrun. That caused the app to wait for
an ACK packet that was never going to come.
What I don't understand is why the call to write() doesn't block until
the buffer has drained.
------- Additional Comments From keldon <at> ont.com 2003-02-02 20:00 -------
Created an attachment (id=388)
--> (http://bugs.winehq.com/attachment.cgi?id=388&action=view)
ugly hack to fix serial writes
------- Additional Comments From tony_lambregts <at> telusplanet.net 2003-02-06
16:30 -------
This is a wonderfull bug report. I am not sure why you think that it is not the
"right" fix. This is not my area though. Anyway If it solves your problem
I would like to se it go to wine patches. The following link gives you the
information on how to do this.
http://www.winehq.org/docs/wine-devel/patches.shtml
I would not want it to bit rot, and someone might want to come up with a better
solution if it is posted there.
BTW is there a demo or download version of this program.
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1248
------- Additional Comments From winebug(a)flonet.net 2003-23-06 11:37 -------
Bug comments restored from Gmane.org:
With Wine 20030115 and the online game Tibia (http://www.tibia.com)
there is a problem which seems to be caused by the games "daylight" feature
which is a shading layer.
The screen blinks chaotically and the blinking square sometimes does not match
the size of the program window in the way it should.
X Server Resolution is 1152 x 1268 and the BPP 24 The video card is a ATI Radeon
7500
See attachments
------- Additional Comments From info <at> moabutah.com 2003-02-01 11:20 -------
Created an attachment (id=384)
--> (http://bugs.winehq.com/attachment.cgi?id=384&action=view)
Basic Console Messages
------- Additional Comments From info <at> moabutah.com 2003-02-01 11:20 -------
Created an attachment (id=385)
--> (http://bugs.winehq.com/attachment.cgi?id=385&action=view)
DDraw Debug Messages
------- Additional Comments From lionel.ulmer <at> free.fr 2003-02-01 13:00 -------
Is it possible to have a demo of the game ? I tried looking at the page and it
does not seem possible (as the page took about 10 minutes to load and I did not
find any obvious 'download' link).
If not, a screenshot of the problem could help.
Moreover, a ddraw log from the beginning could help too (if it's too big, just
gzip / bzip2 it).
------- Additional Comments From info <at> moabutah.com 2003-02-01 19:54 -------
Their site can be quite busy and won't come up during "peak hours" at times.
There is a download link and then you have to sign up for a free account.
Keep trying and you will be able to get the site.
I will try and gzip an attachment if you keep having trouble.
The exe is about 3 megs.
------- Additional Comments From lionel.ulmer <at> free.fr 2003-02-02 04:13 -------
OK, downloaded the game and trying now to get to the Sign-Up page for the free
account...
------- Additional Comments From info <at> moabutah.com 2003-02-03 15:16 -------
Apparently the Tibia site was attacked by a hacker and thats why it was down for
so long! their whole game network was knocked out I guess.
Anyway their site should be back up soon for testing this bug.
------- Additional Comments From info <at> moabutah.com 2003-02-05 17:55 -------
the Tibia site is back now, and the game serevers too.
The account signup link is:
http://tibia.4players.de/home/?subtopic=signup
------- Additional Comments From info <at> moabutah.com 2003-02-05 20:34 -------
Created an attachment (id=389)
--> (http://bugs.winehq.com/attachment.cgi?id=389&action=view)
Another console session
------- Additional Comments From info <at> moabutah.com 2003-02-05 20:37 -------
I tried to log the ddraw messages, but the file got huge really fast. So I
attached another simple console session.
Upon researching, I believe the blinking problem is related to a set of
"sub-windows" which open on the bottom right of the game window when you open
your "bag" or "backpack" (or any other item that "opens"), that show
the
contents of the bag. The blinking stops if you close all these sub-windows and
turn off "show lighting effects" in the menu.
Whenever one of these sub-windows is reopened, the blinking resumes.
Just a quick note - to open an item you right click on it and choose "open".
------- Additional Comments From info <at> moabutah.com 2003-02-05 22:01 -------
Created an attachment (id=390)
--> (http://bugs.winehq.com/attachment.cgi?id=390&action=view)
Partial Debug Messages with opening of item
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1250
------- Additional Comments From winebug(a)flonet.net 2003-23-06 11:24 -------
Bug comments restored from Gmane.org:
My config file has this (just like the sample config file):
[Drive E]
"Path" = "/tmp"
[wine]
"Temp" = "e:\\"
But I have an app (Garmin's Mapsource) that tries to do this:
0807e1a8:Call kernel32.GetTempPathA(00000005,41338e00) ret=00737c67
0807e1a8:Ret kernel32.GetTempPathA() retval=00000003 ret=00737c67
0807e1a8:Call kernel32.CreateDirectoryA(41338e00 "E:\\",00000000) ret=00737d2e
0807e1a8:Ret kernel32.CreateDirectoryA() retval=00000000 ret=00737d2e
0807e1a8:Call kernel32.GetLastError() ret=00737d3e
0807e1a8:Ret kernel32.GetLastError() retval=00000005 ret=00737d3e
It then freaks out about the "Access Denied" error it got and dies. I can work
around this by doing either:
a) Changing Wine so that "Already Exists" is returned instead. The app ignores
this error, apparently.
b) Changing my temp path in the config file to c:\windows\temp (something not at
the root of a "drive")
I suspect this is a bug in the app, not wine. But still, maybe the default temp
path shouldn't be a root directory. There may be other apps that don't like it
either.
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1251
------- Additional Comments From winebug(a)flonet.net 2003-23-06 11:22 -------
Bug comments restored from Gmane.org:
fixme:cabinet:FDICreate (pfnalloc == ^0x244f7880, pfnfree == ^0x244f7890,
pfnopen == ^0x244f78a0, pfnread == ^0x244f7a80, pfnwrite == ^0x244f7c00,
pfnclose == ^0x244f7d70, pfnseek == ^0x244f7e10, cpuType == -1, perf ==
^0x2453e4f0): stub
^^^^^^^^^^^^^^^^^^^
from console output for Wine 20030115
Cannot install Office 2K or Visio XP with fake-windows setup. With the mandrake
9 wine RPM I could at least install Office 2K.
------- Additional Comments From grundig <at> wp.pl 2003-02-20 04:29 -------
*** This bug has been confirmed by popular vote. ***
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1252
------- Additional Comments From winebug(a)flonet.net 2003-23-06 11:20 -------
Bug comments restored from Gmane.org:
When I run Agent I can use <ALT>-S to immediately send the current mail. In that
case the ALT activates the Menubar as if pressed as a single key (this is the
normal behaviour if pressed alone).
This is quite annyoing because now, when I sent a mail, I always have to press
ESC or klick the mouse in the window in order to deactivate the Menubar.
--
Configure bugmail: http://bugs.winehq.com/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.com/show_bug.cgi?id=1376
------- Additional Comments From klevin(a)eskimo.com 2003-23-06 10:58 -------
Not sure what happened to the previous contents of this bug entry, but I updated
my wine checkout about an hour ago and gave it another spin. Same end results.
InstallShield goes through its "Wizard setup" bit, the progress window for the
"Wizard setup" closes and then nothing happens after that. Output to the console is:
Invoking /usr/local/bin/wine /mnt/cdrom/Setup.exe ...
Could not stat /mnt/floppy (No such file or directory), ignoring drive A:
fixme:seh:check_resource_write Broken app is writing to the resource data, enabl
ing work-around
FIXME:pthread_cond_init
Could not stat /mnt/floppy (No such file or directory), ignoring drive A:
fixme:ole:ITypeInfo_fnRelease destroy child objects
[above line repeats more times than I care to count]
fixme:ole:CoTreatAsClass ({8c3c1b17-e59d-11d2-b40b-00a024b9dddd},{22d84ec7-e201-
4432-b3ed-a9dca3604594})
FIXME:pthread_cond_init
Could not stat /mnt/floppy (No such file or directory), ignoring drive A:
fixme:ole:ITypeInfo_fnRelease destroy child objects
[above line repeats more times than I care to count]
))))destroy child objects
fixme:ole:ITypeInfo_fnRelease destroy child objects
[above line repeats more times than I care to count]
FIXME:pthread_cond_init
Could not stat /mnt/floppy (No such file or directory), ignoring drive A:
fixme:ole:ITypeInfo_fnRelease destroy child objects
[above line repeats more times than I care to count]
fixme:ole:CoTreatAsClass ({8c3c1b17-e59d-11d2-b40b-00a024b9dddd},{22d84ec7-e201-
4432-b3ed-a9dca3604594})
fixme:ole:ITypeInfo_fnRelease destroy child objects
[above line repeats more times than I care to count]
fixme:win:SetWindowTextA cannot set text "InstallShield Wizard" of other process
window (nil)
fixme:ole:ITypeInfo_fnRelease destroy child objects
[above line repeats more times than I care to count]
fixme:ole:_copy_arg argument was coerced in-place (0x3 -> 0xb); source data has
been modified!!!
fixme:ole:_xread Read only 0 of 4 bytes from 0x48.
fixme:ole:_StubReaderThread Failed with hres 80004005
And that's it.
--
Configure bugmail: http://bugs.winehq.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.