WM5 bug found, X51v affected.

**ctitanic** · 09-29-05, 07:49 AM

An article describing the bug and a fix for it have been post at
http://www.pocketnow.com/index.php?a...reviews&id=702

This bug affect all WM5 machines but it only be noticed if the Security Prompt is Set ON in the machine. So far the only device that I know with this setting ON is the Axim X51v.

**psionandy** · 09-29-05, 08:31 AM

Thanks for the article....

Is my understanding of it correct in thinking that
1) It is a problem due to the security features not keeping track of the mui files associated with programs
2) The problem will effect programs that use the mui files for localisations of their code
4) It also stops people using the Brute force VGA method
5) The only way to turn this off (at present) is to use the util that you linked to. There's no way you can do this just using the x51v itself

At the moment it's not a problem for me... but it could be a big one when we get our wm5 upgrades

**ctitanic** · 09-29-05, 08:43 AM

Originally Posted by psionandy

Thanks for the article....

Is my understanding of it correct in thinking that
1) It is a problem due to the security features not keeping track of the mui files associated with programs
2) The problem will effect programs that use the mui files for localisations of their code
4) It also stops people using the Brute force VGA method
5) The only way to turn this off (at present) is to use the util that you linked to. There's no way you can do this just using the x51v itself

At the moment it's not a problem for me... but it could be a big one when we get our wm5 upgrades

Exactly!
I'm not sure if this bug stops other kind of files from been seen by the main EXE. And I'll tell you why. I have run on situations when the X51v is asking me for permission to use DLLs that have been called by a main Executable that already has been "approved" to be use in my device. So that's telling me that we have there the same situation that we have with MUI files. Other files associated with the main application do not inherit the authorization to be used. If you are getting a second prompt to approve those files you won't have any problem. But... Try to image your self the situation when an executable try to launch a process in a dll or in another kind of file and that second file is not approved by the system and it's just ignored in the same way it did with the MUI files. That program will just crash. So... What I'm saying is that may be some of the incompatibilities of programs in the X51v could be the result of this bug. The only way to know it is comparing what programs can be used in other WM5 with not Security Prompt that can't be used in the X51v.

In my specific personal case, I have disabled the Security Prompt in my X51v. I never had that prompt in any of my PPCs before and I don't need to know what program has been "approved" by MS or not. In fact, Tweaks2K2 needs MUI to work properly so it disables this feature automatically. So, Tweaks2K2 users do not need to run the SetSecurity.exe to turn off this buggy feature.

ukemaxxer · 09-29-05, 11:48 AM

Do you know if this bug has any effect on the running of TomTom5, which is the main thing I have bought a PDA for?
Cheers

**ctitanic** · 09-29-05, 12:23 PM

Originally Posted by ukemaxxer

Do you know if this bug has any effect on the running of TomTom5, which is the main thing I have bought a PDA for?
Cheers

I don't know Sir. If TomTom 5 gave you some problems deactivate that option using the tool that I uploaded at my site and try TomTom again, if you still have problems that means that your problems are not relative to this bug.

**ctitanic** · 09-29-05, 12:46 PM

Originally Posted by psionandy

Thanks for the article....

5) The only way to turn this off (at present) is to use the util that you linked to. There's no way you can do this just using the x51v itself

Tweaks2k2 disables this option automatically.

JonMisurda · 09-29-05, 01:42 PM

In the interest of full disclosure are you going to explain what registry key you had to modify?

Jon

**ctitanic** · 09-29-05, 01:55 PM

Yes, I will do it at my site, in the how to section as soon as I can (any time before next week).

**ctitanic** · 09-29-05, 02:00 PM

Originally Posted by JonMisurda

In the interest of full disclosure are you going to explain what registry key you had to modify?

Jon

are you using MUI files in your applications?

JonMisurda · 09-29-05, 03:47 PM

I do use one with my only .NET program, Radar Watch. And only because I just didn't bother to do the res2exe to add the HI_RES_AWARE resource after each compile. I guess with my next release I'll just add that as a post-build step. Which reminds me I need to work on that again.

Besides, "strings -e l" told me everything I needed to know

Jon

**ctitanic** · 09-29-05, 04:03 PM

Originally Posted by JonMisurda

I do use one with my only .NET program, Radar Watch. And only because I just didn't bother to do the res2exe to add the HI_RES_AWARE resource after each compile. I guess with my next release I'll just add that as a post-build step. Which reminds me I need to work on that again.

Besides, "strings -e l" told me everything I needed to know

Jon

that's why I told you that I going to release the info as soon as I have a litle time.

That other solution that you are talking about is too much work for me. I have the MUI in my programs and I don't have to care about any extra step after the compilation.

**ctitanic** · 09-29-05, 04:12 PM

Originally Posted by JonMisurda

In the interest of full disclosure are you going to explain what registry key you had to modify?

Jon

Ok, you asked for... and here it goes

http://www.tweaks2k2.com/portal/foru...&showtopic=189

User Name		Remember Me?
Password

X50 / X51 Accessories - Axim X50 / X51 Accessory Discussions