Diamond + mToken 4.3.0 (SPACE key is not working) - Touch Diamond, MDA Compact IV Themes and Apps

Hello,
Can anybody tell me why on my Diamond (ITA original rom, 1.93.408.3) when I open a ssh session with mToken and I use the extended keyboard (the other keyboards don't work at all) all the keys are working except the SPACE key? I tried even to change the kind of terminal (vt100 and xterm) but I didn't get any success with the space key.
Any hint is appreciated

Well I can't help you with why on diamond.
But on TP standard rom or RoMEOS flashed doesn't work at all. Neither software keyboard neither hardware.
What's more funny i think enter key works and yes so does delete.
Before that on wizard/hermes with any rome i haven't seen this problem.
Maybe you can use pocketputty for workaround.
http://www.pocketputty.net/
And mToken 4.3.1 isn't any better. Same not working functionality.

I already tried pocketputty, but while it supports the Diamond extended keyboard fully on the contrary it doesn't support the 80x25 screen format.
So I can't use some linux commands like the simple "w" for example.
I hope somebody can help me with this mToken that despite the not working SPACE key it seems to be the best ssh client that I've ever tried on windows mobile.

On mToken forum, there is a post about problems with XT9.
In my case with TP the sollution worked i can use either SIP or HW keyboard. Applying that registry fixed everything.
Ofcourse alwayws backup before trying anything so you can return previous settings if things go wrong:
Link to the post: http://www.choung.net/db/?q=node/463

jxl69 said:
On mToken forum, there is a post about problems with XT9.
In my case with TP the sollution worked i can use either SIP or HW keyboard. Applying that registry fixed everything.
Ofcourse alwayws backup before trying anything so you can return previous settings if things go wrong:
Link to the post: http://www.choung.net/db/?q=node/463
Click to expand...
Click to collapse
The link is down. Any chance you still have the info for the registry fix?

You're in luck
I've just flashed my TP and i have needed the "fix" again.
Since the site was down i've managed to find me what needs to be changed.
I've created 2 cabs one which disables xT9 and another that enables it. Se attached files.
Here's the registry changes for both cabs:
Disable XT9:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
"Ime File"="compime.dll"
"Keyboard Layout"="00000409"
"Layout Text"="COMP IME"
To return default setting or just reenable xT9:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
"Ime File"="\windows\eT9ime.dll"
"Keyboard Layout"="00000409"
"Layout Text"="eT9 IME"
Hope this helps you

jxl69 said:
You're in luck
I've just flashed my TP and i have needed the "fix" again.
Since the site was down i've managed to find me what needs to be changed.
I've created 2 cabs one which disables xT9 and another that enables it. Se attached files.
Here's the registry changes for both cabs:
Disable XT9:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
"Ime File"="compime.dll"
"Keyboard Layout"="00000409"
"Layout Text"="COMP IME"
To return default setting or just reenable xT9:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
"Ime File"="\windows\eT9ime.dll"
"Keyboard Layout"="00000409"
"Layout Text"="eT9 IME"
Hope this helps you
Click to expand...
Click to collapse
You are a life saver! Thanks I really appreciate it! Works like a charm.

Thanks jxl69, the cabs also works on a BlackStone (of course

Related

Fixing German QWERTZ keyboard for O2miniS with O2 EnglishROM

Fixing German QWERTZ keyboard layout for O2 miniS with English ROM installed is very simple.
Many nomally use AEKmap, but this is not allways fine for somebody.
Now we need a small registry hack.
1. Use a registry editor like total commander.
2. Go to \HKCU(HK Current User)\ControlPanel\Keybd\Locale.
3. Change the value of the key "Locale" from "0809" to "0407". "0407" is the locale ID for Standard German. You can find other Locale ID suitable for you at: http://www.microsoft.com/globaldev/reference/winxp/xp-lcid.mspx.
4. Do a soft reset and enjoy. All the keys and symbols have fixed right.
Hope this help someone.[/list]
wooooooow!!
That's good.
I will try that NOW
Well I don't see any Locale folder under Keybd...
What next?
cizake said:
Well I don't see any Locale folder under Keybd...
What next?
Click to expand...
Click to collapse
Dear cizake,
"Locale" is not a folder. This is a key, locating under the folder "Keybd". We have to change the value of this key. Check the path again, pls.
Hope this help.
I cannot change the vaule, I use PHM Registry editor, after soft reset, the vaule back to 0804,not 0407.....why??
sim1 said:
I cannot change the vaule, I use PHM Registry editor, after soft reset, the vaule back to 0804,not 0407.....why??
Click to expand...
Click to collapse
I have no idea. I am using total commander. This is free at here http://www.ghisler.com/pocketpc.htm.
1. Check your programs that running each time you start windows at \windows\startup\. If they change keyboard settings.
2. After changing the registry key value. Do the soft reset by this way: Hold down the power button for ~5 seconds. When being asked to turn off the device, tap Yes. This will completly turn off the device and save the changes in registry. This method may different from taping the stylus to the reset hole.
I dont see Locale either .... would really appreciate any help on changing :
a) software keyboard layout and
b) hardware keyboard layout
pencilcase said:
I dont see Locale either .... would really appreciate any help on changing :
a) software keyboard layout and
b) hardware keyboard layout
Click to expand...
Click to collapse
Check the path again:
The folder: \\\Registry\\HKCU\ControlPanel\Keybd\
The key: Locale.
If you do not see the folder. Create a new folder "Keybd", then create a new key with name "Locale".
I thing this may help.
This is a fix for hardware (real) keyboard only.
Cool. For AZERTY keyboards the value is 040C. My ROM version didn't have Locale value in the HKC\ControlPanel\Keybd, I had to create one myself. It has to be String value, not DWORD. Thank you for great hack.
GUYS! YOUR ARE GREAT!!!
Works perfect with Eng for Russian Keyboard (Russian code is 0419). Now I can switch between Russian and English
yes can confirm 0809 works a treat for english keyboard, thanks!!
Sweet!
Yup! works a treat. Have now changed WM 5 from french to English (which gave me the english keyboard problem) and thanks to you changed the keyboard layout to French. Brilliant. By the way, where could i get the new qtek 9100 ROM 1.6 WWE?
Sorry, but this nice solution is not working after upgrading to 1.6.7.1
This entry in the Registry does not exit anymore. I can only find things whichhave the value "e0010409" for english keyboard and i want to get back my german one. Has anybody that number?
Check again kbaasch
Check the path again:
The folder: \\\Registry\\HKCU\ControlPanel\Keybd\
The key: Locale.
If you do not see the folder. Create a new folder "Keybd", then create a new key with name "Locale".
I thing this may help.
This is a fix for hardware (real) keyboard only.
my keyboard is now ok
oainot
Its works fine, thanks.
I have T-Mobile MDA Vario from German, I have flashed it with ROM: 1.6.7.1 WWE
And, with reg file my keyboard is now ok.
Code:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\ControlPanel\Keybd]
"Locale"="0407"
MrBuz
Great, stunning solution! Thank you! This is absolutely BRILLIANT !
I have 1.6.7.1 WWE and Russian layout works perfectly...
But the English now lacks a "comma", as the combination "dot+comma" is assigned by the system to switch between layouts.
Is there any solution to re-assign the layout sequence, or to assign "Shift+comma" to print comma (currently Shift does not have any influence on that button on my system...)
Awesome solution.Works like a charm. Can not imaging a better solution. A++++
Fixed permanently?
Cool!
Will this work after hard reset? If not, anyone dare to create a new ROM so that we can flash it and fix it permanently?
Rocks!
hello
I have qwertz keyboard and italian rom
which value i must insert?
tnks a lot
i can try to insert locale key, but when i do soft reset locale it became a directory...
why? i don't understand
the page where i sow the references is because the other doesn't work
http://www.microsoft.com/globaldev/reference/win2k/setup/lcid.mspx

