[quote user="Thomas R. Stephenson"]

Try doing this manually to create the shortcut and make sure that the users have all rights to their mail directories on the server.


Might also get a copy of the mini-dump file extension so that you can send in a crash report.  Michael will analyze the file to pin-point the problem.
http://community.pmail.com/files/folders/community_add-ons_for_pegasus_mail/entry12763.aspx



First of all get a copy of DOSBox and you can run pconfig.exe to set the home and new mail directory.  When you do make sure you are using the UNC \\server\share\path\~n format instead of the drive_letter:\path\~n format.

[/quote]

I tried all of the above including setting pconfig to the server ip address ( from a 32 bit machine ) instead of a name or directory letter.

Nothing would work

 ( 64 bit users would not open ) 

So next from a 32 bit I created a new user 

This I could open on the 64bit machines.

So I then copied and patched all the user folders, settings signatures  etc over from a user which would not open on a 64bit machine...

Then the user(s) which would not open on the 64 bit , the new patched over version would

I checked line for line all  the *.ini files the  *.pm files they were identical line for line..in both the user that would not open and the patched version that would .

So I got it working on win7 64bit but with no logic

 First well done the the beta team for all the work on the upgrade  [:)]

Maybe I didn't post this in the correct place

But I have come across a small problem I have not  been able to work around.

OK well as I described yesterday the 4.61 worked well when installed last night on 32 and 64 bit win 7

This was as stanadlone machines  where files were on the local drive.

Today I upgraded a small office network.Here the files, both programme and mail folders are on a file server.

All 32 bit systems work as expected.

However our 64bit machines ( We have 3 ) both win 7 (2) and visa (1) have an identical  problem.

After upgrade on the file server each local machine ran the wssetup file to set the parametes

 However

when you try to start the progamme over the network, ( put in your

username and wait etc.) it gets to a point where it is above to load (

we have pubic folders so this take a min or two). the programe then

crashes with the single windows error message .

 ( Pegasus mail

for windows has stopped working....A problem caused the progamme to stop

working correctly....windows will close the programme ....and notify

you if a solution is available )

 Next on the same 64bit win7 machines I installed a separate new  local copy of Pegasus,  this worked fine

Next

from the new local copy I was going to try to reconfigure the setting

so it could assess the network files but of course you cant do this

because the pconig and mbxmain won't run on a 64 bit machine so that

option is out

so I guess I am asking any ideas on how to get Pegasus 4.61 to work over a network on 64bit 

Note 4.52 was working fine with our system

The setup is

Remote drive\Pmail\Programme( for the programme files )

Remote drive\Pmail\Mail  ( for all our mailboxes and public folders )

Ideas would be most welcome

I am facing the same problem. I am running Pegasus 4.61 on Ubuntu Maverick via Wine. It is an AMD64 type of architecture. The program crashes every single time I try to run it delivering the same error message as above.

>  First well done the the beta team for all the work on the upgrade  
>  
>
> Maybe I didn't post this in the correct place
>  
> But I have come across a small problem I have not  been able to work around.
>
> OK well as I described yesterday the 4.61 worked well when installed last night on 32 and 64 bit win 7
> This was as stanadlone machines  where files were on the local drive.
>
> Today I upgraded a small office network.Here the files, both programme and mail folders are on a file server.
> All 32 bit systems work as expected.
>
> However our 64bit machines ( We have 3 ) both win 7 (2) and visa (1) have an identical  problem.
> After upgrade on the file server each local machine ran the wssetup file to set the parametes

Try doing this manually to create the shortcut and make sure that the users have all rights to their mail directories on the server.

>
>  However when you try to start the progamme over the network, ( put in your username and wait etc.) it gets to a point where it is above to
> load ( we have pubic folders so this take a min or two). the programme then crashes with the single windows error message .

Might also get a copy of the mini-dump file extension so that you can send in a crash report.  Michael will analyze the file to pin-point the problem.
http://community.pmail.com/files/folders/community_add-ons_for_pegasus_mail/entry12763.aspx

