Community Discussions and Support
Upgrading to PMAIL 4.81 beta problems

Hi there,
I try updating my 4.80 PMAIL to 4.81 beta. My current instalation is in D:\PMAIL directory. After updating, every time I start program there are windows opening indicating "Insufficient disk space!" and "Insufficient TEMP space". After clicking OK on both, program launches normaly. There's plenty of space both on D: and C: drives. TMP and TEMP environment variables are in C:\Users\Username\AppData\Local\Temp. The same error messages are popping up no matter if it's update or new install in different directory on D drive. Interestingly, there are no such messages when installing on C: drive. Another issue is that after update it doesn't detect my old email folders and connection configuration files in PMAIL\MAIL folder. I ran the pconfig32.exe file and it says Configuration directory D:\pmail\programs and
Home mailbox root directory D:\PMAIL\MAIL~N. After I change the latter to just D:\PMAIL\MAIL it detects old mail folders and can connect to my previous GMAIL addresses. What is wrong here? I tried searching for answers here to no avail. Help is very appreciated.


Hi there, I try updating my 4.80 PMAIL to 4.81 beta. My current instalation is in D:\PMAIL directory. After updating, every time I start program there are windows opening indicating "Insufficient disk space!" and "Insufficient TEMP space". After clicking OK on both, program launches normaly. There's plenty of space both on D: and C: drives. TMP and TEMP environment variables are in C:\Users\Username\AppData\Local\Temp. The same error messages are popping up no matter if it's update or new install in different directory on D drive. Interestingly, there are no such messages when installing on C: drive. Another issue is that after update it doesn't detect my old email folders and connection configuration files in PMAIL\MAIL folder. I ran the pconfig32.exe file and it says Configuration directory D:\pmail\programs and Home mailbox root directory D:\PMAIL\MAIL~N. After I change the latter to just D:\PMAIL\MAIL it detects old mail folders and can connect to my previous GMAIL addresses. What is wrong here? I tried searching for answers here to no avail. Help is very appreciated.

Do you have a backup of D:\PMAIL that you could restore? From what you have said, it seems like the 4.81 installer did not do an upgrade but instead installed as multi-user over top of a 4.80 single-user installation. If you can restore, we can then analyze the 4.80 installation and offer advice, but before restoring consider whether any new mail has been retrieved by the 4.81 version. If it has, you may want to capture those messages. Let us know if you need help with that.


Do you have a backup of D:\PMAIL that you could restore? From what you have said, it seems like the 4.81 installer did not do an upgrade but instead installed as multi-user over top of a 4.80 single-user installation. If you can restore, we can then analyze the 4.80 installation and offer advice, but before restoring consider whether any new mail has been retrieved by the 4.81 version. If it has, you may want to capture those messages. Let us know if you need help with that.

Thank you for reply, Brian. Yes. I do have a copy of 4.80 installation, and it seems no new messages were retrieved by 4.81


Thank you for reply, Brian. Yes. I do have a copy of 4.80 installation, and it seems no new messages were retrieved by 4.81

Don't know if it was a typo
PCONFIG32.EXE should show Mail Directory as
D:\PMAIL\MAIL~N not D:\PMAIL\MAIL~N


So, would double check that first.


Don't know if it was a typo PCONFIG32.EXE should show Mail Directory as D:\PMAIL\MAIL\~N not D:\PMAIL\MAIL~N So, would double check that first.

mikes@guam.net

Thank you for reply, Brian. Yes. I do have a copy of 4.80 installation, and it seems no new messages were retrieved by 4.81


Awesome. Let's see what the 4.80 installation looks like. To do this I suggest the following:


  • Rename the current D:\PMAIL to D:\PMAIL_481_BAD. This will maintain it for now.
  • Restore the copy of 4.80 to its original location of D:\PMAIL.
  • You will be running it, but before you do, consider adding the -O (Oh, not zero) option to the command line. This will start Pegasus Mail in offline mode which will prevent email checks if you want to that while sorting out the upgrade issue.
  • Start Pegasus Mail (with the revised command line if you chose to do that).
  • Go to Help > About Pegasus Mail and press the Info button.
  • Copy the entire content of the resulting display and paste it into a reply. Rest assured that there is nothing personal in there. It just records version information, path information, and some configuration settings.

