Skip navigation
Replies 1 2 3 Previous Next
  • Currently Being Moderated
    Jun 29, 2012 7:26 PM   in reply to station_two

    Station_Two,

     

    That is a very common theme, and not just in the PS Forum.

     

    For some reason, many feel that they can "trick" the Adobe programs, but then are angered, if there is a price to pay.

     

    Most users never have issues, but they are NOT trying to do any tricks.

     

    Hunt

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 5, 2012 8:29 AM   in reply to sunstonecreations

    I had the same problem on the mac. Find where the PS preference files are stored and delete them. Also check every disk you have as a scratch disk and by no means uncheck the drive the application is running off of. This is where I ran into problems.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 14, 2012 6:42 PM   in reply to tattooedmonkey

    I had the same problem as everyone else and read the thread, started as administrator and changed the scratch disk to my media disk instead of the default c:\ drive.

     

    I can't believe software this expensive won't launch after installation because of an issue like this. Photoshop is screaming for a competitor

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 15, 2012 1:23 AM   in reply to efridine

    If some of the responses above reflect Adobe's interpretation of "users" and "tricks", you had better believe these problems are here to stay.

     

    In my case, the only "trick" I can think of is that I changed my tmp and temp environment variables from the defaults to locations where more disk space is available. This is a perfectly legitimate action in Windows.

     

    As an additional illustration that Photoshop CS6 is not behaving as it should, I encountered another problem, even with the scratch disk location adjusted. While it now runs OK when used on its own, it still reports an error with a scratch disk when I call it from within Acrobat X to edit an image, then try to save the edited image.

    To make sure this was a Photoshop CS6 problem I changed the image processor in Acrobat X from PS CS6 to PS C5 (64-bit), and that worked flawlessly.

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 15, 2012 4:05 AM   in reply to jerdenberg

    Check your scratch disk assignments in every variant of Photoshop:  32 and 64 bit variants have separate configuration options!  You may have set one and not the other.

     

    Also check that your username specifically has Full Control permissions for your TEMP area and the root folders of all the disks you've identified to Photoshop for scratch use.

     

    You bought one of the most complex and expensive computer applications there is.  While you have a right to expect it to work, you should also expect to have to take some responsibility for properly setting it up and maintaining your work environment to get the best operation and performance from it.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 15, 2012 4:22 AM   in reply to Noel Carboni

    Well, you can't really set it up properly when you can't even start it, can you?

     

    Of course you should expect more variables to tweak from a more complex, expensive software but should it be more difficult to get started on? It's like you just hop in to your KIA and drive away while the guy with the M5 have to call a mechanic to prepare the trunk for your luggage, open the door to let you in and start the engine for you.

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 15, 2012 4:59 AM   in reply to petersjoo

    Changing your example a bit, it takes more knowledge to drive a big rig tractor-trailer than a Kia economy car.  No, you wouldn't expect to just be able to jump in to a truck cab and go as you might a Kia.

     

    It's possible the problem lies with permissions on your hard drive, and there is a way to forcibly configure the scratch disk settings even if Photoshop won't start.

     

    Try pressing and holding Control-Alt immediately upon cold-starting the variant of Photoshop that will not run.  If you're quick enough to get the keys down, you should see this:

     

    ScratchDisks.jpg

     

    Try changing these or even setting None (note that there is no necessity to fill out all 4 fields).

     

    Also, if you're on Windows try running Photoshop (or the parent program that won't run Photoshop properly) As Administrator.  I'm not talking about whether your account is in the Administrators group here, I'm talking about specifically starting the executable from its shortcut using right-click, Run As Administrator.  If this works, where starting the application normally (which with UAC is in a non-privileged state) does not, you have permissions issues on your TEMP folder or scratch drives.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 18, 2012 5:46 PM   in reply to Noel Carboni

    OK, I Too have this issue.

     

    Brand new install of Photoshop CS6 (64 bit)

     

    We run two (2) accounts on a Windows 7 (64 Bit) machine.

     

    Administrator - to Install software.

    Me (User) - to run software

     

    Pressing Ctrl+Alt+Shirt + Starting PS = starting PS with Admin privileges (i.e. UAC requires admin uplift or password)

     

    I have deleted both the preferences file in the Admin and My (user) profiles in various fashions still not joy

     

    i have rebooted the machine, still no joy

     

    PS starts OK in Admin (or using Ctrl+Alt+Shirt + Starting PS), but of course uses the Admin profile settings

     

    PS will throw an error when starting in my User profile.

     

     

    I have changed the scratch file location to the D partition (rather than C), but still no joy. The user (me) has write privileges to the root of D drive.

     

     

     

    The deletion of the setting file has had no effect.

     

    Can Adobe please answer this query. with an authoritative answer?

     

     

    Many thanks

     

    Chris

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 18, 2012 5:53 PM   in reply to Swin70

    PS, I have also started PS in the User profile, then pressed Crtl+Alt+Shift quickly, and recieve the prompt "Delete Adboe PS Setting File?", I click "Yes", but still no joy. Same error

     

    Restart PS, no joy, same error.

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 18, 2012 6:00 PM   in reply to Swin70

    You're just paddling upstream trying to run as a non-privileged user.

     

    It's a great idea in theory - it helps you protect your system when you do dumb things like inadvertently run malware.  But in practice it just doesn't work very well.  So you fight your computer instead of getting work done.

     

    You might be able to make some headway by installing Photoshop from your non-privileged user account.

     

    I've taken it one step further:  Besides being in the Administrators group I have disabled UAC.  Everything just works great.  As it should be.

     

    Other steps to help prevent malware are perfectly effective.  UAC is just a poor implementation of a questionable idea.  Running as a non-privileged user when you're sharing a big, expensive resource with a bunch of other people makes sense.  But this is YOUR personal computer.  No one else needs protection from you.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 18, 2012 6:19 PM   in reply to Noel Carboni

    I'm sorry but I disagree. Have been a Windows administrator for near on 15 years I have seen and delt with many issues with User/admin privilege system setting across many Windows OS. Sure, there are issues, but since the trial, installation, roll out and on going use of Windows 7 for the past few years, this is the first program I have come across that I is produced by a "major" manufacturer that has cause issues.

     

    Disabling the UAC, in my opinion, is NOT the solution. It maybe a solution for you, but it is not the solution for us and against our policy. PCs are not necessarily the personal possession of the people that use them, In fact the vast majority are of corporate use and the need to security and low level user account is a very real need. If you believe that the whole idea is questionable, maybe this should be taken up with system designer.

     

    What I would like is a proper Adobe resolution to the issue, as I think others are after.

     

    PS. With the UAC intact, software cannot be install in a USER account - this is the whole point. AN administrator raises the privilege level to install the software. The User than uses the software.

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 18, 2012 6:22 PM   in reply to Swin70

    There's no question that Adobe ought to make their product work in the modern security environment.  I didn't say my approach was a substitute for them getting things right.

     

    But Photoshop is what it is.  I'm just describing how to make things work in the real world. 

     

    Maybe Adobe is listening and these problems will be addressed in the 13.0.1 patch.

     

    And please, let's not get into a "who's a bigger geek contest".  Suffice it to say I've got more experience than you.

     

    Have fun fighting your operating system to prove who's boss.

     

    -Noel

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 18, 2012 6:28 PM   in reply to Swin70

    Swin70 wrote:

     

    this is the first program I have come across that I is produced by a "major" manufacturer that has cause issues.

     

    Oh, one other thing:  Keep in mind the design of Photoshop (and no doubt a lot of the source code still) is from the early 1990s.  Things were pretty different then regarding how applications were expected to interact with the operating system (e.g., generally speaking, any app worth its salt actually modified the operating system).  Think how opposite that is from today's thinking.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 18, 2012 7:43 PM   in reply to Noel Carboni

    Ok, tired, but may have found a better work around to the issue which involves no UAC or security permission disabling.

     

    It would appear that in my instance, even after the Preferences file was remove from the user profile, when PS tried to recreate this file it encountered an issue (what I don't know) - the Preferences file although created was 0 bytes.

     

    As a  random test I copied the "Adobe Photoshop X64 CS6 Prefs.psp" from the Admin profile to the User profile. Security permission are automatically inherited in Windows 7 (in fact XP and up), then started PS.

     

    et volia. PS started in the user profile, no errors.

     

    Not sure if there will be any fall out from this, however checked the "Camera RAW Prefernces" and the location folder points to the user profile.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 18, 2012 7:49 PM   in reply to Swin70

    As far as I could see, the permission were identical on the file that was created by PS at 0kb and the resultant file i copied in from the admin profile. Not sure what this issue is, but there is obviously one.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 12:29 AM   in reply to Noel Carboni

    @Noel

    I think you're missing the point. PS is marketed to photographers and artists, not computer "tweak super user admins" per se. And not even being able to run the software, without being one, is poor, lazy *** programmed, overpriced junk of software. BUT with a market monopoly Adobe gets away with it.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 12:35 AM   in reply to Noel Carboni

    @Noel

    NO! PS is not "what it is". Adobe gets a lot of money from their customers to make it work in a modern environment, they can easily gather the skill to do so and they should.

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 20, 2012 1:39 AM   in reply to petersjoo

    I'm not trying to discourage you from asking for fixes.  Please don't confuse an attempt to help you get the most from your system with someone being an apologist.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 1:43 AM   in reply to Noel Carboni

    The 32/64-bit problem cannot exist on my pc,as I did not install the 32-bit version of Photoshop CS6.

    I changed the scratch disk for Photoshop to a suitable drive.

    As I mentioned in my report, Photoshop does behave as it should when started on its own, but reports the scratch disk problem when it is called from Acrobat; I have now found that this happens if it is attempting to save the file that is being edited as a pdf; saving as a tiff or a jpeg worked OK. If I start Acrobat as Administrator, then call Photoshop, the problem does not occur. This suggests the problem is pdf-related.

    All of this is happening in my personal tmp folder, wich is on another disk than the boot disk. As an experiment, I set my permissions for the tmp folder to full control, but that did not make a difference.

     

    The fact that these problems do not occur with the 64-bit CS5 version of photoshop only increases my dissatisfaction with the CS6 version.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 1:55 AM   in reply to Noel Carboni

    @Noel

     

    Sorry, your help and fixes are of course very welcome! I only disagree that it's supposed to be this way and, I guess, I hope that somone at Adobe will pick this up and do something about it. I mean, you have to agree that it's quite poor programming to not even use system wide cache spaces by default, but instead assume that every user is a sysadmin?

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 2:14 AM   in reply to jerdenberg

    @jerdenberg

     

    I don't think this issue is purly NTFS security permissions based, more so this is a UAC based issue. It would appear that Adobe have not followed Microsofts guidance in implementing thier program to work for multiple user levels.

     

    As Noel suggested, one way to do this is to disable the UAC. In my opinion, this is a bit like someone losing thier keys to thier house then to resolve the issue they remove all the doors and windows. Sure, they will be able to get in and out, but so will evryone and thier dog. A better solution might be to get a new key cut.

     

    Basically, Adobe should have the resources to re-work thier software to work with the OS for which it is indended to operate on.

     

     

    However, did you try copying the prefernces file from a working Admisistrator profile to the user profile?

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 20, 2012 2:35 AM   in reply to petersjoo

    Absolutely I agree that it ought to be better implemented!  Adobe does see the things posted here and now and again even fixes some, but sometimes I think they're a bit too willing to assign the blame to the user's computer system, or simply de-prioritize the work.  I browbeat them myself over this from time to time, but outside trying to help them clarify issues I can't really influence what they do, so I simply try to help people make things work better.

     

    In the personal computing world a multiple pronged approach seems to work best:  Ask for fixes and at the same time try to make one's own system more apt to run the software properly.  The latter is a concession that shouldn't be necessary but sometimes is.  As a bonus it pays off again and again, because Adobe is not the only vendor who makes mistakes in programming their apps.  I have a lot of experience in this area as a career computer software engineer.

     

    -Noel

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Aug 20, 2012 2:32 AM   in reply to Swin70

    Analogies are fun.

     

    I liken disabling UAC to replacing a door with a lock that is so balky that it both sometimes keeps you from getting into your own home and allows crooks through occasionally.  The words "false sense of security" come to mind.  Your new door always works for YOU, and it no longer needs to be so secure because you've put up a way better fence around your yard and you've stopped inviting crooks into your neighborhood.

     

    People who think UAC is necessary sometimes assume people can't change other parts of their working environment or change bad computing habits, when in fact doing so can keep malware from ever getting near your front door.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 9:11 AM   in reply to Noel Carboni

    So I have come across this thread to try and find a resolution for this issue and i have to say parts of this upset me.

     

    Half the thread is people accussing others of either not listening to the advice or yelling.

     

    the whole segment of the person who hit no when photoshop asked them to delete their settings was very annoying since i did hit yes and thats when this whole thing started.

     

    instead of making people who have this issue read a whole page of people arguing about stupid things that don't adress the issue why not put up something usefull.

     

    my photoshop worked PERFECT for 2 years until i clicked yes to deleting my settings this morning.   Now i get the scratch error. the reason i did that was because my fonts were all screwed up and someone suggested that would fix the error. 

     

    I have 200 gb free, all tmp files removed. i am unable to edit the scratch file settings under performance even in admin mode.  

     

    so does anyone have a solution to this issue?

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 20, 2012 9:19 AM   in reply to DarkWolf719

    I take it that you are running WIndows 7 and have tried all the CTRL+SHIFT+ALT stuff? 

     

    If so, does PS start OK as the Administrator? To check, run PS as Admin, Right click PS icon, then click "Run as Administrator"

     

    If it works, try copying the settings file from the Administrator profile to your profile

     

    Copy

    "C:\Users\Adminstrator\AppData\Roaming\Adobe\Adobe Photoshop CS6\Adobe Photoshop CS6 Settings\Adobe Photoshop X64 CS6 Prefs.psp"

     

    to

    "C:\Users\YOURUSERPROFILE\AppData\Roaming\Adobe\Adobe Photoshop CS6\Adobe Photoshop CS6 Settings\"

     

    (Note- The above asumes you are using the 64bit version and that you profiles are on the C partition.)

     

     

    I would love to knwo if this helps anyone, or if it just help helped me.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 13, 2012 4:48 PM   in reply to Swin70

    After sorting the cache disk issue to enable Photoshop to run, there are other issues that makes CS6 a real pain.... CS6 just gets worse and worse (I had virtually no problem with CS5 Master Collection on my system)

     

    Problems with PS CS6:

    I cannot past a shape from Illustrator (or any other app) as smart object or Pixels... I get a "Could not open scratch file becuase file is locked" error. I can only past as path or shape layer.

    If I open a file with smart objects, I will not be able to save the file unless I rasterise shape layers.

     

    If I run as Administrator:

    I can paste as Smart Object.

    However, If I run an app as administrator, I cannot save to our Samba File Server and must copy files locally to work on them.*

    As admin, I lose the ability to drag files from file explorer into PS*

     

    *This is the same with Indesign (samba server and drag and drop to document) and Bridge which unless I run as admin, they both crash on startup.

     

    It's getting increasingly difficult to see any real advantage upgrading from CS5 to CS6, sure there may be a few bells and whistles, may be 'faster', but to actually use them in a real-world working environment... CS6 is a pain unless you only work with files on your local machine. Iv'e heard that part of the fault is that I have my User folder on a secondary drive. Now that SSD's are a bit cheaper and larger, I may look at getting a 240GB and re-installing my whole system (on both machines), but It'll suck if it doesn't fix it and CS5 ran sweet without a hitch.

     

    Both machines:

    Windows 7 64bit

    CS6 Master Collection (Adobe Cloud)

    120GB SSD with user folder on alternate drive

    Drive array totalling approx 5TB

    16GB Ram

    i7 2600K

    2 x GTX580 SLI (Single GTX580 on my work machine)

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 27, 2012 3:00 PM   in reply to Swin70

    After a new install, changing the scratch disks after running as administrator didn't fix the problem for me.

     

    Copying over Administrator's prefs file to my normal user account did work though, so thanks Swin70. Hopefully this issue is somewhere above the bottom of Adobe's bug tracking priority list.

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Oct 27, 2012 3:18 PM   in reply to Soulflare007

    What scratch disks are now identified in your Edit - Preferences - Performance dialog?

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 13, 2012 2:42 PM   in reply to Swin70

    YES TO SWIN 70, POST #64... Thank You Very Much For This Post!

     

    This worked for me on two different workstations, with different user privileges (less than Admin) and different versions of PS. Both under XP PRO, one copy of CS(1), one of CS5.5. The user profile structure is a tad different under XP, but the idea is the same.

     

    I don't yet know about issues with Acrobat or Illustrator, but for Photoshop this was the answer.

     

    And to those on this thread who are intent on vocalizing the depth and bredth of their vast knowledge and experience as a means to justify their overt hostility toward those deemed lesser than themselves simply for holding an opposing opinion I say... grow up. The lack of maturity by some on this thread is simply stunning.

     

    And no, this problem is not the result of ignorant users running ill-maintained machines (perhaps in some, but certainly not in the majority of cases). It's an issue that should be addressed by Adobe so it never raises its ugly head again. Even Ahead/Nero (V6.0!) has a little applet that allows Administrators to grant application-specific rights to users needing to burn a CD. If nothing else, an executable patch doing the the same thing for accessing a scratch disk seems pretty reasonable to me.

     

    Message was edited by: Reckless283 (Les De Moss)

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Nov 13, 2012 4:15 PM   in reply to Swin70

    Swin70 wrote:

     

     

    Copy

    "C:\Users\Adminstrator\AppData\Roaming\Adobe\Adobe Photoshop CS6\Adobe Photoshop CS6 Settings\Adobe Photoshop X64 CS6 Prefs.psp"

     

    to

    "C:\Users\YOURUSERPROFILE\AppData\Roaming\Adobe\Adobe Photoshop CS6\Adobe Photoshop CS6 Settings\"

     

    I wonder how it came to be that you have a C:\Users\Administrator folder.

     

    I don't have Adminstrator subfolder of Users on any of my Vista, Windows 7, or Windows 8 systems here.

     

    Is it possible this was a result of installing a later version of Windows as an upgrade from XP (or a chain of upgrades)?  Maybe a case Adobe didn't account for?

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 14, 2012 7:18 AM   in reply to Noel Carboni

    Noel Carboni wrote:

     

    Swin70 wrote:

     

     

    Copy

    "C:\Users\Adminstrator\AppData\Roaming\Adobe\Adobe Photoshop CS6\Adobe Photoshop CS6 Settings\Adobe Photoshop X64 CS6 Prefs.psp"

     

    to

    "C:\Users\YOURUSERPROFILE\AppData\Roaming\Adobe\Adobe Photoshop CS6\Adobe Photoshop CS6 Settings\"

     

    I wonder how it came to be that you have a C:\Users\Administrator folder.

     

    I don't have Adminstrator subfolder of Users on any of my Vista, Windows 7, or Windows 8 systems here.

     

    Is it possible this was a result of installing a later version of Windows as an upgrade from XP (or a chain of upgrades)?  Maybe a case Adobe didn't account for?

     

    -Noel

    This is determined in the way you set up your PC in the first place. The administrator accounts are disabled by deafault, however, the vast majority of business systems will enable this account and lower the rights on the standard user acounts.

     

    It is a completely standard business and systems practice, one which I'm sure Abobe have on thier own internal systems. I don't think they would have overlooked this.

     
    |
    Mark as:
  • Noel Carboni
    23,514 posts
    Dec 23, 2006
    Currently Being Moderated
    Nov 14, 2012 8:52 AM   in reply to Swin70

    Thanks for the response.

     

    Of course, I had a lapse.  Administrator is being enabled as part of the custom setup for the enterprise.  As I always am the full administrator of all my own systems here I don't do that as it's not needed.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 19, 2012 11:01 PM   in reply to Noel Carboni

    If only the author of the scratch disk error message has included the text, "... or hold down CTRL+ALT during startup to remap your scratch disk to a new location." instead of suggesting that I locate my scratch disk directory and ensure it is not set to read-only.   The message was already a full paragraph long, and offered no help!

     

    I honestly had no idea which directory Photoshop had defaulted to and no idea which TMP file might be read-only. It was so much easier to just use your CTRL-ALT trick to select a new drive!

     

    As far as the cause, my new Dell XPS PC is just 6 hours unboxed.  I'd only installed Symantec Endpoint Protection prior to this failed install of CS6 Master Collection. Upon the first launch of my virgin software, I was presented with all of these warning diaogs that bombed the system.  

     

    Thank goodness for your screenshot and this posting.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 2, 2012 2:40 PM   in reply to sunstonecreations

    hello!! please someone help me i get the message o the scratch disk  missing  file. , ive tried a lot of the things you post it:

     

    * press ctrl alt shift, and erase the setting, but still the same error

    * run the program right click as administrator, same error

    * press ctrl alt and choose my removable hard disc (which took a longgg time to make it work... but it opened!!! =D, but a msg appear about javascript not been found, and i couldnt save anything that i did because another msg appeard saying that the file could not be found)

    * disable the UAC

     

     

    i just have one user on my laptop, so i cant copy the files from one user to the other i guess thats not my case, (or somethin like that im not very familiar with programing or things like that, so please explain evertithing step by step) and i have just one hard disc, with 50 gb free. windows 7, 32 bits, photoshop cs6.

     

    so nothing works, please please help me =( =(

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 2, 2012 8:05 PM   in reply to angelluzita

    all you have to do is use pixels instead of inches

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 4, 2013 12:30 PM   in reply to Noel Carboni

    I'm going to add my 2c to this post because I had this issue and was able to resolve it satisfactorily. There is a lot of bad behaviour by some arrogant users in this thread, but I'm replying up here anyway despite the grief of reading through a lot of - frankly - useless garbage and verbal harangueing.

     

    Your mileage may vary but here is my scenario: a relatively small SSD as my boot disk, and a large HDD as my data drive. I had already moved /Users to the HDD creating a hard link, and I need my /TEMP directory to be on the HDD because that directory gets a crapton of stuff thrown into it including temporary internet files etc, and I don't want it taking up valuable resources on my boot drive.

     

     

    Originally I had just created the TEMP directory on my D:\ drive and then pointed the environment variables there. But it looks like Photoshop, InDesign, Bridge, Encore and god knows what else for some reason NEED TEMP to be on the C:\ drive.

     

     

    The solution: create another hard link (junction) for C:\TEMP to D:\TEMP like this:

     

     

    Open up a command prompt, navigate to your C:\ drive, check that there is NO TEMP folder yet and then enter:

    mklink /J C:\TEMP D:\TEMP

    (use drive letters that are appropriate to your setup).

     

     

    Then go back and re-edit your environment variables to point TEMP and TMP to C:\TEMP again. Note that you have to do this in 4 places - look through the entire list of system and environment variables and change them all.

     

     

    Now you have the best of both worlds: A) your TEMP files are off your boot drive and are on your data drive B) your Windows environment variables are set up correctly C) Adobe apps THINK they're writing to C drive even though they're not.

     

     

    I don't know for the life of me why Adobe apps care (they should not, and should just respect your environment variables - that's why Microsoft created them!), but they seem to care. This should solve the issue.

     

     

    DISCLAIMER: I'm writing this only moments after having implemented this solution and the only tests I have performed are booting Photoshop, Bridge and InDesign. But where they were all crashing before, they are now booting up correctly.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 13, 2013 10:29 AM   in reply to jerdenberg

    Changing the scratch disk worked for me.  Thanks for the fix.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 15, 2013 10:07 AM   in reply to sunstonecreations

    Thank you so much for sharing your experience. This greately helped me. Here is what happened to me:

     

    As Windows was becoming too big I moved the "Windoss/ Temp" File to an other drive in my computer. After that Photoshop and Bridge would not work anymore. I got the message "could not open a scratch file because the file is locked". Just like you if I ran Photoshop as an administrator I could then open it but it would not work anymore within CS6. The dynamic link being broken.

     

    Reading your post helped me to understand the issue and I put back the Temp Folder in Windows. After that everything is working again.

     

    Thanks again

     

    Cristiana

     
    |
    Mark as:
  • Pierre Courtejoie
    7,038 posts
    Jan 11, 2006
    Currently Being Moderated
    Mar 16, 2013 6:34 AM   in reply to 300188

    I'm wondering if it would be possible to first move the scratch disk location, then move the temp directory.

    Cristiana, did you try what tomauger suggested?

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 16, 2013 8:43 AM   in reply to 300188

    Did you see above where you can hold down CTRL-ALT during start-up to move the Temp Directory?

     

    It's a "Feature" that frequently lament that Adobe does not mention in the paragraph long dialog box when the error occurs.   Do a "Find in Page" for the keword "CTRL-ALT" on this thread for more directions.

     

    My Background on the issue: This saved me about 20 hours, when I got a brand new system with an SSD / HD Combo.  I'd configured all of my environmental variables (TMP, TEMP, Virtual Ram, Scratch Disk, My Documents, etc) to a D: drive to avoid fragmentation and read/writes to the SSD to avoid hastening it's demise.   I really only had a "Windows" directory and "Program Files" on the SSD.  A clean install of CS6 Master Collection to the SSD blew up and wouldn't open because my TMP/TEMP were on a D: Drive.  The dialog to move the scratch disk was such an easy solution that took 20 seconds (though it took me 3 days to find the soultion!). 

     

    Just hold down CTRL-ALT.   (Probably CMD-ALT on a Mac, but I don't know for sure.)

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)