First off, I'd like to thank Sleuth255 for SDAutoRun, and to mousio for his AutoRun tool which provided the inspiration for this project.
SDConfigGen is a command line tool for the PC which inspects a collection of files to be installed, then produces an SDConfig.txt and other associated scripts and provisioning files to allow SDAutoRun to automatically install them.
It differs from mousio's solution in that rather than having SDAutoRun call a MortScript to do all the work, this tool creates an SDConfig.txt to do the majority, only calling scripts for specific functionality when required. Scripts (and therefore MortScript) may not even be required, if nothing being installed needs automation.
Installation
Unzipping the contents of the archive will produce this folder structure:
\
Storage Card\SDConfig\Cabs\
Files\
Scripts\
Settings\
Sys\First things first - to use any of the script-based functionality a copy of the MortScript installation cab file must be placed within the Sys folder. Download MortScript-4.11b7.zip (or newer version) from http://www.sto-helit.de, then extract \cab\MortScript-4.11b7-PPC.cab from it.
Usage
If the name of the Storage Card will be different on your target device, then rename that folder to whatever it will be. Otherwise, just leave it as it is.
Within the sub-folders of SDConfig, add the files you want to be installed.
Cabs:
Any .cab files in this folder will be installed. If the installation of a .cab file requires user interaction (to confirm a license window, for example), then create a .mscr script file of the same name containing instructions to be executed while the cab file is being installed.
For example, if you need to install a cab file: "eWallet-PocketPC-Install.cab",
create a file called "eWallet-PocketPC-Install.mscr" too. This file contains
MortScript to be run while the cab installer is being run, for example:
Code:
windowTitle = "Software License Agreement"
WaitFor(windowTitle, 60)
SendLeftSoft(windowTitle)
Note that you don't need to worry about actually installing the cab, or waiting for installation to finish - just write the automation code itself.
The SDAutoRun UI will be hidden while an interactive cab is being installed like this, and a MortScript status window shown instead. The device will be responsive to user input, so if any non-automatable interaction is required, that can be done manually.
Files:
After the cab files have been installed, all files in this folder will be copied directly to the root folder. To copy files to sub-folders, place them in sub-folders of this folder. For example, to copy files to the Windows folder, create a Windows folder here and place the files within it.
Standard (English) folder names will automatically be replaced by variables, so files in the "Files\Program Files" folder here will be copied to %CE1% folder by SDAutoRun.
The file copy operation is actually performed by generating a CopyFiles.xml provisioning file in the Sys folder, and it is this that goes in the SDConfig.txt file. This method was chosen as it avoids the path length limit of copying directly in SDConfig.txt, and allows for the %CEn% variable subsitution scheme.
Settings:
After the files have been copied, any settings in this folder will be applied. Settings may either be .xml provisioning files (which are added directly to SDConfig.txt), or registry data in .reg, .rgu or .cereg files. Registry data files will be automatically converted to xml provisioning files within the Sys folder, which are then added to SDConfig.txt.
Scripts:
After the settings have been applied, any .mscr scripts within this folder will be executed. SDConfigGen will generate instructions in SDConfig.txt to automatically handle copying them to the \Temp folder and renaming them to replace spaces by underscores before execution if required.
Note that the device will not be interactive at this point, so don't write scripts that require user interaction.
Sys:
Apart from placing a copy of MortScript-4.11b7-PPC.cab in here, you shouldn't touch the contents of this folder; they will be automatically cleaned out and generated by the SDConfigGen tool.
Notes
I've provided RegToXml as a standalone .exe file so that registry data files can be manually converted to .xml provisioning files, if required. This is not generally necessary, though, as it will occur automatically as part of the SDConfigGen process.
Due to limitations of SDAutoRun, during installation some files need to be copied to the \Temp folder on the device before execution. A TempCleanup.xml provisioning file is generated in the Sys folder by SDConfigGen which is the last thing executed by SDConfig.txt. It should remove any temporary files that were placed in the \Temp folder, but will not remove the folder itself, or any other files within it.
SDAutoRun also requires that SDConfig.txt be ASCII, which means that if any files contain characters outside that range (such as accented characters), they can not be directly referenced. SDConfigGen will automatically detect this, and generate provisioning XML files to transparently rename the files before processing them, then back again afterwards.
The last statement in the SDConfig.txt is the RST: Reset statment, to reset the device.
The only part of the file structure that can be changed is the name of the "Storage Card" folder - the other folders cannot be renamed or moved. By default, when the SDConfigGen tool is run, it works with the first sub folder under the folder the .exe file is placed. To override this behaviour, pass the folder path to SDConfigGen.exe as a command line argument.
Cabs, settings and scripts are executed in alphabetical order, grouped by subfolder. Subfolders will be executed first, so for example the contents of Cabs\Prerequisites\ would be installed before the files directly in Cabs\ (but after files in Cabs\A\). All interactive cabs are executed first, followed by non-interactive ones.
All generated files (except SDConfig.txt) are in Unicode UTF-16 encoding.
To have SDConfigGen create a log file of the generation process, use the SDConfigGenWithLog.bat file included in the archive. It will create a results.log file containing the messages that would normally be output to the console.
This is still an early version, so there will probably be bugs with it. I've used it successfully for setting up my own device several times now, but I can't make any guarantees. Please do post any bug reports or suggestions here though!
Alex
Updates
0.6:
All output files are now in UTF-16 encoding, with the exception of SDConfig.txt, which is in ASCII.
If files referenced by SDConfig.txt have names containing non-ASCII characters, provisioning files to automatically rename them before they are accessed, and to restore them afterwards will be generated.
Subfolders are now supported in the Cabs, Settings and Scripts folders. Files within subfolders will be processed first, in alphabetical order of subfolder name.
File folder variable substition made case insensitive
Added SDConfigGenWithLog.bat file for easy logging of output to a log file
0.5.1:
Removed .svn files from the file structure (oops!)
0.5:
Made warning message on skipping registry files less confusing
RegToXml: Now supports empty values for String, MultiString and Binary values
RegToXml: Made ,ore robust to invalid data - if a value contains invalid data, only that value is skipped.
RegToXml: The line number is now reported with any error or warning message.
RegToXml: Whitespace allowed to surround the = in value lines.
0.4:
RegToXml: Fixed nesting bug with registry key deletion conversion
RegToXml: Now supports comments (lines starting with ; )
0.3:
RegToXml now assumes that registry files without Unicode BOM's are encoded in the system default ANSI codepage, rather than UTF-8 (this means that if your registry file is UTF-8, it must contain a Byte Order Mark to be read correctly)
0.2:
Files are now installed in alphabetical order by file name (within their own group). For example, first interactive cabs A-Z, then non-interactive cabs A-Z. This allows control over installing cabs that require others to be installed before or after them.
.NET Framework (required)
Lookin Mighty Fine Siuer.
Not in the Testing Time yet.
But does the scripts folder eventually combine the scripts into one?
(lazy Bum At Work, Not Able to test it)
No, the scripts in the scripts folder are not combined into a single script, they are all executed separately. Would there be some benefit to trying to combine them into a single script before execution?
AlexVallat said:
No, the scripts in the scripts folder are not combined into a single script, they are all executed separately. Would there be some benefit to trying to combine them into a single script before execution?
Click to expand...
Click to collapse
No, you are absolutely right there is now good reason for it.
It's better to have them seprated, makes finding **** Ups easier.
Don't know what i was thinking or why..
AlexVallat,
Thanks for your job, you soft is amazingly simple which is a great pro compared to SASHIMI for instance.
So yhis afternoon I started to put all my files in the appropriate folders and when I launch SDConfigGen with the folder path I don't get in the config.txt file \Storage Card\ before the files to execute but the path I gave as parameter. I think transforming the path given into \Storage Card\ could help.
One other point, as a poor French guy your RegToXml converter does not handle all the French extended character set such as é, à, ... Could you make it support this characters.
Anyway for now it is fully usable but requires SDConfig.txt file edition before launching the whole process. Tomorrow it will be hands-on time as I plan to upgrade my Polaris ROM so more news to come regarding SDCofingGen usage.
The_Steph
The_Steph said:
AlexVallat,
Thanks for your job, you soft is amazingly simple which is a great pro compared to SASHIMI for instance.
So yhis afternoon I started to put all my files in the appropriate folders and when I launch SDConfigGen with the folder path I don't get in the config.txt file \Storage Card\ before the files to execute but the path I gave as parameter. I think transforming the path given into \Storage Card\ could help.
One other point, as a poor French guy your RegToXml converter does not handle all the French extended character set such as é, à, ... Could you make it support this characters.
Anyway for now it is fully usable but requires SDConfig.txt file edition before launching the whole process. Tomorrow it will be hands-on time as I plan to upgrade my Polaris ROM so more news to come regarding SDCofingGen usage.
The_Steph
Click to expand...
Click to collapse
Hm my pall had the same thing but changing to Unicode seemed to solve his XML issue. NOt sure if this is the same but worth the try.
Great work alex!
Question:
Anyway to verify the syntax of the provisioning XML files?
Any tools out there that can create these files or verify them? I think a tool like this would be great.
NEVERMIND! I just saw your reply in the reg2xml converter thread! THANKS!
The_Steph: Thanks for your comments!
The idea with the path is that the name of the folder is used to control the name of the Storage Card on the device. So if you name your folder Storage Card, that's what goes in the SDConfig.txt. If, on your device, it has a different name (due to language changes, or whatever), then you need to rename the folder appropriately.
Thanks for the bug report about accented characters in RegToXml. I will fix that and post an updated version soon.
gtxaspec: I could verify that the files were valid XML, but the more useful check that they contain valid provisioning instructions is beyond the scope of this project. Not least because the documentation describing what are valid instructions is confusing and can be inaccurate. With anything other than the file and registry providers, it usually ends up being a case of trial and error. With the file and registry providers, using the auto-generation capabilities of SDConfigGen will avoid most surprises.
Alex
Version 0.3 released
I've just updated the first post to release version 0.3. This should address the accented characters issue raised by The_Steph, however it does mean that if your registry file is UTF-8 encoded, it must include Byte Order Marks to indicate this. Otherwise, it will be assumed to be encoded in the system default code page.
I've also added a feature that files are now installed in alphabetical order (within each group). If you need to make sure that certain cabs are installed before others, this can now be done by renaming them, usually by including a numeric prefix.
Alex
reg2xml bugs
Hi Alex,
Converting everything to xml and using standard provisioning is an interesting approach!
Only obviously reg2xml has got some problems still with .reg files containing certain characters:
I've attached you a sample file which is not converted correctly at three points, each with a different error cause.
- Comments (Lines beginning with ";") in the .reg files are sometimes (not in every case, could not see what the trigger is) leading to an aborted conversion.
- Some characters like the arrow character (ASCII 27/1BHex) are also a problem.
Maybe the attached file helps in finding the bug.
BTW: Do you also have a tool that is converting just the other way around: From XML to reg indstead of from reg to XML?
Sometimes I need to have a .reg file instead of an .XML. And importing the XML and then trying to find all registry entries to export it back to a .reg can be a very tedious thing when the imports are not all together in one registry branch.
Thanks!
Thanks for the bug report, asango. Yes, I forgot about comments, I'll fix that and release an update soon. I'm looking into what the best way to handle control characters like 0x1B is (which is 'Escape', according to the ASCII chart I'm looking at). Obviously crashing is not an acceptable behaviour, so I'll have some sort of fix for it.
I don't have a XmlToReg tool, but it sounds like a good idea - I'll probably write one over the weekend.
Alex
Great, looking forward to that, thank you!
Version 0.4 released
The first post has been updated to version 0.4. RegToXml has been updated to add support for comments in .reg files.
Unfortunately there appears to be no way to include control characters in an XML file. If the character itself, or even the character entity (like , then the file is regarded as malformed and not accepted. I have therefore not been able to do anything to fix this (sorry asango!).
If anyone knows of a way that a provisioning file could be used to set a registry string value containing these characters, please let me know.
On a more positive note, the requested XmlToReg tool is up - I've given it its own thread here: XmlToReg.
Alex
Yes, the comments are now handled corectly, perfect!
Some other thing is still an issue:
test.reg: Converting...
test.reg: Conversion failed. (Unexpected value format: dword) Skipping.
In this case the output file is not generated at all, seems that not only the value is skipped but this causes the whole file not being written.
This leads to another suggestion: Would it be possible to indicate the line number where a problem happened?
This would make it much easier to find the problem.
And regarding the non handled escape characters:
This also leads to aborting. Would it also be possible to just skip them and issue a warning but go on with the conversion and with writing the outout file for the rest of the entries?
Now that is odd. "dword" is a perfectly valid value format, it shouldn't have produced that error. Any chance you could send me the .reg file that produced it?
Line numbers should be do-able, I'll add that to the next version.
The "skipping" message there referred to the "test.reg" at the start of the message, not to the dword value. I agree it looks misleading as it is currently worded though, I'll improve that.
About recovering from errors and skipping only invalid values rather than the whole file - this will be quite tricky. By the time I am notified of invalid characters by the XmlWriter, it has already given up in a sulk and can't be persuaded to continue writing any further. I'll need to do some sort of pre-vetting before passing data on to it. If I come up with any good ideas on how to do this, I'll include it in the next version.
Alex
asango, here's a candidate RegToXml.0.5.0 - could you check if it is still reporting the "Unexpected value format: dword" error with your file? It now reports line numbers, which might help track down the problem. It should also be able to recover from an invalid value and skip just that value, although I'm not sure how well that is working yet.
Alex
Hi Alex,
Great, the line numbers are making things much easier and this way I even found the reason for this error very easily:
Here's the point where it is failing:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"NITZEnable"= dword:00000001
...with this error message:
test.reg: Converting...
[Line 194] Error: Invalid value (Unexpected value format: dword)
Skipping: HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL\NITZEnable
Done.
As soon as I'm deleting the blank between the "=" and "dword" everything is ok.
Maybe you can allow blanks after the "=" in general?
This would solve this issue definitely
And yes, by the way the xml file is now generated despite of this error, very good!
Asango
Hmm... I'm not sure whitespace is supposed to be allowed around the = sign. It doesn't make anything ambiguous though, so there's no good reason not to relax the matching. Try this 0.5.1 which allows whitespace around the = sign, hopefully that should now parse your file correctly.
Alex
Yes, now I can see no other issues with the RegToXml tool, good work!
Also the whole cold boot import is ok with one exception:
Only the CopyFiles.xml which is generated by the SDConfigGen.exe is not copying all the files from the "Files" diectory during its execution.
Tried to import that xml manually with the xml option of Taskmgr and also got an error, but since the error is *very* uninformative and not showing the line number and my CopyFiles.xml is rather big I could not find the problem.
Could it be that the reason for the error is that if a file is already existing or read only that this will stop the rest of the import?
asango said:
Yes, now I can see no other issues with the Only the CopyFiles.xml which is generated by the SDConfigGen.exe is not copying all the files from the "Files" diectory during its execution.
Tried to import that xml manually with the xml option of Taskmgr and also got an error, but since the error is *very* uninformative and not showing the line number and my CopyFiles.xml is rather big I could not find the problem.
Click to expand...
Click to collapse
Second hands-on day with SDConfigGen and I have the same issue with v0.4. CopyFiles.xml is not executed at all. Probably a syntax error issue as stated by asango (I've done the same tests as him).
The_Steph
Intro
Welcome; I wanted to offer a little "something" back to the XDA community in the hopes that it will benefit others and to show my appreciation to the folks that make XDA the great community that it is.
If you've gotten excited about the idea of cooking your own ROM's, you've probably had to spend several weeks of reading, asking questions, getting acquainted with your facility, and figuring out where you're going to plug your utensils and/or appliances. Now comes the easy part, cooking quality ROM's ... right? It's gotta be simple after that, I mean that was all the hard stuff ... right? Well ...
As any seasoned chef will tell you, the quality of a meal greatly depends on quality ingredients, utensils, and appliances. Ingredients are a personal preference and some chefs can make Macaroni & Cheese taste like the best meal in the world; and how do they accomplish this? In many cases, they use quality utensils and appliances and understand the limitations of them.
Equipping your kitchen with the right tools ensures that you're able to provide quality meals to your patrons - resulting in return visits.
Outro
The goal of this thread is encourage seasoned chefs to share their knowledge of quality tools that they use in their day-to-day activities of ROM cooking.
Some of these tools are free, others have a trial version, and others must be purchased. The goal isn't to promote any one specific tool, it is to provide objective (and hopefully unbiased) reviews of these tools. Lastly, a moderator or senior chef may periodically review and cleanup this thread/post to ensure that it remains on-topic and consistent in format ... so don't take offense; you'll always be credited for your contribution.
Format For Each Post
Take a moment to review existing tool reviews; the goal is to share your experiences in using the tool. The review should contain the following information:
Name of the tool (same as in Title of post)
Version
Author
Link to tool
Cost (Free, Adware, Trialware, Purchase)
Reviewed by [your XDA member name]; in case the post is moved near the top of the thread at a later date.
Summary of what the tool does (uses) and any example you can think of.
Tips on how to use the tool; things you discovered when using the tool.
Potential pitfall (gotcha's) when using the tool; things you discovered when using the tool.
Reference threads (optional); links that might offer some additional usage information.
No attachments please. Post them in the original thread for the tool.
List Of Tools To Review
List Of Tools To Review
Here's a list of tools that I'd like to review and add to this thread. The goal is to review the various tools that chefs will often use while preparing their ROMS; any seasoned chefs (aka volunteers)? If so, post your review in the thread.
CABARC: MS Cabinet SDK in self executing zip
CABtoEXT
CeRegEditor
DSM Assembler Manifest: DSM Editor
EmEditor: advanced string search & editor
HEX Workshop: Intermediate HEX editor
ini2reg : Preformatted ini file for customized Registry extraction
IDA Pro: assembler/disassembler (extremlely advanced)
NBHextract: .NBH Extraction
NBHUtil: .NBH Generation
Notepad2: intermediate multi-editor (lua, xml, cmd, etc.)
Paint.NET: graphics editor
ProvXMLCreator: Autoconfiguration for WiFi, Certificates and email
PE Explorer: resource editor
PHM Registry Editor
PreKitchen Tool: import SYS to kitchen
RECMOD: recode/decode modules
REG2XML: convert .reg and .rgu files to xml
RegLogger: registry logging
ROM Extractor (Link 2)
TrayGUID PC: generate unique GUID to clipboard by clicking it
UAE Debugging Tool (UAEDT = Unrecoverable Application Error Debugging Tool)
WinCE CAB Analyzer (MSCEInf): .CAB extraction
WinCE CAB Manager: .CAB creation
XVI32: basic HEX editor
Resource Builder
Windows Mobile Developer Power Toys
Any others? Feel free to post a request in the thread or send me a PM.
Quick Post Index
Quick Post Index
Sorted alphabetically; at least I hope it is.
CAB/OEM Package Converters
CAB2OEM
CAB to OEM to EXT GUI Suite
Package Creator
Device Side Manifest (.DSM) Editors
BuildDSM
DSM Analyzer
DSM Builder
DSM Dependency Dumper
DSM Editor
Editors
EditPad
SciTE
Syn Text Editor
XML Notepad
Graphics (.BMP, .JPG, .PNG, etc.)
GNU Image Manipulation Program (GIMP)
IcoFX
Kitchen Porting Tools (SYS, OEM, etc.)
Initflashfiles Hex2Text
SYS Porting Tool For Ervius Kitchen
Process, Registry
FDC Task Manager (aka DotFRED)
Registry Workshop
Resource (.DLL, .EXE, etc.)
Dependency Walker
File Editor Suite
PEinfo
Resource Hacker
ROM Squeezer
Search/Comparison/File Managers
Beyond Compare
Compare It
Directory Opus
Senax's Library Of Links
Senax's Library Of Links
There are links to SDK's, developer tools, power toys and more. More links are better than less, so we say in Holland Don't you agree??
Have a nice day folks,
Senax
:UPDATE:
How could I forget to mention;
System Center Mobile Device Manager Resource Kit Tools
That was my left sleeve of links...
Q: Are you going to make it any easier for us?
A: That's a good question! No, (not for the Moderator(s) ) I've no intention of that just yet. First more power links, while thoroughly reviewing stuff, then searching for new links (references) and so on. Then a new review
Have a nice day / night while clicking all them links in ...,
Senax
Here some links to SDK's to inform others and get them reviewed:
Windows Mobile 5.0 SDK for Pocket PC
Windows Mobile 5.0 SDK Documentation
Windows Mobile 6 Documentation
Windows Mobile 6 SDK Refresh
Windows Mobile 6 SDK Documentation
Windows Mobile 6.5 Developer Tool Kit
Windows Mobile 6.5 Documentation
Windows Mobile 6.5.3 DTK
.NET XML PowerToys:
Generating XML Documents from XML Schemas
The XML Diff and Patch GUI Tool
Using the XML Diff and Patch Tool in Your Applications
Using the XSD Inference Utility
XML Tools Update
MSXML SDK
Power Toys for .NET Compact Framework 3.5
&
NETCFv35.Messages.EN.wm.cab ; exception messages
Windows CE CAB Installer SDK (though named SDK its more a CDK (Commercial DK), because you've got to pay $5 for it).
Awesome for UC (User Customization).
Microsoft SDKs (every and all SDKs from MS) for;
Azure Services Platform
Windows Desktop
Office
Devices
Windows Live Services
Server Technologies
Social
Games
Web Development
Other
Developer Tools:
Installing Developer Tools on Windows Mobile
Development Tools and Resources for Windows Mobile
Development Resources for WM on xda-developers.com
UPDATED: http://forum.xda-developers.com/showthread.php?t=445396
What Microsoft does not tell is that when they shot themselves in the foot with 'Vista', they were forced to introduce Win7 earlier as planned. Thus VS2008 (read WM) all its links have been moved to > :NULL
Well maybe not, though I've a hard time finding them .. and I do know how to tweak-search. We (the users) are forced into using VS2010 now! It's all 'embedded' now (cq sort of virtual). Ah, well.. it's not that bad
Windows Mobile 6 Localized Emulator Images
http://www.microsoft.com/downloads/...A8-1DD7-426F-A913-4F370A65A582&displaylang=en
Brief Description
This package includes localized Windows Mobile 6 emulator images that can be used with Visual Studio to test applications on different localizations or simply as standalone emulators without Visual Studio 2005!
Microsoft Power Toys:
Windows Mobile Network Analyzer PowerToy (Released with WM5 though usable with WM6)
Windows Mobile Device Security Manager PowerToy(Released with WM5 though usable with WM6)
General (Embedded) WM 6.x CE PowerToys link
Nowadays there 'll be no more Power Toys from Microsoft, instead we get:
Not (all) Windows Mobile specific: Microsoft Solution Accelerators & ~ A-Z technet :Free power(toys);
MSDN Code Galery third party resources
Windows Phone Developer Tools Beta
XML Notepad 2007 References:
Since this nice free editor is on CodePlex it is nice to mention this link;
http://xmlnotepad.codeplex.com/
I also found this link in my BookmarX_Manager; http://msdotnetsupport.blogspot.com/...-tutorial.html (their MORE button is the best TUTORiAL I've seen online about XML Notepad!!)
Hopper
There's a 'new' Hopper (device stress tester included In WM Developer Power Toys) for WM6> (not WP7). Hopper its two versions WM5 WM6; http://forum.xda-developers.com/show...45#post7549645
[PC] works for device too if its cradled.
Q: Is a file signed with a signature?
A: Let us check that using SystemInternals_Suite (click on the left of that page) its CLI SigCheck.exe
SigCheck; Verify that images are digitally signed and dump version information with this simple command-line utility.
ARM
These links are NOT for a review, these are to inform people about ARM processors used in WM and WP:
ARM Classic Processors
ARM Infocenter
ANDROiD SDK
http://developer.android.com/index.html
Phoenix SDK
Phoenix is the code name for a software optimization and analysis framework that is the basis for all future Microsoft compiler technologies. The Phoenix framework is an extensible system that can be adapted to read and write binaries and MSIL assemblies and represent the input files in an IR, which can be analyzed and manipulated by applications by using the Phoenix API. The code can then be written in binary or JITable form for execution.
It enables teaching and collaborative research in code generation, optimization, program analysis, binary transformation, and software correctness. Phoenix is used as a research platform by Microsoft Research and will be the universal compiler backend for upcoming Microsoft languages and development tools.
Phoenix SDK April 2008
How to install Phoenix SDK
Senax's Library of Links ... continued
AT Commander
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[PC] ATCommander;
http://atcommander.com
The above link does not provide us with much information/links thus I searched some more
and came up with; http://atcommander.com/download/. Same page though not reachable via the first link. Anyway here you can download the latest .zip or .exe.
Note: My anti virus started to whine as soon as I unpacked the zip, though when I ran it in a VMware workstation everything worked smoothly.
Also do not forget to check this link;
http://atcommander.com/public/
Here some AT Commands reference links provided in two pdf files;
http://atcommander.com/download/AT_C...Specification/
[WM5/6] ATCommander;
http://forum.xda-developers.com/showthread.php?t=375395
Senax's Library of Links ... continued
Reserved for future expansion.
Resource Hacker
Name: Resource Hacker
Version: 3.5.2 beta
Author: Angus Johnson
Link: http://angusj.com/resourcehacker
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
Resource Hacker is a freeware utility to view, modify, rename, add, delete and extract resources in 32bit Windows executables and resource files (*.res). Cursor, Icon, Bitmap, GIF, AVI, and JPG resource images can be viewed and WAV, MIDI audio resources can be played. Menus, Dialogs, MessageTables, StringTables, Accelerators, Delphi Forms, and VersionInfo resources can be viewed as decompiled resource scripts. Menus and Dialogs can also be viewed as they would appear in a running application.
Resources can be saved as image files (*.ico, *.bmp etc), as script files (*.rc), as binary resource files (*.res), or as untyped binary files (*.bin). Resources can be modified by replacing the resource with a resource located in another file (*.ico, *.bmp, *.res). Dialog controls can also be visually moved and/or resized by clicking and dragging the respective dialog controls prior to recompiling with the internal compiler. Additionally, resources can be added to an application by copying them from external resource files (*.res).
Tips:
Always keep a copy of the unaltered file as a backup.
Gotcha's:
Even though it is possible to alter the resources, some applications automatically resize controls and dialogs during operation.
Some applications may cease to function when the resource file is altered.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=511876
http://forum.xda-developers.com/showthread.php?t=562645
http://asukal.seesaa.net/article/6114096.html
Beyond Compare
Name: Beyond Compare
Version: 3.1.10
Author: Scooter Software, Inc.
Link: http://www.scootersoftware.com
Cost: Trialware, Purchase
Reviewed By: aruppenthal, Sous-Chef
Summary/Review:
Beyond Compare allows you to quickly and easily compare your files and folders. By using simple, powerful commands you can focus on the differences you're interested in and ignore those you're not. You can then merge the changes, synchronize your files, and generate reports for your records. You can compare entire drives and folders at high speed, checking just sizes and modified times. Or, thoroughly verify every file with byte-by-byte comparisons.
Once you've found specific files you're interested in, Beyond Compare can intelligently pick the best way to compare and display them. Text files can be viewed and edited with syntax highlighting and comparison rules tweaked specifically for documents, source code, and HTML. Data files, executables, binary data, and images all have dedicated viewers as well, so you always have a clear view of the changes. Beyond Compare is a "must have" tool; it will save hours of time. There is no better way to compare new builds and look for what has changed. When properly configured, it can display file versions which make integration of multiple sets of OEMdrivers a breeze. Swapping SYS files is never easier; you get to see dates of creation and can easily move files from one set to the other with a few clicks.
Here are some examples of how comparison can be used:
Compare one .\SYS folder version (ex: 23541) against an updated .\SYS folder version (ex: 23549) so as to determine what changes have occurred in registry files.
Compare one version of a ROM package (ex: Manila_2.1) against a newer version of the package (ex: Manila_2.1.1).
Compare a device ROM (ex: Mega_HTC_Europe_1.28.401.4) against another ROM (ex: Mega_TMO_UK_1.33.110.2) of the device to see what the HTC changed.
Compare specific files such as .XML, .PROVXML, etc.
Tips:
You can copy the installation folder from your system to an external drive. You can then launch the .EXE from the external drive on another system - no need for installation.
Enable the "Send Files To The Recycle Bin" option to avoid having a file permanently deleted when it is removed from the list.
Gotcha's:
Editing INITFLASHFILES.DAT with the built-in editor is not recommended as it may cause corruption resulting in ROM issues.
Reference Links:
http://forum.xda-developers.com/showpost.php?p=5979483&postcount=11
http://forum.xda-developers.com/showpost.php?p=6251478&postcount=27
IcoFX
Name: IcoFX
Version: 1.6.4
Author: Attila Kovrig
Link: http://icofx.ro
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
IcoFX is an all-in-one freeware icon editor solution for icon creation, extraction and editing. It is designed to work with Windows XP, Windows Vista, Windows 7, Windows CE and Macintosh icons supporting transparency.
Easily convert your favorite images into icons, or icons into images. IcoFX gives you the possibility to create icon libraries or change icons inside EXE files. You can extract icons from other files, including Windows Vista, Windows 7 and Macintosh files. You can easily work with multiple files using the batch processing capability of IcoFX.
Tips:
Always keep a copy of the unaltered file as a backup.
Choose free images to avoid potential copyright pitfalls.
Gotcha's:
None discovered.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=511876
Dependency Walker
Name: Dependency Walker
Version: 2.2
Author: Steve P. Miller
Link: http://www.dependencywalker.com
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
Dependency Walker is a utility that scans any 32-bit or 64-bit Windows module (exe, dll, ocx, sys, etc.) and builds a hierarchical tree diagram of all dependent modules. For each module found, it lists all the functions that are exported by that module, and which of those functions are actually being called by other modules. Another view displays the minimum set of required files, along with detailed information about each file including a full path to the file, base address, version numbers, machine type, debug information, and more.
Dependency Walker is very useful for troubleshooting system errors related to loading and executing modules. Dependency Walker detects many common application problems such as missing modules, invalid modules, import/export mismatches, circular dependency errors, mismatched machine types of modules, and module initialization failures. It handles all types of module dependencies, including implicit, explicit (dynamic / runtime), forwarded, delay-loaded, and injected. For example, a quick way to determine what additional packages may be required for an application:
Open each .DLL/.EXE file in the package (ex: YouTube)
Note the files that are flagged as missing.
Search the source (usually an extracted ROM) for those files; odds are you'll need the entire package contents where the file is found.
Repeat the process until all of the necessary files are found.
Dependency Walker runs on Windows 95, 98, Me, NT, 2000, XP, 2003, and Vista. It can process any 32-bit or 64-bit Windows module, including ones designed for Windows CE. Windows CE modules use the same module format (known as the "Portable Executable" format) that is used for modules written for Windows 95, Windows 98, Windows Me, Windows NT, Windows 2000, Windows XP, Windows 2003, Windows Vista, and beyond. There is no version of Dependency Walker that actually runs on Windows CE, but you can open Windows CE modules with Dependency Walker on a standard Windows computer.
Tips:
Create a folder with all of the common WinCE files in it and set a custom search order that includes this path and save it to a file.
Use RECMOD to recode modules that may be required.
Use the "/d:your_file.dwp" command line option to pass a custom search order file to Dependency Walker.
Gotcha's:
Dependency Walker automatically tries to locate dependent modules using the default Windows module search path. For Windows CE modules, this can cause errors since non-CE modules may be found in the default search path. To fix this, you can use Dependency Walker's "Configure Module Search Order" dialog to remove all standard paths and then add a private folder of your own that contains only CE modules.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=576027
FdcSoft Task Manager (aka dotFRED Task Manager)
Name: FdcSoft Task Manager (aka dotFRED Task Manager)
Version: 3.3
Author: FdcSoft (aka dotFred)
Link: http://www.dotfred.net/TaskMgr.htm
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
The Task manager application is a bunch of several useful tools in just one tool. It includes a Process manager, CPU usage, Application Manager, Service Manager, Device Manager (only WM2005 and above), Windows Manager, Notification Manager, IP Config utility, Ping utility, Net Stats utility, Registry Editor, and Run program utility.
Although, the application is intended to run on a Mobile Device, it is an excellent tool to use during the preparation of OEM packages. For example, the following procedure speeds up the process of converting from .CAB to OEM:
Copy the files from extract .CAB to the device
Import the registy settings
Process the .PROVXML files.
Reboot the device
Test application
Tips:
The application can run from an SD card.
.RGU files can be renamed to .REG; make sure to remove the hidden, system file attributes.
Gotcha's:
.PROVXML files require a minor adjustment; see reference link below.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=519548
Directory Opus
Name: Directory Opus
Version: 9.5.3
Author: GP Software
Link: http://www.gpsoft.com.au
Cost: Trialware, Purchase
Reviewed By: ceesheim
Summary/Review:
Directory Opus 9 is a Windows File Manager & Explorer replacement that includes, user-definable file display views, User-definable toolbars, menus, file types, powerful image and file viewers, built-in ZIP and Secure SSL/SSH FTP, easily synchronize files & find duplicates, quick or advanced search and rename functions.
The file manager is extremely useful for moving files between folders, making backup copies of files, viewing pictures and playing sounds, running other utility programs on lists of files, deleting unwanted files and many other "housekeeping" tasks. If you are working with a lot of files in kitchens or Manila, this is a must have.
Tips:
Take a few moments to get familiar with the options.
Can view .XML , HEX , .TXT , .DOC , .CPR , .PROVXML , .MSCR , .DSM , .RGU And many more
In view mode it can tell you if a manila file is a lua or a QTC1 file (in HEX)
Download lot of Plugins & Media Capabilities (RTF-Viewer , CSV-Viewer , Source Code Viewer , Postscript-Viewer , RVF File , EXE/DLL Metadata)
Gotcha's:
None discovered.
Reference Links:
None.
XML Notepad 2007
Name: XML Notepad 2007
Version: 2.5
Author: Microsoft
Link: http://www.microsoft.com/DownLoads/...49-787d-4118-ba5f-4f30fe913628&displaylang=en
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
XML Notepad 2007 provides a simple intuitive user interface for browsing and editing XML documents. XML Notepad provide synchronized Tree View with Node Text View for quick editing of node names and values, incremental search (Ctrl+I) in both tree and text views, so as you type it navigates to matching nodes, Cut/copy/paste with full namespace support, drag/drop support for easy manipulation of the tree, even across different instances of XML Notepad and from the file system.
Additionally, XML schema are instantly validate while you edit with errors and warnings shown in the task list window. It includes intellisense on expected elements and attributes and enumerated simple type values, inplace HTML viewer for processing xml-stylesheet processing instructions, built-in XML Diff tool, support for XInclude, dynamic help from XSD annotations, and goto definition to navigate includes and XSD schema information.
It's a must have when working with .XML and .PROVXML files.
Tips:
Ensure that .NET Framework v2.0 (or higher) is installed
Gotcha's:
None discovered.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=519548
Field Notes: Beyond Compare
Name: Beyond Compare
Version: 3.1.10
Click to expand...
Click to collapse
Hi Hilaireg Long time no talk
I want to emphasize the usage of Beyond Compare. This is the MOST important tool a chef can own. It will save hours of time. There is no better way to compare new builds and look for what has changed. When properly set up it shows file versions making integration of multiple sets of OEMdrivers a breeze. Swapping sys files is never easier as you get to see dates of creation and can easily move files from one set to the other with two clicks.
There is one thing not mentioned as far as cons. Using it on initflashfiles.dat is not recommended. Every time I have done so major issues followed by a restore of the original files.
Also when using beyond compare be SURE to set it to send files to the recycle bin. If not it will permanently delete them
EditPad
Name: EditPad
Version: Lite
Author: Just Great Software Co. Ltd.
Link: http://www.editpadpro.com/editpadlite.html
Cost: Free (Lite), Purchase (Pro)
Reviewed By: Laurentius26
Summary/Review:
EditPad Lite is a general-purpose text editor, designed to be small and compact, yet offer all the functionality you expect from a basic text editor. EditPad Lite works with Windows 98, ME, NT4, 2000, XP, Vista, and 7.
Additionally, You can open as many files in EditPad at a time as you want and change between the open files by clicking on their tabs without the hassle of overlapping windows. EditPad reads and writes UNIX (LF only) and Mac (CR only) text files (in addition to DOS/Windows CR+LF files, of course). EditPad natively supports Unicode text files and text files encoded in a variety of legacy code pages. EditPad supports all Windows and ISO-8859 code pages, plus a wide selection of DOS, KOI8 and EBCDIC code pages.
This means EditPad can edit any text file, whether it was saved on a Windows or Linux computer, an old DOS PC or an IBM mainframe. EditPad fully supports double byte character systems (DBCS) so you can edit texts written in Far East languages, such as Chinese, Japanese or Korean, as easily as those written in European languages.
EditPad is a very handy editor for viewing/editing .rgu, .dat, .xml, .html, and multiple formats - a must have for your kitchen.
Tips:
If you run EditPad again when there is already an instance running, the file(s) you wish to edit will be opened by the existing EditPad window. This means there will be at most one EditPad window open, which will save you from a lot of task switching. Of course, if you do need more instances, simply pick View|New editor from the menu.
EditPad puts an icon in the system tray that remains visible, even if EditPad is closed. This way you have easy and fast access to EditPad, without the need to keep it running all the time.
Gotcha's:
None discovered.
Reference Links:
None.
DSM Editor
Name: DSM Editor
Version: 1.7
Author: ervius
Link: http://forum.xda-developers.com/showthread.php?t=523139
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
In early kitchen and ROM cooking, chefs used to delete Device Side Manifest (.DSM) files from OEM packages that resided in the .\PACKAGES and/or .\EXT folder. Other chefs would delete the .DSM file and create an empty version of a .DSM file as a placeholder. As we learned more about the Windows Mobile, we discovered that .DSM files contained pertinent information that was used during the compilation of a ROM and should be properly managed. DSM Editor is a utility to view and modify components of a .DSM file .DSM such as certificates, dependencies, shadow order, and list of modules/files.
A Device Side Manifest file (.DSM) describes the contents of a package and has the name <GUID>.DSM. Each package has its own .DSM file. The .DSM file is a binary file and the format may change at any time. The .DSM file is created by parsing a package definition file, package shadow file, and a build manifest file. Each item specified within a build manifest file is used to determine the item's file type.
The .DSM file contains the following information:
Public key certificate data used for signature validation.
Version information which includes the previous version of a package so as to create a delta package between an older or baseline package and a new package.
Package GUID
Dependency GUID information
File names and file information in the form of raw file size and original VBase for MODULES so they can be re-based and differentiated during an update.
Tips:
Always keep a copy of the unaltered file as a backup.
A .DSM file should contain a complete (exact) list of all modules/files found in the package folder.
The .RGU file should be excluded from the .DSM file.
Kitchen-specific files should be excluded from the .DSM file.
Gotcha's:
Hidden (H) and/or System (S) attributes may need to be cleared (ATTRIB -s -h -r) from .DSM files before they can be edited.
Requires .NET Framework.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=520009
DSMBuilder
Name: DSMBuilder
Version: 2008-08-08
Author: anmendes
Link: http://forum.xda-developers.com/showthread.php?t=412272
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
In early kitchen and ROM cooking, chefs used to delete Device Side Manifest file (.DSM) files from OEM packages that resided in the .\PACKAGES and/or .\EXT folder. Other chefs would delete the .DSM file and create an empty version of a .DSM file as a placeholder. As we learned more about the Windows Mobile, we discovered that .DSM files contained pertinent information that was used during the compilation of a ROM and should be properly managed. DSMBuilder is a utility to view and modify components of a .DSM such as certificates, dependencies, shadow order, and list of modules/files.
A Device Side Manifest file (.DSM) describes the contents of a package and has the name <GUID>.DSM. Each package has its own .DSM file. The .DSM file is a binary file and the format may change at any time. The .DSM file is created by parsing a package definition file, package shadow file, and a build manifest file. Each item specified within a build manifest file is used to determine the item's file type.
The .DSM file contains the following information:
Public key certificate data used for signature validation.
Version information which includes the previous version of a package so as to create a delta package between an older or baseline package and a new package.
Package GUID
Dependency GUID information
File names and file information in the form of raw file size and original VBase for MODULES so they can be re-based and differentiated during an update.
Tips:
Always keep a copy of the unaltered file as a backup.
A .DSM file should contain a complete (exact) list of all modules/files found in the package folder.
The .RGU file should be excluded from the .DSM file.
Kitchen-specific files should be excluded from the .DSM file.
Gotcha's:
Hidden (H) and/or System (S) attributes may need to be cleared (ATTRIB -s -h -r) from .DSM files before they can be edited.
Dumping a custom ROM where a .DSM file was altered with DSMBuilder may result in the package being placed in the SYS folder.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=520009
DSM Dependency Dumper
Name: DSM Dependency Dumper
Version: 2009-06-19
Author: dj13241
Link: http://forum.xda-developers.com/showthread.php?t=527965
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
DSM Dependency Dumper is a handy tool to extract the list of dependency packages for a single Device Side Manifest file (.DSM) or an entire ROM. The DSM Dependency Dumper will produce a Comma Separated Values (.CSV) output file detailing all of the required dependencies for a package.
A Device Side Manifest file (.DSM) describes the contents of a package and has the name <GUID>.DSM. Each package has its own .DSM file. The .DSM file is a binary file and the format may change at any time. The .DSM file is created by parsing a package definition file, package shadow file, and a build manifest file. Each item specified within a build manifest file is used to determine the item's file type.
The .DSM file contains the following information:
Public key certificate data used for signature validation.
Version information which includes the previous version of a package so as to create a delta package between an older or baseline package and a new package.
Package GUID
Dependency GUID information
File names and file information in the form of raw file size and original VBase for MODULES so they can be re-based and differentiated during an update.
Tips:
Most ROM's are shipped with missing package dependencies.
Gotcha's:
None Discovered.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=520009
Registry Workshop
Name: Registry Workshop
Version: 4.2.4
Author: Torchsoft
Link: http://www.torchsoft.com/
Cost: Trialware, Purchase
Reviewed By: Laurentius26
Summary/Review:
Registry Workshop is an advanced registry editor for Windows 2000 (Service Pack 4), Windows XP (32/64-bit), Windows 2003 (32/64-bit), Windows Vista (32/64-bit), Windows 2008 (32-bit and 64-bit), and Windows 7 (32/64-bit). It is a perfect replacement for RegEdit and RegEdt32 which shipped with Windows. In addition to all the standard features, Registry Workshop adds a variety of powerful features that allow you to work faster and more efficiently with registry related tasks. With Registry Workshop, registry editing becomes more safe than ever before. All changes except changing key permissions can be safely reversed (even registry replacing and importing), using multiple levels of Undo. You don't need to worry about making mistakes when editing registry.
Registry Workshop includes many useful features: multiple undo and redo, the undo history can be saved to disk and reloaded at startup, search and replace registry keys, values and data with super fast search algorithm, compare registry between computers and/or .REG files with super fast speed, connect mobile device (Pocket PC, SmartPhone, etc.) registry via ActiveSync, cut, copy and paste registry keys and values, drag and drop to move or copy registry keys and values, edit .REG files and .POL files in the same way as editing system registry, backup and restore registry, defragment registry with preview, easy and flexible favorites management, quickly browse registry with address bar, bookmarks and visitation history, context menus to navigate to referenced key: open containing folder or open URL if the key or value contains a ProgID, ClassID, folder, file path or URL, jump to the same key in HKLM or HKCU by context menu, open multiple local registry windows, allow to open secure registry keys when running under the administrator privilege, and edit binary data in BYTE, WORD or DWORD format.
Tips:
Excellent for editing/viewing/export/import registry keys on your device from your desktop using ActiveSync.
Gotcha's:
None discovered.
Reference Links:
None.
DSM Analyzer
Name: DSM Analyzer
Version: 1.5
Author: michyprima
Link: http://forum.xda-developers.com/showthread.php?t=444186
Cost: Free
Reviewed By: Sous-Chef
Summary/Review:
In early kitchen and ROM cooking, chefs used to delete Device Side Manifest file (.DSM) files from OEM packages that resided in the .\PACKAGES and/or .\EXT folder. Other chefs would delete the .DSM file and create an empty version of a .DSM file as a placeholder. As we learned more about the Windows Mobile, we discovered that .DSM files contained pertinent information that was used during the compilation of a ROM and should be properly managed. DSM Analyzer is a utility to view and modify components of a .DSM file such as certificates and list of modules/files.
A Device Side Manifest file (.DSM) describes the contents of a package and has the name <GUID>.DSM. Each package has its own .DSM file. The .DSM file is a binary file and the format may change at any time. The .DSM file is created by parsing a package definition file, package shadow file, and a build manifest file. Each item specified within a build manifest file is used to determine the item's file type.
The .DSM file contains the following information:
Public key certificate data used for signature validation.
Version information which includes the previous version of a package so as to create a delta package between an older or baseline package and a new package.
Package GUID
Dependency GUID information
File names and file information in the form of raw file size and original VBase for MODULES so they can be re-based and differentiated during an update.
Tips:
Most ROM's are shipped with missing package dependencies.
Gotcha's:
Does not provide dependencies or shadow order information.
Changes only appear after reloading the .DSM or .DSM(s) in a folder.
Reference Links:
http://forum.xda-developers.com/showthread.php?t=520009