Is it just me, or did Wine > 0.9.12 break CD protection?

[Firewing1]

Hey,
I'm just wondering, has anyone else noticed since upgrading wine from 0.9.12 (to 0.9.19 current, I've also tried compiling 0.9.20) CD protection in games is now broken? I used to be able to play Warcraft III without a CD crack, but it seems I can't anymore :(
Firewing1

[Jongi]

So are you saying know you need a CD crack?

[Firewing1]

If I wanted to play in Linux, yes I would but I don't - I prefer staying legal so I reboot into Windows :( :eek:
I've made a bug report, and apparently the build servers use GCC 4.x - And that, according to Wine HQ, breaks the CD protection features in Wine.
Firewing1

[3006828]

GCC-4.. is there nothing it cant do :D

[Firewing1]

lol... I'm going to try a re-compile of wine with compat-gcc32...
EDIT: Funny thing, Starcraft's working...
Firewing1

[Firewing1]

Hmmm... This is even weirder - Starcraft (expansion, too) and Diablo II LoD both work. Warcraft (III)'s a no-go. Off the AppDB page, this break SecuROM on CDs: * Linux vanilla x86 kernel: 2.6.9, 2.6.10 * Linux vanilla x86-64 kernel: 2.6.9-2.6.15
* Linux kernel versions less that 2.6
* Wine compiled with GCC 4.0.0-4.0.2
* Native msvcrt.dll
* Nvidia video driver compiled against mismatched X11 header files

Does the livna driver count as mismatched? I'm all goon on everything else:

gcc-4.1.1-19
kernel-2.6.17-1.2586.fc6
Non-naitive msvcrt.dll

EDIT: If I boot back to my old FC5 installation, it works. The FC5 has:
hal-0.5.7-3.fc5.2
dbus-0.61-3.fc5.1
wine-0.9.17-1.fc5
kernel-2.6.17-1.2157_FC5
gcc-4.1.1-1.fc5

So it's not the GCC, wine or kernel. Maybe HAL / DBUS?

Firewing1

[Thetargos]

Now that you mention it, it indeed broke my WIII install... Since I do the CD and legally own the key, I installed a crack (backing up my originals, of course!), and that allowed me to play, still reading music and stuff from the CD, though.

I hope this gets fixed in an upcoming version of Wine (I could resort to using my legally owned Cedega, but for some strange reason that feels way too similar as using Windows® altogether as of late).

[Firewing1]

OK, so I'm not alone... The odd thing is, I rebooted into my FC5 install, and it works - I assume you're in FC6 development, too?
Firewing1

[Thetargos]

I use both, actually... But since I'm heaviliy testing, I'm primarily using FC6, will have to test on FC5 later today.

[Firewing1]

I found it. I just installed the newest FC5 kernel onto FC6, and now wine can load the CD properly. So the development kernels break wine.
It's a good workaround for me - I don't use Xen anyways, so I don't miss much in the kernel, but I still get to use all the development versions of stuff! :D

I've reported a bug here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=204270

Firewing1

[Thetargos]

Hmm... So that explains it. I installed a custom 2.6.17 kernel on Core 6 and you are right it works. On Core 5 I don't have any 2.6.18 kernel yet, so that may very well explain the problem... It may be an issue of how 2.6.18 handles optical drives.

[Firewing1]

AFAIK, 2.6.18 is 2.6.17... So they're one and the same.
EDIT: Nopte, just checked... I dunno where I read that piece of information, but you're right 2.6.17 is stable, and the 2.6.18 is the development kernel. I, too, only have 2.6.17 on both FC5 and 6, but the new(er) ones from FC6 somehow manage to break Wine's CD detection...
Firewing1