yashsingh1/xdaforums huggingface dataset:
[Windows Mobile] hilaireg:
DSMBuilder

Name: DSMBuilder

Version: 2008-08-08

Author: anmendes

Link: http://xdaforums.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://xdaforums.com/showthread.php?t=520009
[Windows Mobile] hilaireg:
DSM Dependency Dumper

Name: DSM Dependency Dumper

Version: 2009-06-19

Author: dj13241

Link: http://xdaforums.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://xdaforums.com/showthread.php?t=520009
[Windows Mobile] Laurentius26:
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.
[Windows Mobile] hilaireg:
DSM Analyzer

Name: DSM Analyzer

Version: 1.5

Author: michyprima

Link: http://xdaforums.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://xdaforums.com/showthread.php?t=520009
[Windows Mobile] hilaireg:
BuildDSM

Name: BuildDSM

Version: 1.5

Author: nandlal_mk

Link: http://xdaforums.com/showthread.php?t=312985

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. BuildDSM is a utility to create an initial .DSM file or update an existing .DSM file..

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:

Renaming an empty .TXT file to .DSM will allow the tool to update the file with the known .DSM file information.

Drag-and-drop a package folder that contains a .DSM file onto BUILDSM.EXE.

Gotcha's:

The .DSM created may not contain all of the information required as the tool is outdated.

Requires an existing .DSM file in the directory - empty or other.

Requires Microsoft Visual C++ 2005 SP1 Redistributable Package (x86).

Reference Links:

http://xdaforums.com/showthread.php?t=520009
[Windows Mobile] Laurentius26:
Compare It

Name: Compare It

Version: 4.1

Author: Grig Software

Link: http://www.grigsoft.com

Cost: Trialware, Purchase

Reviewed By: Laurentius26

Summary/Review:

Compare It! is a full-featured visual file comparison and merging tool that allows you to compare and work with different versions of the same text file. A color-coded side-by-side comparison makes it easy to understand the differences between two files at a glance. Compare It! features include: an overview bar that helps you see an overall picture of changes, differences shown within lines, full-featured editor has wordwrap, syntax highlighting, undo, search & replace, and bookmark functionality, windows/DOS, UNIX, and Mac text files are supported, Unicode support of national fonts, customize colors, fonts, file and line compare options, and even filters for the Open File dialog box.

Additionally, Compare It! integrates with file manager, navigation and merging are difference-based, you can use your mouse or keyboard for actions, multiple users are supported, print comparison results and generate HTML and text reports with various options converters support helps you to compare non-text files, and Zip archives support lets you compare a file with its archived copy.

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.

Gotcha's:

None discovered.

Reference Links:

None.
[Windows Mobile] ai6908:
ROM Squeezer

Name: ROM Squeezer

Version: 2007-05-27

Author: edhaas

Link: http://xdaforums.com/showthread.php?p=1283338#post1283338

Cost: Freeware

Reviewed By: ai6908

Summary/Review:

ROM Squeezer was originally included with the edhaas Wizard Rom-Packer kitchen. The technology is applicable to most programs installed in the Wizard and most other devices - either storage memory or SD card. This program uses the open source program UPX to compress .EXE files. The compression is quite remarkable and typically, the files end up less than half their original size.

The loading speed of the programs is actually improved considering storage memory is so much slower than RAM memory; the increase in performance transferring smaller amounts of data from the storage memory to RAM when you run the program is more than enough to make up for the time spent uncompressing in RAM. Additionally, larger applications such as Office seem to load significantly faster. Although .DLL files haven't been extensively tested, most .DLL seem to work fine. A few programs will not work well in this mode, or refuse to load, so keep the original copies as backups. You will also find that a few programs such as Adobe Reader and PocketXpdf are already compressed with this technology!

Tips:

Copy your .EXE's that you want to compress to the squeezer folder and run BAT file.

Gotcha's:

.NET (NetCF) cannot be compressed.

Reference Links:

http://upx.sourceforge.net
[Windows Mobile] hilaireg:
Cab2OEM

Name: Cab2OEM

Version: 0.9

Author: evalu8t0r

Link: http://xdaforums.com/showthread.php?t=422942

Cost: Freeware

Reviewed By: Sous-Chef

Summary/Review:

Cab2OEM is handy tool to convert .CAB installer files to OEM package format. The tool produces an OEM package file that is compatible with Ervius PkgToolBuildOS (legacy) kitchen. Cab2OEM includes parameters to extract the contents of one or multiple .CAB files to a specific folder as well as parameters to pre-configure the settings in the OPTION.XML file.

For example, enter the following syntax at a Command (CMD) Prompt to extract the contents of a .CAB file:

cab2oem -f <application>.cab -d "c:\xda\targetfolder"

To convert the folder to Ervius Visual Kitchen format, perform the following steps:

Create a sub-folder entitled: Files (ex: c:\xda\targetfolder\Files).

Delete OPTION.XML.

