Photoshop CS6: Save for Web Automatic Resize Issue

Some my .psd files (CS6 Photoshop, MAC OSX 10.7.5, Processor: 2.5 GHz Intel Core i7) automatically resize to a percentage. I can't figure out what the cause is, and it will not allow me to change it back to 100% to slice out images for web.
File Type is .psd - RGB 8 bit/color
Fie Dimensions are 1400px by 10,800px.
File Size is 60MB
The file is extremely slow to open and adjust anything within the file as well, not sure if the issue is related.
I am working off of my desktop not off of a server.
Attached is the save for web issue.

I have the exact same issue, just on certain files?
I have to 'save as' instead of 'Save for Web'?
What causes this to happen?? I also have the preview window displaying a gif when I've got the PNG option selected???

Similar Messages

  • Photoshop CS6 Save For Web UI extra border Bug

    Last week we finally got upgraded to CS6, and I'm dissapointed to see the visual defect I reported in CS5.5 still exists in Photoshop CS6 Save for Web. The details and screenshots are all the same as in my previous thread. http://forums.adobe.com/message/3843054#3843054
    Isn't there a way to fix this?  I rely on PhotoShop to be pixel perfect, not to add extra distracting lines and borders to my work.

    FYI, just to test I just did a crop of an image, then screen grabbed the result.
    To ensure the edge is visible, I changed the workspace background from the dark gray I usually use to a lighter gray...  Here's the pertinent part of the workspace...
    A closeup of the upper-right corner:
    Notably, I don't see any black line around it like you showed.  This leads me to wonder whether I interpreted your screen grab properly...
    -Noel

  • In Photoshop CS6, Save for Web strips out my filename after a period "." character

    I have a file named label-1.5oz.psd.  In Photoshop CS6 when I use "Save for Web" to save it as a JPG, it only wants to save a part of the filename: label-1.jpg
    I strips out everything after the period "." character.  I know it's incorrectly thinking that's a file extension.
    Any ideas how I can fix this?  Any settings I should tweak?  I'd really love for it to save the full filename without requiring me to retype the last part every time.
    Thanks in advance for any help!

    Oh if only it were that easy...  Unfortunately, they have to be cropped and resized, converting over from a print catalog where much of that work was originally done in InDesign, and now have to convert each individual image to make the web site look like the catalog...  but thanks for the suggestion, have already tried to automate what I could..  But much of this is going to be hands on...  getting my familiar quick keys to function correctly would help greatly.

  • Photoshop CS6 save for web some colors change?

    I have a picture with large area of color: #fffdfd, when I save it for web (jpg) this color is changed to #fefcfd (in JPG).
    I just can not save as JPG with #fffdfd.
    (was trying uncheck convert to sRGB, do not embed color profile - always #fffdfd changes to #fefcfd when save for web)
    However, color #fefcfd when save for web , does not change.
    Why some colors change and some not? Is it a bug ?
    Window7 64bit, Photoshop CS6

    Save for Web & Devices will strip some color data from the file.
    Browsers aren't color managed. Most file formats on browsers assume they're sRGB. While Photoshop gives you an option of embedding sRGB to the document color space, it also strips off data that is not relevant. This is a common occurence.
    PNG-24 on the other hand will give you the exact color match.
    Also, Save for W&D, JPG quality matters a lot - The same color at Quality 10,20,30,40,50...100 wil give you different color reproductions on the JPG end output.
    If you're concerned that much about an offset of +/- 1 hex value to your RGB colorspace, dont save for web & devices. Do a 'Save As' instead. Then use an image editing/ resizing application such as ResizeMe to resize the quality of your document. This, in most cases will retain colorspace information but just drop the resolution and quality of the image - giving you a lesser filesize.
    On a sidenote, You may also want to read this article on how to best manage color spaces: http://viget.com/inspire/the-mysterious-save-for-web-color-shift

  • Photoshop CS6 Save for Web not working

    I am using photoshop CS6 (cloud) on Mac (10.7.5) and when I use the Save For Web > save, i got the following popup :
    ---- Adobe Save For Web Error ----
    Could not complete this operation. An unknown operating system error has occurred.
    I have been using CS6 for months and it worked fine yesterday before shutting done. Today morning at startup it was not working anymore.
    I have tried to  uninstalled and reinstalled photoshop, clear my presets, shut down/started up, repair disk, repair permissions,... without succes.
    The save for web function still works in CS5.
    Any help will be very much appreciated,
    Raphaël K.

    I found the solution (took forever to consolidate all the answers) for OS X 10.9 + Maverick. Finally!
    1. Change permissions (as AOTPR says) to your User/Library/Preferences file so that your admin and user (the one you are using) has read + write permissions within the Get Info pane (command+I). You may have to add them with the sign.
    2. Delete Adobe save for web 12.0 Prefs & Adobe save for web 13.0 Prefs files within the User/ Library/ Preferences folder. These may be hidden for some people, so when in a finder window, hold Option(alt) and click Go from the main top menu (keep holding Option/Alt) and click Library — the full Preferences folder should open for you.
    3. Change the view when in Save for web pane in PS. If you have it in Cover Flow — it won't work. Change it to another view like List or Columns view.
    Presto! Works for me on Maverick.
    Thank god. It took forever to get this cleared up!!
    If you have any questions, email me [email protected]

  • A different take on the "Save For Web" color shift issue...

    Ok, everyone who has fussed much with photoshop and "Save For Web" knows about the color shift issue. If you want your colors to look right after you "save for web", you have to work in the sRGB colorspace, and have Proof Colors checked (soft proofing on) and the proof color setup set to Monitor RGB, otherwise what you get looks terrible when displayed in a browser.
    But of course if you are editing for print, this is exactly what you DON'T want to do. Well, I work in both. In fact, often the same images, and I want them to appear as close as reasonably possible in both print and web formats, and without a lot of fussing on my part. And I'm pickiest about the print mode, since I have the most control there, so that's the way I want to edit by default.
    Nothing new here.
    Now comes the interesting part (in my mind, anyway). Obviously there is a known remapping -- because PhotoShop DOES it when you select Proof Colors. So the inverse mapping must also be known (with some gamut issues, but I'm not concerned with those, because, after all, I'm VIEWING it on a monitor anyway!). What I want is a plug-in that automatically applies that inverse mapping so that, when I do a Save For Web, I end up with the colors I've been viewing all the time when setting the shot up in print mode. Then, too, I don't have to worry about what mode I'm in when I'm editing -- it just fixes it when doing a save-for-web.
    Again, I want to edit in my normal print mode (typically ProPhoto colorspace, and with soft-proofing off or set to the printer/medium combination I expect to use), then do a single operation (might be a multi-step action) to "screw up" my colors so that when I then do a "Save-For-Web", the resulting image, when viewed on the average color-stupid browser, looks like the image I've been seeing in Photoshop.
    Anyone know of such a beast?   I would gladly pay for a plug-in that really works and fixes the problem.
    And if you have other solutions, I'm interested, but the absolute requirement is that it I do one single edit pass for my colors for both print and web use, and I get what I see on the screen in PS on both the prints and on the web display (i.e., working in sRGB/Monitor RGB mode all the time won't cut it). And PREFERABLY, let me do all my editing work in the ProPhoto (or at least AdobeRGB) colorspace so I have a gamut closer to what the printer can do.
    Anyone got a decent solution for this?

    Sorry, I think I'm being unclear.  This has nothing to do with individual monitor profiles.  In Proof Setup, "Monitor RGB" amounts to turning off ALL color management, and simply letting the monitor do what it will.  It is what the vast majority of web browsers do (even if the operating system provides color management, the browsers don't take advantage of it), so that is what you need to consider for images that will be viewed on a web browser.  If you convert your image to sRGB,  select Monitor RGB in Proof Set up, and turn on Proof Colors, you will see the image as it would appear on a web browser (after you save it as a jpg or use "Save For Web/Devices" to save it as a jpg).   Since almost everyone is running different uncalibrated monitors, there will be lots of variation in how it will look to them, so precise control of the color is unimportant.
    That said, I would expect the color on a calibrated monitor (such as the one I use when editing) to be reasonably close to the colors I am seeing while editing in PS.  To the extent a monitor deviates from "calibrated", those colors will vary, but a good monitor should show good colors.   Unfortunately, this is NOT the case, as my previous post shows.  The colors produced by the steps above are oversaturated and significantly shifted in hue.  There is, to my mind, anyway, no reason for this.  Adobe clearly knows what the mapping is between the colors as it displays them in PS and the un-controlled "Monitor RGB" -- that is, it is the color map they are using during normal editing display.  If they were to reverse-apply that map prior to saving it as a jpg, then the image would appear on a browser on that same (presumably calibrated) monitor very similar to what you set up when editing.  Anyone else viewing the image on a web browser with a calibrated monitor would also see good colors.  To the extent other viewers' monitors are out of calibration, their colors will suck, but there's nothing you can do about that.
    I guess in some sense I AM "asking for a Color-Mamangement-solution for a "non-Color-Management-situation", but specifically I'm asking for PS Color Management to do the best it can for non-Color-Managed situations that we all face every day.
    Does that make more sense?

  • Looking for a better solution to the "Save for web" color shift issue

    Ok, everyone who has fussed much with photoshop and "Save For Web" knows about the color shift issue. If you want your colors to look right after you "save for web", you have to work in the sRGB colorspace, and have Proof Colors checked (soft proofing on) and the proof color setup set to Monitor RGB, otherwise what you get looks terrible when displayed in a browser.
    But of course if you are editing for print, this is exactly what you DON'T want to do. Well, I work in both. In fact, often the same images, and I want them to appear as close as reasonably possible in both print and web formats, and without a lot of fussing on my part. And I'm pickiest about the print mode, since I have the most control there, so that's the way I want to edit by default.
    Nothing new here.
    Now comes the interesting part (in my mind, anyway). Obviously there is a known remapping -- because PhotoShop DOES it when you select Proof Colors. So the inverse mapping must also be known (with some gamut issues, but I'm not concerned with those, because, after all, I'm VIEWING it on a monitor anyway!). What I want is a plug-in that automatically applies that inverse mapping so that, when I do a Save For Web, I end up with the colors I've been viewing all the time when setting the shot up in print mode. Then, too, I don't have to worry about what mode I'm in when I'm editing -- it just fixes it when doing a save-for-web.
    Again, I want to edit in my normal print mode (typically ProPhoto colorspace, and with soft-proofing off or set to the printer/medium combination I expect to use), then do a single operation (might be a multi-step action) to "screw up" my colors so that when I then do a "Save-For-Web", the resulting image, when viewed on the average color-stupid browser, looks like the image I've been seeing in Photoshop.
    Anyone know of such a beast?   I would gladly pay for a plug-in that really works and fixes the problem.
    And if you have other solutions, I'm interested, but the absolute requirement is that it I do one single edit pass for my colors for both print and web use, and I get what I see on the screen in PS on both the prints and on the web display (i.e., working in sRGB/Monitor RGB mode all the time won't cut it). And PREFERABLY, let me do all my editing work in the ProPhoto (or at least AdobeRGB) colorspace so I have a gamut closer to what the printer can do.
    Anyone got a decent solution for this?

    Chris
    I spent all day Googling and doing side by side comparisons of my old and new systems.
    My display is a Dell U2410. It has several presets, including sRGB and Adobe RGB. I've been using sRGB.
    On my OLD system, (Win XP, PsCS2, DwCS4) there seems to be no distinction between color managed and non color managed apps, even on this wide gamut display. I could capture (digital camera) in Adobe RGB, open and edit in PsCS2, save as .psd, convert to CMYK for print, or convert to sRGB for SFW. All images looked identical and they printed and displayed perfectly. I thought this was normal, and seemed logical. This also seems to be the source of my incorrect assumptions. I was trying to get my new machine to behave like my old one.
    So I get this new machine (Windows 7, PsCS5, DwCS5) and now (still in sRGB display mode) all color managed apps appear de-saturated. Non color managed apps are OK. If I switch the display to Adobe RGB, color managed apps are OK, but non color managed apps are way too saturated. From my investigation, I believe this is normal behavior on a wide gamut display. I've tried changing the Control Panel > Display > Screen Resolution > Advanced settings > Color Management options, but to no avail. Either I'm missing something, or Windows 7 is doing color management differently.
    It seems my only option now is to use Adobe RGB display setting for Ps, etc. and switch to sRGB for Dw and non color managed apps. Or, have 2 separate files for print and web. I've Googled 'til my eyes are numb and still not sure I'm getting this. Any enlightenment would be greatly appreciated.
    Finally, I don't see an edit function here, so I can't remove my previous incorrect reply. Moderator, please feel free to do so.
    Thanks

  • About CS6 save for web quality.Always aliasing.

    I used to save JPEG or PNG by save for web before(CS5).
    I found out beside the "save for web" interface changes and the quality become very low in CS6.
    No matter setting high quality 100%. it is sill aliasing.
    I know if use "export" it colud be better. BUT I can't set the image size.
    I have to edit artboards or resize in photoshop.
    I want to make sure what worng with my cs6 save for web. it's my computer problem or does anyone else have the same problem??
    Thanks.
    mac pro os x 10.8.3 / cs6

    save for web setting
    I tried optimized and matte...same result.
    save-for-web-seeting-300%forview
    result_save-for-web

  • CS6 "Save for Web" "Convert to sRGB" Issues

    Hello,
    I'm aiming to take RAW photo files, edit them in a wide color space, and when posting them to the web, save them as sRGB.
    My workspace is as follows:
    I open RAW files in Photoshop via ACR as 16-bit ProPhoto smart objects.
    When I finish editing them, I use "Save for Web" with the "Convert to sRGB" and "Embed Color Profile" boxes checked.
    Photoshop and Bridge tell me the profile in photos saved as such is sRGB as expected. When I upload to a site like flickr, however, the metadata says the photo is still in ProPhoto. See an example here: http://www.flickr.com/photos/nrbelex/7950202448/meta/in/photostream
    If I use "Convert to Profile" and change it to sRGB, then upload to flickr, the metadata says the photo is in sRGB, as it should be.
    What am I missing here?
    Thanks!

    Without using Flickr, I'm not seeing any problem with any of the color-managed software I have here.
    The ProPhoto test file I prepared, when Save For Web is used, is saved with sRGB numbers and (since I checked the box) has the sRGB IEC61966-2.1 profile embedded in it.
    Photoshop re-opens the file and correctly judges that it has the sRGB IEC61966-2.1 profile.
    A search through the binary data from the file Saved For Web using a text editor turns up a number of references to sRGB IEC61966-2.1, but none to ProPhoto RGB.
    Your first image above, however, has BOTH references to sRGB IEC61966-2.1 and ProPhoto RGB, the latter appearing in a string of text data that looks like:
    <rdf:Description
    rdf:about=""
    xmlns:xmp="http://ns.adobe.com/xap/1.0/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:aux="http://ns.adobe.com/exif/1.0/aux/"
    xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/"
    xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/"
    xmlns:stEvt="http://ns.adobe.com/xap/1.0/sType/ResourceEvent#"
    xmlns:stRef="http://ns.adobe.com/xap/1.0/sType/ResourceRef#"
    xmp:Rating="3"
    xmp:ModifyDate="2012-09-07T12:40:05-05:00"
    xmp:CreateDate="2012-09-06T19:18:56"
    xmp:MetadataDate="2012-09-07T12:40:05-05:00"
    xmp:CreatorTool="Adobe Photoshop CS6 Windows"
    dc:format="image/jpeg"
    aux:SerialNumber="022031001932"
    aux:LensInfo="70/1 200/1 0/0 0/0"
    aux:Lens="EF70-200mm f/2.8L USM"
    aux:LensID="165"
    aux:LensSerialNumber="0000000000"
    aux:ImageNumber="0"
    aux:ApproximateFocusDistance="4294967295/1"
    aux:FlashCompensation="0/1"
    aux:Firmware="1.1.3"
    photoshop:DateCreated="2012-09-06T19:18:56.056"
    photoshop:ColorMode="3"
    photoshop:ICCProfile="ProPhoto RGB"
    xmpMM:DocumentID="xmp.did:0F84D078F91311E19565E271D59D6831"
    xmpMM:OriginalDocumentID="98EDC08C95F6E809F2FB9CADB1F3442D"
    xmpMM:InstanceID="xmp.iid:0F84D077F91311E19565E271D59D6831">
    -Noel

  • Ps CS6 Save For Web - various resampling choices give identical result

    Ps CS6
    OS X 10.6.8
    Save For Web offers 5 resampling algorithms (the same 5 as in Image Size, ignoring "Bicubic Automatic", of course) for when the output is being resized.
    All choices except "Nearest Neighbor" output an identical image (which is different to all results of Image Size). Although the "Bilinear" output contains the same pixels as the output of the 3 bicubics, its file size is slightly different then their shared file size.
    I normally resize with Image Size, so this post is not a request for help. This is only to alert Adobe to the apparent problem.

    conroy2009-
    i am happy to report the issue for you, with some more information to better understand the problem.
    i would recommend you take a look at the following link:
    http://www.jeremymoore.com/GettingGoodPictures/PhotoshopResample/
    http://help.adobe.com/en_US/photoshop/cs/using/WSfd1234e1c4b69f30ea53e41001031ab64-7945a.h tml#WSfd1234e1c4b69f30ea53e41001031ab64-793ca
    http://www.photoshopessentials.com/essentials/resizing-vs-resampling.php
    the link above better explains the differences in the three resampling modes.
    -janelle

  • Photoshop CS4 Save for Web JPEG Colors are Off

    Ok, I've scoured the web to see about finding a solution for this and tried every possible option and still I'm coming up empty handed. I have a website that I'm developing for a painter and have an image converted to sRGB, and the colors are where I want them to be. I use Save for Web, and every iteration suggested online for the, embed and don't embed, convert to sRGB and dont' covert, use document color profile, use windows, yada yada. Here's a recent example:
    when i preview the image with Firefox, here's the difference:
    The photoshop version is on the left and is the color that I want/need. The image on the right is firefox and saturated. If I save for web with embedded profile, safari is accurate, whereas firefox is saturated, so it's obviously discarding the icc and using some color space that I can't see in my file. I did notice that if I have my Custom, Proof and select Monitor RGB, then I can see what firefox will ultimately display and also what Safari will display if i have Embed ICC Profile unchecked in the save for web dialogue box.
    I know that CS2 and CS3 were easier and less squirrely with color managing web files, but I think CS4 has some juju under the hood. Am I the only one out there frustrated, or like other web developers just accept the inaccuracy and move on? Since this is fine art, I'm doing my best to dial the color in, but it's been all afternoon beating on this.
    Any ideas, I'm ready to install CS3 and see if my life will be easier, but I'm wondering if having Photoshop CS3 and CS4 will cause any issues.

    >> your logic
    That's my rant and I'm sticking to it.
    The OP wrote he doesn't want or need to discuss the pros and cons of embedding profiles in Web images, but for the sake of anyone else reading this:
    1) Embedded ICC Profiles increase file sizes (about 4K per image).
    a) I may have over 100 thumbnails and dozens of photos on one page,
    b) Plus, I may have an image sliced into many pieces.
    c) That additional 4k per image, per slice, will add up fast and may kill dial-up traffic.
    2) Very few computers use color-managed web browsers or calibrated monitors anyway, and
    3) Problems with matching/blending image's edges or background color with a filled box or page color.
    d) If I tag the image — on Mac colormanaged browsers — the color will mismatch the box/page color on managed browsers because the tagged image is being Converted to MonitorRGB, and the untagged page or box color is having MonitorRGB Applied.
    e) This matching or blending a pixel-based graphic to page color is a pretty big deal to do correctly in professional web publishing.
    f) If I publish untagged sRGB images/graphics, the box/page color will match the images and blend correctly in all browsers.
    I WILL QUALIFY my general recommendation about embedding profiles in pixel-based web images for the following reasons:
    1) You are posting fine-art images, creative portfolios, and are not worried about adding 4K additional data per image, per slice.
    2) You are not worried about having Mac visitors seeing graphic blends or photos mismatched to a background color.
    3) You understand only properly-profiled monitors and color-managed web browsers will benefit from your embedded profile — and it is likely 99% of web surfers don't have either — however, if you are targeting the one percent who do, then there is your number one best reason for tagging web photos with embedded profiles.

  • Photoshop cs5 + Save For Web appends file names

    Hey everyone :
    Anyone know of a fix or a preference i can set? Hopefully, the response isn't "Can't do that anymore".
    Example file name/structure:
    Filename_partof-filename.version-01.00.psd
    Issue (save for web):
    CS3 - Filename_partof-filename.version-01.00.jpg
    CS5 - Filename_partof-filename.jpg
    Using a period as part of the file name was never a problem before CS5/5.5. Having to re-type half the file name in the SaveForWeb dialog is aggreviating/annoying to say the least. I know I can use hypens and underscores, etc but after using photoshop since v3 and using periods as part of my naming convention for 15 years, ...like I said, it's just an annoyance.
    Anyone come across this? Suggestions?
    Thanks tons,
    Greg

    Adobe Photoshop Version: 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch]) x64
    ...yep, everything up to date (more or less).
    This isn't a recent CS5 issue but a CS5 issue from the day it was released...I just got aggreviated enough today with it to come here and see if I could find an answer. It's definitely a SaveForWeb issue and not SaveAs.
    Here's a similar post from back in March 2011...http://forums.adobe.com/message/3509172#3509172
    Just to be clear...
    - Open new/old PS file
    - Save with name.name.v.01.psd
    - Quit PS
    - Re-open file
    - SaveForWeb
    ...if you're able to save it out with the file name in tact, I have no idea how.
    I've tried 4 different CS5 Photoshops and they all truncate the name after the first period.

  • CS6 "Save for Web" problem.

    Hi. I am trying to save an animated GIF using Photoshop CS6. But when I hit the Save for Web option, a dialog box appears saying, "This operation could not be completed." What should I do?

    Hi, sir. I have tried your suggestion but none of them helped. I'm sorry. Here's a screenshot of my work. After I have imported the video clip I'm about to used for my animated gif.
    But then when I click "Save for Web" option, a dialog box appears.
    I'm a photoshop newbie so please can you help me.

  • Photoshop wont "Save for Web"

    Ever since I installed CC on my vanilla MacMini (Late 2014) running OS X 10.10.1, I haven't been able to use the "Save for Web" feature in Photoshop (2014.2.2 Release, 20141204.r.310 x64) anymore. I keep getting an error message saying "The operation could not be completed. The file or directory could not be found."
    Google and the forums have unfortunately only come up with people having similar problems, but not with any solutions. Any help would be greatly appreciated!

    I seem to have skipped your earlier response.
    I've been on OS X 10.10.2 for a couple of days now. Pretty much since it was released.
    Here's the contents of my ~/Library/Preferences/Adobe Photoshop CC 2014 Settings directory:
    Seems like the file is missing and PS can't write in there for one reason or another. These are the permission settings on the folder:
    Turns out, my initial idea wasn't the worst: I now transferred the entire ~/Library/Preferences/Adobe Photoshop CC 2014 Settings directory from my tmp-admin user to my actual user. Lo and behold – tataaa – sure enough, there was a Save For Web Prefs.psp file in there. And after starting PS, I can now SFW again.
    This issue is worked around, but I am still puzzled and a bit annoyed by the fact, that there doesn't seem to be any real explanation, why on earth that problem happened in the first place and what might still be running differently than it should.
    For reference …
    The contents of the imported settings-directory (permissions: drwxr-xr-x   20 r8r  staff) look as follows:
    The contents of the original directory (permissions: drwxrwxr-x  17 r8r  staff) like this:
    Beats me.
    Anyways – thanks a lot for the assistance, and if you have any further ideas on how to get to the root of the problem, I'd be happy to hear about it!

  • CS6: save for web doesn't work

    i have photoshop extended CS6 since yesterday and today when i was going to save an animation, go to file- save for web, this appears "the operation could not be compleated" someone help me please.

    i have a PC, well i made a lots of animations from ps cs5 and i never had problems with that, i just made a animation from a clip of a video like this
    but when i press click photoshop crash down or this appears:
    this doesn't happen to me with CS5 and i didn't copied plug-ins from another version, i just intalled it and that's all.