[quote="pid:57633, uid:50806"]Thank you for reply, Brian. Yes. I do have a copy of 4.80 installation, and it seems no new messages were retrieved by 4.81[/quote] Awesome. Let's see what the 4.80 installation looks like. To do this I suggest the following: - Rename the current D:\PMAIL to D:\PMAIL_481_BAD. This will maintain it for now. - Restore the copy of 4.80 to its original location of D:\PMAIL. - You will be running it, but before you do, consider adding the -O (Oh, not zero) option to the command line. This will start Pegasus Mail in offline mode which will prevent email checks if you want to that while sorting out the upgrade issue. - Start Pegasus Mail (with the revised command line if you chose to do that). - Go to Help > About Pegasus Mail and press the Info button. - Copy the entire content of the resulting display and paste it into a reply. Rest assured that there is nothing personal in there. It just records version information, path information, and some configuration settings.

Here it is.
Pegasus Mail for Microsoft Windows
Copyright (C) 1992-2022, David Harris, all rights reserved
Electronic mail to support@pmail.gen.nz.


WinPMail version: Version 4.80.1028, Jan 16 2022, build ID 1028
Language resources: Standard UK English resources (EN,0,LL)
Extension Manager version: 1.14
Operating mode: Standalone
User name and ID: Admin, 0
Windows version: 6.2
Windows flag word: 0
WINPMAIL.EXE directory: D:\PMAIL\Programs
Home mailbox location: D:\PMAIL\MAIL
New mailbox location: D:\PMAIL\MAIL
TMP environment variable: C:\Users\artme\AppData\Local\Temp
TEMP environment variable: C:\Users\artme\AppData\Local\Temp
LAN-based SMTP support: N, N, N
NetWare MHS support: N, N, N
Built-in TCP/IP support: Enabled


  • WINSOCK version: WinSock 2.0
  • WINSOCK path: WSOCK32.DLLCommandline: -A -I AdminActive -Z options: 32768PMR variable: (None)PML variable: (None)

Here it is. Pegasus Mail for Microsoft Windows Copyright (C) 1992-2022, David Harris, all rights reserved Electronic mail to support@pmail.gen.nz. WinPMail version: Version 4.80.1028, Jan 16 2022, build ID 1028 Language resources: Standard UK English resources (EN,0,LL) Extension Manager version: 1.14 Operating mode: Standalone User name and ID: Admin, 0 Windows version: 6.2 Windows flag word: 0 WINPMAIL.EXE directory: D:\PMAIL\Programs Home mailbox location: D:\PMAIL\MAIL New mailbox location: D:\PMAIL\MAIL TMP environment variable: C:\Users\artme\AppData\Local\Temp TEMP environment variable: C:\Users\artme\AppData\Local\Temp LAN-based SMTP support: N, N, N NetWare MHS support: N, N, N Built-in TCP/IP support: Enabled - WINSOCK version: WinSock 2.0 - WINSOCK path: WSOCK32.DLL Commandline: -A -I Admin Active -Z options: 32768 PMR variable: (None) PML variable: (None)

Windows version: 6.2
Windows flag word: 0
WINPMAIL.EXE directory: D:\PMAIL\Programs
Home mailbox location: D:\PMAIL\MAIL

User name and ID: Admin, 0


Hmmm...
This entry indicates that there is a user named "Admin"
"User name and ID: Admin, 0"
but these entries indicate that it is a single user installation, which would then mean that there should not be any named users. Please check these two things:


  1. Is there a pmail.usr file in D:\Pmail\Mail?
  2. Does the directory D:\Pmail\Mail\Admin exist.