Sym Key not working? Here's the solution...

Okay, this prob got me for some hours:
I updated my Universal from German ROM to latest (original) WWE ROM. After that, I tried all known hacks to put the hardware-keyboard to QWERTZ instead of QWERTY.
HKCU\ControlPanel\Keybd\Locale=0407
HKCU\keyboard layout\Preload\Default=e0010407
HKCU\keyboard layout\Preload\1\Default=e0010407
HKLM\SOFTWARE\OEM\Qwerty\Layout=0x20407
Unfortunately, after that, the SYM-Key wasn't working.
Now after trying various things and thinking a lot, I guess I have the answer.
It seems to be important that the first 3 values don't get changed. The Qwerty\Layout is the locale for the hardware keyboard driver and if you change the locales for WM5, too, I guess the scancodes get converted once more and so the SYM-Key doesn't work. After changing the first 3 registry keys back to 409, now everything works fine.
Cheers,
-mARKUS
I did similar modifications to my registry to make it work well with my italian keyboard and I ended with the same problem: the SYM key doesn't work.
I'll try with your solution. Thanks for sharing it!
In your original Ext_ROM, there should be a file called Signed_GER_KB.CAB. Just run that, then the KB is back as it should be. No need to modify the registry. The sym key is controlled by the sym.txt file in your windows folder.

problem italian (qwerty) keyboard

hi,
i have a imate pda2k with qwerty keyboard.
wm6 doesn't recognize special characters like "." "@" "," and others.
with my old wm2003 i had to install after an hardreset a special cab to solve the problem.
i have tried this cab also in wm6 but without results.
does a fix exists ?
ok i have found the right solution before posting my question here,
http://forum.xda-developers.com/showthread.php?t=365832&highlight=qwerty
but i forgot to tap "exit" at the end of registry edit. so i have not saved the new registry key.
sorry

Help: Using a herald ROM on a Wing:WIFI problems

My WIFI doesn't work, and I need some help fixing it.
I own a T-Mobile Wing, and decided to change the ROM. I've tried a couple, and so far the the best one for me is the Throttle Diamond II. The only problem is that this is a Herald ROM, not a Wing ROM.
I know that the differences between these two devices is what causes my WIFI problem, and that the fix involves changing the registry. I even found instructions for doing that. However, that fixed nothing, and I don't know why.
Here's what I did:
Changed "HKEY_LOCAL_MACHINE \SOFTWARE \HTC \CommManager \WLAN" to
"HKEY_LOCAL_MACHINE \SOFTWARE \HTC \CommManager \Windows WLanMgr.exe"
Under that location, I changed Device Name to "{98C5250D-C29A-4985-AE5F-AFE5367E5006} TNETWLN1" and Default to "\Windows\ctlpnl.exe"
And here's the exact instructions I was following:
Change "HKEY_LOCAL_MACHINE \SOFTWARE \HTC \CommManager \WLAN= "Windows WLanMgr.exe " "DeviceName" = "{98C5250D-C29A-4985-AE5F-AFE5367E5006} TNETW12345"
the end of this long String is the WLAN-Adaptername of the Device.
just change in this Example "TNETW12345" into "TNETWLN1"
-Step 3: (Fixing Wi-Fi setting launch issue) **Thanks for phatman81’s post for this fix.
Change "HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CommManager\WLAN\ Default:"
\Windows\WlanMgr.exe --> \Windows\ctlpnl.exe
Click to expand...
Click to collapse
This made no difference. One thing that may be causing problems is that I'm not sure if the device name is right, but I can't find how to figure out what the device name really is, and I wouldn't be surprised if that's not the only problem.
I'm sorry if the solution to this problem is really obvious, but I'm just not seeing it, and can't find anything to fix it, no matter where I look. Could someone please help me?
also have a problem with my wi-fi switch. it doesn't work. also tried the registry fix, but that didn't seem to fix anything. will reflash to a newer version tonight and post back.
I fixed it, the solution was something really obvious that I should have been able to find before I made this thread. I just needed to install the 10 button comm manager, then the registry changes could fix the problem. RussianBear, here's a link to the cab file for the comm manager, thanks to Nyer78 for uploading it.
http://forum.xda-developers.com/attachment.php?attachmentid=48832&d=1188607222
may be you can try as follow
1:chang Device Name to "{98C5250D-C29A-4985-AE5F-AFE5367E5006} TNETWLN1
2:locat HEKY_LOCAL_MACHING\CONTROLPANEL\WIFI\WRLSMGR
CHANGE "REDIRECT" AS "\WINDOWS\COMMMANAGER.EXE"
I ALSO USE A WING,AND I DONE THE WORK ABOVE ,IT'S WIFI IS ALL OK

Keyboard problem in 6.5

Hi, guys. I am trying to cook my own ROM for wm6.5. The Problem is I can't change the default keyboard to another keyboard input. Editing the reg in [HKEY_CURRENT_USER\ControlPanel\Sip] to another keyboard input make the ROM not bootable. Installing SIPchanger also not solve the problem. Is there any other way to forcefully change the default keyboard input??
You do it by changing the guid in the defaultIM reg key; you also need the clsid for the new sip. Let me say, I had a ***** of a time getting it to work w/ resco keyboard (worked fine w/ fnkbd). The key is to set the defaulIM key during customization, otherwise the rom won't boot. The skin files need to be installed before that key is loaded. With fnkbd, you'd just get an error when the welcomehead appeared (annoying) if the defaultIM was cooked in. But with Resco, you never see your bloody welcomehead. I'm not eve sure that the read letters appear on the splash screen.
I set the defaultIM during customization with a mortscript:
Code:
RegWriteString("HKCU","\ControlPanel\Sip","DefaultIM","{A070BE16-AD56-11D3-BC77-00C06C512035}")
It runs after the skin files are installed (also with a mortscript during customization). Again, it's important that the clsid for the keyboard is cooked in, otherwise the rom will brick when you soft reset it. Once the defaultIM is set, you don't need a sipchanger, and reboots are quick
Edit: it's always a good idea to put in all relevant info if you really want help. What keyboard? What sipchanger? What's your package look like? Did you make it yourself? Did you do it manually, or use a cab-2-oem type tool, which probably crapped everything up? My guess is that you used cab-2-oem, but that there was a setup.dll that installs the clsid for the keyboard, and you didn't get that reg key, so now your package doesn't work. I suspect this because it's weird that sipchange isn't working for you-this is probably because you don't have the clsid (you put the shortcut in Startup, right?). Cab-2-oem type deals are not a reliable method to make packages.

Categories

Resources