Strange Finder Behavior

Hi every one!
I have a folder with 2101 pictures in it.
In list view, everything is fine.
But in thumbnail view, right-clicking on any file past the 912th file and up to the 1820th file in the folder, I get folder information instead of file information, and from the 1821st files to the last file in the folder, I get file information from the first file in the folder and so on in the right click menu.
Is this a known limitation or bug, or have I serious problem here?
Thanks in advance for any thoughs or solutions you might have.
Dan
2.1GHz 20" iMac G5 (iSight) 1.5GB 250GB HD Mac OS X (10.4.6) / 300MHz iBook (clam) 3G 288MB OS X (10.2.8) / 1GHz PIII 1GB 170GB HDs XP SP2

Hi bitman, your question really doesn't relate to this thread. You should post a new topic here. top of the page, on the left.
But while you're here try this:
Navigate to ~(yourhome)/library/preferences and trash these two files:
com.apple.finder.plist
com.apple.sidebarlists.plist
Then log out and back in again. Or restart.
(You will have to reset a few finder prefs the way you like them.)
If this doesn't help then post the new topic.
-mj
[email protected]

Similar Messages

Bug in my code or strange memory behavior ?

Hi, Guys !
It's been a while since I post something in this forum - trying to use your help when it's really needed.
So, here we go ...
(we use Oracle 8.1.7 on Unix box and SQL * Plus 8.1.6)
While back I wrote "core" PL/SQL package that resides in let's say DB1 database. It has RECORD_EXISTS_FNC function designed to dynamically check If the record exists in certain table/view. Assumptions are that you pass in :
Table/View name, Column name, and unique numeric value (because by DBA rules all of our Tables have SEQUENCE as a Primary Key. And I plan soon to put in overloaded function to accept unique character value)
Also every Table has SYS_TIME_STAMP and SYS_UPDATE_SEQuence columns that populated by Trigger before Insert/Update representing Last Update time_stamp
and how many times record was updated within same second.
(in case more than one User updates same record in same time - that was written before Oracle had more granular date/time). So function has SYS_TIME_STAMP and SYS_UPDATE_SEQUENCE parameters (optional) accordingly.
And It looks something like :
FUNCTION RECORD_EXISTS_FNC
(iBV_NAME IN USER_VIEWS.VIEW_NAME%TYPE,
iPK_FIELD IN USER_TAB_COLUMNS.COLUMN_NAME%TYPE,
iPK_VALUE IN NUMBER,
iSYS_TIME_STAMP IN DATE DEFAULT NULL,
iSYS_UPDATE_SEQ IN NUMBER DEFAULT NULL) RETURN BOOLEAN IS
TYPE REF_CUR IS REF CURSOR;
CR REF_CUR;
i PLS_INTEGER DEFAULT 0;
vRESULT BOOLEAN DEFAULT FALSE;
vQUERY USER_SOURCE.TEXT%TYPE;
BEGIN
vQUERY := 'SELECT 1 FROM ' || iBV_NAME || ' WHERE ' || iPK_FIELD || ' = ' || iPK_VALUE;
IF iSYS_TIME_STAMP IS NOT NULL AND iSYS_UPDATE_SEQ IS NOT NULL THEN
vQUERY := vQUERY || ' AND SYS_TIME_STAMP = TO_DATE (''' || iSYS_TIME_STAMP || ''')
AND SYS_UPDATE_SEQ = ' || iSYS_UPDATE_SEQ;
END IF;
IF iBV_NAME IS NOT NULL AND
iPK_FIELD IS NOT NULL AND
iPK_VALUE IS NOT NULL THEN
OPEN CR FOR vQUERY;
FETCH CR INTO i;
vRESULT := CR%FOUND;
CLOSE CR;
END IF;
RETURN vRESULT;
EXCEPTION
WHEN OTHERS THEN
IF CR%ISOPEN THEN
CLOSE CR;
END IF;
INSERT_ERROR_LOG_PRC ('CORE_PKG', 'ORACLE', SQLCODE, SQLERRM, 'RECORD_EXISTS_FNC');
RETURN vRESULT;
END RECORD_EXISTS_FNC;
So the problem is when I call this function from let's say
database DB2 (via db remote link and synonym) and I know exactly that record does exists (because I am selecting those SYS fields before pass them in) - I get the correct result TRUE. The other programmer (Patrick) calls this function within same DB2 database, within same UserID/password (obviously different session), running exactly the same testing code and gets result FALSE (record doesn't exist, but it does !) He tried to Logoff/Login again several times within several days and try to run it and still was getting FALSE !
I tried to Logoff/Login again and I was getting mostly TRUE and sometimes FALSE too !!!
I thought may be It has something to do with REF CURSOR that I use to build SQL on the fly, so I changed to NDS
using EXECUTE IMMEDIATE statement - nothing changed.
vQUERY := 'SELECT COUNT (1) FROM ' || iBV_NAME || ' WHERE ' || iPK_FIELD || ' = ' || iPK_VALUE;
IF iSYS_TIME_STAMP IS NOT NULL AND iSYS_UPDATE_SEQ IS NOT NULL THEN
vQUERY := vQUERY || ' AND SYS_TIME_STAMP = TO_DATE (''' || iSYS_TIME_STAMP || ''') AND SYS_UPDATE_SEQ = ' || iSYS_UPDATE_SEQ;
END IF;
EXECUTE IMMEDIATE vQUERY INTO i;
vRESULT := NOT (i = 0);
RETURN vRESULT;
Interesting note : when Patrick doesn't pass SYS parameters (Time_stamp, Update_sequence), or passes NULLs - function always finds the record ! (Statement 2 below)
May be it has to do with the way TO_DATE () function gets parsed in that dynamic SQL - I don't know ...
Here's the test code :
SET SERVEROUTPUT ON;
DECLARE
SYS_TIME DATE;
SYS_SEQ NUMBER;
bEXISTS BOOLEAN DEFAULT FALSE;
BEGIN
SELECT SYS_TIME_STAMP, SYS_UPDATE_SEQ INTO SYS_TIME, SYS_SEQ FROM LOCATION_BV WHERE PK = 1;
bEXISTS := CORE_PKG.RECORD_EXISTS_FNC ('LOCATION_BV','PK',1, SYS_TIME, SYS_SEQ); -- STATEMENT 1
--bEXISTS := CORE_PKG.RECORD_EXISTS_FNC ('LOCATION_BV','PK',1, NULL, NULL); -- STATEMENT 2
IF bEXISTS THEN
DBMS_OUTPUT.PUT_LINE ('TRUE');
ELSE
DBMS_OUTPUT.PUT_LINE ('FALSE');
END IF;
END;
I asked our DBA, he has no clue about this strange inconsistent results.
I debugged line by line, extracted that generated SQL and ran it in same account - works fine !
Does anyone knows or have clues or can help what's going on ???
I don't know If this is bug in my code or strange memory behavior ?
(Please let me know If anything unclear)
Thanx a lot for your help and time !
Steve K.

see your other thread
Bug in my code or strange memory behavior ?

Capturing DVCAM in FCP 6.0.2 and encountering strange capture behavior

I have FCP 6.0.2 and OSX 10.5.2 and QT 7.3.1. I have been capturing several DVCAM cassettes using my Sony DSR-20 deck. Although I have done this countless times before in earlier versions of FCP, I am encountering some strange repetitive behavior. I am capturing 30 minute clips one at a time. When I use batch capture it will cue the tape up properly to the in point...and then start capturing until it gets to about 10-12 minutes in, and then capture unexpectedly stops, no dialogue box, the tape rewinds and starts capturing again from the original in point. On this second capture, the tape sails past the 10 minute mark and keeps going to the end of the 30 minute clip. It then stops, gives me the dialogue box that it has successfully captured. And it has.
But every DVCAM tape I captured today exhibited the same behavior. Capture would be successful until about about 10 minutes in, then FCP aborts (no dropped frame message, no dialogue box) rewinds the tape back to the in point, tries again, and this time succeeds with the second pass capturing the entire clip. Note at the 10 minute mark there is no scene change or no camera start/stop.
Have other users experienced this issue? And if so, is there a workaround or a possible patch forthcoming from FCP?
Many thanks,
John

Yes, each tape has an in and out point defined. In my 6 years of editing with Final Cut and DVCAM tapes I've never encountered this issue before in the capturing process until now. I will have to see in future weeks with other captures whether this is an on-going issue or not, but at least I can capture for now.

Strange Permissions Behavior with Public/Private Drop Box

Strange Permissions Behavior with Non-Course Drop Box
In an effort to promote iTunes U on campus this semester (and to get people working with audio and video more) we're having a contest in which people can submit personal or group audio/video projects.
This being an iTunes promo, we intend for students to submit their contributions via a drop box.
To that end, I began experimenting with drop boxes in iTunes U, which I haven't done much of previously. I've created a course called "iTunes U Drop Box Test" under "Campus Events". Within that, I have two tabs: "Featured Submissions" and "Dropbox". My goal with this drop box was to allow faculty, students and college folks the ability to use the drop box ("college" being a role I've defined for those who don't fit into the faculty/student roles).
When I first started experimenting, access to the "iTunes U Drop Box Test" course looked like this:
--- Credentials (System) ---
Edit: Administrator@urn:mace:itunesu.com:sites:lafayette.edu
Download: Authenticated@urn:mace:itunesu.com:sites:lafayette.edu
Download: Unauthenticated@urn:mace:itunesu.com:sites:lafayette.edu
Download: All@urn:mace:itunesu.com:sites:lafayette.edu
--- Credentials ----
Download: College@urn:mace:lafayette.edu
Download: Instructor@urn:mace:lafayette.edu
Download: Instructor@urn:mace:lafayette.edu:classes:${IDENTIFIER}
Download: Student@urn:mace:lafayette.edu
Download: Student@urn:mace:lafayette.edu:classes:${IDENTIFIER}
For the "Featured" Submissions tab, I gave the non-system credentials the "download" right, and for the "Dropbox" tab I gave the non-system credentials the "dropbox" right.
My understanding of this setup is that everyone should have had the ability to view the course and the contents of the "Featured Submissions" tab and that those in the College/Instructor/Student roles would be able to upload files via the "Dropbox" tab ... but not see the contents of said tab after the files were uploaded (aside from any files they uploaded themselves).
This is not the behavior we saw however. While the College/Instructor/Student roles could upload files to the dropbox, everyone (including the unauthenticated public) was able to see all of the contents of the dropbox.
The only way I could get this to work as advertised was to change all of the system credentials save the "Administrator" to "No Access":
--- Credentials (System) ---
Edit: Administrator@urn:mace:itunesu.com:sites:lafayette.edu
No Access: Authenticated@urn:mace:itunesu.com:sites:lafayette.edu
No Access: Unauthenticated@urn:mace:itunesu.com:sites:lafayette.edu
No Access: All@urn:mace:itunesu.com:sites:lafayette.edu
Once I did this, everything worked as advertised: College/Instructor/Student roles could upload tracks, and the "Dropbox" tab would only display tracks they uploaded.
So my question is ... is this the correct behavior for the drop box? It looks like when the system credentials are in play, they're simply overriding whatever the normal "view" rule is for the drop box, which doesn't seem right.

Your current configuration where things work as you wanted does seem correct to me. You are not using any System Credentials to accomplish the functionality and that's fine.
Here's some more info to clarify how / why this is working for you and why you had to set "No Access" for the System Credentials:
The System Credential "Authenticated@..." is going to get assigned to any user that goes through your transfer script. Even if you transfer script assigns no credentials to a user, upon entering iTunes U they will have at least 1 - the "Authenticated@..." credential. Therefore, unless you block access using "No Access", any user that passes through your transfer script is going to be able to access the area in question.
When you change values for "Unauthenticated@..." or "All@..." you are defining what someone that DOES NOT pass through your transfer script can do. You want both of those to be "No Access" at the top level of your site if you do not want unauthenticated visitors.
The distinction between "Unauthenticated" and "All" is that "All" applies to all users whether they pass through the transfer script or not.
Here's another way to remember things:
User passes through your transfer script, iTunes U automatically assigns:
Authenticated@....
All@....
User does not pass through your transfer script and instead access your iTunes U site through derivable URL*, they get assigned:
Unauthenticated@....
All@....
*The derivable URL for a site is: http://deimos.apple.com/WebObjects/Core.woa/Browse/site-domain-name
Mac OS X (10.4.6)

Strange Finder behaviour since installing Mountain Lion

I've been experiencing some strange finder behaviour since updating to Mountain Lion. Folders take several seconds to open after clicking on them (and sometimes won't open at all) and files cannot be moved around the desktop or dragged on to an app. However, it is possible to open a file by clicking on it. I've tried re-booting with Snow Leopard and everything seems OK, but as soon as I go back to ML, the problem starts again.

Library is a folder, not a file. There're more than one Library folders, one at the root and one for each user in your Mac. All of them are hidden, this is why you can't find them. But you can see their contents using
Finder Menu > Go > Go to Folder
And then type:
~/Library
for your Library Folder
-or-
/Library
for the root Library folder.

Strange finder icon in my dock!

I have a strange Finder icon in my dock that looks like it has a glass box over it. I know it definitely is not supposed to look like that. I have tried the following:
- Restarting
- Moving Dock from side to side to bottom
- Changing wallpaper
- Changing magnification settings

Someone posted this problem a couple of years ago. Doesn't seem like anyone had an answer then.
http://forums.macrumors.com/showthread.php?t=455721
This is really weird.
Regards,
Steve M.
Message was edited by: Steve M.

Strange XSLT Behavior: xsl:template match

Hello I found the following strange XSLT behavior when using xsl:template. I only want to read the content of the element /Source/Surname/Details. Therefore I match this path using xsl:template match.
What is strange that in the target message also the value of the Element LastName is written at the end. Please see example below. This is just a short example to point out the problem. I have a bigger message structure where I have to match a similar path. How can I avoid the the value of the FullDetails is just written at the end (not even beeing in an element)? I would have expected that the path is only matched once and the instructions then executed without <LastName> beeing even touched.I used XML Spy for this test.
Here is an example:
Source message:
<?xml version="1.0" encoding="UTF-8"?>
<Source>
     <Surname>
          <Details>MyFirstName</Details>
     </Surname>
     <LastName>
          <FullDetails> MyLastName </FullDetails>
     </LastName>
</Source>
XSLT
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
<xsl:template match="/Source/Surname">
<PORR>
<Name><xsl:value-of select="Details"/></Name>
</PORR>
</xsl:template>
</xsl:stylesheet>
Target Message
<?xml version="1.0" encoding="UTF-8"?>
<PORR xmlns:fo="http://www.w3.org/1999/XSL/Format">
<Name>MyFirstName</Name></PORR>MyLastName
Edited by: Florian Guppenberger on Oct 8, 2009 4:35 AM
Edited by: Florian Guppenberger on Oct 8, 2009 4:36 AM
Edited by: Florian Guppenberger on Oct 8, 2009 4:36 AM
Edited by: Florian Guppenberger on Oct 8, 2009 4:37 AM

Hi,
I am not sure why your XSLT behaving like that,please try this XSL,what i did chnages is Templete match /*,I given exact path in Value of select,.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
<xsl:template match="/*">
<PORR>
<Name><xsl:value-of select="/Source/Surname/Details"/></Name>
</PORR>
</xsl:template>
</xsl:stylesheet>
Regards,
Raj

Strange typeover behavior in Newsfeeds

I am getting this strange intermittent behavior when create a post in the Newsfeed.
As you begin to type the text compress and it almost looks like the letters are typing over themselves
The resulting text can be posted and looks fine when posted, it some times does throw an error but the error and type over don't seem connected
It happens on all browser types and even phones and tablets

Hi,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Best Regards,
Eric
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Changing OS X's default "Find" behavior

Is there a way to change the Finder's "Find" behavior so it DOES NOT automatically / immediately start searching your hard drive(s) and volumes as soon as you begin typing a term in the search field? I'd like to disable this feature if possible.

3rd party tools and copying and pasting
are not really that desirable.
You can use Automator to do most of the work for you.
Open Automator and drag the following Actions to the right-hand side workflow pane, in this order:
1) Ask for Text -- The purpose of this action is to create a dialog box into which you'll enter your search term. In the upper field (pre-populated with the word "Question"), enter a text query appropriate to the task at hand, "Search for..." or "Search Spotlight..." for example. Leave the Default Answer field blank.
2) Copy to Clipboard -- Copies the text you entered in the dialog box to the Clipboard.
3) Spotlight -- Opens Spotlight automatically. Make sure to check "Show Action When Run" under Options. At this point you need only paste into the Spotlight search field and Spotlight will begin searching.
Test the Automator workflow by selecting Workflow > Run; when you find it works properly, File > Save As an Application.
While it would be ideal if in step 3 Spotlight would open with the search term already populated, thus making pasting unnecessary, I haven't found a way. However, there is a 3rd-party application called Laserlight 2.0.3 which will do just that. Good luck!
Regards, Andrew99
iMac 1 GHz Flat Panel 15" PPC 768 MB RAM Mac OS X (10.4.10)

Strange ZWSREG behavior

We are in the middle of a rollout of about 300 new machines. (used sysprep in the image) The first 100 are doing something strange. They boot up get renamed and join the windows domain with their new name, but register with ZEN as the randomly generated Microsoft name. (usually someting like N-398477634379d979) I deleted the workstation object, unreged and rereged the computer, but it always reregisters with the randomly generated name. What gives? I found a TID that said this was fixed by an update on the latest desktop agent, but that I could work around it by deleting the incorrectly named object and waiting for the machine to reboot, However it still registers with the wrong name. Any ideas? Thanks.
J. Daniel Treadwell

But these are new computers. They should not have image safe data yet. I tried it, but got the same result.
Originally Posted by Craig Wilson
Try running ZISWIN -R when you unregister.
My guess is that it's pulling the old info from Image Safe Data.
Craig Wilson - MCNE, MCSE, CCNA
Novell Support Forums Volunteer Sysop
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
"jtreadwell" <[email protected]> wrote in message
news:[email protected]..
>
> We are in the middle of a rollout of about 300 new machines. (used
> sysprep in the image) The first 100 are doing something strange. They
> boot up get renamed and join the windows domain with their new name,
> but register with ZEN as the randomly generated Microsoft name.
> (usually someting like N-398477634379d979) I deleted the workstation
> object, unreged and rereged the computer, but it always reregisters
> with the randomly generated name. What gives? I found a TID that said
> this was fixed by an update on the latest desktop agent, but that I
> could work around it by deleting the incorrectly named object and
> waiting for the machine to reboot, However it still registers with the
> wrong name. Any ideas? Thanks.
>
>
> J. Daniel Treadwell
>
>
> --
> jtreadwell
> ------------------------------------------------------------------------
> jtreadwell's Profile: NOVELL FORUMS - View Profile: jtreadwell
> View this thread: Strange ZWSREG behavior - NOVELL FORUMS
>

Strange icons behavior on Finder and Dock

Hi!
I’ve purchased a new MacBook and am in the process of transforming my old iBook G4 into a sort of netbook for Web and iWork but am having some strange problems.
This notebook served me very well for several years but I decide to clean it after the migration of all my content to the new MacBook.
First I formatted and reinstalled Leopard on it. Then I performed all the OS online updates and finally installed iWork/iLife and also performed the online updates for these Apps. After that I activated MobileMe, imported all my data and began to download Apps like Evernote, Skype, etc.
After downloading some Apps I started to place their icons on the Dock but for some reason they simple disappeared after some seconds. Went to the web and found some tips to delete the Dock "plist" and some other files. Did that, perform a restart, but that didn’t work for me.
Since everything was new I decide to create a new user and test the Dock. It worked fine in the new user (without MobileMe activated) but then some other strange thing happened. The icons of installed Apps are not appearing on the Finder, though they were there in the deleted user. If I search for them with Spotlight they are there (in the Application folder!) and I can even drag them to the Dock, but for some reason they are not in the Finder window itself.
I remember selecting “install in all users” when installing all the Apps, so this cannot be the problem. Other interesting thing to notice is that if I search for a App with Spotlight, drag it to another place (out of the Application folder) and then move it back to the Application folder, the icon appears on the Finder window.
My questions are: Does anyone know what can be happening? Should I start all over reinstalling Leopard?
Thanks!

vladcampos wrote:
Hi!
I’ve purchased a new MacBook and am in the process of transforming my old iBook G4 into a sort of netbook for Web and iWork but am having some strange problems.
This notebook served me very well for several years but I decide to clean it after the migration of all my content to the new MacBook.
First I formatted and reinstalled Leopard on it. Then I performed all the OS online updates and finally installed iWork/iLife and also performed the online updates for these Apps. After that I activated MobileMe, imported all my data and began to download Apps like Evernote, Skype, etc.
After downloading some Apps I started to place their icons on the Dock but for some reason they simple disappeared after some seconds.
this is a very common mobileme issue caused by corupt sync data. turn off and reset mobileme syncing
http://support.apple.com/kb/HT1497
Went to the web and found some tips to delete the Dock "plist" and some other files. Did that, perform a restart, but that didn’t work for me.
Since everything was new I decide to create a new user and test the Dock. It worked fine in the new user (without MobileMe activated) but then some other strange thing happened. The icons of installed Apps are not appearing on the Finder,
I don't understand what you mean by this.
though they were there in the deleted user. If I search for them with Spotlight they are there (in the Application folder!) and I can even drag them to the Dock, but for some reason they are not in the Finder window itself.
which finder window?
I remember selecting “install in all users” when installing all the Apps, so this cannot be the problem. Other interesting thing to notice is that if I search for a App with Spotlight, drag it to another place (out of the Application folder) and then move it back to the Application folder, the icon appears on the Finder window.
My questions are: Does anyone know what can be happening? Should I start all over reinstalling Leopard?
Thanks!

Strange Finder non-responsive behavior.

Recently my Finder has started acting oddly: when I navigate to the absolute top level of the directory chain, i.e. the computer folder (mine is named Fenchurch, includes the HDD's and the Network folder), the window pretends to be unresponsive. I can't close it, I can't resize it, and more often than not it doesn't even display the contents; it either stays white or some sort of graphical jumble.
I say "pretends" because if i click a few times on a different folder in my sidebar, that folder loads perfectly fine in the same window. CMD+down also works to load my HDD folder, as if it was highlighted despite Finder not actually showing it as highlighted.
Sooo, what's the deal? Anyone run into this problem before?

Recently my Finder has started acting oddly: when I navigate to the absolute top level of the directory chain, i.e. the computer folder (mine is named Fenchurch, includes the HDD's and the Network folder), the window pretends to be unresponsive. I can't close it, I can't resize it, and more often than not it doesn't even display the contents; it either stays white or some sort of graphical jumble.
I say "pretends" because if i click a few times on a different folder in my sidebar, that folder loads perfectly fine in the same window. CMD+down also works to load my HDD folder, as if it was highlighted despite Finder not actually showing it as highlighted.
Sooo, what's the deal? Anyone run into this problem before?

Strange window behavior with CS5

I have begun experiencing strange behavior with PS CS5. I should begun with the machine configuration: 2.66GHz iMac (8,1) Intel Core Duo with 4GB RAM and OSX 10.6.6, Radeon HD 2600 Pro graphics card. The initial symptom showed up suddenly as an inability to display an image window; that is, I could open PS normally, everything would show up properly, but when I opened an image file of any sort, there would be no image window. Other cues indicated that the file was open; for example, the window menu would show it selected, and the layers palette would show the file's layers.
It did not seem to matter what type of file was involved: PSD, JPG, TIF, whatever. Occasionally, this behavior would begin during a session. Sometimes it would happen right off the bat. Sometimes, stopping and restarting PS seemed to clean things up; other times, this had no effect. After messing around quite a bit with different permutations and combinations, all I could say was that the problem was random.
I might add that I've had PS CS5 on this machine pretty much since it was announced, and had not had problems with it before. So this issue came along quite suddenly a couple of weeks ago. This was a little after I'd installed an update for Nik's Viveza 2; and I began to suspect that. Although why Viveza should do such a strange thing was odd, and Viveza was never part of the files I was experiencing issues with. Anyway, I went back to an earlier version of Viveza and the problem persisted.
Since I run Time Machine, I also went back to versions of the entire PS folder from a month back, and found the same problem. Along the way, I experimented with the files I was using with PS CS4 & CS3, which I also have installed on this machine. These two versions of PS run perfectly well. At least the CS4 version has precisely the same plugins as the CS5 folder, and this seems to discount the potential problem with plugins.
To be sure about CS5, I completely deactivated, deinstalled, and reinstalled it. The same issues occurred. Now, I have to admit that I let PS run its update process so that I brought it back to the most recent version in this step of my troubleshooting. So, I can't be certain that the issue isn't with some update of CS5.
I might add that I have been running CS5 in 32-bit mode, for compatibility with certain plugins. This may or may not be an issue, since I have limited experience with running in 64-bit mode. At this point, I should add a bit more about the confusing behavior.
While messing around with CS5, I also suspected the GPU support, since my problem had to do with windows. When the problem presents itself, the usual cycle through window views that you get by pressing the "F" key seems to get messed up. In particular, the "F" key doesn't work at all. Next, if you use the View menu to select different views, the full screen with menu bar view will often have garbled pixels, while the full screen view will show a blank grey screen. Then, cycling back to a window view will show a window with blank grey contents. This is interesting since the starting point was no window at all; but going into full screen and then back will produce a window with bogus contents.
Now, the next strange thing, having to do with the GPU, is that CS5 often fails to recognize the Radeon HD 2600 card. Oddly enough, it did originally. And I had it running in Basic mode. However, CS4 does recognize the GPU; and I can set it in any variety of modes: Basic, Normal, and Advanced. This behavior is not consistent at all either; that is, while CS5 almost always now fails to detect the GPU, sometimes it does. As near as I can tell, this failure to detect the card does not depend upon whether I start CS5 in 32-bit or 64-bit mode. OTOH, CS4 always recognizes the GPU.
Another form of this odd behavior arises if I start CS5 cold, and then just open a new blank window. This almost always works. I get a blank white window, and I can paint on it with a brush, etc. However, if I go ahead at this point and open a file, then the new file takes over the window; and there are no tabs. If I select the original new file, usually labelled "Untitled", the window bar will show the change of filename but the window's contents and the layers palette will continue to show the old file that I had opened. Cycling through views can sometimes get back to the new Untitled file, but just selecting file windows never works.
Yet another aspect of this messed up window behavior is that the workspace bar, which shows the Bridge, MiniBridge and view icons on the upper left and the various workspace options and CS Live on the upper right, is present but blank. OTOH, the tool bar is always displayed correctly, as is the horizontal bar that shows the various tool options. Likewise, the palettes for the workspace such as layers, swatches, adjustments, and so on, are always correctly displayed on the left.
My next steps in trying to figure this out will be to ensure that I am running the latest of all plugins so that I can get everything running in 64-bit mode and try this again. However, the single factor that seems consistent in this whole mess is that whenever I do find this odd behavior, the performance preferences window will indicate that CS5 is not detecting the GPU. Whenever this happens, if I open up CS4 and check the same performance preference in it, the GPU is detected. I can have the two preference windows side by side on the screen in fact, CS4 sees the GPU and CS5 does not. The counter-indication is that sometimes CS5 will work properly and the preferences window still shows that the GPU has not been detected. Having said that, I can add that if I have opened up CS5, and it has found the GPU, and I have set it into, say, Basic mode, and then later found CS5 messing up, and I go back and check the performance preferences again, the GPU has always been lost. So, CS5 can mess up windows with or without the GPU detected and active; but when if it started with the GPU present, it will show up as lost after the weird behavior starts.
To add one more observation, I have had Macs and other computers with failing GPUs. This computer is showing none of the typical signs of that. Every other program seems to be working just fine, and I have a lot of these, many graphics intensive; e.g., Corel Painter 11, Parallels v6 running Windows 7, PS CS4, Lightroom v3, Aperture v3, and so on. It is just CS5 that is messing up.
I could load up this message with screen shots of all this nonsense, but I'm not sure what that would add to the strange tale, other than I'm not pulling your legs. I am, however, pulling out my own hair.
As I stated before, this began quite suddenly a couple of weeks ago, early Feb 2011. My best guess as to cause is some combination of incompatible updates between CS5, OSX, and maybe some plugin or other. I found unusual behavior with onOne's FocalPoint v2 last year after Apple updated GPU drivers in some OSX update, and cratered that program. It took onOne a month or two to fix that. I have CS5 on a laptop with the same OSX version, and on that I haven't seen these issues; but then, I haven't been using it as intensely over there. Also, that machine has different CPU and GPU models than this iMac.
So, to the community: is anybody else starting to see this odd stuff? Am I alone?

Here's the reason I say that the same plugins exist for both CS4 & CS5. Sometime last year, the internal hard drive on this computer died (as they so often do), and it was replaced under the Apple care warranty. As a consequence, I decided to rebuild the OS and applications from scratch and bring back my user files from backup. I among other things, I reinstalled all of CS4 as well as CS5 (and I had to put CS3 back too for reasons having to do with printing calibration images for Quad Tone RIP). Then, I went to reinstall the plugins that I needed. I use Nik Software, onOne, Portrait Professional and various Topaz plugins. To my recollection, most of these install in PS CS3, CS4, CS5, Aperture, and Lightroom. In short, it is not that I've copied or moved plugin folders from one application folder to another, just that the installers automatically detect the presence of the various applications and put the various plugins into each, as appropriate.
The only 32-bit plugins that I have that don't fit into this category are from Vincent Versace. He provides special versions of certain Nik plugins (Tonal Contrast, Contrast Only, etc) that function with some Acme Educational extensions for performing B&W conversion, sharpening, blah blah blah. These plugins are only 32-bit and the extensions are only CS5 compatible. I've installed these ones only into CS5; so, you've got me. OTOH, I've had these from Vincent as soon as CS5 was available; and they've worked so far without problems. Perhaps I should just edit the extensions so I could use the latest plugins direct from Nik instead of the Versace special editions...
I've checked fonts and repaired permissions. I am presently going through the rather tedious process of disabling plugins and extensions to see if anything yields consistent results. The rather random arrival of the strangeness makes ensuring that a change is really having an effect more difficult to validate, as you will appreciate.
I apologize for my long-winded original post. I add all of the detail so that anyone who'd experienced similar strange behaviors might properly pattern-match what they were seeing. On the one hand, in finding the cause of a problem, you look for what's changed; and theoretically nothing is new. On the other hand, there's always so much changing behind the scenes with automatic updates of this, that, and the other thing that it's impossible to make the claim that nothing's new.

Strange Mail Behavior when cicking reply to

I am having a very different but very strange behavior when in mail 5.2 I click on reply or forward in my menu bar a new mail window opens up and quickly moves off to the right of the screen and disappears laving my inbox. I cannot find where they are going and the only way I can respond is open the mail in a new window. This is weird I have been using mail forever and never seen this before?
any suggestions???
mac os 10.7.4
Thanks for any suggestions

So Mail doesn’t really crash (i.e. quit unexpectedly). Rather, it freezes (i.e. becomes unresponsive), right?
What type of mail account is this (POP, IMAP, .Mac)?
Verify/repair the startup disk (not just permissions), as described here:
The Repair functions of Disk Utility: what's it all about?
Go to Apple Menu > System Preferences > Network, choose Network Port Configurations from the Show popup menu, and make sure that the configuration used to connect to Internet appears at the top of the list.
Try disabling Search .Mac For Certificates in Keychain Access > Preferences if it’s enabled. Take a look at the following articles for an explanation of why this could be the problem:
http://www.hawkwings.net/2006/07/18/apple-mail-phones-home-too/
http://www.macgeekery.com/tips/mailapp_doesnt_phone_homeeither/

Some strange SAX behavior

Hi,
I'm somewhat new to SAX processing. I have a simple program that uses the SAX parser. In testing this code, I've noticed some behavior that I find strange. Can anyone veryify if what I describe is expected behavior?
1) Parsing an element with no data, like <element></element>. I'm finding that the characters method is still being called when it sees elements like this. Furthermore, when I extract the supposed data using:
String data = new String(p_buff, p_start, p_length);
What I get is a newline, '\n'.
2) SAX appears to drop data when it parses an element that contains an entity. For example, the characters method returns only an "R" when it parses an XML field like:
<genre>R&B/Soul</genre>
Where & is actually the ampersand character, followed by "amp;"
Are these bugs/features, or is more likely that I'm coding it incorrectly?

1) Parsing an element with no data, like <element></element>. I'm finding that the characters
method is still being called when it sees elements like this. Furthermore, when I extract the
supposed data using:
String data = new String(p_buff, p_start, rt, p_length);
What I get is a newline, '\n'.The newline and space characters are called ignorable Whitespace and are passed by a SAX parser by the character() or the ignorableWhitespace() callback methods, that is between the XML's root element start and end tags. Your example <element></element> does not generate any ignorable whitespace, however, so let's look at this as an example (4 spaces before each child tag):
<root>
<child>
</child>
</root>Here, the ignorable whitespace is:
a newline after <root> - will be attributed to element <root>
4 spaces before <child> - will be attributed to element <root>
a newline after <child> - will be attributed to element <child>
4 spaces before </child> - will be attributed to element <child>
a newline after </child> - will be attributed to element <root>
There are two categories of SAX parsers: validating and non-validating. Validating parsers must report ignorable whitespace through the ignorableWhitespace() callback. Non-validating parsers CAN use the same method OR the character() callback (yours is the latter, apparently).
2) SAX appears to drop data when it parses an element that contains an entity. For example,
the characters method returns only an "R" when it parses an XML field like:
<genre>R&B/Soul</genre>
Where & is actually the ampersand character, followed by "amp;"Again, SAX parser implementations have some freedom here as well. A parser CAN report content in one character() callback or can use several callbacks (Xerces, which I use, calls the method 3 times for your example [once for R, once for &, and once for B]). You might want to look at your character() implementation if you only see a callback for R and nothing else, or your parser is faulty (which is unlikely).
So, relax, everything is normal SAX parser behaviour.

Strange Finder Behavior

Similar Messages

Maybe you are looking for