http://bugs.winehq.org/show_bug.cgi?id=7712
------- Additional Comments From dmitry(a)codeweavers.com 2007-18-03 09:32 -------
Sorry for the late ideas, but it would be interesting to see:
1. what GetClassInfo (both A/W) returns for such a class
2. whether any other user32 window proc works the same way (button, edit, menu,
listbox, desktop and other control procs, DefMDIChildProc, DefDlgProc come to
mind).
--
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=7786
Summary: Grand Prix 3 dplay error
Product: Wine
Version: 0.9.33.
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-directx-dplay
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: greg87(a)online.de
The game is crashing at start. I patched the game to latest version and applied
a nocd crack on it.
wine: Call from 0x7ee0e6d0 to unimplemented function
dpnhpast.dll.DirectPlayNATHelpCreate, aborting
--
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=7696
------- Additional Comments From stefandoesinger(a)gmx.at 2007-18-03 09:27 -------
That is interesting. Can you add a trace to output the values of the old
drawable and context?
It may be an idea to just invalidate the currently active context instead of
reactivating the old one. Maybe an incorrect old context is reported due to a
driver bug or leftover from a former d3d device. The context manager could
restore a known good context from the context list.
--
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=7779
gtsarouchas(a)commissario2994.it changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
------- Additional Comments From gtsarouchas(a)commissario2994.it 2007-18-03 08:12 -------
ok found the source of the problem, wrong permissions in system fonts.
--
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=7663
------- Additional Comments From rmh(a)aybabtu.com 2007-18-03 07:40 -------
> You should not use malloc in Wine, wcslen and others won't work properly
> in Wine. Use Win32 APIs like HeapAlloc and lstrlenW instead.
Ok.
> Also it looks like your code won't work if there are non-ascii characters
> on the command line.
Ok, then I suppose I would have to convert the string to the charset defined in
Un*x locale before calling canonicalize_file_name().
Btw, I notice my use of config_dir is not very correct either, since it won't
support drives that are not in a subdir of config_dir. I think I would have to
check which win32 drive does the file belong to, and then check if it's fully
contained in it. But then there's that "catch-all" '/' drive, which breaks this
scheme.
Perhaps what we should do is checking if getcwd() is a subdir of our
executable's drive; if it is then leave relative paths as-is, and otherwise
convert to absolute paths?
--
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=7723
------- Additional Comments From jeremielapuree(a)yahoo.fr 2007-18-03 07:29 -------
The console output
[joaopa@localhost ~]$ file /dev/ttyS0
/dev/ttyS0: character special (4/64)
[joaopa@localhost ~]$
Joaopa
--
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.