TheBlunderbuss wrote:
It has just occurred to me that safedisc copy protection (bug 219!)wasn't put on the Wine 1.0 task list. It's a pretty major bug and covers a wide range of programs, with a wide range of safedisc versions. Considering this, how should we plan for this implementation?
Some versions should work. Newer versions mos likely won't. But as usual in these cases your mileage may vary. Since there are so many variables.
Setting target for such bugs to 1.0 won't magically fix them. Nor will it keep them from breaking.
Vitaliy.
On Thu, Apr 24, 2008 at 09:57:39PM -0600, Vitaliy Margolen wrote:
TheBlunderbuss wrote:
It has just occurred to me that safedisc copy protection (bug 219!)wasn't put on the Wine 1.0 task list. It's a pretty major bug and covers a wide range of programs, with a wide range of safedisc versions. Considering this, how should we plan for this implementation?
Some versions should work. Newer versions mos likely won't. But as usual in these cases your mileage may vary. Since there are so many variables.
Setting target for such bugs to 1.0 won't magically fix them. Nor will it keep them from breaking.
There has been some movement in the past to split up the Safedisc bug and deal with the individual versions separately. Would it be useful to advance this? I'm certain that I have a number of games that listed as apps affected by this bug that no longer have a problem. So I'm not sure that it works well to maintain the same bug for all versions of safedisc.
Darragh Bailey wrote:
There has been some movement in the past to split up the Safedisc bug and deal with the individual versions separately. Would it be useful to advance this? I'm certain that I have a number of games that listed as apps affected by this bug that no longer have a problem. So I'm not sure that it works well to maintain the same bug for all versions of safedisc.
I think that's a good idea
-
Darragh Bailey -
TheBlunderbuss -
Vitaliy Margolen