Photoshop CS4 : Printer name too long problem

hi,
we have a special problem only in Photoshop CS4 when we want to print here.
When students wants to print their document on one of our printer, Photoshop is not keeping the printer selected correctly.
When we go in File --> Print...
The page "Imprimer" open and I select the printer : RN-CORRIDOR-D306-COULEUR(PS)
the (PS) is for the PostScript Driver.
then if we click on "Mise en page" (Page Setup) you see the name of the printer is now : RN-CORRIDOR-D306-COULEUR
this printer is the one with PCL driver.
I have these 2 printers installed on my computer. If I remove the PCL one, everything works correctly.
I have made some testing and I found that if the printer has more thant 30 character for the name identical with another one, it will switch to the printer above in the list in photoshop.
the name of these printers are in fact : \\sprint1\RN-CORRIDOR-D306-COULEUR and \\sprint1\RN-CORRIDOR-D306-COULEUR(PS)
and they appear like this in the listing :
\\sprint1\RN-CORRIDOR-D306-COULEUR
\\sprint1\RN-CORRIDOR-D306-COULEUR(PS)
So if I choose the PCL one, everything works fine, but if I choose the PostScript one, it will switch on the PCL driver. (it is impossible to print on the PS)
Another test I made :
Create 2 printer locally on my computer with 2 names with 30 character identical and 1 different at the end, 2 completely different driver (HP 4050PCL and Lexmark OptraS1650PCL) on 2 different ports: same results, it swith to the first printer in the listing.
As I said, this is the only application that have this problem. Any other Adobe application or MS Office is working for now 3 years with these printers with more than 30 character in the name. And we can't change the name as they are installed on over 100 computers.
Did someone ever saw this ?
Thanks
Benoit

these printer are installed on our lab computer with more than 100 softwares installed.
the only application having this problem is Photoshop CS4.
Illustrator CS4 for exemple is correct, last version of Acrobat Pro too.
Photoshop CS3 was ok before...

Similar Messages

Photoshop CS4 layers palette too wide problem!

http://img232.imageshack.us/img232/6828/swatchesld2.jpg
The Photoshop CS4 layers palette is too wide and distorts the layout of the default color swatches palette when docked on the same column. And I don't want to have to put the color swatches palette anywhere else but the same column. Can the layers palette be fixed so that it can be as narrow as the other palettes, so it won't cause a conflict with the swatches layout?

As for the rescalability of panels I think this is more of a Windows issue, but even on mac these are nowhere near as well designed as they were.
Panel and UI design issues are now unfortunately more complex than just to do with Photoshop. The whole Creative Suite is now unified to some extent in the way it handles panels. Part of these problems stem from the fact that Indesign and Illustrator's concerns are quite different to those of Photoshop. Partly because the designers of these two applications have introduced a great swaithe of additional panels, which now need to be accomodated. Hence the panel buttons, and poorly docking panels.
The design of The Creative Suite interface now seems much more influenced by Flash Web design, and Windows OS. Unfortunately with flashing buttons, icons, and distracting transparency whenever you move anything, Photoshop appears on the surface much more complex than it needs to. This surface complexity will lead to further misguided accusations of "bloat".
Photoshop CS and CS2 in my humble opinion, had much more "solid" and well designed panel (or palette) interfaces. Although here and there there have been one or two useful additions to the overall UI, including more readily accessible workspaces, tiling, and obvious clickable icons for people who can't deal with keyboard shortcuts.

