Community Discussions and Support
Problem setting up a peer to peer workgroup network with v4.63

[quote user="StanH"]
Q - Are these startup times unusual?
Startup time desktop: 2 sec
Startup time laptop: 50 sec
(15sec to display Pegasus)
(25 more sec to begin folder window -- this is reduced to 10 sec by not using the mapped drive approach.)
(10 more sec to display newmail list)
[/quote]

Too long.  There are two known issues that impact Pegasus Mail performance:

1. Printer driver - which you have addressed

2. Winsock - In Tools > Options > General settings > Advanced settings  ensure that the "Load Windows Internet Services" option is set to "Always"

 

There was a second question in my email notice from the forum that has not appeared here which was:

[quote user="StanH"]Q2 - What settings control startup configuration: Like start with [Mail
folders..] closed, and when opened, have My Mailbox selected, or make My
Mailbox and Gmail open together?[/quote]

Tools > Options > General settings > Basic settings > Save the Pegasus Mail desktop state between sessions.  Read the help files for details about what this saves. 

Most configuration settings, including this one, are mailbox specific so keep in mind that you are accessing the Admin mailbox from two machines so changes made on one machine will be reflected on the other machine.  You can enable the "Save desktop state" option, configure things as you like, close Pegasus Mail to save, then reopen and disable that setting so things don't get altered but that setting must be disabled on both machines.  Also, there is a method of using a different .ini file by each machine but it doesn't offer much in the way of control (different main window sizes & specifying a different temp directory are the only ones that come to mind). 

 

<p>[quote user="StanH"] Q - Are these startup times unusual? Startup time desktop: 2 sec Startup time laptop: 50 sec (15sec to display Pegasus) (25 more sec to begin folder window -- this is reduced to 10 sec by not using the mapped drive approach.) (10 more sec to display newmail list) [/quote]</p><p>Too long.  There are two known issues that impact Pegasus Mail performance:</p><p>1. Printer driver - which you have addressed</p><p>2. Winsock - In Tools > Options > General settings > Advanced settings  ensure that the "Load Windows Internet Services" option is set to "Always"</p><p> </p><p>There was a second question in my email notice from the forum that has not appeared here which was: </p><p>[quote user="StanH"]Q2 - What settings control startup configuration: Like start with [Mail folders..] closed, and when opened, have My Mailbox selected, or make My Mailbox and Gmail open together?[/quote] </p><p>Tools > Options > General settings > Basic settings > Save the Pegasus Mail desktop state between sessions.  Read the help files for details about what this saves.  </p><p>Most configuration settings, including this one, are mailbox specific so keep in mind that you are accessing the Admin mailbox from two machines so changes made on one machine will be reflected on the other machine.  You can enable the "Save desktop state" option, configure things as you like, close Pegasus Mail to save, then reopen and disable that setting so things don't get altered but that setting must be disabled on both machines.  Also, there is a method of using a different .ini file by each machine but it doesn't offer much in the way of control (different main window sizes & specifying a different temp directory are the only ones that come to mind).  </p><p> </p>

I have Pegasus v4.63 installed on Win 7 Pro 64 desktop. I ran wssetup.exe on a  Win 7 Pro 64 laptop networked peer to peer. wssetup did not ask me for the address of the a computer and created a shortcut as if local.

C:\PMAIL\Programs\winpm-32.exe -roam -A -I Admin

I modified it but the following didn't work either:

\\Dell-T1700\PMAIL\Programs\winpm-32.exe -roam -A -I Admin

(The user you are attempting to 'become' (Admin) does not exist on this system.)

The file configuration on the desktop pc is:
C:\pmail\mail\Admin
C:\pmail\programs
 

 Also, my V4.63 is recently installed. Now I see that v4.71 is the official version. Will v4.71 work better with the network? What does it take to upgrade?

<p>I have Pegasus v4.63 installed on Win 7 Pro 64 desktop. I ran wssetup.exe on a  Win 7 Pro 64 laptop networked peer to peer. wssetup did not ask me for the address of the a computer and created a shortcut as if local. C:\PMAIL\Programs\winpm-32.exe -roam -A -I Admin I modified it but the following didn't work either: \\Dell-T1700\PMAIL\Programs\winpm-32.exe -roam -A -I Admin (The user you are attempting to 'become' (Admin) does not exist on this system.)</p><p>The file configuration on the desktop pc is: C:\pmail\mail\Admin C:\pmail\programs  </p><p> Also, my V4.63 is recently installed. Now I see that v4.71 is the official version. Will v4.71 work better with the network? What does it take to upgrade? </p>

