Could you create a batch (.bat) file with a series of simple, straightforward commands that clearly show exactly what file replacements, registry key additions, and deletions onecoreapi performs? This would allow users who prefer not to use update.exe—or those integrating onecoreapi into environments like nLite or Windows XP Embedded—to directly incorporate it more efficiently, avoiding the large disk space usage and long wait times associated with the standard update process.
Could you create a batch (.bat) file with a series of simple, straightforward commands that clearly show exactly what file replacements, registry key additions, and deletions onecoreapi performs? This would allow users who prefer not to use update.exe—or those integrating onecoreapi into environments like nLite or Windows XP Embedded—to directly incorporate it more efficiently, avoiding the large disk space usage and long wait times associated with the standard update process.