Re: PSPad unicode 5.0.2 (341) English

ejfield:

I'm an getting occasional "Application Error" dialog when I exit PSPAD, first noticed it in 339. It's not very repeatable unfortunately. I cant work out how to paste an image, but it says:

Exception EAccessViolation in module PSPad at 000000000011E499. Access violation at address 000000000011E499 in module 'PSPad.exe'. Read of address 0000000700000000.

I'm using the 64bit version. As far as I can tell, it doesn't do any harm.

Can you tell me what exactly are you doing? Step by step? I need to simulate your problem.

Not really, No! As I said, it's not reliably repeatable. It only happens sometimes, when I click the 'X' top right to close PSPAD. Sometimes I just open a file, look at it, make NO changes, close it again, then I get the message. Other times I don't.

I started with 501en, then copied over 502b341, then 502b341x64.

hi
same mistake, same error for me.
When i use "project", i have not this probleme. Even if i m not sure if this is always the case.

I m Under Windows 10 64 bit, VMwareregards

64b version of PSPad is still not stable as 32b version.
There is only one reason why to use 64b version - when do you work with big files (hundreds of MB). In any other cases I suggest you to use 32b version. 32b version isn't more slow on 64b operating system and doesn't bring any disadvantages.

OK, fair enough, I'll go back to the 32b version.

It was useful to know that I'm not the only one though!

Thanks for everything.

It doesn't mean I won't try to fix this problem. It was only explanation why used / don't used 64b version

just for adding one thing : the error doesnt occured if i do :

* click "parametres"
* click "parametres du programme"
* OK

regards

I think i will keep the 64b for big files

Hi Jan, WSH not working after update. In settings it apeared as strikethrough text

Hello

WSH doesn't work in 64b version. In 32b version it should work.

i see. it works in 32b. thank you