You can view the drive letter mappings used by a Wine prefix from a command-line interface (CLI) on a Linux system by opening a terminal window and entering the command ls -l ~/wineprefix/dosdevices/ where wineprefix is the relevant Wine prefix. E.g., ls -l ~/.wine-collectorz/dosdevices/, if the Wine prefix is .wine-collectorz. I can limit the output to just drive mappings with ls -l ~/.wine-collectorz/dosdevices | grep "[a-z]:" | grep -E '/dev/|/run/media', which pipes the output of the ls through two grep commands. The first looks for lines that have a drive letter, i.e., one of the lowercase letters a through z followed by a colon, e.g., c:, while the second then looks for those lines that have either "/dev/" or "/run/media" in them.

alice@Wonderland:~$ ls -l ~/.wine-collectorz/dosdevices | grep "[a-z]:" | grep -E '/dev/|/run/media'
lrwxrwxrwx 1 alice alice  8 May  4 16:29 d:: -> /dev/sdc
lrwxrwxrwx+1 alice alice  8 May  4 16:29 e:: -> /dev/sr0
lrwxrwxrwx 1 alice alice  8 May  4 16:29 f:: -> /dev/sdd
lrwxrwxrwx 1 alice alice  8 May  4 16:29 g:: -> /dev/sde
lrwxrwxrwx 1 alice alice  8 May  4 16:29 h:: -> /dev/sdf
lrwxrwxrwx 1 alice alice  9 May  4 16:29 i:: -> /dev/sdi1
lrwxrwxrwx 1 alice alice  8 May  4 16:29 j:: -> /dev/sdg
lrwxrwxrwx 1 alice alice  8 May  4 16:29 k:: -> /dev/sdh
lrwxrwxrwx 1 alice alice  9 May  4 16:29 l:: -> /dev/sdg1
lrwxrwxrwx 1 alice alice  8 May  4 16:29 m:: -> /dev/sdi
lrwxrwxrwx 1 alice alice 43 Aug 26 17:47 n: -> /run/media/alice/MS 3
lrwxrwxrwx 1 alice alice  9 May  4 16:29 n:: -> /dev/sdg2
lrwxrwxrwx 1 alice alice  8 May  4 16:29 o:: -> /dev/sdj
lrwxrwxrwx 1 alice alice 47 Sep  3 19:49 p: -> /run/media/alice/Nifler
lrwxrwxrwx 1 alice alice  9 May  4 16:29 p:: -> /dev/sde1
lrwxrwxrwx 1 alice alice  9 May  4 16:29 q:: -> /dev/sde2
lrwxrwxrwx 1 alice alice  9 May  4 16:29 r:: -> /dev/sdc1
lrwxrwxrwx 1 alice alice 43 Jun 27 11:29 s: -> /run/media/alice/MS 2
lrwxrwxrwx 1 alice alice  9 May  4 16:29 s:: -> /dev/sdc2
lrwxrwxrwx 1 alice alice  9 May  4 16:29 t:: -> /dev/sdj1
lrwxrwxrwx 1 alice alice  9 May  4 16:29 u:: -> /dev/sdh1
lrwxrwxrwx 1 alice alice  9 May  4 16:29 v:: -> /dev/sdh2
lrwxrwxrwx 1 alice alice 48 Aug 26 17:47 w: -> /run/media/alice/Willow
lrwxrwxrwx 1 alice alice  9 May  4 16:29 w:: -> /dev/sdf1
lrwxrwxrwx 1 alice alice  9 May  4 16:29 x:: -> /dev/sdd1
lrwxrwxrwx 1 alice alice 43 Jun 27 11:29 y: -> /run/media/alice/MS 1
lrwxrwxrwx 1 alice alice  9 May  4 16:29 y:: -> /dev/sdd2
alice@Wonderland:~$ 

I can use the lsblk -o name,mountpoint,label,size to see the connection between the device designations and the labels on drives.

