Opening files is SLOW

The first time I try to open or save a document in Word it can take from 45 seconds to two minutes for the box to open that allows me to choose a file, or a destination. Of course the beachball is spinning away the whole time.
I'm finding that this is the case with more apps than just Word. This lag does not happen on successive attempts to save or open. It only happens the first time after opening the program.
Has anyone else had this problem? Solutions? Ideas?

thanks dr smoke!! finally someone with a brain!!! guess i'll put the hammer away and not try to fix that blasted colorwheel with it.
Hi, pgreensoup.
Do you have an iDisk? If so, disable iDisk auto-sync
in System Preferences > .Mac per this thread.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X

Similar Messages

File Server Role: Slow access for "opened files" and slow Explorer browsing

Since we migrated our fileserver from Windows Server 2008 R2 to Windows Server 2012 we are facing two major problems:
1. Opening files which are already opened by other users takes about 1 minute before the file actually opens. This is not only for Office files such as Excel and Word, but also for other (not office) files. Again, this problem only rises when the file(s)
is/are already opened by another user. There seems to be a sort of "Lock" check time which is about 45 to 60 seconds.
2. The other problem is browsing via Explorer through the network drive (all clients are Windows 7 clients). Half of the time there is some kind of "hick up" with displaying the results of the folder. I cannot figure out a patern, but if there
is no "hick up" then browsing is very fast (also in the busiest times of the working day)... If there is a "hick up" the result can take about 50 seconds to display the content of a folder.
I suspect the SMB implementation / settings of Windows Server 2012 which are causing the problems...
Things I tried:
1. Changed the Oplocks wait time to 10 seconds (which is the minimum). The result is that openening files does indeed go some faster (still taking about 45 seconds).
2. Disabled SMB2: the result is that browsing is fast... Opening files does go faster. BUT: we are then facing other problems like some files are not able to open... This setting was, after getting a lot of complaints from the users, changed back to enabled
SMB2.
3. Within the NIC card properties I disabled "QoS packet Scheduler", "Link-Layer Topology Discovery Mapper I/O Driver", "Link-Layer Topology Discovery Responder" and IPv6 (as we only use IPv4).
All above with not the promising results.
The server is a dedicated (virtual machine on vSphere 5.1) fileserver.
Please Advice since this is not workable, and we have postponed the migration of the fileserver for our aother location.

Hi Dave,
I suggest you disable all third party applications like Anti-Virus application to test if it could reduce the waiting time when accessing a file.
Here are some related threads below that could be useful to you:
DFS Slowness when Opening Microsoft Documents and Excel Spreadsheets
http://social.technet.microsoft.com/Forums/windowsserver/en-US/61ec9a99-0027-44cb-815c-0da9276c1c96/dfs-slowness-when-opening-microsoft-documents-and-excel-spreadsheets?forum=winservergen
Opening files over network takes long time
http://social.technet.microsoft.com/Forums/windows/en-US/c8ddb65f-8a17-4cee-afd4-dfc09e99d562/opening-files-over-network-takes-long-time?forum=w7itpronetworking
opening folder or file takes over a minute on Windows 2008R2 File server
http://social.technet.microsoft.com/Forums/windowsserver/en-US/b9aa98c4-3ef7-4e6d-810d-6099e72b33f6/opening-folder-or-file-takes-over-a-minute-on-windows-2008r2-file-server?forum=winserverfiles
Best Regards,
Amy Wang

Photoshop CS3 opening files painfully slow on a Mac

We're having an issue here at work where Photoshop CS3 is very slow in opening files of any size on our Macs.
We're running 10.5.8 on 2x2.66 GHz Dual-Core Intel Xeon MacPros with 3 of them having 8 gigs of ram and my machine running 12 gigs.
I've tried doing a bunch of research on the issue, but all I can find about it has to do with the issue on a Windows machine involving the network/default printers. I've tried deleting both our network printers and adding them again after a restart with no luck. We've even tried deleting the Photoshop preference file along with the Adobe Mediabrowser preference.
If anybody has any thoughts on how to fix this (aside from upgrading to a newer CS), they would be greatly appreciated.
Thanks in advance!