[quote="pid:57636, uid:50806"]Windows version: 6.2 Windows flag word: 0 WINPMAIL.EXE directory: D:\PMAIL\Programs Home mailbox location: D:\PMAIL\MAIL[/quote] [quote="pid:57636, uid:50806"]User name and ID: Admin, 0[/quote] Hmmm... This entry indicates that there is a user named "Admin" "User name and ID: Admin, 0" but these entries indicate that it is a single user installation, which would then mean that there should not be any named users. Please check these two things: 1. Is there a pmail.usr file in D:\Pmail\Mail? 2. Does the directory D:\Pmail\Mail\Admin exist.

Yes, there are both.


This means that it was once a multi-user installation but is now functioning as a single user. This is likely what confused the 4.81 installer. To fix this I suggest doing a clean installation of 4.81 and then copying the \Mail directory from the 4.80 installation. The steps would be:


  • Rename the current D:\PMAIL to D:\PMAIL_480_saved
  • Run the 4.81 installer.
    • Set the installation destination to D:\PMAIL.
    • Untick the "Preconfigure a mailbox" option if it is selected. You do not want it to preconfigure one. Be attentive for any option pertaining to single or multi user. If one is presented, select single-user.
    • I believe the "roam" option will be enabled by default. I don't know whether you need it, but it is harmless if you don't, so leave it enabled.
  • The installer will complete the installation and them start prompting to start configuration. Don't do any of that. Skip or cancel all configuration prompts. Exit Pegasus Mail once you have a stable mail window.
  • Use a file explorer to confirm that you have a directory structure of D:\PMAIL|Programs and D:\PMAIL\Mail. Look in \Mail to confirm that no PMAIL.USR file exists.
  • If these are confirmed, rename D:\PMAIL\Mail to D:\PMAIL\Mail_to_be_deleted.
  • Now copy D:\PMAIL_480_saved\Mail to D:\PMAIL\Mail (you are placing a copy of the old \Mail directory in the new installation)
  • Now, in D:\PMAIL\MaiL, delete the \Admin directory and the PMAIL.USR file.

That should be it. I can now start Pegasus Mail. It should look and behave like it always did except be on 4.81.


Notice how I rename instead of delete what I think will be unneeded directories. This is out of an abundance of caution, and it provides an easy way to return to a certain point in the process for a re-do if something goes wrong. Obviously you can delete these once things are working as expected


[quote="pid:57638, uid:50806"]Yes, there are both.[/quote] This means that it was once a multi-user installation but is now functioning as a single user. This is likely what confused the 4.81 installer. To fix this I suggest doing a clean installation of 4.81 and then copying the \Mail directory from the 4.80 installation. The steps would be: - Rename the current D:\PMAIL to D:\PMAIL_480_saved - Run the 4.81 installer. - Set the installation destination to D:\PMAIL. - Untick the "Preconfigure a mailbox" option if it is selected. You do not want it to preconfigure one. Be attentive for any option pertaining to single or multi user. If one is presented, select single-user. - I believe the "roam" option will be enabled by default. I don't know whether you need it, but it is harmless if you don't, so leave it enabled. - The installer will complete the installation and them start prompting to start configuration. Don't do any of that. Skip or cancel all configuration prompts. Exit Pegasus Mail once you have a stable mail window. - Use a file explorer to confirm that you have a directory structure of D:\PMAIL|Programs and D:\PMAIL\Mail. Look in \Mail to confirm that no PMAIL.USR file exists. - If these are confirmed, rename D:\PMAIL\Mail to D:\PMAIL\Mail_to_be_deleted. - Now copy D:\PMAIL_480_saved\Mail to D:\PMAIL\Mail (you are placing a copy of the old \Mail directory in the new installation) - Now, in D:\PMAIL\MaiL, delete the \Admin directory and the PMAIL.USR file. That should be it. I can now start Pegasus Mail. It should look and behave like it always did except be on 4.81. Notice how I rename instead of delete what I think will be unneeded directories. This is out of an abundance of caution, and it provides an easy way to return to a certain point in the process for a re-do if something goes wrong. Obviously you can delete these once things are working as expected