Move all the files to this folder; do not move: *.DSM, *.RGU, INITFLASHFILES.TXT.

Rename INITFLASHFILES.TXT to APP.DAT.

Make a copy of the .RGU file.

Rename the copy of the .RGU file to APP.REG.

Tips:

Use quotes around the folder path.

Omitting the folder parameter will instruct Cab2OEM to create a folder that is the same name as the .CAB file.

Gotcha's:

.CAB file must contain a _setup.xml file.

Reference Links:

None.
[Windows Mobile] ai6908:
File Suite Editor

Name: File Suite Editor

Version: 2008-10-01

Author: schreda

Link: http://xdaforums.com/showthread.php?t=432041

Cost: Freeware

Reviewed By: ai6908

Summary/Review:

File Editor Suite is compilation of tools required to sign/unsign .EXE, .DLL, .MUI, and other such files. The File Editor Suite includes an unsigner, signer, reshacker, and certificates. The process of editing and signing a file with a different (newer) certificate is simple:

Unsign the file to edit using the unsigner tool.

Edit the file with the reshacker tool.

Sign the file with the signer tool using one of the certificates included.

Tips:

Useful for modifying taskbar icons resource (.DLL) files.

Any resource editor tool similar to reshacker can be used.

Only required for ROM's where certificate checking is enabled.

Gotcha's:

Certificates included in the package are expired; newer versions are obtainable from the reference links below.

Reference Links:

http://windowsteamblog.com/cfs-file...gs.Components.WeblogFiles/wmdev/WM65Certs.zip

http://htcpedia.com/news/new-certificates-out-for-windows-mobile-developers.html
[Windows Mobile] + Que PPC:
CAB to OEM to EXT GUI Suite

Name: CAB to OEM to EXT GUI Suite

Version: 0.0.1

Author: |Jason8|

Link: http://xdaforums.com/showthread.php?t=525302

Cost: Freeware

Reviewed By: + Que PPC

Summary/Review:

CAB to OEM to EXT GUI Suite is GUI made that utilizes existing command line tools to allow a user to freely convert .CAB's to OEM and EXT files. Drag .CAB's into the listbox and they will be automatically added. Select the .CAB's to convert by clicking on them. There is a library file that is needed in order to run it called COMDLG32.OCX; this is installed when the self-extracting archive is finished.

The process of is simple:

Run the Cab Converter executable

Add the .CAB's

Click the OEM or EXT button

Tips:

Useful for batch conversion of .CAB's.

Gotcha's:

There are no checks to see if the conversions have been successful, so that will still need to be done manually by the user.

Can only be installed to Local disk; do not try installing anywhere except the default location.

Can only perform .CAB > OEM and .CAB > EXT.

Converting multiple .CAB's may take a while; wait before clicking OK in the message box if you have 100+ .CAB files.

There are still some cab files that will not convert because they do not have a _setup.xml file (CAB2OEM issue).

Reference Links:

http://xdaforums.com/showthread.php?t=422942

http://xdaforums.com/showthread.php?p=3147148
[Windows Mobile] + Que PPC:
SYS Porting Tool For Ervius Kitchen

Name: SYS Porting Tool For Ervius Kitchen

Version: 2009-10-24

Author: SHAYDER

Link: http://xdaforums.com/showthread.php?t=575897

Cost: Freeware

Reviewed By: + Que PPC

Summary/Review:

The SYS Porting Tool for Ervius Kitchen is handy utility to extract specific device resolutions, DPI, and languages from a master SYS package and copy them to the Ervius Visual Kitchen. For example, to extract a 240x320, 96 DPI, RESH 240, 0409:

Create a porting folder (ex: C:\PortBuild)

Copy the PACKER.JAR to the porting folder (ex: C:\PortBuild)

Extract the SYS folder from the master SYS package using an archive tool (ex: WinRAR)

Copy the extracted SYS folder to the porting folder (ex: C:\PortBuild\SYS)

Launch PACKER.JAR

Enter 0409 in the LANG box

Enter 96 in the DPI box

Enter 240 in RESH box

Enter 320 in the RESV box

Copy the final results to the Ervius Kitchen

Tips:

The PACKER.JAR can be launched via command line (ex: java -jar 0409 96 240 320)

Gotcha's:

Requires JAVA Runtime Edition.

Reference Links:

http://xdaforums.com/showthread.php?p=3147148
[Windows Mobile] chrisjaffe:
GNU Image Manipulation Program (GIMP)

Name: GNU Image Manipulation Program (GIMP)

Version: 2.6

Author: The GIMP Team

Link: http://www.gimp.org

Cost: Free

Reviewed By: chrisjaffe

Summary/Review:

GIMP is an acronym for GNU Image Manipulation Program. It is a freely distributed program for such tasks as photo retouching, image composition and image authoring. It has many capabilities. It can be used as a simple paint program, an expert quality photo retouching program, an online batch processing system, a mass production image renderer, an image format converter, etc. You can create and edit almost any image file including: jpg, png, gif, animated gif's, ico, psd, raw, tif, xcf and more.