>  ( Pegasus mail for windows has stopped working....A problem caused the progamme to stop working correctly....windows will close the
> programme ....and notify you if a solution is available )
>

>  Next on the same 64bit win7 machines I installed a separate new  local copy of Pegasus,  this worked fine
>
> Next from the new local copy I was going to try to reconfigure the setting so it could assess the network files but of course you cant do
> this because the pconig and mbxmain won't run on a 64 bit machine so that option is out so I guess

First of all get a copy of DOSBox and you can run pconfig.exe to set the home and new mail directory.  When you do make sure you are using the UNC \\server\share\path\~n format instead of the drive_letter:\path\~n format.

This sounds similar to what I encountered when trying to open Pegasus Mail (installed on an XP machine) from my Windows 7 (64bit) machine: I couldn't succeed either and wasn't able to solve this while it worked properly when switching machines (using Windows 7 as server for an XP client). I've no idea what could be causing this ...

So what would the suggestion be for setting up Pegasus Mail in a "shared executable" network environment that has both 32-bit and 64-bit workstations?  Let the 32-bit users use the shared copy, and do standalone installs using the shared mail folder for the 64-bit users?  Right now we are all currently 32-bit but I have a couple 64-bit machines coming in a few weeks.

-=Glen

[quote user="Glen Jackson"]So what would the suggestion be for setting up Pegasus Mail in a "shared executable" network environment that has both 32-bit and 64-bit workstations?[/quote]

I have absolutely no idea, I guess someone needs to figure out the underlying issue. Could it have something to do with SMB 2 (not that I understand a single bit of how this exactly works, but some of you system admins might do, perhaps)?

Hi there,

I have also installed Pegasus 4.61 on our networked system. We were using 4.52 successfully in a mixed environment of Windows XP, Windows 7 64 bit and Windows 7 32 bit.

We are sticking to the Windows 7 model, because it works and is a lot more stable (and less resource hungry) than Vista.

Our File Server is a QNAP (Linux based) and handles all our data, videos and music for all our devices (computers, media streamers etc)

All the computers running Windows are connnected to the Server with mapped drives (e.g. M:, N:, S: etc), and these are mapped to the the explicit server internal IP address (e.g 192.168.1.11), and therefore do not need to rely on the vagaries of DHCP! 

For example, we have our all our Pegasus Mail in a folder called Pegmail in a Network Folder called SharedDocs.  Therefore the path, as seen by Windows for everything to do with Pegasus is S:\PegMail. The Mapped drive S: maps to \\192.168.1.11\SharedDocs.

When I did the upgrade from 4.52 to 4.61, I simply told the install program where the Pegasus Programs Folder was (e.g. S:\PegMail\Programs). I did not re-run the workstation install as all our computers have identical maps. The install was done from a Windows 7 Ultimate 64 bit partition on my own main workstation. All other Windows 7 machines, (32 bit Utimate) ran the new 4.61 Pegasus without any further setup. I have also tested this on a Windows XP Pro partition and there is also no problem and no need to run the wssetup program.

Things to watch out for with Windows Networking:

1. Only XP Pro, Windows 7 Pro and Ultimate can correctly store network user id and passwords.
2. You need to have the server address added to your local Intranet settings under Internet Options, (this shows you how embedded Internet Explorer is with the OS even if you don't use it!). This sets the correct security permissions for the internal IP address used by your server, and prevents the publisher cannot be trusted message appearing every time you run the program from the Server
   
3. Check that the user id you are logging in with (to the File Server) has the correct read/write permissions set on the Server for the folder you have Pegasus installed in.
4. Avoid the Windows Homegroup/Workgroup mapping method (e.g. Server Name\SharedDocs) as this requires a Browse Master to resolve the IP address from the name and Windows Networking is notoriously slow in resolving this if one Browse Master goes away. Although we have an "always on" Server as the Browse Master we still use explicit IP address for all maps and never have any problems with Pegasus or other networked apps we use.
   

I hope that some of this may help you and point you in the right direction, post back with your progress.

 Update:

Also checked this with Windows Vista Ultimate 32bit and again, no problems or error messages.