UPDATE:

I upgradedv4.63 to v4.71. The program runs good but from the laptop it still won't accept the Admin username.

<p>UPDATE:</p><p>I upgradedv4.63 to v4.71. The program runs good but from the laptop it still won't accept the Admin username. </p>

Try removing the -roam option.  That is telling Pegasus Mail to ignore path references and use the local drive.  

If that doesn't work, on the laptop try mapping a drive to C: on \\Dell-T1700 and then in a command window change to that drive, navigate to \PMAIL\Programs, and then run wssetup and see if that makes a difference.

An unknown to me is how wssetup behaves on a single user install since it is designed for use with a multi-user network install.  Regardless, manually creating the shortcut should work provided all the Windows networking components are configured correctly (this is the most challenging part).

 

 

<p>Try removing the -roam option.  That is telling Pegasus Mail to ignore path references and use the local drive.   </p><p>If that doesn't work, on the laptop try mapping a drive to C: on \\Dell-T1700 and then in a command window change to that drive, navigate to \PMAIL\Programs, and then run wssetup and see if that makes a difference.</p><p>An unknown to me is how wssetup behaves on a single user install since it is designed for use with a multi-user network install.  Regardless, manually creating the shortcut should work provided all the Windows networking components are configured correctly (this is the most challenging part).</p><p> </p><p> </p>

[quote user="Brian Fluet"]

Try removing the -roam option.  That is telling Pegasus Mail to ignore path references and use the local drive.  

[/quote]That didn't work.

[quote]If that doesn't work, on the laptop try mapping a drive to C: on \\Dell-T1700 and then in a command window change to that drive, navigate to \PMAIL\Programs, and then run wssetup and see if that makes a difference.

[/quote] The drive C: does not show in the Map browse window -- but \pmail\, \mail\, and \admin\ show.

[quote] An unknown to me is how wssetup behaves on a single user install since it is designed for use with a multi-user network install.  Regardless, manually creating the shortcut should work provided all the Windows networking components are configured correctly (this is the most challenging part).

[/quote]I can access all the Pegasus files on \\Dell-T1700 from IE on the laptop. (leaving off the C: ) But not with the Pegasus shortcut. I created a Windows shortcut on the laptop to \Admin on \\Dell-T1700. Clicking it opens IE showing all the files in \admin.

Since the Pegasus shortcut on laptop opens winpm-32.exe on \\Dell-T1700 I conclude that the permissions are correct for starting the executable. The problem is when the executable tries to access \admin. I verified this by creating a windows shortcut on the laptop that opens \admin and then double click winpm-32.exe. It runs but doesn't get past the user-input screen.

[quote user="Brian Fluet"]<p>Try removing the -roam option.  That is telling Pegasus Mail to ignore path references and use the local drive.   </p><p>[/quote]That didn't work.</p><p> [quote]If that doesn't work, on the laptop try mapping a drive to C: on \\Dell-T1700 and then in a command window change to that drive, navigate to \PMAIL\Programs, and then run wssetup and see if that makes a difference.</p><p>[/quote] The drive C: does not show in the Map browse window -- but \pmail\, \mail\, and \admin\ show. </p><p>[quote] An unknown to me is how wssetup behaves on a single user install since it is designed for use with a multi-user network install.  Regardless, manually creating the shortcut should work provided all the Windows networking components are configured correctly (this is the most challenging part).</p><p>[/quote]I can access all the Pegasus files on \\Dell-T1700 from IE on the laptop. (leaving off the C: ) But not with the Pegasus shortcut. I created a Windows shortcut on the laptop to \Admin on \\Dell-T1700. Clicking it opens IE showing all the files in \admin.</p><p>Since the Pegasus shortcut on laptop opens winpm-32.exe on \\Dell-T1700 I conclude that the permissions are correct for starting the executable. The problem is when the executable tries to access \admin. I verified this by creating a windows shortcut on the laptop that opens \admin and then double click winpm-32.exe. It runs but doesn't get past the user-input screen. </p>