Again. In first message it has D:\PMAIL\MAIL~N which is not correct. Is missing a \ before the ~N.
Should usually be C:\PMAIL\MAIL or C:\PMAIL\MAIL~N (C: or D: or whatever drive).
PCONFIG32.EXE to double check that and correct or confirm that it has the ~N.


I once did a test to convert a single user setup to the new default mult-user setup.
After backup, moved all files from C:\PMAIL\MAIL to C:\PMAIL\MAIL\Admin.
Then move teh C:\PMAIL\MAIL\PMAIL.USR back to C:\PMAIL\MAIL.
Need to open the C:\PMAIL\MAIL\PMAIL.INI and correct the paths with drive letter.


Working home mailbox location = C:\PMAIL\MAIL\Admin
New mailbox location = C:\PMAIL\MAIL\Admin


then use PCONFIG32.exe in programs directory to make sure it is changed to
C:\PMAIL\MAIL~N


So, files that need to be in correct sync (with whatever driver letter)
C:\PMAIL\Program\PMAIL.CFG (using PCONFIG32.exe)
C:\PMAIL\MAIL\PMAIL.USR
C:\PMAIL\MAIL\Admin\PMAIL.INI


Again. In first message it has D:\PMAIL\MAIL~N which is not correct. Is missing a \ before the ~N. Should usually be C:\PMAIL\MAIL or C:\PMAIL\MAIL\~N (C: or D: or whatever drive). PCONFIG32.EXE to double check that and correct or confirm that it has the \~N. I once did a test to convert a single user setup to the new default mult-user setup. After backup, moved all files from C:\PMAIL\MAIL to C:\PMAIL\MAIL\Admin. Then move teh C:\PMAIL\MAIL\PMAIL.USR back to C:\PMAIL\MAIL. Need to open the C:\PMAIL\MAIL\PMAIL.INI and correct the paths with drive letter. Working home mailbox location = C:\PMAIL\MAIL\Admin New mailbox location = C:\PMAIL\MAIL\Admin then use PCONFIG32.exe in programs directory to make sure it is changed to C:\PMAIL\MAIL\~N So, files that need to be in correct sync (with whatever driver letter) C:\PMAIL\Program\PMAIL.CFG (using PCONFIG32.exe) C:\PMAIL\MAIL\PMAIL.USR C:\PMAIL\MAIL\Admin\PMAIL.INI

mikes@guam.net

https://community.pmail.com/index.php?u=/topic/12214/whitepaper-combine-c-pmail-mail-into-c-pmail-mail-admin-when-home-and-new-mailbox-locations-are-different


Has some more info.


Note: If the 4.81 is installed as an upgrade it seems to detect the setup as either single or multi, and does the update keeping them in sync.


https://community.pmail.com/index.php?u=/topic/12214/whitepaper-combine-c-pmail-mail-into-c-pmail-mail-admin-when-home-and-new-mailbox-locations-are-different Has some more info. Note: If the 4.81 is installed as an upgrade it seems to detect the setup as either single or multi, and does the update keeping them in sync.

mikes@guam.net

Again. In first message it has D:\PMAIL\MAIL~N which is not correct. Is missing a \ before the ~N.
Should usually be C:\PMAIL\MAIL or C:\PMAIL\MAIL~N (C: or D: or whatever drive).
PCONFIG32.EXE to double check that and correct or confirm that it has the ~N.


This forum does not display the backslash character when it is followed by a tilde so blame the forum software for the missing backslash.


