Windows Embedded Standard 7: Diagnosing IBW installation problems with DOS commands

Are you installing Windows Embedded Standard 7 image through IBW, and partway through installation, you get a nice little popup that looks something like (see pic). IBW does its best to provide users with descriptive error messages for common problems but, there’re quite a few things that can go wrong during installation of large operating […]

Are you installing Windows Embedded Standard 7 image through IBW, and partway through installation, you get a nice little popup that looks something like (see pic). IBW does its best to provide users with descriptive error messages for common problems but, there’re quite a few things that can go wrong during installation of large operating system. Sometimes things’ll go wrong that we can’t predict and you’ll need to look at IBW’s log files to find out more about what happened. IBW log locations: While running "autorun" (before clicking "Build an Image" or "Deploy an Answer File or WIM") = No Logs | Before installation actually starts (before clicking "Next" on the disk selection screen) = X:\windows\panther | After installation starts = C:\$WINDOWS.~BT\Sources\Panther | After installation completes = C:\Windows\Panther. After you encounter an error in IBW but before clicking OK, you can hit Shift + F10 to open Command Prompt window, as after you click OK, setup will attempt to roll back the installation, potentially deleting your logs in the process. If you’re not familiar with Windows/DOS commands, see a good list of DOS commands here. Essentially you’ll use cd to navigate around and dir to list files in the currently selected directory. As you navigate to C:\$WINDOWS.~BT\Sources\Panther, you can see the log files that we’re interested in.

[Source]