http://bugs.winehq.org/show_bug.cgi?id=18778
Summary: Unhandled page fault on read access
Product: Wine
Version: 1.1.22
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: interflap(a)gmail.com
Created an attachment (id=21548)
--> (http://bugs.winehq.org/attachment.cgi?id=21548)
Macmillan English Dictionary error log
Macmillan English Dictionary 2nd Edition.
The installation goes fine on Ubuntu 8.04 i386, but then if I try to launch the
app, I have the errors shown below in the attachment.
--
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=18783
Summary: Check whether a DDL can be executed
Product: Wine
Version: unspecified
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: fn65j24kqrgxys7(a)thisisnotmyrealemail.com
My friend lately tried to start a wine application which requires a dll file
that was shipped in the same folder. The point was that he didn't mount the
volume where both the dll and the exe file live with an exec flag, so wine just
didn't start the application:
[adi64@tux Crashday]$ wine Crashday.exe
err:module:attach_process_dlls "RakNet.dll" failed to initialize, aborting
err:module:LdrInitializeThunk Main exe initialization for
L"Z:\\media\\share\\programme\\Atari\\Crashday\\Crashday.exe" failed, status
c0000005
He tried different wine versions, downloaded the dll from me (where it works),
reinstalled the program very often and it still wouldn't work as he didn't know
that the dll file simply couldn't be executed.
Here's my feature request:
Write a descriptive message to the output when a dll file can not be executed
because there are no exec rights. This would be very helpful.
PS: This also happened to me once, but I took a very long time to realize, that
this was the same issue.
Here's my friend's forums thread: http://forum.winehq.org/viewtopic.php?p=25912
Thanks for reading.
--
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=8365
Xavier Vachon <xvachon(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xvachon(a)gmail.com
--- Comment #16 from Xavier Vachon <xvachon(a)gmail.com> 2009-06-04 22:37:01 ---
I use the game in windowed mode, and if I either switch workspaces or alt+tab
to another window the game maintains focus for both mouse and keyboard. In full
screen mode, attempting to alt+tab makes the game crash with no terminal
output.
--
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=7902
Xavier Vachon <xvachon(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xvachon(a)gmail.com
--- Comment #15 from Xavier Vachon <xvachon(a)gmail.com> 2009-06-04 22:16:00 ---
This is still present in latest git (1.1.22).
--
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=6181
Xavier Vachon <xvachon(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xvachon(a)gmail.com
--- Comment #20 from Xavier Vachon <xvachon(a)gmail.com> 2009-06-04 21:20:16 ---
With latest git (1.1.22), the schedtool workaround and a clean, non-hacked
wineprefix, the menus are still slow to draw and I have the
"fixme:ddraw:IDirectDrawImpl_WaitForVerticalBlank (0x149840)->(1,(nil)): Stub"
message appearing. The cutscenes however run at normal speed.
--
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=4487
--- Comment #18 from Xavier Vachon <xvachon(a)gmail.com> 2009-06-04 20:52:07 ---
(In reply to comment #17)
> (In reply to comment #16)
> > (In reply to comment #15)
> >
> > Alright. Well, I have The First Decade package, which has WinXP support for the
> > early C&C titles. Should I test it with win95 or winXP compatibility? Also, how
> > should users with multicore CPUs workaround this bug? I noticed the schedtool
> > suggestion, I would need to learn how to use schedtools first before testing it
> > with C&C. Do you have other recommendations?
>
> No, there is no need to test anything on Windows. To workaround, there's
> nothing to learn, build or install schedtool, then instead of doing `wine
> foo.exe` do `schedtool -a 0x1 -e wine foo.exe`
Using schedtool seems to work for me, drawing works fine. However, I have
Dsound issues everytime I click somewhere in a menu.
err:dsound:DSOUND_MixOne Fatal error. Under/Overflow? primary_done=10232,
mixpos=608/71332 (278/32768), primary_mixpos=248, writepos=22784, mixlen=0
It looks like Alexander has these issues as well. Is there a way to work around
this? Is this material for a new bug?
--
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=4487
--- Comment #17 from Jeff Zaroyko <jeffz(a)jeffz.name> 2009-06-04 20:39:50 ---
(In reply to comment #16)
> (In reply to comment #15)
>
> Alright. Well, I have The First Decade package, which has WinXP support for the
> early C&C titles. Should I test it with win95 or winXP compatibility? Also, how
> should users with multicore CPUs workaround this bug? I noticed the schedtool
> suggestion, I would need to learn how to use schedtools first before testing it
> with C&C. Do you have other recommendations?
No, there is no need to test anything on Windows. To workaround, there's
nothing to learn, build or install schedtool, then instead of doing `wine
foo.exe` do `schedtool -a 0x1 -e wine foo.exe`
--
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=4487
--- Comment #16 from Xavier Vachon <xvachon(a)gmail.com> 2009-06-04 20:35:59 ---
(In reply to comment #15)
> (In reply to comment #14)
> > With current git (1.1.22) and a clean, non-hacked prefix, the issue still
> > happens. My output is below, if by any chances relevant.:
> >
> > err:ntdll:RtlpWaitForCriticalSection section 0x7e6a58e0 "x11drv_main.c:
> > X11DRV_CritSection" wait timed out in thread 0018, blocked by 0009, retrying
> > (60 sec)
> >
> > I have a quad-core CPU. Does anybody know if there has been any progress on
> > DirectDraw to address the multicore CPU issues?
>
> I don't think anyone has worked out any details of what's going wrong yet.
> Plus it seems perfectly acceptable to restrict the affinity of the program to 1
> cpu core, since Windows 95, 98/ME never had SMP support and later versions of
> Windows have compatibility modes which could be potentionally working around
> this issue too.
Alright. Well, I have The First Decade package, which has WinXP support for the
early C&C titles. Should I test it with win95 or winXP compatibility? Also, how
should users with multicore CPUs workaround this bug? I noticed the schedtool
suggestion, I would need to learn how to use schedtools first before testing it
with C&C. Do you have other recommendations?
--
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=4487
--- Comment #15 from Jeff Zaroyko <jeffz(a)jeffz.name> 2009-06-04 20:25:55 ---
(In reply to comment #14)
> With current git (1.1.22) and a clean, non-hacked prefix, the issue still
> happens. My output is below, if by any chances relevant.:
>
> err:ntdll:RtlpWaitForCriticalSection section 0x7e6a58e0 "x11drv_main.c:
> X11DRV_CritSection" wait timed out in thread 0018, blocked by 0009, retrying
> (60 sec)
>
> I have a quad-core CPU. Does anybody know if there has been any progress on
> DirectDraw to address the multicore CPU issues?
I don't think anyone has worked out any details of what's going wrong yet.
Plus it seems perfectly acceptable to restrict the affinity of the program to 1
cpu core, since Windows 95, 98/ME never had SMP support and later versions of
Windows have compatibility modes which could be potentionally working around
this issue too.
--
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=4487
Xavier Vachon <xvachon(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xvachon(a)gmail.com
--- Comment #14 from Xavier Vachon <xvachon(a)gmail.com> 2009-06-04 20:22:10 ---
With current git (1.1.22) and a clean, non-hacked prefix, the issue still
happens. My output is below, if by any chances relevant.:
err:ntdll:RtlpWaitForCriticalSection section 0x7e6a58e0 "x11drv_main.c:
X11DRV_CritSection" wait timed out in thread 0018, blocked by 0009, retrying
(60 sec)
I have a quad-core CPU. Does anybody know if there has been any progress on
DirectDraw to address the multicore CPU issues?
--
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.