Inline Browser Viewing and Windows 7 64 bit

[CDS4LD]

Up until recently the inline PDF viewer plug in was working correctly in all three browsers (IE8, Firefox 3.5 and Google Chrome Dev Channel) on our two Windows 7 64 bit machines. Since about January 15th (Not sure if it was a PDF Viewer update or a Chrome update) it has stopped rendering inline in Firefox and Chrome (It comes up as a black page) but continues to work fine in IE8. BTW, we also have two Windows 7 32 bit machines and PDF Viewer renders inline fine in all three browsers. I updated Firefox to version 3.6 but received the same black page. I've uninstalled Firefox, Chrome and PDF Viewer and reinstalled latest standard versions of all to no avail. Entering about:config - plugins in Firefox and about:plugins in Chrome, the PDF Viewer plugin is listed in both as being the viewer of choice. Any ideas on what can be done to restore proper functionality?
Thanks in advance for your reply.
CDS4LD

[Corwin - Tracker Sup]

Please try to recheck "Display PDF in browser" option in Viewer:
1. Close your browser.
2. Run PDF-XChange Viewer;
3. Go to Edit->Preferences->File Associations;
4. Uncheck (if checked) 'Display in Browser' and press 'Make Default..' button. Check 'Display in Browser' again and press 'Make Default..' button;
5. Close PDF-XChange Viewer;
6. Check your browser.

HTH.

[CDS4LD]

No luck...Same thing happens.
CDS4LD

[CDS4LD]

Okay, so I did a little follow up as during my original "No Go" post I did not have Firefox installed. After I installed Firefox it initially did not work in either browser so I closed them both and followed the steps you suggested and voila, it worked correctly in both. When I uninstalled Firefox it stopped working in Chrome. Not sure what this means other than to have inline PDF viewing in Chrome on a Windows 7 64 bit system I have to have Firefox installed. For now it is an acceptable work around but sure would like to figure out why it won't work in Chrome without Firefox installed.
Thanks for the help a let me know if there is additional experimentation I can do to to help find a permanent solution from the PDF Viewer standpoint or isolate what the Google Chrome boys need to do to fix it from their end.
Regards,
CDS4LD