Start typing “Windows 7 thumb…” into Google, and the first entry in the auto-suggestion list that appears under the search box is “Windows 7 thumbnails not showing”. A long process, and obviously PDF files added later would not have thumbnails until I viewed the folder again in Nitro.It seems I’m far from the only person being blighted by this problem. It would seem that I have to open every folder for which I want PDF thumbnails displayed in Niro first. The thumbnails remain displayable even after Nitro is shut down. Once Nitro generated thumbnails for those files, they were displayed in DO as well. The folders that were listed below the window display had not yet had thumbnails generated. I went back to Nitro and scrolled down the folder. The last ones listed in the folder did not. I was surprised to find that not all of the PDF files had thumbnails. In other folders there are no PDF thumbnails.įor another folder in Nitro, I set display to thumbnails and opened that folder in DO. What surprised me was that subsequently when I open DO, navigate to that folder, and change the view to thumbnails, all of the PDF files are displayed as proper thumbnails. Not all that hard to understand, as one of the options of PDF files is to display thumbnails of the individual pages to the side of the document. Clicking through the display options and selecting thumbnails displays the folder's contents in thumbnails. To do this, in Nitro you to go to File>Open, which brings up a window with a folder tree on the left side and the folder's contents on the right. Although the program is still 32-bit, it generates thumbnails. On my old system I have been using Nitro PDF Pro for years, and I installed the latest version on my new 64-bit system. However, I have a semi cure and am hoping you can help make it a full cure. I now have all of the PDF thumbnail issues others have been having. I've since built up a new system and installed Windows 8.1 64-bit. I don't know what happened, but now I can enjoy my weekend. To my surprise, when it reopened all of the PDF thumbnails were fully visible and functioning normally again. Then this afternoon DOpus crashed while I was working in a folder and shut down the program. As with the download attempts, the installation attempt was automatically aborted.Īs I had work to do using Adobe Reader and the Reader program was working fine, I decided to continue working and wait 'til the weekend to uninstall and reinstall Adobe Reader. This worked up to a point, when a new message appeared saying the version I was trying to install was already installed. So I tried installing directly from Adobe, rather than downloading. Both browsers responded with an error message and aborted the download, although cookies were not blocked on either system. I tried downloading a new copy from Adobe's site using both Firefox and IE. The most recent version of Adobe Reader from Adobe is the same version that is presently installed on this system. One of the few good things about ancient 32-bit systems. Reinstalling Adobe Reader is usually enough to fix things on 32-bit machines. Other than things like that, 64-bit versions of apps are not necessarily better (or worse) than 32-bit versions it will vary from app to app (and also on different hardware or different workloads given to the same apps). Explorer and shell extensions such as context menu items added by other programs) and/or see the "real" view of the filesystem and registry (instead of the fake view that 32-bit processes see) without having to bend over backwards (which can confuse the app and/or its plugins if you're not very careful). It makes sense to use 64-bit versions of apps if you want them to be able to access more than 2-3GB or if you need them to interact with other 64-bit components (like, as is the case with Opus, the Windows shell, i.e. The speed issue is neither here not there, really. OTOH, 64-bit code can use more registers, so it can also run faster than the same 32-bit code. For example, 64-bit code must use larger pointers (8 bytes instead of 4) and if that extra space usage means the difference between a cache hit and a cache miss (multiplied by millions of times) it can slow things down. It can be, but sometimes it's slower, too. 64-bit code isn't always faster than 32-bit code, even if it is well-written (and well optimized by the compiler, etc.).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |