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

I'm trying to get the XP-like sample skin to work, and to do that I'd have to replace the default gwes.exe of my image with the one that has the skin (which I have available). Now it seems like it's completely impossible to replace modules in an image (with binmod or whatever tool), is this true? Is there perhaps another way to load my gwes.exe instead of the default one? :/

It is certainly possible as CmoneX managed it with the MP900 custom ROM. Rich might know more. I don't think I have seen it done on a CE 5 bin before mine.

Was it maybe done via .mui renaming? I wonder if there's a way to contact her

I don't think that she wants to be. Like I say, Rich can probably advise, he's made custom ROMs

Is this for your x86 or MIPS 5.0 device ?

It's for the x86 device!

Try this https://www.hpcfactor.com/forums/forums/thread-view.asp?tid=2280&sta...

Well wouldn't you look at that:
I just copied my XP style gwes to the internal hard drive and changed the init key to specify its path and it works!

Sadly for some reason, this breaks TextMaker and PlanMaker
What could possibly be causing that..?







Attachments
----------------
xpstyle.jpg (93KB - 0 downloads)
softmakererror.jpg (76KB - 0 downloads)

Yeah, it looks like it has some general instability now. I'm going to try to add the XP gwes to the image as gwes2.exe somehow, let's see if it's possible

I'm using the binmod tools and a Russian program called BOOOFF. The latter allows me to convert the nk.bin to an nk.nb0, and then make space in it by deleting unused files (wavs from a different sound scheme for example). It lets me load and insert the gwes2.exe. However, after I convert it back to a .bin file, binmod no longer lets me do anything with it. Trying to extract the registry file just leads to this:

c:\binmod>binmod -e "default.fdf" 
BinMod V1.0 built Apr  5 2006 11:32:47 

 

Checking record #363 for potential TOC (ROMOFFSET = 0x00000000) 

Found pTOC  = 0x8189892c 

rom offset = 0x00000000 

Found 'default.fdf' in the image! - located at 8172fba0, size 0000d5f7 compressed 

Error: failed reading reading file 

Error: Extraction failed!

What could I be doing wrong here? Is what I'm trying to do even possible?

In regards to Textmaker in x86:
It was almost unusable when it was copied to a usb flash drive even with me having 512mb ram.

I had to copy the program to the internal storage for it finally to be usable.

So I suspect with skinning inherently causing instability, having Textmaker likely doesn’t help. It’s about the only x86 program I’ve used that’s like this.

Anyway, if you haven’t already I found the following threads for you to peruse since I don’t have the answer to your question :

https://www.hpcfactor.com/forums/forums/thread-view.asp?tid=11437&st...

https://www.hpcfactor.com/forums/forums/thread-view.asp?tid=8725&sta...

https://www.hpcfactor.com/forums/forums/thread-view.asp?tid=10483&st...

https://www.hpcfactor.com/forums/forums/thread-view.asp?tid=17567&st...

https://www.hpcfactor.com/forums/forums/thread-view.asp?tid=5920&sta...

https://www.hpcfactor.com/forums/forums/thread-view.asp?tid=1477&sta...

https://www.hpcfactor.com/forums/forums/thread-view.asp?tid=14703&st...

https://www.hpcfactor.com/forums/forums/thread-view.asp?tid=6272&sta...

Edited by torch 2023-01-10 6:03 PM

Textmaker runs completely fine for me otherwise, so it's definitely the gwes thing I'm trying. Right now I'm trying to add in gwes2.exe with "XIPPort for CE", but the images it produces are too large and don't work at all

I know. The point I was making is it’s a very sensitive program. You with your skin and me when it was on the usb flash drive

That's true!

Could it be that these bin modification tools are all for windows phone and don't work for CE? Because I'm following these guides as closely as I can, and it just produces garbage for me for some reason