GIF/PDF  preview

hi
my "preview" don't show gif animated!!! it show that frame by frame!!!
i want to add a gif animation to a pdf file!! but the preview don't show it!!!...
but i have another question too!!!
how can i add a gif animation to a pdf file????
Message was edited by: disc burning device not found

hi
my "preview" don't show gif animated!!! it show that frame by frame!!!
i want to add a gif animation to a pdf file!! but the preview don't show it!!!...
but i have another question too!!!
how can i add a gif animation to a pdf file????
can i add a gif animation in indesign and export to pdf????

Similar Messages

  • LaTeX composition in (g)vim with live update-as-you-type PDF preview

    Ever since I tried the gummi LaTeX editor, I've been intrigued by the idea of having a live-updating PDF preview--i.e., a PDF output panel which updated as I typed. This provides all the good things of WYSIWYG, but without taking away the control I have by editing the source directly. However, apart from its preview panel, I was thoroughly unimpressed with gummi as an editor. It had none of the advanced features I was used to.
    Since then, I've been trying various techniques to make it work with my preferred editor, (g)vim. At first, I used latexmk with the -pvc option which recompiles whenever the file changes, along with a PDF editor that refreshes whenever the file changes (like evince); but found it slow and tended to get stuck.
    My current method is to use mupdf as my viewer, with a custom LaTeX script which calls xdotool to update mupdf whenever I have a successful compilation. This seems to be working fairly well.
    Here's an animated GIF screen capture showing it in action
    There is typically still a 1-second delay between typing something and it showing on the PDF preview, but it's not really any worse than it seems to be wih gummi, and I get to use a world-class editor.
    I should note that I'm not using the vim-latex suite plugin or anything similar, so I don't know whether or not any of this is compatible.
    Anyway, I thought I'd post my method here just in case anyone thought it useful, or more importantly, anyone had any feedback for how it might be improved. I'm not a programmer (--my degrees are in philosophy!--) and don't really have that much experience with vim or bash scripting, so forgive my naive methods.
    Anyway, in my ~/.vim/ftplugin/tex.vim I have:
    " Function to save, check if already compiling and compile if not
    function! KKLtxAction()
    " go to right directory
    lcd %:p:h
    " save the file if need be and it's possible
    if filewritable(bufname("%"))
    silent update
    endif
    " see how many kkltx processes there are
    " note that there are always 3 when the checking itself happens
    " so we need there to be no more than that
    let numrunning = system("ps ax | grep kkltx | wc -l")
    if numrunning < 4
    exec "silent !kkltx " . expand("%") . " &"
    endif
    endfunction
    " Call this function whenever mupdf the cursor moves
    " But only in gvim
    if has("gui_running")
    au CursorMoved *.tex call KKLtxAction()
    au CursorMovedI *.tex call KKLtxAction()
    endif
    So whenever the cursor moves, the file saves and checks if the compilation script is running. If it is not, it runs it. Here's the script, named kkltx. (To make it work, create a ~/.config/kkltx folder. Sorry about the stupid name; I needed it to be uncommon.)
    #!/bin/bash
    file="$1"
    logfile="${file%.tex}.log"
    auxfile="${file%.tex}.aux"
    # check to see when file was last saved and
    # check see what version of file was last compiled
    currmodified=$(stat -c %Y "$file")
    oldmodified=$(cat $HOME/.config/kkltx/lastprocessedfile)
    # if they're the same exit with no change
    if [ "$currmodified" == "$oldmodified" ] ; then
    echo "nochange"
    exit 0
    else
    # if compilation is necessary, check what program to use
    # 'xelatex' should appear in first 5 lines for xelatex docs
    if head -n 5 "$file" | grep -i -q 'xelatex' > /dev/null 2>&1 ; then
    execprog="xelatex"
    else
    execprog="pdflatex"
    fi
    # try to compile
    if ${execprog} -interaction=batchmode -file-line-error -synctex=1 "$file" > /dev/null 2>&1 ; then
    # if compiling worked check if bibtex needs to run
    if cat "$logfile" | grep -i -q 'undefined citations' > /dev/null 2>&1 ; then
    if bibtex "$auxfile" > /dev/null 2>&1 ; then
    if ! ${execprog} -interaction=batchmode -file-line-error -synctex=1 "$file" > /dev/null 2>&1 ; then
    echo "failure"
    exit 1
    fi
    else
    echo "bibfail"
    exit 2
    fi
    fi
    # check if a rerun is necessary to update cross-references
    if cat "$logfile" | grep -i -q 'rerun to get' > /dev/null 2>&1 ; then
    if ! ${execprog} -interaction=batchmode -file-line-error -synctex=1 "$file" > /dev/null 2>&1 ; then
    echo "failure"
    exit 1
    fi
    fi
    # update mupdf by sending the r key to it
    xdotool search --class mupdf key --window %@ r > /dev/null 2>&1
    echo "success"
    # save time of compilation
    echo -n "$currmodified" > "$HOME/.config/kkltx/lastprocessedfile" 2>/dev/null
    else
    echo "failure"
    exit 1
    fi
    fi
    exit 0
    One thing you miss out on with mupdf is the SyncTeX ability in, e.g., TeXworks that allows you jump from the source to the corresponding part of the PDF and vice-versa. Here's a kludge that at least gets to you to the right page by using xdotool to send the signal to move to a certain page matching the source, or to read what page mupdf is on, and move to the beginning of the source code for that page (or strictly, a couple inches over and down). Again, in my ~/.vim/ftplugin/tex.vim
    " \v to open the viewer
    nnoremap \v :exec "silent! !mupdf ".expand("%:r").".pdf &"
    " forward search with mupdf
    function! MuPDFForward()
    " make sure I'm in the right directory
    lcd %:p:h
    let pageforward = 0
    " find where I am now; adjust for starting with 0
    let searchline = line(".") + 1
    let searchcol = col(".") + 1
    " use synctex to find the page to jump to
    let pageforward = system("synctex view -i " . searchline . ":" . searchcol . ":\"" . expand("%") . "\" -o \"" . expand("%:r") . ".pdf\" | grep -m1 'Page:' | sed 's/Page://'")
    " if a page other than 0 is found, send the page number to mupdf
    if pageforward > 0
    call system("xdotool search --class mupdf type --window %1 \"" . pageforward . "g\"")
    endif
    endfunction
    " inverse search with mypdf
    function! MuPDFReverse()
    lcd %:p:h
    let gotoline = 0
    " call a script which returns the line number near start of page shown on mupdf
    let gotoline = system("syncreverse-mupdf.sh " . expand("%:p:r"))
    if gotoline > 0
    exec ":" . gotopage
    endif
    endfunction
    " mappings \f and \r for forward and reverse search
    nnoremap <buffer> \f :call MuPDFForward()<CR>
    nnoremap <buffer> \r :call MuPDFReverse()<CR>
    Here is the script syncreverse-mupdf.sh called by the above:
    #!/bin/bash
    # syncreverse.sh full-path-of-PDF-minus-extension
    pathfn="$1"
    # reduce filename to base, add .pdf
    pdffile="$(echo "$pathfn" | sed 's@.*/@@g').pdf"
    # change to directory containing files
    cd "$(echo "$pathfn" | sed 's@\(.*\)/[^/]*@\1@g')"
    # read page number in mupdf window title
    page=$(xdotool search --class mupdf getwindowname | sed 's:.* - \([0-9]*\)/.*:\1:')
    # synctex lookup; remove junk
    line=$(synctex edit -o "$page:288:108:$pdffile" | grep -m1 'Line:' | sed 's/Line://' | head -n1)
    line=$(echo "$line" | sed -n 's/\([0-9]*\).*/\1/p')
    # return line for gvim
    echo "$line"
    exit 0
    I also recommend putting mappings in vim to send keys to mupdf to move around, so you can move around in the preview but without making (g)vim lose focus. These are just examples.
    nnoremap <silent> <buffer> <C-PageDown> :silent! call system("xdotool search --class mupdf key --window %@ Page_Down")<CR>
    nnoremap <silent> <buffer> <C-PageUp> :silent! call system("xdotool search --class mupdf key --window %@ Page_Up")<CR>
    Anyway, these could definitely be improved, by, for example, accommodating master/sub-documents, and so on. Thoughts?
    Last edited by frabjous (2010-11-04 22:41:21)

    OK, I've uploaded a PKGBUILD to AUR. Since I've changed how it handles recognizing when it's safe to recompile, it no longer needs to have a weird name. The name is now:
    vim-live-latex-preview
    It comes with a very short vim help file, which I'll copy here.
    *live-latex-preview.txt* For Vim version 7.3. Last change: 2010 Oct 27
    *live-latex-preview*
    A plugin for creating a live-updating PDF
    preview for a LaTeX file in MuPDF
    Default key bindings:~
    \p = Begin auto-compilation and launch MuPDF preview.
    \o = End auto-compilation and close MuPDF preview.
    \s = Check the result of the last compilation;
    jump to first error in case of errors.
    \f = Forward search to page in PDF matching cursor
    position in source.
    \r = Reverse/inverse search to position in source
    matching active page in MuPDF. (Very approximate.)
    \<PageUp>, \<PageDown>, \<Up>, \<Down>, \<Right>, \<Left>, \G
    \m, \t, \-, \+, \= = Send the corresponding keystrokes
    to the MuPDF preview without losing focus on vim Window
    The '\' can be changed by changing <LocalLeader>.
    Be aware that your file is saved whenever the cursor moves. Be sure
    to take the appropriate measures to keep back-up saves and undo files
    so you can undo changes if need be.
    To compile with XeLaTeX rather than PDFLaTeX, include the string
    'xelatex' somewhere in the first five lines of your file (e.g., in a
    comment). Currently only PDFLaTeX and XeLaTeX are supported. (Support
    for LuaLaTeX and/or LaTeX > dvips > ps2pdf may be added in the future,
    but they may be too slow for the live updating process anyway.)
    The plug-in does not currently support master- and sub-documents
    via LaTeX's \input{...} and \include{...} mechanisms. This may be
    added in the future.
    vim:tw=78:ts=8:ft=help:norl:
    This is a new version; pretty much completely rewritten from the above. In particular, I've tried to incorporate keenerd's ideas; in particular some changes:
    Rather than grepping the active processes, when it begins a compilation, it records the process ID of the compilation script, and will not begin a new compilation until that process finishes.
    When it first launches MuPDF, it records the Window ID and sends it back to vim, so vim knows which instance of MuPDF to refresh or work with.
    I've added a \s quick key which provides a one-word summary of the effects of the last compilation and jumps to the line number of the first error, if there were errors.
    The script is located in a separate file in the main $VIMRUNTIME/ftplugin folder, rather than a user's tex.vim file.
    I'm sure there's still plenty of room for improvement. I'd still like to get it to handle master/sub-documents well, for example. All comments welcome.

  • Viewing animated gifs in preview

    Anyway to view animated gifs in preview, or is there just some "play" or "animate" button i'm just not seeing?

    The Tiger version of Preview was supposed to work better with animated gifs than the Panther version. Unfortunately instead of improving it they broke something and it doesn't work at all. Thus far no fix has come out in the Tiger updates. Send Apple feedback:
    http://www.apple.com/macosx/feedback/
    The more people who complain the more likely it is to get fixed.
    Francine
    Francine
    Schwieder

  • Gif file preview stopped working

    New computer. Gif file preview was working last night and now I'm just getting a still picture. I installed Photo Impact Pro and that program may have made some changes. I can't preview gifs in that program.  Anyone know a way to restore this feature? I would like to be able to click on a gif file and see it move in preview like it was doing.

    Hi,
    First of all you have to make analysis of the issue.. why its comming..
    thats why i had suggested you to uninstall your newer installed software.. by uninstalling them you can analyse the issue.
    may be programme hadnt installed correctly thats why you are getting this error.
    Please, try to troubleshoot the issue by your self.. uninstall the programme and then check.. if our .gif works with older programme perfectly then your newely installed programme having issue or it was not installed correctly..
    you can install your uninstalled programme later to resolve that issue.
    post result if having any issue. thx
    **Clicking on the Kudos! white star is a nice way to say thank you on any post that helped you or resolved the problem.**
    **Selecting "Accept as Solution" for a reply that solves your issue helps others who are searching the web for an answer**

  • Error while opening the PDF preview

    Hi,
    While opening the form in the PDF preview, i am getting a pop window with a message saying, 'Cannot find 'c:\.\Adobe Examples\request_de.xml'. Make sure the path or Internet address is correct.'. When i click 'ok' it is giving a blank window. Do i need to install anything for that?
    Thanks and Regards,
    Giridhar.

    hi,
    Check u r Adobe version.....
    Adobe Reader 7 to 8.1 its preferable.
    (or)
    Check u r Adobe Lifecycle Designer (ALD).
    Adobe Lifecycle Designer 7.1 and above is preferable.
    by
    Parthasarathi

  • Error message while clicking PDF Preview of a ADOBE interactive form

    Hi -
    I am creating an ADOBE interactive form having Tables, few text fields and E-mail submit button. The scripting language used is FormCalc.
    Whenever I am clicking on PDF Preview to see the form layout and to check other functionality, I am getting an error message:
    Error message -
    Error: syntax error near token '|' on line 1, column 14.
    Script failed (language is formcalc; context is xfa[0].form[0].data[0].Mainpage[0].Subform3[0].Table2[0].Row1[0].RATING[0])
    script=this.isnull || (this.rawvalue >= -32768 && this.rawvalue <= 32767
    I checked my scripts and there is no syntax error in that. My form is also working absolutely fine except getting this error message pop up whenever I try previewing my form.
    Can you please tell me, what can be the possible reason.

    I tried everything, but couldn't figure out the reason for error. I wrote the script again, but the error is still coming.
    Here is a part of my script. I have written this script on Email submit button in preSubmit event, to check if the RATING field value is less than or equal to 3. depending upon this condition, I am making the COMMENT field as mandatory. The same script is repeated for all the RATING & COMMENT fields.
    if (data.GyanMainBodyPage.Subform2.Table1.Row1.RATING1 <= 3)
    then
                  data.GyanMainBodyPage.Subform2.Table1.Row1.COMMENT1.mandatory = "error"
                  data.GyanMainBodyPage.Subform2.Table1.Row1.COMMENT1.mandatoryMessage = "Please fill corresponding comment"
    else
                  data.GyanMainBodyPage.Subform2.Table1.Row1.COMMENT1.mandatory = "disabled" 
    endif

  • Office web apps 2013 March update 2013....pdf preview

    the web application is configured as permissive.
    I did the following
    Remove-OfficeWebAppsMachine
    updated with the march 2013.
    restarted the office web apps 2013 server.
    New-OfficeWebAppsFarm -InternalUrl "https://owa.domain.com" -ExternalUrl "https://owa.domain.com" –CertificateName "*.domain.is" -EditingEnabled
    New-SPWOPIBinding –ServerName "OWA.domain.is" -Application WordPDF
    word / excel preview works
    (Invoke-WebRequest
    https://wac.contoso.com/m/met/participant.svc/jsonAnonymous/BroadcastPing).Headers["X-OfficeVersion"]
    gives an error
    PDF does not open in browser.
    The updates in January were installed automatically.
    Is that maybe the problem?
    I have seen this:
    http://www.wictorwilen.se/sharepoint-2013-enabling-pdf-previews-with-office-web-apps-2013-march-2013-update

    Is it not working only for PDF files? I only used the zone external-https as an example so please confirm that you set the right binding. After all applications have the correct binding you need to create a result type for PDFs:
    Site Settings > (Search) Result Types and then finding the PDF Result Type. Choose to Copy the Result Type.
    Give the new Result Type an appropriate name, “PDF with Preview” for instance. Then scroll down to Actions and in the “What
    should these results look like?” drop-down, choose to use the Word Display Template.
    Regards,
    Andrew J Billings
    Portal Systems Engineer//MCSA,MCSE
    Blog:
    http://www.andrewjbillings.com 
    Twitter:   LinkedIn:
      

  • Office web apps service pack 1 pdf preview

    Hello Experts,
    I have successfully installed and configured OWA Service pack 1 for a sharePoint farm, All office document preview works perfectly only for PDF files not to show preview, are there any special configuration to get this working in SharePoint 2013.
    Thanks

    Hi,
    from Wictor blog
    Before you start fiddling with this, you need to make sure that you have the March 2013 update of Office
    Web Apps Server 2013 (WAC) installed and connected to your farm – if you don’t know for sure, ask your admins – sometimes 
    http://www.wictorwilen.se/sharepoint-2013-enabling-pdf-previews-with-office-web-apps-2013-march-2013-update
    Kind Regards,
    John Naguib
    Senior Consultant
    John Naguib Blog
    John Naguib Twitter
    Please remember to mark this as answered if it helped you

  • PDF preview in windows 8.1

    I am facing a problem previewing PDF file from my application.
    It was working find in windows xp and windows 7 machines, but showing error line "Error HRESULT E_FAIL has been returned from a call to a COM component" in windows 8.1 machine.
    my application using "Adobe PDF preview for Vista" for PDF preivew.
    i think my previewer is causing the problem, but dont know which preview handler me to use instead of "Adobe PDF preview Handler for vista"
    please help me to solve this
    ps: from my windows explorer i can see pdf preview.
    Thanks
    Rosh

    After a close debug, i found that "doPreview" is crashing my application. Also the previewer assembly "PDFPrevHndlr.dll" is modified in Adobe Acrobat XI.
    the modified "DoPreview" method now expecting 2 parameter (int, out int), after giving some values in it, it stops crashing, still my PDF preview not shown up.

  • When I try to open PDF files in my computer, it tells me that my PDF previewer has malfunctioned, how do I correct this situation.

    Recently my computer won't allow me to open PDFs. After looking into the situation, I'm being informed that my PDF previewer is not responding.

    Delete and redownload it if doing so is free in your country.
    (86225)

  • Urgent help needed with iPhoto/pdf preview for book order - mysterious pixelated areas show on PDF but not in iPhoto

    Hello. I ordered an iPhoto book last week to give to my parents for their 50th wedding anniversary. Tonight, I just checked on the order status and found that my book is cancelled. I received no notification about it, and all I could do was fill out the online form, so customer service will get back to me on Monday via email (if I'm lucky...). There is no telephone number for me to call about this. I decided I'd best do some searching to try to figure out what had happened.
    I had thought that the preview I saw in iPhoto was the preview of the book. I found out I was wrong. So I created a PDF preview of the book and found some craziness that I don't understand. In iPhoto (and any other program, i.e. PhotoShop), my photos are fine. They are mostly TIFF format and high resolution with a few high res JPEGs. However, when I view the PDF, there is a band of black and white pixelation about 1/2-inch across the bottom of some pages - not all. The photos in that area are messed up in that band zone. The other photos are totally unaffected. This affects both TIFF and JPEG photos, and both black and white and color.
    Has anyone else had this problem, and what was your solution? I would be extremely grateful to anyone for advice or information about this! The anniversary party is less than a week away and I'm beyond my limit of stress right now...

    Launch iPhoto with the Option key held down and create a new library.  Import enough photos for a book (use some of those in the current book) create a new book and preview as a PDF.  If you don't see the problem then it's limited to your library which may be damaged.  If that's the case make a temporary, duplicate copy of the library and try the two fixes below in order as needed:
    Fix #1
    1 - delete  the iPhoto preference file, com.apple.iPhoto.plist, that resides in your Home/Library/Preferences folder. 
    2 - delete iPhoto's cache file, Cache.db, that is located in your Home/Library/Caches/com.apple.iPhoto folder. 
    3 - reboot, launch iPhoto and try again.
    NOTE: If you're moved your library from its default location in your Home/Pictures folder you will have to point iPhoto to its new location when you next open iPhoto by holding the the Option key.  You'll also have to reset the iPhoto's various preferences.
    Fix #2
    Launch iPhoto with the Command+Option keys depressed and follow the instructions to rebuild the library.
    Select the options identified in the screenshot and the option to rebuild the small thumbnails.
    Click to view full size
    If you get the same problem in the test library then log into another user account on your Mac, create a test library and try it there.  If the problem shows up there a reinstall of iPhoto is indicated.  To do so you'll have to delete the current application and all files with "iPhoto" in the file name with either a .PKG or .BOM extension that reside in the HD/Library/Receipts folder and from the /var/db/receipts/  folder,
    Click to view full size
    If you don't encounter the problem in the other user account then it's something in your account that's the culprit. Post back with the results.
    OT

  • Links (urls) inside a pdf document are not enabled by the New firefox pdf preview feature but are in Chrome & IE

    The new pdf preview feature in firefox desktop does NOT seem to activate any links (urls) inside the pdf meaning they are no longer clickable.
    Is anyone else experiencing this problem.
    I send out product information using pdf's with clickable links inside (as do lots of businesses) and this loss of clickable links functionality is a problem.
    I also tried the same pdf files in IE and Chrome and their inline pdf previews keep all links fully working.
    I know the pdf preview in firefox can be deactivated and the adobe reader can be used instead but in reality lots of people won't know how to do this or won't be troubled to find out how and will just move on.
    Does anyone know if this feature is going to be fixed or supported or is it a deliberate security feature.
    Thanks.
    JP.

    Hey JPEdwards,
    The PDF.js team is still hard at work on the built-in viewer. It looks like there is already a bug on file for this and they are aware of it:
    https://bugzilla.mozilla.org/show_bug.cgi?id=821599
    Please don't post in the bug if you are just confirming that you've seen the problem too. That clutters the tickets ;)

  • PDF Preview Handler Not Working in Outlook 2010

    I have Win 7 Home Premium 64-bit and Outlook 2010.
    Everything was working fine, until a few months ago when the PDF Preview Handler stopped working. I got the typical message that others were having with the issue with Adobe Reader 9. I have Adobe Acrobat X Pro and have also used Adobe Reader X. I have tried the little registry fix app that is supposed to fix this issue, but it states that my registry is already correct. Has anyone found a resolution for this issue with Acrobat X and Outlook 2010? As a workaround I am using the Foxit PDF Preview Handler, but I have to reinstall it everytime Adobe Reader or Acrobat is udpated as for some reason Outlook then reverts back to the PDF Preview Handler, which is not working.
    Thanks,
    Merg

    Nope, using 32-bit. And I recently uninstalled Acrobat Pro completely and reinstalled it due to an issue with it not updating due to having the "Error Applying Transforms" issue. After I reinstalled, I updated it completely. I suppose I can try uninstalling and reinstalling again, but that seems like overkill.
    - Merg

  • White border in pdf preview of bleed doc

    Hi,
    As the attached image shows I get a thin white border on my pdf preview of a document that has a 3mm bleed. I have tried to increase the bleed to 5mm but with same result. I've also tried to exceed the black background outside the bleed marks in InDesign - no result. The pdf is exported with document is generated I'm stuck. Why do I get this annoying thin white border when previewing the pdf document? The people I'm sending this to thinks its something wrong and even if this should turn out to be in preview mode only its ruining my work as everyone else is asking about it when looking at the pdf. Use Document Bleed settings is ticked.

    You mentioned trying to increase the bleed areas by dragging the black box larger, but are you actually specifying the larger bleed when exporting the PDF
    Also, you mention Bleed Marks rather than Crop Marks.
    Crop marks show where the page will be trimmed and this is what the printer needs to see.
    Bleed marks are essentially useless. they only show the edge of the bleed, but give NO indication where the printer should trim to
    Your black screenshots are hard to decipher, but the Magenta box in your 2nd screenshot only shows the margins on the inside of the page.
    Unless you have set the margins to 0, the magenta margin box will always be smaller that the page (the final trim size which is what the Crop marks are for)
    Have you accidently set a Slug area larger than the bleed? This is only way I can get the white space to show.
    The example below used greatly exaggerated settings to better show some issues.I greatly increased the bleed area to swallow the Crop marks and then included the Slug area to show the white.(slugs are not always used or even needed)
    The Magenta box are the margins inside the page.
    The Red box is the bleed area.
    The Crop marks in between these two are what the printer need to cut on to produce the final page size.
    Click on the image below to see a larger version with more detail.
    P,S, you mentioned about not being able to print the bleeds. If you have bleeds and crops that will make the final PDF size larger than your desktop printer can print, just select FIT or REDUCE OVERSIZE PAGE in the print dialog and it will print on your printer. Of course it will not be to 100 scale, but it will show all the elements in the PDF.

  • Adobe PDF Preview Handler Issue in WIndows 8 64 Bit Machine - After installing Adobe Pro 11.0.10

    Hi Guys ,
    We are facing a serious issue with Windows 8 and Adobe PDF Preview Handler . We are using the PDFPrevHndlr.dll from Adobe to show PDF Previews in our application. It is working fine in Windows 7 and Vista and for some reason it is not working in Windows 8.1 64 bit machines after upgrading to Adobe Pro 10.0.10 .  Please help us figure out what is the root cause of this issue .
    During a close analysis we have found that the PrevHost.exe( Windows component ) is failing soon after it is being invoked . Any help in this is much appreciated.
    Regards
    Sree

    Hi Sree,
    According to your description, your case related to Adobe PDF Preview Handler. This is third-party product. I am afraid this is out of our support. Please ask in their special forum
    https://forums.adobe.com/community/adobe_reader_forums
    By the way, after do some search, it seems not working for 64bit machine,
    >> It is working fine in Windows 7 and Vista
    Also work fine in win7/vista 64bit????
    If your scenario is not working in 64bit machine, try to put "adobe pdf preview handler 64-bit fix" in search engine. Good luck.
    Have a nice day!
    Kristin
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

Maybe you are looking for