Exposing the steps and having them each have their own progress bar or "reset" the progress bar is always preferable to me as a user, both because I like feelin

Exposing the steps and having them each have their own progress bar or "reset" the progress bar is always preferable to me as a user, both because I like feeling like I know what my software is doing (even -- or, in some cases, especially -- if it is behind the veneer of plain speech and a nice UI), and also the more fine granularity feeds my boredom and often does "make it seem quicker." If you have something to look at and track, you don't feel like it could take forever. Letting people see the light at the end of the tunnel /always/ makes it more bearable. Giving them "sub-tunnels" helps that further, I think. Another example of this is online checkout paths. Obviously the fewer pages and fewer form fields a user has to fill out, the better, but even if its just a single page and a confirmation page, I /always/ prefer checkout paths which list the number of steps and number of pages at the top, and indicate how far along in the process I am. It's always so exasperating when online shopping when you think you're about to make a purchase, only to be taken to an unexpected "confirm everything you just did" page, followed by two order confirmation pages. Its not the same as an installer or other crunching process, but granulated progress bars get you a surprising amount of mileage in many linear processes you can put your users through.