http://bugs.winehq.org/show_bug.cgi?id=2131
Speeddymon(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |1434
nThis| |
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Summary|freecell fails to load |16-bit games bundled with
| |windows fail to load
| |(freecell, solitaire)
------- Additional Comments From Speeddymon(a)gmail.com 2005-07-05 20:02 -------
I wouldnt say WONTFIX, Ill forward a note to wine-devel and see if they think
its worth it to add in 16-bit calls to the dll. Basically for them it should be
semi-trivial, only because they already have a working 32-bit version, they just
need the functions to either convert the 32-bit functions to 16-bit, or just add
something like an if running 16-bit game use these functions, else use the
32-bit ones..
Of course if they say WONTFIX, we should add a note to the Users guide about the
fact that we are slowly moving (have moved?) away from 16-bit support, and that
therefore win98/me programs (bundled with the os or not) may not work.
Since it is an issue, confirming.
--
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=2131
------- Additional Comments From felix.nawothnig(a)t-online.de 2005-07-05 19:49 -------
Confirmed. (I first tried the WinXP version which works fine)
It doesn't run because Win9x/ME ships a 16 bit cards.dll, the one which comes
with WinXP is 32 bit (and so is ours).
The Win9x freecell.exe doesn't run with the 32 bit cards.dll on WinXP either.
Since the 16 bit and 32 bit versions share the same name in this case it is not
really fixable. (Well, I think it would be possible to hack together a
workaround but I don't think it would be worth the effort (and probably would be
rejected anyway :) since freecell.exe and sol.exe are probably the only programs
ever written which only work with the 16 bit version - the cards.dll tutorial on
the web discusses the problem and gives example code which will run on both
Win9x and NT (and on Wine I guess)).
WONTFIX?
P.S.:
This errorcode (21 - ERROR_NOT_READY) still bothers me.
ne_module.c explicitly sets it when
(
LoadLibraryA()ing the owner of a 16bit dll failed
or
the search for the 16bit dll returned a real (.so)
dll and not a symlink to the owner
) and trying to load a native version of the 16bit dll failed with
ERROR_FILE_NOT_FOUND.
... huh?
--
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=2939
------- Additional Comments From inverseparadox(a)comcast.net 2005-07-05 18:01 -------
Yes, the "freeze" does represent a behaviour change; before the "can't change
resolution/won't run" failure first occurred, upon completion the program would
exit normally. Similarly, at first when the failure occurred, the window would
close after I acknowledged the pop-up DDraw error. After a while, though, the
behaviour changed to the one described - the window remains, unresponsive, until
Wine is killed.
It takes me a while to track down change dates, since it takes at bare minimum
fifteen minutes for a typical recompile and then I have to notice that it's done
and go test, but with luck the new bug should show up before I have to go to
work tomorrow evening. Unless someone specifically requests such, I won't post
anything more to this one.
--
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=2035
------- Additional Comments From lubosd(a)gmail.com 2005-07-05 17:46 -------
Winealsa still does not work. I tried it with Call of Duty and the game fails on
waveOutOpen. Wineoss works fine.
--
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=2939
Speeddymon(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|VERIFIED |CLOSED
------- Additional Comments From Speeddymon(a)gmail.com 2005-07-05 17:24 -------
Ahh, thanks. As far as tracking down a commit date that it stops working, did
it "used to work" that you know of? Or is it pretty much a wild guess that it
has worked in the past?
Reason I ask is because you may be wasting your own time trying to find a patch
that caused it to break, when there wasn't any specific one (its always been
broken). Just thought you should know, and Ill keep up with the new bug too.
Patch committed, closing.
--
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=2939
------- Additional Comments From inverseparadox(a)comcast.net 2005-07-05 17:14 -------
As it happens it already has been committed, this morning; I'm compiling the
updated CVS version now. I'm not sure I know what to search on to look for bugs
matching the more general second issue (since I don't have explicit error
messages), but a few somewhat cursory queries find nothing; I'm going to go
track down the offending commit date and open a new bug.
--
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=2905
Speeddymon(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |1434
nThis| |
Severity|blocker |critical
Status|UNCONFIRMED |NEW
Component|wine-binary |wine-misc
Ever Confirmed| |1
------- Additional Comments From Speeddymon(a)gmail.com 2005-07-05 16:47 -------
Changing severity, attaching to games bug, confirming per bug output, forwarding
log file to wine-devel.
--
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=2939
Speeddymon(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
------- Additional Comments From Speeddymon(a)gmail.com 2005-07-05 16:25 -------
I would say to use the query bugs link in the left navbar to try and find any
bugs that may be open about the 2nd issue, and if non are able to be found, go
ahead an file a new bug. Since this patch has been verified as fixing the
issue, I am marking it as such. Will have to close after the patch has been
committed.
--
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=2939
------- Additional Comments From inverseparadox(a)comcast.net 2005-07-05 16:15 -------
Confirmed, the patch submitted fixes the first and most significant problem:
Might and Magic VI now runs for me (and oddly enough, now no longer exhibits an
undesirable behaviour which I had attributed to a misconfigured window manager).
However, this still leaves a second problem, which I mentioned once before as
having cropped up at some point after the other problem came to exist: upon
program exit, the program window does not close, but remains frozen until Wine
is killed.
I'm well aware that this is very likely a completely unrelated issue, requiring
its own regressions to track down. My immediate question is one of protocol:
should I continue to post information on the remaining problem here, or open a
new bug to discuss it? (Or is there an existing open bug which may already cover
the problem?)
--
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.