That helped, along with fixing the printer setup. Apparently pmail is very sensitive to the status of the printer?

Pegasus Mail has been locking up at Locks up at "Restoring desktop layout . . ." recently. Anybody know of a way to get past it? I haven't been able to access some of my email accounts because of this :(.

At the very least, some advice on where to look to find clues on why this is happening to me??

If there's a dev on or something, here's some stack traces from the threads that are running in it (from Process Explorer in Sysinternals):

(winpm-32.exe+0x185dd2)

ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x682
ntoskrnl.exe!KeWaitForSingleObject+0x19f
ntoskrnl.exe!PsIsSystemProcess+0x68
ntoskrnl.exe!KeStackAttachProcess+0x11b9
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x88d
ntoskrnl.exe!KeWaitForSingleObject+0x19f
ntoskrnl.exe!PsGetCurrentThreadWin32ThreadAndEnterCriticalRegion+0x493f
ntoskrnl.exe!SeLockSubjectContext+0xa6
ntoskrnl.exe!RtlValidSid+0x52a
ntoskrnl.exe!FsRtlGetFileSize+0x2654
ntoskrnl.exe!KeSynchronizeExecution+0x3a43
ntdll.dll!ZwAlpcConnectPort+0xa
wow64.dll!Wow64EmulateAtlThunk+0xff86
wow64.dll!Wow64SystemServiceEx+0xd7
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x24
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64KiUserCallbackDispatcher+0x204
wow64win.dll+0x337cd
ntdll.dll!KiUserCallbackDispatcher+0x1f
wow64win.dll+0x4032a
wow64win.dll+0x200dc
wow64.dll!Wow64SystemServiceEx+0xd7
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x24
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64KiUserCallbackDispatcher+0x204
wow64win.dll+0x329ee
ntdll.dll!KiUserCallbackDispatcher+0x1f
wow64win.dll+0x3fc3a
wow64win.dll+0x1ac9e
wow64win.dll+0x3257b
wow64win.dll+0x1adda
wow64.dll!Wow64SystemServiceEx+0xd7
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x24
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64KiUserCallbackDispatcher+0x204
wow64win.dll+0x337cd
ntdll.dll!KiUserCallbackDispatcher+0x1f
wow64win.dll+0x4032a
wow64win.dll+0x200dc
wow64.dll!Wow64SystemServiceEx+0xd7
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x24
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x429
ntdll.dll!RtlResetRtlTranslations+0x1b08
ntdll.dll!RtlResetRtlTranslations+0xc63
ntdll.dll!LdrInitializeThunk+0xe

(winpm-32.exe+0x1818c2)

 ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x682
ntoskrnl.exe!KeWaitForSingleObject+0x19f
ntoskrnl.exe!PsIsSystemProcess+0x68
ntoskrnl.exe!KeStackAttachProcess+0x11b9
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x88d
ntoskrnl.exe!KeDelayExecutionThread+0x186
ntoskrnl.exe!RtlEqualUnicodeString+0x14e
ntoskrnl.exe!KeSynchronizeExecution+0x3a43
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x690
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x53e
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x429
ntdll.dll!LdrGetProcedureAddress+0x24db7
ntdll.dll!LdrInitializeThunk+0xe

(ntdll.dll!EtwDeliverDataBlock+0x44c)

ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x682
ntoskrnl.exe!KeWaitForSingleObject+0x19f
ntoskrnl.exe!PsIsSystemProcess+0x68
ntoskrnl.exe!KeStackAttachProcess+0x11b9
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x88d
ntoskrnl.exe!KeWaitForMultipleObjects+0x26b
ntoskrnl.exe!MmCreateSection+0xe23
ntoskrnl.exe!NtOpenResourceManager+0x59d
ntoskrnl.exe!KeSynchronizeExecution+0x3a43
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x690
wow64cpu.dll!TurboDispatchJumpAddressEnd+0xe3
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x429
ntdll.dll!LdrGetProcedureAddress+0x24db7
ntdll.dll!LdrInitializeThunk+0xe
 

> At the very least, some advice on where to look to find clues on why this is happening to me??

Move all of the *.CNM files out of the new mail directory and try again.  It should now open normally.  You can then put the messages back one at a time until you find the problem message.  

"Move all of the *.CNM files out of the new mail directory and try

again.  It should now open normally."

Sigh, it doesn't :(.

"Move all of the *.CNM files out of the new mail directory and try

again.  It should now open normally."

Sigh, it doesn't :(.

If it's really locking up, i.e. Never opens and opposed to opening real slow, you can try moving the desktop.* files out of the mail directory and try again.