Also, IMO, converting single to multi is irrelevant. The existing 4.80 installation shows the Home and the New mailbox location as D:\PMAIL\Mail while showing the Pegasus Mail user as "Admin". That's seriously messed up. Fixing it so that D:\PMAIL\MAIL\Admin is the mailbox directory won't help since the mail data is in \MAIL. What won't surprise me is if my procedure doesn't work due to a PMAIL.INI inside of D:\PMAIL\MAIL\Admin that is specifying D:\PMAIL\MAIL as the path to the Home and New Mailboxes.


Something I didn't address, and am clueless about, is the cause of the "insufficient space" notices being thrown by installations on D:.


[quote="pid:57640, uid:2546"]Again. In first message it has D:\PMAIL\MAIL~N which is not correct. Is missing a \ before the ~N. Should usually be C:\PMAIL\MAIL or C:\PMAIL\MAIL~N (C: or D: or whatever drive). PCONFIG32.EXE to double check that and correct or confirm that it has the ~N.[/quote] This forum does not display the backslash character when it is followed by a tilde so blame the forum software for the missing backslash. Also, IMO, converting single to multi is irrelevant. The existing 4.80 installation shows the Home and the New mailbox location as D:\PMAIL\Mail while showing the Pegasus Mail user as "Admin". That's seriously messed up. Fixing it so that D:\PMAIL\MAIL\Admin is the mailbox directory won't help since the mail data is in \MAIL. What won't surprise me is if my procedure doesn't work due to a PMAIL.INI inside of D:\PMAIL\MAIL\Admin that is specifying D:\PMAIL\MAIL as the path to the Home and New Mailboxes. Something I didn't address, and am clueless about, is the cause of the "insufficient space" notices being thrown by installations on D:.
I've had the posting do some format conversionos, so uusally use the block option.
Might want to look in the registry? There are w few places where it list the mail directory and the user name.
Think this might be where the ~N gets set to Admin.

It is the PMAIL.CFG and entries in PMAIL.INI that point to were to look for the PMM/PMI and other files.
Otherwise /PMAIL/MAIL just contains the PMAIL.USR file and the subdirectories for Users mail folders.

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Software\Pegasus Mail]

[HKEY_CLASSES_ROOT\Software\Pegasus Mail\BaseDir]
@="C:\\PMAIL\\Programs"

[HKEY_CLASSES_ROOT\Software\Pegasus Mail\Command]
@="C:\\PMAIL\\Programs\\WINPM-32.EXE"

[HKEY_CLASSES_ROOT\Software\Pegasus Mail\Identity]
@="<Default>"

[HKEY_CLASSES_ROOT\Software\Pegasus Mail\Mailbox]
@="C:\\PMAIL\\MAIL\\Admin"

[HKEY_CLASSES_ROOT\Software\Pegasus Mail\Newmail]
@="C:\\PMAIL\\MAIL\\Admin"

[HKEY_CLASSES_ROOT\Software\Pegasus Mail\Username]
@="Admin"

[HKEY_CLASSES_ROOT\Software\Pegasus Mail\Version]
@="0481 32"

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Pegasus Mail]

[HKEY_CURRENT_USER\Software\Pegasus Mail\BaseDir]
@="C:\\PMAIL\\Programs"

[HKEY_CURRENT_USER\Software\Pegasus Mail\Command]
@="C:\\PMAIL\\Programs\\WINPM-32.EXE"

[HKEY_CURRENT_USER\Software\Pegasus Mail\Identity]
@="<Default>"

[HKEY_CURRENT_USER\Software\Pegasus Mail\Mailbox]
@="C:\\PMAIL\\MAIL\\Admin"

[HKEY_CURRENT_USER\Software\Pegasus Mail\Newmail]
@="C:\\PMAIL\\MAIL\\Admin"

[HKEY_CURRENT_USER\Software\Pegasus Mail\Username]
@="Admin"

[HKEY_CURRENT_USER\Software\Pegasus Mail\Version]
@="0481 32"

