[Windows Mobile Software Development] 12aon:
Frequently Asked Questions (FAQ)

What types of files can be placed in the '.\_SOURCE' folder?

Any type of file may be placed in the .\_SOURCE folder. The MANILATOOL command script will only copy files that contain the word "manila" in them to the .\_queue folder.

I accidentally specified the wrong version of Manila files during the kitchen initialization; is there a way to change it without initializing the kitchen again?

The default Manila file version is stored in the kitchen-ver file. Use a standard text editor such as Notepad2 to edit file. The file must contain a three characters equivalent to the version - valid versions are: 2.5, 2.2, 2.1, 2.0, 1.3, 1.2, 1.1, 1.0, and 0.0 (Unknown/Custom)

What is the '._BACKUP' folder used for?

Before most operations occur, a backup of files that will be changed or removed from/in a given folder is performed. This ensures that previous functional files remain available in the event that a "rollback" is required.

What is the difference between the "Incomplete", "Error", and "Completed" (successful) LUA folders?

Manila files that are successfully decompiled are will appear in the "completed" folder - 100% comparison result. Manila files that are decompiled but do not pass the comparison validation (less than 100%) are placed in the "incomplete" folder. Manila files that report a 0% decompilation result are placed in the "error" folder.

What is the difference between the files in the '.\Release\_lua', '.\Release\_error', '.\Release\CAB', and '.\Release\DEVICE' folders?

The .\Release_error folder will only appear when unexpected errors were encountered during Manila LUA file recompilation. The folder will contain logs detailing the problem that was encountered with a Manila LUA file. The folder is removed and recreated at each recompilation.

The .\Release\_lua folder contains the recompiled versions of the Manila LUA files that are found in the .\Workspace\_lua folder. These are the files can be distributed directly to a device or via CAB file.

The .\Release\CAB folder contains the recompiled versions of the files found in the .\Release\_lua folder. These are the files can be installed via ActiveSync or a Storage Card.

The .\Release\DEVICE folder contains the recompiled versions of the files found in the .\Release\_lua folder. These are the files can be installed via ActiveSync or a Storage Card.

What is the difference between the files in the '.\Processed', '.\Workspace', and '.\Repository' folders?

The .\Processed folder contains the HTC OEM Manila files that were copied to the .\_queue during the Manila Kitchen initialization process. During the decompilation process, the files are moved from the .\_queue folder to the appropriate folder - which is determined by the LUA Comparison tool results.

The .\Workspace\_lua folder contains decompiled versions of the HTC OEM Manila files - these are the files that are typically modified and recompiled. The remainder of the folders in the .\Workspace folder contain various non-LUA files.

The .\Repository\_lua folder contains a duplicate copy of the decompiled Manila files. The repository serves a form of backup.

What are the extra .TXT files that appear in the partially decompiled LUA script folders?

The *.error.txt file contains the STDOUT error that was generated by the LUA Decompiler. When this file appears, there is a logical error in there script, which makes it impossible to run the script. The file will usually contain the approximate (line number) location where the problem was encountered.

The *.log.txt file contains the compared disassembly output from the orignal Manila file and the decompiled LUA version - which appears in the folder. When this file appears, it is an indication that the script will function but it does not match the original Manila file.

The *.dis.txt file contains the raw (full) disassembly of the original Manila file and may be used to resolve the decompilation issue.

The *.status.txt file contains the decompilation result - 0% to 100%.

Visit the following website to obtain more information in troubleshooting a failed decompilation:

http://winmo.sztupy.hu

Is the disassembly output always correct?

Yes. Even though the some of the events may be not be displayed in the disassembly output, the correct sequence of events will be provided.

The M9Editor tool provides a built-in decompiler, why not just use that?

The internal LUA Decompiler (luadec.exe) provided with the M9Editor tool is an earlier version. This internal version does not provide the extra files required to resolved decompilation errors.

The M9Editor should be used when editing Mode9 files and attach extracted embedded LUA script back to their original Mode9 files.

There are strange errors such as '.\documents and settings\<profilename>\eee' errors, what is the solution? (Only in older versions)

One of the Manila Kitchen tools is in an unknown state or temporary files are locked and cannot be freed. Note the path location of the .\eee folder, restart the workstation, and manually delete the folder, sub-folders, and files.

An error message is displayed when attempting to delete a file or folder, what is the solution?

A running process is preventing the file or folder from being removed. Restart the workstation and manually delete the file or folder.

Can Error Reporting be disabled so as to not have to click the Close button every time the LUA Decompiler and/or LUA Comparison tool generate an application error?(Only in older versions)

As previously noted, some Manila files cause the LUA Decompiler (luadec.exe) and/or LUA Comparison (compare.exe) tool to generate an application error. Visit the following website(s) for more information on how to suppress the Error Reporting message box.

Windows XP

http://www.windowsnetworking.com/articles_tutorials/Disable-Error-Reporting-Windows-XP-Server-2003.html

Windows Vista/Seven

http://thehiddenguide.com/how-to-disable-error-reporting-in-windows-vista