PDF Preview help

Unsure where to post this question but here goes.
I have two PDF documents which I can view in PREVIEW.
How can I add the pages from one PDF file to another in order to make one PDF file? Wish to view in Preview.
Thanks.

you can also use a free app called Combine PDFs.
http://www.versiontracker.com/php/search.php?mode=basic&action=search&str=combin e+pdfs&srchArea=macosx%7Cosx&x=0&y=0
Really cool!

Similar Messages

  • Pdf preview don´t work. help

    Hi
    i have problem in  tab pdf preview, when i click there appear this message: Warining security:
    "the current security settings do not allow the transfer of this file"
    Can you help me?
    Thanks

    seems fixed with this method:
    http://groups.google.it/group/it.comp.macintosh/browse_frm/thread/6954f6bcc67df8 a8/7860bf2927f8380d

  • 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

  • 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.

  • 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.

  • 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.

  • Adobe PDF Preview Handler Issue in WIndows 8 64 Bit Machine

    Hello Gurus ,
    We are facing a serious issue with Windows 8 and Adobe PDF Preview Handler . We are referring 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 . Any help on this topic 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.

  • PDF previewer not working in Outlook

    All,
    I have recently updated to Adobe reader 11.0.10, I can now open the documents I was not able to open, but the previewer in Outlook stopped working. The error I get is that the doc is not supported by my currect reader and that I have to upgrade to the latest
    version. I have done everything that people suggest on the web - trust center settings, etc., but I have not been successful. Has anyone encountered the same issue and do we have a solution?
    Any help is greatly appreciated
    My details: Win 7 Ent / 32 bit / Office 2010 / Adobe reader 11.0.10
    Thanks

    Hi,
    Have you checked if the PDF Preview Handler is available and shows as enabled in File > Options > Trust Center > Trust Center Settings > Attachment Handling > Attachment and Document Previewers?
    Which format of file are you previewing in Outlook? Please first make sure the format is supported by Adobe reader. You can verify this by consulting the Adobe Reader support. If the file type is supported by Adobe Reader, please open Control Panel,
    find and click Default Programs >
    Associate a file type or protocol with a program, then locate the file format and make sure
    Adobe Reader is set as the default program for the file type.
    If it's not a PDF document that you want to preview, we can also try to preview a PDF attachment to see if it works fine. If this issue continues when previewing a PDF attachment in Outlook, I'd recommend we uninstall and then reinstall the Adobe reader
    to see the result.
    Please let me know the result.
    Regards,
    Steve Fan
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • PDF preview not working in ITS after patch31 - HTTP 404 file not found

    Hi Friends,
    We installed Patch 31 on ITS 620.
    Previousl patch level was 17.
    The functionality to show pdf preview using FM 'SSFCOMP_PDF_PREVIEW' is not working.(Which is working fine when viewed from SAP GUI)
    We are getting 'HTTP 404 - File Not Found' error.
    What could be the reason?
    Any help on this is highly appreciated.
    Thanks,
    Simha
    Edited by: Simha on Oct 30, 2008 3:03 AM

    problem not resolved and we reverted back to older patch.
    Closing this thread

  • Again after last patch: Windows 64 - PDF preview handler not working

    Adobe's PDF preview handler doesn't work unter Windows XP/Vista/7 64 bit. Because of that PDF preview e.g. in Windows explorer or MS Outlook isn't displaying PDF preview.
    This issue has been discussed in this forum some months ago, and this page gives a solution that has helped:
    http://www.pretentiousname.com/adobe_pdf_x64_fix/index.html#fixer
    Instead of fixing this well-known issue with the last patch Adobe decided again not to fix. And after installing the patch you have to repair PDF preview handler again...
    Friendly
    Philipp
    Philipp
    http://ferienbretagne.livejournal.com
    Lenovo W500, 2,8 Ghz T9600, 8GB RAM, Windows 7 Pro 64-Bit, Acrobat 9

    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.

  • PDF previews for FBA users

    Hi, 
    I have an extended web app for FBA users in SharePoint 2013 site. I configured the PDF previews according to following article:
    http://stevemannspath.blogspot.com/2012/10/sharepoint-2013-pdf-preview-in-search.html
    it is working but not for FBA users. I opened the extended web app in SharePoint designer and the code explained in step 6 in above article was there. Unable to figure out if there is any additional step for FBA users.
    Any help would be really appreciated. 

    unfortunately, PDF previews will not work for FBA users according to above mentioned method. So, i followed another method explained here

  • PDF preview and display issue : NWDS CE 7.1 SP05+ALD 7.1

    Hi All
    I am creating a webdynpro java application in NWDS 7.1 SP 05. This application has an interactive form ui element. The livecycle designer version is 7.1 and reader versions tried are 8 and 9.
    The issue is that the pdf preview in NWDS is blank and also I am getting blank white space instead of the form when i deploy the application on a browser.
    I have used NWDS 7.1, SP05 + ALD 7.1 combination on another system and there i can see the form in NWDS pdf preview.
    I am completely stuck, please let me know of any way out.
    Thanks
    Lisha

    Hi,
    Try to uninstall adobe life cycle designer and install it onceagain..
    Even we faced some times this problem, but better to use higher version of adobe life cycle designer like 8.0 whiuch will be compatible to your NWDS version...
    Hope this helps you in resolving the problem...
    Regards,
    Saleem

  • PDF Preview

    hey im trying to make a app that previews PDF files in it but im having some problems. im using alivepdf to generate pdfs then im using a class called CPDFPREVIEW (found here) to preview the pdf. im developing my app on a mac and testing on a pc and pdf preview used to work on all my computers but now on my pc ( and my clients pc ) it has stopped working, what happens is the window comes up but its just white and nothing ever loads nor do i see a loading progress indication. all computers have newest version of adobe reader installed.
    any help with this matter would be appreciated.
    heres my code :
    var stream:FileStream = new FileStream();
                var file:File = File.desktopDirectory.resolvePath("pdf/note.pdf");
                stream.open(file, FileMode.WRITE);
                var bytes:ByteArray = printPDF.save(Method.LOCAL);
                stream.writeBytes(bytes);
                stream.close();
                aPreview = PopUpManager.createPopUp(this, CPDFPreview, false);
                  CPDFPreview(aPreview).width = 1025;
                  CPDFPreview(aPreview).height = 550;
                CPDFPreview(aPreview).loadFile( file );

    ok so i ran HTML.PDFCapbabilities and everything is fine. im thinking it has to do something with finding the file because it acts the same as if i point it too a pdf that doesnt exist. but the pdf im trying to get does exist and i made it through the same app using alivepdf so the file directory must be right...there must be something im missing...dont you hate it when something that used to work just mysteriously stops working?

  • PDF Preview kicks out to Acrobat 7 and Body Pages goes blank

    Two problems, and I suspect they are related...
    I just purchased and installed Acrobat 7 Professional with Adobe Designer.
    FIRST--The PDF Preview in Designer automatically kicks the preview out to Acrobat 7 and does not preview in Designer. Why???
    SECOND--When I click back to Body Pages, for no reason after a little while the workspace goes blank (back to sheer white). It takes about 5 seconds for that to happen--and it happens inconsistently. It seems strange.
    Can anyone help???
    OS/ Windows XP sp2
    Gateway M675 with tons of power and RAM

    It's a rare thing indeed when you can answer your own posts.
    I did a "detect and repair" in Acrobat 7.0 Professional, which seemed to fix the problem.
    I had loaded Acrobat Reader 7 after the initial install of Acrobat 7.0 Professional, and am wondering if that didn't cause the problem somehow.
    Anyway, if anyone else has this problem, you might want to try the "detect and repair."
    Let's hope the problem is fixed for good. :-)

Maybe you are looking for