On Thu, Dec 18, 2008 at 3:07 PM, Michael Ost wrote:
> Michael Karcher wrote:
>>
>> Am Donnerstag, den 18.12.2008, 14:53 -0800 schrieb James Hawkins:
>>>
>>> I don't understand the problem. If you have the proper permissions,
>>> wine should be able to read the volume name and everything should ju
On Thu, Dec 18, 2008 at 2:47 PM, Michael Ost wrote:
> James Hawkins wrote:
>>
>> On Thu, Dec 18, 2008 at 12:31 PM, Michael Ost
>> wrote:
>>>
>>> wine-devel-requ...@winehq.org wrote:
>>>>
>>>> Date: Tue, 16 Dec 2008 13:52:00 +0100 F
James Hawkins wrote:
> On Thu, Dec 18, 2008 at 12:31 PM, Michael Ost wrote:
>> wine-devel-requ...@winehq.org wrote:
>>> Date: Tue, 16 Dec 2008 13:52:00 +0100 From: "Hoehle, Joerg-Cyril"
>>> Subject: winecfg volume serial
>>> number To: Message-
On Thu, Dec 18, 2008 at 12:31 PM, Michael Ost wrote:
> wine-devel-requ...@winehq.org wrote:
>> Date: Tue, 16 Dec 2008 13:52:00 +0100 From: "Hoehle, Joerg-Cyril"
>> Subject: winecfg volume serial
>> number To: Message-ID:
>> <47cc5abb01651443a88db8ec5b4
wine-devel-requ...@winehq.org wrote:
> Date: Tue, 16 Dec 2008 13:52:00 +0100 From: "Hoehle, Joerg-Cyril"
> Subject: winecfg volume serial
> number To: Message-ID:
> <47cc5abb01651443a88db8ec5b4d657b01c8f...@s4de8psaank.mitte.t-com.de>
> Content-Type: text/plain;
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 h
