" mce_src="">hello,

I just got the following error after upgrading from 4.41  to 4.51 when I try to start the program. the startup-window's latest status is "restoring desktop layout ...", where it crashes

I am running pmail under NT4 on a socket-7 board gigabyte ga-5ax, K6-3-550 cpu.

I solved the problem with using the old iconv.dll from version 4.41

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date:  7/10/2009
Time:  5:27:47 PM
User:  N/A
Computer: 
Description:
Faulting application winpm-32.exe, version 4.5.1.0, faulting module iconv.dll, version 1.13.0.0, fault address 0x00013e50.

.Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 77 69 6e   ure  win
0018: 70 6d 2d 33 32 2e 65 78   pm-32.ex
0020: 65 20 34 2e 35 2e 31 2e   e 4.5.1.
0028: 30 20 69 6e 20 69 63 6f   0 in ico
0030: 6e 76 2e 64 6c 6c 20 31   nv.dll 1
0038: 2e 31 33 2e 30 2e 30 20   .13.0.0
0040: 61 74 20 6f 66 66 73 65   at offse
0048: 74 20 30 30 30 31 33 65   t 00013e
0050: 35 30 0d 0a               50..   

Computer specs:

Mainboard : Asus P5A-B
Chipset : ALI M1541 Aladdin V/V+ AGP System Controller
Processor : AMD K6-III @ 401 MHz
Physical Memory : 320 MB
Video Card : NVidia Riva 128/128ZX
Hard Disk : SAMSUNG (20 GB)
Hard Disk : SAMSUNG (20 GB)
DVD-Rom Drive : Memorex DVD16+/-DL4RWlD2
DVD-Rom Drive : SCSIVAX DVD/CD-ROM SCSI CdRom Device
Monitor Type : Envision ENVISION - 16 inches
Operating System : Microsoft Windows XP Professional 5.01.2600 Service Pack 3
DirectX : Version 9.0c 

Virus and spyware free

====================

Anyone else run into this yet ?

Hi magi135,

after having installed PM 4.5.1 (over the previous 4.4.1) on my computer (still WIN 98 !!) I encountered an equivalent crash when trying to start the Program. Since it concerned the module iconv.dll in the Pmail folder, I tried to replace that library by the old iconv.dll 1.9.0.0 (892.928 bytes), luckily found in my previously saved zipped installation - that did the trick for me! In the meantime, I could not detect any drawback caused by this while working with PM4.5.1.

Kind regards

Klaus

Thanks will give that a try.

If you can identify the problem message, I would really like a copy to do forensic analysis on it. Please send the copy to irelam@telus.net, with the message attached, thank you

Martin

[quote user="magi135"]

Faulting application winpm-32.exe, version 4.5.1.0, faulting module iconv.dll, version 1.13.0.0, fault address 0x00013e50.

[...]

Anyone else run into this yet ?
[/quote]

Unfortunately this information doesn't help a lot: The given address lies outside of any module used by Pegasus Mail (including ICONV.DLL) - and I also wonder how it can happen on Pegasus Mail's startup - unless you're using preview mode which automatically opens a message causing this (ICONV is used for charset decoding only). For locating and fixing this issues two things would be helpful:

