Interesting Phenomenon on 10.1.5... thoughts?
I just posted these notes to Apple's feedback board on OS X on a problem I experienced with 10.1.5. I just copied and pasted them here, since I see no need to type it all twice. Here is my post:
I have a PowerBook G3 (firewire/Prismo) with a 400 MHZ processor, 640 MB RAM on system 10.1.5. I have written a couple of times, already on the failure of my screen saver and energy saver settings to engage. At first I thought it to be a bug with the new system upgrade (10.1.5), period. However, I wrote, again, to say it occurred only while the most recent version of AIM was active (or, maybe, saying does not occur is more accurate). My screen saver does not come on automatically, and my screen never fades black automatically, as set in my preferences, while AIM is active. It works fine the remainder of the time. Well, tonight it worked, and I was shocked by its functionality. However after typing in my password to remove the screen saver (after moving the cursor to bring the screen back to life), I could save nothing to disk at all. It gave me an error -34 message when I tried to move, copy, or rename anything, and I could not close any program. I had to force quit them all, and then restart my Macintosh. I am sure there is some Terminal, command-line method to do it, but I found a restart works (when the unable-to-save problem happened in previous system editions, 10.1.2 [maybe 10.1.1...working from memory here] and especially 10.1.3, for certain). I thought the correlation of the settings suddenly functioning and of the inability to save to disk might give you a better idea of any problem in this version of the system, and so I am reporting it. The only real difference in my behavior on my Macintosh before these events occurred was burning a CD earlier tonight. Afterwards, I noticed the Finder would open windows with the icons moved ierratically and fonts blurred through, but by closing and reopening the window, the items displayed normally. Since I moved no other files around after opening and closing the windows, I did not notice the problem continuing, although it could have been persisting through to the loss in my ability to save any data to my hard drive. I think I have provided all the information pertient to this episode. If I notice or think of anything else, I'll be certain to send it to you.
Any thoughts / comments?
Anyone else experience anything similar?
I have a PowerBook G3 (firewire/Prismo) with a 400 MHZ processor, 640 MB RAM on system 10.1.5. I have written a couple of times, already on the failure of my screen saver and energy saver settings to engage. At first I thought it to be a bug with the new system upgrade (10.1.5), period. However, I wrote, again, to say it occurred only while the most recent version of AIM was active (or, maybe, saying does not occur is more accurate). My screen saver does not come on automatically, and my screen never fades black automatically, as set in my preferences, while AIM is active. It works fine the remainder of the time. Well, tonight it worked, and I was shocked by its functionality. However after typing in my password to remove the screen saver (after moving the cursor to bring the screen back to life), I could save nothing to disk at all. It gave me an error -34 message when I tried to move, copy, or rename anything, and I could not close any program. I had to force quit them all, and then restart my Macintosh. I am sure there is some Terminal, command-line method to do it, but I found a restart works (when the unable-to-save problem happened in previous system editions, 10.1.2 [maybe 10.1.1...working from memory here] and especially 10.1.3, for certain). I thought the correlation of the settings suddenly functioning and of the inability to save to disk might give you a better idea of any problem in this version of the system, and so I am reporting it. The only real difference in my behavior on my Macintosh before these events occurred was burning a CD earlier tonight. Afterwards, I noticed the Finder would open windows with the icons moved ierratically and fonts blurred through, but by closing and reopening the window, the items displayed normally. Since I moved no other files around after opening and closing the windows, I did not notice the problem continuing, although it could have been persisting through to the loss in my ability to save any data to my hard drive. I think I have provided all the information pertient to this episode. If I notice or think of anything else, I'll be certain to send it to you.
Any thoughts / comments?
Anyone else experience anything similar?
Comments
You did graduate from the sixth grade (grammatically speaking), didn't you? If I can't make heads or tails of it, I doubt Apple will either. Distinct paragraphs will help next time. Also: have a point (seriously).
It's hard to determine exactly what your complaint is, based on what you wrote. Maybe you seek opinions in the Trouble-shooting forum?
He did notice that after burning a CD - before the other stuff happened - the Finder displayed icons in the wrong location and that labels were blurred. Reopening the affected windows fixed the problem. He didn't try to move/copy/rename any files at that time, so he doesn't know if the problem with those functions started before or after the screen saver came on.
Stop trying to post as though you're some sort of ****ing intellectual and go learn to express yourself in writing instead. Once you do that, all of your problems will magically disappear.
-DisgruntledQS733Owner
Donny-I am sorry I can't help your problem (don't have 10.1.5, wait I dont have a G4 now either) however ignore anyone who gives you sh*t here.
<strong>I suggest other AI members take a look in this thread and tell me who the real jackasses on the board. Some of you need to seriously check yoself. Do you all have your heads up your asses so far that you fail to believe any Macs have problems? That's what it seems like when you attack people just asking for help and take the attitude of "Well you must have screwed the computer up yourself". Honestly.
Donny-I am sorry I can't help your problem (don't have 10.1.5, wait I dont have a G4 now either) however ignore anyone who gives you sh*t here.</strong><hr></blockquote>
stop being an ******* and bringing your sad ass into other threads
<strong>...By the way, I am an intellectual, a philosopher, a computer-geek, a neuroscientist, pharmacological researcher, and professor. I enjoy my share of people, parties, shows, and all other entertainment that makes life worth living, also. Being a psychologist.... </strong><hr></blockquote>
In-other-words.... I am a nutcase, looney. Claiming to be a philosopher, neuroscientist, pharmacological researcher.... oh... must not forget... psychologist puts you in the "I have no grasp of reality" subset of humanity.
Anyway, Donny, if it happens again, you may have a disk problem. I would suggest running apple's "Disk Utility" to try and see if you have any HFS (or UFS, if like me you prefer case-sensitive fs') problems. And if that doesn't do it, Backup your data, reformat, and reinstall.
That's what I would do.
If you want to be really helpful, try to isolate and reproduce the problem, post it to Apple's discussion boards, and send a thorough and precise account of what happens when to Apple (the feedback link will do).
For what it's worth, I've never heard of this behavior.
Anyone else able to repeat this behavior?
Under 10.1.5 with the most recent version of AIM beta that supports Mac.com addresses as screen names, I would like to see if anyone else sees the same behavior. It would be very interesting to me, and it could be helpful.