Adobe 8 Standard problem

Today my adobe 8 standard started corrupting the documents I scanned. I thought I could re-install it but don't know how.

Adobe has release the latest versions of Reader and Acrobat which are 10.1.8 and 11.0.4
In case you are talking about Adobe Reader please upgrade it to the latest.
un-install the older version first and then install latest from below link
http://get.adobe.com/reader/
Please let me know if you face more issues with this.

Similar Messages

Adobe Reader does not recognize file name (filename10.5.11.pdf) but does in Adobe Standard 9. Why?

I post documents to our Intranet site and found out recently that Adobe Reader does not recognize certain file names in PDF files. For instance, when trying to open a PDF file with the name
filename10.5.11.pdf in Adobe Reader, the web browser will not open the PDF and the display is blank.   When I'm using another computer with Adobe Standard 9, I do not have a problem opening the file.
I would like to know if anyone else has had a similar issue and why Reader will not recognize the file name and Standard does.

The version is Adobe Reader 10.1.0    I will request the latest version
and let you know if that fixes the problem
Actually I had changed the name of the file so our associates could access
the file (changed the . to a hyphen) It still made me wonder why Reader
wouldn't open it at that time.
Thanks again for you assistance and I will let you know if this resolves
the issue.
Regards,
Susan
From:   Ankit_Jain <[email protected]>
To:     SusanPleso <[email protected]>
Date:   10/19/2011 12:56 AM
Subject:        Adobe Reader does not recognize file name
(filename10.5.11.pdf) but does in Adobe Standard 9. Why?
Re: Adobe Reader does not recognize file name (filename10.5.11.pdf) but
does in Adobe Standard 9. Why?
created by Ankit_Jain in Adobe Reader - View the full discussion
Hi Susan,
Thanks for providing the information.
Could you also let me know what is the exact version of Adobe Reader on
your system. You can check the same y clicking on Help > About Adobe
Reader X.
In case its not 10.1.1, please try updating to the latest version and see
if the problem persists.
Also, does any other PDF with a different filename open in Internet
Explorer correctly?
Thanks
Ankit
Replies to this message go to everyone subscribed to this thread, not
directly to the person who posted the message. To post a reply, either
reply to this email or visit the message page: [
http://forums.adobe.com/message/3979020#3979020]
To unsubscribe from this thread, please visit the message page at [
http://forums.adobe.com/message/3979020#3979020]. In the Actions box on
the right, click the Stop Email Notifications link.
Start a new discussion in Adobe Reader by email or at Adobe Forums
For more information about maintaining your forum email notifications
please go to http://forums.adobe.com/message/2936746#2936746.

Word 2007 to pdf in Adobe Standard 8.1 errors

I have an XP PC with Word 2007 and Adobe Standard 8.1. I'm having issues converting some
word docs to pdf but not all. You click on the acrobat tab in Word and run the converter, but it stops midway thru the process and says "Error" Other documents work fine. Could it be a template issue or something in the document itself that Adobe doesn't like, ie a symbol, format, font?? Any assistance would be appreciated.

Often it is a document issue, combined with some of the screwy ways that OFFICE 2007 is working. You might try saving parts of the document to another file and delete parts until you find where there is a problem. That might likely point to the issue. Also, try to print to the Adobe PDF printer to check for potential issues. One thing that can crop up with the PDF Maker is that you run out of memory in the TEMP folder. To check that, turn off adding tags to the PDF (really bloats things) and try again. If it works, it is likely a memory issue and cleaning out the TEMP folder might take care of the problem.

Why does the Adobe Standard profile make a mess of old NEF files?

Recently I've been reprocessing some old NEF files taken with the Nikon D50 camera years ago, and I was startled to find that the Adobe Standard camera profile does a bad job on them: the photos come out muddy-looking, really unacceptable, with too much yellow and magenta. I can fix the problem by choosing the Camera Standard profile, which gives acceptable results. However, I believe that Adobe Standard is generally recommended by Adobe, and I wonder what the problem is here. Does anyone know?
I currently use a Nikon D7000, and Adobe Standard seems to work well enough with that camera.
Later: After checking and comparing more carefully, I think that perhaps I prefer Camera Standard with the D7000 too. Adobe Standard is certainly acceptable with the D7000, but Camera Standard gives blue skies of clearer blue, and less exaggerated reds. So the best fix for me is probably to make Camera Standard my default for all cameras.
Looking around the Web, I see various people complaining about too much magenta with Adobe Standard, although other people are happy with it.
Message was edited by: Jonathan Palfrey

Yammer P, thanks for the input. I have been working with the DNG Profile Editor since the first version was available. I also started using the Passport software when it was first available. I first worked on a profile for the D200 and after many attempts I finally have one that works great. The Camera profiles did not exist at that time and the D200 does not have Picture Control Profiles, I believe that was first available with the D300. Adobe did generate Picture Control Profiles for the D200 and they are also available in Nikon Capture NX2.
I currently have a D700, and have spent a lot of time working on profiles for this camera. I have used the DNG Profile Editor's Chart Tab to generate profiles for most of the Camera Profiles and Adobe Standard. I find that Adobe Standard profile is brighter than the Camera profiles by about 0.25 stop. After working on this for about 2 years I have decided to use the Camera Neutral with a modified tone curve and slight reduction in saturation as my starting point and no changes in hue. I also generated a modified Picture Control profile for Neutral using the Nikon Picture Control software that has the same characteristics and loaded it into the camera. I get good agreement between jpg's from the camera and the nef file that opens in ACR without adjustments. The tone curve I used only has three points - the In/out values are 27/22, 127/127, 228/233 and saturation was set to -5.
I don't understand what Adobe changed when they genrated the Adobe Standard Profile instead of the ACR4.x versions, but I like the ACR4.x version better.

User not able to open Adobe Standard 9 on Vista

I can open Adobe Standard as an administrator, no problem. However, when my user tries we get this error:
Faulting application Acrobat.exe, version 9.0.0.332, time stamp 0x4850eb76, faulting module Annots.api, version 9.0.0.332, time stamp 0x4850e57f, exception code 0xc0000005, fault offset 0x001bd9e0, process id 0x7d0, application start time 0x01c996a75577e79e.
Any ideas?

Are you using the standard Vista USER profile? Have you modified the permissions access for that USER profile to something other than the default?
Sanctus

Adobe standard to adobe x

I am having a problem with users being able to digitally sign a pdf using a common access card. I have tried to create several pdf files with adobe standard and it works perfectly. I have extended the "forms fill in and save to reader" option and have also checked all of my security settings. When I save the file and try to open with adobe x the digital sign field does nothing and the security properties now say "not allowed" for digital signature. I have verified the settings in both programs. Is there a patch or something obscure that I may be missing?
Thanks for any help.

I have extended the "forms fill in and save to reader" option and have also checked all of my security settings.
Where did you extend this option?

Arranging files with in a portfolio for adobe standard 9

I have been trying to figure out a way to arrange and save the files in an order that is not alphbetical with in a portfolio. So far I haven't been able to and renaming them to be alpahbetical isn't condusive to what I am trying to do. Any ideas?

The version is Adobe Reader 10.1.0    I will request the latest version
and let you know if that fixes the problem
Actually I had changed the name of the file so our associates could access
the file (changed the . to a hyphen) It still made me wonder why Reader
wouldn't open it at that time.
Thanks again for you assistance and I will let you know if this resolves
the issue.
Regards,
Susan
From:   Ankit_Jain <[email protected]>
To:     SusanPleso <[email protected]>
Date:   10/19/2011 12:56 AM
Subject:        Adobe Reader does not recognize file name
(filename10.5.11.pdf) but does in Adobe Standard 9. Why?
Re: Adobe Reader does not recognize file name (filename10.5.11.pdf) but
does in Adobe Standard 9. Why?
created by Ankit_Jain in Adobe Reader - View the full discussion
Hi Susan,
Thanks for providing the information.
Could you also let me know what is the exact version of Adobe Reader on
your system. You can check the same y clicking on Help > About Adobe
Reader X.
In case its not 10.1.1, please try updating to the latest version and see
if the problem persists.
Also, does any other PDF with a different filename open in Internet
Explorer correctly?
Thanks
Ankit
Replies to this message go to everyone subscribed to this thread, not
directly to the person who posted the message. To post a reply, either
reply to this email or visit the message page: [
http://forums.adobe.com/message/3979020#3979020]
To unsubscribe from this thread, please visit the message page at [
http://forums.adobe.com/message/3979020#3979020]. In the Actions box on
the right, click the Stop Email Notifications link.
Start a new discussion in Adobe Reader by email or at Adobe Forums
For more information about maintaining your forum email notifications
please go to http://forums.adobe.com/message/2936746#2936746.

Vista OS and Adobe Standard 9.x

I would like to hear input from Vista users that have
experience with Adobe Acrobat Standard 9.x
Is there any problems with the functionality of Adobe
Standard 9.x on your Vista OS? What are they, and how did you
correct it (them)?

Thank you for your response. These forums are specific to the
Acrobat.com website and its set of hosted services, and do not
cover the Acrobat family of desktop products. Please visit the
following forums for any questions related to the Acrobat family of
desktop products:
http://www.adobeforums.com/cgi-bin/webx/.3bbeda8b/
Regards,
Ksenija
Acrobat.com moderator

Adobe Standard Beta 1 and D70 profile

I was testing the Adobe Standard Beta 1 with Camera Raw 4.5, and while skin tones and reds are much better it gets completely wrong the following hue
Camera RAW 4.5 Adobe Standard beta 1
http://img166.imageshack.us/img166/7705/purpleadobestandardbetash1.jpg
Nikon NX 2
http://img232.imageshack.us/my.php?image=purplenx21kb2.jpg
Thomas, you might want to have a look at it before final release.
arguros

Dear Thomas,
Can you help me?
I have a problem to use DNG profile:
I am user of Fujifilm S5Pro, which has RAF file (=raw). The ACR (start from version 3...) and DNG understand my RAF files very well. But DNG profile editor dose not want to open it, even if Adobe DNG Converter 4.5 converts it to DNG file. My workflow is:
Launch Adobe DNG Converter.exe, => convert RAF to DNG (tryed different settings);
Launch DNG profile editor, => trying to open DNG file => have error???
May be I'm doing in a wrong way? Please advise me.

Strong colour shift when reselecting Adobe Standard camera profile

I'm having this curious problem with Nikon V1 NEFs (raw files) in Lightroom 4 beta.
In the develop module, Adobe Standard is selected as the default camera profile. If I switch to one of the other profiles (for the V1, the options are Camera Landscape, Neutral, Portrait, Standard, and Vivid) and then switch back to Adobe Standard, I get a strong color shift in the blues, which move towards teal. It looks like a white balance shift, but the white balance settings themselves don't change.
I've attached three screenshots, the first showing an untouched file with Adobe Standard selected as the default profile in the develop module, then with the Camera Vivid profile selected, and then with Adobe Standard reselected. Besides changing the profile, there are no edits on this file: all I've done is import it, put it in a collection, switch to the develop module, select the Camera Vivid profile and then reselect Adobe Standard.
The color shift happens regardless of which camera profile I pick before reslecting Adobe Standard. Interestingly, while the colors are off in the develop module, they're correct in the library module. Switching back and forth between library and develop doesn't fix the problem -- as long as Adobe Standard has been reselected in develop, the colors are off in that module but correct in library. The only way I've found to clear the color shift is to click reset in develop. Select another camera profile, though, and then reselect Adobe Standard and the problem comes right back.

Yes. This is a bug that has been reported/fixed after the public beta build was made ready. Somehow it did not make it to the final public beta release note. The current workaround is to relaunch LR4 or
a) Copy Settings (check all except Calibration),
b) Reset,
c) Paste Settings.
This will invalidate some internal memory cache that went stale.
-Simon

Adobe Standard profile for 5D mark II includes tone curve?

In ACR, I see a "Point" tone curve with the "Adobe Standard" profile on Canon 5d Mark II files.
I've never seen a tone curve before on standard profiles for other cameras. I understand that tone curves are included in the camera standard, faithful, portrait and landscape profiles in attempt to match the in-camera jpegs. But I thought the Adobe Standard profiles were supposed to target only color (hue/sat) and leave tone up to the user.
Can someone verify that your system includes a point tone curve on 5D2 raws. Maybe my config is messed up.

Dear Eric,
I have Photoshop/Bridge CS3 and Camera Raw Version 4.5.0.175 on Windows XP (SP2).
To "see" tone curves I launch Bridge, navigate to a folder, double-click a raw or DNG file and get the ACR window.
In the ACR window, I click on the "Camera Calibration" tab and navigate through the various Camera Profiles.
For each profile, I click on the "Tone Curve" tab and view both the "Parametric" and "Point" curves.
For canon 5D Mark II DNG files there is always a "Medium Contrast" Point Curve, under every camera profile. I do not have a Canon 1Ds Mark III, but I have downloaded a sample raw file and converted it to DNG. For this DNG I also see a Medium Contrast Point Curve under every profile.
For my Canon 20D and Canon 1Ds raw or DNG files the Point and Parametric curves are flat under every camera profile.
When I downloaded the latest DNG converter and DNG Profile Editor, I'm reasonably confident I also downloaded and installed the most current camera profiles.
For Canon 5D2 files I see the following profiles: Adobe Standard, Camera Faithful, Camera Landscape, Camera Neutral, Camera Portrait, and Camera Standard, in that order.
For the Canon 1DS Mark III image I see all those profiles, plus ACR 4.4 and ACR 4.3
For Canon 20D files I see all those profiles, plus ACR 4.4 and ACR 2.4
To make sure I'm not picking up any presets, I have invoked the pop-up menu in ACR and selected "Reset Camera Raw Defaults". Then, for each file viewed in ACR I checked the pop-up menu again to make sure "Camera Raw Defaults" was checked.
And a reminder, all this was after I had created a number of custom profiles from Macbeth Color Checker images using the DNG Profile Editor. Those custom profiles created a problem with Bridge previews, so I removed all of them before viewing Point Curves as described above. Still hoping to get some feedback on the Bridge preview problem I described in this message:
http://www.adobeforums.com/webx/.3bb6a869.59b790c8

Aptus II 8 Adobe Standard color profile missing from LR3.5?

I was wondering, several versions ago, (2.7 I believe) the Leaf Aptus II 8 aka Leaf Aptus 40 was added to the list of supported cameras. My version of Lightroom 3.5 (MacOs 10.6.8) can read these files, however there is no Adobe Standard color profile for this back. When I go to the calibration tab it just shows embedded. These files are uncompressed .mos files and not jpegs or tifs. With my Leaf Aptus 75 I use the Adobe Standard profile and like it. Is this a bug or just an unsupported feature of the Aptus 40?

Thanks, that sounded like a good idea and it got me thinking. Why not trash the profile and import it from another computer. Doing that I found that the file sepraratly downloaded on another computer has the same problem so I can't move it over. The other computer is OS 10.5 Leopard whereas mine is 10.6 Snow Leopard. This leads me to believe that this is an Adobe issue.
Would any other Mac LR3 users please go to Library>Application Support>Adobe>Camera Raw>Lens Profiles>1.0>Canon and see if there is an "exec icon" next to the file named...... Canon EOS 5D Mark II (Canon EF 16-35mm f2.8 L USM) - RAW.lcp
I'd appreciate it and it will help isolate the problem.
Thanks
Greg Eddinger

Adobe Standard unexpected exit when updating Headers

Using Adobe Standard 8.1.4 on Windows Vista. Every time I open a pdf file and try to edit the Headers, I get a message to say that 'Adobe Acrobat 8.1 has stopped working' and I am forced to stop the program. Looking at the details, I see the information:
Problem Event Name: BEX
Application Name: Acrobat.exe
Application Version: 8.1.0.137
Application Timestamp: 46444c82
Fault Module Name: ADMPlugin.apl
Fault Module Version: 3.16.128.32
Fault Module Timestamp: 4644172b
Exception Offset: 000a7bf1
Exception Code: c000000d
Exception Data: 00000000
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 16d2
Additional Information 2: f9851a9f899ba98efdf1ad516412e16f
Additional Information 3: b6e5
Additional Information 4: d4ddf66021077584a030ea3282c4081d
I have followed advice on the website and uninstalled and reinstalled the product completely, but it makes no difference. The same version running on a Windows XP box works fine on exactly the same file.
Any suggestions?
Frances

Hi Shinder,
I would like to know was there any previous version of Acrobat or MS office installed previously? Or Multiple versions of MS office?
The steps you may want to try are:
1. Uninstall Acrobat using cleaner Tool : http://labs.adobe.com/downloads/acrobatcleaner.html
2. Uninstall MS office.
3. Logon as local admin
4. Clean boot: http://support.microsoft.com/kb/929135
5. Install MS Office, check for updates if any available.
6. Install Acrobat and make sure while installing Acrobat all the applications of MS office are closed.
Regards,
Ajlan Huda.

Adobe plugin removed. Defaults set to Adobe Standard. I get Firefox demand to install plugin. How can I force Adobe to use Standard?

Adobe Reader won't open certain (large) Adobe files.
> I set all Firefox defaults to Adobe Standard. Firefox still uses Adobe Reader.
> Uninstalled Adobe Reader. Uninstalled Firefox Adobe plugin.
> When I try to open an Adobe File, Firefox now says to install Adobe Plugin.
... catch - 22.
What can I do to force Firefox to use Adobe Standard? (none of the moderator solutions appear to work)

RESOLUTION (seems not logical, but this worked):
Firefox would do nothing other than ask me to install the Firefox plugin for Adobe, which I accepted. This process leads to re-installing Adobe Reader. After installing Adobe Reader, all of the defaults that I previously had set to use Adobe Standard were re-set during the Adobe Reader installation to use Adobe Reader interally in Firefox.
After re-installing, I was able to load the document that previously I was unable to load (using Adobe Reader inside Firefox). I changed all of the Adobe defaults (under TOOLS/OPTIONS) to "always use Adobe Standard" instead of "Use Adobe Reader (default)". I was then able to open the document using Adobe Standard.
It appears that the following process solved the problem:
> uninstall Adobe Reader
> reinstall Adobe Reader (and the Firefox Adobe plugin)
> change the defaults from "Use Adobe Reader (default)" to "Adobe Standard [release number]"
Note: I have Firefox 21.0 installed, and Adobe Reader XI 11.0.3 installed prior to, and after, this issue.

Adobe Standard 9.1.0 crashes when attempting create .pdf from scanner

Adobe Standard 9.1.0 crashes when attempting "create .pdf from scanner" from a Kyocera Mita KM-2550 using the twain driver. The error encountered is 0xc0000005 at address 0x0000000002d78e70. I have downloaded and installed the latest updates. This is happening on two new PCs with the same configuration. Is anyone else having this problem? Any suggestions?

Spent quite a while on this one.. My problem was related to twain drivers which reside in c:\windows\twain_32. I'm running windows 7 64-bit. First it's usually possible to scan in windows 7 maybe vista and from adobe without even using twain (using WIA). So try renaming the twain_32 folder to _twain_32 and see what happens... If that stops the crashing look at the contents of the twain folder. I had a Dell folder for some printer I wasn't even using. That was causing the crash. I removed the dell folder and renamed the twain folder back to twain_32. Now everything works as designed.

Severe Magenta Cast Some Cameras Adobe Standard

Adobe Standard
Generic Daylight Profile for Canon G10 Created by me with a Macbeth Chart and the DNG Profile Editor (not of this scene specifically) and Adobe Standard as the Base Profile.
Images from a Canon Powershot G10. Both have exactly the exactly the the same settings. White Balance Auto and then Auto Tone with Brightness set back to default of 50.
Download DNG file here
Download Generic Daylight Profile for G10 used in this example here.
Happens with my 5D (original) as well. Does not happen with Leica M9 and can't say for any other cameras at this time.

Actually, I wouldn't expect that much difference between most camera sensors under the same controlled conditions. I suspect if you divided up the Adobe Standard profiles into sensors and other factors more meaningful than make and model, the differences might be more obvious.
So, for example, I see little difference between a Nikon D80 and a Canon (which uses the same APC sensor technology [down to the manufacturer], I think) there is little difference. But when I compare Nikon and Ricoh I see a much more obvious difference. The fact is that the image guts of most DSLRs these days are made from one of at most three manufacturers. The majority come from two. A few others that I recall had similar sensors and image processing engines also seemed pretty similar.
The Adobe Standard is not about trying to pull the wool over our eyes. It is about establishing a baseline for raw image manipulation. The fact that most sensors and bodies will really respond pretty closely aside, there could be outliers. Making the standard based on the make and model allows for a more natural way to handle presets and what-not from the point of an application. The fact that, under the covers, most cameras really respond quite similarly in similar median conditions is not all that interesting.
It is at the extreme edges of image reproduction that the makes, models and even specific bodies will be most drastic (which is why getting to know your camera in extreme shooting conditions is important, and why being able to make your own profiles is so powerful.)
At any rate, if your particular make and model (or even specific body) is not to your liking, it is pretty easy to make your own standard. Because I don't have a studio, I've gone ahead and made "standards" like based on things like time of day (for natural light) or "my living room" which sometimes give me an easy out. No one needs to use Adobe Standard. Heck, if you really like the in-camera settings and Adobe profiling doesn't work then it may be that the vendor software is the way to go. Double heck, some professionals still think this whole raw thing is stupid and shoot JPEG. This solves a whole raft of problems -- decisions one doesn't even have to make. Just get exposure right and go!

Adobe 8 Standard problem

Similar Messages

Maybe you are looking for