Is it possible to replace the gwes.exe of my nk.bin?

Good job

Thank you! And thank everyone here for the help

Perhaps we could try out this method of switching gwes themes on other devices? And maybe write out a guide (with plenty of disclaimers of course, I wouldn't be doing this on a device that is brickable)

I'm happy to publish it in the support section

C:Amie, is there:
1-any performance difference to using the XP theme for CE versus the normal one? Kinda similar to Win32 having the theme service? Let’s assume all conditions are equal and you’re just having two different ROM images and the only difference is that?
Also :
2-what is the proper term for the XP theme for Windows CE?

1. Of course, the redraw is more complex
2. Luna

Oh I didn’t know the same term existed for CE devices too. Thank you!

Last question that’s a bit unrelated ..
Remember the XP style start menu logo introduced in CE 4.0?

Anyway, the initial screenshots of CE6 show the same logo. But my thin client has a Vista style logo.

Did the icon get changed in an R1 or R2 release? I can’t figure out when this occurred. Not sure if you know

I can tell that the CEPC is a tiny bit less snappy with the XP-like theme, but it's completely negligible

I’m actually the opposite. I’d want the original theme. My thin client has Luna - an olive green version.

It's all been running fine, though there's one strange quirk that I've noticed: After closing any of the Softmaker programs, MilkyTracker or ScummVM (though this sometimes also happens to other applications), the window disappears as usual, but the program's process runs in the background for 10-30 seconds at close to 100% CPU usage, causing the system to hang for a while. This wasn't happening with the default gwes.exe.

Any ideas perhaps?

edit: I renamed my Windows directory to Windows 2 and made a new Windows directory with just gwes.exe in it and rebooted. The issue is now no longer occuring! So it must be loading some DLL that's causing this!

Edited by I dunk for bananas 2023-01-14 3:44 PM

Fixed! The culprit seems to have been a certain DLL meant for debugging. It's gone now