IE8 crashes printing to Acrobat 9 from Yahoo message

Question

Anyone who belongs to a Yahoo list area is probably familiar with the print command to print a message either to a printer or to Acrobat (this is not the print command at the top of IE to print the whole page). With IE7, I had no problems printing to PDF. With IE8, printing to Acrobat crashes IE at the point where the window comes up showing the folder structure on the local drive and a generic filename for the PDF. The cursor blinks at the highlighted filename but IE is frozen. I can't overwrite the filename, change folders or cancel the print. I have to use Task Manager to kill the app. Oddly enough, an error message comes up and says I can't kill the process because the system is waiting for a User command - a command I can't execute because IE is frozen. I assumed this is an IE problem but there were no answers in an MS forum except to upgrade Acrobat. I upgraded to Acrobat Pro 9.1.1. Same problem.
The reason I put the question here is that I can print the mesage to a local printer, just not to Acrobat, so it looks like a compatibility problem.
Any hints except restoring back to IE7? If this were a valid option, I would restore my Vista Business 32 system back to XP. For what it's worth,  I installed IE8 because of security problems with Vista and IE7 per MS.

Answer 1

I have found this to be a problem with any web page that has a print command. The solution I have found is to open task manager, go to the process tab, kill the "acrotray.exe" process. This removes the locked "File|Save" dialog box. Then with the printer friendly formated window open I choose the print command from IE (or use the CTRL-P short-cut if there is no menus) and the "File|Save" dialog opens again this time not locked and I can save the PDF to a file.
This solution will not work if the embedded print command does not first display the printer friendly output in a window, but only presents the dialog boxes. In that case there is no work around.
I have looked all over the Adobe and Microsoft sites and although I can replicate this issues 100% of the time, there appears to be no discussion or solution other than your post of the problem.
I have opened a support case with Adobe, but I am not holding my breath.
Good Luck.