Community Discussions and Support
Installing pegasus in a 64 bit OS

It makes no sense that it was working when installed in \Program Files (x86) on a previous Win7 machine, regardless of the bittedness.  All experiences I have seen indicate failures when installed inside of a \Program Files directory on any Win7 OS.  That said,  the only thing I know about 32 bit vs. 64 bit is that 64 bit allows you process more data at once and access more memory.  I haven't encountered any old apps that wouldn't run on my 64 bit machines but I have found many that won't work correctly when installed in \Program Files.  All of these do what Pegasas Mail does which is routine update configuration or .ini files that reside with the rest of the program rather than some other place like \AppData.

It makes no sense that it was working when installed in \Program Files (x86) on a previous Win7 machine, regardless of the bittedness.  All experiences I have seen indicate failures when installed inside of a \Program Files directory on any Win7 OS.  That said,  the only thing I know about 32 bit vs. 64 bit is that 64 bit allows you process more data at once and access more memory.  I haven't encountered any old apps that wouldn't run on my 64 bit machines but I have found many that won't work correctly when installed in \Program Files.  All of these do what Pegasas Mail does which is routine update configuration or .ini files that reside with the rest of the program rather than some other place like \AppData.

I have been a pegasus user for many many years. I got a new laptop that has 64 bit windows 7 and I would like to install peagsus. I installed 4.70 and when I start it up I point it to where my data files are. As soon as I do this it shows me all the users I have a mail box for. AT this point however, I only have a close button. As soon as I do Peagsus closes. If I try start again it just gors to the sme screen asking me again how I want to run the system (single user, multiple user, etc).

 

I have tried opening the program with the -i option and my mailbox name but that does the same. Can Peagsus not run on 64 bit Windows 7? 

<p>I have been a pegasus user for many many years. I got a new laptop that has 64 bit windows 7 and I would like to install peagsus. I installed 4.70 and when I start it up I point it to where my data files are. As soon as I do this it shows me all the users I have a mail box for. AT this point however, I only have a close button. As soon as I do Peagsus closes. If I try start again it just gors to the sme screen asking me again how I want to run the system (single user, multiple user, etc).</p><p> </p><p>I have tried opening the program with the -i option and my mailbox name but that does the same. Can Peagsus not run on 64 bit Windows 7? </p>

I also renamed my data folder, and then created a new one but the same thing happens.

I also renamed my data folder, and then created a new one but the same thing happens.

Pmail will run on 64-bit systems.

If you provide more information about how you transferred to the new machine more help will be forthcoming.

<p>Pmail will run on 64-bit systems.</p><p>If you provide more information about how you transferred to the new machine more help will be forthcoming. </p>

[quote user="caisson"]If you provide more information about how you transferred to the new machine more help will be forthcoming.[/quote]

And to which directory specifically ... information from the menu Help => About => Info screen in Pegasus Mail might help!

<p>[quote user="caisson"]If you provide more information about how you transferred to the new machine more help will be forthcoming.[/quote]</p><p>And to which directory specifically ... information from the menu <i>Help => About => Info</i> screen in Pegasus Mail might help! </p>
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

Here is the old machine info.

 

Pegasus Mail for Microsoft Windows

Copyright (C) 1992-2011, David Harris, all rights reserved

Electronic mail to support@pmail.gen.nz.


WinPMail version: Version 4.63 (Win32), Dec 22 2011, build ID 325

Language resources: Standard UK English resource set

Extension Manager version: 1.14

Operating mode: Standalone

User name and ID: glrider, 0

Windows version: 6.1

Windows flag word: 0

WINPMAIL.EXE directory: C:\Program Files (x86)\PMail\Programs

Home mailbox location: C:\DATA\PMAIL\MAIL\glrider

New mailbox location: C:\DATA\PMAIL\MAIL\glrider

TMP environment variable: C:\Users\glrider\AppData\Local\Temp

TEMP environment variable: C:\Users\glrider\AppData\Local\Temp

LAN-based SMTP support: N, N, N

NetWare MHS support: N, N, N

Built-in TCP/IP support: Enabled

  - WINSOCK version: (Not loaded)

  - WINSOCK path: C:\Windows\system32\WSOCK32.DLL

Commandline: -i glrider

Active -Z options: 32768

PMR variable: (None)

PML variable: (None)

MAI variable: (None)

NB variable: (None)

Autofiltering folders: 0 (0 active, 0 inactive)

Last new mail count: 1

Message size soft limit: 0 bytes

Message size hard limit: 0 bytes

Attachment size soft limit: 0 bytes

Attachment size hard limit: 0 bytes

 

 

