Related
Hi
The attached file makes necessary registry changes to move Mail and Atachement storage to SD Card.
There have been a few cab installers available to perform a registry change, enabling storage of both Mail as well as Attachments on the Storage Card. However these solutions have the "Storage Card" hard coded as destination, which means if more than one partitions exist on Storage Card, manual changes would be required to the registry to use another partition. Another way is to have separate cabs created for each partition. Another problem is that on some devices the Storage Card is named as "Memory Card" (I've seen this on on my O2 Atom Exec), hence again manual registry changes are required or a custom cab needs to be created for these devices.
The attached cab installer tries to overcome above mentioned limitations. During the installation "Device" and all the available Storage Card Partitions are listed and user is asked to select the destination. The registry changes are performed accordingly to enable Mail and Attachment storage on the selected partition or Device.
The cab creates following registry entries under "HKLM\System\Inbox\Settings" :
- PropertyPath = <destination>\Mail
- AttachPath = <destination>\Mail\Attachment
where <destination> is the option selected as destination while installing the cab.
Uninstalling the application from Add/Remove programs should restore the old values (if any) of the above registry keys.
The cab file has been tested to be working fine on WM6.1 and should work fine on WM6 also. WM5 requires different registry entries and the attached cab does not work for WM5.
Please let me know if anyone find this useful
I just installed this on my Verizon XV6900 with Windows Mobile 6.1. All I can say is, Awesome! Thanks for this. I love the automation of it. Seamless. And providing the uninstall is also nice. Just installed, powered off, then back on, and all is well. Do you think you might also be interested in doing the same thing for Internet explorer temp files, favs, cookies. Maybe make the folder it creates be called "Internet". I had a file before for my Moto Q9m that made a bunch of things store on my storage card and I loved it. It really kept my phone running very fast, as it didn't use up main storage. With my old phone, I had 5000+ emails, alot of favs and such. I loved the fact that I could wipe my phone out any time, and then re-import the reg changes to point back to the storage card for all my stuff, and I was right back up and ready to go with all my files.
Thanks Again!
ABOUT
The purpose of this CAB is to reach a sort of UC way but with a very easy & friendly approach
HISTORY
I come from Diamond world, so because this CAB can be adapted for other platform/devices why not preparing a separate sUC.cab to use for enabling ALL the stuff (ramdisk, pimbackup,ram recovery,etc...) included in Dia Duit rom series?
what have I to do with this cab?? simply it will apply these features:
Latest stable MortScript is inscluded & ready to go, so no more needs to install as separate cab
Choose between 3 speed profiles: 1. fast (takes more ram & battery), 2. balanced (not heavy tweaked but not funny) & 3. untouched (default WM6 settings)
GPS profile: TomTom, iGO, Navigator or default WM6
Everyday auto recover RAM feature (at 4.30AM) + automatic sms/contacts/calls backup/fav manila people (trough pre-configured pimbackup app, PimBackup included)
Ramdisk (2Mb) feature (optional)
A new way for a fully automated CAB/REG/EXE/CPY installation/copy after every hard-reset/rom upgrade
UPX executable, compress (fully automated) exe files from fresh installed cabs, this saves space & gives faster app load times
Easy & fast tweaking method without 3rd part software: tweak registry scripts (with comments)
Tips enabled by default to preserve a bit more battery life (for ex 3 secs of led blinking instead 5, increased battery life counter,etc) + increased speaker sound volume + many example for setting automatic alarms, rings, etc...
Moved MAIL + Attachments folders from main memory (My Device) to external one (Storage Card)
3 / 4 rows configuration
This should work on every WM based rom, also because I added the auto recognition of "Storage" name... so should work without troubles also on NON WWE roms (except for CABi installation)
DOWNLOAD sUC.cab HERE
DOWNLOAD sUC_source.zip HERE
BEFORE INSTALL (mandatory)
create in your "Storage" (the BIG one) a folder called "Backup and Restore", then inside it a folder CAB (inside this another folder called CABi), then at the same level of CAB folder create a folder called CPY, then REG, then EXE
so practically your basic structure should be like:
Code:
Storage Card (or whatever name)
=> Backup and Restore (folder)
=> CAB (folder, put here all the cabs you want install on main memory)
=> CABi (folder inside CAB folder, specific for "must go into Storage", see notes)
=> REG (if present all reg files here will be joined to default WM registry)
=> CPY (if present all files here will be copied under their correspondent folders)
=> EXE (if present all .exe & .mscr files will be launched)
all files in the CAB folder will be installed (automatically) into "device", the ones in the CABi folder will be installed into "Internal Storage" (or whatever you have, always automatically), from REG folder all *.reg/*.rgu files will be loaded on the fly, from CPY all files will be copied (with overwrite) into correspondent folders (for ex useful for copying personal dlls, wav/wma/mp3 files or background, etc...), for finish from EXE folder will be launched your executables (personally never needed, but who knows?) & if present all *.mscr scripts... pay attention to exe files that needs user interaction
INSIDE THE CAB (a deeper explanation)
when your sUC cab is installed it simply creates a registry entry under [HKLM\init\]"Launch69"="2ndboot.exe", this permits the script 2ndboot.mscr (launched by 2ndboot.exe) to be loaded upon system reboot (just one time)
this script, if the structure mentioned above isn't found, it will create automatically all the folder & default reg files needed under your storage card, the name isn't important because it should guess itself its correct name, so don't care if your storage is called something like "MyBigStorageCard"
then it will ask you some questions... such as if you use ActiveSync, which GPS performance adopt, etc... all this info, which at 1st you'll pay high attention, will be stored under your storage card in a file called config.txt ...why?? simple... because next time you will flash or hard-reset your phone you wont have to push a button the script will found that previous stored config file & it will take all the info needed for final rom configuration to skip all annoying questions after every upgrade/HR
note: there is also an hidden option that should be used only by experts, to enable this option simply add by hand to your config.txt file the line: FastInstall=1
this will skip all countdown menu & messages... personally I use this option because flashing a lot this saves much time more
next it will look in the CAB folder for installing your CABs into "device" or main memory
next in the CABi folder for installing CABs into your storage card (you need to do this just 1st time, I'll explain later...)
next it will look at a file called upxlist.txt (must filled before), where simply you will specify all the *.exe file you want to compress after every cab installation... for example your upxlist.txt could look like:
Code:
\Program Files\Navigator\TomTom Navigator.exe
\Program Files\9.5 Beta\Opera9.exe
\Internal Storage\Program Files\Binaryfish\All Mobile Mines\All Mobile Mines.exe
note: every line for every EXE file, pay attention that you can compress just EXE files coming from extra CABs, because EXE files present in the rom are read-only
next it will copy a set of basic reg files with many tips/tricks/examples inside, useful for making many customizations
note: of course if you have previously prepared the folder structure & you have copied your REGs files under the REG folder they will be processed together the files above
next it will look in the CPY folder and will replicate the found folder structure (with files too), for example create inside it a folder \windows with some file inside & it will copy all found files under \windows on your device, or create \program files\myapp & it will create that folder structure in your device, of course it works also for Internal Storage even if it has no sense, anyway just a note it doesn't create empty folder, to create an empty folder just use a single .mscr script (something like: MkDir("\mydir") ) & copy it in your EXE folder
next it will look in the EXE folder & will launch all the exe files inside it, if found it will launch also all *.mscr scripts
next if found (you'll understand better upon an HR), it will ask you to restore your backed-up start menu, so you don't have to re-arrange your icons again
next if found, it will ask you to restore your last PIM backup & will reboot
notes:
right now CABi procedure works only on WWE roms (due to translations work to be finished), anyway there is a trick to skip CABi installation, or better make by hand just once (read few lines below)
installing cabs into Storage Card sometimes will fail, this simply because some cabs need confirmation/accept license & so on, so don't expect will work 100%, also many cabs require to be installed into main memory so NOT into Storage Card, for ex I use to install into Storage Card simple cabs such as games
sometimes pim backup restore can fail, try to restore by hand after installation; backup are divided into week days (monday, sunday, etc... "Last" is the last saved backup)
if you put sUC.cab in your CAB folder wont re-processed of course, useful if using sUC together with UC/UC2 installation method (see at bottom)
if you still use the 1st sUC release way your personal scripts still work like before, simply move them under EXE folder, or transport as reg entries directly into your personal reg file & copy it under REG folder, you can find on the same folder some examples (to clean all your old stuff simply empty the REG folder, modded REG files wont be touched on future upgrades)
you don't need to re-install every time your CABi, just install them once, then on next upgrade answer No or simply edit your config.txt & change the correspondent value; after CABi installation on a clean boot go with your explorer under "\windows\start menu" folder & re-organize your start menu structure (cut/past links, create/delete folders, etc...), remember to don't delete "Settings" folder even if empty, then go under sUC menu & backup your StartMenu, on next upgrade sUC will detect start menu backup & it will reinstall automatically... because the content of your storage card isn't erased after a rom upgrade/hard-reset your installed CABs will stay there untouched, so backed-up start menu has inside correct links
is possible to move TomTom, iGO, Navigon, etc... definitively into your storage card, so you don't need to install them every time: copy entire nav software folders from \program files to \internal storage\program folders, re-create icon shortcuts (copy/past as shortcut in your start menu), for iGO you have to edit sys.txt (under iGO folder) & change the path of base installation
in the same way is possible to skip for example FingerKeyboard installation from related cab, simply take a look at this short guide
INSTALLATION
note: to migrate in every new sUC version simply move your reg mods in your Personal.reg file, erase all the rest of reg files because they will be re-generated with the new ones, remember that on upgrades reg files wont be touched so pay attention on what you mod
if the rom is UC compliant simply create a called SDConfig.txt file in the root folder of your Storage Card, for example your SDConfig.txt could look like (pay attention to upper-lower case & no empty lines):
Code:
LOCK:Enabled
CAB :\Internal Storage\Backup and Restore\CAB\sUC.cab
LOCK:Disabled
RST: Reset
in this way at reboot will start standard sUC procedure (remember MortScript is included & also that sUC cab wont be re-processed even if present in CAB folder), instead if the rom isn't UC compliant simply install sUC as any normal cab, then it will ask to restart (or restart manually) & automated procedure will begin on reboot[/b]
bye,
davide
OK, that's all very nice, but WTF is it?
Wouldn't hurt to have an "about" section in the post for ppl who see this thing the first time in their life.
GENIAL !!!!!!
aiiro said:
OK, that's all very nice, but WTF is it?
Wouldn't hurt to have an "about" section in the post for ppl who see this thing the first time in their life.
Click to expand...
Click to collapse
yep... you right sorry, I'll correct soon...
suiller
OMG~ You finally made it available!!! I'm going to test it with my HD and will report back once everything is organised
I didn't mean to sound rude, sorry... Anyway, thanks for the addition, but still - what is UC? User Configuration? Could You post some screenshots too to make it more comprehensible for dumbusers like me?
jackkkkk said:
suiller
OMG~ You finally made it available!!! I'm going to test it with my HD and will report back once everything is organised
Click to expand...
Click to collapse
oh FRIEND! I found you
yep, I'm looking here around to see if my mad projects can be useful
the cab isn't still perfect but should work, of course I haven't a different device from diamond so all you will be a sort of beta tester
I've removed all specific diamond stuff, so it should work
Of course this is just a starting point, I'm dedicating much time to develop this small piece of "software", thx also to many other friends
You know as it works, so you should feel a bit like at home
aiiro said:
I didn't mean to sound rude, sorry... Anyway, thanks for the addition, but still - what is UC? User Configuration? Could You post some screenshots too to make it more comprehensible for dumbusers like me?
Click to expand...
Click to collapse
yep you are right... UserConfiguration, the only difference is that you don't need to write any config file, at least not as "normal" user, it's enough to copy under correct folders the CAB plus other stuff you want installed/loaded after every flash/hard-reset
I'll porvide soon a video-guide, so it will be for sure more clear
OK, OK, nuff with making fun of me Or were You seriuous with video guide?
Cos I just had a brilliant idea - I'll install the damn thing and look for myself
I think I should have done that in the first place. But still, I believe screenshots would save some time understanding what's it really about.
Yeah Screwed Up Click for life
no no I'm serious friend... but I'll suggest to wait a couple of days because I'm working on a new version where is possible to cut-off all the specific HTC/manila stuff & above all I'm re-commenting all the registry entries that interact with OS
no no I'm serious friend... but I'll suggest to wait a couple of days because I'm working on a new version where is possible to cut-off all the specific HTC/manila stuff & above all I'm re-commenting all the registry entries that interact with OS
Hi,
really don't want to be rude or offence, but ... isn't this something like SASHIMI????
If so ... where are sUC's pros?
kind regards
fwt
almost... but it's very very simple... I'm testing an heavy modified version able to run on almost every WM6.x base device
OK the CAB is ready for testing purposes... please re-read 1st post because I'm making a better, I hope easier, description of features... thx
bye,
davide
Mate, this piece of software is plain GENIUS!
So much easier than the UC thing, with all the boring scripting. This way you just place in folders, and you are (mostly) done! Amazing stuff!
I have some questions/requests for you though...
Is there a way to repeat the procedure (restore at 1/2 start up), at a later time? This could be useful, for example, if some files get corrupted, or you just want to revert back to default cabs/settings, etc. So I guess what is needed is a way to manually activate the procedure.
Second thing is regarding mail settings. Is there a way to back this up? My hotmail settings get destroyed after every HR.
Cheers.
Forgot to mention, a manual activation of this procedure would also help if (for example) you want to make multiple program installations. This way you could just use the folder CAB, without wasting time on every single program you are installing/testing...
Cheers
krale said:
Forgot to mention, a manual activation of this procedure would also help if (for example) you want to make multiple program installations. This way you could just use the folder CAB, without wasting time on every single program you are installing/testing...
Cheers
Click to expand...
Click to collapse
hmm... it could be a good idea... even if some phases can't be reverted, or better it's very complicated to "go back"... such as for ramdisk
anyway many phases are yet accessible as indipendant scripts just take a look under "\Backup and Restore\scripts" folder, of course other script could be extrapolated but I'll do probably on next version... let's say this is a testing purpose version because I have to "think" that this app must work on many (almost all I hope) wm6.x based devices
As one of the end (l)users who first saw this in Suiller's Dia Duit rom series, I can attest to this resolving one of the major grievances of Windows Mobile rom-upgrades. With some "smart" planning ahead, getting everything back can now be mostly scripted by simply placing the install file in the correct directory. Same with restoring data from your pimbackup, or adding registry settings. Once again we have a case where the xda-developers have surpassed the "offficial" roms in user friendliness.
I have since moved on to WM6.5 (still on my Diamond), but I sorely miss sUC from my later roms.
//Svein
updated sUC, corrected some small issues
I corrected some default/samples reg files, so I suggest to erase all default *.reg files under REG folder to update correctly
move your personalization to something like "MyRegPers.reg"
please reports here bugs/issues/suggestions or whatever... thx
Hi,
I'm currently working on a few tools, and want to know what features would be liked by cooks/users or anyone really.
The first tool is an exe generator for hot fixes. Simply put, you plug some files into it, and it generates an exe that can be run on the target device which will do all the hot fixes.
The advantages it gives:
No more cabs!
Can use a custom icon for the exe if desired
Things like messing around with setup.dll files doesn't need to happen, and an application can be launched after install if wanted
Files can be deleted
File properties can be changed
Can use XMLs
Can edit registry
Can install files
Since it's written in native C++, it should run without a hitch on WM5+ devices, whether or not they have .Net whatever...
The second tool is an AutoRun/UC/whatever like system that simply searches through a folder, finds all cabs/xmls/provxmls and then installs them. This means there's no reliance on autorun for parsing config files, or any other requirements. Again, it's written in native C++ so is better
Any suggestions/ideas would be welcome!
Oh, and once I've got slightly further, both these will be released as open source. Probably.
l3v5y said:
Hi,
I'm currently working on a few tools, and want to know what features would be liked by cooks/users or anyone really.
The first tool is an exe generator for hot fixes. Simply put, you plug some files into it, and it generates an exe that can be run on the target device which will do all the hot fixes.
The advantages it gives:
No more cabs!
Can use a custom icon for the exe if desired
Things like messing around with setup.dll files doesn't need to happen, and an application can be launched after install if wanted
Files can be deleted
File properties can be changed
Can use XMLs
Can edit registry
Can install files
Since it's written in native C++, it should run without a hitch on WM5+ devices, whether or not they have .Net whatever...
The second tool is an AutoRun/UC/whatever like system that simply searches through a folder, finds all cabs/xmls/provxmls and then installs them. This means there's no reliance on autorun for parsing config files, or any other requirements. Again, it's written in native C++ so is better
Any suggestions/ideas would be welcome!
Oh, and once I've got slightly further, both these will be released as open source. Probably.
Click to expand...
Click to collapse
Wow, this sounds very very promising. Can't wait!
dwizzy130
yeah some user friendly and easy to understand specialy editing the rom or making add/remove programs EASILY is the best specialy to noobs like me when cooking ROMS all in one tool with advance AI for error checking
Sounds very attractive. go on my friend.....
Sounds good mate
I'm looking for a tool to easily make a setup.dll. Like setup.dll maker/generator/wizard.
Seems the only tools I can ever found is from e-pocketsetup, but that company was sold to another company and the product was never available since then.
I know cooks hate a cabs with a setup.dll. But seems without setup.dll a cab installer can not execute some little complicated actions. And it is impossible to make a setup.dll without grasp a computer language like c++.
Edit: Found another one: setupdllcreator , but it's not strong enough and not freeware.
Edit: If these can be realized, a setup.dll maker is much less needed:
No more cabs!
Can use a custom icon for the exe if desired
Things like messing around with setup.dll files doesn't need to happen, and an application can be launched after install if wanted
Files can be deleted
File properties can be changed
Can use XMLs
Can edit registry
Can install files
Click to expand...
Click to collapse
But we need above mentioned fubctionalities to be DYNAMIC, like:
Can detect availability of certain reg entries or installed apps, base on the result to decide which variants of install files to be installed, or whether some supporting apps like netcf or mortscript to be installed. Or can detect device id, resolutions, drivers to decide what to do.
Otherwise it still can not completely replace setup.dll.
But if dynamic actions can be executed, wow that's a dream of developers & hackers and even common users can benefit from that, a real revolution !
woww can wait for realese
l3v5y said:
Any suggestions/ideas would be welcome!
Click to expand...
Click to collapse
So I'm posting my requests again, the idea is this: It will be much helpful if I can know what is happening/changed in the registry after I did anything to my WM devices. So maybe you can develop a tool to monitor & log the real-time changes of registry. Or at least we can have a registry-comparision tool on ppc.
Another thing is it seems we don't have a file structure viewer on ppc, not the stuff like total commander etc., want to export the file structure to a file like .txt or .jpg.
Update: Now my idea is clearer for this, what I suggest would be a System Snopshot program to realize this:
Can make a system snapshot to record the registry content, file structure, ram usage etc.
The snapshot can be initialized in the similiar way of CapSure screen capture program, i.e., a hardwre button, a fixed time, a screen tap, a program launch, etc., defined by user.
Can choose a full system snapshot or only on selected part of registr, file system etc.
Can generate a file containing the recorded system condition.
Can compare any two system snapshot result and generate a comparision chart/change log.
So I've posted my requests as per your request, whether or not you'll do it is not my business lol.
Update: Found SK Tracker, cost EUR9.95, so forget this one. Why I did not know it in the past?!
Gurus,
I tried searching for this but in vain. I keep flashing all the great roms posted here frequently. And every time i have to configure my email accounts from scratch and this is a real pain. Is there any way to backup the settings like we do in PIM backup and restore upon reflashing the ROM'S?
Help greatly appreciated...
Thanks,
Raj
prudviraj said:
Gurus,
I tried searching for this but in vain. I keep flashing all the great roms posted here frequently. And every time i have to configure my email accounts from scratch and this is a real pain. Is there any way to backup the settings like we do in PIM backup and restore upon reflashing the ROM'S?
Help greatly appreciated...
Thanks,
Raj
Click to expand...
Click to collapse
Same here, what is best method to backup & restore phone settings regardless of what ROM we are using.
What about Microsoft my phone?
get makisu from HERE
(its a plugin to sashimi, but it will run standalone too)
run it, (it may take a few moments to start, be patient) enter your account details, add as many as you like, including wifi settings
tutorial video HERE
copy the xml file it creates (created mine as program files/makisu/makisu.xml)
get the microsoft cabinet sdk from HERE
extract it, and in the BIN folder is an .exe file called makecab.exe
I coppied that file out to its own folder, i dont use anuthing else in the sdk.
put makecab.exe and makisu.xml in a folder together, rename the xml to _setup.xml
open a command line window, and browse to that folder.
(Useful tip for vista/7, with the folder open on screen, hold shift and right click, you will get the option to 'open command window here')
issue the command
makecab /D COMPRESS=OFF _setup.xml mail.cab
(set mail.cab to whatever.cab name you want)
Thats it, copy the cab to your phone and run it when you need to set up your email accounts (and wifi if you set that too, very handy, i've automated 5 email accounts and 3 wifi networks)
(You could also just stop at the xml stage, and next time you hard reset, instal makisu and then choose 'provision xml' and browse to the makisu.xml file and it will install the settings.)
@samsamuel - I've just found this post (after searching for "rename email account"!!) and it's awesome.....just what I've been looking for!! Now I can reload my mail settings whenever I flash....assuming I can find a way to rename the current (incorrect) mail account I just added, otherwise I'll have to go for the delete/re-create option
Thanks again for posting about "makisu" - shame I have to register on yet another forum I'll never use just to get it....unless it's hidden on XDA somewhere?
Mark.
This is all that you guys need.
This will take care of provisioning for Wi-Fi Configs, Email Configs and Certificates.
leepriestenator said:
This is all that you guys need.
This will take care of provisioning for Wi-Fi Configs, Email Configs and Certificates.
Click to expand...
Click to collapse
After you make the xml with the program, how do you access it on the phone for restoration of settings? I don't need it right now but I am making xml's since I have had to hard reset my phone 4x already (and not because I was flashing a ROM) and re-creating all the settings is such a pain. I read into the sashimi and makisu but those apps make my head spin. There has to be a simpler way. Thanks in advance.
Edit: I think I got it. Either I use Makisu to access the xml or make the cab using the post above. If I make the cab and I want to use Quick cab (since it is much easier to use), where does the file install? \Windows?? It was unclear from the previous post since the instructions are for a different cab making utility.
k8sh said:
Edit: I think I got it. Either I use Makisu to access the xml or make the cab using the post above. If I make the cab and I want to use Quick cab (since it is much easier to use), where does the file install? \Windows?? It was unclear from the previous post since the instructions are for a different cab making utility.
Click to expand...
Click to collapse
it doesnt install any files anywhere, not in teh way you mean, its just setting/changing/applying settings. Think of the xml file as a script that makes changes as it runs.
For me, i have makisu in my autoinstall folder, so it gets installed at hard reset, and i run teh xml file (also on my sd card) manually when i am ready to apply it. (I flash a lot, so sometimes i dont want email setting up, because i am gonna flash again in a few minutes).
I no longer bother creating the cab, because with the xml file you can just open it in notepad and add anotehr email account, make other small adjustments, whatever, which you cant do with a cab, you have to rebuild the whole thing from scratch. (for some reason wince cab manager cant open that cab.)
Well if you are on a custom rom, every chef support some form of UC or the other (User Customization).
In addition to Sashimi / Makisu you can also use SDConfig.txt & XDA_UC if your ROM supports it.
Google them and you'll find more info.
This looked like it would do the trick. When I run it I get a visual basic error. I have netcf v4 installed. Is there another file required to make this run?
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?