http://bugs.winehq.org/show_bug.cgi?id=13273
Jörg Höhle hoehle@users.sourceforge.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hoehle@users.sourceforge.net
--- Comment #8 from Jörg Höhle hoehle@users.sourceforge.net 2008-12-16 06:23:49 --- To me, this is a regression. I remember long ago using winecfg to define labels and to declare a given directory hierarchy on my HD as CD-ROM (e.g. Syberia2). This created the files .windows-label and .windows-serial there.
Thus IIRC Vitaliy is wrong in comment #2:
And winecfg does not write anything to those files. Nor does Wine.
Winecfg tries. The log says: trace:winecfg:apply_drive_changes warn:winecfg:set_drive_label unable to set volume label for devicename of L"E:\", label of L"xyz" trace:winecfg:PRINTERROR error: 'Access denied' I don't know why it gets that error from directory "/dev/shm/foo/bar".
Nowadays (I tried 1.0.1 and 1.1.10), labeling within winecfg does not seem to work anymore, and I'm writing .windows-label by hand into the relevant directory when I need it. OTOH it *sometimes* seems to work.
By contrast, setting a serial number succeeds in creating the .windows-serial file. (Don't clear the input field in 1.1.6 - 1.1.10, or winecfg crashes. I just submitted a fix to wine-patches to fix that).
Regarding comment #7 (using the registry instead of .windows-xyz), I see it as an valuable but distinct enhancement request, while the current issue is IMHO a regression.