The structure for holding my email will be the same except for it will be on the E drive instead of the C drive.

 

On both machine the software was installed into c:\program files(x86)\pmail 

<p>Here is the old machine info.</p><p> </p><p>Pegasus Mail for Microsoft Windows</p><p>Copyright (C) 1992-2011, David Harris, all rights reserved</p><p>Electronic mail to support@pmail.gen.nz.</p><p> </p><p>WinPMail version: Version 4.63 (Win32), Dec 22 2011, build ID 325</p><p>Language resources: Standard UK English resource set</p><p>Extension Manager version: 1.14</p><p>Operating mode: Standalone</p><p>User name and ID: glrider, 0</p><p>Windows version: 6.1</p><p>Windows flag word: 0</p><p>WINPMAIL.EXE directory: C:\Program Files (x86)\PMail\Programs</p><p>Home mailbox location: C:\DATA\PMAIL\MAIL\glrider</p><p>New mailbox location: C:\DATA\PMAIL\MAIL\glrider</p><p>TMP environment variable: C:\Users\glrider\AppData\Local\Temp</p><p>TEMP environment variable: C:\Users\glrider\AppData\Local\Temp</p><p>LAN-based SMTP support: N, N, N</p><p>NetWare MHS support: N, N, N</p><p>Built-in TCP/IP support: Enabled</p><p>  - WINSOCK version: (Not loaded)</p><p>  - WINSOCK path: C:\Windows\system32\WSOCK32.DLL</p><p>Commandline: -i glrider</p><p>Active -Z options: 32768</p><p>PMR variable: (None)</p><p>PML variable: (None)</p><p>MAI variable: (None)</p><p>NB variable: (None)</p><p>Autofiltering folders: 0 (0 active, 0 inactive)</p><p>Last new mail count: 1</p><p>Message size soft limit: 0 bytes</p><p>Message size hard limit: 0 bytes</p><p>Attachment size soft limit: 0 bytes</p><p>Attachment size hard limit: 0 bytes</p><p> </p><p> </p><p>The structure for holding my email will be the same except for it will be on the E drive instead of the C drive.</p><p> </p><p>On both machine the software was installed into c:\program files(x86)\pmail </p>

Sorry for the transfer mode I used file transfer within Team Viewer.

Sorry for the transfer mode I used file transfer within Team Viewer.

[quote user="glrider"]On both machine the software was installed into c:\program files(x86)\pmail [/quote]

This is the reason for your problems: Since Win7 you must not install to this path anymore. For more details see this post.

<p>[quote user="glrider"]On both machine the software was installed into c:\program files(x86)\pmail [/quote]</p><p>This is the reason for your problems: Since Win7 you must not install to this path anymore. For more details see <a href="/forums/post/25552.aspx" target="_blank" mce_href="/forums/post/25552.aspx">this post</a>. </p>
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

So I see this to run this dosbox emulator. I am guessing I need to run this emulator every time I want to start pegasus and not just to run pconfig. Is this correct? If so maybe it is not worth it. Maybe I will either just stick with my old 32 bit machine or use a different email program, which I really don't want to do.

 

I saw a post from Dave some where that talked about how big pegasus is and the time it is taking to get to version 5. Any chance a 32 bit version will ever be created? 

<p>So I see this to run this dosbox emulator. I am guessing I need to run this emulator every time I want to start pegasus and not just to run pconfig. Is this correct? If so maybe it is not worth it. Maybe I will either just stick with my old 32 bit machine or use a different email program, which I really don't want to do.</p><p> </p><p>I saw a post from Dave some where that talked about how big pegasus is and the time it is taking to get to version 5. Any chance a 32 bit version will ever be created? </p>

The issue you are experiencing has nothing to do with bittedness.  Beginning with Window7, Microsoft introduced file protections in the \Program Files directory that prohibit Pegasus Mail from being able to update its configuration files. 

If you are wanting to migrate an installation from a pre-Win7 OS to Win7 or later and that previous installation was anywhere inside of the \Program Files directory then you MUST do a clean install of Pegasus Mail to the new OS and install in a location outside of the \Program Files directory.  The default locations of C:\PMail\Programs and C:\Pmail\Mail is strongly recommended for ease of troubleshooting and upgrading. 

If your goal is to duplicate the previous install then you will need to

create Pegasus Mail users in the new install that are identical to the

ones in the old install.   You can then copy data from the mailbox directories of the old installation to those of the new installation (mail, addressbooks, distribution lists,...).  Use the whitepaper found at the link below as a guide.

http://community.pmail.com/files/folders/whitepapers/entry41852.aspx

This process is not very difficult once you get into it.  The only thing that is tedious is if you had a lot of identities in the old install as these need to be recreated manually in the new install. 

