I recently patched Warcraft 3 to 1.15, and decided I might as well try running it without a no-cd patch. To my surprise, it whirred for a bit and then detected the CD, which had never worked before. I don't know whether the difference was something about the version of WC3, or because I'd just upgraded to a 2.6 kernel, or because of the Wine version (20040309), but having upgraded Wine to 20040505 it no longer works. I've set up the devices symlinks and tried using both a new config file and the old one with the drives setting removed (as suggested by Wine's output), but I still have to use a crack again now. It's not the end of the world, but it did seem really cool for about 3 days:-(. Any idea why this would be? I don't really know what was changed recently with the alterations to the way drives are set up... Anyway, thought it might be worth mentioning, Aneurin Price.
On Sun, 2004-05-16 at 13:35, Aneurin Price wrote:> but I still have to use a crack again now.You don't *have* to do that at all. You could always pay for the software you've stolen...
> You don't *have* to do that at all. You could always pay for the > software you've stolen...Maybe you're not aware of what's going on. Actually you're certainly not sure about what's going on. This guy HAS bought the software, and HAS paid for it, but the original CD has copy protection, so he can only use his legally bought and paid software on wine with a cd crack, otherwise his legally licensed software won't work on linux and wine. If he was using stolen software, he wouldn't even be aware of the problem. Feel free to apologize to him. Ivan.
> I don't know whether the difference was something about the version of WC3, or > because I'd just upgraded to a 2.6 kernel, or because of the Wine > version (20040309), but having upgraded Wine to 20040505 it no longer works.Some work was done to load the copy protection drivers, it would be very nice to get this working again. Can you try wine-20040408 to see if it works with that version? You can then pinpoint the regression by running CVS regression testing, instructions are at http://www.winehq.com/site/docs/wine-devel/cvs-regression Ivan.
Aneurin Price wrote:> They're not directories because they're symlinks to the devices, but > obviously the game cannot find the cd if the drive has been ignored. > Similarly, if I mount the cd and point the symlink to the mount point, > the game doesn't have access to the device to do its copy protection > routine.> I presume a similar thing is happening with 20040505, since after > checking (by just running an app and looking in the open file dialogue) > I've discovered that the contents of the cd aren't being read, so it > must need the device symlink to point to the mount point. How then would > one also provide it with the device as could previously be done using a > "Drive" entry in the config file?man wine says: $WINEPREFIX/dosdevices Directory containing the DOS device mappings. Each file in that directory is a symlink to the Unix device file implementing a given device. For instance, if COM1 is mapped to /dev/ttyS0 you???d have a symlink of the form $WINEPREFIX/dosdevices/com1 ???> /dev/ttyS0. DOS drives are also specified with symlinks; for instance if drive D: corresponds to the CDROM mounted at /mnt/cdrom, you???d have a symlink $WINEPREFIX/dosdevices/d: ???> /mnt/cdrom. The Unix device corresponding to a DOS drive can be specified the same way, except with ???::??? instead of ???:???. So previous exam??? ple, if the CDROM device is mounted from /dev/hdc, the corre??? sponding symlink would be $WINEPREFIX/dosdevices/d:: ???> /dev/hdc. HTH
> I'd be happy to do some CVS regression testing if you think it's still > worth itYes, it is. Install wine-20040309 form CVS and see if it works. If it does, upgrade to wine-20040408, always using the CVS. It probably won't work. Once you're sure about this, try something like wine-20040320 and so on, until you can pinpoint the patch that caused the regression. You can see the time, description, and contents of patches at http://www.winehq.com/hypermail/wine-cvs/ once you find the patch that caused the problem, send an email to the wine-devel list. Hopefully someone will fix the problem. Ivan.