http://bugs.winehq.org/show_bug.cgi?id=30632
--- Comment #14 from Alex cerebro.alexiel@gmail.com 2012-05-16 02:05:05 CDT ---
[...] is reset to be owned by "root:disk" and only root can access files. [...]
No, nothing is reseted. When you create a regular file (text, movie, ISO...), you are the owner of the file because you created it. A symbolic link points to another file, in your case something like /dev/cdrom. If you do $ls -l /dev/cdrom, you'll see "root" as the owner and "disk" for the group. This is because the /dev directory is created dynamically at boot time by the system (hence root as the owner). But since users may need to access the cdrom content, the group is set to "disk". If you're confused by linux permissions, owner and groups, maybe you should learm more about it by googling these terms.
So Bruno is right, by belonging to the "cdrom" group, you should be able to dd the game without being root. The $groups command lists the groups you are belonging ro.
If you can dd the game being hendrik, then you'll also be the owner of the ISO file. Then, wine will have the read access to your symbolic link .. and the ISO content.
[...] sudo mount -r -o uid=1000,gid=1000 /dev/cdrom /media/Sims3 [...]
Mine is mounted read only so -r seems useless. Also, from your $ls -l /media/Sims3, all seems ok so no need to force the user and the group. All you need is reading files in /media/Sim3.
Except this rights issue, the bug remains : with the ISO file, the game works while with the real disc, it does not. I must admit I only played the game with the ISO because it's handy and faster (I tried installing the game with the disc but it was sooooo long..)
Even if our disc are not identical (md5sum different), I will try playing the game with the real dic (and install with the ISO file as it seems an independant issue).
Finally (yes, I speak a lot), I started reading your log file and you was right, no MessageBox presence so I will have to take some time to read it. Are you sure the error appeared while recording the log ? Just to be sure the error is contained in the log...