Related
Ok heres my dilema:
I wan't to cook in loads of manila files, but theres a few different versions of each one, and they aren't going into windows.
its better I explain it, heres an example:
Root Folder
\Folder 1
¬FileX
\Folder 2
¬FileX
\Folder 3
¬FileX
How can I do this? is I cant put the same file (FileX) in the files folder of a package as it has the same file name... The only way I can think of is to have a seperate package for each invidual file, and considering theres over 40 files, its going to take a long time!
Are there anymore efficient ways to do this? Thanks
SOLVED: AIRXTREME HAS MADE A UTILITY FOR CHEFS TO FIX THIS VERY PROBLEM:
[GET IT HERE]
THANKS AIRXTREME!!!
[★] said:
Ok heres my dilema:
I wan't to cook in loads of manila files, but theres a few different versions of each one, and they aren't going into windows.
its better I explain it, heres an example:
Root Folder
\Folder 1
¬FileX
\Folder 2
¬FileX
\Folder 3
¬FileX
How can I do this? is I cant put the same file (FileX) in the files folder of a package as it has the same file name... The only way I can think of is to have a seperate package for each invidual file, and considering theres over 40 files, its going to take a long time!
Are there anymore efficient ways to do this? Thanks
Click to expand...
Click to collapse
If all these files go into "\Windows", there will be only one in the end ... not 40. Meaning the last "FileX" your kitchen finds will have overwritten all the others ...
You can't end up with all these files, without doing a little bit of legwork.
When you cook a ROM, all the files end up in \Windows, and are then moved around as required.
So, you could either cook all the files in with different names (so they don't overwrite) and then move them using a provxml or initflashfiles.dat, or you could cab up all the files, and run the cab after first boot.
The easiest way is to use a cab or to put everything in a zip file and use an 'inzipall' mortscript to unzip the folders wherever you want during customization.
Diegis0n said:
If all these files go into "\Windows", there will be only one in the end ... not 40. Meaning the last "FileX" your kitchen finds will have overwritten all the others ...
Click to expand...
Click to collapse
Yeah thats what I thought , althought I didnt know they went into windows first, thanks.
l3v5y said:
You can't end up with all these files, without doing a little bit of legwork.
When you cook a ROM, all the files end up in \Windows, and are then moved around as required.
So, you could either cook all the files in with different names (so they don't overwrite) and then move them using a provxml or initflashfiles.dat, or you could cab up all the files, and run the cab after first boot.
Click to expand...
Click to collapse
Hmm the cab sounds like a good aproach, although still I wouldn't be able to have more than one manila file with the same name in the cab.
Farmer Ted said:
The easiest way is to use a cab or to put everything in a zip file and use an 'inzipall' mortscript to unzip the folders wherever you want during customization.
Click to expand...
Click to collapse
hmm thats a good idea, could you point me to that script please
[★] said:
Yeah thats what I thought , althought I didnt know they went into windows first, thanks.
Hmm the cab sounds like a good aproach, although still I wouldn't be able to have more than one manila file with the same name in the cab.
Click to expand...
Click to collapse
Cab files do allow you to specify the paths, so they do allow you to have files with the same name. WinCE CAB Manager is a good choice to create cabs. You can then use RunCC / Autorun/ XDA_UC to install it during the first boot.
[★] said:
hmm thats a good idea, could you point me to that script please
Click to expand...
Click to collapse
Just take a look at this package; it has a zip file, a mortscript, and the add2config that you need. Here's a mortscript package that you can use.
You could also rename the files for example "1_FileX", "2_FileX" and have initflashfiles.dat rename it to the filename you want it to be, like so:
Directory("\Folder_1"):-File("FileX","\Windows\1_FileX")
Directory("\Folder_2"):-File("FileX","\Windows\2_FileX")
Click to expand...
Click to collapse
But that would really clog up your ROM, so the mortscript way is better.
ock said:
Cab files do allow you to specify the paths, so they do allow you to have files with the same name. WinCE CAB Manager is a good choice to create cabs. You can then use RunCC / Autorun/ XDA_UC to install it during the first boot.
Click to expand...
Click to collapse
Yes but putting the files in will overwrite eachother, as they have to have the same file name
Farmer Ted said:
Just take a look at this package; it has a zip file, a mortscript, and the add2config that you need. Here's a mortscript package that you can use.
Click to expand...
Click to collapse
Thanks I dont understand what the mortscript for is (the one from 4shared) but Im using the add2config package, I think I get it I will let you know when its finished cooking. Although I am having a problem where none of my add2config packages are working so it might be useless
seeM_ZA said:
You could also rename the files for example "1_FileX", "2_FileX" and have initflashfiles.dat rename it to the filename you want it to be, like so:
But that would really clog up your ROM, so the mortscript way is better.
Click to expand...
Click to collapse
Yeah but the files have to keep the same name
You need mortscript support cooked into your rom one way or another if you're going to use zip files; that's what the 4shared package is for.
l3v5y said:
So, you could either cook all the files in with different names (so they don't overwrite) and then move them using a provxml or initflashfiles.dat
Click to expand...
Click to collapse
+1 for this...
ai6908 said:
+1 for this...
Click to expand...
Click to collapse
That's ok if you're talking a couple of files, but if you're talking a few dozen (or more), then putting together all the initflashes scripts will get tedious.
Farmer Ted said:
That's ok if you're talking a couple of files, but if you're talking a few dozen (or more), then putting together all the initflashes scripts will get tedious.
Click to expand...
Click to collapse
Did you get my message?
and yeah, it seems your mortscript may be easier If I can get add2config to work lol
SOLVED: AIRXTREME HAS MADE A UTILITY FOR CHEFS TO FIX THIS VERY PROBLEM:
[GET IT HERE]
THANKS AIRXTREME!!!
Hi all!
I searched a lot on that topic an coocked loads of roms (for XPERIA/Kovsky/Venus) for testing purpose...But I cannot find a solution for that.
All my recently cooked ROMS (several Builds) are missing root certificates, I only have each two from HTC and Sony Ericsson in Setings. What went Wrong? where to find them? I thought to have found them in the following provxml's which actually is not the case I found out... (see below)
<old> Here is my problem. Build 23541 is seemingly (at least for me) missing root certificates. I managed to figure out they are included in a provxml called mxip_wpc_3.provxml. So I copied that one from a official LEO ROM (Build 21***) and did not change anything. After flash I can find it located in \Windows\ but the certificates are not appearing in Settings.
Now I now that provxmls need to be in UTF-8 format and set to read only, hidden and system. That ist tha case with this specific file. So what's wrong? </old>
I hope that someone can help me with that topic cause I have no other idea now.
Thanks A lot guys!
Hilaireg put together a really good tutorial om provxml's. Look it up, it may help. And make sure NET CF is cooked in (just a guess).
I guess you don't have that provxml added to any of dsm files . Just use this tool and add it to any of dsm files.
http://forum.xda-developers.com/showthread.php?t=523139
You can also use xml parser to check if file is good, for example Serna Editor.
tomcug said:
I guess you don't have that provxml added to any of dsm files . Just use this tool and add it to any of dsm files.
http://forum.xda-developers.com/showthread.php?t=523139
You can also use xml parser to check if file is good, for example Serna Editor.
Click to expand...
Click to collapse
Do you happen to know if that is needed too with platformrebuilder?
I've never worked with it but my guess is that you won't have to manually add provxml to dsm files.
Farmer Ted said:
Hilaireg put together a really good tutorial om provxml's. Look it up, it may help. And make sure NET CF is cooked in (just a guess).
Click to expand...
Click to collapse
Must be talking about this thread: http://forum.xda-developers.com/showthread.php?t=519548 Found it, thanks, very interesting indeed...this one will go into my bookmarks
Anyway, as i just copied the files from a working ROM I don not think something is wrong with them...
tomcug said:
I guess you don't have that provxml added to any of dsm files . Just use this tool and add it to any of dsm files.
http://forum.xda-developers.com/showthread.php?t=523139
You can also use xml parser to check if file is good, for example Serna Editor.
Click to expand...
Click to collapse
Thnkas as well, Layout is probably good, as the are woring in that LEO ROM.
I will look a bit deeper in your link, this sounds like the right way.
Are there other sugestions?
tomcug said:
I guess you don't have that provxml added to any of dsm files . Just use this tool and add it to any of dsm files.
http://forum.xda-developers.com/showthread.php?t=523139
You can also use xml parser to check if file is good, for example Serna Editor.
Click to expand...
Click to collapse
Tryed that now...But it did not help! Considering the xml is good (as it is working in a leo ROM) what else opportunities are there?
EDIT: Tried to import the provxml's (mxip_wpc_2.provxml and mxip_wpc_3.provxml) using AdvancedConfig but with no luck. Wondering...
Rename the file ZZZmxip_wpc_3.provxml and try again. EVK processes .provxml files in alphabetical order. If a directory referenced in the above .provxml is not created by a previously processed .provxml, then the modifications will not be applied.
I guess you are referring to this thread: http://forum.xda-developers.com/showthread.php?t=707717
From what I understand (probably very little) your provxml got executet too early as one shortcut was not yet present in the startmenu, so it stopped, right? With my files they do not depend on other files / reg values as these are just certificates...anyway, lets see
I will do so now, but I also tried to build a clean (no EXT) ROM from 23563 Rollup thread by Da_G and had the same problem! This is starting to get starnge...Will report in about 30 mins.
EDIT: Renaming did not help. Starting to get frustrated...
EDIT2: Even converting that provxml to a cab did not work. Am I looking in the wrong place?
Yes that thread, some ppl said that you need to edit the OEMs dsm where you add the provxml and add the provxml into it, dunno if it works... another one is... when a provxml fails in a corrupted line the next lines dont be executed but the before lines were set... so maybe the dirty way can works for you... if not works... your provxml is wrong in that thread many ppl said something about using a tool to see if the provxml is ok try them too
the dirty way to make it is... ad the provxml lines in your provxml to any other provxm... remember to keep the same attributes in that provxml.
+ Que PPC said:
Yes that thread, some ppl said that you need to edit the OEMs dsm where you add the provxml and add the provxml into it, dunno if it works... another one is... when a provxml fails in a corrupted line the next lines dont be executed but the before lines were set... so maybe the dirty way can works for you... if not works... your provxml is wrong in that thread many ppl said something about using a tool to see if the provxml is ok try them too
the dirty way to make it is... ad the provxml lines in your provxml to any other provxm... remember to keep the same attributes in that provxml.
Click to expand...
Click to collapse
trying the dirty way now.
I checked the provxml using a provxml2cab converter which usualy gives an error on bad files. And I am using Notepad++ which makes chacking quite easy. Than again, it comes from a official ROM and was not modified...
EDIT: Nope, not included!
what does that provxml has inside? some icons arrangement? or shortcuts?
Root certificates. both are attached below.
Are you using oskitchen alpha? There have been some problems with provxml not running (hence the alpha) but alpha5 should be fine.
Not sure? Its the NewUI Version and one of the last ones with the old folder structure (I think 1.27 or so)
derliebewolf said:
Not sure? Its the NewUI Version and one of the last ones with the old folder structure (I think 1.27 or so)
Click to expand...
Click to collapse
It was a problem specific only to the 1.31 alphas. Make sure the provxml files have the three attributes set (hidden, read-only and system), that could be the cause of the issue.
I am pretty sure the attributes are stet as you say.
If dirty way doesn't work, then I'm pretty sure it's something wrong with provxml file.
derliebewolf said:
I am pretty sure the attributes are stet as you say.
Click to expand...
Click to collapse
The only real way to find out is to set oskitchen to stop before imgfs generation or setting LZX and going quickly in the platformrebuilder temp\dump folder while it's generating IMGFS and using the ATTRIB command on the files in the dump folder to see what attributes those end up with. If all those three attributes aren't set the files won't run.
I'm pretty sure I've had provxml file with no attributes and it worked perfectly, but maybe I'm wrong .
First of all, sorry for openeing a new thread; but surely i have searched all of chef central din't find anything much or maybe din't understand which one was my solution.
The problem is after boot of my ROM ( regardless of which boot ie 1st 2nd or 10th ) i get 2 pop up errors:
1) "The file 'programs' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found.If the problem persists please try reinstalling or restoring this file."
2) "The file 'Tools' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found.If the problem persists please try reinstalling or restoring this file."
I have a folder called "Tools" in the start menu, and it works fine, and everything inside also works good. But still this error.
I'm pretty sure all the Packages cooked which are meant to go in this folder do go in.
And the programs error is it anything to do with the fact that in the APP.DAT in almost all packages i have used similar naming:
Code:
Directory("\Windows\Start Menu\Programs"):-Directory("System")
Directory("\Windows\Start Menu\Programs\Tools\Tweaks"):-File("Flip_IT.lnk","\Windows\_Flip_IT.lnk")
and also added similar REG in the REGS :
[HKEY_LOCAL_MACHINE\Security\Shell\StartInfo\Start\Tools\Tweaks\Flip_it.lnk]
Click to expand...
Click to collapse
As i was not sure which one will decide the location, so some packages have only .REGs, some have only APP.DATs and some have both ( but all the locations are same that is sure !)
Please help me with this.
Thanks alot.
PS: I have enabled NoCert in EVK, and also cooked in the latest ( 2015 ? ) SDKCerts EXT. And after that no other apps give an unsigned problem.
Just a question, this isnt the full app.dat right?
Code:
Directory("\Windows\Start Menu\Programs"):-Directory("System")
Directory("\Windows\Start Menu\Programs\Tools\Tweaks"):-File("Flip_IT.lnk","\Windows\_Flip_IT.lnk")
If yes, you miss some lines,this app.dat is just copying a link to startmenu but i guess that you need the program in Windows.
i'm afraid that is the full App.DAT
here is another one
Code:
Directory("\Windows\Start Menu\Programs"):-Directory("System")
Directory("\Windows"):-Directory("appdb")
Directory("\Windows\appdb"):-File("_end_mid_2.png","\Windows\_end_mid_2.png")
Directory("\Windows\appdb"):-File("_end_mid_8.png","\Windows\_end_mid_8.png")
Directory("\Windows\appdb"):-File("_folder_2.png","\Windows\_folder_2.png")
Directory("\Windows\appdb"):-File("_folder_8.png","\Windows\_folder_8.png")
Directory("\Windows\appdb"):-File("_folder_8_2.png","\Windows\_folder_8_2.png")
Directory("\Windows\appdb"):-File("_lock_gray.png","\Windows\_lock_gray.png")
Directory("\Windows\appdb"):-File("_lock_green.png","\Windows\_lock_green.png")
Directory("\Windows\appdb"):-File("_lock_red.png","\Windows\_lock_red.png")
Directory("\Windows\appdb"):-File("_logo_2.png","\Windows\_logo_2.png")
Directory("\Windows\appdb"):-File("_single_2.png","\Windows\_single_2.png")
Directory("\Windows\appdb"):-File("_single_8.png","\Windows\_single_8.png")
Directory("\Windows\appdb"):-File("_start_2.png","\Windows\_start_2.png")
Directory("\Windows\appdb"):-File("_start_8.png","\Windows\_start_8.png")
Directory("\Windows\appdb"):-File("_suite_2.png","\Windows\_suite_2.png")
Directory("\Windows\appdb"):-File("_suite_8.png","\Windows\_suite_8.png")
Directory("\Windows\appdb"):-File("_ack_2.png","\Windows\_ack_2.png")
Directory("\Windows\appdb"):-File("_ack_8.png","\Windows\_ack_8.png")
Directory("\Windows\appdb"):-File("_compiling.png","\Windows\_compiling.png")
Directory("\Windows\appdb"):-File("_disable_2.png","\Windows\_disable_2.png")
Directory("\Windows\appdb"):-File("_disable_8.png","\Windows\_disable_8.png")
Directory("\Windows\appdb"):-File("_dt_2.png","\Windows\_dt_2.png")
Directory("\Windows\appdb"):-File("_dt_8.png","\Windows\_dt_8.png")
Directory("\Windows\appdb"):-File("_dukeok_2.png","\Windows\_dukeok_2.png")
Directory("\Windows\appdb"):-File("_dukeok_8.png","\Windows\_dukeok_8.png")
Directory("\Windows\appdb"):-File("_empty.png","\Windows\_empty.png")
Directory("\Windows\appdb"):-File("_end_ams_2.png","\Windows\_end_ams_2.png")
Directory("\Windows\appdb"):-File("_end_ams_8.png","\Windows\_end_ams_8.png")
Directory("\Windows\appdb"):-File("_logo_8.png","\Windows\_logo_8.png")
Directory("\Windows\Start Menu\Programs\\Tools\System"):-File("Java.lnk","\Windows\Java.lnk")
This seems to be correct right ?
Can you please tell me does APP.DAT decide the position or REG ? and what if both exist.
Thanks.
Can an incomplete app.dat cause those errors ?
EDIT: i have identified 3 packages have incomlete app.dat
1) task manager
app.dat says :
Directory("\Windows\Start Menu\Programs\Tools\"):-File("Task Manager.lnk","\Windows\dotFred Task Manager.lnk")
Directory("\Windows\Start Menu\Programs\Tools\Utilities"):-File("Regeditor.lnk","\Windows\dotFred RegEdit.lnk")
Click to expand...
Click to collapse
reg also defines a location.
2) flip it
app.dat says
Directory("\Windows\Start Menu\Programs"):-Directory("System")
Directory("\Windows\Start Menu\Programs\Tools\Tweaks"):-File("Flip_IT.lnk","\Windows\_Flip_IT.lnk")
Click to expand...
Click to collapse
reg defines location and settings.
3) torch
app.dat says
Directory("\Windows\Start Menu\Programs\Tools\Utilities"):-File("hTorch Flashlight.lnk","\Windows\hTorch Flashlight.lnk")
Click to expand...
Click to collapse
reg defines settings only.
4) reg editor
app.dat says:
Directory("\Windows\Start Menu\Programs\Tool\Utilities"):-File("PHM RegEdit.lnk","\Windows\PHM RegEdit.lnk")
Click to expand...
Click to collapse
reg defines sttings and location.
Can anyone of the above cause the issue ?
can some please help me correct them ?
Thanks.
EDIT: can someone please tell me the REG to enable Call Waiting Tone.
I don't hear any tone it when i have a call waiting.
The app.dat decide the position of file and folders.
I found thi " Flip-IT" from a Tom Codon thread and i used Cab Converter for extracting it.
This is the App.dat that i got:
Directory("\Windows\Start Menu\Programs\Tools"):-File("Flip_IT.lnk","\Windows\Flip_IT.lnk")
Click to expand...
Click to collapse
In red are the subfolders that doesnt come with the original.
There are some difference with your but i dunno if this is the problem but worth try.
Umm well i have defined those locations as to fit them lnk in the place i want in the start menu.. isn't that the way ?
Im Quoting you from 1st post:
1) "The file 'programs' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found.If the problem persists please try reinstalling or restoring this file."
2) "The file 'Tools' cannot be opened. Either is not signed with a trusted certificate or one of it's components cannot be found.If the problem persists please try reinstalling or restoring this file."
you got this popup error automatically, no need to open any folder\file?
It seems that you put a wrong shortcut to files called "Tools and programs" in your StratUp folder.
Check some other App.dat
i have checked all APP.DAT in the EXT can't find any which i cook and does not get cokked in the correct location ?
Umm and the two errors are seperate not in one only.
So i guess the conflict is there with 2 seperate folders "Tools" and "programs" respectively.
Ideally it should not conflict with tools, because i do have a tools folder in the start menu.. so everything should go there :/
any other help?
Try to cook a rom without one of the latest apps that you have add and if the problem gone then you have find the issue,after that post here the responsable so we can look at it.
madnish30 said:
i have checked all APP.DAT in the EXT can't find any which i cook and does not get cokked in the correct location ?
Umm and the two errors are seperate not in one only.
So i guess the conflict is there with 2 seperate folders "Tools" and "programs" respectively.
Ideally it should not conflict with tools, because i do have a tools folder in the start menu.. so everything should go there :/
any other help?
Click to expand...
Click to collapse
af974 said:
Try to cook a rom without one of the latest apps that you have add and if the problem gone then you have find the issue,after that post here the responsable so we can look at it.
Click to expand...
Click to collapse
I'll try and cook without the 5 EXT i identified with wrong app.dats ?
I have had this problem since long, but i din't bother much, so i really don't know whats the issue..
it has been there basically since i tweaked the start menu locations.
now i have to get rid of it cuz any ROM user won't like to just press ok and continue with the ROM.
I'll try.
My suggestion is to try one by one but ofcourse this way you need to flash 5 times your phone.
Did you ,maybe,tweaked your Initflashfile.dat?
madnish30 said:
I'll try and cook without the 5 EXT i identified with wrong app.dats ?
I have had this problem since long, but i din't bother much, so i really don't know whats the issue..
it has been there basically since i tweaked the start menu locations.
now i have to get rid of it cuz any ROM user won't like to just press ok and continue with the ROM.
I'll try.
Click to expand...
Click to collapse
No i don't play with initiaflash... because i don't know much about it..
I guess i will not cook anyone of them so that if its one of them i will just download fresh CABs for them and convert them into EXTs rather than flashing my phone 5 times..
Thanks alot.
i tried cooking without those apps no luck
Same 2 errors hence those 2 apps are ok..
Attached my Initflashfile.dat if that helps.
Please help.
You really need to look in your startup folder to see what is in there. That's the first thing to do. Then, look in the start menu and see if anything weird is going on. Particularly, look for corrupted files or folders. If there are any files that look like folders, that could be the issue.
You're initflashfiles.dat is effin' huge!! Learn to make a cab, or relocate apps to windows. You must be wasting a ton of storage space.
thanks for the help Ted,
In the startup i see 2 folders
1) programs in which there is tools->system->Arkswitch.
2) tools -> system -> XDA_UC.
rest are the normal i guess.
Then in the startmenu it seems fine.
but one problem there i see in the start menu i see a system folder which is empty AFAIK i did not create and such path why is that there ?
You're initflashfiles.dat is effin' huge!! Learn to make a cab, or relocate apps to windows. You must be wasting a ton of storage space.
Click to expand...
Click to collapse
I'm not good with initflashfiles.dat i don't know much about it.
Can you please link me to a thread where i can learn about it.
Also what do you mean by CABs ? does that mean using UC to install via CABs ?
And how can i reloacte apps to windows ?
can you give a little explaination please.
thanks alot for the help.
The app.dat for Arksswitch is
Directory("\Windows"):-Directory("StartUp")
Directory("\Windows\Start Menu\Programs"):-Directory("Tools")
Directory("\Program Files"):-Directory("ArkSwitch")
Directory("\Program Files\ArkSwitch"):-Directory("Theme")
Directory("\Program Files\ArkSwitch"):-Directory("NLS")
Directory("\Program Files\ArkSwitch\NLS"):-File("1033.xml","\Windows\1033.xml")
Directory("\Program Files\ArkSwitch\NLS"):-File("1036.xml","\Windows\1036.xml")
Directory("\Program Files\ArkSwitch\NLS"):-File("1040.xml","\Windows\1040.xml")
Directory("\Program Files\ArkSwitch\NLS"):-File("1049.xml","\Windows\1049.xml")
Directory("\Program Files\ArkSwitch\Theme"):-File("config.xml","\Windows\config.xml")
Directory("\Program Files\ArkSwitch\Theme"):-File("status-bar.png","\Windows\status-bar.png")
Directory("\Program Files\ArkSwitch\Theme"):-File("x-deselected.png","\Windows\x-deselected.png")
Directory("\Program Files\ArkSwitch\Theme"):-File("x-selected.png","\Windows\x-selected.png")
Directory("\Program Files\ArkSwitch"):-File("Microsoft.WindowsMobile.Gestures.dll","\Windows\Microsoft.WindowsMobile.Gestures.dll")
Directory("\Program Files\ArkSwitch"):-File("ArkSwitch.exe","\Windows\ArkSwitch.exe")
Directory("\Program Files\ArkSwitch"):-File("ArkSwitchNative.dll","\Windows\ArkSwitchNative.dll")
Directory("\Windows\Start Menu\Programs\Tools\System"):-File("ArkSwitch.lnk","\Windows\_ArkSwitch.lnk")
Directory("\Windows\StartUp\Programs\\Tools\System"):-File("ArkSwitch.lnk","\Windows\_ArkSwitch.lnk")
Click to expand...
Click to collapse
and the app.dat for XDA_UC is
Directory("\Windows\StartUp\Tools\System"):-File("XDA_UC.mscr","\Windows\XDA_UC.mscr")
Click to expand...
Click to collapse
Please help me correct the two in order to remove the warning.
Will try and cook without them to see if they cause they problem.
I don't use xda_uc, but delete the sub-folders in startup and the problems go away.
App.dat copies files from windows to other places. In many cases, an app works fine in windows. You just need to fix paths (shortcuts, registry) so they point to windows. It's a complete waste to have two copies of all your files, especially when the ones in rom work perfectly fine. Personally, I don't even use app.dat's, except to create directories and to copy the important customization links into startup.
Edit: ok, so I'm looking at your initflashfiles.dat. One, there's something weird with your Manila twitter lines. Why does it appear twice? That's kind of a waste, and will slow down 1st boot. Also, you've got a dozen mui files in there. Just put in the one you need (0409 or whatever), and delete the rest. You've to two copies of a bunch of files that you don't use. Remove the lines you don't need from the app.dat.
As far as relocating apps, you've got 20 or so that would work fine in windows. For example, clean ram does not have to be in program files. Just leave the exe's in windows, and send 1 lang file to \windows\lang. The app will work fine. Do you really need 20 lang files for cleanram? Dude, that's a total waste.
Here's an easy one to fix: pocket rar. You've got two copies of it now on your device. Just get a shortcut for it to windows, and you're done. You stick rar.exe in a package, along with the shortcut, and send the shortcut to the start menu as normal. Speaking of which, it looks like you've got a syntax error there:
Directory("\Windows\Start Menu\Programs\\Tools\System"):-File("Pocket RAR.lnk","\Windows\_Pocket RAR.lnk")
Click to expand...
Click to collapse
Get rid of the extra \.
Thanks sir i got it, now i will impliment it.
Sir if you don't use app.dats then how do you chose which package shows up where in the start menu ?
I do pretty much everything with morscripts. I put all files and directories in zip files that are unzipped during customization, and all shortcuts are created by a script. This reduces the rom file count by hundreds (I have about 1800 rom files), and the zip files reduce the storage memory for files that have to be inserted elsewhere. There's also a restore script that resores files that change a lot and that aren't practical to cook in.
Anyway, were I you, I'd work on fixing all of your packages to make the rom more efficiently designed (instead of worrying about upgrading build numbers). I bet you could removed 500 files and clean up a crazy amount of memory (like 50 mb). It can be tricky moving an app to windows. Some apps have .ini files or similar settings files, and the app will crash or not load if the setting file is read-only, so you need to get the file into windows without having it read only (do it with an app.dat that copies or renames it to windows). Some apps have their settings in the same damn file name (like settings.txt), so you can't have them both in the same directory.
To relocate to windows, almost anything in the root program folder (like \program files\cleanram) can be moved straight to windows. Sub-folders generally just need to be moved to \windows. Typically, an exe looks for .dlls first in its own directory and second in \windows, so just about any dll can be moved to windows without issue. It will then usually look for the support files in the same directory that it's located in. The only apps I've had problems with are resco keyboard (the skin files seem to be hard coded to program files), and the latest Power Radio (2.4.0.2, or something like that). I had a bunch of power radio packages that worked fine in windows, but the latest wouldn't, so I just didn't do the upgrade.
It's usually easiest just to test things without cooking. In your case, you've already got everything in windows. Just click on exes and see what works and what doesn't. Some apps will need sub-folders relocated to windows, and it looks like your cab-to-ext package unfortunately renamed the rom files, so some files in the program folder will need to be copied to windows. Just do this for testing purposes, to see what works and what doesn't. I bet your rom is effin huge, and you could make it a lot leaner by cleaning your packages up. The cab-to-ext makers all more or less suck; it's better to do things manually (or with kheb 1.1).
Edit: you've got the tachan black theme in there twice, too. You really, really don't need those files copied elsewhere. I'm guessing there's a reg file with all the file locations (in HKCU\Software\Microsoft\Today). Fix it!!! All you need to do is do a 'replace all' and replace \\My Documents\\Themes\\tacchan23black with \\windows. Then delete that gawdawful app.dat file (both occurrences). That will remove 101 redundant files.
Do you remember this from your 1st post?
Directory("\Windows\Start Menu\Programs"):-Directory("System")
Directory("\Windows\Start Menu\Programs\Tools\Tweaks"):-File("Flip_IT.lnk","\Windows\_Flip_IT.lnk")
Click to expand...
Click to collapse
Here is (marked in red) your System folder (empty) in startmenu.
madnish30 said:
Then in the startmenu it seems fine.
but one problem there i see in the start menu i see a system folder which is empty AFAIK i did not create and such path why is that there ?
Click to expand...
Click to collapse
Thanks ted & af974.
i will try to do things you suggested.
But Ted, what does the attachment mscr do ?
I attached and EXT package from Chucky's Rom thanks to birkoffsjunk, i guess you will understand what mscr does looking at it.
madnish30 said:
Thanks ted & af974.
i will try to do things you suggested.
But Ted, what does the attachment mscr do ?
Click to expand...
Click to collapse
I tried to keep the title as descriptive and short as possible, I hope it makes sense
I picked up the kitchen of nhathoa (a retired Topaz cook) hoping to get it customized to make it exactly the way I want but I'm running into some issues.
Long story short, I'm using Ervius Visual Kitchen (1.8.2) and I noticed that the EXT packages I added end up leaving two copies of the files, a copy under \windows\ and another one in the places I specified using app.dat using:
Code:
Directory("\Program Files\bla\"):-File("bla.exe","\Windows\bla.exe")
Is there some way to get rid of the copy under \Windows\ ??
I know that I could simply leave everything there and discard the app.dat files but I would really prefer having everything organized properly (I have a bit of an OCD when it comes to organizing everything neatly ).
I'm pretty sure that this is a rather simple and noobish issue but I couldn't find anything relevant by searching and I took a look at some ext packages by various cooks and noticed the same behaviour.
MusikMonk said:
I tried to keep the title as descriptive and short as possible, I hope it makes sense
I picked up the kitchen of nhathoa (a retired Topaz cook) hoping to get it customized to make it exactly the way I want but I'm running into some issues.
Long story short, I'm using Ervius Visual Kitchen (1.8.2) and I noticed that the EXT packages I added end up leaving two copies of the files, a copy under \windows\ and another one in the places I specified using app.dat using:
Code:
Directory("\Program Files\bla\"):-File("bla.exe","\Windows\bla.exe")
Is there some way to get rid of the copy under \Windows\ ??
I know that I could simply leave everything there and discard the app.dat files but I would really prefer having everything organized properly (I have a bit of an OCD when it comes to organizing everything neatly ).
I'm pretty sure that this is a rather simple and noobish issue but I couldn't find anything relevant by searching and I took a look at some ext packages by various cooks and noticed the same behaviour.
Click to expand...
Click to collapse
No, it's call Read-Only-Memory (ROM) and is the reason you can hard-reset your phone. Every file you cook into the ROM is in \windows. Two ways I know of to reduce the amount of files would be to zip them and have a mortscript unzip them to the proper location during customization or cook in a cab containing all of the files and have it run during customization.
That makes a lot of sense, I really feel ashamed that I didn't figure it out earlier
EXT packages seemed easier than bothering to read about customization but I guess it's time to start reading about this kind of stuff.
Thread marked as solved.
Thanks for the quick reply!
Yup, files in rom are in rom forever, or until you flash again, lol. The trick is to just run bla.exe from \windows. I would say that 90% of the time, bla.exe runs just fine out of the windows directory (especially if it's the only file in the package). When people create cabs, they naturally install the app in \program files, but in general apps don't need to be in a specific folder. If there are other files present, usually an .exe will search within its own folder for those files. So, if you just cook everything straight into windows, you'll be good to go. It's easy enough to test: just move all the files from program files to windows after installing a cab, fix the shortcut in the start menu, and then try to run the app. It's always a good idea to do a soft reset and try again (found this out the hard way many times). The one thing you have to watch out for is settings files, like .dat files. These files frequently have to be archived (not read-only). Particularly with apps that use net 3.5, if there's a setting file that is read-only, the app won't boot and you'll get an error message. The fix is to name the file settings-1.txt (or whatever) and have an app.dat rename it to settings.txt (and keep it in \windows).
Also, remember to fix the shortcut path in the start menu, and examine the registry entries to see if there are any paths for files present-you may need to change them to point to \windows (this could also be true in settings files).
mwalt2 said:
No, it's call Read-Only-Memory (ROM) and is the reason you can hard-reset your phone. Every file you cook into the ROM is in \windows. Two ways I know of to reduce the amount of files would be to zip them and have a mortscript unzip them to the proper location during customization or cook in a cab containing all of the files and have it run during customization.
Click to expand...
Click to collapse
This actually made me think a little bit. When you think about read only, I always thing can't delete or overwrite. Obviously I can run a cab and replace a file that is located in the \Windows directory, that leads me to believe there is a way to delete a file or maybe even replaced with an empty file of the same name.
You can over-write a rom file, but the rom file is still there. The file system just flags it somehow or another and tells the device to ignore it and instead use the new file.
TMartin03 said:
This actually made me think a little bit. When you think about read only, I always thing can't delete or overwrite. Obviously I can run a cab and replace a file that is located in the \Windows directory, that leads me to believe there is a way to delete a file or maybe even replaced with an empty file of the same name.
Click to expand...
Click to collapse
The new file you copy over goes into the "user" partition of the file system and windows knows to use that file instead. Once you delete this newly copied file from \windows, the old one from the ROM will take its place back in the filesystem.
Farmer Ted said:
Yup, files in rom are in rom forever, or until you flash again, lol. The trick is to just run bla.exe from \windows. I would say that 90% of the time, bla.exe runs just fine out of the windows directory (especially if it's the only file in the package). When people create cabs, they naturally install the app in \program files, but in general apps don't need to be in a specific folder. If there are other files present, usually an .exe will search within its own folder for those files. So, if you just cook everything straight into windows, you'll be good to go. It's easy enough to test: just move all the files from program files to windows after installing a cab, fix the shortcut in the start menu, and then try to run the app. It's always a good idea to do a soft reset and try again (found this out the hard way many times). The one thing you have to watch out for is settings files, like .dat files. These files frequently have to be archived (not read-only). Particularly with apps that use net 3.5, if there's a setting file that is read-only, the app won't boot and you'll get an error message. The fix is to name the file settings-1.txt (or whatever) and have an app.dat rename it to settings.txt (and keep it in \windows).
Also, remember to fix the shortcut path in the start menu, and examine the registry entries to see if there are any paths for files present-you may need to change them to point to \windows (this could also be true in settings files).
Click to expand...
Click to collapse
First of all, a small question about the underlined part, just to make sure that I got it right: it won't be exactly a rename just a copy with a different name, correct?
Some of the apps I use need a specific directory structure for the resources and files they use, so just dumping them in one big folder won't work.
Another possible issue that I think I'll run into is having two files sharing a generic name (let's say settings.xml) while each belongs to a different app. I didn't personally encounter such a situation just yet but my packages are still a work in progress and I did see a post or two about this while searching.
I was still hoping there would be a simple way to arrange the files in folders while keeping them under \windows\ but I can't find such a method either. Doesn't seem like I have other options than to decided on a firstboot customization method: Runcc, autorun, xda_uc or something that I haven't read about yet...
"Runcc" is currently used in the base kitchen so that gives it an edge right now.
Edit:
Remembered that I had another question, and it's probably not worth a new thread.
I was looking at how to manually create .lnk files and I noticed something that I didn't understand and couldn't find info about.
For example:
Code:
21#"\Windows\MSDict.htm"
What exactly does the "21" refer to?? I tried changing it randomly to other values a couple of times and it didn't effect anything.
NRGZ28 said:
The new file you copy over goes into the "user" partition of the file system and windows knows to use that file instead. Once you delete this newly copied file from \windows, the old one from the ROM will take its place back in the filesystem.
Click to expand...
Click to collapse
Ok now that makes a lot of sense. I guess I'm just use to Android and being able to see that separate partition. Thanks for the explanation.
That sort of leaves me to another question. Can't someone develop a way to overwrite directly to the "system" partition? It would almost be like a root/superuser for WinMo.
Sent from my HTC Evo 4G!
MusikMonk said:
First of all, a small question about the underlined part, just to make sure that I got it right: it won't be exactly a rename just a copy with a different name, correct?
Click to expand...
Click to collapse
Yup, that's correct. Another approach is to take all similar files that go into windows and stick them in a zip file that unzips to the windows directory. I do that in a few cases (power radio comes to mind; it has an ini file). What I do in most cases though is use a backup/restore mortscript. The backup copies all settings files (and similar things) on my device to my sd card. During customization, the restore copies them back. It's convenient for apps where I change the settings a lot and I don't want to have to constantly fuss with the packages.
Some of the apps I use need a specific directory structure for the resources and files they use, so just dumping them in one big folder won't work.
Click to expand...
Click to collapse
What you do in that case is move the sub-folders into windows. In this case, I'll use a zip file to unzip those folders into windows. Using app.dat files to copy large numbers of files blows. It increases the rom file count as well as the storage used. A zip file is a single file, and usually it saves space.
Another possible issue that I think I'll run into is having two files sharing a generic name (let's say settings.xml) while each belongs to a different app. I didn't personally encounter such a situation just yet but my packages are still a work in progress and I did see a post or two about this while searching.
Click to expand...
Click to collapse
In that case, you're screwed unless there's a registry key that lets you change the name. I've run into a few complications; tcpmp and OMarket both use a common.dll. My solution was to buy Core Player, lol.
I was still hoping there would be a simple way to arrange the files in folders while keeping them under \windows\ but I can't find such a method either. Doesn't seem like I have other options than to decided on a firstboot customization method: Runcc, autorun, xda_uc or something that I haven't read about yet...
"Runcc" is currently used in the base kitchen so that gives it an edge right now.
Click to expand...
Click to collapse
Using cabs or zip files is the way to go if you want to copy large folders in one shot (with a mortscript; you can also un-rar rar files, but I don't know how. Yet, lol). Zips are easier to make and edit than cabs, but you need to have mortscript cooked in and know how to write the simple script (aka cut-and-paste).
Edit:
Remembered that I had another question, and it's probably not worth a new thread.
I was looking at how to manually create .lnk files and I noticed something that I didn't understand and couldn't find info about.
For example:
Code:
21#"\Windows\MSDict.htm"
What exactly does the "21" refer to?? I tried changing it randomly to other values a couple of times and it didn't effect anything.
Click to expand...
Click to collapse
The 21 is the number of bytes after the #. It doesn't matter. I usually just change the first number to 1. It works fine. Counting bytes blows.
That was extremely helpful. Too bad these boards don't use a rep system
Farmer Ted said:
Yup, that's correct. Another approach is to take all similar files that go into windows and stick them in a zip file that unzips to the windows directory.
Click to expand...
Click to collapse
Well, if I'm going to follow this method, and it seems like I am, I don't see why I would still have to limit myself to the \windows folder. I can just put everything the way I originally wanted to do. I only looked at arranging files under \windows when I found out that there's no way to get rid of the duplicates.
Farmer Ted said:
Using cabs or zip files is the way to go if you want to copy large folders in one shot (with a mortscript; you can also un-rar rar files, but I don't know how. Yet, lol). Zips are easier to make and edit than cabs, but you need to have mortscript cooked in and know how to write the simple script (aka cut-and-paste).
Click to expand...
Click to collapse
I haven't tried writing mortscripts yet but I've seen enough to figure out the basic and notice how easy it is. I'm gonna check how usable is the WM version of 7zip, as long as it accepts arguments combining it with mortscript will be easy and perfect for me.
7z archives can get smaller in size than half of the zip archives for the same files. And cabs are too annoying to work with and keep updated later on.
Only issue remaining now is checking whether I should put the archived files under \windows or use the sdcard for customization. I'm leaning toward the first but I'll have to wait and see how much memory I would be sacrificing that way.
Farmer Ted said:
The 21 is the number of bytes after the #. It doesn't matter. I usually just change the first number to 1. It works fine. Counting bytes blows.
Click to expand...
Click to collapse
Ah! I thought about counting bytes/characters and noticed that it works sometimes. But I thought it was a coincidence after I experimented in changing the value and noticed that it wasn't always the right count in the .lnk files that I found.
[rant]
Nice, I was messing around with some packages to free up ram and storage and I seem to have ended up with a rather b0rked up xTask. And then there's still convincing Resco Explorer that the registry add-in IS in fact there.
Figuring out the causes should keep me happily busy for a while (and probably heavily pissed for another while afterwards).
[/rant]
Edit:
Just for the record, I ended up using xda_uc it's a lot easier than doing things manually. Although it would help if there was some kind of documentation available, took me a while to understand what .xda, xdai, xdas & .xdaz files are supposed to be.
hi by the way is it possible to convert ext packages of QVGA phones to one another?
So, I'm pretty new at creating working ext packages from cab files, and I could use some help.
I'm trying to cook in the latest Quick Shutdown, and of course tie it to long press end key, like it was meant to be used for.
With some help from Grumps, here is what I've managed to get for my app.dat and app.reg:
app.dat:
Code:
Directory("\Windows"):-Directory("resources")
Directory("\Windows\resources"):-Directory("lang")
Directory("\Windows\resources"):-Directory("VGA")
Directory("\Windows\resources\VGA"):-File("bg_common_divider_section.png","\Windows\bg_ common_divider_section.png1")
Directory("\Windows\resources\VGA"):-File("bg_common_dotline.png","\Windows\bg_common_d otline.png1")
Directory("\Windows\resources\VGA"):-File("bg_common_msgbox.png","\Windows\bg_common_ms gbox.png1")
Directory("\Windows\resources\VGA"):-File("bg_common_titlebar.png","\Windows\bg_common_ titlebar.png1")
Directory("\Windows\resources\VGA"):-File("btn_checkbox_thirdState.png","\Windows\btn_c heckbox_thirdState.png1")
Directory("\Windows\resources\VGA"):-File("btn_common_checkbox.png","\Windows\btn_commo n_checkbox.png1")
Directory("\Windows\resources\VGA"):-File("btn_common_combo_down.png","\Windows\btn_com mon_combo_down.png1")
Directory("\Windows\resources\VGA"):-File("btn_common_input.png","\Windows\btn_common_i nput.png1")
Directory("\Windows\resources\VGA"):-File("btn_common_listitem_bottom.png","\Windows\bt n_common_listitem_bottom.png1")
Directory("\Windows\resources\VGA"):-File("btn_common_listitem_middle.png","\Windows\bt n_common_listitem_middle.png1")
Directory("\Windows\resources\VGA"):-File("btn_common_msgbox_large.png","\Windows\btn_c ommon_msgbox_large.png1")
Directory("\Windows\resources\VGA"):-File("btn_common_msgbox_small.png","\Windows\btn_c ommon_msgbox_small.png1")
Directory("\Windows\resources\VGA"):-File("btn_common_normal.png","\Windows\btn_common_ normal.png1")
Directory("\Windows\resources\VGA"):-File("btn_common_slider.png","\Windows\btn_common_ slider.png1")
Directory("\Windows\resources\VGA"):-File("sliderBtn.png","\Windows\sliderBtn.png1")
Directory("\Windows\resources\lang"):-File("lang.czech.txt","\Windows\lang.czech.txt")
Directory("\Windows\resources\lang"):-File("lang.danish.txt","\Windows\lang.danish.txt")
Directory("\Windows\resources\lang"):-File("lang.english.txt","\Windows\lang.english.txt ")
Directory("\Windows\resources\lang"):-File("lang.french.txt","\Windows\lang.french.txt")
Directory("\Windows\resources\lang"):-File("lang.german.txt","\Windows\lang.german.txt")
Directory("\Windows\resources\lang"):-File("lang.greek.txt","\Windows\lang.greek.txt")
Directory("\Windows\resources\lang"):-File("lang.italian.txt","\Windows\lang.italian.txt ")
Directory("\Windows\resources\lang"):-File("lang.polish.txt","\Windows\lang.polish.txt")
Directory("\Windows\resources\lang"):-File("lang.russian.txt","\Windows\lang.russian.txt ")
Directory("\Windows\resources\lang"):-File("lang.spanish.txt","\Windows\lang.spanish.txt ")
Directory("\Windows"):-File("bootloader.exe","%Windows%\bootloader.exe")
Directory("\Windows"):-File("ConfigQS.exe","%Windows%\ConfigQS.exe")
Directory("\Windows"):-File("DLLSetup.dll","%Windows%\DLLSetup.dll")
Directory("\Windows"):-File("QuickShutdown.exe","%Windows%\QuickShutdown.exe")
Directory("\Windows"):-File("Short_Power.exe","%Windows%\Short_Power.exe")
Directory("%Windows-StartMenu-Programs%"):-File("Quick Shutdown.lnk","%Windows%\_Shutdown.lnk")
app.reg:
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Manila_Config QuickShutdown]
"SourcesDirectory"="\\Windows\\resources\\VGA\\"
[HKEY_LOCAL_MACHINE\Software\Manila_QuickShutdown]
"actionShortPress"=hex:00
"BootActiv"=hex:01
"langFile"="\\Windows\\resources\\lang\\lang.english.txt"
"RestartActiv"=hex:01
"ScreenOffActiv"=hex:01
"ShutdownActiv"=hex:01
"SleepActiv"=hex:01
Cooking that package, I have a few problems. When I hold down the power button, it says exe can't be found. So, just to make sure that the visual aspect is working, I try searching for quickshutdown.exe in \Windows and can't find it.
So, what's wrong in my .dat and .reg?
Thanks a lot for the help, this will definitely give me a better understanding of how EXT packages work!
Regards
Smith
First of all, I think that these lines in your app.dat are unnecessary; because when you cook the ROM then the files that are not specified with the path in app.dat land automatically in the Windows folder:
Directory("\Windows"):-File("bootloader.exe","%Windows%\bootloader.exe")
Directory("\Windows"):-File("ConfigQS.exe","%Windows%\ConfigQS.exe")
Directory("\Windows"):-File("DLLSetup.dll","%Windows%\DLLSetup.dll")
Directory("\Windows"):-File("QuickShutdown.exe","%Windows%\QuickShutdown.exe")
Directory("\Windows"):-File("Short_Power.exe","%Windows%\Short_Power.exe")
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Second: All of the lines are wrong. Example:
Directory("\Windows"):-File("QuickShutdown.exe","%Windows%\QuickShutdown.exe")
Click to expand...
Click to collapse
It should be:
Directory("\Windows"):-File("QuickShutdown.exe","\Windows\QuickShutdown.exe")
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Third: Open up the file _Shutdown.lnk in notepad and see if it links to the \Windows\QuickShutdown.exe
Click to expand...
Click to collapse
Maybe you will find something in my post that can help you.
It's much, much easier to do than the way you're trying to do it. First, copying all of those files is really wasteful. If you look at your registry keys, there are paths there for the resource files. Instead of creating a \windows sub-directory, you could just set the path as \windows. Then, the files that are in rom will be used, and you won't need duplicates, or any of the app.dat lines (except for the .lnk).
Change the .rgu to this:
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Manila_Config QuickShutdown]
"SourcesDirectory"="\\Windows\\"
[HKEY_LOCAL_MACHINE\Software\Manila_QuickShutdown]
"actionShortPress"=hex:00
"BootActiv"=hex:01
"langFile"="\\Windows\\lang.english.txt"
"RestartActiv"=hex:01
"ScreenOffActiv"=hex:01
"ShutdownActiv"=hex:01
"SleepActiv"=hex:01
Try deleting the DLLSetup.dll-it's really unlikely that you need it. It's just cabinstall information, most likely. Unless you really want all those other lang files, I'd just delete all but the English one. If you cook them all in, it's possible that you'll need to get the others into \windows\lang (it doesn't look like there's a reg key for the lang directory, just for the file being used). I don't know, I've never used the app. As mentioned above, you may also need to fix the path of the shortcut.
You may also want to look into compressing the png files, although it's not really worth it if they're only 1-2 kb each.
This is what I use. I put it together and it worked, so I never did much investigation to see if it could be optimized.
One thing to be aware of ... if you have carrier files which fire provxml, it is possible that the provxml could do something to overwrite the poweroffwarning file here. Same is true if you have a poweroffwarning file getting copied in later in the build process.
Best regards,
-boggsie
Farmer Ted said:
It's much, much easier to do than the way you're trying to do it. First, copying all of those files is really wasteful. If you look at your registry keys, there are paths there for the resource files. Instead of creating a \windows sub-directory, you could just set the path as \windows. Then, the files that are in rom will be used, and you won't need duplicates, or any of the app.dat lines (except for the .lnk).
Change the .rgu to this:
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Manila_Config QuickShutdown]
"SourcesDirectory"="\\Windows\\"
[HKEY_LOCAL_MACHINE\Software\Manila_QuickShutdown]
"actionShortPress"=hex:00
"BootActiv"=hex:01
"langFile"="\\Windows\\lang.english.txt"
"RestartActiv"=hex:01
"ScreenOffActiv"=hex:01
"ShutdownActiv"=hex:01
"SleepActiv"=hex:01
Try deleting the DLLSetup.dll-it's really unlikely that you need it. It's just cabinstall information, most likely. Unless you really want all those other lang files, I'd just delete all but the English one. If you cook them all in, it's possible that you'll need to get the others into \windows\lang (it doesn't look like there's a reg key for the lang directory, just for the file being used). I don't know, I've never used the app. As mentioned above, you may also need to fix the path of the shortcut.
You may also want to look into compressing the png files, although it's not really worth it if they're only 1-2 kb each.
Click to expand...
Click to collapse
Great call! Worked immediately! Thanks a lot!
One more quick question. Cooking total commander is being dumb. The EXT I create doesn't have any exe files in the "files" folder, and doesn't extract any into windows. It just isn't working well lol.
Also, what version or what addon enables the user to hold the slash button and bring up the menu where you can hide exit blah blah total commander?
Thanks
Smith
Total Commander is easy to cook in. Again, you don't need app.dat lines, except for the shortcut (make sure it points to windows). Just put the .exe and the plugins (registry, wlan, ftp and webdav, if you have it) in windows. Cook in the reg settings, and you're good to go. I would convert the exe to a module as well.
Farmer Ted said:
Total Commander is easy to cook in. Again, you don't need app.dat lines, except for the shortcut (make sure it points to windows). Just put the .exe and the plugins (registry, wlan, ftp and webdav, if you have it) in windows. Cook in the reg settings, and you're good to go. I would convert the exe to a module as well.
Click to expand...
Click to collapse
So... Create the EXT and recmod without any reg or dat entries except icon and shortcut?
No, include the ghisler reg key (hkcu-software-ghisler). Set it up however you like it (like w/ a fully loaded hotlist). But don't move the files around w/ the app.dat.
Farmer Ted said:
No, include the ghisler reg key (hkcu-software-ghisler). Set it up however you like it (like w/ a fully loaded hotlist). But don't move the files around w/ the app.dat.
Click to expand...
Click to collapse
Huh this isn't working lol could you post the cab you're working with? My cab is acting up (even on fully functional roms)
Farmer Ted said:
Total Commander is easy to cook in. Again, you don't need app.dat lines, except for the shortcut (make sure it points to windows). Just put the .exe and the plugins (registry, wlan, ftp and webdav, if you have it) in windows. Cook in the reg settings, and you're good to go. I would convert the exe to a module as well.
Click to expand...
Click to collapse
Hello Farmer Ted - what for is the file that you attached?
It's a plugin for WebDav, which is the new big thing. I have no clue wtf it does.
Get the ghisler reg key from the device, not the cab. That's always the way to do it. Kheb 1.1 is the way to go for making packages. Cab converters miss a lot of stuff.
Edit: here's my package; it's in oem form (for osbuilder), and it looks like there's a second file needed to get webdav to work in the plugins. Edit the hotlist however you want it (it has folders on my sd card, which are useless to anyone else). It doesn't have a shortcut or initflashfiles.txt in it, since I don't use them for my start menu.
To be more specific about TCMD, here is the output I get with OSkitchen cab to ext:
TCMD>Files
And within the files directory:
000cecmd.002
CECMD_~2.001
00000ftp.003
00000LAN.005
registry.004
TcmObex3.007
TcmObex5.006
So what do I do with those files lol
Regards
Smith
Farmer Ted said:
It's a plugin for WebDav, which is the new big thing. I have no clue wtf it does.
Get the ghisler reg key from the device, not the cab. That's always the way to do it. Kheb 1.1 is the way to go for making packages. Cab converters miss a lot of stuff.
Edit: here's my package; it's in oem form (for osbuilder), and it looks like there's a second file needed to get webdav to work in the plugins. Edit the hotlist however you want it (it has folders on my sd card, which are useless to anyone else). It doesn't have a shortcut or initflashfiles.txt in it, since I don't use them for my start menu.
Click to expand...
Click to collapse
Thank you for sharing the package.
Farmer Ted said:
It's a plugin for WebDav, which is the new big thing. I have no clue wtf it does.
Get the ghisler reg key from the device, not the cab. That's always the way to do it. Kheb 1.1 is the way to go for making packages. Cab converters miss a lot of stuff.
Edit: here's my package; it's in oem form (for osbuilder), and it looks like there's a second file needed to get webdav to work in the plugins. Edit the hotlist however you want it (it has folders on my sd card, which are useless to anyone else). It doesn't have a shortcut or initflashfiles.txt in it, since I don't use them for my start menu.
Click to expand...
Click to collapse
Thanks for your package, much appreciated! This thread has taught me a lot about how ext's work
Do you know what all those strange files I talked of 2 posts up are though? Like, how do I put those all together?
Regards
Smith
smithisize said:
Thanks for your package, much appreciated! This thread has taught me a lot about how ext's work
Do you know what all those strange files I talked of 2 posts up are though? Like, how do I put those all together?
Regards
Smith
Click to expand...
Click to collapse
I'm not sure what the technical name is, but those are the raw files from the cab; if you extract the cab with winzip or 7-zip, that's the file names. If you give them the proper extensions (.dll, exe, etc) then you can recover the proper files. It looks like the unpacking didn't work properly.
Farmer Ted said:
I'm not sure what the technical name is, but those are the raw files from the cab; if you extract the cab with winzip or 7-zip, that's the file names. If you give them the proper extensions (.dll, exe, etc) then you can recover the proper files. It looks like the unpacking didn't work properly.
Click to expand...
Click to collapse
Ah! You're right thanks a lot lol that's where my confusion was stemming from lol I couldn't figure out what to do with them!
Thank you very much!
Regards
Smith