Maybe you are looking for

  • Can no longer view pdf files in Safari

    Adobe viewer installed. Was working okay. Upon first "download" of pdf file, had pop-up window to locate Adobe Reader application. Then pdf files were opened in Safari with Adobe Reader controls across the top of the Safari window. For no apparent re

  • Windows 7 Issues

    I am running Windows 7 64-Bit Ultimate with 16 processors (4 Quad i7 cores), 128GB of RAM on 2TB of SSD drives. and I have a range of issues.  The most prevalent is that the computer will completely freeze while typing into any application (Word, Pow

  • Password doesn't work and my old email is listed s...

    When I go into my settings to update my profile and change my email address, it prompts me for my password which doesn't work and then won't update my profile.  I can't ask for a new password as it'll send it to my old email account??  There's no oth

  • Attachment name in Outlook is ok, see on Exchange always named "body"

    Hi, I'm using the SMTP adapter to send emails in my organization. Last week a guy come to talk to me, because the file attached to the email sent to biztalk (2006 R2) has different names when looking from Outlook and when looking from the webmail (Ex

  • R12 on Windows: I cannot find the OM tables in VIS - please help

    Hi, I have R12 installed on my Windows. I am using Oracle SQL Developer to browse the VIS tables but I cannot find the tables I need to browse. For example: oe_order_headers_all, oe_order_lines_all, & wsh_delivery_details Thanks, Amorsolo