https://bugs.winehq.org/show_bug.cgi?id=33292
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #1 from Anastasius Focht focht@gmx.net --- Hello folks,
is this problem still present? Please retest with recent Wine 1.7.x version, preferably Wine 1.7.33
From what you've described it could be the data density measurement phase
failing here. I've described it here: https://bugs.winehq.org/show_bug.cgi?id=10190#c21
--- quote --- The original media is recognized in general but there are some cases where it still fails. The reason is there a high precision time measurement done during software and optical drive interaction, called "data density measurement".
There is a set of locations spread over the disc which are read using pairs of SCSI read commands (pass-through) per location from the drive. You can watch them using +cdrom channel. While the disc spins the time is measured it takes for the second command to return (depends on the time it takes the disc to do a full round = depends on the data density). Combining all predefined locations a vendor specific pattern is formed and verified.
Wine might not be able to reliably guarantee certain timing constrains.
If your disk fails to be recognized this helps:
- start wineserver and services prior (notepad/whatever in different terminal) - wait a bit until the drive/media completely stopped spinning before start
Don't run any CPU intensive processes in background that cause workload spikes during time measurement/calibration phase.
(still fails: try again) --- quote ---
If it still fails many times with the "time limit" message there is not much that can be done here, unless you use less crappy original media (DVD) and better host hardware (certain disk drives/models are pretty crappy when it comes to validating copy protected media). Likely a WONTFIX.
Regards