Related
After careful reading of the big storage (anansky's) ROM thread and hearing people were having trouble with patching ROMs I thought i'd write a small tool to do it for you..
Just select a source image, a destination, choose how many bytes to copy and click 'copy'. All done. It simply copies the desired number of bytes from the begining of one file to the begining of the other.
Hope this helps!
Disclaimer: backup stuff, although i've been developing software for 17 years I am still (partially) human and this software may cause you to implode, kill you pet kitten or bring about world peace. Use with care, and DO SOME READING first
Installtion: put on harddrive and run. If you need the support files extract these in the same directory as the program.
Read this thread first: http://forum.xda-developers.com/viewtopic.php?t=20043
thanks man... great toool
You're welcome - just want to give something back to this amazing forum
interesting stuff...
I'm doing manual edits in rom, but was thinking about smthng, which could just patch them, so user will not need to download the whole rom, just the diffs...
let me try it...
thanx
buzz
buzz_lightyear said:
interesting stuff...
I'm doing manual edits in rom, but was thinking about smthng, which could just patch them, so user will not need to download the whole rom, just the diffs...
let me try it...
thanx
buzz
Click to expand...
Click to collapse
Well if you've any ideas on what you want the utility to do then just let me know - I can knock up something pretty quick to make the job easier
I made this simply because i'll be flashing my Qtek s100 this weekend and didn't want to mess around counting bytes in a hex editor (and possibly getting it wrong) and it doesn't take long to write a patch program!
would be cool, if it can read a text file, where I can say:
SourceBinFile, DestinationOffset, Length
Then it will read those bytes from couple of small binary files. that way I can patch multiple locations of rom.
it would also be nice, if I can specify rom header and your app will first check that against the rom to be patched.
thanx
buzz
Ok I see what you mean...
I think it might be better to do it via a GUI rather than a text file (but i'll add the text file later for you) so you can choose a source, sourceoffset, num of bytes to copy and then 'add' it to the queue. Then you can hit 'GO' and it'll do all the patching in one go. Does that sound ok?
Ok, here's the updated program - this is a beta version which requires some testing so please let me know if this is OK and then i'll produce the next version which will allow you to load and save the queues.
Sorry I didn't have huge amounts of time to test, but i'll post an update later if this turns out to be duff!
great work dangel looks really nice app...
You're welcome...
Perhaps todo:
- Use a relative path instead of selecting them
- Save/load queues from a file (possibly XML)
- Command line processing (so that we can automate patching - this would actually allow you to distribute a patch 'suite' to perform a particular patching task without user interaction)
Small update to support themeing under WindowsXP
Just finished queue save, just doing the load parser
Version 1.2
- Can now save the queue (the files are .cpy files)
- Can now load the queue
The file format is text, but take care when editing - it's best to use the program to generate the files for you...
So does it work?
OK well if anyone needs any updates PM me otherwise i'll leave this one alone for now.
excellent program! Thanks!
Hi all,
my father got MS Visual Studio 2005 some time ago and I just discovered that it's capable of creating mobile applications as well so I'm playing with it, trying to do some cool stuff (program for recording my marks at school atm ). The fact is, that I'm not extremely experienced in C# (in which I'm working in the MSVS2005) so I have to look up syntaxes or parts of code in help database every now and then. I have always succeeded so far, but now I have a problem I need someone to help me with.
I just started working with files, everything is fine, I think i quite understand the syntax and stuff, but I can't figure out how file paths under Windows Mobile work. In help file, they say that this should work:
string path = @"c:\temp\MyTest.txt";
but i think this is for desktop Windows only. If I try to use this in my programme, "Catch (Exception Ex)" command returns error saying: System.IO.DirectoryNotFoundException.
I tried various variants of the file path and the only one working was just plain name of file, for example
string path = @"MyTest.txt"
This way, I managed to write into the file and read the input back..but I couldn't find the file anywhere in my phone's memory :S
So if there was someone who would be so kind and told me how to specify file paths under WM correctly, I would really appreciate it. btw if the "someone" gave me his MSN/ICQ too, and was willing to give me real-time help once a time, it would be absolutely perfect
The root of the Windows Mobile filesystem is "\". If you want to place the file in the temp dir of the root, use this:
string path = @"\temp\MyTest.txt";
Øystein
Hi All,
Wouldn't it be great to be able to control which applications ran on your PDA...Ensuring that your users could not run certain apps would be a real bonus.
So I came across a URL that explained just how to do this...
http://www.satter.org/2007/03/lets_shell_some.html#comment-74156022
Sadly, for me I am on WM6 but only have access to the WM5 SDK and when I tried to carry out the suggestions I failed with the SMS text error:
Change of Device Settings Unsuccessful
Your device settings cannot be changed by Test.cpf
So I am at a dead end. Can anyone else who has interest step in and assist this beginner to get this function working?
I ran the SDKCerts.Cab on my device and the SecurityOff.CPF file. They were successful and I got the SMS message telling me that the changes in SecurityOff.cpf were successful.
I am probably close to a solution but don't have the background to make the last few steps. Can anyone else assist me please?
Have I just a typo in my test.cpf file (on the URL there is a message about the script containing a typo error - I couldn't spot it though...was it fixed?)
All help is greatly appreciated and would deserve a beer or a cyber equivalent.
Many thanks,
PianoSam.
Could you post the wap-provisioning source you used? So I could check for a typo or sumthin.. I've done the same thing as the blogg describes, and it works fine with me..
I on the other hand, wanted to restrict wceload being loaded via Activesync->Add/Remove programs.. but it seems like RAPI doesn't use the same disallowrun settings etc..
But post you cpf file or you code.. and i'll take a look at it.
Hi,
Thanks for the assistance. I have attached a small zip with the various bits and pieces that I have.
My file is the test.cpf file. What I actually wish to do is to prevent Pocket IE from loading...although my test tried to control the clock.exe file.
all assistance is greatly appreciated and you have already renewed my hope that I might be able to do what is needed...
Thanks,
PianoSam
I'll have a look at it.. but it seems that the Test.cpf is just a doc or a rtf file you've renamed? You know this isn't a "cpf" file that wceload.exe can recognize?
I'll have a look at the registry settings within the file and build a cab/cpf file .. so i can test it... i'll let you know how this goes.. unfortunately, i can't reply before tomorrow.
I didn't realise...
Thanks for your help. I just created my test.cpf in word by cutting and pasting the xml script from the url.
I saved as utf-8 and thought job done. Sadly not.
So what should I do instead? forgive me but I don't know the steps to make a suitable cpf/cab file.
Once again THANK YOU for your kindness,
Sam.
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!)