Ok, I think I found a little work around that so far, for the past hour or so is working good. Files are opening up a lot faster.
What I did was create a virtual default printer following instructions I found Adobe's site...
1. Open System Preferences, and select Print & Fax.
2. Choose the + sign to add a new printer.
3. Choose IP.
4. In the Protocol pop-up menu, choose Line Printer Daemon - LPD.
5. In the Address field, type in localhost.
6. After Generic PostScript printer displays in the Print Using field, click Add.
7. Close out of the Print & Fax preference or Quit System Preferences.
http://helpx.adobe.com/x-productkb/global/set-default-printer-print-center.html
Once I did all that, I had to go into the Preferences and delete the Photoshop and Mediabrowser preferenses and then restart the computer. Hopefully this fix sticks, but if not, I'm sure I'll back to see if anybody has any other ideas.
Thanks for all the help guys, I really appreciate it.
EDIT
Well, it's been a few days and it looks like I may have spoke too soon on the above fix. Photoshop seems to be slowly reverting back to the problem.

Dreamweaver CC opening files very slow iMac with Fusion drive

I am working on a small website based off on Bootstrap 3. Now that I am almost done with the project opening files take a few seconds to open them (in code view). I have tried the various fixes like resolveremoteurltoipaddress=FALSE but still the files load very slow. On my Windows Machine it loads very fast and that machine is 4 years old. The iMac I am using at work is the latest version with decked out specs and only Dreamweaver CC and Edge Code have very slow opening of files. Creating new documents inside Dreamweaver CC is fast. Is there a way to make Dreamweaver open files faster? How to make it load faster, open documents faster, especially in code view. My initial thought is maybe its because I am linking to a few JS library like TypeKit and jQuery but I have not experience these problems on my Windows PC. Any help would be appreciated.

I am working on a small website based off on Bootstrap 3. Now that I am almost done with the project opening files take a few seconds to open them (in code view). I have tried the various fixes like resolveremoteurltoipaddress=FALSE but still the files load very slow. On my Windows Machine it loads very fast and that machine is 4 years old. The iMac I am using at work is the latest version with decked out specs and only Dreamweaver CC and Edge Code have very slow opening of files. Creating new documents inside Dreamweaver CC is fast. Is there a way to make Dreamweaver open files faster? How to make it load faster, open documents faster, especially in code view. My initial thought is maybe its because I am linking to a few JS library like TypeKit and jQuery but I have not experience these problems on my Windows PC. Any help would be appreciated.

The latest issue of Pages for iPad: 1. Very slow. 2. Late in reacting to typing. 3. When I go to a specific file, informs me that some images were deleted and therefore file has been changed. Then when OPEN option used, opens file slowly. Please, help!

What I have to do to correct the following problems with Pages app. For iPad:
Hesitates to display results of typing, some times for 5-6 characters;
Very slow in opening files;
Before opening of a specific file displays message: DOCUMENT DETAILS. SOME CHANGES WERE MADE TO YOUR DOCUMENT. SOME IMAGES ARE MISSING BECAUSE THEY WERE DELETED FROM YOUR DOCUMENT. We'll, nothing is missing. But it takes forever to open this file. The previous issue of Pages worked very good. But they would not let me to go back to it. Please, help!

Tmobile did the exact same thing to me. So that is customer service at work in general. Nice try though lol.
To the OP
I see you said You paid for shipping, did you Insure it? Claim insurance on it. If you did not, It may not be Verizon or your fault in the sense of the phone not making it to the warehouse. There are people out in the postal world that will steal phones that are not insured. It could have been a Verizon employee, i suppose.
But, if this was to be a bought in court, if you shipped it with out insurance, sadly your at fault.
Do you still have the Serial number of your old phone? If so, you should be able to track where your phone is (if it is reported as a defect/damaged) If so, you may be able to use that as proof. If it does not show up as a defect or what ever they determine use as a loss, then you know it did not make it to the warehouse to be checked in. I would suspect Apple or Verizon could tell you what the Serial number came up as.

Lion Preview and Textedit very slow when opening files from Leopard Server

