[quote user="K. Baumann"]

Most computerproblems reside between keyboard and bureauchair ;-) 

[/quote]

LOL. This kind of error is known as PEBKAC - Problem Exists Between Keyboard And Chair. I think you should try and blame your partner, children or pet rather than admit to any mistake on your part!

Ok Michael, I will go to start a new thread named "performance and compressing folder".

Thanks a lot.

Miguel

You are great!  Now I'm happy!  I got the desired result by following your instructions to reach Formatting and use of styling ...  Then I removed checks from ALL the boxes.  Eureka!  It worked.  Thank you.

[quote user="DragonsDream"]edit: I'm thinking what has happened is that my FOLSTATE.PM file has been overwritten with a new version that only lists my new mail folder but none of my previous ones. is there any way to reconstruct the file?[/quote]

My FOLSTATE.PM only contains tray information, it's very unlikely that it has any effect on reading folders. It's more likely HIERARCH.PM and/or CACHE.PM.

[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.




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

[quote user="PaulW"]Can you get a session log of this - Tools / Internet options then check the box 'Create Internet session logs'.[/quote]

And don't forget to read the associated help entry for advice ...

Thanks for confirming that it can be duplicated. 

I was hoping that there was a setting that needed to be changed...guess not. 

My users haven't complained about it. Overall, their responses to the new version have been positive.

Tony

[quote user="Grumpy Jeff"]Is there a list of known issues (aka a bug list) to save reporting what you already know?[/quote]

No, there isn't, sorry. And to be exact: I don't know how many people see exactly this runtime error you encounter, but Pegasus Mail usually just crashes if doing what you did (runtime error 216 is actually an access violation which is usually converted into a fatal exception; why it occurs this way or the other is beyond my knowledge).

Schlafen Sie gut!

Glad to hear it!

Tom

Glad to hear it!

Tom

I believe you should be able to find that information by looking in the "Copies to Self" folder (if Pegasus is configured to automatically keep copies of all messages sent). If there are many messages in that folder, they can be sorted by Subject, Date/Time, etc. by clicking on the heading of the column in the message listing, to make it easier to locate the message you are looking for.

 Hope this is helpful.

 Jim

Problem solved. I did the installation wrong - so PM did not find its icons...

Sorry for the confusion. PM did a very good job here!

Adio,

Gerd

If someone else has this issue in Win7+, try disabling the  following settings in your network adaptor - helped my performance a hell of a lot:

"Large transfer offload" for Ipv4 and IPv6 if you use the latter.

 See another post I've made on a similar "slow" topic for an explanation.

[quote user="Jonas"]One reference had "Name_Unavailable" in the line.

Many other lines also contain that string. Therefore I have the question if I can remove those lines too.[/quote]

Yes, these are "cached" entries of whatever Pegasus Mail registered before, deleting them doesn't cause any serious issues.

The Adobe manual for Tiff V6 is here: http://partners.adobe.com/public/developer/en/tiff/TIFFphotoshop.pdf   It seems to have warnings about differences that have been introduced. For Pegasus Mail, we need information from the vendor SubSystems on what version they support.

Martin

[quote user="Chester"]Any assistance much appreciated.[/quote]

Doing a might help ...

[quote user="Alar.Pandis@mtk.ut.ee"]Any ideas?[/quote]

Check .

Start with a basic and simple test first. Hit F2 key while in winpmail and then hit Search and when  you see wife name double click on it. If a new message jumps up addressed to wife then you can send to her using that. There are one or more settings in Tools, Internet options, SMTP that effect ability to send to local username. To send, assuming settings are ok, you just put the name used for user on cystem in the To: line of message editor new mail.  For example to send to admin just type that in To: block or if the name  under ..pmail\mail\wife send mail to <wife>.

If you have checked the block to use for all adddresses then mail must go to server. Unchecked local delivery is allowed.

[quote user="KarenM"]Could main file be full and if so could I move or archive it. Has about 600 messages in it.[/quote]

The more important question is the number of message in your new mail folder as ?