When winpm32.exe is run it looks to the PMAIL.CFG file for the path to the mailboxes (users).  I recall when setting the office network install years ago it was important to make sure all machines recognized the same path so a UNC path was used to avoid having to worry about mapped drives being consistent on all machines.  In our case the mailboxes were on a server so not on a machine from which Pegasus Mail was being run but I think the concept would be the same.  So I think if PMAIL.CFG contained a path to  \\Dell-T1700\pmail\mail then both machines would recognize that path (test that). 

PMAIL.CFG is one of the few Pegasus Mail configuration files that can not be manually edited.  It is modified by running PCONFIG.EXE (or PCONFIG32.EXE which is a 32 bit version released with version 4.71).  You might try copying your existing PMAIL.CFG file for safe keeping then running PCONFIG32.EXE and setting the home mailbox root location to \\Dell-T1700\pmail\mail\~N provided this is a valid path for the Dell desktop.  If it isn't then map the same drive letter on both machines to \\Dell-T1700\pmail then use MappedDrive:\\mail\~N as the path instead.


<p>When winpm32.exe is run it looks to the PMAIL.CFG file for the path to the mailboxes (users).  I recall when setting the office network install years ago it was important to make sure all machines recognized the same path so a UNC path was used to avoid having to worry about mapped drives being consistent on all machines.  In our case the mailboxes were on a server so not on a machine from which Pegasus Mail was being run but I think the concept would be the same.  So I think if PMAIL.CFG contained a path to  \\Dell-T1700\pmail\mail then both machines would recognize that path (test that).  </p><p>PMAIL.CFG is one of the few Pegasus Mail configuration files that can not be manually edited.  It is modified by running PCONFIG.EXE (or PCONFIG32.EXE which is a 32 bit version released with version 4.71).  You might try copying your existing PMAIL.CFG file for safe keeping then running PCONFIG32.EXE and setting the home mailbox root location to \\Dell-T1700\pmail\mail\~N provided this is a valid path for the Dell desktop.  If it isn't then map the same drive letter on both machines to \\Dell-T1700\pmail then use MappedDrive:\\mail\~N as the path instead. </p>

I ran pconfig32.exe and left the configuration directory as C:\PMAIL\Programs and changed the home mailbox root location to \\Dell-T1700\pmail\mail\~N. That prevented the program from starting. (on the desktop)

Edit

I tried this from a Win10 laptop and had the same result. Doesn't recognize Admin.

<p>I ran pconfig32.exe and left the configuration directory as C:\PMAIL\Programs and changed the home mailbox root location to \\Dell-T1700\pmail\mail\~N. That prevented the program from starting. (on the desktop)</p><p>Edit</p><p>I tried this from a Win10 laptop and had the same result. Doesn't recognize Admin. </p>

[quote user="StanH"]

I ran pconfig32.exe and left the configuration directory as C:\PMAIL\Programs and changed the home mailbox root location to \\Dell-T1700\pmail\mail\~N. That prevented the program from starting. (on the desktop)

Edit

I tried this from a Win10 laptop and had the same result. Doesn't recognize Admin.

[/quote]

I believe the trick is to get the path to the mailbox directory set to one that is usable by both PCs.  Mapping the same drive on both machines as previously mentioned is the next thing to try.

Triple check the networking as well.  Are your share and NTFS permissions granted at the \Pmail directory level and allowed to propogate to all subdirectories?  I know you said you could browse the \Admin directory from the laptop but confirm that you can open and modify files.  Use the desktop to create some test .txt files in \Pmail\Programs, \Pmail\Mail, and \Pmail\Mail\Admin then modify each from the laptop.

 

[quote user="StanH"]<p>I ran pconfig32.exe and left the configuration directory as C:\PMAIL\Programs and changed the home mailbox root location to \\Dell-T1700\pmail\mail\~N. That prevented the program from starting. (on the desktop)</p><p>Edit</p><p>I tried this from a Win10 laptop and had the same result. Doesn't recognize Admin. </p><p>[/quote]</p><p>I believe the trick is to get the path to the mailbox directory set to one that is usable by both PCs.  Mapping the same drive on both machines as previously mentioned is the next thing to try.</p><p>Triple check the networking as well.  Are your share and NTFS permissions granted at the \Pmail directory level and allowed to propogate to all subdirectories?  I know you said you could browse the \Admin directory from the laptop but confirm that you can open and modify files.  Use the desktop to create some test .txt files in \Pmail\Programs, \Pmail\Mail, and \Pmail\Mail\Admin then modify each from the laptop. </p><p> </p>