My small office (about 10 users) recently upgraded our iMac's, Mac Mini's, and Macbook Pro's. We are experiencing a big problem with Preview opening super slow (1-2 minutes) when trying to open JPG's, PDF's, etc from our 10.5.8 Leopard Server. We have deleted numerous plist files related to Preview, completely deleted Preview.app from one iMac and reinstalled it via Pacifist and still no change in performance. One of the new iMac's does open much faster than the others, but we cannot figure out why this one machine works well and the others don't.
All machines are showing the below error (dozens of times) in Console when trying to open files directly from the server...
sandboxd: ([###]) Preview(###) deny system-fsctl
We have searched the internet for a solution but have not come up with anything that works. This problem exists with Textedit as well. We did try opening a file from one Lion machine to the other and it opened very fast. We also can open files very quickly from older 10.4.11 Tiger machines directly from the server. So the best we can determine right now is Lion and Leopard Server are not playing nicely together.
Any help would be greatly appreciated.
I have pasted (one of) the console log files below for reference.
Preview(3364) deny system-fsctl
Process:         Preview [3364]
Path:            /Applications/Preview.app/Contents/MacOS/Preview
Load Address:    0x102c9a000
Identifier:      Preview
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process: launchd [114]
Date/Time:       2012-04-24 13:28:40.470 -0700
OS Version:      Mac OS X 10.7.3 (11D50d)
Report Version: 7
Backtrace:
0   libsystem_kernel.dylib                  0x00007fff922a0516 fsctl + 10
1   AppleShareClientCore                    0x0000000105629f4a afp_getMountURL + 112
2   afp                                     0x0000000104e7fe03 AFP_GetMountInfo + 161
3   NetFS                                   0x00007fff8a17c295 NetFSGetMountInfo + 147
4   NetFS                                   0x00007fff8a17e08f GetCompleteMountURL + 68
5   CoreServicesInternal                    0x00007fff86ef1e51 _ZL29addVolumeInfoForURLToBookmarkPK13__CFAllocatorR19BookmarkMutableDataPK7__C FURLmjPK9__CFArrayPP9__CFError + 1535
6   CoreServicesInternal                    0x00007fff86ef12fb _ZL28createBookmarkWithURLAtDepthPK13__CFAllocatorPK7__CFURLmS4_PK9__CFArrayR19 BookmarkMutableDatajbPP9__CFError + 3230
7   CoreServicesInternal                    0x00007fff86ef2443 _CFURLCreateBookmarkData + 1309
8   CoreFoundation                          0x00007fff8d1e3219 -[NSURL bookmarkDataWithOptions:includingResourceValuesForKeys:relativeToURL:error:] + 105
9   Foundation                              0x00007fff91b72fbf -[NSURL(NSURL) encodeWithCoder:] + 239
10 Foundation                              0x00007fff91b2e4ed _encodeObject + 1120
11 Preview                                 0x0000000102cdfb4d
12 AppKit                                  0x00007fff90975f0b -[NSWindow encodeRestorableStateWithCoder:] + 316
13 AppKit                                  0x00007fff90974a00 -[NSPersistentUIRecord generateArchive:] + 177
14 AppKit                                  0x00007fff90975937 recursivelyEncodeInvalidPersistentState + 525
15 AppKit                                  0x00007fff90973ccc -[NSPersistentUIManager flushAllChangesOptionallyWaitingUntilDone:updatingSnapshots:] + 1128
16 AppKit                                  0x00007fff90973836 -[NSPersistentUIManager flushPersistentStateAndClose:waitingUntilDone:] + 182
17 AppKit                                  0x00007fff90973714 __-[NSPersistentUIManager acquireDirtyState]_block_invoke_1 + 53
18 libdispatch.dylib                       0x00007fff8a79b2b6 _dispatch_source_invoke + 635
19 libdispatch.dylib                       0x00007fff8a797f77 _dispatch_queue_invoke + 71
20 libdispatch.dylib                       0x00007fff8a7986f7 _dispatch_main_queue_callback_4CF + 257
21 CoreFoundation                          0x00007fff8d0da06c __CFRunLoopRun + 1724
22 CoreFoundation                          0x00007fff8d0d9676 CFRunLoopRunSpecific + 230
23 HIToolbox                               0x00007fff86aa731f RunCurrentEventLoopInMode + 277
24 HIToolbox                               0x00007fff86aae5c9 ReceiveNextEventCommon + 355
25 HIToolbox                               0x00007fff86aae456 BlockUntilNextEventMatchingListInMode + 62
26 AppKit                                  0x00007fff90918f5d _DPSNextEvent + 659
27 AppKit                                  0x00007fff90918861 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
28 AppKit                                  0x00007fff9091519d -[NSApplication run] + 470
29 AppKit                                  0x00007fff90b93b88 NSApplicationMain + 867
30 Preview                                 0x0000000102c9bdb4
Binary Images:
       0x102c9a000 -        0x102e7efef com.apple.Preview (5.5.1 - 719.16) <EE12E506-F88C-319F-A2B4-5EF997884F0C> /Applications/Preview.app/Contents/MacOS/Preview
       0x104e7f000 -        0x104e86fff com.apple.URLMount.AFPPlugin (4.0 - 4.0) <91C71C5D-562D-37C4-9131-6E6F086288DE> /System/Library/Filesystems/NetFSPlugins/afp.bundle/Contents/MacOS/afp
       0x105618000 -        0x105664ff7 com.apple.AppleShareClientCore (2.5 - 2.5) <CC62F28C-398E-35E2-B2C0-B85A02E57247> /System/Library/Frameworks/AppleShareClientCore.framework/Versions/A/AppleShare ClientCore
    0x7fff86aa5000 -     0x7fff86dcfff7 com.apple.HIToolbox (1.8 - ???) <D6A0D513-4893-35B4-9FFE-865FF419F2C2> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
    0x7fff86eec000 -     0x7fff86f17ff7 com.apple.CoreServicesInternal (113.12 - 113.12) <C37DAC1A-35D2-30EC-9112-5EEECED5C461> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/Cor eServicesInternal
    0x7fff8a17a000 -     0x7fff8a181fff com.apple.NetFS (4.0 - 4.0) <433EEE54-E383-3505-9154-45B909FD3AF0> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x7fff8a795000 -     0x7fff8a7a3fff libdispatch.dylib (187.7.0 - compatibility 1.0.0) <712AAEAC-AD90-37F7-B71F-293FF8AE8723> /usr/lib/system/libdispatch.dylib
    0x7fff8d0a1000 -     0x7fff8d275fff com.apple.CoreFoundation (6.7.1 - 635.19) <57B77925-9065-38C9-A05B-02F4F9ED007C> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x7fff90910000 -     0x7fff91514fff com.apple.AppKit (6.7.3 - 1138.32) <A9EB81C6-C519-3F29-89F1-42C3E8930281> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff91ae2000 -     0x7fff91dfbff7 com.apple.Foundation (6.7.1 - 833.24) <6D4E6F93-64EF-3D41-AE80-2BB10E2E6323> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff92289000 -     0x7fff922a9fff libsystem_kernel.dylib (1699.24.8 - compatibility 1.0.0) <C56819BB-3779-3726-B610-4CF7B3ABB6F9> /usr/lib/system/libsystem_kernel.dylib

"Enable Related Files" isn't the fix for this issue. It's slightly different - I wanted to still load related files, but only the ones local to the file I was editing.
The fix was to use DW's Resolve To IP Address feature. It required adding a registry value - it fixed the issue straight away
This Adobe support doc helped: http://kb2.adobe.com/cps/887/cpsid_88742.html

Acrobat 9 Pro very slow open files over network in Windows 7

I have installed Acrobat 9 pro on my new PC. It's running Window 7 64bit. I use it for pre-press of high-resolution files for printing. Sometimes the file sizes run into the 100s of MB.The new PC has reasonably high specs, with 6Gb of RAM and a 2.8Ghz Quad core i7 CPU and gigabit networking.
Opening them when on the local hard disk is reasonably fast. For example a multi-page 400Mb file starts drawing the first page withing 3 seconds. But opening the same file when it's on the server of our gigibit network generates a very long pause. The application locks up and dispays a "not responding" message for 2-3 minutes. The bigger the file, the longer the pause. It doesn't completely crash -- eventually it starts to draw the pages and I can work as normal.
I used to have Acrobat 9 pro on my old XP PC which was a cheap low-end machine when bought 3 years ago. (has on-board shared RAM graphics card and only 1Gb of RAM). But what grieves me the most, is this slow old machine will open the same 400Mb file off the server so much faster than my expensive new machine. There is no lock up and it begins drawing the first page after only approx 5 seconds.
The problem doesn't seem to be simply related to slow network speed. I can copy the entire 400Mb file from the server to my hard disk in only 12 seconds. The old PC is actually slightly slower copying to/from the network. If the application was for some reason copying the entire file into memory or to a local cache, this should still only generate an extra 12 second delay -- not 3 whole minutes.
Adobe Reader 9 doesn't have the problem. I can open the 400Mb file off the network on either my new or old machine within seconds.
Acrobat 9 Pro doesn't have the problem on an old G5 mac either. It's somewhat slower than my old PC but will begin drawing the first page after a few seconds,
So what exactly is Acrobat doing for those 2-3 minutes?
I have already tried:
1. changing network ports/cables.
2. disabling anti-virus software
3. disabling "remote differential compression"
4. Patching Acrobat 9 to 9.2
5. Files located on Windows servers and Mac Xserves.
Not improvements from any of these.

I think I have isolated the source of this problem. It's the Pitstop Professional 9 plug in. I un-installed this, and everything opens quicker than greased lightning. I re-installed it and it's back to slowsville.
Unfortunately Pitstop is essential to my workflow.
Until recently I did my pre-press on a Mac G5 with Acrobat Pro 7 and Pitstop 6.5. I never had this problem with slow file opening. But it seems that the delays would occur when I used the plug-in with large complex files.. So it would open files as fast as you'd expect from an elderly machine. But starting to use Pitstop would result in a prolonged period of staring at a spinning beachball.
I wonder is there any way to stop the Pitstop plug-in from initializing until it is used? So the plug-in stays inert until you select the tool from from the menus.

Excel 2007 Slow Opening File

We were looking at migrating to Office 2007. To verify compatibility, several key users have loaded Office 2007 on their machines. There seems to be several problems related to opening files in Excel.
If Excel is open and the user does a File/Open, files will open quickly. However, if the user clicks on a file to open it, it can take up to a minute to open. I found a fix for this on this forum. It is to add "%1" to the end of the Open command line in the defined file types for XLS files. After this worked, I found that also needs it for the New on XLT, Open for XLSX, New on XLTM, and New XLTX files.
After adding in the above fix I wanted to verify that it worked correctly by recreating the problem so I went in and removed the "%1" from all of the commands. When I tried to open a file, I got an error. So I went back into the File Types and checked the command lines. Now all of the command lines had a %1 at the end of them without the quotation marks. When I would try to delet this %1, it would now allow me to. I could remove it but when I reopened the line, it was back again. If I added the "%1" back to the end of the line it would take that and it would fix the problem again but I was still unable to remove the %1 from the other commands such as New, Print, Save As, etc. I had to Restore my system in order to remove them.
Further testing on the fix reveals that when I file is opened, it attempts to open the file twice. The first time it opens very quickly and then a minute later it opens the second time. Notice that this is the same delay that was experienced previously. It you open the file and make a change before the minute has elapsed, then you get a message stating that the file is already open and if you open it again you will lose your changes. This is probably due to the Use DDE being selected. But If I turn off DDE, then when I click on the first file, it opens quickly and when I click on the second file, it also opens quickly but if I look at the Task Manager, their are 2 copies of Excel running. If I go to the View tool bar in either copy of Excel and try to view the other window, I can not. So it appears that there physically 2 copies of Excel running. When I went back into the File Types, the Use DDE that I had unselected before is now checked again but the DDE command line is blank.
Thinking that may this was something that was surely fixed now that it is 2008 and the software is 2007, I looked for updates and found that IT had not run the updates. Loaded the Compatibility Pack and Service Pack 1 and high hopes that this would correct the problems. After loading the updates, I found that the File Types had reverted back to their original form without the "%1". Now I was really excited. Why would they reset user changes unless they fixed something related to them? To my dismay, the slow startup was back. I had to go back and set the "%1" back into all of the proper command lines.
As of now, my recomendation to IT is to stay as far away from Office 2007 as possible until Microsoft gets their act together.
By the way...I have tried all of the other recomendations from Microsoft about Excel being slow to start. They make a difference of less than 1 second. They also only make the App start quicker. They are not related to clicking on a file to open it.

I didn't seem to get much help from this forum but I will pass on the fix that I have found.
The problem doesn't have anything to do with the %1 fix that everyone is using. All that does is to open the file before Excel is fully started. In particular, before the add-ins are opened.
You can verify this by changing the command line in the File Types to use a /s parameter which will bypass loading the add-ins.
What I found was that even though I had removed the Adobe AcrobatMaker add-in, the file PDFMaker.xla was still in the XLSTART folder and was being loaded.
Since Office now has it's own PDF functionality, this is no longer needed. I did however want to keep Acrobat so that I could print PDFs from other applications and edit PDF files so I wanted to keep it. Just not in Office.
Here are the steps to remove PDFMaker from Excel.
Choose Start > Control Panel > Add/Remove Programs.
Select Acrobat Professional and click Change/Remove.
Click Next.
Select Modify and click Next.
Expand the Create Adobe PDF menu, then select the Acrobat PDF Maker option, and change the status to "This feature will not be available".
Click Next, and then click Finish to complete the process and allow Acrobat to remove the PDFMaker component. Note: You need the installation disk to do this.
After completing this process, it is interesting that it disabled but did not remove the PDFMaker.xla add-in. It is therefore necessary to remove it manually by exploring to C:\Program Files\Microsoft Office\Office12\XLSTART and manually deleting PDFMaker.xla.
Now for those of you who have already tried the "%1" fix and found that it causes new problems and doesn't fix things, you may have already found out that when you try to remove the "%1" from the File Type Open command line, something puts it back in as %1 without the quotation marks. This causes errors when you open a document that has spaces in it's path such as unable to open C:\Documents.xlsx, Unable to open And.xlsx, unable to open Settings.xlsx. No matter how hard you try, you cannot remove the %1.
So here is 2 ways to overcome this.
You can change the parameter from %1 to "%10". This will work as long as you don't try to open 10 files at the same time.
Or you can edit your registry and remove the %1. The easiest way I found was to open the registry editor and search for excel.exe" /e %1. Notice that this is the end of the command line. When I found it, I removed the %1. If you edited more than just the Open command for XLS files, you will need to keep searching until you remove all of the changes. This will get you back to where you were before you tried the "%1" fix.
There may be other add-ins that cause similar problems. Look in the C:\Program Files\Microsoft Office\Office12\XLSTART folder to see what is really getting loaded.

Adobe reader x very slow opening files over vpn to samba share

Takes 2 to 3 minutes to open a file - Acrobat Pro v7 accesses immediately - downgrade
to Acrobat 7 reader works fine - true on XP and Windows 7 - all updates installed.

I think I have isolated the source of this problem. It's the Pitstop Professional 9 plug in. I un-installed this, and everything opens quicker than greased lightning. I re-installed it and it's back to slowsville.
Unfortunately Pitstop is essential to my workflow.
Until recently I did my pre-press on a Mac G5 with Acrobat Pro 7 and Pitstop 6.5. I never had this problem with slow file opening. But it seems that the delays would occur when I used the plug-in with large complex files.. So it would open files as fast as you'd expect from an elderly machine. But starting to use Pitstop would result in a prolonged period of staring at a spinning beachball.
I wonder is there any way to stop the Pitstop plug-in from initializing until it is used? So the plug-in stays inert until you select the tool from from the menus.

EXTREMELY slow to open files - Illustrator CC 2014!

Hi,
I just updated from Maverick to Yosemite 10.10.1
See my system config on this monosnap link:
http://take.ms/2CAxh
I have installed the latest Illustrator CC - 18.1.1
See monosnap link:
http://take.ms/lgqj0
I have a big problem everytime I try to open a file from within Illustrator CC!
When try to open a new folder (with few or meny files) it TAKES FOREVER for Illustrator to render the files in the folder. (Aprox 2-5 minutes...).
Everything on the machine freezes - it's like a big hang! - but after the loooong wait the hang kind of releases and I can see all files in the folder and can open and go on with the job...
When I do exactly the same but from within Photoshop CC (2014.2.2) everything works smooth, quick and fine!
I have turned of Yosemite transparance, checked that I have Verdana installed.
What more can I do???
Please help - this problem is extremely tedious to have!

Hi Evil Lair Bear,
have You find a solution and solved the problem (besides the embedding idea)?
I still have the same problem = extreeemly slow to open files from within Illustrator 18.1.1
We have tons of old illustrator files dating back so far as Illustrator 3.2...
It's impossible fur us at the studio to reopen all old files and embedding pics...
Now we alla have to have to do the annoying work around "find and open the files in finder"...
This is driving me nuts...
Any help would be magic! ;-)

Photoshop CS3 slow to open files

I have looked at all the answers i can find so far on this and other forums, but have not yet been able to effect a solution, so please bear with me, and hopefully someone can assist further.
The problem is that opening files is painfully slow - having read about the issue with network printers (which I don't have) I have deleted everything listed under printers and re-installed the only printer that I have (which is locally attached via USB, but I deleted it in case Adobe thought is was a network printer).
I have tried to create a generic printer (as recommended by Mr Joslin to jangel2 http://forums.adobe.com/message/2657130#2657130), but the installation failed and no additional printers were visible in control panel/printers.
I am running Windows 7 on a Dell desktop, with plenty of memory etc.
I have a number of external hard drives, and have turned all these on so Photoshop can find them in case it's looking, but this made no difference.
I am at a loss and hope someone can help.
Many thanks
Lizzie

Hi All, Apologies for the radio silence and many thanks for your responses.
A techy friend of mine came round and changed loads of settings, restored to a previous point (prior to the windows upgrade) to no avail, and decided that the whole system needed rebuilding. Rather dejected, we searched the internet once more for possible solutions (this time under the heading "slow printing from Photoshop Epson" - although it was not the printing per se that was slow, just the loading of the file).
This is the fix that we found: http://www.luminous-landscape.com/forum/index.php?action=printpage;topic=48960.0
The relevant text from the forum (in case the link doesnt work) is:
"I spoke with both Photoshop and Epson support guys and was able to come up with a fix (from Epson). The fix involved deleting a hidden file in a hidden folder called Program Data on the C:\ drive. The file had an extension of .AUD and was 40 megabytes in size. It was the only file with the .aud extension. Once I deleted that file, all of my problems went away. The Epson support guy said that this file has caused problems in the past. He thinks that the file is generated by the system and just keeps getting larger and larger until everything grinds to a halt. To access hidden folders in Windows Explorer, click on the Tools tab, click on Folder options, click on View. Under the heading "Hidden Folders and files" click on "Show Hidden Folders and files". You will then be able to access the folder "Program Data". In the folder called "Program Data" you will find a folder titled "Epson". In the Epson folder is a folder called "Printer". In the printer folder is the file (In my case anyway) called "EPAUDF01.AUD. When I deleted the file (that had swollen to 40 megabytes), the system (or the Epson Printer program... I'm not sure which), generated a new file that was 2 kilobytes in size, after I had restarted my machine. I keep monitoring the file to see if it changes size, but so far it hasn't."
Having deleted the file *.AUD, Photoshop loaded images as fast as lightning.
Thought this would be of use to you all, and thank you once again.
Lizzie

Dreamweaver CS5 Slow to Open File... Enable Related Files

Hello,
I have a page that uses the Fancybox script and it takes Dreamweaver 50 seconds to open this page.
This script requires jQuery, so in the head of my page I have this:
<script type="text/javascript" src="http://code.jquery.com/jquery-1.4.2.min.js"></script>
If I comment that line out, the page opens immediately. Also, if I disable "Enable Related Files", the page opens immediately... neither option is a good one of course.
It's my guess that dreamweaver is retrieving and parsing the remote jQuery file which is what is slowing things down. How to I stop dreamweaver from going after remote files???
I was hoping setting "Discover Dynacially-Related Files" to "Disabled" would do the trick, but trying that has led me to another problem that I posted in a different topic which is that Dreamweaver won't save the selection for "Discover Dynamically-Related Files". That option always returns to "Manually".
Any ideas how to stop dreamweaver from retrieving remote files?
Thanks!
Peter

Im on a mac with CS5 and I have started getting an issue with one of my sites where it is slow to open the files. I tried following the steps in the article you attached here but I can not find that preference file at /Users/Your User Name/Library/Preferences. In fact, I don't have a library under /users/my name.
I can open files fine on a different site, but for some reason just this one is giving me trouble.

Mac Dreamweaver CS6 very slow to open files

Hi
My Mac Dreamweaver CS6 opens html files in about 1-2 minutes! It is very very slow. It all works when the file is open but it is the actual opening that is slow.
I have turned off external files but no change.
Any ideas??
Thanks
Mac Pro
Processor 2 x 2.8 GHz Quad-Core Intel Xeon
Memory 4 GB 800 MHz DDR2 FB-DIMM
Graphics ATI Radeon HD 2600 XT 256 MB
Software Mac OS X Lion 10.7.4 (11E53)

I've been strugling with this issue for a long time.
I've found that Dreamweaver takes about 2 minutes to open CSS files with @import url for font face.
for example:
@import url(http://fonts.googleapis.com/css?family=Oswald:400,300);
i've never had problem with big files but if i place this line into my 20k css file, it takes for ever to load.
if i remove it, it opens fast as usual.
Please don't tell me that it could be a Google problem thatis loading slow because it's not.
the font file isnt big enough either.
Of course i have deativated the "load things from external urls" setting.
any ideas on how could this be fixed withoput changing my work style ?

Slow opening files

Hi,
I recently a user's PC. They went to a Windows 7 64bit 12GB RAM, 1 x SSD drive and 1 x SATA. They have been upgraded from Photoshop 7 to PhotoShop CS5. The user is complained that opening files from the network is slower than it was with PS7. I did a comaprision and there is a difference in the speed with which files apepar in the Window in CS5. I have now had to put a version of PhotoShop 7 back on her PC to appease her but her point is correct. PS7 displays files quicker than CS5. Is there anything that can improve the speed with which files are displayed?
I have had a read and applied as many of the settings as are relevant from this article on optimizing performance but it hasn't changed things.
Thanks,
Dermot.

I have done some more research.
The original complaint was that CS5 was comapred to PS7.1. That comparison however was between two different machines. I checked and the slow machine (the new one with the spec in the original post) was using a 100mb network connection whereas the other was on 1GB. I re-patched the slow machine so it was operating at 1gb also. I thought that was the end of it but no!
I had already installed PS7.1 on the slow machine so I did a comparision. I took 10 jpeg whose disk size was between 200kb and 800kb (about 2mb un-compressed). I opened them in CS5 and they took between 8-9 seconds from draging into CS5 to fully rendered. I then did the same on the installed version of PS7. It too 2-3 seconds. These files were from a network share. There may be some improvement with PS7 due to disk caching somewhere.
The graphics card is an Nvidia Quardo 600 1GB DDR3. There is no direct option to disable OpenGL. In the Display options/Nvidia Control Panel you can control global and specific program graphics options. You can modify graphics options for PhotoShop CS (which incidently is called CS4). The options where Quardo or Global. I have set it to Quadro for now I am not sure that the graphics card is the issue but I'm happy to change any settings if they will have a bearing.
Does anyone have any other suggestions I can try?
Thanks,
Dp.

Fix for slow opening files... soon?

We have several stations set up globally in various offices using Photoshop CS...
Image files, no matter how small the file is... even a single small JPG takes a good 10-15 seconds to open (win xp) and we frequently need to work with hundreds of images. This seems to be a major problem and from what I find on Google, not uncommon...
I finally ran into this temporary 'fix' in the archives which involves setting up a LOCAL printer/driver as a DEFAULT...
While that DID alleviate that problem, I can't see that adobe is just letting this be THE fix for the problem... I've done updates to our CS3 products and have a difficult time believing that there is no permanent fix for this yet.
It seems unlike adobe to expect so many clients to have to experience this problem, spending hours or days trying to figure out why their systems have slowed down and asking themselves questions mostly unrelated to the problem, such as 'did i run out of swap space on my drive?', 'how are my history/cache settings?', 'is there some network drive causing the problem?', 'Is there some spyware slowing my box?', etc...
And on top of that having to notify all the offices... 'Okay guys, if you use photoshop you need to do this, this, and that... temporarily'
Please tell me there is a permanent fix soon...

I don't know which versions of photoshop need to check/contact the network printer...
For volumes of image processing via the batch commands I often need to use our old Photoshop 6 which, even with the network (a fairly large corporate network) the files open up almost instantly... every time... unless they're huge print resolution images...
On the same network for such a task (batching hundreds of images) PS CS3 is unuseable to us unless we implement the local printer 'fix'... and even so, there is more of a delay than with our old photoshop...
And why does it need to contact the printer for each file that is opened? For the first one, sure... check it, done... I'm not printing dammit, just opening files.
If it needs printer information the local OS already has drivers loaded up, couldn't it check those? It shouldn't have to look for other network devices on there unless it's using them... but I'm no tech... so there must be a reason that it simply MUST do it...
And even so... why is this 'fix' so damn hard to find on the net? Tons of people with issues and a lone, difficult-to-find blurb as an obscure fix...?

Opening files is SLOW

Similar Messages

Maybe you are looking for