First of all, a little history here: I am 83 years old, and was an IT Pro at the University of Idaho for over 30 years and am now retired. I am fairly familiar with most common computer software, and still have no trouble dealing with computer hardware. I and my family have been using Pegasus for many years, probably at least 30.

Recently, I have been attempting to migrate our home computers from Windows to a Unix clone, FreeBSD. So far that attempt has been successful....until yesterday.

I have both Windows 10 and FreeBSD 14.2 in this computer on separate HDDs, and boot into the OPSYS of choice by rebooting the computer, and choosing the OPSYS at that time.

I have been using Pegasus successfully under WINE in FreeBSD. I was using the FreeBSD system for the past three days or so, and rebooted into Windows this morning. Pegasus when running within FreeBSD uses the same mailbox as when I use Pegasus under Windows.

Now, when I try to run Pegasus, after booting into Windows, I get the "locked' message, and when I hit "Continue" the Pegasus opening screen shows for several seconds, then suddenly closes with no messages and no Pegasus.

I have looked at my mail in C:/PMAIL/MAIL/<my user>, and everything is still there, yet can no longer access it.

I have copied the PMAIL.INI.OLD to PMAIL.INI and that does nothing.

How can I fix this issue?

Ken Gordon

Which version of wine are you using and what CPU.

I've got a machine with Pentium CPU and it works fine up to wine-devel 10.8, but with 10.9 thru 10.12 it will not even run notepad without dumping. downgrading to 10.8 works fine.

With other machines, there was and issue with wine-devel 10.11, but that error was found and correctec in 10.12.

So, not familure with FreeBSD, but what specific version of wine are you running, and what cpu.

The "locked" message indicates an abend when Pegasus Mail last closed. You likely know that Pegasus Mail is designed to prevent multiple instances from accessing the same mailbox simultaneously. It does this by creating a lock file on first access. This lock file is deleted on shutdown. An abnormal shutdown can leave the file in place resulting in the "locked" message on next startup. Clicking the "Continue" button overrides the lock but you only what to do that if you are certain no other instance of Pegasus Mail is using the mailbox.

As for the startup issue under Windows, the behavior you describe is what happens when Pegasus Mail can't find the mailbox, which is strange because the "locked" message indicates that it did. If it weren't for that, I would be thinking that FreeBSD/Wine left Pegasus Mail with a path to the mailbox directory that is invalid when run under Windows. @msetzerii runs Pegasus Mail under Wine so I hope he'll come along with useful advice.

I got to thinking about this and your replies last night. First of all, as far as WINE is concerned, I suspect the version I am using is not the problem, but I will take a close look at that as soon as I can to determine which version I am using.

What came to my mind last night is that although my FreeBSD install is not running when I am using Windows, its HDD is still connected and running. My install of Pegasus on FreeBSD/WINE is not working now either. When I try to "launch" Pegasus, the system tells me that it cannot find it, despite the system also telling me that the installation is complete.

I am suspecting that the reason Pegasus on Windows is having "difficulty" is that the still-running HDD with my FreeBSD install on it has some link or working part of Pegasus which is interfering with Pegasus on Windows.

What I am going to do today is to physically disconnect the FreeBSD HDD and try to run Peggy from Windows again to see if there is any difference in the result.

I will report back here.

Thank you for the help.

Ken Gordon

Something to consider is to temporarily put Pegasus Mail on an external USB device until you settle on an OS. Adding the -ROAM command line option to its start command (shortcut) will tell Pegasus Mail to ignore any paths in its configuration files and instead use the path from which it was started. Assigning the same drive letter to the USB device in both OSes would be a plus but I don't know the feasibility of that in FreeBSD with Wine.

Mike, is this a viable option in your eyes?

Thank you. I'll try that next.

Well, after I disconnected the FreeBSD HDD, checked the BIOS, then rebooted, I still have the problem.

And despite my going to the correct C:/PMAIL/MAIL/<my user>, and finding and deleting the lock file, the same thing happens: i.e., when I try to start Peggy as I normally do, the LOCK warning appears, I click on CONTINUE, and see "Preparing Folder Management Layer" at the bottom of the window, and it then fails.

So, Peggy is somehow misconfigured. I repeat, ALL my files are there: I simply can no longer access them.

When I fire up another instance of Peggy, under another user (my wife), then change the mailbox to MY mailbox, I get the same experience.

This tells me that my problem is somehow within MY mailbox of Peggy.

I am still investigating.

Ken Gordon W7EKB

Just to note a copy of things.
wine --version should give version of wine.
$ wine --version
wine-10.12

Is the version I get under my Fedora 42.

