To address reported bugs we will be updating and posting new builds of v1.2 until we feel enough of the known bugs have been addressed to move forward with making it an official release. Please provide any and all feedback right here.

Beta 1

Enhanced the error logging capability
The registry related errors logged in the file C:\ErrorLog.txt were not proper i.e. the message did not correctly indicate the error in accessing the key this bug is fixed. Also error logging for MSI database creation is also now properly formatted. It will now dump the Table name and the actual query that has failed.

Fix: Folder specified in the Defaultincludeexclude.xml are not excluded (in the Package Content Review - File Selection page)
The File Enumeration logic had a bug i.e. the even if certain folder was specified in the excluded section of DefaultIncludeExcludeList.xml file, the folder was appearing in the included list after taking the folder differences. This problem is highlighted for setups writing to the folder C:\windows\winsxs. In Windows Vista even administrators do not have rights to write in this folder.

Fix: Next page would sometimes automatically appear while taking first or second snap
While taking first and second snapshot sometimes it is observed that the next page automatically appears while still taking the snapshot.
This is reproduced always in the Debug Build and rarely reproduced in the release build.

Fix: Spaces removed from product name, manufacturer name and version
Spaces needed to be removed from the end of these entries, not from the entire values. This has been corrected.

Fix: Replacement of invalid characters in component names
Only valid chars are used in File and Component names now. Invalid chars are replaced by underscores. Previously, if a filename contained spaces, dashes or other punctuation the result was an invalid component name.


0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Thanks Bob. That last fix is important as otherwise programs that had files with punctuation (such as a space) would fail. Now they work!
Answered 06/16/2009 by: gperks
Senior Yellow Belt

Please log in to comment
Superseded by Beta 2: http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning6766
Answered 09/22/2009 by: bkelly
Red Belt

Please log in to comment