File name too long cannot copy (cont'd)

This is a continuation of the post started September 01, 2009, with the last post on
October 17, 2011 named File name too long cannot copy
Since this is an ongoing unsolved issue, and the thread was locked, it continues here.
It is ever so easy to create a long file/path using explorer.exe as will be shown below.
What needs to be solved is, what is an easy way (no, not by listing out all the files in a directory to a text file and counting characters), perhaps using a shell extension, to find out which files in a directory and it's subdirectories will be (or were)
too long to copy, (and then perhaps even copying those over either intact or renamed)?
Maflagulator said:
I'm running the 7100 build...enjoying it except for one big thing:
While attempting to copy 402gb from my main storage volume onto a spare 500gb drive (for the purpose of changing to a new RAID array) I've come across something that I would expect a Windows 98 OS to give me.
It tells me that a file has TOO LONG of a file name, then provides with two unhelpful options: SKIP or CANCEL
I never had XP give me an issue like this at all, so what gives? And while some specific files did have long file names (such as for songs, etc.) it had 7 issues with folders stating that their name was too long, but in fact they were not since they were
titled '07-06-07' for the date that I dumped the audio files in them. However, they may have contained FILES with long file names though.
Anyone else get this same situation? Perhaps the RTM version does not do this? Can anyone verify this regarding their install of the RC or the RTM?
It made it through 400gb out of the 402gb transfer.
I'm just happy to see that it doesn't spazz out about an issue like this until it has done all the other transfers that it can do because it saves the issues it has with files until the very end. In XP it would spazz about it the moment it came across it
causing the transfer process to halt.
Since long path/file names can so easily be created on Win7, it might be useful to see a typical way this happens, which might then give clues how to work with them.
In Windows Vista, we learnt from:
File names and file name extensions: frequently asked questions that:
Windows usually limits file names to 260 characters. But the file name must actually be shorter than that, since the complete path (such as C:\Program Files\filename.txt) is included in this character count.
In Windows 7, we are told here:
File names and file name extensions: frequently asked questions that:
It depends on the length of the complete path to the file (such as C:\Program Files\filename.txt). Windows limits a single path to 260 characters. This is why you might occasionally get an error when copying a file with a very long file name to a location
that has a longer path than the file's original location.
From the Windows Dev Center - Desktop, we read about Maximum Path Length Limitation here:
Naming Files, Paths, and Namespaces
This helps us understand why a folder can be a maximum of 244 characters, from the defined 260 length of MAX_PATH as follows:
260 minus C:\ (3) minus <NUL> (1) = 256
256 minus 8.3 file name (12) = 244
We also learn there that: The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters.
And we read the claim that: The shell and the file system have different requirements. It is possible to create a path with the Windows API that the shell user interface is not be able to interpret properly.
There is also a comment below this document that reads: In a previous iteration of this document, it is mentioned that The Unicode versions of several functions permit a maximum path length of approximately 32,000 characters composed of components up to
255 characters in length. This information is now gone.
So we are in a position where the file system and Windows API can create long path/flies that the shell cannot handle.
But then we need to be able to handle it, so a little exploration might lead to a better understanding of how to do this.
For most tasks being performed on long folder/files, Windows 7 and other Windows programs balk when the Path+Filename length > 260
Let's create a long path/file.
Create a folder called A at the root of a Drive.
Create a sub-folder of A called: B
Create a sub-folder of B called: C
Make a FILE in sub-folder C called (no spaces or break, one long continuous string): 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T
123456789U123456789V123456789W123456789X123456.txt
Rename sub-folder C to the string (no spaces or break, one long continuous string) (The actual directory created will be slightly shorter than this full length): 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J
123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X123456789Y123456789Z
Rename sub-folder B to the same full string above. (The actual directory created will be slightly shorter than this full length but 2 characters longer than the step above.)
Rename folder A to that same full original string. (Again the actual directory created will be slightly shorter than this full length but 2 characters longer than the step above.)
You now have the lovely file placed at (the breaks are just so it fits into the screen):
C:\123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X1234\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J
123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X12\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T
123456789U123456789V123456789W123456789X\ 123456789A123456789B123456789C123456789D123456789E123456789F123456789G123456789H123456789I123456789J 123456789K123456789L123456789M123456789N123456789O123456789P123456789Q123456789R123456789S123456789T 123456789U123456789V123456789W123456789X123456.txt
You have a folder length of over 700 and a file length of over 250 for a total of over 950
However you will notice that each folder, when created, could only be a maximum of 247 charachters including the path (example C:\ , & C:\A , & C:\A\B
This only applies backwards, that is up the path. It did not matter what was further down the path.
Now, you can't easily access or rename the file, but you can rename the folders easily.
For best results, start renaming from the top of the Tree, working down the subfolders, because renaming from down up will limit you, and in fact won't work if the folder lengths are too long.
So how might knowing this help us?
Well, to copy this long_file from the C:\ drive to the D:\ drive, and keeping the path structure, this should work:
Note the name of the top folder. Rename it to something very short, say: A (Make sure C:\A does not exist)
Note the name of the 2nd folder. Rename it to something very short, say: B (Make sure C:\A\B does not exist)
Note the name of the 3rd folder. Rename it to something very short, say: C (Make sure C:\A\B\C does not exist)
Make sure D:\A does not exist - then copy the A folder on disk C: to disk D: (which gives you D:\A\B\C\long_file
Rename D:\A\B\C to D:\A\B\Original_3rd_Folder_name
Rename D:\A\B to D:\A\B\Original_2nd_Folder_name
Rename D:\A to D:\Original_top_Folder_name
Rename C:\A\B\C back to their original names, in this same reverse order starting with C, then B, then A
Note: If using Explorer, at some points you might have to press the F5 refresh key.
This is of course how you might copy such long path/files without using the other more "easy" techniques for the "normal" everyday user like:
sharing a sub-folder
using the commandline to assign a drive letter by means of SUBST
using AddConnectionunder VB to assign a drive letter to a path
using the "\\?\" prefix to a path string to tell the Windows APIs to disable all string parsing and to send the string that follows it straight to the file system
and so on.
See how simple Windows can be for Dummies!
But then, how can we know that files to be copied exceed this MAX_PATH? Or also after a copy has taken place, know exactly which files that have NOT been copied because of exceeding the MAX_PATH limit, and then a procedure to copy these either by renaming
them, or by copying them intact as they are?
There have been suggestions to use
LongPathTool, but this does not have a facility to check a series of folders and tell you which files are going to be caught by the error when copying. So once a copy has taken place using Windows 7, one does not know which files did not get copied, and
where exactly they are located.
Neither does the free
Old Path Scanner do that. It can only check for overly long directory paths, but misses out when the directory path is within limits, but adding in the file name puts it out of bounds.
So, as shown above, it is ever so easy to create a long file/path using explorer.exe
So, what then is an easy way (no, not by listing out all the files in a directory to a text file and counting characters), perhaps using a shell extension, to find out which files in a directory and it's subdirectories will be (or were) too long to copy,
(and then perhaps even copying those over either intact or renamed)?

This is a not a "solution" ....but a "work around": a low tech fix....for error message "your file name is too long to be copied, deleted, renamed, moved" :
1.   problem is this: the "file name" has a limit on number of characters.....the sum of characters really includes the entire path name; you gotta shorten it first (i.e, if the total number of characters in the file name + Path name are over the
limit, the error appears). The deeper your file folder sub levels are, the more this problem will come up, especially when you copy to a subfolder of a subfolder/subfolder of another path ...adds to character limit)
2. How do you know which combined file names + path names are too long if you are in the middle of a copy operation and this error pops up? Some files copied but the "long files error message" says "skip" or "cancel" ... but not which
files are the "too long" ones. If you hit "skip" or "cancel" the "too long" files are left behind...but are mixed in with non-offender "good" "short name" files.   Sorting thru 1000s of "good" files to find a few "bad" ones manually is impractical.
3.   Here's how you sort out the "bad" from the "good":
4.    Let's say you want to copy a folder ..."Football" ...that has five layers of subfolders; each subfolder contains numerous files:
C:/1 Football / 2 teams/ 3 players/ 4 stats/ 5 injuriessidelineplayerstoolong
       There are five levels root "1 football" with subfolders 2, 3, 4 and lastly "5 injuries"
5.    Use "cut" and "paste" (for example to backup all five levels to a new backup folder):
       select "1 football" ....cut....select target folder....paste
       ("cut" command means as the files are copied to the target destination, the file is deleted from the source location)
      Hint: avoid "cut" and "paste" to a target folder that is itself a sub/sub/sub folder ...that compounds the "characters over the limit" problem ...because the characters in the sub/sub/sub folder are included in the "file name
character limit"...instead "paste" to a C:/ root directory.
       Suppose in the middle of this operation...error pops up: "5 files have file names that are too long" Skip or cancel?
       select "skip" ...and let operation finish
6.    Now go back and look at the source location: since the software allows only the "good" "short name" files to be copied (and because you "skipped" the "bad" "Long name" files so they are not copied or deleted) ...all that remains
in the source location are the "bad" "long name files" (because "good" ones were deleted from the source location after the "cut" operation...the bad ones stick out like a sore thumb.
7.   You will find ....all that remains in source folders are: the "bad" "too long" files; in this example the "bad" file is in level 5:
      C:/ 1 football / 2 teams /3 players /4 stats /5 injuriessidelineplayerstoolong
8.   select folder 5 injuriessidelineplayerstoolong (that's right...select folder, not file) gotta rename the folder first.
9. hit F2 rename folder..folder name highlighted...delete some of the letters in the folder name:
       like this:   5 injuriessidelineplayers ....you should delete 'toolong'....from the folder name
10. then go into folder 5....and do the same operation ...with the too long file name:
        hit F2 rename file....file name hightlighted...delete some of the letters
           like this: injuriessidelineplayers.....you should delete 'toolong' from the file name
11. Now..."cut and paste" the renamed file to the target backup folder.
The Error message will pop up again if you missed any "bad" files....for example, it will indicate "5 files too long" ....then repeat process 5 times until you fix all of them
12.    Finally, copy the target destination files back to the source location (when you are certain all source location file folder locations are empty)
Of course, this "makeshift" solution would not be necessary if MSFT would fix the problem...

Disk Utility (10.5.6) error: File name too long

Hello, here is one for you all...
I am in the midst of creating a new "build image" so I can start deploying Leopard.
Before I upgraded the build to 10.5.6 I was able to create a disk image of this build machine.
After updating it to 10.5.6 and all of the current Apple updates I am no long able to create a disk image.
I keep getting an error several minutes into the imaging process that says +"*File name too long".*+
I've run permission repair on the disk and Disk Warrior with still no luck. I've also used different machines and a boot FireWire drive to make he image and still have had no luck. I can use CCC to clone my Master build to another machine but I need to be able to make an image of it.
Thanks in advance for any help.

Bear in mind that in Unix, a file name includes the path, so if you have a very deep file or perhaps some kind of infinite recursive link, that might cause the problem, since that would make the file name very long indeed.
This may not be the problem you are having, but it just came to my mind when I read your post

"Maximum number of application files exceeded or file names too long"...help!!!

Hi there…
I am trying to create a game for my mobile.
The “problem” is that I have more than 500 swfs that I want to pack using the Adobe Mobile Packager. And I am getting this error:
“Maximum number of application files exceeded or file names too long”
How could I solve this problem?
Thanks everyone!
Cheers.
Leo.

500?? What are there so many files?
The problem is that the CAB format only allows for 300 files maximum, so there's nothing that we can do about that I'm afraid.
Mark
www.flashmobileblog.com

File communication channel issue : object name too long

Hi Experts,
My requirement is to place the successful files in folder and un-successful files in one folder after processing.
we used parameterized mapping to achieve this requirement.
I'm facing below issues, please help me to resolve.
" An error occurred while connecting to the FTP server. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 501 Unexpected reply codeSpecified object name too long, limit is 10 characters: $Filepath_Su.'. For details, contact your FTP server vendor.
As per my understanding it is not taking the path specified,because of length issue.
Please send me your valuable inputs and help me.
Thanks in advance for your help.
Regards
Bhargava Krishna

Hello,
By loking ur error description, it's quite evident that it's a FTP sever issue?
Sometime on FTP server, there is a check which is enabled to limit the length of file names, and i think the same has been recently implemented on ur FTP server. So instead of changing ur config, check with ur FTP admin.
Tested the same after tweaking existing FTP server settings.
Thanks
Amit Srivastava

Trying to install Illustrator cs3, during the installation I am asked for photoshop cs4 disk I no longer have the photoshop cs4 disk

Trying to install Illustrator cs3, during the installation I am asked for photoshop cs4 disk I no longer have the photoshop cs4 disk

Do you own Illustrator CS3? An older version should not only not be asking you to utilize a newer version in any way, it couldn't even know about the existence of it.

Photoshop CS4 printer driver

I installed the Photoshop CS4 printer driver (ipf6100) that I downloaded from Canon's website. When I chose export and choose the ipf6100 it gives me the error message
"Could not complete the export command because of a program error". How do I get the plugin working.

I am not understanding what your trying to do or the steps. When you install the plug in your saying there should be your printer listed in PS CS4 Export as a option to choose from? Do you have a 64 bit OS? If so my guess is that it is only a 32 bit plugin option and maybe you installed it in the 64 bit plug in folder? Or the opposite?

JAXB: Error compiling classes generated by xjc (file name too long)

Hi friends,
I am trying to compile classes that are generated by using XJC tool on xsd file. The compilation fails with following message.
buildxsdmodel:
    [javac] Compiling 794 source files to /home/uchamad/working/teleworker/ejb/build/classes
    [javac] /home/uchamad/working/teleworker/ejb/build/tmpsrc/uk/co/novatel/teleworker/model/wlr/bulksearch
results/impl/ApplicationInformationTypeImpl.java:58372: error while writing
uk.co.novatel.teleworker.model.wlr.bulksearchresults.impl.ApplicationInformationTypeImpl.XMLRequestID
TypeImpl.SearchOrderResultsTypeImpl.SearchTypeDetailTypeImpl.OrderTypeImpl.OrderDetailsTypeImpl.
OrderLinesTypeImpl.NumberPortingTypeImpl.OLODetailsTypeImpl.NumberLocationTypeImpl.OLOMainP
STN1AddressTypeImpl.Unmarshaller: /home/uchamad/working/teleworker/ejb/build/classes/uk/co/novatel
/teleworker/model/wlr/bulksearchresults/impl/ApplicationInformationTypeImpl$XMLRequestIDTypeImpl$S
earchOrderResultsTypeImpl$SearchTypeDetailTypeImpl$OrderTypeImpl$OrderDetailsTypeImpl$OrderLin
esTypeImpl$NumberPortingTypeImpl$OLODetailsTypeImpl$NumberLocationTypeImpl$OLOMainPSTN1A
ddressTypeImpl$Unmarshaller.class (File name too long)
    [javac]                                             public class Unmarshaller
    [javac]                                                    ^
    [javac] 1 error
The compiler is complaining about the file name being too long. This is happening because the java classes when generated from XSD contains deep nesting of inner classes. So when it comes to compile the .class name file is too long for the operating system.
I am trying this on unix box.
I wonder if there is a way to configure XJC so that it does not produce inner classes but instead keep them out.
Any help would be appreciated.
many thanks
Usmangani

Flattening your schema definition will flatten the output files, too -- that will probably be nice for coding as well since you wont have to use class names such as SomeTypeNestedInAnotherTypeThatHasYetAnotherType. Instead of having all of the elements defined directly within the enclosing root element, define logical chunks at the top level and incorporate them in the definition of real root element of your documents by reference.

OS Yosemite/Photoshop CS4/Printer Problem

I recently upgraded to OS 10.10, Yosemite. I can no longer get accurate colors printed for photos from Photoshop. I have Photoshop CS4 and I use an Epson Stylus Photo R2400 printer. I am able to use Photoshop for everything but printing accurately. I downloaded all recommended drivers for the printer, reloaded profiles for the printer and even tried a trial of Photoshop CC. Nothing resolves the problem. My prints look kind of solarized. Black and white photos have green areas where there should be black. Please help.

Yosemite introduced a number of serious bugs that Apple has not fixed yet.
Some Yosemite users have been advised to downgrade to Mavericks.

Photoshop CS4 printing everything in dots???

My Photoshop CS4 has been running fine and then this past week I printed a document I created and the whole thing came out as a series of small dots...including the fonts. Also, I tried printing various high resolution stock photos that have printed fine from Photoshop in the past, and they all came out dotted too.
The document I created was 8.5 x 11, 300 dpi, CMYK. In order to determine if the problem was my printer, I saved the file as a .jpg and opened it in Windows Picture & Fax Viewer. I printed the document from that program and I got a great print...no dots! So it seems it has something to do with Photoshop and I am clueless. I haven't changed any of the prefs or settings, so I'm not sure what is going on.
Does anyone know what might be happening? I appreciate any wisdom or insight, as I have none!

From your Photoshop Print dialog (i.e., the window that opens when you choose File - Print), press the Print Settings button.
Ensure all your printer settings, including those in Advanced sections, are set to your preferences. Chances are something's set to "Draft" mode or to a minimal dot pitch.
You don't need to actually print something to get these settings to "stick". Just press the Done button.
-Noel

Receiving ERROR meassage when trying to copy..file name too long.

Hello.
There is an error code number, but didn't write it down...will do so, if no-one can answer this question at the minute. I am not at the Mac at the moment, so this post is pre-emptive.
Problem:
If I try to copy over a folder with photoshop images onto another drive, the copy is incomplete due to the name/s of the files being too long, apparently.
The error message says something to the effect: 'the names are too long can't complete copy'.
The file names are about 10-12 [at most]characters in length.
Please advise
Chris

If the drive is formatted HFS then you are limited to 32 characters on a file name. If it is formatted HFS + then you can have file names as long as 255 characters. I am not familiar withi the format you say the drive is formatted in so I can't speak to it.
If you are receiving -50 errors that can indicate a file name that is too long OR an illegal character in the filename regardless of its length.
If you are actually using 10.3.8 as your profile states then that may be part of the problem. Many of these problems existed in 10.3.X but were fixed in 10.4
I remember that 10.3.8 had issues copying to external drives when there were more than a certain number of characters in a filename. I don't remember the number but for some reason 10 or 12 is what comes to mind. It caused me many problems when I would try and copy files to a Zip disk that I used to have. Since I updated to 10.4 those issues have never occured again.
Since you know what folder the problematic files are in why not just open the folder and try to copy files one at a time. When you get to the one(s) that is a problem, change the file name to something shorter.
A better solution would be to update to 10.4 but with 10.5 coming out sometime in the Spring of 2007 this may not be the time.

Photoshop CS4 Trial Bugs - Eraser & Text problems

Hows everybody doing...I recently downloaded the Photoshop CS4 Extended Trial and installed it on my computer...I am noticing some bugs and im not really sure if its just a bug in the trial version which will be fixed when i buy the program or if there was an error with the install...
I dont have screenshots at the moment since im not on the computer having the issue but i can get them if needed...
First lets start with the eraser tool...When i set the eraser tool as a size of say about 10px it works fine...However, if i zoom in on the image above its nautral size i start to lose the eraser...When i say lose the eraser i mean you can no longer seen the round area which will be erased..When you zoom in part of the circle disappears...It will still erase and area of the set size but its sort of hard to do erasing on detailed images when you cant see the whole eraser....
More bugs with the eraser....If i set the eraser to a larger size, say 30px or more, i right off the bat start seeing less of the eraser area....It will go from a whole circle down to something like a half moon with only half the circle being displayed...
This may be a little hard to understand so if need be i will get some screenshots of what im talking about later....
I am also having a problem with the text...For starters, i cant scroll through the text...When i enter text and highlight it and highlight the fonts i would expect to be able to scroll through the fonts while watching the actual text change on thet screen....I am unable to do that, i highlight the text and the fonts and CS4 will let me scroll maybe 4-5 fonts and then it just stops and wont scroll anymore...
Another issue im having with the font is the size....Whenever i enter text it is extremely small...Even if im working with a 200px x 200px image if i set my font at say 75px its tiny, tiny enough to where i cant even see it to highlight it....There appears to be something wrong with the sizing of the text...Just to get text to show up normally, at a readable size, i have to set the font size to 800px+ and this is on images which are only like 600px wide and 300px tall...Usually a font of 800px would fill up this image but when i do it the 800px font shows up like a 36px font...
Like i said if this is all to hard to understand i can get some screen shots later on...I wanna make sure this is something which can be fixed before i go ahead and drop 700+ on the program...

Yes i installed the patch...That was the first thing i did, before checking the video driver...The patch didnt fix any of the problems im having...The video driver update did however fix the eraser/brush issue...
I did what you said in post #1 about un-checking the option listed....When i did that nothing changed for me....
I have some more details about the scrolling issue though....From what i am able to find it seems that if i just enter digits i am able to scroll through the entire list of fonts and see a live preview of every single one....
With any sort of text it will only allow me to scroll through 5-6 fonts...You can see that it wants to scroll more when i hold the arrow down cause you can see the blue hightlight flashing and the words trying to change but it just wont go any further...At times when i hold the arrow down to scroll through the fonts it will scroll through 5-6 and then all of a sudden just go white and wont let me scroll up or not...At that point i have to select the font list and pick a font

Consolidating Library Error: File Name Too Long, But What File?

I am trying to consolidate my library to put all my music (very unorganized) in one spot so I can back it all up. When I try to consolidate, it takes a second to prepare, then immediately brings up an error window saying "Copying Music Failed. The file name was invalid or too long."
How do I fix this? I really would like to back up my music!

Hi, ZeroGravity107.
This can be a tricky problem to figure out since iTunes doesn't specify what file name is "invalid or too long" and there's no documentation on what determines if a file name is "invalid or too long".
We had one user report that he was able to use his/her keen eyesight to note the last file that appeared before the error message appeared and it turned out that file was the cause of his/her trouble.
If your eyesight isn't that keen, I'd suggest concentrating on the file name being too long possibility.
The entire directory path leading to the file is considered part of the file name so, as an example, iTunes' default settings might place a particular file at C:\Documents and Settings\ user name \My Documents\My Music\iTunes\iTunes Music\artist folder\album folder\whatever.m4a.
Is the directory path leading to your consolidated location much longer than that?
polydorus has suggested a way to look over your file names: Assuming your music is currently in the default location, make your way there with Windows Explorer and select List in the View menu menu and see if anything stands out as being unusual.

Can't access files with names too long

I have some files on a Windows formatted external hard drive that have filenames that seem to be too long for OS X to handle. I can't open them, nor can I delete them. I can't even seem to "rm" them from the command line. I know they're there, and not just some bitwise mirage. Does anyone have any way to deal with these files (they're 0 bytes long, as far as the Finder is concerned, and if you click on them, they disappear)?

MacOS X supports file names of 256 characters (or is it 255?). Are your files names longer then that? If not, then I would suspect the problem is somewhere else, probably permissions.
When you try to rm the file, does it produce an error? If so, what is it?

Photoshop CS4 : Printer name too long problem

Similar Messages

Maybe you are looking for