From: Dmitry Timoshkov dmitry@baikal.ru
It looks like it's impossible to create an empty section, and without "dummy=0" entry a being created [fonts] section contains only "=" which may probably confuse some people/apps.
Wine-Bug: http://bugs.winehq.org/show_bug.cgi?id=33492 Signed-off-by: Dmitry Timoshkov dmitry@baikal.ru --- loader/wine.inf.in | 1 + 1 file changed, 1 insertion(+)
diff --git a/loader/wine.inf.in b/loader/wine.inf.in index 00c4b114644..7dc657cc9e0 100644 --- a/loader/wine.inf.in +++ b/loader/wine.inf.in @@ -879,6 +879,7 @@ system.ini, drivers32,,"; vidc.IV31=ir32_32.dll" system.ini, drivers32,,"; vidc.IV32=ir32_32.dll"
win.ini, mail,,"mapi=1" +win.ini, fonts,,"dummy=0"
[BITSService] AddReg=BITSServiceKeys
Do we know that we actually need to touch win.ini, or is the registry redirection sufficient?
On Mon Oct 20 17:01:11 2025 +0000, Elizabeth Figura wrote:
Do we know that we actually need to touch win.ini, or is the registry redirection sufficient?
The affected application is 16-bit, so it's unlikely that the registry mapping would help. On the other hand I've checked win.ini contents in Windows 11 and it has an explicit comment there "; for 16-bit app support" with empty [fonts],[extensions],[msi extensions],[files] and [mail]/MAPI=1 sections. Note, that this is on 64-bit Windows 11 where 16-bit support was completely removed.
The affected application is 16-bit, so it's unlikely that the registry mapping would help.
Our 16-bit profile functions forward to the 32-bit ones.
On the other hand I've checked win.ini contents in Windows 11 and it has an explicit comment there "; for 16-bit app support" with empty [fonts],[extensions],[msi extensions],[files] and [mail]/MAPI=1 sections. Note, that this is on 64-bit Windows 11 where 16-bit support was completely removed.
Okay, if native has it that's probably a good enough reason.
-
Dmitry Timoshkov -
Dmitry Timoshkov (＠dmitry)
-
Elizabeth Figura (＠zfigura)