Related
Hey people on the board!
I'm a relative newbie in this PDA-stuff so I have a question which perhaps (hopefully) is easy to answer. Problem:
I have an application which I run on my Qtek 1010. The application runs fine, but prior to using it, a significant amount of time must be spent on installing and configuring it. In case of battery-faliure, this needs to be done from scratch. I would therefore like the Qtek to execute a script-like file (autorun.exe) which performs this task, immediately after booting.. The file is present on a flash-card inserted in the slot. How do I do this? Where - on the card - do I place the file? In the root? And how do I detect it and run it automatically after a cold-boot?
Any help would be greatly appreciated! Thx!
/Joe72
Its quite simple
Hi there, your problem to fix is quite easy.
If you look in in your windows directory with the built-in explorer, you'll find a directory - either "startUp" or "Autostart" depends on the system language you are using. Here you put a link to the program you're having on card. With every cold- or warm boot it will be executed. :lol:
regards
cimber
On the memory card make a directory named 2577, I believe the pocket pc will look here for your autostart on boot, try it and see. You can try putting a cab file in there or your autostart config file. I am not an expert in this but thats how its done with ipaq navigation system which is an automatic routine using the 2577 directory and I have also seen other software using the same method.
the file should be called 'autorun.exe' in the '\storage card\2577\' directory.
when you insert the card, the autorun.exe will be copied to \windows, and executed with 'install' as parameter.
when you remove the card, it will get executed with 'uninstall' as parameter.
and then removed from \windows.
but this will not nescesarily happen at boot.
just figured out another thing: the number you put in the .lnk file in \windows\startup is completely ignored by windows.
also, if the executable is in \windows, you may omit the path,
you may also omit the extension if it is .exe.
if you specify commandline parameters, your application will get passed upto 255 characters starting from the first non-whitespace character after the executable name.and including any newlines that may be in the file.
Hi!
Thanks for the response. I'll give the methods a try during the day and get back.
Thanks so far - I appreciate it
/Joe72
Hi there (again)!
I have tried the different suggestions with no luck. Perhaps I should have been a bit more specific. What I actually need is to have the autorun.exe run (install) a number of cab-files also on the flash-card. I was - perhaps naively - thinking that there would be a generic tool out there to create this type of autorun.exe file? I am looking for something along the lines of what is being done here:
http://forum.xda-developers.com/viewtopic.php?t=508&highlight=autorun
Only, in the case above, the autorun.exe lauches a specific .cab-file which contains a ROM for the PDA.
Is there a "configurable" .cab-installing autorun.exe out there somewhere? Or should it be written from scratch every time for new purposes?
Hope I make myself clear
/Joe72
yes, it is in the extended rom, processing the config.txt file.
eeeh, but the location of the config.txt is taken from the registry, which is currently always set to \extended_rom\config.txt.
itsme said:
yes, it is in the extended rom, processing the config.txt file.
eeeh, but the location of the config.txt is taken from the registry, which is currently always set to \extended_rom\config.txt.
Click to expand...
Click to collapse
Could you explain that to me in more detail, please? As I mentioned, I am a relative newcomer in this Xda stuff Thanks..
/Joe72
what you are asking for is the autorun.exe found in the extended rom,
look for 'extended rom batch language' on the forum for details.
problem is that the autorun.exe from the extended rom uses the config.txt
pointed to by the "[HKEY_LOCAL_MACHINE\Comm] AutoRunCfg" registry value. which always is '\Extended_ROM\Config.txt"
what you could do, is change the 'autoruncfg' string in the autorun.exe binary in to something else. and then fill your own config.txt path in that registry value.
Thanks - that sounds like the way to do it. I guess I would copy the original config.txt, add my .cab-files, put it on the flash-card and then change the key in the registry to point to the card. Is that how it would go?
Now another stupid question: How do I access the registry? There is apparently no regedit.exe like on my desktop?
/Joe72
Joe72 said:
Thanks - that sounds like the way to do it. I guess I would copy the original config.txt, add my .cab-files, put it on the flash-card and then change the key in the registry to point to the card. Is that how it would go?
Now another stupid question: How do I access the registry? There is apparently no regedit.exe like on my desktop?
/Joe72
Click to expand...
Click to collapse
Managed to access the registry using Windows CE Remote Registry Editor. But whooops.. After a cold boot, the registry is reset to factory settings?! Hence my changes of the path to config.txt are also lost..? What to do?
/Joe72
What you'll need:
CAB editor, such as OCP WinCE CAB Manager
Madkat's WM2k3 Boot Image Tool (attached)
Adobe Photoshop or other image editor
a compatible HTC device such as the Magician or Blue Angel
Summary:
Customized SplashX.nb files to be installed in \Windows directory of your device
Included:
Customizable Splash2.psd file for use with Adobe Photoshop
Steps:
1. Change the Splash2.psd file as necessary, then save a 24-bit BMP file called Splash2.bmp.
2. Use Madkat's Tool to convert the BMP file to an NB file.
3. Use the CAB editor to replace the Splash2.nb file with your version. WinCE CAB Manager may state an "Unspecified Error" when replacing the file. Instead, delete the original file, then drag the new NB file into the CAB file, hardcoding the \Windows folder as the install destination.
4. Save the CAB file and run it on your device!
Magician devices have only one splash screen, and it must be saved as Splash2.nb.
Blue Angel devices have two splash screens, Splash1.nb and Splash2.nb. Use the above steps to incorporate both splash screens as necessary.
Splash screens will be retained even after a hard reset, so use this after the Anansky's Big Storage hack, or if you just want to personalize your device, such as in the unfortunate event that it's lost or stolen - unless they know this trick, they won't be able to get rid of it!
Have fun!
Thanks mate works like a dream!!
Maybe it's just me, but I've read this post here and at Howardforums and I'm clearly missing something.
I've only ever used the nb_image_converter_859_418.exe to convert "any" bmp to the Splash2.NB file.
Then I drop that into my Windows Folder and use MDA3_bootimage_changer2.cab to apply the file. (Yes I'm using a Magician with this file!)
Soft reset and that's that. No need to do any cab file editing.
Cheers
Howard
PS. I've have both tools on my pc and can repost them, but they are from this site!
hshortt said:
Maybe it's just me, but I've read this post here and at Howardforums and I'm clearly missing something.
I've only ever used the nb_image_converter_859_418.exe to convert "any" bmp to the Splash2.NB file.
Then I drop that into my Windows Folder and use MDA3_bootimage_changer2.cab to apply the file. (Yes I'm using a Magician with this file!)
Soft reset and that's that. No need to do any cab file editing.
Cheers
Howard
Click to expand...
Click to collapse
Tried that way myself a while ago but for some reason it refused to work for me? (could of been the fact i used a file called XDA2_bootimage_changer.CAB)?? anyway now I can use self contained cabs so I make some splash's for my friends
PS. I've have both tools on my pc and can repost them, but they are from this site!
it must be me, but what cab file are we using here ?
3. Use the CAB editor to replace the Splash2.nb file with your version. WinCE CAB Manager may state an "Unspecified Error" when replacing the file. Instead, delete the original file, then drag the new NB file into the CAB file, hardcoding the \Windows folder as the install destination.
Click to expand...
Click to collapse
:?: :idea: :!: :?:
DOH! I forgot to include the file. It's there now in the top post.
3. Use the CAB editor to replace the Splash2.nb file with your version. WinCE CAB Manager may state an "Unspecified Error" when replacing the file. Instead, delete the original file, then drag the new NB file into the CAB file, hardcoding the \Windows folder as the install destination.
well, i'm using resco file explorer. i'm choosing on my pc to send the file to windows directory. he ask's me if i wanna overwrite it, i click yes and then it's done. i'm reloading, but still qtek logo on the screen(( what am i doing wrong?
ps. i tried to use WinCE CAB Manager but i didn't figured out how to use the program....
update:
oh, i needed to use a different file...
thanks guys! well done)
my version (unfortunatelly understandble only for russian speaking users) but maybe somebody will like it)
http://zhgun.ru/pics/i/draw/jamming_.jpg
http://rapidshare.de/files/2112736/jamming.cab.html
hshortt said:
Maybe it's just me, but I've read this post here and at Howardforums and I'm clearly missing something.
I've only ever used the nb_image_converter_859_418.exe to convert "any" bmp to the Splash2.NB file.
Then I drop that into my Windows Folder and use MDA3_bootimage_changer2.cab to apply the file. (Yes I'm using a Magician with this file!)
Soft reset and that's that. No need to do any cab file editing.
Cheers
Howard
PS. I've have both tools on my pc and can repost them, but they are from this site!
Click to expand...
Click to collapse
hi, can't seem to download the attachments, could you repost them?
If you don't like Bill's Stuff...
I wonder if anyone can put some help my way.....
I used the xda2 image changer before and I had custom images on my XDA2.
I use this and all I get is a black screen on startup. If I open the .nb file with the converter it shows as it should. (this same .nb works on my XDA2!)
I now have a plain black boot up screen!!
DOH!!!!
Any ideas......?
THanks
First i had the t-mobile splash... wich i didn't like.
Now, whatever bootsplash cab i make, or download here.. after running it, my bootscreen stays blank ( as in black ).
oh well... its an improvement over t-mobile pink
( or is it because i'm running an ancient rom : 1.01.00 WWE ?, only have the device for 3 days... will be upgrading this weekend tho )
Here are my 2 favourites Splashscreens.
The blue one ist for the silver Magician, the darker one is for the new O2 XDA mini (black edition).
Hi I've editted the o2 logo here's the jpg file
I tried to upload the psd so you can edit it but it doesn't work, to bad!
Step-by-step making your own splashscreen
Guys,
Simpler than this you will not find.
Goto
http://pocketpcdubai.infopop.cc/groupee/forums/a/tpc/f/582600994/m/138105069
and find everything you need to know.
It worked perfectly for me...
Excellent information, real easy to do
this is mine:
Awesome...
I saw this before, but I have just tried it... and it is really cool 8) ... it gives the device a whole new look...
thanks BTT
My way to splash changer.
Hi,
I thanks to BTT for Splash Changer how to. But it is troublesome to everytime run WinCE cab manager in order to put Splash2.nb to the .cab file.
I try to remove Splash2.nb from the .cab file (and renamed the .cab to splash_changer.cab). Afterthat, put the Splash2.nb manually to \windows on PPC. Voila....., no need to everytime run WinCE cab manager!!!!!
Process:
1. Edit .bmp file to your like (Must be 240x320 pixels, 24bit).
2. Use nb_image_converter_859_418 to convert .bmp file to .nb, and change the .nb file to Splash2.nb.
3. Put Splash2.nb file directly to your \windows on PPC. You can do activesync and explore it.
4. Put splash_changer.cab to \temp for you to easier found it.
5. Run file explorer on PPC, and tap on splash_changer.cab.
6. Done! You can check by soft reset the PPC.
Hope it is helpful!
Regards,
Arto.
can it work on normal pocket pc?
can it work on normal pocket pc? (x50v)
Re: can it work on normal pocket pc?
avi9899 said:
can it work on normal pocket pc? (x50v)
Click to expand...
Click to collapse
No idea....
Regards,
Arto.
Hi all,
I just sucessfully installed big storage on my O2 mini and was wondering how i can change the default directory to which my software installs. The software is Imaginet-arabitizer and it uses a PC-based installation. No cab files...
Help please....
help
you can only whether you want to install a program to a default location, storage or a storage card. it will ask you in the beginning of installation by ActiveSync. choose NO and install sonewhere else.. gl
Still no luck....
Unfortunately, this particular program does not use the active sync user interface for the installation....
Any other methods?
i saw a shareware program on the forums once that did that... wish i downloaded it then cause i cant find it again sorry .. thought id let you know its out there though.....
aidil916 - unless it's some kind of ROM update etc, anything that gets installed on the PPC must always use a cab file, even on PC based install. So, start the install, and does add/remove programs or something come up?
Either way, if it installs something to the PPC (i've no idea how the arabizer works), interrupt the installation or somehow stall it. Then use a program like Filetracer or even the XP search tool to find any cabs installed to your pc in the last few minutes. Track down the cab (usually in your temp folder, programs folder or activesync folder) and then take a backup copy of the cab. Then, copy that to your PPC..
Tell me how it goes.
V
aidil916 said:
I just sucessfully installed big storage on my O2 mini and was wondering how i can change the default directory to which my software installs.
Click to expand...
Click to collapse
Usually when you perform PC-based installation software asks you for target location but some programs are hard-coded with "\Program Files\ProgramName" path so they will fail to work if you place them to another locations, i.e. to Storage Card
For programs that don't allow you to change target location you can change their registry entries to correct their path from "\Program Files\" to "\Storage Card\Program Files\". Here you will also need to manually move your program to a new location (SD) using Explorer's copy-&-paste functions
ps: don't use cut-&-paste because some of your programs may be running and this will cause sharing violation errors
Example, I have program "ABC" installed at "\Program Files\ABC" folder.
1) Using Explorer I navigate to "\Program Files" and COPY "ABC" folder to clipboard
2) Now I navigate to "\Storage Card" and create folder "Program Files"
3) I open newly created folder "\Storage Card\Program Files" and PASTE my "ABC" folder from clipboard here
4) Using Registry Editors I search for "\Program Files\ABC" entries and change them to "\Storage Card\Program Files\ABC"
5) I do soft-reset. If after that program works Ok, I delete "\Program Files\ABC"
The software is Imaginet-arabitizer and it uses a PC-based installation. No cab files...
Click to expand...
Click to collapse
Check your activesync's installation location. You will find the cab file within Software name or company folder, like "C:\program files\microsoft activesync\ABC"
Cheers
aidil916 said:
Hi all,
I just sucessfully installed big storage on my O2 mini and was wondering how i can change the default directory to which my software installs. The software is Imaginet-arabitizer and it uses a PC-based installation. No cab files...
Help please....
Click to expand...
Click to collapse
There are 3 methods i use,
1st is download the CAB file if you can, copy to your PPC and install with a program called CAB Install http://www.s-k-tools.com/fp/viewtopic.php?t=44 which allows you to install the app anywhere you want.
2nd is to run the standard ??.exe PC installation file but without your PPC pluged in. After the ??.exe install file is finished it will normally produces a CAB file on your PC which will copy across to your PPC next time you plug it in. All you need to is to find the CAB file and manually copy it to your PPC and use CAB Install.
The 3rd way is to do the same as 2 above and then use an app called WinCE CAB manager which you can generally modify the CAB files standard installation directory to what ever you want to.
Hope this helps
Most software including PC based installs eventually use CAB files. For this I use a small program CabInstl.
Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool. Use ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf to read up on how to create OEM packages and how they work.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
When you provide the packages, try to provide it with the original package.rgu and/or package.dsm filenames (not with the GUID that was generated for you). People will then be able to just run the buildos.exe and the GUID will get created for them without changing filenames. Then just edit the options.xml file to use the newly generated GUID.
so screenshot + cab + short info + status: freeware/shareware/etc. would be fine?
mfrazzz said:
Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
The only tricky thing here would be the guid for the files. I'm still new to this, so if someone has an idea how to handle that (maybe the person does the package.rgu and runs the program where it generates the guide, then unzips the files and modifies the guid to the new one in the right places).
Click to expand...
Click to collapse
The GUID is so simple, if you to use a package, just go to http://www.famkruithof.net/uuid/uuidgen . Then you just get a new GUID and paste it in all the different palces in the package, then you dont have to chnage file names then have them chnaged again by buildOS
I thik this is a good idea, would be good to share and also good for problem finding, cus i have one that i cant for the life of me get the today plugin to work how it is meant to!!!
GSFinder Package
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for GSFinder. This is a freeware file manager (like TotalCommander).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
MoDaCo NoData
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for MoDaCo NoData. This is a freeware program that allows you to turn off and on what data sources will work on your device (so if you don't have a GPRS plan, you can turn off GPRS so your phone will not use it).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
mUn Keyboard Skin
This is a package for the mUn keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is in the mUn aRTM WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.
XPlore Keyboard Skin
This is a package for the XPlore keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is provided for the XPlore 2.0 WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.
mfrazzz said:
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
Click to expand...
Click to collapse
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
I'd noticed this when I was building another package. In my experience, I have to do a build without the options file, let the [GUID].dsm file get built, then create the options.xml file with the correct GUID in it and then rerun.
saeba said:
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
Click to expand...
Click to collapse
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.
mfrazzz said:
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.
Click to expand...
Click to collapse
Can i jst say that the chnace of the same number being used again in you kitchen is really high, so you should not have to chnage it!!! Try run the buildOs without chnaging anything!
Has anyone figured out how to move files yet?
RickoT said:
Has anyone figured out how to move files yet?
Click to expand...
Click to collapse
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.
Battery Status Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Reposting with generic Registry Entries (removing ADB100's custom settings he mentions in his post below)
WM5torage Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.
mfrazzz said:
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Click to expand...
Click to collapse
I should note that it is pre-configured with the following options:
General Tab - Show CpuSpeed, Show Mobile Operator
Indicator Tab - Show more Indicators, Use Small Fontsize, Show Powerdrain, Show Temperature
Tools Tab - DeviceLock on Wakeup, Lock if Display..., Backlight fix - 30-seconds
Omap Tab - Overclock to 247Mhz, Overclock on Wakeup, Remember last CpuSpeed, Overclock after reboot
Traylaunch Tab - All disabled
Not sure this will suit everybody so be warned...
Andy
Adobe Reader LE
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for Adobe Reader LE. This is the "faria Adobe Reader" cab thats been posted, but then I've altered the .rgu to fix the registry entry for opening docs that have spaces in the name (Thanks ADB100 for pointing that fix out), and made a couple of fixes to the initflashfiles.txt (it had moves for files that didn't exist and I've added where it moves a shortcut into \Windows\Start Menu\Programs\Accessories
Just unzip into your OEM directory.
ADB100 said:
I should note that it is pre-configured with the following options
[... snip ...]
Not sure this will suit everybody so be warned...
Click to expand...
Click to collapse
I've reloaded the zip file in my post above for Battery Status and put the registry entries back to generic like a fresh install. If you want specific settings, then install BS, tweak it to your heart's content, then dump out the registry entries and replace them in the .rgu file.
mfrazzz said:
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.
Click to expand...
Click to collapse
Sorry mate but your package is not right! The .rgu was not setup right!
funman said:
Sorry mate but your package is not right! The .rgu was not setup right!
Click to expand...
Click to collapse
Arrrgh! Sorry about that. I was putting that one together and got interupted with a concall at work, and some other things. I went back to working on it, and I guess I didn't edit and fix what I thought I had done... Sheesh...
Thanks...
mfrazzz said:
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.
Click to expand...
Click to collapse
Are you sure, because I think I read in faria's rom thread that it copies the files, not moves them, (Unless im utterly retareded and misread it, which is very possible)
I feel like a total n00b asking a question like this, but I must know, so I know whether there's something I'm missing.
I have an HTC FUZE (Raphael) device, and I've been dumping Topaz & Rhodium ROMs as I come across them and incorporating the updated packages into my personal ROMs. I started seeing this new program called "RunCC" in the ROMs, and when I looked in the folder at the files, it looks a lot like the Windows Customization that runs after hard-resetting my device where it installs all the stuff the config_operator or config.txt has in it.
Now my question is, is that in fact what RunCC is? An updated method of customization? How do I use it? How I do I stop using my current method (AutoRun?)? Is there some advantage to using RunCC?
I wasn't even sure where to ask this question, but this seemed like the safest bet. Is anyone else wondering this, or am I the only one that doesn't know?
EDIT: Thanks to everyone's help, RunCC is finally working!! Here's what I did to get it working (with UC). NOTE: These instructions apply to using RunCC with VGA devices only!!
1) Make sure you have a runcc.lua file included somewhere. This is what mine looks like:
Code:
chk = oem.checkfileexist("\\windows\\config.txt")
if chk == 1 then
runcc.addrun("RunDefault", "run", "\\windows\\config.txt")
end
chk = oem.checkfileexist("\\Storage Card\\SDConfig.txt")
if chk == 1 then
runcc.addrun("RunExtra", "run", "\\Storage Card\\SDConfig.txt")
end
2) Make sure your RunCC package includes these two files (these are specific for VGA devices):
Code:
RunCC_default_bg_480_640.jpg
RunCC_default_bg_640_480.jpg
3) Make sure you have these reg entries in your app.reg (these are also specific for VGA devices)
Code:
[HKEY_LOCAL_MACHINE\Software\HTC\RunCC]
"ProgressImgUnit"=dword:00000001
"ProgressImgTime"=dword:00000003
"ProgressImgPosX"=dword:00000032
"ProgressImgPosY"=dword:0000023A
"ProgressImgLandPosX"=dword:000000F6
"ProgressImgLandPosY"=dword:00000190
4) Make sure you've deleted AutoRun.exe, AutoRun.lnk & CheckAutoRun.exe, CheckAutoRun.lnk from your OEMDrivers, and make sure you delete these lines from your OEMDrivers rgu file:
Code:
[HKEY_LOCAL_MACHINE\Comm]
"AutoRun"="\\Windows\\autorun.exe"
"AutoRunCFG"="\\Windows\\config_operator.txt"
"AutoRunCheckNC"=dword:00000001
5) SDAutoRun should be deleted too, and if you have a line in your config.txt that calls it, that line should be removed. Also, you should remove the "RST: Reset" line from your config.txt. If you want the device to reset after customization is complete, just change this reg entry in the RunCC package:
Code:
[HKEY_LOCAL_MACHINE\Software\HTC\RunCC]
"ResetDevice"=dword:00000000 ;CHANGE to dword:00000001
That should get your RunCC working. Report back with feedback!
One important note - If you decide to use RunCC with UC, as indicated above, make SURE that your cabs are set as Read-Only - otherwise they will be deleted from your Storage Card after being installed.
I can answer your last two questions: yes, I've been wondering what it is, but no, I'm not really sure what it is and how it works. It is something that goes during customization, and I've mostly seen Noonski talking about it.
Some info, but not much: http://forum.ppcgeeks.com/showpost.php?p=876466&postcount=29
Warjcowski said:
Some info, but not much: http://forum.ppcgeeks.com/showpost.php?p=876466&postcount=29
Click to expand...
Click to collapse
Hm. You're right, that was vague, at best. bengalih seemed to be more defending the use of SASHIMI than really explaining how RunCC works. It appears that Noonski may be the only one that knows anything about RunCC. Maybe I should send him a PM and ask for a comment/explanation of RunCC.
It's just an updated Autorun.exe method from HTC.
Some newer versions even support direct cab installation from SD card by simply adding a config.txt line to the LUA script.
L3V5Y once told me the correct name it should have for that. (Should be posted in the XDA_UC thread)
You don't need it on Raphael, the regular Autorun does it's job well enough and XDA_UC even better
RunCC does have a better Background and loading bar that's pretty easy to customize though, but other then that it is not Needed on Raphael.
The main problem was just that new devices would start using this and it broke SDAutorun compatibility, that should now not be an issue anymore with newer versions. Personally i don't use either RunCC or Autorun anymore and it's made Flashing and especially waiting for being able to use the phone faster.
There might still be some underlying code still unknown at the moment. And with the addition of RunCC.exe being able to actually run files from SD card's it looks like HTC is giving providers more control over extra apps on phone while concentrating on just one Rom for the phones instead of making multiple roms for different providers.
You can step over to RunCC but you would have to remove Autorun.exe, welcome.lnk & CheckAutorunexe/lnk from your rom. And the Autorun registry entries.
So I wanted to try this RunCC out. I deleted AutoRun & CheckAutoRun from my OEMDrivers, and deleted the reg entry that calls AutoRun. Then I included the RunCC Package in my ROM. Only when I cooked the ROM, RunCC didn't run. What did I do wrong? Did I need to change the AutoRUn reg entry to call RunCC.exe instead? Maybe I'll try that this time and see if it works.
RunCC should be called by the HKLM\Init\Launch58 registry entry.
This runs just before the \StartUp items.
It then calls for the RunCC.lua file that has the config files listed to install.
In most Roms the RunCC.lua file is not in the RunCC Package.
RunCC.lua is just text file.
Noonski said:
RunCC should be called by the HKLM\Init\Launch58 registry entry.
This runs just before the \StartUp items.
It then calls for the RunCC.lua file that has the config files listed to install.
In most Roms the RunCC.lua file is not in the RunCC Package.
RunCC.lua is just text file.
Click to expand...
Click to collapse
Thanks. That's what I was missing. I also found an interesting discussion of RunCC (as well as some tips to get it working) in the Elf Fourm. See here:
http://forum.xda-developers.com/showthread.php?p=3425124#post3425124
Now maybe some others can try it and see if it works for them, and if there's any value to using it in place of AutoRun. I guess that means UC doesn't work with RunCC, since it calls AutoRun. There must be a way to make that work, right?
No you can't call Autorun as taking the reset option away from the RUnCC registry settings might result in a Cold boot an it will keep rebooting.
If you check out XDA_UC you'll see that both runcc, SDAutorun & Autorun aren't needed anymore.
And you can then even speed the proces up by using .xdas files wich are basicly ip files being unzipped by Mortscript. A lot faster then using cabs.
It was that conversation in the cooking class, that got me into looking into RunCC and getting it to work with SDAutorun
back from the dead
I figured I'd resurrect this thread, as I finally got RunCC working on my Fuze.
But now I have a few questions about doing more with it:
What do the various commands in runcc.lua do? I currently am using only a config.txt for customization, and am using the "RunDefault" command to execute it. I noticed (before deleting the other info in the file) that there were also "RunExtra" & "RunCustomer" commands. What's the difference?
My second question is, would it be possible to call for the execution of an SDConfig.txt file on a Storage Card, if specified by path in both config.txt & runcc.lua? That would mean I wouldn't have to include AutoRun anymore at all, which I would kind of prefer.
Currently, I have it set up so RunCC calls SDAutoRun if I want to use UC, and since SDAutoRun calls AutoRun, I include have to include it in the ROM (though I leave out most of the reg entries for it).
Anyone with some RunCC knowledge want to help me out with these answers?
Captain,
I was able to get my RunCC (running on a Pure) to execute files on my SD card, but I'm not sure if you can add a direct link to SDConfig.txt, but I'm going to try it when I've got some time...
I know you can run files like "XML: \Storage Card\whatever.xml" from within config.txt, so i know you could do a "CFG: \Storage Card\SDConfig.txt" to run it, but the problem here is that if the SDConfig.txt didn't exist it would bomb out, resulting in an endless loop of hard resets...
Optimally, I think we try to edit RunCC.lua to look and see if the SDConfig.txt exists and if so, then it executes it.
I'm not really sure what the differences are in the "RunDefault", "RunCustomer", etc though... I guess it'll take some experimenting...
I think the RunCustomer etc just run in different orders, though some may be able to do things like XMLs/Config text files. I'd just use RunDefault option which seems to work...
i neva tried to but this may work if u add these codes to ur control block
Code:
chk = oem.checkfileexist("\\Storage Card\\UC\\config.txt")
if chk == 1 then
runcc.addrun("RunDefault", "run", "\\Storage Card\\UC\\config.txt")
end
but i use a sort of alternate method. here it is if u wana try it out
0.extract this zip file ur ur SD card:View attachment 242051
1. intall this cab using runCC:View attachment 242050
Code:
;;;;;;;;;;check and run script
if (FileExists( "\Storage Card\silent_UC\Autorun.mscr" ))
callscript ( "\Storage Card\silent_UC\Autorun.mscr" )
EndIf
;;;;;;;;;;delete calling script to prevent it from loading
SetFileAttribute(SystemPath("Startup") \ "s.mscr" , "readonly", FALSE)
SetFileAttribute(SystemPath("Startup") \ "s.mscr" , "system", FALSE)
Delete(SystemPath("Startup") \ "s.mscr" )
more details on how to add customization here
hope this helps
Captain_Throwback said:
I figured I'd resurrect this thread, as I finally got RunCC working on my Fuze.
But now I have a few questions about doing more with it:
What do the various commands in runcc.lua do? I currently am using only a config.txt for customization, and am using the "RunDefault" command to execute it. I noticed (before deleting the other info in the file) that there were also "RunExtra" & "RunCustomer" commands. What's the difference?
My second question is, would it be possible to call for the execution of an SDConfig.txt file on a Storage Card, if specified by path in both config.txt & runcc.lua? That would mean I wouldn't have to include AutoRun anymore at all, which I would kind of prefer.
Currently, I have it set up so RunCC calls SDAutoRun if I want to use UC, and since SDAutoRun calls AutoRun, I include have to include it in the ROM (though I leave out most of the reg entries for it).
Anyone with some RunCC knowledge want to help me out with these answers?
Click to expand...
Click to collapse
Glad to see that someone else has these questions also.
I was able to get SDconfig.txt to run from the storage card with this:
Code:
chk = oem.checkfileexist("\\Storage Card\\Sdconfig.txt")
if chk == 1 then
runcc.addrun("RunDefault", "run", "\\Storage Card\\SDconfig.txt")
end
Just make sure you take the reset command out of the SDconfig.txt
Now, what I haven't been able to do is get some of the things in my Sdconfig.txt to work.
Copy Commands don't seem to work. Such as CPY1:\ CPY2:\
Also, anything that requires user intervention doesn't seem to work either. It just seems to skip right over those somehow.
If someone has some answers, I would like some help also.
rgb-rgb said:
Glad to see that someone else has these questions also.
I was able to get SDconfig.txt to run from the storage card with this:
Code:
chk = oem.checkfileexist("\\Storage Card\\Sdconfig.txt")
if chk == 1 then
runcc.addrun("RunExtra", "run", "\\Storage Card\\SDconfig.txt")
end
Just make sure you take the reset command out of the SDconfig.txt
Click to expand...
Click to collapse
Nice. I kind of thought that would work. Do you still have to call the SDConfig file from the config.txt file with a "CFG: \Storage Card\SDConfig.txt" at the end, or does it find the file with only adding the above to the runcc.lua?
Captain_Throwback said:
Nice. I kind of thought that would work. Do you still have to call the SDConfig file from the config.txt file with a "CFG: \Storage Card\SDConfig.txt" at the end, or does it find the file with only adding the above to the runcc.lua?
Click to expand...
Click to collapse
No, do not call it from the config.txt file, just add it to the runcc.lua
Also, I used RunDefault instead of RunExtra. I have also been able to get the user input to work on one try. Now I'm going for the whole SDconfig.txt file that I had.
I changed the app.reg file to this:
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\init]
"Launch58"="RunCC.exe"
[HKEY_LOCAL_MACHINE\Software\HTC\RunCC]
"DisplayFilename"=dword:00000001
"script"="\\windows\\runcc.lua"
"UIMode"=dword:00000000
"TurnOffRadio"=dword:00000000
"RecoveryType"=dword:00000002
"TodayDelay"=dword:00000000
"ResetDevice"=dword:00000001
"ResetUICountDown"=dword:00000005
"LaunchCSType"=dword:00000002
"RunCCRunStatus"=dword:00000000
"InitUITopmost"=dword:00000000
"PreCreateUI"=dword:00000001
"EnableTransition"=dword:00000001
"FullScreen"=dword:00000001
"ProgressImgTime"=dword:00000005
"ProgressImgUnit"=dword:00000001
"ShowMessageBar"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\MASD]
"RunCC"="1_1_7_0"
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\PKG]
"shadow"="1"
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\AutoShortcut]
We'll see what happens in about 10 minutes
Okay, so all of my CAB files that require user input worked as they should.
I still have a couple of issues to deal with, I have the connection setting wizard coming up which I have to shut down so I can see my input dialogs. Don't know how to stop the connection settings from running yet.
Also, the CPY1: CPY2: commands did not work when running it this way, so I have to figure out a way to get xcopyce to run and the only way I can see doing it right now is to cook xcopyce into the ROM unless the FILEOP command work somehow, but I don't know anything about that yet.
rgb-rgb said:
Okay, so all of my CAB files that require user input worked as they should.
I still have a couple of issues to deal with, I have the connection setting wizard coming up which I have to shut down so I can see my input dialogs. Don't know how to stop the connection settings from running yet.
Also, the CPY1: CPY2: commands did not work when running it this way, so I have to figure out a way to get xcopyce to run and the only way I can see doing it right now is to cook xcopyce into the ROM unless the FILEOP command work somehow, but I don't know anything about that yet.
Click to expand...
Click to collapse
You should be able to prevent Connection Setup from interrupting your customization by setting the "TurnOffRadio" from dword:0 to dword:1. If the phone radio is off, Connection Setup won't run.
Captain_Throwback said:
You should be able to prevent Connection Setup from interrupting your customization by setting the "TurnOffRadio" from dword:0 to dword:1. If the phone radio is off, Connection Setup won't run.
Click to expand...
Click to collapse
Thanks, I'll give that a try on the next flash which at the rate I'm going will be in less than 30 minutes
hey Captain_Throwback, it's OMJ...
*EDIT* ooops, I missed page 2 b4 posting...I'm gonna try to above suggestions
1st, can you tell me how you got RunCC to work w/ SDAutoRun, and how is it beneficial over using the AutoRun package?
I tried using RunCC and included SDAutoRun & AutoRun in the rom, I had runcc.lua setup to run config_operator.txt, and it did execute the commands, except for SDAutoRun.exe. I assume I need to add some reg entries for Autorun?
I was also hoping runcc.lua could be used to call the SDConfig.txt file on a Storage Card. maybe w/ code like: (this is on a Diamond)
Code:
chk = oem.checkfileexist("\\Internal Storage\\SDConfig.txt")
if chk == 1 then
runcc.addrun("RunDefault", "run", "\\Internal Storage\\SDConfig.txt")
end
As Noonski stated earlier...if a cab can be installed why not SDConfig.txt?
Noonski said:
Some newer versions even support direct cab installation from SD card by simply adding a config.txt line to the LUA script.
Click to expand...
Click to collapse
Captain_Throwback said:
I figured I'd resurrect this thread, as I finally got RunCC working on my Fuze.
But now I have a few questions about doing more with it:
What do the various commands in runcc.lua do? I currently am using only a config.txt for customization, and am using the "RunDefault" command to execute it. I noticed (before deleting the other info in the file) that there were also "RunExtra" & "RunCustomer" commands. What's the difference?
My second question is, would it be possible to call for the execution of an SDConfig.txt file on a Storage Card, if specified by path in both config.txt & runcc.lua? That would mean I wouldn't have to include AutoRun anymore at all, which I would kind of prefer.
Currently, I have it set up so RunCC calls SDAutoRun if I want to use UC, and since SDAutoRun calls AutoRun, I include have to include it in the ROM (though I leave out most of the reg entries for it).
Anyone with some RunCC knowledge want to help me out with these answers?
Click to expand...
Click to collapse