Hello:

Following info in bug report?
On Fedora 44 with wine-11.19
ran the install program and clicked on Help and this screen showed.

No wierd characters. Looks Fine.

Did note this message in text window screen? But seem normal.
cat pegwinetxt.txt
012c:fixme:winisableProcessWindowsGhosting : stub
012c:fixme:graphicshutdownBlockReasonDestroy (00010080): stub
012c:fixme:graphicshutdownBlockReasonCreate (00010080, L"Installing": stub
012c:fixme:rstrtmgr:RmStartSession 0049F3FC, 0, 0049F400 stub!
012c:fixme:rstrtmgr:RmEndSession 3735928559 stub!
012c:fixme:graphicshutdownBlockReasonDestroy (00010080): stub
root@fedora:~# 013c:fixme:winisableProcessWindowsGhosting : stub
013c:fixme:graphicshutdownBlockReasonDestroy (0002005E): stub
013c:fixme:graphicshutdownBlockReasonCreate (0002005E, L"Installing": stub
013c:fixme:rstrtmgr:RmStartSession 0049F3FC, 0, 0049F400 stub!
013c:fixme:graphicshutdownBlockReasonDestroy (0002005E): stub
013c:fixme:graphicshutdownBlockReasonCreate (0002005E, L"Installing Pegasus Mail.": stub
013c:fixme:msg:ChangeWindowMessageFilterEx 00010096 c03a 1 00000000
013c:fixme:msg:ChangeWindowMessageFilterEx 0001009E c03a 1 00000000
013c:fixme:msg:ChangeWindowMessageFilterEx 0002009E c03a 1 00000000
013c:fixme:shellHAutoComplete stub
013c:fixme:rstrtmgr:RmRegisterResources -559038737, 59, 01855674, 0, 00000000, 0, 00000000 stub!
013c:fixme:rstrtmgr:RmGetList -559038737, 0026FE54, 0026FE58, 01855674, 0026FE50 stub!
013c:fixme:sfcfcIsFileProtected (00000000, L"C:\users\msetzerii\AppData\Local\Temp\is-6I7B8.tmp\1025.png" stub
013c:fixme:explorerframe:taskbar_list_SetProgressValue iface 0090AED8, hwnd 0002005E, ullCompleted 0, ullTotal 35b stub!
013c:fixme:explorerframe:taskbar_list_SetProgressState iface 0090AED8, hwnd 0002005E, flags 0 stub!
0144:fixme:file:NtLockFile I/O completion on lock not implemented yet
013c:fixme:rstrtmgr:RmEndSession 3735928559 stub!
013c:fixme:graphicshutdownBlockReasonDestroy (0002005E): stub

Did this under root user with no wine installed for that user.

Did it again with regular user that already had wine and Pegasus installed, and got the same good help screen?

Put a comment on bugzilla report on winehq showing that for me the process produces a clean help screen.
Fedora 44 fully upgraded with wine 11.19
Did with both a user with no wine or pegasus installed
and also with a user that had both wine and pegasus already setup.
Both gave the help screen from earlier message.
So, why it works fine with this setup, and not with other I don't know.
bug reports wine 11, but many of the messages said wine 8, and a linux distro that I am not familar with.

Perhaps a process to better isolate what is the issue.

If I had hardware might try this.
Boot from a Fedora live usb
do a dnf install wine
Then run installer and see if help screen displays correctly with Fedora repo wine? Yes/No?

Then install the winehq version of wine stable or delopment.

Do they display help screen correctly.
So, figure if it a linux distro issue, or some hardware issue.
Would be interesting to know, but with the installer help gives a quick point to check. Since TER32 and HTS32 have nothing to do with installer to the point of help?

Went to the user that didn't have wine or Pegasus Installed.

It installed the wine, and ran the installer up to point of checking help screen that was fine, then cancelled it.

The PMAIL directory had not yet been created and there was not TER32 or HTS32 files, so they have nothing to do with the help being displayed incorrectly. Must be some other problem with the distro or wine setup.
I've used Fedora from Core 1 to the latest Fedora 45. Pegasus is main program I run under wine. Irfan is the other one.

Does the wine notepad work correctly? Think wine-11.4 thru .8 had an update that message up things, but then they resolved the issue. 11.20 should be coming up soon.

Sorry Mike, but that's not correct: After launching PM's setup click the "Setup Info" button. If using Process Explorer on Windows it shows three child processes of the main w32-491.exe, one of these being wpmsi.exe which has both the above modules loaded (the setup creates subdirs in the current user's Temp dir where the required modules are unpacked to).

Ran the install program.
Have the welcome screen open.
Have wine open cmd prompt
C:>dir
Volume in drive C has no label.
Volume Serial Number is 4300-0000

Directory of C:\

09/05/2026 06:44 AM <DIR> Program Files (x86)
09/05/2026 06:35 AM <DIR> ProgramData
09/05/2026 06:35 AM <DIR> users
09/05/2026 06:44 AM <DIR> windows
09/05/2026 06:35 AM <DIR> Program Files
0 files 0 bytes
5 directories 30,782,562,304 bytes free
Click on Setup Info

dir
Volume in drive C has no label.
Volume Serial Number is 4300-0000

Directory of C:\

09/05/2026 06:44 AM <DIR> Program Files (x86)
09/05/2026 06:35 AM <DIR> ProgramData
09/05/2026 06:35 AM <DIR> users
09/05/2026 06:44 AM <DIR> windows
09/05/2026 06:35 AM <DIR> Program Files
0 files 0 bytes
5 directories 30,782,382,080 bytes free
Open Help

dir
Volume in drive C has no label.
Volume Serial Number is 4300-0000

Directory of C:\

09/05/2026 06:44 AM <DIR> Program Files (x86)
09/05/2026 06:35 AM <DIR> ProgramData
09/05/2026 06:35 AM <DIR> users
09/05/2026 06:44 AM <DIR> windows
09/05/2026 06:35 AM <DIR> Program Files
0 files 0 bytes
5 directories 30,782,341,120 bytes free
All display fine no PMAIL directory created.

Click Next - This screen prompts for the C:\PMAIL
Still NO C:\PMAIL directory

Click Next

Still no C:\PMAIL presents other options.

Click Next
Still no C:\PMAIL but screen showing ready to install.
Click finish and then it goes thru the install process and C:\PMAIL now exists.

C:>dir
Volume in drive C has no label.
Volume Serial Number is 4300-0000

Directory of C:\

09/05/2026 06:35 AM <DIR> Program Files
09/05/2026 06:44 AM <DIR> Program Files (x86)
09/05/2026 06:35 AM <DIR> ProgramData
09/05/2026 06:35 AM <DIR> users
09/05/2026 06:44 AM <DIR> windows
10/15/2026 10:51 PM <DIR> PMAIL
0 files 0 bytes
6 directories 30,713,757,696 bytes free
So nothing exists before that point.

Look at directory in linux

du . | sort -n
4 ./MAIL/ADMIN
12 ./MAIL
76 ./Programs/DEFAULTS
484 ./Programs/RESOURCE
1412 ./Programs/PNG
8532 ./Programs/DICTS
14692 ./Programs/IERenderer
66716 ./Programs
66732 .
So, that is what I see. NO PMAIL directory or TER32 or HTS32 until many steps later. Don't know what you are seeing.

Info from terminal window.

wine w32-491.exe

MESA-EGL: warning: DRI3 error: Could not get DRI3 device
MESA-EGL: warning: Ensure your X server supports DRI3 to get accelerated rendering
00e8:fixme:wineusb:add_usb_device Interface 1 has 6 alternate settings; using the first one.
00e8:fixme:wineusb:add_usb_device Interface 1 has 7 alternate settings; using the first one.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00b4:fixme:wineusb:query_id Unhandled ID query type 0x5.
012c:fixme:winisableProcessWindowsGhosting : stub
012c:fixme:graphicshutdownBlockReasonDestroy (00010080): stub
012c:fixme:graphicshutdownBlockReasonCreate (00010080, L"Installing": stub
012c:fixme:rstrtmgr:RmStartSession 0049F3FC, 0, 0049F400 stub!
012c:fixme:rstrtmgr:RmEndSession 3735928559 stub!
012c:fixme:graphicshutdownBlockReasonDestroy (00010080): stub
root@fedora:~# 013c:fixme:winisableProcessWindowsGhosting : stub
013c:fixme:graphicshutdownBlockReasonDestroy (0002005E): stub
013c:fixme:graphicshutdownBlockReasonCreate (0002005E, L"Installing": stub
013c:fixme:rstrtmgr:RmStartSession 0049F3FC, 0, 0049F400 stub!
013c:fixme:graphicshutdownBlockReasonDestroy (0002005E): stub
013c:fixme:graphicshutdownBlockReasonCreate (0002005E, L"Installing Pegasus Mail.": stub
013c:fixme:msg:ChangeWindowMessageFilterEx 00010096 c03a 1 00000000
013c:fixme:msg:ChangeWindowMessageFilterEx 0001009E c03a 1 00000000
013c:fixme:msg:ChangeWindowMessageFilterEx 0002009E c03a 1 00000000
013c:fixme:shellHAutoComplete stub
013c:fixme:rstrtmgr:RmRegisterResources -559038737, 59, 01855674, 0, 00000000, 0, 00000000 stub!
013c:fixme:rstrtmgr:RmGetList -559038737, 0026FE54, 0026FE58, 01855674, 0026FE50 stub!
013c:fixme:sfcfcIsFileProtected (00000000, L"C:\users\msetzerii\AppData\Local\Temp\is-OB9D7.tmp\1025.png" stub
013c:fixme:explorerframe:taskbar_list_SetProgressValue iface 0090AEF0, hwnd 0002005E, ullCompleted 0, ullTotal 35b stub!
013c:fixme:explorerframe:taskbar_list_SetProgressState iface 0090AEF0, hwnd 0002005E, flags 0 stub!
0144:fixme:file:NtLockFile I/O completion on lock not implemented yet
0144:fixme:gdiplus:resample_bitmap_pixel Unimplemented interpolation 7
01b0:fixme:userenv:LoadUserProfileW 00000088 0026FEB0
0188:fixme:nstc:NSTC2_fnSetControlStyle2 mask & style (0x00000004) contains unsupported style(s): 0x00000004
0188:fixme:shell:IShellBrowser_fnSendControlMsg stub, 00007FFFF0841940 (2, 1026, a003, 0, 00007FFFF023F3C
0188:fixme:shell:IShellBrowser_fnSendControlMsg stub, 00007FFFF0841940 (2, 1026, a004, 1, 00007FFFF023F3C
0188:fixme:shell:IShellBrowser_fnSendControlMsg stub, 00007FFFF0841940 (2, 1025, a003, 1, 00007FFFF023F3C
0188:fixme:shell:IShellBrowser_fnSendControlMsg stub, 00007FFFF0841940 (2, 1025, a004, 1, 00007FFFF023F3C
01ec:fixme:system:NtUserSystemParametersInfo Unknown action: 8220
01ec:fixme:wtsapi:WTSRegisterSessionNotification Stub 0001024E 0x00000000
01ec:fixme:uxtheme:BufferedPaintInit Stub ()
01ec:fixme:winisableProcessWindowsGhosting : stub
01ec:fixme:graphicshutdownBlockReasonDestroy (0001024E): stub
01ec:fixme:graphicshutdownBlockReasonCreate (0001024E, L"Installing": stub
01ec:fixme:rstrtmgr:RmStartSession 006F0B34, 0, 006F0B38 stub!
01ec:fixme:userenv:LoadUserProfileW 0000008C 019C818C
01ec:fixme:graphicshutdownBlockReasonDestroy (0001024E): stub
01ec:fixme:graphicshutdownBlockReasonCreate (0001024E, L"Installing Pegasus Mail HTML Renderer.": stub
01ec:fixme:msg:ChangeWindowMessageFilterEx 00010258 c03a 1 00000000
01ec:fixme:msg:ChangeWindowMessageFilterEx 00020258 c03a 1 00000000
01ec:fixme:shellHAutoComplete stub
01ec:fixme:rstrtmgr:RmRegisterResources -559038737, 3, 019B8A50, 0, 00000000, 0, 00000000 stub!
01ec:fixme:rstrtmgr:RmGetList -559038737, 0026FE34, 0026FE38, 019B8A50, 0026FE30 stub!
01ec:fixme:explorerframe:taskbar_list_SetProgressValue iface 00B71D70, hwnd 00020258, ullCompleted 0, ullTotal 46a stub!
01ec:fixme:sfcfcIsFileProtected (00000000, L"C:\PMAIL\Programs\unins000.exe" stub
01ec:fixme:explorerframe:taskbar_list_SetProgressState iface 00B71D70, hwnd 00020258, flags 0 stub!
01ec:fixme:userenv:UnloadUserProfile (0000008C, 80000001): stub
01ec:fixme:rstrtmgr:RmEndSession 3735928559 stub!
01ec:fixme:graphicshutdownBlockReasonDestroy (0001024E): stub
01ec:fixme:wtsapi:WTSUnRegisterSessionNotification Stub 0001024E
01ec:fixme:uxtheme:BufferedPaintUnInit Stub ()
013c:fixme:rstrtmgr:RmEndSession 3735928559 stub!
013c:fixme:graphicshutdownBlockReasonDestroy (0002005E): stub

Again. Don't know what this WINE 8 that keeps getting mentioned is.

WINE is 11.0 thru 11.19.

AI says.

Yes, Linux Devuan Daedalus (Devuan 5, which is based on Debian 12 "Bookworm" can run Wine 11.0.
So what is reason someone is trying to run Wine 8?

Like saying I want to run 4.91 on windows 3.11??
Guess I'll just drop the this since it seems a dead issue.

@msetzerii :

Could you please stop with the "random listings" fetish? It just increases the noise level and makes the thread hard to read.
Maybe you think it's professional-looking? No, it's just annoying: If somebody needs some specific piece of information, he'll ask for it.

Most of all, please do not go pollute the WineHQ bug tracker thread with your random listings too.
If the WineHQ devs need additional information, they will ask for it.

Hello:

Hello:

[root@devuan ~]# apt install wine
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
wine is already the newest version (8.0~repack-4).  <<<------------------ #####
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[root@devuan ~]#

Seems the distro is locked at wine 8? So bugzilla report is wrong, since it shows wine 11.0.

I don't see how running a 3 major version old release or wine could be worked on.

This is what I found. So I'll drop it.

The default package version available in the Devuan Daedalus repository is Wine 8.0.
Dev1 Galaxy
While WineHQ currently hosts Wine 11.0 (Stable) and Wine 11.19 (Development), this version gap comes down to how conservative Linux distributions manage software updates.
WineHQ Forums +1
Why Devuan Daedalus has Wine 8.0

Debian Bookworm Core: Devuan Daedalus is a "systemd-free" fork based directly on Debian 12 (Bookworm).
The "Stable" Philosophy: Linux distributions like Debian and Devuan prioritize absolute system stability over having the latest bleeding-edge software features. When Devuan Daedalus was frozen and released, Wine 8.0 was the current stable upstream version.
No Major Version Upgrades: Once a Debian/Devuan stable release goes live, the software versions in its main repository are locked. They only receive critical security patches and major bug fixes, not feature updates that bump the version to 9, 10, or 11.

How to get the latest Wine on Devuan
If you need the performance improvements of Wine 11.x for newer apps or games, you do not have to use the outdated version from the default repository. You can bypass it using these options:

Add the Official WineHQ Repository: You can add the official WineHQ Debian Repository to your Devuan sources to pull Wine 11.x directly from the developers. 

Of course there's no PMAIL dir while installing, but as I already wrote all files copied to the later PMAIL and its subdriectories are unpacked to temporary directories (names starting with is-... for Inno Setup). Certainly I don't know which TEMP dir is used on Wine as I'm a Windows only user.

Hello:

In Wine you have a [TEMP] directory located at [/home/user/.wine/drive_c/TEMP/] where, after all is said and done (intallation wise) you will have a file named [bearhtml.before.htm].
Here is what it says:

Welcome to Pegasus Mail!
This message has been placed in your new mail folder as part of the Pegasus Mail installation process.
To see what's new in this version of Pegasus Mail, please go to the "Help" menu and choose "What's new in this version".
Pegasus Mail has a very rich help system, accessible from the "Help" menu above. As well as the help system, a full manual for Pegasus Mail has been installed in the same directory as the program - it is called "manual.pdf" and can be viewed using Adobe Acrobat or any other program that can display PDF files.
If you need technical support or information and cannot find what you need in the help system or manual, please visit the Pegasus Mail user community.
We hope you enjoy using Pegasus Mail!
David Harris and the Pegasus Mail test team.

Thanks for your input.
Best,
S.

@Admin:
Dealing with this forum's formatting is a truly awful experience.

Has a possible fix with a winecfg setting??

Your analysis is completely accurate. The issue here is a known architectural gap between Wine 8 and the updated rendering system introduced in Pegasus Mail 4.8+.
When Pegasus Mail updated from version 4.73 to 4.8+, Sub Systems updated the underlying ter32.dll engine. In newer versions of Wine (like your Wine 11.19), the enhanced rich text and GDI font-scaling mechanisms handle this update perfectly. However, Wine 8 has a known font-rendering and richedit regression with this newer version of ter32.dll, causing text in the message body/viewer to compress entirely, look unreadable, or appear completely garbled.
WineHQ +4
If the user is stuck on a distribution locked to Wine 8 (such as Debian 12 "Daedalus" stable), they can bypass the garbled text using these strategies:
Dev1 Galaxy

1. Disable the Buggy Native Font Handling via winecfgThe garbled text is usually caused by Wine 8 failing to map the specific rich-text fonts requested by the newer ter32.dll. WineHQ Bugzilla

   Open terminal inside the user's Pegasus Wine prefix and run: winecfg Go to the Libraries tab. In the "New override for library" box, type riched20 and click Add. In the list, select riched20, click Edit, and change it to Native then Builtin. Repeat this step for riched32. (This forces Wine to rely heavily on standard Windows rich-text libraries if bundled, rather than Wine 8's flawed built-in font mapping).

2. Strip out IERenderer (Crucial for 4.8+ on Wine Pegasus Mail 4.8 introduces severe regressions on Wine 8 when trying to process HTML via IERenderer.fff. It frequently defaults to unreadable fallback bitmap fonts when it fails. WineHQ Bugzilla +3

   Tell the user to look in their Pegasus directory (usually C:\PMAIL\Programs). Run the included unins000.exe to completely uninstall IERenderer. Alternatively, navigate to drive_c/PMAIL/Programs/ and rename IERenderer.fff to IERenderer.fff.bak. This forces Pegasus to use BearHTML or older text-rendering paths, clearing up the garbled font artifacts. WineHQ +2

3. Downgrade the DLL Component (The "Frankenstein" Fix)Since the user verified that older ter32.dll versions handle text fine, they can manually place the ter32.dll from Pegasus 4.73 into the C:\PMAIL\Programs\ folder of their 4.8+ installation. WordPress.com

   Note: While this often fixes the immediate visual text corruption in the main read windows, it may cause minor menu quirks or unstable behavior during OAUTH2 credential pop-ups later on. Pegasus Mail

4. Bypass the System Lock with a Portable Wine AppImage / FlatpakIf the user's Linux distribution locks the system package manager to Wine 8, they do not have to settle for it. They can bypass the OS lock entirely without root privileges:

   Bottles (Flatpak): Have them install Bottles via Flathub. Bottles manages its own isolated runners (like sys-wine-10+ or soda) and will let them run Pegasus Mail 4.8 on a modern Wine layer completely independent of their distribution's Wine 8 lock.

If the user applies these steps, let me know:

Does disabling the IERenderer or overriding richedit clean up the font display?
Would they be open to trying a Flatpak-based Wine manager like Bottles to easily leap past Wine 8?

Is this an AI reply, Mike?

OMG. This is bad for my blood pressure...

Is there a moderator here? Can (s)he please lock this thread since there is no way one can have a constructive discussion under those circumstances, and what little useful information there was is progressively drowned in the ever-rising noise level?
Thanks, I've got the information I wanted, I filed a bug report at WineHQ, the ball is now in WineHQ's camp.