>>Don't know your customers, but you might consider to let the user decide on which method to use: some might prefer fast and ugly. Probably the worst part of the job is to write the explanation for the docs and the help <g>.
>>
>
>I'm a corporate developer, so our customers are kind of stuck ;-) Mgt. has been pushing to get this out, so I didn't have the luxury to keep playing with this - it was more important to ship it than make the installation fast. I had to start burning DVD's before I left Friday so that they'd be ready to go on Monday (and I had to test my source DVD first, burn a test copy and then install that one to make sure everything worked OK; that alone took about 6 hours).
>
>I went back and forth on this one. I was going to create a Demoshield install that let them choose between "slow and pretty" and "fast and ugly". However, most users still won't think 35 minutes is all that fast, so I decided to go with the solution that at least gave them some feedback and an easy way to cancel it if they needed too.
>
>The docs are pretty simple - put the disk in, go to bed, wake up the next morning and it will be done <g>.


If you prefer to have a nice animation that provided by SHFileOperation, you might want to try this. I'm not really sure but it might help a little faster.

- Use FOF_NOCONFIRMATION + FOF_NOCONFIRMMKDIR flags. Because without this flags the function always call it's callback function for every file to do some checking.
- Since the user will not doing anything while installing (I think), set the process to HIGH priority.