It is EXTREMELY important that you do not overwrite any configuration files when copying from the old install.  If you are unsure about an overwrite, ask first.  Work slowly, test often.  Backup the mailbox directory often as you work so you can quickly restore it should something go wrong.

Hint:  Print out the PMAIL.INI file from each mailbox directory of the old install and use them as a guide for configuring each user in the new install.

BTW, this approach eliminates the need to run pconfig.

<p>The issue you are experiencing has nothing to do with bittedness.  Beginning with Window7, Microsoft introduced file protections in the \Program Files directory that prohibit Pegasus Mail from being able to update its configuration files.  </p><p>If you are wanting to migrate an installation from a pre-Win7 OS to Win7 or later and that previous installation was anywhere inside of the \Program Files directory then you MUST do a clean install of Pegasus Mail to the new OS and install in a location outside of the \Program Files directory.  The default locations of C:\PMail\Programs and C:\Pmail\Mail is strongly recommended for ease of troubleshooting and upgrading.  </p><p>If your goal is to duplicate the previous install then you will need to create Pegasus Mail users in the new install that are identical to the ones in the old install.   You can then copy data from the mailbox directories of the old installation to those of the new installation (mail, addressbooks, distribution lists,...).  Use the whitepaper found at the link below as a guide.</p><p>http://community.pmail.com/files/folders/whitepapers/entry41852.aspx </p><p>This process is not very difficult once you get into it.  The only thing that is tedious is if you had a lot of identities in the old install as these need to be recreated manually in the new install. </p><p> It is EXTREMELY important that you do not overwrite any configuration files when copying from the old install.  If you are unsure about an overwrite, ask first.  Work slowly, test often.  Backup the mailbox directory often as you work so you can quickly restore it should something go wrong. </p><p>Hint:  Print out the PMAIL.INI file from each mailbox directory of the old install and use them as a guide for configuring each user in the new install. </p><p>BTW, this approach eliminates the need to run pconfig. </p>

Brian,

 

This is perfect.  That is exactly what I tried to do but was not aware of the new windows 7 restrictions. I will give it a shot and get back to you.

 

P.S. Nice bike. I have a 2000 GL1500.....ride on  

<p>Brian,</p><p> </p><p>This is perfect.  That is exactly what I tried to do but was not aware of the new windows 7 restrictions. I will give it a shot and get back to you.</p><p> </p><p>P.S. Nice bike. I have a 2000 GL1500.....ride on  </p>

Are you sorted now?

The best way to do this is indeed to install somewhere other than program files like C:\pmail for example.  Another way if to as an administrator go in to the program Files directory where Pegasus is and change the directory permissions.  I have used bot approaches successfully but preffer putting Pegasus outside the program Files structure.  It can be worth making sure that any user account that will be using Pegasus has Fill Control of C:\Pmail or wherever you put Pegasus.

For what it is worth I am currently running Pegasus on a 64 bit Windows 10 system, using Davmail to access the Exchange server which my company has insisted we use in their head office in the USA.

 

<p>Are you sorted now?</p><p>The best way to do this is indeed to install somewhere other than program files like C:\pmail for example.  Another way if to as an administrator go in to the program Files directory where Pegasus is and change the directory permissions.  I have used bot approaches successfully but preffer putting Pegasus outside the program Files structure.  It can be worth making sure that any user account that will be using Pegasus has Fill Control of C:\Pmail or wherever you put Pegasus.</p><p>For what it is worth I am currently running Pegasus on a 64 bit Windows 10 system, using Davmail to access the Exchange server which my company has insisted we use in their head office in the USA.</p><p> </p>

Hi All,

 

Thanks so much for your help. I have successfully migrated my email  to my Windows 7 64 bit laptop.

 

One parting question though. Brian said it had nothing to do with bitness., but it just occured to me as I was writing this response that my desktop I migrated from was also Windows 7, but it is 32 bit. So maybe the restrictions from Microsoft did indeed only take hold in the 64 bit version of Windows 7.

 

Thanks again for your help. I praise the people who take their spare time to help out on list forums. 

<p>Hi All,</p><p> </p><p>Thanks so much for your help. I have successfully migrated my email  to my Windows 7 64 bit laptop.</p><p> </p><p>One parting question though. Brian said it had nothing to do with bitness., but it just occured to me as I was writing this response that my desktop I migrated from was also Windows 7, but it is 32 bit. So maybe the restrictions from Microsoft did indeed only take hold in the 64 bit version of Windows 7.</p><p> </p><p>Thanks again for your help. I praise the people who take their spare time to help out on list forums. </p>
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