Now, I run into a file system performance problem of WM5.0.The product we customized has terrible file system perfermance,the index of file system(use spb benchmark) is very low.How can I enhance the performance?Please help me, Thanks.
Oh,give me your hands...I fill with anxiety about it.
Related
Is it possible to find out for a file which sectors contain the file data
and read/write the data using low level functions? Platform - win-based PPC.
Thanks a lot in advance.
I have unlocked the ExtROM and am using it, I have no need for the Orange customisations.
In the registry this is called HKLM\System\StorageManager\Profiles\TRUEFFS_DOC1 and can be unlocked, renamed, written to and even (by Buzz) erased and the space added to ... Main storage or \.
What about TRUEFFS_DOC and TRUEFFS_DOC2?
Which parts of the system are they?
DOC is typed as imgfs, which I imagine is the 128MB ROM that contains the OS, flashed in working state during a ROM upgrade.
DOC2 is FAT and could be the \ partition?
If we could make the DOC partition read/write (yes, very dangerous), even temporarily, could we overwrite the OS installed files with our own instead of taking up space in the \ memory?
Overwriting stuff in the 128MB partition seems more sensible than keeping the original file and using the valuable 64MB that HTC skimped on.
I know that you can cook a ROM to do this, but that is a long and involved process that isn't for the faint hearted. I'm tearing my hair out at the registry creation part, going through the posts here trying to make sense of them before asking another question in an already long thread. Renaming a few files and putting them in the expected places seems like a quick fix solution that if done properly shouldn't be too dangerous.
Universal DOC2 visible
In search for a find today, I'll post here how to make the DOC2 partition visible.
This registry adjustment allows you to see a new partition called 'ShadowROM' (saw it in the registry somewhere > the name I've given it last format). It contains all data, *.vol databases etc.. THE Windows basic replication folder. All your new/user data, as of the last install.
First things first: BACK UP YOUR DEVICE.
What you do with this is for your own purpose. Incorrect use and you loose all your data!
Open Notepad and copy/paste the following into a reg file which you can simply open on your device.
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC2]
"Bootphase"=dword:00000001
change this to:
"Bootphase"=dword:00000002
to make the partition active in normal operation, being bootphase 2.
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2]
"Folder"="ShadowROM"
To give the little beast a name.
Notice the extra screenshots I posted for oddities!
This is interesting... What are the pro & cons of keeping files and apps here vs external storage?
Is it just saving space for the apps that must be installed internally?
Are there performance or ram gains for the universal?
Thanks.
leaving the registry this way, I can delete files within that partition, or copy a (several megabyte in size even)file. Consequence of such an operation: next soft reset = hard reset. No 'buts'. Straight to 'OUT'.
I've been fiddling with other registry keys in the neighbourhood which seem to have some effect.
The use however... finding that there are several directories "Windows" and "Program Files" and so on... these events take up processing time, i/o operations, some of which have caused and probably will cause performance issues.
This looks more like a mess then 'user friendlyness'. If for instance backup or dataloss purposes are reasons for these... leave the device without charging for a couple of days.....
epicus, thanks for the sharing... Looks like I'd still need to wait a little bit before I venture into this.
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?!
Hello all,
I am planning to start a new project on Automated But Configurable User Configuration (ABC-UC), if I get good feedback from the community. The goal is to provide a simple user configuration interface for the end user. Complexity of Chef’s job will remain the same. A small binary will be required to be cooked in ROM and the rest will be on SD card.
Motivation for yet another UC:
1. Automated execution - If you are a dummy user like me, you for sure do not like the itsy-bitsy of UC – SDConfig.txt, making sure the paths are OK etc. We have XDA_UC that does everything automatically. My tool will include (possibly almost) every feature of XDA_UC.
2. More configurability – sometimes I find SDConfig.txt to be too restrictive. To get a way around I write an (ad hoc) Mortscript file. At different point in the SDConfig.txt I execute the script file. Based on the place from where the script is executed, it does different tasks. I never found this ad hoc solution interesting. For advance users, ABC-UC will be configurable. An advance user may control the order of actions from ABC-UC – like the order of different directory managed by ABC-UC, install registry or cab first, confirm each action or not, etc.
3. Extended command support – besides command for installing cab, copy single file, provisioning, ABC-UC will provide extended file management command support. At this point most of the users use a combination of XML and Mortscript to do this job. However, not everyone can write those scripts and writing an error free XML is not always easy. At this point I am planning to include following commands copy (single or multiple files with wild card or an entire directory), move (single or multiple files with wild card or an entire directory), delete (single or multiple files with wild card or an entire directory), makedir (make all the directories in a given path), exec (without the space constraints), attrib (change attribute of a single or multiple files with wild card or an entire directory).
Do you think the effort will be worthy?
If you think the effort is worthy, then what other features do you want to see here?
Thanks for your input,
mma123
Whilst i think the goals of your project are great, i honestly dont see a need for it.
A tool which would allow new users to quickly generate the correct XML code could be a good idea, but the complexity of the requirements is likely to very quickly make the tool outdated & incorrect, or not complete enough for advanced users.
I keep thinking that i might start to reduce the UC thread into a more user friendly guide or even a wiki based guide (so that it can be updated easily as required), but then never quite get round to it!
I honestly believe the information within the UC thread is sufficient for even new - non tech users to build an automated setup as long as they are prepared to spend a little time to read & try. The big problem is that its currently spread out over 138 pages!
That aside - if you want to make a new tool - good luck, and i'll happily try it as you develope it & give feedback if required.
Edit:
Hmm, my comments were made regarding the original UC thread, i havent used XDA_UC (yet!)
I am trying to replace the default icons and skin inside the coreplayer.exe with res hacker but reshacker told me that the coreplayer.exe was created with a EXE decompressor and now I don't know how to deal with this,I need your help,thx...
Sure dude, you've come to the right place. Its packed using UPX !
Sure dude, you've come to the right place Its packed using UPX !
Simple
UPX4PPC
UPX4PPC is a utility for you to compress & optimize EXE/DLL files, just like the desktop PC version.
Our machines have few memory and we are always trying to save the RAM. This program helps you in this task, but it is reserved to power users. It allows to compress up to 40% any EXE or DLL file and, better, the consequence is an improvement in performance.
Attention: do not forget to make a backup copy of the original file. Sometimes, the compressed file just do not work and you need to put the original back in place. For instance, you cannot compress the PocketInformant EXE file.
Despite this warning, it is a very good solution to save RAM.
o/~