```` I&#039;ve had the posting do some format conversionos, so uusally use the block option. Might want to look in the registry? There are w few places where it list the mail directory and the user name. Think this might be where the ~N gets set to Admin. It is the PMAIL.CFG and entries in PMAIL.INI that point to were to look for the PMM/PMI and other files. Otherwise /PMAIL/MAIL just contains the PMAIL.USR file and the subdirectories for Users mail folders. Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\Software\Pegasus Mail] [HKEY_CLASSES_ROOT\Software\Pegasus Mail\BaseDir] @=&quot;C:\\PMAIL\\Programs&quot; [HKEY_CLASSES_ROOT\Software\Pegasus Mail\Command] @=&quot;C:\\PMAIL\\Programs\\WINPM-32.EXE&quot; [HKEY_CLASSES_ROOT\Software\Pegasus Mail\Identity] @=&quot;&lt;Default&gt;&quot; [HKEY_CLASSES_ROOT\Software\Pegasus Mail\Mailbox] @=&quot;C:\\PMAIL\\MAIL\\Admin&quot; [HKEY_CLASSES_ROOT\Software\Pegasus Mail\Newmail] @=&quot;C:\\PMAIL\\MAIL\\Admin&quot; [HKEY_CLASSES_ROOT\Software\Pegasus Mail\Username] @=&quot;Admin&quot; [HKEY_CLASSES_ROOT\Software\Pegasus Mail\Version] @=&quot;0481 32&quot; Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Pegasus Mail] [HKEY_CURRENT_USER\Software\Pegasus Mail\BaseDir] @=&quot;C:\\PMAIL\\Programs&quot; [HKEY_CURRENT_USER\Software\Pegasus Mail\Command] @=&quot;C:\\PMAIL\\Programs\\WINPM-32.EXE&quot; [HKEY_CURRENT_USER\Software\Pegasus Mail\Identity] @=&quot;&lt;Default&gt;&quot; [HKEY_CURRENT_USER\Software\Pegasus Mail\Mailbox] @=&quot;C:\\PMAIL\\MAIL\\Admin&quot; [HKEY_CURRENT_USER\Software\Pegasus Mail\Newmail] @=&quot;C:\\PMAIL\\MAIL\\Admin&quot; [HKEY_CURRENT_USER\Software\Pegasus Mail\Username] @=&quot;Admin&quot; [HKEY_CURRENT_USER\Software\Pegasus Mail\Version] @=&quot;0481 32&quot; ````

mikes@guam.net

Did check the registry for Single user setup. Note Identity is blank?


Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Pegasus Mail]

[HKEY_CURRENT_USER\Software\Pegasus Mail\BaseDir]
@="C:\\PMAIL\\Programs"

[HKEY_CURRENT_USER\Software\Pegasus Mail\Command]
@="C:\\PMAIL\\Programs\\WINPM-32.EXE -A"

[HKEY_CURRENT_USER\Software\Pegasus Mail\Identity]
@="<Default>"

[HKEY_CURRENT_USER\Software\Pegasus Mail\Mailbox]
@="C:\\PMAIL\\MAIL"

[HKEY_CURRENT_USER\Software\Pegasus Mail\Newmail]
@="C:\\PMAIL\\MAIL"

[HKEY_CURRENT_USER\Software\Pegasus Mail\Username]
@="Single-user mode"

[HKEY_CURRENT_USER\Software\Pegasus Mail\Version]
@="0481 32"

Did check the registry for Single user setup. Note Identity is blank? ```` Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Pegasus Mail] [HKEY_CURRENT_USER\Software\Pegasus Mail\BaseDir] @=&quot;C:\\PMAIL\\Programs&quot; [HKEY_CURRENT_USER\Software\Pegasus Mail\Command] @=&quot;C:\\PMAIL\\Programs\\WINPM-32.EXE -A&quot; [HKEY_CURRENT_USER\Software\Pegasus Mail\Identity] @=&quot;&lt;Default&gt;&quot; [HKEY_CURRENT_USER\Software\Pegasus Mail\Mailbox] @=&quot;C:\\PMAIL\\MAIL&quot; [HKEY_CURRENT_USER\Software\Pegasus Mail\Newmail] @=&quot;C:\\PMAIL\\MAIL&quot; [HKEY_CURRENT_USER\Software\Pegasus Mail\Username] @=&quot;Single-user mode&quot; [HKEY_CURRENT_USER\Software\Pegasus Mail\Version] @=&quot;0481 32&quot; ````

