http://bugs.winehq.org/show_bug.cgi?id=21085
Summary: Comctl32 status control uses tooltip window wrongly
Product: Wine
Version: 1.1.35
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P3
Component: comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: us(a)edmeades.me.uk
I've been debugging a private application and tracked down the source of a trap
to the way the status control initializes and uses the tooltip control.
The application in question traps because it receives a WM_CREATE message for
the tooltip window and calls GetWindowLong against an hwnd for a value it
should have set earlier - this fails but the code doesnt notice, and results in
a trap.
On windows, the status control does not create the tooltip until the first
WM_MOUSEMOVE event, and hence all application initialization would have
finished in my case. You can clearly see this by use of a simple application
with a statusbar control set to have a tooltip and text, and then use SPY++ to
monitor the window creation messages.
Note this also shows a 2nd problem which is that the status control passes the
tooltip text to the tooltip window to manage. This is wrong, because using the
status bar you can set and then get the tooltip text before the tooltip window
is ever created. Additionally, SPY++ shows that the notify messages (NEEDTEXT
type) are sent to the status window when the tooltip needs the text, both of
which mean that the status control should manage the text.
I have a simple application which has a button for get tip, set tip text, and
using it you can see the behaviour above. It doesnt replicate the trap but you
can see the behavious using it - you dont get a WM_CREATE for the tooltip until
such time as you move the mouse into the statusbar area on windows.
Simple workarounds for me: winetricks comctl32, or modifying the
STATUSBAR_WMCreate method to something like "if (0 && dwStyle & SBT_TOOLTIPS)
{" to prevent the tooltip altogether.
JECC
JECC
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=17181
Summary: Winbench 96 disk test fails during recursive directory
deletion; bug in INT21_FindFirst/FindNext?
Product: Wine
Version: 1.1.13
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: dos
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Install and run Ziff-Davis PC Benchmarks WinBench 96
(on the Winstone 32 cd-rom).
Start it with
cd .wine/drive_c/ZDBENCH/WB96
wine WB96
Get past the hangs described in bug 12267 by killing and restarting twice.
Run the "Disk Tests". Get past the abort
"A DOS file operation that was supposed to fail succeeded during the test.
The following information is for ZDBOp use:
Drive: C Operation: GetFileAttrib
Script Location: 0d0b11 0
Pathname(s): C:\~WBDM.TMP\ZDBENCH\WS96.B03\WORK\PDOX50\"
by applying the patch
http://www.winehq.org/pipermail/wine-patches/2009-January/068579.html
The test runs for a long time, then tries to delete its temporary
directory, C:\~WBDM.TMP, but fails with the dialog
and the app aborts with
"A DOS file operation failed during the test.
The following information is for ZDBOp use:
Drive: C Operation: DeleteTestDir
Pathname(s): SB, ???????????
Working Dir: ~WBDM.TMP
Int 21 Function: 3a 00 CF: 1 Expected CF: 0"
Looking at the log, it seems as if Wine trips over its shoelaces
when the app is doing its recursive directory list,
and does not tell the app about one directory,
C:\~WBDM.TMP\MGA\CPANEL. As a result, the app doesn't
delete its contents, and when the app then tries to
delete C:\~WBDM.TMP\MGA, it fails with 'directory not empty'.
INT21_FindHelper looks awfully tricky. It seems to have
a loop to skip over some directory entries, and maybe this
is firing improperly here. The code seems to date from
2003-11-14, mostly written by Eric Pouech in
http://source.winehq.org/git/wine.git/?a=commit;h=8ca6cadab1ebb386f1dfa2e47…
and touched up by Alexandre same day in
http://source.winehq.org/git/wine.git/?a=commit;h=adfa5e101fc2e01d4276c3f3e…
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=15700
Summary: Unable to set/get cursor location through VGA registers
0x3b4 or 0x3d4
Product: Wine
Version: 0.9
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: dos
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: flerchjj(a)ieee.org
Created an attachment (id=16781)
--> (http://bugs.winehq.org/attachment.cgi?id=16781)
Output from Space Quest 5
Apps trying to set or get the text cursor position using VGA registers directly
get an error similar to the following:
fixme:ddraw:VGA_ioport_in Unsupported index, register 0x3d4: 0x0f
fixme:ddraw:VGA_ioport_out Unsupported index, register 0x3d4: 0x0f (value 0x66)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=15688
Summary: DOS games (e.g. Colonel's Bequest) need vga Color plane
write enable register
Product: Wine
Version: 1.1.6
Platform: Other
URL: http://www.abandonia.com/en/games/218/Laura+Bow+1+-
+The+Colonels+Bequest.html
OS/Version: other
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: dos
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Several DOS games, e.g. Colonel's Bequest, complain and display nothing
because Wine does not yet support register 0x3c4 index 2:
fixme:ddraw:VGA_ioport_out Unsupported index, register 0x3c4: 0x02 (value 0x01)
fixme:ddraw:VGA_ioport_out Unsupported index, register 0x3c4: 0x02 (value 0x02)
fixme:ddraw:VGA_ioport_out Unsupported index, register 0x3c4: 0x02 (value 0x04)
fixme:ddraw:VGA_ioport_out Unsupported index, register 0x3c4: 0x02 (value 0x08)
http://www.qzx.com/pc-gpe/vgaregs.txt documents this register/index as follows:
Port-Index: 02h Port: 03c4h
usage: Color plane write enable register
d7,d6 Reserved
d3 Plane 3 Write enable
d2 Plane 2 Write enable
d1 Plane 1 Write enable
d0 Plane 0 Write enable
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=15570
Summary: Fake BIOS unable to render text in graphics mode
Product: Wine
Version: 0.9
Platform: All
OS/Version: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: dos
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: flerchjj(a)ieee.org
Fake BIOS interrupt 10h service number 9 has routines to handle character
displaying in a text mode terminal window, but no code exist for handling
graphics modes. No text is therefore displayed in graphics modes. Currently
only 256 color modes (and possibly linear memory 16 color modes) are supported
as graphics modes & these should be fixed first.
Currently Wine tests for text mode by looking at color depth (Wine 1.1.6) and
calls to this BIOS service could cause Fake VGA memory corruption in monochrome
graphics modes (which aren't supported anyways). That is a separate issue but
the patches for it need to be applied before addressing this issue.
I would suggest a use of the OEM_FIXED_FONT, which I believe is defined in GDI,
and converting it to a bitmaps of the proper resolution for desired chars.
GetStockObject(OEM_FIXED_FONT), GetObject, SelectObject, wglUseFontBitmap may
all be useful functions, but I'll have to investigate more later.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=11570
Summary: VDMSound crashes with illegal instruction
Product: Wine
Version: CVS/GIT
Platform: Other
URL: http://sourceforge.net/project/showfiles.php?group_id=20
091
OS/Version: other
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: dos
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: chris.kcat(a)gmail.com
Created an attachment (id=10741)
--> (http://bugs.winehq.org/attachment.cgi?id=10741)
Trace log and backtrace of crash
VDMSound is used on NT-based Windows systems for emulating audio cards (digital
and midi) for DOS apps. Trying to run the provided dosdrv.exe results in an
illegal instruction when trying to load vddloader.dll. The instruction it seems
to crash on is
popl %gs
in the vm86_[enter|return] assembly functions (in ntdll/signal_i386.c).
I have an AMD X2 4200+ CPU which is a 64-bit CPU, however I'm running a full
32-bit system (32-bit Linux kernel and all; nothing 64-bit). I should also
probably note that the app I'm trying to run through VDMSound (Daggerfall) does
not crash with an illegal instruction, but complains that it can't run under
Windows 3.1, and exits. VDMSound is supposed to help allow the game to run
under real Win2k/XP.
Attached is a +all,-gdi,-syslevel,-heap winedebug trace, along with the winedbg
dump at the very end. You can search for "code=c000001d" to find the point
where it crashes. For some reason, some of the threads' traces in the log get
intermingled at points, and I can't seem to help it much.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=14495
Summary: NVIDIA Dawn Demo Fails to run
Product: Wine
Version: 1.1.1
Platform: PC
URL: http://www.nzone.com/object/nzone_dawndemo_home.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cwadge(a)gmail.com
Created an attachment (id=14820)
--> (http://bugs.winehq.org/attachment.cgi?id=14820)
Debug Verbosity
NVIDIA's "Dawn" graphical demo crashes on execution with the following messageL
wine: Unhandled page fault on read access to 0x00000044 at address 0x406609
(thread 0009), starting debugger...
More verbose debugging is attached as a text file.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=15726
Summary: incorrect text background on listview in Paf 5.2
Product: Wine
Version: 1.1.6
Platform: PC
URL: http://ftp.ldscatalog.com/PAF5AllLangs.exe
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cjstimpson(a)utwire.net
In Paf 5.2
In the dialog from Edit/Add -> Individual, the list view has white instead of
transparent backgrounds for the following text on the left side: "PERSONAL:"
"EVENTS:" "OTHER:".
There's also these partial grey backgrounds that show up on the selected row
that aren't supposed to be there.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=9493
Summary: Cosmetic Errors when using Default Luna theme from
Windows XP
Product: Wine
Version: 0.9.44.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: wine-gui
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: smackdat1(a)gmail.com
Created an attachment (id=7842)
--> (http://bugs.winehq.org/attachment.cgi?id=7842)
errors using luna theme
Background for dragbar is black and Frame and Checkbox labelsdo not blend with
the background. Component is just a guess
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13332
Summary: widl fails with unknown embedded type for somedata (0x0)
Product: Wine
Version: 1.0-rc1
Platform: Macintosh
OS/Version: Mac OS X 10.5
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: tools
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sachin_bhandare(a)persistent.co.in
Created an attachment (id=13211)
--> (http://bugs.winehq.org/attachment.cgi?id=13211)
Sample IDL file
Attached sample IDL file fails with following error.
$>widl -I $WINE_HOME/include/wine/windows -I. -s -u -p -h test.idl
error: write_embedded_types: unknown embedded type for somedata (0x0)
I am using following WIDL version
$>widl -V
Wine IDL Compiler version 1.0-rc1
Copyright 2002 Ove Kaaven
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.