[Bug 25024] New: Floppy diskette label and serial number not reported by WINE
http://bugs.winehq.org/show_bug.cgi?id=25024 Summary: Floppy diskette label and serial number not reported by WINE Product: Wine Version: 1.3.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: cparke(a)parkerfamily.name For floppy diskettes, GetVolumeInformation() returns blank for the diskette label and 0000-0000 for the serial number. For key floppy diskettes needed to allow an installer to run, this causes key validation to fail! WINE should either read the volume label and serial number correctly from the boot record and FAT file system on the diskette, or should allow us to hardcode the values needed in WINECFG (currently this is allowed for hard disks but not floppies!) Still broken in 1.3.6 despite fix attempted in Bug 24871. -- 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=25024 --- Comment #1 from Alexandre Julliard <julliard(a)winehq.org> 2010-11-04 09:54:43 CDT --- Please attach a +volume trace. -- 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=25024 Dmitry Timoshkov <dmitry(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Floppy diskette label and |Floppy diskette label and |serial number not reported |serial number not reported |by WINE | --- Comment #2 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2010-11-04 09:57:27 CDT --- It would probably be better to reopen bug 24871 and mark this one as a duplicate. -- 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=25024 --- Comment #3 from Chris Parker <cparke(a)parkerfamily.name> 2010-11-04 10:06:54 CDT --- I wanted to reopen the previous bug, but couldn't figure out how! With WINEDEBUG=+volume and then running CMD.EXE and using the VOL command, as well as running GetVolumeInformation.EXE, the only debug output I get is: fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:msvcrt:_controlfp_s ((nil) 65536 196608) semi-stub I don't think either of those have anything to do with this bug. The bug cannot be found using existing trace output. -- 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=25024 --- Comment #4 from Alexandre Julliard <julliard(a)winehq.org> 2010-11-04 10:11:55 CDT --- If you don't get any traces from +volume something is wrong with your setup. -- 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=25024 --- Comment #5 from Chris Parker <cparke(a)parkerfamily.name> 2010-11-04 10:30:33 CDT --- Yes, it does look like I was setting the trace flag incorrectly. I am now getting one trace flag on this system call, but the error code seems to fluctuate among several values: trace:volume:GetVolumeInformationW cannot open device L"\\??\\B:\\": err 203 trace:volume:GetVolumeInformationW cannot open device L"\\??\\B:\\": err 0 trace:volume:GetVolumeInformationW cannot open device L"\\??\\B:\\": err 18 trace:volume:GetVolumeInformationW cannot open device L"\\??\\B:\\": err 2 All I did was do a variety of calls, VOL B: command, DIR B: command, run GetVolumeInformation.EXE B:\, with the current drive set or not set to B: -- 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=25024 --- Comment #6 from Alexandre Julliard <julliard(a)winehq.org> 2010-11-04 10:42:13 CDT --- (In reply to comment #5)
Yes, it does look like I was setting the trace flag incorrectly. I am now getting one trace flag on this system call, but the error code seems to fluctuate among several values:
trace:volume:GetVolumeInformationW cannot open device L"\\??\\B:\\": err 203 trace:volume:GetVolumeInformationW cannot open device L"\\??\\B:\\": err 0 trace:volume:GetVolumeInformationW cannot open device L"\\??\\B:\\": err 18 trace:volume:GetVolumeInformationW cannot open device L"\\??\\B:\\": err 2
All I did was do a variety of calls, VOL B: command, DIR B: command, run GetVolumeInformation.EXE B:\, with the current drive set or not set to B:
The trace is slightly broken, just ignore the error value. Anyway, the problem is that you cannot open the device. Check the permissions. -- 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=25024 --- Comment #7 from Chris Parker <cparke(a)parkerfamily.name> 2010-11-04 10:46:28 CDT --- The device is open. I can see the directory list with the DIR command, I can type out a text file with the TYPE command. However, GetVolumeInformationW still reports this trace error. The device can't be opened by GetVolumeInformationW because of a bug in GetVolumeInformationW, no other reason. -- 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=25024 --- Comment #8 from Alexandre Julliard <julliard(a)winehq.org> 2010-11-04 10:50:52 CDT --- (In reply to comment #7)
The device is open. I can see the directory list with the DIR command, I can type out a text file with the TYPE command. However, GetVolumeInformationW still reports this trace error. The device can't be opened by GetVolumeInformationW because of a bug in GetVolumeInformationW, no other reason.
No, the device and the file systems are two different things. You need access to the raw device (/dev/fd0 or so) to read label and serial. -- 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=25024 --- Comment #9 from Chris Parker <cparke(a)parkerfamily.name> 2010-11-04 10:54:37 CDT --- Maybe this is an Ubuntu bug then. I can't mount the floppy drive using the mount command since 10.04.1 because they broke something. Instead, I mount using udisks directly. I'll try 1.3.6 on another Linux distro without that bug and see if the problem still exists in 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=25024 Dmitry Timoshkov <dmitry(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE --- Comment #10 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2010-11-04 11:19:51 CDT --- Marking this bug as a duplicate, feel free to reopen that bug, or add a comment with a request to reopen. *** This bug has been marked as a duplicate of bug 24871 *** -- 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=25024 Dmitry Timoshkov <dmitry(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #11 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2010-11-04 11:20:05 CDT --- Closing duplicate. -- 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=25024 --- Comment #12 from Austin English <austinenglish(a)gmail.com> 2010-11-04 12:56:48 CDT --- (In reply to comment #9)
Maybe this is an Ubuntu bug then. I can't mount the floppy drive using the mount command since 10.04.1 because they broke something. Instead, I mount using udisks directly. I'll try 1.3.6 on another Linux distro without that bug and see if the problem still exists in wine.
Try adding yourself to the 'floppy' group, then log out/in. -- 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=25024 --- Comment #13 from Chris Parker <cparke(a)parkerfamily.name> 2010-11-16 09:24:59 CST ---
No, the device and the file systems are two different things. You need access to the raw device (/dev/fd0 or so) to read label and serial.
Look - I have to ask you, is the floppy drive letter supposed to be assigned to the /mnt/floppy path or to the /dev/fd0 path? Because it only seems to work for me against /media/floppy (i.e. the file systems, and it isn't working even on openSUSE or an older Ubuntu before they broke mount for floppy. Assuming I am mounting the floppy letter correctly, how does WINE know the correct raw device path (does it look up the Linux mount?)? The only thing a little odd that I am doing is the assignment of the machine's single floppy to drive B:. Of course, I could assign it to any letter (even F: if I wanted). If wine is hardcoded assuming A: is fd0 and B: is fd1, that might explain it. I will try it again soon using A:, but in any case, I don't think this is a permissions issue because I can use DD to read the boot sector on /dev/fd0 just fine. -- 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=25024 --- Comment #14 from Juan Lang <juan_lang(a)yahoo.com> 2010-11-16 10:58:46 CST --- (In reply to comment #13)
Look - I have to ask you, is the floppy drive letter supposed to be assigned to the /mnt/floppy path or to the /dev/fd0 path? Because it only seems to work for me against /media/floppy (i.e. the file systems, and it isn't working even on openSUSE or an older Ubuntu before they broke mount for floppy. Assuming I am mounting the floppy letter correctly, how does WINE know the correct raw device path (does it look up the Linux mount?)?
This isn't the proper forum for support: ask on wine-users instead. (And have a look at ~/.wine/dosdevices, that'll tell you something.) -- 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.
participants (1)
-
wine-bugs＠winehq.org