mikes@guam.net

Thank you very much Brian and msetzerii for your help. I followed your advices and it seems I can make beta installation look like an update. However, the problem of “insufficient space” is still there even in clean install of 4.81 on D: drive.


Thank you very much Brian and msetzerii for your help. I followed your advices and it seems I can make beta installation look like an update. However, the problem of &ldquo;insufficient space&rdquo; is still there even in clean install of 4.81 on D: drive.

I have sent an inquiry about the insufficient space warnings to some folks who are smarter than I. There may be questions about what drive D: is (eg: internal drive or partition?, portable usb device? network drive?).


Do you use the -ROAM command line option? I don't believe this is relevant to the insufficient space warnings issue, I'm just curious.


I have sent an inquiry about the insufficient space warnings to some folks who are smarter than I. There may be questions about what drive D: is (eg: internal drive or partition?, portable usb device? network drive?). Do you use the -ROAM command line option? I don&#039;t believe this is relevant to the insufficient space warnings issue, I&#039;m just curious.

Ideal just came to mind. Believe there was an issue with Bearhtml having an issue if the C:\Temp directory didn't exist or perhaps D:\Temp in your case. I don't recall the specifics, but just creating the directory and making sure it was writable to the user. I don't have IERenderer or BEARHMTL on my system since the IERenderer has issues with Linux, and HTS32 and TER32 are newer than the older BEARHTML, and seem to work better for Linux (at least for me).


Think Pegasus was modified at some point to user the users Temp directory, but BEAR was written to user the C:\TEMP directory, and it doesn't find the directory, might give that error.


Only 3 message in the years directory with \temp, and 13 from last years. Haven't looked at all of them.
Perhaps you could doublem check that the Temp directories do exist as shown in the directories.


Believe your earlier message showed the TEMP directories on the C: drive?
Do the exist on C: drive and/or D: drive, and are they writable?


On mine they show.
WINPMAIL.EXE directory: C:\PMAIL\Programs
Home mailbox location: C:\PMAIL\MAIL
New mailbox location: C:\PMAIL\MAIL
TMP environment variable: C:\users\msetzerii\Temp
TEMP environment variable: C:\users\msetzerii\Temp


Do you have yours as C: or D: for any and do the exist and writable.
What exact version of Windows are you using?


Ideal just came to mind. Believe there was an issue with Bearhtml having an issue if the C:\Temp directory didn&#039;t exist or perhaps D:\Temp in your case. I don&#039;t recall the specifics, but just creating the directory and making sure it was writable to the user. I don&#039;t have IERenderer or BEARHMTL on my system since the IERenderer has issues with Linux, and HTS32 and TER32 are newer than the older BEARHTML, and seem to work better for Linux (at least for me). Think Pegasus was modified at some point to user the users Temp directory, but BEAR was written to user the C:\TEMP directory, and it doesn&#039;t find the directory, might give that error. Only 3 message in the years directory with \temp, and 13 from last years. Haven&#039;t looked at all of them. Perhaps you could doublem check that the Temp directories do exist as shown in the directories. Believe your earlier message showed the TEMP directories on the C: drive? Do the exist on C: drive and/or D: drive, and are they writable? On mine they show. WINPMAIL.EXE directory: C:\PMAIL\Programs Home mailbox location: C:\PMAIL\MAIL New mailbox location: C:\PMAIL\MAIL TMP environment variable: C:\users\msetzerii\Temp TEMP environment variable: C:\users\msetzerii\Temp Do you have yours as C: or D: for any and do the exist and writable. What exact version of Windows are you using?