With wine it creates a directory .wine and drive_c
/home/msetzerii/.wine/drive_c# ls -l
total 24
drwxr-xr-x. 4 msetzerii msetzerii 4096 May 7 07:09 PMAIL
drwxr-xr-x. 3 msetzerii msetzerii 4096 Dec 5 2023 ProgramData
drwxr-xr-x. 7 msetzerii msetzerii 4096 Nov 8 2024 'Program Files'
drwxr-xr-x. 6 msetzerii msetzerii 4096 Dec 5 2023 'Program Files (x86)'
drwxr-xr-x. 4 msetzerii msetzerii 4096 Dec 5 2023 users
drwxr-xr-x. 22 msetzerii msetzerii 4096 Jun 15 00:16 windows

Creates s separate wine environment for each user.

Don't know how FreeBSD does thins.

Well, as I mentioned earlier, Peggy in FreeBSD is no longer working at all, and furthermore, I have completely disconnected the HDD which contains FreeBSD, so at this point, nothing on my FreeBSD install should be even in the picture.

At this point, I am convinced that there is some corrupted file, or an unnecessary file, within my C:/PMAIL/MAIL/<my user> directory which is causing the problem.

All other users of Peggy are still completely without issues, AND I can run Peggy from either of two other computers in our home with my same user without any problem.

I an only having issues with my user on this computer.

Ken Gordon W7EKB

How are you switching to your mailbox. Once upon a time that could be done by switching users from withing Pegasus Mail but that capability was remove a number of versions ago. Besides, one instance of Pegasus Mail should not know anything about the mailboxes (Pegasus Mail users) in another instance.

The lock file is MAILBOXP.LCK. If that is the file you deleted then I suspect Pegasus Mail now thinks your mailbox directory has change and there is a MAILBOXP.LCK file in whatever directory it thinks is your mailbox directory.

In the directory C:/PMAIL/Programs is a file named PMAIL.CFG. Copy that file to a temporary location the rename it to PMAIL_CFG.TXT. Now open it with a text editor and look at the path it contains. It should be C:\PMAIL\Mail~8 or C:\PMAIL\Mail~N. NOTE: PMAIL.CFG is not a plain text file. Any discrepancy in the path CAN NOT be corrected by modifying the file. Post about any discrepancy for additional advice.

Pegasus Mail is dependent on paths. Two HDDs makes me think two different drive letters although that may not be the case since they each contain a different OS. If each OS boots as a different drive letter then Pegasus Mail can not deal with that other than running as a portable installation (the -ROAM switch as I previously mentioned).

My problem with Peggy on FreeBSD is a completely separate problem, and has nothing to do with my problem with Peggy on my Windoze box. I'll address the FreeBSD issue after I have fixed this one.

Thanks.

Ken Gordon W7EKB

My C:\PMAIL\Programs\PMAIL.CFG file, readable by MS Notepad directly, is as follows:

C:\PMAIL\MAIL~N

That looks correct to me.

Yes, both HDDs use two different drive letters, but at this point, the second HDD is completely disconnected from the system and, AFAI can see, is no longer of any concern in this case. Furthermore, it cannot even be "seen" by Windoze. The BIOS sees it just fine when I have it connected, but Windoze can't.

Also, checking the registry, I see that (at least in one case) the -roam switch is incorporated in the command, followed by -A.

I have not yet figured out how to get directly to the icon which I ordinarily use to fire up Peggy so I can edit it to include the -roam switch, though.

Ken Gordon W7EKB

I forgot to mention: although I delete the LOCK file, nonetheless, every time I attempt to fire up Peggy, it is almost instantly "re-made" and I find it there then next time I look for it.

Ken Gordon W7EKB

"How are you switching to your mailbox. Once upon a time that could be done by switching users from withing Pegasus Mail but that capability was removed a number of versions ago. Besides, one instance of Pegasus Mail should not know anything about the mailboxes (Pegasus Mail users) in another instance."

I log into my wife's user. go into Peggy's TOOLS/OPTIONS/Mailbox.location then type in MY mailbox location overwriting where it shows <DEFAULT>, DO NOT check the box which says, <Move mailbox contents to new location>, then click <Change now> shut down Peggy and try to log in again. I then get the same error message as if I am using my own account. So, to fix it, I have to go to C:/PMAIL/MAIL/<her.user> and manually edit the mailbox location back to hers. And that works just fine.

You should not use notepad on the PMAIL.CFG File. It is not a regular text. The correct tool to use is the program

347648 Nov 18 2015 PCONFIG32.EXE
Hexedit view of file shows that it is a string followed by nulls.
Mine is Single user setup, so doesn't that the ~n option

