Registry location for Advanced Diary registration information
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:
-
Obtaining a command prompt in Windows 11
Date: August 14, 2023
-
Windows Reg Query Command
Date: October 1, 2026
-
Checking Microsoft Windows proxy server
settings
Date: January 7, 2015
-
Installing Advanced Diary on a Linux system with Wine
Date: February 24, 2026
-
Access violation when installing Advanced Diary 9.0 with Wine on a Linux system
Date: August 4, 2026
-
Advanced Diary Active Database and Backup Registry Values
Date: July 18, 2026
[/os/unix/linux/wine/AdvDiary]
permanent link
SSH ServerAliveInterval
If you want to prevent a
Secure Shell (SSH)
connection being dropped when it has been inactive for several minutes, you can
specify a keepalive value.
To specify a keepalive value directly from the command line, use
the -o flag followed by the
ServerAliveIntervaloption
Command Line Syntax
Run the following command to send a keepalive packet every 60 seconds:
ssh -o ServerAliveInterval=60 user@hostname
Advanced Keepalive Control
For more robust protection against drops, combine the interval with ServerAliveCountMax. This defines how many consecutive keepalive messages can go unanswered before the client disconnects.
ssh -o ServerAliveInterval=60 -o ServerAliveCountMax=3 user@hostname
ServerAliveInterval=60: Sends a packet every 60 seconds of inactivity.
ServerAliveCountMax=3: Drops the dead connection if the server fails to respond 3 times in a row.
Making It Permanent (Optional)
If you get tired of typing this out every time, you can save it to your local configuration:
[/network/ssh]
permanent link
Access violation when installing Advanced Diary 9.0 with Wine on a Linux system
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
Making an optical drive accessible to a guest OS running in VirtualBox
I needed to make an
optical disc drive accessible to a Windows virtual
machine (VM) running in VirtualBox
on an Ubuntu
Linux system. The drive was attached to the host operating system
(OS) via a USB
connection. One way to make a USB optical drive connected to a Linux
host available to a Windows VM is to pass through the host optical
drive. With the VM running, I could select Devices and then
the optical drive connected to the host operating system, "Host Drive
PIONEER BD-RW BDR-XS07U (sr0)". Since I had seen a recommendation to
use a USB passthrough method instead, though, as while passing through
the host optical drive works well for ordinary CD/DVD access, unusual
discs or software that communicates directly with the hardware are less
likely to be problematic if one uses the USB passthrough method, instead,
I chose the USB passthrough option. To do so, I verified that the logged
in user account was in the vboxusers
group by issuing the command grep vboxusers /etc/group in
a terminal
window. If it isn't, you can add the account to that group using
sudo usermod -aG vboxusers $USER. I also verified that
the USB 3.0 Controller option was enabled by selecting the Windows 10
VM in VirtualBox and clicking on Settings and then selecting
USB. I then made the Pioneer Blu-ray drive accessible inside
the Windows VM by clicking on Devices at the top of the running
Windows VM window and then selecting Pioneer Corporation Pioneer
Blu-ray Drive [0100]. I then was able to see the blu-ray drive in
the Windows File
Explorer.
[ More Info ]
[/os/virtualbox]
permanent link