mikes@guam.net

It’s a second SSD drive in my laptop. I don’t use –ROAM command line. Should I? What is clear by now that “insufficient space” is 4.81 specific. I made a clean install of 4.80 on D: drive and then copied MAIL folder following your advice. Everything working good so far, no insufficient space messages. And I cleaned up all this mess that accumulated in PMAIL over decades. Thank you once again for this. As for 4.81, I’m curious if new release will still have this problem. My guess it will, since nobody seems to have this issue. Maybe it’s my system specific, who knows. So far, it seems I’m stuck with 4.80. I would very much appreciate your further inquiries on this problem.
Msetzerii, I do have Temp directories on both drives. That was my first idea that came to mind to make a path to D:\Tem in PMAIL.INI, and I can see temporary files are being placed there upon opening emails and cleared off when program closes.


It&rsquo;s a second SSD drive in my laptop. I don&rsquo;t use &ndash;ROAM command line. Should I? What is clear by now that &ldquo;insufficient space&rdquo; is 4.81 specific. I made a clean install of 4.80 on D: drive and then copied MAIL folder following your advice. Everything working good so far, no insufficient space messages. And I cleaned up all this mess that accumulated in PMAIL over decades. Thank you once again for this. As for 4.81, I&rsquo;m curious if new release will still have this problem. My guess it will, since nobody seems to have this issue. Maybe it&rsquo;s my system specific, who knows. So far, it seems I&rsquo;m stuck with 4.80. I would very much appreciate your further inquiries on this problem. Msetzerii, I do have Temp directories on both drives. That was my first idea that came to mind to make a path to D:\Tem in PMAIL.INI, and I can see temporary files are being placed there upon opening emails and cleared off when program closes.

Did just notice a difference.


Your message shows
TMP environment variable: C:\Users\artme\AppData\Local\Temp
TEMP environment variable: C:\Users\artme\AppData\Local\Temp


Mine shows
TMP environment variable: C:\users\msetzerii\Temp
TEMP environment variable: C:\users\msetzerii\Temp


Not clear on difference between \Temp and \AppData\Local\Temp??


I have the \AppData\Local\Temp directory, but it is totally empty.
The \Temp directory does have Pegasus Files in it.
Again, I run Pegasus using Linux with Wine, so your version of Windows may do it differently.
Are there any files in C:\Users\artme\AppData\Local\Temp or in C:\Users\artme\Temp


Not sure if Pegasus has write access to C:\Users\artme\AppData\Local\Temp? Know Pegasus doesn't work if installed in the Program Files directory because of some permissions.


Did just notice a difference. Your message shows TMP environment variable: C:\Users\artme\AppData\Local\Temp TEMP environment variable: C:\Users\artme\AppData\Local\Temp Mine shows TMP environment variable: C:\users\msetzerii\Temp TEMP environment variable: C:\users\msetzerii\Temp Not clear on difference between \Temp and \AppData\Local\Temp?? I have the \AppData\Local\Temp directory, but it is totally empty. The \Temp directory does have Pegasus Files in it. Again, I run Pegasus using Linux with Wine, so your version of Windows may do it differently. Are there any files in C:\Users\artme\AppData\Local\Temp or in C:\Users\artme\Temp Not sure if Pegasus has write access to C:\Users\artme\AppData\Local\Temp? Know Pegasus doesn&#039;t work if installed in the Program Files directory because of some permissions.

mikes@guam.net

I run Windows 11, and I believe \AppData\Local\Temp is the directory for most programs and is definitely used in my case. I did not check if it is used by 4.80 and not used by 4.81, maybe worth testing.


I run Windows 11, and I believe \AppData\Local\Temp is the directory for most programs and is definitely used in my case. I did not check if it is used by 4.80 and not used by 4.81, maybe worth testing.
12
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft