[Windows Mobile Apps and Games] RoboWang:
OK, I have updated my work of jpc's mortscript.

I added a speed update check to all scripts.

Your device must be a Rhodium, or I cannot help you with problems, I only have a Tilt 2 GSM.

The requirements are:

You must have Mortscript installed to your device.

You must be proficient in using your device's File Explorer, I recommend Total Commander.

You must be proficient in using your device's Registry Editor.

To decide what scripts to use, you MUST manually check your device's registry for values and locations.

1st, open your reg editor and search for "DispOn" and write down the location. These scripts are dependent upon THAT location.

2nd, using your reg editor, drill down to HKLM\System\State\Phone and see what value is set for Cellular System Available. Write down the value.

Now we look at what script you need.

If your DispOn is in HKLM, you need one of the M scripts.

(Status_M.mscr or CSA_M.mscr)

If your DispOn is in HKCU, you need one of the U scripts.

(Status_U.mscr or CSA_U.mscr)

If your HKLM\System\State\Phone Cellular System Available value is NOT a 4, you will need one of the Status scripts, if it is a 4, then one of the CSA scripts is the one. Using the DispOn info above, just use the CSA or Status version.

I recommend Copying the appropriate script to your phone's SD card or the root of the device, then using your File Explorer, create a shortcut for the script and copy it to the device's Windows\Startup directory.

You can just copy the script to the device's Windows\Startup Directory, but I don't recommend it. You may be changing this file several times in the next few days, and even ONE little error in the Windows directory can make you re-flash the whole danged thing! So if this is what you prefer to do, BE CAREFUL, it's on YOU!

Then just reset and it should be running if you have the right script, again, it's on you to choose wisely, grasshopper. No biggie if you don't have the right script, but it is a small hassle to fix it.

Now, we get to the OC. The scripts set a fairly safe value for the speeds. PLEASE run the script a few days before going Medieval on the OC. Make sure the script works for you before you do, as if it freezes, who knows whether it's the script or the overclock. That is troubleshooting hell, and you will have to start over, anyway. So, be patient!

When you have confidence the script will work for you, and want to start OCing, start slow and run for a day or two, then up the settings. If it freezes up, just change the settings DOWN and try again. It takes a couple of days seeing what your cpu will do. I have a person, right now, who's 8 month old Tilt 2 will NOT run over 672. He had some hairy days as almost ALL will run 710. But, regardless, I start you out at 691, and even THAT may be too high!

NOTE: Always save the original file. Never use it for a working copy!

To make speed changes to the script, use a decent editor (notepad is ok, but you have to tell it "all files" every time you try to save changes. The final file MUST be .mscr, period!) I recommend doing a Google search for Notepad 2. It's a powerful FREE open source editor and can do MANY formats, like xml, even! And you always save as the original file unless you want to change it. MUCH better than Notepad, in my opinion.

The script has the various settings for the desired speeds notated. Use them to set the two relevant speeds in the script. Leave the safe_speed alone, it has to be what it is.

You can set the start_speed either the same, or one point above, the boost_speed. I have no idea what happens if you set it below the boost_speed, don't want to find out.

Don't make ANY other changes to the file, unless you are a MortScript guru. Or at least willing to have it ON YOU if you mess up!!

Again, make sure the file is saved as the same name as the original if you are copying it to the SD card. That way, you don't have to re-create the shortcut. As I said, I go into the device's windows directory only when I have to. I don't have to do so to set this script.

If you still want to copy the saved file to the Windows\Startup, be careful and it's still ON YOU if you screw up and bricks your device.

Happy Hunting.