00000000   43 3A 5C 50  4D 41 49 4C  5C 4D 41 49  4C 00 00 00  00 00 00 00  00 00 00 00  C:\PMAIL\MAIL...........
00000018   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
00000030   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 43 3A  5C 50 4D 41  ..................C:\PMA
00000048   49 4C 5C 4D  41 49 4C 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  IL\MAIL.................
00000060   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
00000078   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
00000090   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
000000A8   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
000000C0   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
000000D8   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
000000F0   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
00000108   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
00000120   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
00000138   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
00000150   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
00000168   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
00000180   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
00000198   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................
000001B0   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ........................

File is longer than the part here.
Looking at file with a regular text editor would not work, but the program should correct it.

Each time you do this you are switching the location of her Home mailbox directory to yours while still logged into Pegasus Mail as her (using her configuration file). Is this the way you have always done it?

In C:\PMAIL\Mail there is a file named PMAIL.USR. This is the file that keeps the record of Pegasus Mail users. Open it with a text editor and let us know what it contains.

For context regarding "Home mailbox directory":
Pegasus Mail can use different directories for "Home" and "New" mailbox locations.
"Home" contains mail folders , distribution lists, address books and other Pegasus Mail-related files except unread new mail.
"New" contains unread new mail and PMAIL.INI.

What does this mean? Can you not find it? How are you starting Pegasus Mail?
FWIW, all indications so far indicate that you don't need the -roam switch although it is harmless if there.

Need to make sure your PMAIL.CFG file in C:\PMAIL\Programs diretory is not corrumpted.
It is not a regular test file.

It you use type PMAIL.CFG it will only display the first information up to the NULL.

Microsoft Windows 10.0.19043

C:\PMAIL\Programs>type PMAIL.CFG
C:\PMAIL\MAIL
C:\PMAIL\Programs>exit

Under linux/unix using the cat command will display the contents of file with exception of the NULL characters.

 ~/.wine/drive_c/PMAIL/Programs$ cat PMAIL.CFG
C:\PMAIL\MAILC:\PMAIL\MAIL
$

In my case with single user mode, it is just the C:\PMAIL\MAIL directory. Other setups may have /~N of /~8

Best to run PCONFIG32.EXE and make sure the enter C:\PMAIL\MAIL~N as that seems to be what your setup is using. Multi-user.

As for selecting different email directories, it is generally
WINPM-32.EXE -I user

Wither default user of Admin or other names.
Listed in C:\PMAIL\MAIL\PMAIL.USR

Showing contents of PMAIL.CFG converting NULLs to X
Not sure why if shows linefeed after pasting?

tr '\0' 'X' <PMAIL.CFG
C:\PMAIL\MAILXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
C:PMAIL\MAILXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

PMAIL.CFG is generally 512 or 1024 bytes.

Generally, run PCONFIG32.EXE
Enter on first windows with C:\PMAIL\Programs
On second should be C:\PMAIL\MAIL~N and select save and exit to correct file.

Be careful here. This forum does not display a backslash when it is followed by a tilde so C:\PMAIL\MAIL~N does not display the backslash before the tilde. IOW, it should read C:\PMAIL\MAIL\ ~N but without the space between the backslash and the tilde.

Ken, have you ever used two monitors with the Pegasus Mail main window being on the second monitor, but that second monitor is not available now? If so, Pegasus Mail could be opening offscreen. To check this, open Task Manager, select the details tab, then look for any "winpm-32.exe" entries. It would be best to do this when you think all instances of Pegasus Mail are closed.

Another thought...

The Pegasus Mail folder list is maintained in a file named HIERARCH.PM. Corruption of this file could be causing the problem and would logically be associated with the "Preparing Folder Management Layer" phase of startup. If you have a backup copy of HIERARCH.PM from before the problem started then rename HIERARCH.PM to HIERARCH.SAV and then restore the backup copy. If that doesn't work, or if no backup is available, there are two options to consider.

One:

• Backup HIERARCH.PM then open it with a text editor. Delete each entry that looks like it contains garbage. I am not an advocate of this approach but there is not much to lose at this point so what the heck. You have a backup, right?Entry examples are below. Italics represent values that will be different for you.
• • You should see a mailbox entry that looks something like this:
• • • 2,1,"1EDF4308:My mailbox","",""
• • A typical folder entry will look like this:
• • • 0,0,"064F8D5C:7483:FOL02A64","2AAD3336:My mailbox","folder-name"
• • A typical tray entry will look like this:
• • • 1,3,"26E96249:@tray-name","033F1989:My mailbox","@tray-name"

Two:

• Rename HIERARCH.PM to HIERARCH.SAV and then try starting Pegasus Mail. A new HIERARCH.PM file will be created by polling each of the folder files. IMPORTANT NOTE: Doing this will result in the loss of any tray structure that existed.

Option Two will reveal whether or not a corrupted HIERARCH.PM file was the cause however I did not list it as #1 because if you used trays, rebuilding a tray structure can be extremely difficult if it was extensive.

Man, it is really hard to create a sequential tiered or indented instruction list in this forum software.