GIMP is expandable and extensible. It is designed to be augmented with plug-ins and extensions to do just about anything. The advanced scripting interface allows everything from the simplest task to the most complex image manipulation procedures to be easily scripted.

Tips:

Make sure to use the latest version. Some older versions are harder to use because of the modular style of the program.

Gotcha's:

The tool palettes are separate windows. The developers have moved to make a more unified experience but there is still room to improve.

Reference Links:

None.
[Windows Mobile] aruppenthal:
Just a note on beyond compare. I was recently contacted by the developers of this fantastic program wanting to reproduce and fix the issue with intflashfiles.dat.

With the newest build and windows 7 I cannot reproduce the issue. Previously i was using a older build and xp. If anyone can reproduce any issues comparing initflashfiles.dat let me know or pass it on to their support department ;)
[Windows Mobile] miniterror:
Package Creator

Name: Package Creator

Version: 2.7

Author: Ervius

Link: http://xdaforums.com/showthread.php?t=388883

Cost: Freeware

Reviewed By: miniterror

Summary/Review:

Package Creator is handy tool to convert .CAB installer files to OEM package format. The tool produces an OEM package file that is compatible with Ervius PkgToolBuildOS (legacy) kitchen. Package Creator includes parameters to extract the contents of a .CAB file to a folder and pre-configures the settings in the OPTION.XML file. Additionally, Package Creator can convert *.EXE, *.DLL, and *.MUI to module format.

For example, click the Open CAB File button to select a .CAB file - Package Creator extracts the contents of the .CAB file automatically. To remodule the *.EXE, *.DLL, and *.MUI files, perform the following steps:

Click the Open Package button.

Select the desired kitchen package.

Select the Remodule All EXE-DLL-MUI Files Into Created Package checkbox.

Click the Initfiles.txt tab.

Click Button3.

To convert the folder to Ervius Visual Kitchen format, perform the following steps:

Create a sub-folder entitled: Files (ex: c:\xda\targetfolder\Files).

Delete OPTION.XML.

Move all the files to this folder; do not move: *.DSM, *.RGU, INITFLASHFILES.TXT.

Rename INITFLASHFILES.TXT to APP.DAT.

Make a copy of the .RGU file.

Rename the copy of the .RGU file to APP.REG.

Tips:

Microsoft .NET required.

Gotcha's:

Designed for Ervius PkgToolBuildOS (legacy) kitchen.

Reference Links:

None.
[Windows Mobile] tidus18:
Initflashfiles_Hex2Text

Name: Initflashfiles_Hex2Text

Version: 2010-05-19

Author: tidus18

Link: http://xdaforums.com/showpost.php?p=6520523&postcount=4

Cost: Freeware

Reviewed By: tidus18, + Que PPC

Summary/Review:

Initflashfiles - Hex2Text is a simple tool written using Visual Basic for Application (VBA) in Microsoft Excel. Initflashfiles - Hex2Text can be used to translate the hex paths found in the initflashfiles.dat to normal paths. A hex path typically appears in this format: File("\x0053\x0070\x0072\x0069\x006E\x0067\x002E\x006A\x0070\x0067","\Windows\Spring.jpg").

For example, to translate the hex paths found in the initflashfiles.dat, follow these steps:

Open initflashfiles.dat in a text editor such as notepad.exe.

Highlight all of the content that appears in the text editor and select Copy - do not close the text editor window, you'll need it again at the end of the procedure.

Launch Microsoft Excel.

Click in column A of row 1 on the sheet named initflashfiles.dat and then select Paste from the Edit menu - each line should now occupy one row.

Select the sheet named RunVBA and click the Translate button.

Highlight all of the translated content and then select Copy.

Switch over to the open text editor window and delete the current hex path content -the initflashfiles.dat file should now br empty.

Select Paste to copy the translated contents into the empty initflashfiles.dat.

Save the file; you're done.

Tips:

Macros must be enabled for VBA to run.

Temporarily set the Macro Security level in Microsoft Excel to Low (Tools -> Macro -> Security -> Low).

Gotcha's:

Requires Microsoft Excel.

If so some reason Translate button is not working, activate sheet named initflashfiles.dat and manually execute subroutine named Hex2Text under Module1 from within the VBA Editor (Press Alt + F11).

Reference Links:

http://xdaforums.com/showthread.php?t=684032
[Windows Mobile] IzaacJ:
[ADD] syn Text Editor

Name: syn Text Editor

Version: 2.1.0.46

Author: neum, paulggardner

Link: http://www.sourceforge.net/projects/syn/

Cost: Free

Revied By: IzaacJ, PentaMedia

Summary/Review:

A perfect text editor. Uses it for all my text-file editing. Been using it for the last few years. Supports a lot of syntax markup schemes.

Tips:

None.

Gotcha's:

None.

References:

None.
[Windows Mobile] lostbullettt:
nice
[Windows Mobile] ynh1427:
ok

ok