alice@Wonderland:~$ lsblk -o name,mountpoint,label,size
NAME                        MOUNTPOINT                         LABEL        SIZE
loop0                       /snap/canonical-livepatch/406                  13.5M
loop1                                                                     201.3M
loop2                       /snap/celluloid/322                            21.9M
loop3                       /snap/cups/1238                                47.9M
loop4                       /snap/bare/5                                      4K
loop5                       /snap/chromium-ffmpeg/112                       8.3M
<text snipped>
sda                                                                          20T
├─sda1                                                                       16M
└─sda2                      /run/media/alice MS 4          20T
sdb                                                                        29.3G
└─sdb1                      /run/media/alice             29.3G
sdc                                                                        14.6T
├─sdc1                                                                      499M
├─sdc2                                                                      128M
├─sdc3                      /run/media/alice Windows     14.5T
└─sdc4                                                         Recovery    74.5G
sdd                                                                          20T
├─sdd1                                                                       16M
└─sdd2                      /run/media/alice MS Working    20T
sde                                                                        14.6T
└─sde1                      /run/media/alice Nifler      14.6T
sdf                                                                         4.5T
└─sdf1                      /run/media/alice Oak          4.5T
sdg                                                                        18.2T
├─sdg1                                                         EFI          200M
└─sdg2                      /run/media/alice MS 3        18.2T
sdh                                                                        25.5T
├─sdh1                                                         EFI          200M
└─sdh2                                                         MS 2        25.5T
sdi                                                                        25.5T
├─sdi1                                                         EFI          200M
└─sdi2                      /run/media/alice MS 1        25.5T
sdk                                                                        18.2T
├─sdk1                                                         EFI          200M
└─sdk2                      /run/media/alice YouTube     18.2T
sr0                                                                         4.1G
nvme0n1                                                                     1.8T
├─nvme0n1p1                 /boot/efi                                         1G
├─nvme0n1p2                 /boot                                             2G
└─nvme0n1p3                                                                 1.8T
  └─dm_crypt-0                                                              1.8T
    └─ubuntu--vg-ubuntu--lv /                                               1.8T
alice@Wonderland:~$

You can use the Wine Configuration Tool for a graphical user interface (GUI) view of drive mappings by using a command like WINEPREFIX=$HOME/.wine-collectorz winecfg.

alice@Wonderland:~$ WINEPREFIX=$HOME/.wine-collectorz winecfg
alice@Wonderland:~$

References:

1. How do I list Wine drive letter mappings?
   By: Rovanion
   Date: February 27, 2023
   Stack Exchange - Unix & Linux

Related

1. Creating and using a Wine prefix on an Ubuntu Linux system
   Date: July 31, 2026

[/os/unix/linux/wine] permanent link

You can check specific keys with reg query commands like the ones below, where the Wine prefix is .wine-collectorz, which show the version of Movie Collector, the location of the currently specified database, and the location where backups will be stored.

alice@Wonderland:~$ WINEPREFIX=$HOME/.wine-collectorz wine reg query "HKCU\Software\Collectorz.com\Movie\Version info" /v Version

HKEY_CURRENT_USER\Software\Collectorz.com\Movie\Version info
    Version    REG_SZ    23.3.5

alice@Wonderland:~$ WINEPREFIX=$HOME/.wine-collectorz wine reg query "HKCU\Software\Collectorz.com\Movie\Databases" /v CurrentDatabase

HKEY_CURRENT_USER\Software\Collectorz.com\Movie\Databases
    CurrentDatabase    REG_SZ    T:\Movie Collector\Movies.mvc

alice@Wonderland:~$ WINEPREFIX=$HOME/.wine-collectorz wine reg query "HKCU\Software\Collectorz.com\Movie\Folders" /v Backup

HKEY_CURRENT_USER\Software\Collectorz.com\Movie\Folders
    Backup    REG_SZ    I:\Movie Collector\Backup\

alice@Wonderland:~$ 

References:

1. Collectorz.com® Movie Collector for Windows - Getting Started
   Collectorz.com

Related:

1. Creating and using a Wine prefix on an Ubuntu Linux system
   Date: July 31, 2026
2. Windows Reg Query Command
   Date: October 1, 2016

[/os/unix/linux/wine] permanent link

The Advanced Diary journaling/diary program from CSoftLab stores its license information in the Windows registry at HKEY_CURRENT_USER\Software\CSoftLab\Advanced Diary. When you install the software, you will have a 30-day trial period and the LicenseCode and LicenseName keys will not have any values set. You can see the values using the Microsoft Windows registry editor regedit.exe.

If you need to view the license information, you can navigate to the HKEY_CURRENT_USER\Software\CSoftLab\Advanced Diary key in the registry using the registry editor or you can open a command prompt window and issue the following reg query commands.

C:\>reg query "HKCU\SOFTWARE\CSoftLab\Advanced Diary" /v LicenseName

HKEY_CURRENT_USER\SOFTWARE\CSoftLab\Advanced Diary
    LicenseName    REG_SZ    John Doe


C:\Users\Lisa>reg query "HKCU\SOFTWARE\CSoftLab\Advanced Diary" /v LicenseCode

HKEY_CURRENT_USER\SOFTWARE\CSoftLab\Advanced Diary
    LicenseCode    REG_SZ    VN37-H79K-28ZZ-XMMUMM9XX9


C:\>