[quote user="Brian Fluet"]I believe the trick is to get the path to the mailbox directory set to one that is usable by both PCs.  Mapping the same drive on both machines as previously mentioned is the next thing to try.

Triple check the networking as well.  Are your share and NTFS permissions granted at the \Pmail directory level and allowed to propogate to all subdirectories?  I know you said you could browse the \Admin directory from the laptop but confirm that you can open and modify files.  Use the desktop to create some test .txt files in \Pmail\Programs, \Pmail\Mail, and \Pmail\Mail\Admin then modify each from the laptop. [/quote]

I verified that I can access and modify test file on the mailbox from the laptop.That was OK.

Accessing \Programs\PMAIL.CFG from either computer is not a problem by any method of addressing.

My (previous) problem has been that I wasn't making syntax of the laptop shortcut's address to \Programs\ match the syntax of home mailbox root address that is in PMAIL.INI. I had to use the UNC address to the mailbox in PMAIL.CFG to prevent the "Admin doesn't exist" error on the laptop. Addressing \Programs\ from the desktop computer does not require this matching so I can use C:... It is only the laptop shortcut and PMAIL.CFG address of the mailbox that require matching UNC addresses.

I removed -roam from all shortcuts, as I now understand that it

blocks the "\\DELL-T1700\PMAIL\MAIL\~N" type of (UNC) addressing.

My remaining problem  (I hope) is that during the startup of Pegasus on the laptop, after "restoring desktop layout", it is killed by an error addressing the printer.

[quote user="Brian Fluet"]I believe the trick is to get the path to the mailbox directory set to one that is usable by both PCs.  Mapping the same drive on both machines as previously mentioned is the next thing to try.<p>Triple check the networking as well.  Are your share and NTFS permissions granted at the \Pmail directory level and allowed to propogate to all subdirectories?  I know you said you could browse the \Admin directory from the laptop but confirm that you can open and modify files.  Use the desktop to create some test .txt files in \Pmail\Programs, \Pmail\Mail, and \Pmail\Mail\Admin then modify each from the laptop. [/quote]</p><p>I verified that I can access and modify test file on the mailbox from the laptop.That was OK. </p><p>Accessing \Programs\PMAIL.CFG from either computer is not a problem by any method of addressing.</p>My (previous) problem has been that I wasn't making syntax of the laptop shortcut's address to \Programs\ match the syntax of home mailbox root address that is in PMAIL.INI. I had to use the UNC address to the mailbox in PMAIL.CFG to prevent the "Admin doesn't exist" error on the laptop. Addressing \Programs\ from the desktop computer does not require this matching so I can use C:... It is only the laptop shortcut and PMAIL.CFG address of the mailbox that require matching UNC addresses. <p>I removed -roam from all shortcuts, as I now understand that it blocks the "\\DELL-T1700\PMAIL\MAIL\~N" type of (UNC) addressing. </p><p>My remaining problem  (I hope) is that during the startup of Pegasus on the laptop, after "restoring desktop layout", it is killed by an error addressing the printer. </p>

Pegasus Mail is dependent on a printer driver which requires that a default printer be installed.  This has become challenging in recent years because Pegasus Mail checks for the printer driver which in turn may check to confirm that the printer is online.  If any of these checks fail, Pegasus Mail struggles.  In cases where a printer is not alway accessible you may have to install a generic text printer as the default printer then manually select the physical printer when you need to print.

Pegasus Mail is dependent on a printer driver which requires that a default printer be installed.  This has become challenging in recent years because Pegasus Mail checks for the printer driver which in turn may check to confirm that the printer is online.  If any of these checks fail, Pegasus Mail struggles.  In cases where a printer is not alway accessible you may have to install a generic text printer as the default printer then manually select the physical printer when you need to print.

I got Pegasus to load from the laptop by installing a printer driver -- even though there is no printer connected.

Q - Are these startup times unusual?
Startup time desktop: 2 sec
Startup time laptop: 50 sec
(15sec to display Pegasus)
(25 more sec to begin folder window -- this is reduced to 10 sec by not using the mapped drive approach.)
(10 more sec to display newmail list)

I got Pegasus to load from the laptop by installing a printer driver -- even though there is no printer connected. Q - Are these startup times unusual? Startup time desktop: 2 sec Startup time laptop: 50 sec (15sec to display Pegasus) (25 more sec to begin folder window -- this is reduced to 10 sec by not using the mapped drive approach.) (10 more sec to display newmail list)
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