Related
This post is obsolete
Thank you very much for this!
EDIT:
Only these two folders? No more or do I have to replce the folders inside of my Kitchen?
I took the liberty to changing the Title to Internet Explorer and Giving you Bump in informing you.
Hope people get the intention of this thread, so hopefully there won't be hundred's of different IE versions around.
Have you Seen PIE8 yet?
HI!!!
I am looking forward the PIE6 such a long time!!!
Thank you very much!!
But I want to know " Can it be uninstall to roll back to PIE4???"
Thanks!!!
Noonski said:
I took the liberty to changing the Title to Internet Explorer and Giving you Bump in informing you.
Hope people get the intention of this thread, so hopefully there won't be hundred's of different IE versions around.
Have you Seen PIE8 yet?
Click to expand...
Click to collapse
Hi Noonski, yes I already have Internet Explorer version 8 for a few days. Not tested yet. I uploaded it to mediafire so you can download the cab here. I didn't make an OEM package yet.
animelover said:
Only these two folders? No more or do I have to replce the folders inside of my Kitchen?
Click to expand...
Click to collapse
I would like to know as well what SYS packages (if any?) should be removed before putting this in the kitchen?
Andy
i installed mi ie8 cab on my hp ipaq 214. but i dont know how to start it. where is exe?
so I tried instaling the cab file and I do not see any differences. It seems like an addon for the already existing PIE... ?
I looke at the OEM, and I am not sure what the differences are other than the new DLLs.
Can someone explain what the new features are?
I still can't see the myspace page normal. WTF?!
Ok guy more details...
The oem package must go in Sys folder togehter other Browsing folders, you must not delete anything!
Cook your room and enjoy, rember tu put flashlite also in your rom!
For IE8 probably need some other file, I'll try to cook in a rom to try it!
robertus3d said:
Ok guy more details...
The oem package must go in Sys folder togehter other Browsing folders, you must not delete anything!
Cook your room and enjoy, rember tu put flashlite also in your rom!
For IE8 probably need some other file, I'll try to cook in a rom to try it!
Click to expand...
Click to collapse
That explains it. I was going to report back as not working but i might try that and check back later.
I tried the Package both in OEM and Sys, iT did not change anything here to.
More Play tomorrow.
**** Just Noticed this was Post Number 3000 for me.
Noonski said:
I tried the Package both in OEM and Sys, iT did not change anything here to.
More Play tomorrow.
**** Just Noticed this was Post Number 3000 for me.
Click to expand...
Click to collapse
Congrats on that.
Did you try the first root folder and put the two inner folders in the sys?
Repack posted in post #1, this should work.
I have cooked this into my ROM and it all works OK apart from the IE home page. In the folder 'browsingie_LANG_0409' the .RGU file sets the home page to
Code:
"home_0409"="file://\\Windows\\iemo6_default_0409.htm"
and this file is included in the folder. When I launch IE though I get the 'Action canceled' page. I have verified the file is there and if I use File Exlporer to find the file and then open it, it all opens OK. If I open the file this way and then set it to the home page and then close and open IE the problem is still there so I am stuck as to what the issue is?
I have noticed similar behaviour with other .htm files as well; for example the JBlend0409.htm file when trying to access it via Help - you get 'Cannot open Help. The file cannot be found' however the file is there and the shortcuts are correct?
It is pretty weird?
Andy
Hi Guys
I am using a HTC hermes. I just upgraded my device with wm6. I used offficial upgarde from AT&T. After upgrading the internet explorer is not working. Need help to solve the problem. With thanks
Pump Man
Hi,
i downloaded the Pack linked here:
http://forum.xda-developers.com/showthread.php?p=2870848
But this one is not installable on my Polaris. It says "Installation not successful".
I also downloaded M-Amines Opal Phone, but this one is also not installable correctly and it does not have this slider, that protects the buttons, that i can not click "end call" with my face
Does anyone have a Cab with the slider as shown on the pics in the link above?
I have M-Amine's 2.0 (GER) installed
Thanks...
Baxter. said:
Hi,
i downloaded the Pack linked here:
http://forum.xda-developers.com/showthread.php?p=2870848
But this one is not installable on my Polaris. It says "Installation not successful".
I also downloaded M-Amines Opal Phone, but this one is also not installable correctly and it does not have this slider, that protects the buttons, that i can not click "end call" with my face
Does anyone have a Cab with the slider as shown on the pics in the link above?
I have M-Amine's 2.0 (GER) installed
Thanks...
Click to expand...
Click to collapse
I don't remember where I got this cab from and I'm not sure whether it has the slider to answer etc. You might want to check the name/size just to make sure it isn't one you already tried. Hope it helps.
Thanks, it is the right one.
BUT: It looks weird
The Slider is not transparent and the Red Button which ends the call is only red and does not show any font.
Do you know why and how to fix it? Maybe I'm doing something wrong
Baxter. said:
Thanks, it is the right one.
BUT: It looks weird
The Slider is not transparent and the Red Button which ends the call is only red and does not show any font.
Do you know why and how to fix it? Maybe I'm doing something wrong
Click to expand...
Click to collapse
Maybe just make sure you have any other dialer uninstalled before you install this one?
Baxter. said:
The Slider is not transparent
Click to expand...
Click to collapse
This is what the Opal phone canvas looks like.
There is no transparent slider.
Sascha
Read this in another thread but can't remember where it was: Maybe try this and then attempt to reinstall the cab file. Hope this helps.
Delete reg keys under HKEY_LOCAL_MACHINE\Software\HTC\PhoneCanvas & set HKEY_LOCAL_MACHINE\Security\Phone\Skin\Enabled=0, it should then return to the default windows mobile dialer.
SaBo said:
This is what the Opal phone canvas looks like.
There is no transparent slider.
Sascha
Click to expand...
Click to collapse
Look at the Pics in this Thread:
http://forum.xda-developers.com/showthread.php?t=470510
The Phone is black-skinned and has a transparent slider. I need this, cause it looks really great
But the author only posted the raw files. Does anybody has this as a cab? I'm not a pro, i don't know how to make a cab out of the files
Baxter. said:
Look at the Pics in this Thread:
http://forum.xda-developers.com/showthread.php?t=470510
The Phone is black-skinned and has a transparent slider. I need this, cause it looks really great
But the author only posted the raw files. Does anybody has this as a cab? I'm not a pro, i don't know how to make a cab out of the files
Click to expand...
Click to collapse
OK, i got it.
It's the cab posted here and the skin posted in this thread
http://forum.xda-developers.com/showthread.php?t=470510
you just have to copy the new skin-Files to windows-directory with total commander
Thanks all
Look's good, i'm going to try it myself.
Thanks a lot!
I got it via mbarvian's upload. Just great to have it on TyTn II. Hope someone comes with a black colour.
Baxter. said:
the Red Button which ends the call is only red and does not show any font.
Click to expand...
Click to collapse
How did you solve this problem? I have it too (with M-Anime 2.0 [ITA])
mang1 said:
How did you solve this problem? I have it too (with M-Anime 2.0 [ITA])
Click to expand...
Click to collapse
You need the right language files for your ROM.
I installed mbarvian's CAB from here, and it has 3 language file:
phcanrc.dll.0409.mui
ContactAssistDll.dll.0409.mui
PhoneSettingExt.dll.0409.mui
Since I use your same ROM (M-Amine 2.0 [ITA]) I needed .410.mui files and managed to extract these
phcanrc.dll.0410.mui
PhoneSettingExt.dll.0410.mui
from AZTOR Diamond's ROM, and just copied ContactAssistDll.dll.0409.mui to ContactAssistDll.dll.0410.mui.
I am attaching these files, just unzip in \windows and reboot.
Met
P.S.
I also had to install jadeStatusIcons.cab to fix the "battery shows as always full" problem.
met67 said:
You need the right language files for your ROM.
I am attaching these files, just unzip in \windows and reboot.
Met
Click to expand...
Click to collapse
Thank you so much, my friend!
met67 said:
You need the right language files for your ROM.
I installed mbarvian's CAB from here, and it has 3 language file:
phcanrc.dll.0409.mui
ContactAssistDll.dll.0409.mui
PhoneSettingExt.dll.0409.mui
Since I use your same ROM (M-Amine 2.0 [ITA]) I needed .410.mui files and managed to extract these
phcanrc.dll.0410.mui
PhoneSettingExt.dll.0410.mui
from AZTOR Diamond's ROM, and just copied ContactAssistDll.dll.0409.mui to ContactAssistDll.dll.0410.mui.
I am attaching these files, just unzip in \windows and reboot.
Met
P.S.
I also had to install jadeStatusIcons.cab to fix the "battery shows as always full" problem.
Click to expand...
Click to collapse
Is it possible for you to upload the german files also? Would be great. Thanks
Baxter. said:
Is it possible for you to upload the german files also? Would be great. Thanks
Click to expand...
Click to collapse
Here you go...
I haven't tested these files, but they should work.
In order to extract more languages, just download the ROM in your language from AZTOR thread, extract DIAMIMG.nbh from the archive and issue these commands (you can find the executable here in XDA, just download a recent kitchen...):
NBHextract.exe DIAMIMG.nbh
ren *_OS.nb OS.nb
NBSplit.exe -kaiser OS.nb
ImgfsFromNb.exe OS.nb.payload imgfs.bin
ImgfsToDump.exe imgfs.bin
If everything is fine, you will find a "dump" folder which contains every file in the ROM, just open it and search for the MUIs in your language.
met67 said:
Here you go...
I haven't tested these files, but they should work.
In order to extract more languages, just download the ROM in your language from AZTOR thread, extract DIAMIMG.nbh from the archive and issue these commands (you can find the executable here in XDA, just download a recent kitchen...):
NBHextract.exe DIAMIMG.nbh
ren *_OS.nb OS.nb
NBSplit.exe -kaiser OS.nb
ImgfsFromNb.exe OS.nb.payload imgfs.bin
ImgfsToDump.exe imgfs.bin
If everything is fine, you will find a "dump" folder which contains every file in the ROM, just open it and search for the MUIs in your language.
Click to expand...
Click to collapse
thanks man
cr1960 said:
I don't remember where I got this cab from and I'm not sure whether it has the slider to answer etc. You might want to check the name/size just to make sure it isn't one you already tried. Hope it helps.
Click to expand...
Click to collapse
Thanks to all,
I was looking to change my dailer, and the opal one is exactly what I was looking for.
I then install the cab with the one correcting the battery status (works fine)
BUT SINCE MY PHONE IS NO LONGER RINGING NOR VIBRATING WHEN INCOMING CALL !!
I checked the register HKCU/ControlPanel/Sounds/RingTone0 Script String=av0pw3r on the default Windows Mobile ring tone
Any idea?
Many many BIG Thanks in advance !!
Hi all
I reply to myself: I got the solution:
For whatever reason the Category key in HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0 was corrupted: after Ring, some gabrage appear poluting the key.
I just earased it and leaving only Ring and now my phone is ringing and vibrating again.
Good night
Cannot install it on 3LIT3 II ROM Naked... Instalation unsuccesfull
michelD said:
Hi all
I reply to myself: I got the solution:
For whatever reason the Category key in HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0 was corrupted: after Ring, some gabrage appear poluting the key.
I just earased it and leaving only Ring and now my phone is ringing and vibrating again.
Good night
Click to expand...
Click to collapse
Thanks, i got the same problem, but didn't find a fix for it
Nice to know how to fix it
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!!!
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
Hi,
I'm using the latest osKitchen (v1.33.5) to build my own ROM for the HTC Kovsky (SE Xperia X1). Followed the tutorial, imported the latest official R3A WWE build, added a WM 21916 build and started cooking. But there's no first boot customization after a flash/hard reset. There are no errors, executing AutoRun.exe from the Windows folder doesn't seem to work either.
The config.txt (used by AutoRun and RunCC) files are left stock, but editing them doesn't make a difference. How can I fix this? If you need more information, just ask. I'll reply asap.
Have you added the runcc.lua file and redirected it to the right config.txt?
If so, flash the ROM and look whether those files are in \Windows\ (and just not executed) or not present.
Flashed the ROM: runcc.lua was already added and it redirects to the right config.txt. Paths are correct.
...
this happened to me not so long ago:
check that the autorun.exe and config**.txt files do not get overwrote during rom creation.
check that there are no duplicate files with those file names..
good luck!
Rn
I don't think those files are being overwritten during ROM creation. How can I check this? Can't find the Autorun.exe in the kitchen but after building and flashing it is visible in the Windows folder on the device. There are no duplicate files, triple checked that.
Tried building a new kitchen from scratch, an untouched build (only importing the stock ROM and the 21916 build) didn't have a first boot customization either.
I remember figuring this out on my X1 a year ago was a pain in the a*s. Can't recall where the problem was anyway. I could upload my OEM Packages for you if you'd like to? I'm using a older version of that kitchen anyway so this "could" lead to new problems...
That would be great! Please let me know what kitchen version you used, if there are any problems I can try to roll back to that one.
I PM'd you. Most persons would not know what to do with said files so it makes no sense posting them here I guess...
...
hey dude,
not sure what your problem is if all your config**.txt are there and there is no duplicate files, for me i had a mortscript called "autorun.exe" which obviously overwrote my original autorun.exe and caused my device to do no customisation.
erm, as for not finding your autorun.exe
lots of files in the kitchen are hidden and the windows hidden files toggle does not show all the hidden files for some reason :/
me personally i use ACDSee photo manager 9 to view the files in my kitchen, i then select all the files and untick the 'hidden' properties.
ALL the files you couldnt see in windows explorer are always visable using Acdsee, by unticking the properties with Acdsee, it now makes them visable in windows explorer.
hope you understand what i meen :s
btw, i only use acdsee9 to view my pictures and to change the properties of the files.
i edit all my images with photoshop and paint.
Rn
derliebewolf said:
Most persons would not know what to do with said files so it makes no sense posting them here I guess...
Click to expand...
Click to collapse
According to my searching results this issue seems to be very rare. Posting the download link here shouldn't harm others.
For osKitchen version number you mentioned in your PM, open the kitchen and use Help -> About. Don't know if this option was present in earlier builds, but at least in 1.33.5 it is.
raving_nanza said:
erm, as for not finding your autorun.exe
lots of files in the kitchen are hidden and the windows hidden files toggle does not show all the hidden files for some reason :/
Click to expand...
Click to collapse
I wasn't at the stage of using Mortscript in my ROMs yet. Untoggle hidden system files in Windows folder options did the trick, I found AutoRun.exe
Now I'm gonna sit and wait until the download is available...
DillonDarko said:
I wasn't at the stage of using Mortscript in my ROMs yet.
Click to expand...
Click to collapse
let me know when you are at that stage dude, ive got a small collection of usefull scripts that might prove themselves usefull.
DillonDarko said:
Untoggle hidden system files in Windows folder options did the trick, I found AutoRun.exe
Click to expand...
Click to collapse
cool man, but remember:
the windows hidden files toggle does not show all the hidden files.
Acdsee will show them all so none are hidden, trust me
Rn
NVM....thought of a some other problem...
raving_nanza said:
let me know when you are at that stage dude, ive got a small collection of usefull scripts that might prove themselves usefull.
Click to expand...
Click to collapse
Will do.
For the others that might experience this problem, the download link for EXT and OEM packages available here. These packages are untested, but I'm cooking them now. Thanks for the help. Scroll down for the fix.
So I think it's working now?
@All: please be aware, those packages are device-specific and for HTC Kovsky / SE Xperia X1!
Ok, tried replacing the existing packages with those from derliebewolf. Even when left untouched or using different (correct) commands there's still no customization. @derliebewolf, could you upload your "osKitchen.exe" and "Resources" directory for me? It's all I need, I can fill the kitchen from scratch there.
If this turns out to be a kitchen specific problem I won't hesitate posting it in the official osKitchen thread.
This is a pretty complicated problem to give advise.
Just a suggestion, didn't you modified/removed something from your initflashfiles.dat?
I mean the startup.
Compair it with a stock rom if you did and check if something is missing.
On my HD2:
Directory("\Windows\StartUp"):-File("ConfigureDevice.lnk","\Windows\ConfigureDevice.lnk")
Directory("\Windows\StartUp"):-File("bugtrap.lnk","\Windows\bugtrap.lnk")
Directory("\Windows\StartUp"):-File("HTCStartUp.lnk","\Windows\HTCStartUp.lnk")
Directory("\Windows\StartUp"):-File("PKG.lnk","\Windows\PKG.lnk")
Directory("\Windows\StartUp"):-File("SignatureReplace.lnk","\Windows\SignatureReplace.lnk")
Directory("\Windows\StartUp"):-File("Welcome.lnk","\Windows\welcome.lnk")
Click to expand...
Click to collapse
You tried everything possible so I taught maybe this could be possible.
On Xperia it's probably about the same.
DillonDarko said:
Ok, tried replacing the existing packages with those from derliebewolf. Even when left untouched or using different (correct) commands there's still no customization. @derliebewolf, could you upload your "osKitchen.exe" and "Resources" directory for me? It's all I need, I can fill the kitchen from scratch there.
If this turns out to be a kitchen specific problem I won't hesitate posting it in the official osKitchen thread.
Click to expand...
Click to collapse
You really need to leave the welcome.lnk line in there, or else you won't get the alignment screen and you can't boot the device up.
Found the issue: an incomplete initflashfiles.dat. By adding the lines below to a stock initflashfiles.dat the whole issue has been fixed.
Code:
Directory("\Windows\StartUp"):-File("CheckAutoRun.lnk","\Windows\CheckAutoRun.lnk")
Directory("\Windows\StartUp"):-File("AutoShortcut.lnk","\Windows\AutoShortcut.lnk")
Turned out a stock initflashfiles.dat file doesn't have those lines included by default. Thanks to all for the help, expect a new custom Xperia X1 ROM soon.
That's nice to hear, congrats.
Please at [SOLVED] to the topic title and I will link this thread to the solved cases sticky.
DillonDarko said:
Found the issue: an incomplete initflashfiles.dat. By adding the lines below to a stock initflashfiles.dat the whole issue has been fixed.
Code:
Directory("\Windows\StartUp"):-File("CheckAutoRun.lnk","\Windows\CheckAutoRun.lnk")
Directory("\Windows\StartUp"):-File("AutoShortcut.lnk","\Windows\AutoShortcut.lnk")
Turned out a stock initflashfiles.dat file doesn't have those lines included by default. Thanks to all for the help, expect a new custom Xperia X1 ROM soon.
Click to expand...
Click to collapse
DillonDarko said:
Found the issue: an incomplete initflashfiles.dat. By adding the lines below to a stock initflashfiles.dat the whole issue has been fixed.
Turned out a stock initflashfiles.dat file doesn't have those lines included by default. Thanks to all for the help, expect a new custom Xperia X1 ROM soon.
Click to expand...
Click to collapse
Which makes me woder whether those lines are missing in my initflashfiles.dat as well? RunCC is working perfectly anyway... Glad you solved it!