http://bugs.winehq.org/show_bug.cgi?id=7782
Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xerox_xerox2000(a)yahoo.co.uk
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #3 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> 2007-10-07 01:42:54 ---
Hi, this should be fixed in current git (see more info at
http://www.winehq.org/pipermail/wine-patches/2007-October/044740.html )
Try either current git or next wine-release 0.9.47, and reopen if you still run
into trouble.
--
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=8867
Chris <chris.kcat(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |chris.kcat(a)gmail.com
--- Comment #2 from Chris <chris.kcat(a)gmail.com> 2007-10-07 01:32:02 ---
Water seems to be mostly working for me now, using the latest git. See bug
#9931 for a screenshot. Are you using fbo, pbuffer, or backbuffer for offscreen
rendering?
--
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=7579
Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #14 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> 2007-10-07 00:21:14 ---
closing
--
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=7579
Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xerox_xerox2000(a)yahoo.co.uk
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
--- Comment #13 from Louis Lenders <xerox_xerox2000(a)yahoo.co.uk> 2007-10-07 00:21:00 ---
>Sorry for the delay -- already one of the previous wine versions released after
>your last comment did work, so I suppose this bug can be closed.
Reported fixed
--
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=9098
Kenneth Brown <SagaciousKJB(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |SagaciousKJB(a)gmail.com
--- Comment #2 from Kenneth Brown <SagaciousKJB(a)gmail.com> 2007-10-06 23:59:52 ---
I had this problem as well. I initially installed DirectX 9 from the GTASA
installer after having the game running without it, once this was done it
crashed after the NVIDIA logo. I did not track it back to that .dll, but after
getting rid of DirectX 9 the game ran fine.
--
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=5723
Kenneth Brown <SagaciousKJB(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |SagaciousKJB(a)gmail.com
--- Comment #45 from Kenneth Brown <SagaciousKJB(a)gmail.com> 2007-10-06 23:34:12 ---
Using wine version 0.9.46 and this is still an issue, disabling pixel/vertex
shading still solves it
--
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=6591
--- Comment #30 from Marco Trevisan (Treviño) <trevi55(a)gmail.com> 2007-10-06 20:17:02 ---
(In reply to comment #27)
> If you use current wine (0.9.46), and start with a clean
> .wine directory, and use winetricks to install the visual C++
> runtimes (e.g. wget http://kegel.com/winetricks; sh winetricks vcrun2006),
> does it work for you?
Well, yes it seems it works, but the script is downloadable from
http://www.kegel.com/wine/winetricks and the right command is sh winetricks
vcrun2005, but the essential thing is right...
(In reply to comment #28)
> @Marco Trevisan:
> I tried that Osiris app thingy, and it comes with it's own vc2005redist. You
> should just install this app on a new ~/.wine. It then loads msvcr80.dll just
> fine. However it then run into another bug, loading another dll fails, but
> seems that one can be fixed quite easily. I'll have a look into it.
Well, in fact I had the mentioned error, when I tried to run that app from the
"zip version" while, installing it with the setup.exe, the app installed, then
I need to extract libnspr
(ftp://ftp.mozilla.org/pub/mozilla.org/nspr/releases/v4.6.4/msvc6.0/WINNT5.0…)
to its directory... After that the software started, but then it freezes while
loading plugins, but maybe I should open another bug for it also if a porting
for linux is planned...
Bye
--
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=8033
--- Comment #39 from James Hawkins <truiken(a)gmail.com> 2007-10-06 19:27:39 ---
(In reply to comment #38)
> (In reply to comment #37)
> > It sounds like you're adding registry entries
> > from Windows to make the app work in the first place. Is that the case?
>
> Of course not; the missing registry entries were presumably installed by either
> the application itself or its installation process. (It's Windows - Windows
> applications do that sort of thing!)
>
What missing registry entries? Are you copying over the app installation from
a Windows install?
> And yes, this is a regression of sorts in that I installed the application with
> Wine 0.9.3x and it broke when I upgraded to Wine 0.9.35. The fix posted in bug
> #8033 kept me running until 0.9.42 was released and then bug #9147 broke it
> again.
>
> > Keeping a wineprefix between version is extremely common, but you miss the
> > point that it's not guaranteed to work.
>
> No, I get that it's not guaranteed to work. It's the "(lack of) what happens
> next" that I am having trouble with. In particular, your "sanitized" wineprefix
> approach that just looks like a back-handed way of telling your users to go
> away and reinstall all their applications.
>
> If you're going to create mandatory registry entries in Wine that will make
> Wine crash/explode if they're not present then you need to find a way to update
> the .reg files in users' .wine/ directories too. Or put all these critical
> entries into an unmodifiable wine.reg file that every wine installation loads
> at start up. Or SOMETHING.
What mandatory registry entries are you talking about? Registry entries are
created *only* when you run wineprefixcreate, so you have to remove the old
.wine and generate a new .wine. This also gets rid of any cruft from
installing other apps that may interfere with the bug (installation and
uninstallation in Wine is not complete and that's another reason why this is
the policy).
> Because no-one who installs Wine as binary packages
> is *ever* going to be interested in recreating his/her .wine directory each
> time they update. E.g. do you have any idea how much work is involved to
> install World of Warcraft, with all of its patches and expansion packs?
>
Do you read what I say?
$ mv .wine .wine-save
$ wineprefixcreate
$ test app
$ mv .wine-save .wine
voila! Your old apps are back...
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.