Could you provide a brief answer as to why?

Just to make clear - I’m a npp user as you are, so my answer on this is just my assumption nothing official.

In general there isn’t much benefit of having a 64bit over an 32bit version of a program. Memory allocation benefits most
of it but for most “normal” users memory allocation beyond 4GB isn’t important. But making a program work for both
environments isn’t trivial all the time especially when using 3rd party libraries like scintilla which of course must then also support
64-bitness. From npp repository we can see that work is in progress but I can’t say when it is done.

From my point of view I would love to see a warning, in whatever way, if someone edits a file which is assumed to be in system32
but current loaded is different.

Cheers
Claudia

Hello @Fisher-Chen ,

What is your Wine prefix - 32 bit or 64 bit?
What version of Windows is your Wine configured to emulate?

Try Wine in XP mode with 32bit prefix.

BR,
Pavel

Hi Claudia,

We are doing some migration at the moment from W2k8 to W2k12 so we have domain controllers running both OS.
I was also confused when I saw the GPO, that other applications do promt for UAC.
I hope you find something :)

Best regards
Jesper

Hi Guy,

sorry for answering so late - I had a day off - mostly bicycling and enjoying the nice weather.
I thought since upgrading scintilla this lib wasn’t working anymore!!??
Because of that I didn’t test it - I will give the original code a try and see what it is complaining about.

Will comeback on this.

Cheers
Claudia

I prefer 4, replacing by space.

@Almir-Abrarov, I meant changes which were (or not) done in npp between version 6.5 and 6.9.
As I’m still confused about the current discussion, may I ask you to answer the following question/assumption?

If you add the comment to the perl source file

in npp 6.9 -> OK detected as windows-1251 in npp 6.5 ->NOT OK detected as ANSI

Is this what we are talking about?

Cheers
Claudia