winecfg volume serial number

James Hawkins truiken at
Thu Dec 18 16:53:02 CST 2008

On Thu, Dec 18, 2008 at 2:47 PM, Michael Ost <most at> wrote:
> James Hawkins wrote:
>> On Thu, Dec 18, 2008 at 12:31 PM, Michael Ost <most at>
>> wrote:
>>> wine-devel-request at wrote:
>>>> Date: Tue, 16 Dec 2008 13:52:00 +0100 From: "Hoehle, Joerg-Cyril"
>>>> <Joerg-Cyril.Hoehle at> Subject: winecfg volume serial
>>>> number To: <wine-devel at> Message-ID:
>>>> <47CC5ABB01651443A88DB8EC5B4D657B01C8FD22 at>
>>>>  Content-Type: text/plain;    charset="iso-8859-1"
>>>> Hi,
>>>> I just sent a bug-fix to wine-patches to prevent a crash in winecfg
>>>> when editing the volume serial number input field, together with some
>>>> unrelated thoughts about winecfg and the device/volume serial number
>>>> handling. Then I realized that wine-patches is not a good place for
>>>> discussion. So here are the ideas about winecfg's GUI:
>>> It doesn't make sense to me to rely on writing to a file to set the
>>> windows serial number or label. What about readonly disks?
>>> I think those values should be in the registry. Or at least check the
>>> registry should be a fallback if .windows-serial or .windows-label does
>>> not exist.
>>> I am stuck now because an installer program is looking for a CD of a
>>> certain label. I can't fudge in the label because it's a CD that I can't
>>> write to.
>>> Is anyone working on this issue, or agree/disagree? ... mo
>> The label of the CD is read from the disk.  If you're using a mounted
>> ISO, you have to fix the access rights of the loopback file
>> representing the ISO file.
> Yes, you are right. And this does work.
> In my system I am mounting a remote CD over samba and creating a drive
> letter for it in Wine. That's the disc that the installer wants to query. I
> was hoping to be able to set the label for the "network" drive to work
> around this issue. But the CD is read only so I can't write the file.
> So I am trying to do something tricky, that is probably not even possible in
> Windows. And I'll probably just have to my own internal Wine hack to get
> this to work.

I don't understand the problem.  If you have the proper permissions,
wine should be able to read the volume name and everything should just
work.  What does volname give you for the network-mounted image?

James Hawkins

More information about the wine-devel mailing list