I recently had to recreate my linux installation due to a faulty media. I had been running linux Mint, so I downloaded the Mint 21 and installed to new media. I then installed wine according to winehq using ubuntu jimmy as it said that was for linux Mint 21.x. I recreated my 64-bit prefix and ran the application installer. When the installer finished it automatically started the application and it ran fine. Exiting that, and then trying to restart the application fails. The application is Legacy9, a genealogy program.
dave@dave-Aleena:~$ cd '/home/dave/LEGACY/drive_c/Program Files (x86)/Legacy9'
dave@dave-Aleena:~/LEGACY/drive_c/Program Files (x86)/Legacy9$ WINEARCH=win64 WINEPREFIX=/home/dave/LEGACY wine Legacyx
0088:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0088:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0088:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0088:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
010c:fixme:ole:OaBuildVersion Version value not known yet. Please investigate it !
wine: Read access denied for device L"\\??\\f:\\", FS volume label and serial are not available.
wine: Read access denied for device L"\\??\\z:\\", FS volume label and serial are not available.
010c:fixme:variant:VarDateFromUdateEx unsupported flags: 4
010c:fixme:variant:VarDateFromUdateEx unsupported flags: 4
010c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
010c:fixme:richedit:IRichEditOle_fnInPlaceDeactivate stub 00EA7BA8
dave@dave-Aleena:~/LEGACY/drive_c/Program Files (x86)/Legacy9$/code]
I tried search in the forum but nothing was returned. Searching the net it says that "f" and "z" drives are owned by root so I don't have access. I really don't understand what it going on given it was working previously in prior release of Mint.
Any help would be greatly appreciated.
One way to test is to see if you can go into those directories and create and delete a file. Or if you know you don't have permissions, you can change them as root user with chmod for owner, group, other. "man chmod" will tell you more. You can also just run as root with the usual risks of running as root of course.
Often, you can ignore these errors.
By default, Z: refers to / so it makes sense you don't have write permissions.
I expect that F: refers to a DVD player. If you want to be sure, you can find out with:
I am looking at the same error. Under ./wine/dosdevices, there are a bunch of symbolic links to each removable drive. My D: links to /dev/sdb. Now I don't have access to /dev/sdb whatsoever, not even read access, which is correct from a security standpoint, otherwise any user can circumvent any access control and peer at any other users' data by low level disk access.
Reading just the volume label and serial should be legal and permitted, so I believe what you are seeing is not a feature but a bug. In my case the underlying Win32 API call I used is GetVolumeInformation. There must be some way for wine to implement this call without low level disk access.