http://bugs.winehq.org/show_bug.cgi?id=3739
------- Additional Comments From karllinuxtest.relton(a)ntlworld.com 2007-19-04 12:56 -------
Regression testing shows that things started to go wrong with patch commit
5defa499795116cc996085e1142137bb03844200 'Moved update region handling to the
server'
This is not so surprising, since it clearly changes window drawing/handling.
The patch causes very bad behaviour - blank screen and flikering cursor. A
latter patch has obviously made it better - but with the behaviour I now have
with this app. I'll try and find that patch 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=8106
ben(a)atomnet.co.uk changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|wine-directx-ddraw |wine-directx-dplay
------- Additional Comments From ben(a)atomnet.co.uk 2007-19-04 12:45 -------
Sorry, seems to be directPlay not DirectDraw.
--
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=8106
Summary: Age of Empires 2 pagefaults on start
Product: Wine
Version: 0.9.35.
Platform: PC-x86-64
OS/Version: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: wine-directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ben(a)atomnet.co.uk
Age of Empires 2 (with or without expansion) now appears to page fault on start
after issuing some warnings about DirectPlay (but they don't look serious). The
game used to work so this is a regression.
--
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=8104
------- Additional Comments From johan.gill(a)gmail.com 2007-19-04 10:48 -------
A refinement: if it works for most people, I agree that it is not a blocker.
--
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=7346
------- Additional Comments From singpolyma(a)gmail.com 2007-19-04 10:28 -------
Hey sorry guys... I had less time with the system than I thought I did and it
has already been shipped overseas. I will try to get this generated next time
I'm doing a setup, but for now I don't have access to the software. So there's
not much that can be done I guess...
--
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=922
------- Additional Comments From focht(a)gmx.net 2007-19-04 10:03 -------
Hello,
--- quote ---
Can we have Wine detect the buggy installshield and
give a specific warning that directs the user to
a wiki page that describes the fix?
--- quote ---
Detect a broken ishield installation (already present) or quiet prerequisite
installation (presetup step)?
Possible but why hack wine for such deficencies.
-1-
Some shell script that checks for buggy (known) ishield versions by traversing
file system (beware of localized folder names/different ishield version folders)
MD5 on specific files, like "IKernel.exe" which is checked against "bad boy" list.
Only useful if ishield components already present.
Not fool proof, if the app installer brings it's own buggy ishield kernel
(older/newer) along and uses it.
-2-
Hook LoadLibraryA/W and -Ex on api level (like in native windows).
Can be global or local hook (wrapper spawn with dll injection).
That way *any* buggy version of installshield kernel can be detected at runtime.
Detection would be same as 1. -> check module MD5 against list of known "bad boys".
Though one has to ask: how many buggy installshield versions are floating around
and how many wine bug reports might result from this?
You might end up writing detection tools for all sorts of installers ...
I don't see the value by adding such stuff to wine (as scripts/diagnostic tools).
There is already "Wine Known Issues" wiki page present, with that 0x80040706
listed too.
Maybe some link could be added which directs the user to ishield support page
(for this case: http://consumer.installshield.com/kb.asp?id=q110641)
Regards
--
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=8104
------- Additional Comments From johan.gill(a)gmail.com 2007-19-04 10:02 -------
I have a Geforce 6600, with the 9755 driver, which is the latest one at the time
of writing. I did the recommended change to the X config file to enable GLSL.
Also, if it is not a blocker I suggest changing the Bugzilla help text.
--
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=8105
Summary: %SystemRoot%" is not accessible
Product: Wine
Version: 0.9.35.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sz__g(a)freemail.hu
The Protel99 install was succes but the setup maked something wrong.
All my wine programs (totalcmd, winecfg ...) got this:
Warning: the specified Windows directory L"%SystemRoot%" is not accessible.
but all programs run, except the Protel99. It crashes at startup.
--
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.