You can extract the information from the registry by right-clicking on the Advanced Diary entry in the registry and choosing Export and then saving the information to a .reg registry file. That will save all of the registry information for Advanced Diary. You can then delete all but the lines that are like the ones below, if you only need the license entries in the registry.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\CSoftLab\Advanced Diary]
"LicenseName"="John Doe"
"LicenseCode"="VN37-H79K-28ZZ-XMMUMM9XX9"

You can then import the registry entries after installing Advanced Diary on another system. You can import them by opening the registry editor and choosing Registry and then Import Registry File.

Note: if you are transferring the registry keys to an installation of Advanced Diary running under Wine on a Linux system, you can run the registry editor provided by Wine by opening a terminal window and then setting the WINEPREFIX environment variable equal to whatever Wine prefix you have set, if you are using one other than the .wine one, and then running wine regedit. E.g.:

$ export WINEPREFIX="$HOME/.wine-advdiary"
$ wine regedit

If you have saved the registry values to a .reg file, e.g. file.reg, and want to import the values from that file from a command-line interface (CLI), open a command prompt window as an administrator and run reg import "C:\path\to\file.reg". Alternatively, use regedit /s "C:\path\to\file.reg" to import the file silently without a confirmation prompt. To import the registry values from a Windows system into the registry for an instance of Advanced Diary 9.0 running in a Wine prefix named .wine-advdiary on an Ubuntu Linux system, I used the commands below in a terminal window to import a .reg file named AdvancedDiary_LicenseInfo.reg.

$ export WINEPREFIX="$HOME/.wine-advdiary"$ wine regedit /s "$HOME/Documents/AdvancedDiary_LicenseInfo.reg"
$

After doing so, when I clicked on Help and chose About Advanced Diary, I saw it was registered.

Related articles:

1. Obtaining a command prompt in Windows 11
   Date: August 14, 2023
2. Windows Reg Query Command
   Date: October 1, 2026
3. Checking Microsoft Windows proxy server settings
   Date: January 7, 2015
4. Installing Advanced Diary on a Linux system with Wine
   Date: February 24, 2026
5. Access violation when installing Advanced Diary 9.0 with Wine on a Linux system
   Date: August 4, 2026
6. Advanced Diary Active Database and Backup Registry Values
   Date: July 18, 2026

[/os/unix/linux/wine/AdvDiary] permanent link

