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
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
Hello! if you create in \TomTom\SdkRegistry\ 2 files called, for example, mortplayer.bmp and mortplayer.cap, and edit this with notepad as follow:
AppName|MortPlayer.exe|
AppPath|\Scheda di memoria\Mort's MortPlayer\|
AppbmpnFile|mortplayer.bmp|
AppMainTitle|Avvia MortPlayer|
COMMAND|CMD||mortplayer.bmp|MortPlayer|
Tomtom will show a 4th menu with your bmp (72x48, 24 bit, 72dpi) and the link to the application.
Now i want to insert a link to VJDialer and dial a number with one click.
Here is, for example, the code:
AppName|VJDialer.exe 0123456789|
AppPath|\Storage\|
AppbmpnFile|vjdialer.bmp|
AppMainTitle|Avvia VJDialer|
COMMAND|CMD||vjdialer.bmp|FRIEND_NAME|
Now... this method does not work.
Vijay Help ME! can i do this?
I halso have tried to create a link to vjdialer, put it into sdkregistry dir, and execute it from .cap file:
AppName|VJDialer.lnk|
AppPath|\TomTom\SdkRegistry\|
AppbmpnFile|vjdialer.bmp|
AppMainTitle|Avvia VJDialer|
COMMAND|CMD||vjdialer.bmp|Friend|
and
AppName|VJDialer.lnk|
AppPath|\Storage\|
AppbmpnFile|vjdialer.bmp|
AppMainTitle|Avvia VJDialer|
COMMAND|CMD||vjdialer.bmp|Friend|
But with no results.
SkizZO: I'm afraid I don't use TomTom (find the poll I'm running to decide if I should buy the Mio with built in GPS!).
However, check your .lnk file. If it launches correctly when run, then I would try copying it into your MortPlayer folder, and editing the entry you know works for mortplayer, and just make it launch your VJDialer.lnk instead (since you know the other settings work).
Perhaps TomTom can't run command lines? That'd be a pain and require some thinking about?
This wasn't too helpful:
http://www.opentom.org/Menu_structure
V
You can't use links and you can't use parameters....
You can only start a exe file, that's it...
What you could do :
- Create a mortscriptfile TTdial.mscr
run vjdialer.exe 0123456789
make a copy of the autorun.exe that comes with mortscript, rename it TTdial.exe
Make the .CAP file as you wish and make it run TTdial.exe
The mortscript autorun.exe always starts a .mscr scriptfile with the same name, so you can have TTdial1.mscr + TTdial1.exe, TTdial2.mscr + TTdial2.exe etc.
WoW Thnx to aLL!
Hemm... wich is the exact shyntax of the mscr script?
...and.. can i use Onlu Autorun.exe (and autorun.mscr) without install anything?
SkizZO: I've made an app just for you, to make this a lot easier, I hope!
VJBrisk - http://forum.xda-developers.com/viewtopic.php?t=50509&start=0&postdays=0&postorder=asc&highlight=
Basically, setup your VJDialer shortcut, rename it to VJTarget.lnk, and copy the file VJBrisk.exe into the same folder.
Get TomTom to launch VJBrisk, and VJBrisk will launch VJTarget.
Let me know if that makes sense. But the autorun solution is still very neat.
V
oops double post
Thanx for all. In order:
Mortscript works well, the exact shyntax is (in mscr file):
run [PATH]\VJDialer.exe , 0123456789
Thanx vijay, i will try NOW your app.... only a question:
VJbrisk.exe launch only one vjtarget.lnk or just rename it (exe) with the same name of the link to have more than 1 phone link?
(es Vjbrisk1.exe call Vjbrisk1.lnk, Vjbrisk2.exe call VJbrisk2.lnk etc ?
sorry 4 my english
hello all....ive been looking around for a way to make the Palm Threading cab into an oem package. idk if its possible or not but from what ive seen its way beyond me considering how the app integrates itself into the os. another reason why idk if its possible or not.
the reason why i want to do with is bc i really like the palm threading app...but i find it that it majorly decreases the speed of ur wizard for some reason or another. all i use my phone for is calling and txting so if i had this as an oem package i could cook my rom and hopefully it would not slowdown the overall system...idk if its possible or not.
thanks before hand!...and yes i have done alot of searching on this....lol
o and sry if im completly retarted in thinking all this lol
it might be possible, but you need to provide a cab
cab
alright ill pm u the link. bc i no ppl got in trouble for posting the cab b4
Did anyone ever get the MMS feature wokring on a Wizard???
i was able to create a OEM package for this program...but it doesnt work when building the rom.
when i try to build i get an error
"The target file "temp\dump\htmlnote.dll" is a directory, not a file."
i never got the initflashfile generator program to work so i had to create my own
initflashfile if that matters. here is a copy
;==========================================================================
;==========================================================================
; Application bib for Palm SMS Threader
;==========================================================================
Directory("\Windows"):-Directory("Palm Messaging")
Directory("\Windows\Palm Messaging"):-File("tpcutil.dll","\Windows\tpcutil.dll")
Directory("\Windows\Palm Messaging"):-File("htmlnote.dll","\Windows\htmlnote.dll")
Directory("\Windows\Palm Messaging"):-File("mailtrns.dll","\Windows\mailtrns.dll")
Directory("\Windows\Palm Messaging"):-File("mdsmailsvc.dll","\Windows\mdsmailsvc.dll")
Directory("\Windows\Palm Messaging"):-File("MsgMnuExt.dll","\Windows\MsgMnuExt.dll")
Directory("\Windows\Palm Messaging"):-File("MsgMnuExt_enUS.dll","\Windows\MsgMnuExt_enUS.dll")
Directory("\Windows\Palm Messaging"):-File("poutlook.exe","\Windows\poutlook.dll")
Directory("\Windows\Palm Messaging"):-File("tkitapp.exe","\Windows\tkitapp.exe")
Directory("\Windows\Palm Messaging"):-File("tmail.exe","\Windows\tmail.exe")
Directory("\Windows\Palm Messaging"):-File("tmailutl.dll","\Windows\tmailutl.dll")
Directory("\Windows\Palm Messaging"):-File("tmarshaller.exe","\Windows\tmarshaller.exe")
Directory("\Windows\Palm Messaging"):-File("pimgdll.dll","\Windows\pimgdll.dll")
Directory("\Windows\Palm Messaging"):-File("webview.dll","\Windows\webview.dll")
Directory("\Windows\Favorites"):-File("Inbox.Ink","\Windows\Inbox.Ink")
Directory("\Windows\Programs"):-File("Inbox.Ink","\Windows\Inbox.Ink")
;==========================================================================
; END Application bib for Palm SMS threader
;==========================================================================
and i also made the .rgu file with the help of the cab analyzer
if anyone can help it would b great appreciated, im using a base rom with no other OEM packages. if any one needs the palm threader cab let me know. thanks
The issue is that this overwrites a currently existant file. Chec that portion out. I have been attempting to get this working along with Arcsoft since the mms ability does not work with this application.
ya ur right...i went through the sys folder and deleted the files as the error would appear and made it oem build process but then got an error could not create default.hv and user.hv. does this mean i screwed up in my .rgu file?
i made the .rgu file in textpad and just copied the regestry intres from the cab manager and saved as unicode
i have linked it below
and yes i this process doesnt really and OEM package bc u cant just drag and drop it in...im just seeing if i can make a rom with the palm app preinstalled,
thanks again for the help
Based on your intitflashfile.txt file you provided, these duplicate named files are not really duplicates (as it appears you are moving them to \Windows\Palm Messaging (I assume this is how the cab does this?). If thats the case, then don't rememove the original versions from the rom. Instead prefix all of the files (or the duplicate ones at least) in your package with palmmessaging_ or pm_ or somesuch to make them unique. Then in your initflashfile.txt you would do something like this:
Code:
Directory("\Windows\Palm Messaging"):-File("htmlnote.dll","\Windows\palmmessaging_htmlnote.dll")
By doing this, both files can exist in the \Windows folder, but then when it moves it to true destination it will then be renamed to the correct name that that app expects.
Personally, I hate putting stuff in my roms where you have duplicates of the files in both \Windows and then in some other directory. Seems like such a waste (but you have to do that sometimes based on what you are trying to make into a package).
Hope that helps.
jug6ernaut said:
ya ur right...i went through the sys folder and deleted the files as the error would appear and made it oem build process but then got an error could not create default.hv and user.hv. does this mean i screwed up in my .rgu file?
Click to expand...
Click to collapse
As for your rgu, get rid of all the spaces! Example:
Code:
[HKEY_CURRENT_USER\ControlPanel\Notifications\{283E0018-E5C9-44e4-9864-4C4A3DED3BC3}]
"EventType" = dword : 00000002
should look like:
Code:
[HKEY_CURRENT_USER\ControlPanel\Notifications\{283E0018-E5C9-44e4-9864-4C4A3DED3BC3}]
"EventType"=dword:00000002
I'm not sure if thats specifically the problem you have, but thats the first fix I'd do, as I don't think it likes things to be pretty
oh, here's another couple of problems I just noticed:
Code:
"AppName" = "\Windows\messaging.exe"
should be
Code:
"AppName"="\\Windows\\messaging.exe"
You have to use double backslashes in the .rgu file for the backslash to show up (otherwise it thinks you are escaping the next character).
Also, stuff like this is wrong:
Code:
"" = "LS6021023"
should be
Code:
@="LS6021023"
If you are using Core Kitchen you can use the tool in there to dump the cab file and it will give you a nice registry entry file to use.
wow thanks alot lol, man i didnt think i could mess up that much in 1 file lol.
umm in the .rgu file you say i should use \\ instead of \ is this universal throughout the file to where i could could use the find/replace function in textpad of is it more specfic? also with the "" needing to change to @.
thanks for the quick response and all the help
o and on the initflashfile, i was actually thinking about doing what u said b4, when nottosmart mentioned the error b4 was about a duplicate file and i did some searching and came to a post in the core kitchen thread(yes im using the core kitchen) about how to make OEM packages that said something in relation to what you said..but i didnt no at the time thats what i should do.
o and i use the cab analyzer(im not sure if its the same as the cab dumper u mentioned) in the core kitchen, thats how i came up with the reg entries in my .rgu file. all i did was opened the cab in the program and then clicked xml, regestry entries, and copied what was there.
thanks again
jug6ernaut said:
wow thanks alot lol, man i didnt think i could mess up that much in 1 file lol.
umm in the .rgu file you say i should use \\ instead of \ is this universal throughout the file to where i could could use the find/replace function in textpad of is it more specfic? also with the "" needing to change to @.
thanks for the quick response and all the help
Click to expand...
Click to collapse
I think in your file the \\ for \ is universal (but not positive, I didn't read every line just scanned for things I know to look for). And yea, I think everywere you have "" = you could change that to @=
Also I noticed you had a hex: entry line. Not sure that one is correct format or not.
One thing that helped me a lot was to take a cab and install it. Then go into the registry with PHM Regedit or the Regedit in TaskManager and use the Export to dump out registry entries I knew were created by that install. This will give you the proper formatting.
ok i got the regedit tool and ill work on getting the reg entries that way....
but i tried what u said with initflashfile and i got the same error as b4 about how its a directory not a file....idk what to do...
what you need is an application called Cab Manager. It will give you the reg keys. and if you buy it you will be able to do an export on the reg keys which will work perfectly on in your package
hello, i was just wondering if you guys got the OEM package working yet. i have been using the palm threader for a few days and i love it. it has been a while since the last post here and i just wanna see if its working or not. thanks in advanced and if it is working, please let me know where to get it.
I have been messing around with cooking roms for a few weeks now. I have cooked up a rom (New Att Rom) that has these numbers.
Total Storage: 166.16mb (Free 164.27mb)
Total Program: 101.38mb (Free 75.28mb)
I am trying to make this Att rom as clean as possible. I have removed abosultly everything that I can. I have a few questions though as Im being kind of a perfectionist. When I load up my rom and go into the registry I can find traces of old programs that were removed from the rom (for example transcriber or sim manager registry keys) I have edited the proxml files and they are not the curlprit. I have checked the .RGU files and there is only two in the whole rom (one is boot.rgu and the other one has only one entry in it) I have also checked the initflashfiles.dat file and edited it but it doesnt have the registry keys I am looking for either. Where is the main part of the registry in these roms?
Another question I have is why the dsm files (when opened in a text editor) show other programs or files in them. I would like to delete the microphone, clear storage and key lock app or the TTY icon in the settings screen. I have found these files in the DSM files but they cant be deleted. Is there a way to edit the dsm files or are they updated when other changes are made?
Lets say I load the stock att rom on my phone and make changes to the registry (add or remove registry settings). Then if I dump the rom, will the registry changes be saved when I use the dumped rom in cooking a new rom?
Has anyone figured out a way to get the memory back when a memory card is placed into the phone? I would be around 79mb free program memory (before speed tweaks) if someone figures this out!
I will have a few more questions probably but I cant remember them right now. The rom I have made is working very well and is stable. I just want to make sure all of the trace files in the registry and other places are gone. Thanks for the help
All of the pros must be working on their own roms, look at how many have been updated! Someone must know the answer to a few of these questions. I dont mind doing the work I just need a few hints!
hollywood said:
When I load up my rom and go into the registry I can find traces of old programs that were removed from the rom
Click to expand...
Click to collapse
Default.hv and User.hv are the default and user registries where you will find the entries.
hollywood said:
Is there a way to edit the dsm files or are they updated when other changes are made?
Click to expand...
Click to collapse
There's a app that does it in the general section under hacking IIRC search for build dsm that should bring it up.
hollywood said:
Lets say I load the stock att rom on my phone and make changes to the registry (add or remove registry settings). Then if I dump the rom, will the registry changes be saved when I use the dumped rom in cooking a new rom?
Click to expand...
Click to collapse
Yes.
hollywood said:
Lets say I load the stock att rom on my phone and make changes to the registry (add or remove registry settings). Then if I dump the rom, will the registry changes be saved when I use the dumped rom in cooking a new rom?
Click to expand...
Click to collapse
I beleave the answer to this is no... the dump you get is the unmodiffied ROM you have after flash it... all changes after this are not dumped.
Cheers.
Great info thanks guys
What program do you use to edit the default.hv and user.hv? Thanks again
hollywood said:
What program do you use to edit the default.hv and user.hv? Thanks again
Click to expand...
Click to collapse
You can not edit directly, you must convert from .HV format to REG (text) format using RGUCOMP.EXE (included in KaiserKitchen) to edit, and once edited, convert back to .HV with the same tool.
Code:
dump default.hv:
1. SET _FLATRELEASEDIR=.
2. RGUCOMP -o default.hv -nologo > default.txt
3. Add 'REGEDIT4' (first line)
4. Last line MUST be empty
5. Save as UNICODE
... edit the txt file ...
build default.hv:
1. rename default.txt to boot.rgu (same folder as RGUCOMP.exe)
2. SET _FLATRELEASEDIR=.
3. RGUCOMP -b
4. rename boot.hv to default.hv
Cheers.
Great info. I have cooked up a rom and I am having a hard time figuring out what is causing the screen delay in my registry settings. Does anyone know what setting is causing like the three second delay in the screen going from landscape to portrait? Thanks
SO if I understand you correctly.
I can open the files, edit in all of my reg edits (particularry the ones I can not export) and recompress it with RGUCOMP.EXE and cook my edits into my rom ?
Ok I tried this and finally figuted I have to do it from a command line.
WHen I do
1. SET _FLATRELEASEDIR=.
2. RGUCOMP -o default.hv -nologo > default.txt
I get fronm the txt file:
dump default.hv:
1. SET _FLATRELEASEDIR=.
2. RGUCOMP -o default.hv -nologo > default.txt
3. Add 'REGEDIT4' (first line)
4. Last line MUST be empty
5. Save as UNICODE
... edit the txt file ...
build default.hv:
1. rename default.txt to boot.rgu (same folder as RGUCOMP.exe)
2. SET _FLATRELEASEDIR=.
3. RGUCOMP -b
4. rename boot.hv to default.hv
obviously I am doing something wrong, but I have no idea what.
I have been working on a rom based on the rogers 1.83 release.
I hit a snag during a recent change. I was replacing the .netcf 2.0 to .netcf 3.5 and SqlCeMobile 3.0 to SqlCeMobile 3.5.
My problem is it looks like none of the .provxml files are running after hard boot. (Did a second hard boot after I each flash test.)
If I cold boot the phone it loads fine and runs the configuration files to load the themes and cabs and then reboots. I have the SDAutorun installed and that also seems to run then reboot (i do not have a sdconfig.txt defined on storage card.)
To try and debug
I did a test as suggested in the uc thread:
I took an original provxml file (mxipupdate_oemoperators_105.provxml), renamed it to _setup.xml. It loads in the browser fine.
Ran this command to make it a test cab file.
"cabarc n test.cab _setup.xml" (is this syntax correct?)
ran it on the phone but install is unsuccessful.
Can someone tell me if either app plays in the running of the .provxml files or if not what program run it? The configuration routines run fine for loading the startup cabs, themes etc.
Any other hints as to why none of the provxml files run? I could roll it back and start over but it would be great if someone has a suggestion.
Thanks for whatever suggestions come my way.
well....all i can say is...your probably in for many trial and errors with this issue. I'll try my best to explain this to you. I myself had this very same issue when 1st cooking kaiser roms. 1st of all, make sure your running the latest kitchen. 2nd, try to get an understanding of how the xml\provxml are structured. Provxml and .xml files are very sensative to changes made in the rom. You need to make sure that files in the rom and the referenced files in provxml and xml are edited accordingly. for example: If you delete a .wma file that has been called up and placed into a specific folder by the .provxml/xml file, then you need to make sure you edit out the instructions in the xml\provxml. If you dont then the xml\provxml file will still try looking for the referenced file that you deleted and once it cannot be found then, the customizations stops and leaves you with an incomplete customization setup! Hopefully this will help you.
provxml's not executing
Thanks for responding. As a test I put back the original provxml files. My changes were minor anyways, mostly just changing some of the default values (such as renaming rogers.gif to animated.gif).
Anyhow same result with the originals.
Maybe as a test i will try removing all but one provxml file and see if it runs. if not then perhaps I didnt get the .net3.5 installed correctly. I havent been using the kitchens directly, just baseing the add-ons from the packages. This has worked well until recently.
Last night I re-did the whole upgrading/stripping of the rom from scratch with the same result so at least i am consistent hehe.