Hi,

I am using Windows 2003 Server in my development machine. It doesn't have Windows Journal Viewer, but still, Adobe Acrobat 7 works absolutely fine, and I'm pretty happy with it. Acrobat 6 was sluggish and it was not able to do lots of things, including, for example, opening a PDF file stored on CD. Double clicking the file just showed Acrobat's splash screen, then nothing happened. I had to kill it each time :(

Anyway, about the subject: Maybe Acrobat 7 shares files with Windows Journal Viewer, but it definately does not depend on it.

>Interesting. The Win 2K systems I've bought recently all came with Windows Journal Viewer in the Start menu but not actually installed. I've never bothered to install it either. However, despite the fact that Windows Journal Viewer is not actually installed on these machines, several users at my workplace, when attempting to view .pdf documents over the Web, have encountered problems related to Windows Journal Viewer. There's even a specific note about it at the Adobe site. This note indicates that there is indeed a dependency between Acrobat Reader versions 6 and 7 and Windows Journal Viewer. The note claims that the problem is due to "corrupt registry entries" for WJV. (I won't even go into the absurdities that ensue if you actually try to "repair" WJV or download and install the latest version from the MS website. Suffice it to say that it doesn't work.) Why WJV registry entries should be corrupt--or even exist--when
>the product hasn't been installed, I can't imagine. Even if my vendor somehow messed up the Windows install and, thereby, the WJV settings (which I doubt), I still shouldn't be seeing this problem. Why Adobe--after releasing 5 successful and reliable versions--should have suddenly decided to introduce this dependency on WJV components in a viewer for a document standard that is supposed to be platform-independent, is the real heart of the matter.