I needed to install the Advanced Diary diary/journaling program from CSoftLab on an Ubuntu Unix system. The application is developed only for Microsoft Windows, so to get it to work on an Ubuntu Linux system I used Wine, which is free and open-source software that allows one to run applications developed for the Microsoft Windows operating system (OS) on Linux systems. I started the installation from a terminal window after creating and initializing a Wine prefix for it. But when I clicked on Install, I saw the message "Invalid operation in GDI+ (Code: 2)". When I canceled the installation and closed the window associated with it, I saw an error window stating "The setup files are corrupted. Please obtain a new copy of the program." I had encountered the same "Invalid operation in GDI+ (Code: 2)" problem many months ago (the setup file wasn't actually corrupted, so I could ignore that message) when I installed a previous version of Advanced Diary, version 8.0, on another system using Wine — see Installing Advanced Diary on a Linux system with Wine — and remembered that I had used a shell script then to install additional software for Wine that would alleviate that problem. I needed Winetricks installed, so I verified I had already installed it on this system with the which command (you can install it with sudo apt install winetricks, if it is not installed). I used winetricks to install gdiplus and core fonts for Windows applications. That resolved the problem with the "Invalid operation in GDI+ (Code: 2)", but then I saw a "Access violation at address 75D947DC in module 'qcap.dll'. Read of address 5F505353" message every time I started Advanced Diary.

[ More Info ]

[/os/unix/linux/wine/AdvDiary] permanent link

A Wine prefix is a directory that acts like a separate Windows installation. Each prefix has its own registry, installed programs, libraries, and configuration, providing a way to isolate applications and configure Wine in a way that is optimal for a particular Windows application or set of applications without affecting other Windows applications that you need to run on the system. To create a new Wine prefix, take the following steps:

Create a new Wine prefix

1. Choose a location for the new prefix. For example:

   export WINEPREFIX="$HOME/.wine-myapp"

2. Initialize the prefix:

   WINEPREFIX="$HOME/.wine-myapp" wineboot

   Wine will create the directory and initialize a fresh Windows environment.

[ More Info ]

[/os/unix/linux/wine] permanent link

My wife and I have been using the Microsoft Windows desktop versions of CLZ's database programs for managing book, comic, and movie collections for many years. We've found the Collectorz database programs to be well-designed and very useful, but we've encountered some issues getting the programs to work correctly on her Ubuntu Linux system, though I would note that the software was developed for Microsoft Windows operating systems and the company doesn't indicate they are supported under Linux. One problem we encountered is that after installing the programs under Wine, when she opened one of the programs, e.g., Movie Collector, and then minimized it or switched to another application with Alt-Tab, she was unable to switch back to the Collectorz program. Alt-Tab would not work nor would the Super key plus Tab key combination. There would be a small window at the upper, left-hand corner of the screen indicating the program was running, but clicking on it would not allow her to enlarge the window to work in the application again and there didn't appear to be any way to enlarge or maximize the window.

I was able to resolve the problem with minimizing the application or switching from it without re-creating a problem opening files by checking the Emulate a virtual desktop option under the Graphics tab for winecfg instead.

[ More Info ]

[/os/unix/linux/wine/collectorz] permanent link

[ More Info ]

[/os/unix/linux/wine/collectorz] permanent link

A couple of days ago, when my wife tried to play Disney Dreamlight Valley under Steam on her Ubuntu Linux system, when she clicked on "Play" it would appear that the game was going to start, but it never did. When I checked on whether the executable program for the game, ddv.exe, was running using the ps command and piping its output through grep with ps -aux | grep -i 'ddv.exe' | grep -v grep in a Terminal window, I could see it ran briefly, but when I reissued the command a few moments later, it was no longer running. To troubleshoot the problem, I closed Steam and then killed all running instances of it with pkill command, i.e., pkill Steam, in a Terminal window. The system has a NVIDIA Quadro P2000 and the problem seems to have been an issue related to Vulkan graphics software on the system. When I upgraded the operating system and rebooted, the problem disappeared.

[ More Info ]

[/os/unix/linux/wine] permanent link

My wife had been playing Disney Dreamlight Valley under Windows 11. When I installed Ubuntu 25.10, I installed Wine, then Steam as a Snap package, and then installed Disney Dreamlight Valley under Steam. She was able to use the Cloud Save option to log into the game with all of the progress she had made under Windows. She needed to switch back to Windows for a while and didn't switch back to Ubuntu for several weeks. When I started Steam and Disney Dreamlight Valley again under Ubuntu and then tried the Cloud Save option, it did not work with the message below displayed when I was prompted to provide login credentials:

Login Error

Cannot connect to online services. Continue playing in offline mode

If I entered the wrong password, I got a response indicating that the system was able to check the credentials, which I presumed were being checked on a remote server. And I was able to successfully use the change password option, which sent a password reset code to my wife's email address. I was able to resolve the problem by uninstalling Disney Dreamlight Valley under Steam and then reinstalling it.

[ More Info ]

[/os/unix/linux/wine] permanent link

My wife has been using Filename Magic Pro for Windows for many years; she has version 1.00, which still appears to be the latest version. The software "offers robust functionality for batch renaming files within folders. It streamlines the process for organizing large collections of documents, music, or images." I transitioned her desktop PC from Microsoft Windows 11 to Ubuntu Linux 25.10 and installed Wine so that she could run Windows applications that she might want to still use on the Ubuntu system. I was able to install Filename Magic Pro and use it without any problems on the Ubuntu system. If you choose to have the program create a desktop shortcut during the installation, you will see two shortcuts on the desktop, Filename Magic Pro.desktop and Filename Magic Pro.lnk. If you right-click on Filename Magic Pro.desktop and choose Allow Launching, you can then double-click on the shortcut to start the application. You can delete the Filename Magic Pro.lnk by right-clicking on it and choosing Move to Trash.

When you start the program, if it is unregistered, you will see a countdown timer that counts down from 15.

You can wait to the countdown gets to zero or just close the countdown window to proceed, which will then lead to the display of the window below.

There is a "click here to purchase" link, but that no longer works; if you click on it, you will see a HTTP 404 error indicating the page no longer exists. But if you previously purchased a license as we had, you can transfer it from an old system to a new system or, in our case, from Windows to Linux by exporting the HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\L5 Software Group registry keys, which you can do with the Windows registry editor, RegEdit, or you can download or copy this L5SoftwareGroup.reg file and edit it with a text editor, such as Windows Notepad and replace the AppRegKey Xs with your license key (be sure to save it with just the .reg extension and not a .txt file extension tacked on). You can add the registry keys to the registry used by Wine by opening a Terminal window and running the command wine regedit filename.reg where filename is the name of the .reg file.

jim@Wonderland:~$ wine regedit ~/Downloads/L5SoftwareGroup.reg 
jim@Wonderland:~$ 

When you then open the program, you won't see the countdown timer and can just click on OK. You can press Alt-Tab afterwards to get to the main Filename Magic Pro window.

[/os/unix/linux/wine] permanent link