1. The message which may be causing this so we can duplicate it (I'm the one who compiled the current version of ICONV.DLL);
2. A stack trace preferrably created by my minidump extension (you may need to use the stand-alone mode if it crashes so hard that the extension isn't executed properly, see the extension's ReadMe/Help text). If using it please do not send the resulting report to the given ("beta-reports") address but instead to my private email address (contained in the ReadMe and Licence files).

[quote user="Klaus Seguin"]

iconv.dll 1.9.0.0 (892.928 bytes), luckily found in my previously saved zipped installation - that did the trick for me! In the meantime, I could not detect any drawback caused by this while working with PM4.5.1.

[/quote]

Well, the new version of ICONV.DLL is the most current one (created by the libiconv maintainers) and provides some fixes (included by me) for Asian charsets which frequently fail to decode because of obvious confusion about the proper names of Asian charsets (don't know who's at fault here, though: the libiconv team or the (email) message creators).

Hi Michael -

sorry I didn't look into the forum earlier.

I've just created a crash dump report and sent it to your private eMail as wanted - hope it helps.

Kind regards

Klaus

Michael -

just one additional thought, as I've looked on the libiconv website just now: As of July 2nd, there exists a release 1.13.1. Couldn't that be possibly a bugfix to the previous release 1.13.0 causing all the trouble?

Weird, probably, but one never knows (I don't, that is...).

Kind regards

Klaus

[quote user="Klaus Seguin"]

Hi Michael -

sorry I didn't look into the forum earlier.

I've just created a crash dump report and sent it to your private eMail as wanted - hope it helps.

Kind regards

Klaus

[/quote]

The crash dump shows that it's an issue with IConv.dll being compiled for Pentium Pro CPUs, hence it fails on older CPUs: I've now re-compiled it using the latest version (1.13.1) for plain Pentium CPUs hoping people don't use even older ones.

[quote user="idw"]

The crash dump shows that it's an issue with IConv.dll being compiled for Pentium Pro CPUs, hence it fails on older CPUs: I've now re-compiled it using the latest version (1.13.1) for plain Pentium CPUs hoping people don't use even older ones.

[/quote]

Michael, thanks much, also for your answer to my other message on this subject.

This PC has an AMD K6-2-450; the other one has an Intel N270.

What category are they in, vis-a-vis the Pentiums you mentioned?

I'll try this new DLL; have been using the one from the Pegasus 4.41 as someone suggested.

Sheldon Isaac

[quote user="sheldonisaac"]

[quote user="idw"]The crash dump shows that it's an issue with IConv.dll being compiled for Pentium Pro CPUs, hence it fails on older CPUs: I've now re-compiled it using the latest version (1.13.1) for plain Pentium CPUs hoping people don't use even older ones.[/quote]

(some snippage)

This PC has an AMD K6-2-450; the other one has an Intel N270.

I'll try this new DLL; have been using the one from the Pegasus 4.41 as someone suggested.[/quote]

Your new IConv.dll (973258 bytes?) works fine!

PM 4.51 starts up without any problem on this computer; I see now that the OP? has an ASUS MB similar to mine, which is a P5A from about 1999?  The 450MHz AMD cpu is also from about that period. It runs Windows 98SE.

Both your previous  IConv.dll and the new one work OK on the Acer Aspire one with Atom cpu and Windows XP.

Thanks again,

Sheldon

[quote user="sheldonisaac"]

[quote user="idw"]The crash dump shows that it's an issue with IConv.dll being compiled for Pentium Pro CPUs, hence it fails on older CPUs: I've now re-compiled it using the latest version (1.13.1) for plain Pentium CPUs hoping people don't use even older ones.[/quote]

(some snippage)

This PC has an AMD K6-2-450; the other one has an Intel N270.

I'll try this new DLL; have been using the one from the Pegasus 4.41 as someone suggested.[/quote]

Hello,

I just installed the new PM 4.5.1 on computers with 2 different chips and I have the same problems. One is an Intel Core 2 Duo and the other an N270 both run on OS XP.

I tried using the replacement for the IConv.dll suggested above on the CPU with the Intel Core 2 Duo, but that did not work. I saved the error report if that is useful. Do you have any suggestions. I am cut off from my mail!

Many thanks, Mjo

[quote user="Mary Jo Figuerero"]

Hello,

I just installed the new PM 4.5.1 on computers with 2 different chips and I have the same problems. One is an Intel Core 2 Duo and the other an N270 both run on OS XP.

I tried using the replacement for the IConv.dll suggested above on the CPU with the Intel Core 2 Duo, but that did not work. I saved the error report if that is useful. Do you have any suggestions. I am cut off from my mail!

Many thanks, Mjo

[/quote]

Does the error report mention an invalild instruction error somewhere like shown in another thread or do you get a different error? As posted in this thread the replacement library should at least work with the N270. Is your crash caused by IConv.dll at all? I can't really believe it is as the Intel Core 2 Duo is said (search Wikipedia to learn about it) to be a successor of the Pentium M model (being a successor of the Pentium Pro) which can already work with the original IConv.dll distributed with Pegasus Mail 4.51; and the notebook I'm typing this on (and compiled the library with which wouldn't have succeeded otherwise) actually uses a Pentium M. I'm afraid we have a different issue here ...

[quote user="idw"][quote user="Mary Jo Figuerero"]

Hello,

I just installed the new PM 4.5.1 on computers with 2 different chips and I have the same problems. One is an Intel Core 2 Duo and the other an N270 both run on OS XP.

I'm afraid we have a different issue here ...

[/quote]

If my assumption is true it might help to get a crash dump, see my previous reply.

Michael,

I feel a bit lost. I downloaded and tried the minidump (both versions), as indicated. Still crashed and nothing according to the indications in the readme file. I saved the error report and will mail them to your other address. Meanwhile I'd love to reinstall the previous version of pmail, ut cannot find where to download previous versions.

;o), Mary Jo

[quote user="Mary Jo Figuerero"]

(parts snipped)

Meanwhile I'd love to reinstall the previous version of pmail, ut cannot find where to download previous versions.

;o), Mary Jo [/quote]

http://community.pmail.com/files/folders/pegcur/entry12.aspx

Saved  Many thanks! ;o), mjo

[quote user="Mary Jo Figuerero"]Saved  Many thanks! ;o), mjo
[/quote]

I'd still like to know what your issue was: Crashes are a serious issue

which need to be fixed as they certainly will re-occur - if not for you

then for somebody else (and in fact I've already had some mail exchange with someone encountering a very similar issue). To ensure the IConv.dll

would be causing it you could take the respective library provided with PM 4.41 and

replace the newer one of PM 4.51 with it - if it fixes your crash

(which I still don't think, though) I would need to create another

compatibility version for even older CPUs than the plain Pentium. Any chance you may take the time (and hassles) to try? You could install into a different directory for testing if you don't want to impact your current version again ...