[Bug 13273] New: Wine does not remember disk labels set through winecfg
http://bugs.winehq.org/show_bug.cgi?id=13273 Summary: Wine does not remember disk labels set through winecfg Product: Wine Version: 1.0-rc1 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ccf2egd02(a)sneakemail.com Wine does not seem to remember disk labels or serial numbers when set via winecfg. Steps to reproduce: 1) create a disk entry in ~/.wine/dosdevices ln -s /someplace_with_CD_image ~/.wine/dosdevices/q\: 2) run winecfg, select disk tab. 3) Select q: 4) Show advanced 5) Set to manual setup, disk label to "SOMETHING", disk ID to "FEEDBE" 6) APPLY 7) verify data by selecting some other drive, then re-selecting q: 8) quit winecfg 9) Restart winecfg and reselect the disk tab. Reselect q: Expected results Disk label should be "SOMETHING", id should be "FEEDBE" Actual results Disk label unset, disk ID 0 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 Lei Zhang <thestig(a)google.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |minor Status|UNCONFIRMED |NEW Component|-unknown |programs Ever Confirmed|0 |1 --- Comment #1 from Lei Zhang <thestig(a)google.com> 2008-05-17 15:45:08 --- confirmed. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #2 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2008-05-17 22:02:42 --- For a "fake" drive Wine tries to read .windows-label and .windows-serial from the root of the drive for label and serial accordingly. And winecfg does not write anything to those files. Nor does Wine. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #3 from David Hagood <ccf2egd02(a)sneakemail.com> 2008-05-18 10:05:39 --- If those fields don't work, then they shouldn't be in winecfg. If they are in winecfg, they should work. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 Ben Klein <shacklein(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |shacklein(a)gmail.com --- Comment #4 from Ben Klein <shacklein(a)gmail.com> 2008-06-03 21:12:53 --- Note that the label/serial for CD-ROMs get set correctly in the "Manually Assign" fields, even though "Autodetect from Device" is apparently not implemented. From what I can tell, what needs to be done is: 1) Allow "Autodetect from Device" to be selectable, and make it the current functionality 2) For the "Manually Assign" fields, actually write the data into the registry! 3) Implement a new label/serial faking system, where Wine looks up the appropriate fields in the registry and reports those back to applications when the label or serial is requested -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #5 from David Hagood <ccf2egd02(a)sneakemail.com> 2008-06-03 21:31:03 --- Actually, detecting the data from an actual CDROM worked for me - indeed, that was how I got the UID for the CDs I was imaging onto my server. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 Pete Lesko <leskop(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leskop(a)yahoo.com --- Comment #6 from Pete Lesko <leskop(a)yahoo.com> 2008-09-15 13:28:15 --- I ran across this bug while looking for a solution to get "ReBirth" to run under wine because it looks for the CD as a copy protection mechanism. winecfg *does* in fact write to the .windows-label file and .windows-serial, but here's the problem. If you mount an ISO image in a location with a command such as: mount -o loop -t iso9660 /home/me/coolprogram.iso /mnt/coolprog You cannot change the "label" because the filesystem will be interpreted as a read only cdrom type. If you cannot create .windows-label and/or .windows-serial in that directory, winecfg will not remember the label's serial or label. The workaround: Instead of mounting an ISO image, extract the files on it into a new directory, and use that instead. Perhaps winecfg could indicate "I couldn't write to this file space because of a permission problem" or something to that effect? (In reply to comment #2)
For a "fake" drive Wine tries to read .windows-label and .windows-serial from the root of the drive for label and serial accordingly. And winecfg does not write anything to those files. Nor does Wine.
-- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #7 from Ben Klein <shacklein(a)gmail.com> 2008-09-15 16:43:04 --- (In reply to comment #6)
winecfg *does* in fact write to the .windows-label file and .windows-serial, but here's the problem.
Wine should not *write* the .windows-label or .windows-serial files, since ISO9660 (an in particular CDROMs) are read-only filesystems. I stand by what I said in comment #4, and still believe it is the correct solution to the problem. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 Jörg Höhle <hoehle(a)users.sourceforge.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hoehle(a)users.sourceforge.net --- Comment #8 from Jörg Höhle <hoehle(a)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. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 ChALkeR <chalkerx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chalkerx(a)gmail.com --- Comment #9 from ChALkeR <chalkerx(a)gmail.com> 2009-01-23 12:50:12 --- Ok. Tried to install Utawarerumono from a mounted iso image (I have an eeePC, no dvdrom here). The game installer (installed from english-patch, that was separate from the iso) searches for a disk by disk label. 1) Tried mounting with fuseiso and adding a disk + autodetect parameters. Autodetecting media type and disk label does not work. Failed. 2) Same as #1, but setting parameters manually. Setting media type manually works, setting disk label does not work. Failed. 3) Tried mounting as root with -o loop. (mount -o loop *.iso /media/vdrive ). Autodetecting disk label does not work. Failed. 4) Same as #3, but with "sudo chmod 0744 /dev/loop0". Here autodetecting media type _and_ disk label works, and I was able to launch the installer. OK. But it is a bad idea to use root access for that what could be done in user mode. And giving user permissions to read the whole root-mounted device - too. #1 and #2 could be fixed. #2: just fix the field and store the disk id and label in registry in the same place, as disk type. #1: just make it work as #4, but look for the paths to devices in fuse. (~/.mtab.fuseiso). It is probably a different wine bug with fuse. Should I open a new bugreport? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #10 from Ben Klein <shacklein(a)gmail.com> 2009-01-23 15:32:37 --- (In reply to comment #9)
Ok. Tried to install Utawarerumono from a mounted iso image (I have an eeePC, no dvdrom here). The game installer (installed from english-patch, that was separate from the iso) searches for a disk by disk label.
1) Tried mounting with fuseiso and adding a disk + autodetect parameters. Autodetecting media type and disk label does not work. Failed. 2) Same as #1, but setting parameters manually. Setting media type manually works, setting disk label does not work. Failed. 3) Tried mounting as root with -o loop. (mount -o loop *.iso /media/vdrive ). Autodetecting disk label does not work. Failed. 4) Same as #3, but with "sudo chmod 0744 /dev/loop0". Here autodetecting media type _and_ disk label works, and I was able to launch the installer. OK.
But it is a bad idea to use root access for that what could be done in user mode. And giving user permissions to read the whole root-mounted device - too.
#1 and #2 could be fixed.
#2: just fix the field and store the disk id and label in registry in the same place, as disk type.
#1: just make it work as #4, but look for the paths to devices in fuse. (~/.mtab.fuseiso).
It is probably a different wine bug with fuse. Should I open a new bugreport?
Do you have a device node link in ~/.wine/dosdevices that points to the ISO file? #1 may not be easily fixed. Wine can't account for ever single irregularity in various fuse drivers, and autodetecting a mounted image (especially one that's not in fstab) is always a problem because it just looks like another directory. I proposed a method for fixing #2 in comment #4. In your #4, if the problem is fixed by making the loop device readable by your normal user, then it's not really a problem with Wine, and it would probably be fixed by the device node link I mentioned before. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #11 from ChALkeR <chalkerx(a)gmail.com> 2009-01-23 18:06:28 --- (In reply to comment #10)
Do you have a device node link in ~/.wine/dosdevices that points to the ISO file?
Ok, thank you ). I created a f:: pointed to the iso. That removes the "sudo chmod 0744 /dev/loop0". But it still works only with mount command, if f: is mounted via fuse - this method does not work. Like any other method ).
#1 may not be easily fixed. Wine can't account for ever single irregularity in various fuse drivers, and autodetecting a mounted image (especially one that's not in fstab) is always a problem because it just looks like another directory.
This is how mounted via mount iso looks in /etc/mtab: /dev/loop0 /media/vdrive iso9660 rw 0 0 This is how mounted via fuseiso iso looks in ~/.mtab.fuseiso: /path_to_iso.iso /path_to_mountpoint fuseiso defaults 0 0 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #12 from Ben Klein <shacklein(a)gmail.com> 2009-01-23 19:03:41 --- (In reply to comment #11)
(In reply to comment #10)
Do you have a device node link in ~/.wine/dosdevices that points to the ISO file?
Ok, thank you ). I created a f:: pointed to the iso. That removes the "sudo chmod 0744 /dev/loop0". But it still works only with mount command, if f: is mounted via fuse - this method does not work. Like any other method ).
Sounds good to me! Is there any particular reason why you want to use fuse? Also note that in the case of CD images, cdemu may be more appropriate than fuse.
This is how mounted via mount iso looks in /etc/mtab: /dev/loop0 /media/vdrive iso9660 rw 0 0
This is how mounted via fuseiso iso looks in ~/.mtab.fuseiso: /path_to_iso.iso /path_to_mountpoint fuseiso defaults 0 0
This is something specific to your fuse ISO driver. It's not standard, and I really don't think Wine should be made aware of it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #13 from Austin English <austinenglish(a)gmail.com> 2009-07-30 12:05:57 --- Is this still an issue in current (1.1.26 or newer) wine? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 ahso47(a)yahoo.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ahso47(a)yahoo.com --- Comment #14 from ahso47(a)yahoo.com 2010-01-11 10:06:55 --- confirm same here. I can't set D:\ for the cdrom which i need to access for Flight simulator 2004 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #15 from ahso47(a)yahoo.com 2010-01-13 01:24:41 --- (In reply to comment #14)
confirm same here. I can't set D:\ for the cdrom which i need to access for Flight simulator 2004
PS: I'm on openSuse 11.2 with the current wine. automount uses /media/FS_DISC4 which is not found by wine. Earlier wine versions found the cd after mounting to /mnt/cdrom but not anymore. So thanks for help. ( i didn't understand some "fixes" here above ) Michael -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #16 from Austin English <austinenglish(a)gmail.com> 2011-03-29 19:30:47 CDT --- This is your friendly reminder that there has been no bug activity for 6 months. Is this still an issue in current (1.3.16 or newer) wine? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 Márcio <marcio(a)verdesaine.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marcio(a)verdesaine.net --- Comment #17 from Márcio <marcio(a)verdesaine.net> 2011-10-06 09:26:57 CDT --- I have been trying to use the construction budget software "Engwhere Magma" on Wine 1.3.26. The protection scheme of this software includes checking a pendrive label and serial in order to allow you to use it. But winecfg don't save this data properly. The serial is a two part hexadecimal number in this format: 4 hexa digits, a minus signal, and more 4 hexa digits. Example: A1B2-EF0A By putting the label inside a .windows-label file on the pendrive it is possible to set correctly the label. But putting the serial inside a .windows-serial file don't work. Winecfg shows only the first part of the serial, ignoring everything from the minus signal until the end. If we put, for instance, A1B2-EF0A on the file, winecfg shows only A1B2. Somehow winecfg does not accept the minus signal on the serial or consider it as a line end. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #18 from Alexandre Julliard <julliard(a)winehq.org> 2011-10-06 10:22:51 CDT --- The serial number is a dword, it shouldn't contain a dash. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #19 from Márcio <marcio(a)verdesaine.net> 2011-10-07 07:43:29 CDT --- (In reply to comment #18)
The serial number is a dword, it shouldn't contain a dash.
The serial I am talking about is the volume serial number - that you can check using the command "vol" in windows command line, and it have a dash, as you can see here http://en.wikipedia.org/wiki/Vol_(command) C:\Users\root>vol C: Volume in drive C is Vista Volume Serial Number is 080F-100B Wine is not getting the right volume serial number and not accepting alternative ways of setting it like using winecfg or creating by hand a .windows-serial file. The volume in question is a USB pendrive. Greetings, Márcio -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #20 from Alexandre Julliard <julliard(a)winehq.org> 2011-10-07 10:27:15 CDT --- It's a dword internally, the dash is just pretty printing, it's not part of the serial. Just get rid of it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 Vitaliy Margolen <vitaliy-bugzilla(a)kievinfo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kelytharun(a)gmail.com --- Comment #21 from Vitaliy Margolen <vitaliy-bugzilla(a)kievinfo.com> 2012-02-21 21:59:01 CST --- *** Bug 29966 has been marked as a duplicate of this bug. *** -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=13273 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, source --- Comment #22 from Austin English <austinenglish(a)gmail.com> --- Still in wine-1.7.16-135-g7f311fb -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=13273 --- Comment #23 from Austin English <austinenglish(a)gmail.com> --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.16 or newer) wine? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=13273 ReaperX <reaper2021(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |reaper2021(a)protonmail.com --- Comment #24 from ReaperX <reaper2021(a)protonmail.com> --- As of 2019 and wine version wine-4.18, this is still a problem. Winecfg forgets drive labels as soon as you enter them. It's not a dealbreaker, but it's an annoyance- it would be nice if your "drives" in windows apps could have labels. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=13273 Thespikedballofdoom <thespikedballofdoom@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thespikedballofdoom@gmail.c | |om --- Comment #25 from Thespikedballofdoom <thespikedballofdoom@gmail.com> --- Still going on leading into 2026... uck... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (3)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla -
WineHQ Bugzilla