I knew a few people were having a cry but as far as I knew it was a small minority so I never expected Apple to change it!
People round here always underestimate how many people a vocal minority represents.
I think it was the right decision to make if it had to be one way or the other because the transparency negatively affected usability.
As ever though, a simple choice would have been good. I would be surprised if there wasn't a way to turn transparency back on but with Apple you never know.
I think it was the right decision to make if it had to be one way or the other because the transparency negatively affected usability.
The irritating thing is that technically, having a variable amount of transparency would be very easy to implement. Apple could then have a slider in System preferences to allow the user to set the transparency level to whatever they please.
As you allude to, it might be possible to set the transparency by playing with a plist file somewhere.
Thanks for the hint! It did work (I got it up to 2MB/s in one direction), but I'm so lazy I'll probably just end up waiting for the official fix in 10.5.3...
Yep that worked - thanks to mikep123 for posting the link!
It worked when I applied the patch to both machines - otherwise yes it only worked in one direction.
Just a quick update, in case anyone finds this page while searching for info on the PDF copy bug. I received this email after following Mr. H's suggestion: (pretty cool that they reply to developer bug reports individually!)
This is a follow up to Bug ID# 5741969. After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 5565883. The original bug number being used to track this duplicate issue can be found in the State column, in this format: Duplicate/OrigBug#.
If you have any additional questions related to this bug or wish to check on status of the original issue, please update this bug report or send an email to <devbugs@apple.com>, referencing your Bug ID# 5741969.
Thank you for submitting this bug report. We truly appreciate your assistance in helping us discover and isolate bugs.
Just a quick update, in case anyone finds this page while searching for info on the PDF copy bug. I received this email after following Mr. H's suggestion: (pretty cool that they reply to developer bug reports individually!)
This is a follow up to Bug ID# 5741969. After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 5565883. The original bug number being used to track this duplicate issue can be found in the State column, in this format: Duplicate/OrigBug#.
If you have any additional questions related to this bug or wish to check on status of the original issue, please update this bug report or send an email to <devbugs@apple.com>, referencing your Bug ID# 5741969.
Thank you for submitting this bug report. We truly appreciate your assistance in helping us discover and isolate bugs.
Best Regards,
Allison Vanderby
Apple Developer Connection
Worldwide Developer Relations
What was the point, this thread is old already. Who cares.
What was the point, this thread is old already. Who cares.
Wow! Thanks for that!
The point is stated quite clearly by meelash: "in case anyone finds this page while searching for info on the PDF copy bug".
Google and other web search-engines have "bots" which continually scan and index these pages. There are millions of OS X users around the world and it is quite possible that some of them who may suffer from this bug would search for info on it and come across this page.
Others of us just like to keep up-to-date with this kind of info, so we know what are bugs and what is user-error or malfunction. Even if we're not affected directly, it helps to assist others with trouble-shooting.
The point is stated quite clearly by meelash: "in case anyone finds this page while searching for info on the PDF copy bug".
Google and other web search-engines have "bots" which continually scan and index these pages. There are millions of OS X users around the world and it is quite possible that some of them who may suffer from this bug would search for info on it and come across this page.
Others of us just like to keep up-to-date with this kind of info, so we know what are bugs and what is user-error or malfunction. Even if we're not affected directly, it helps to assist others with trouble-shooting.
What's the point, the thread is dead. Start a new one if need be. Again WHO CARES.
What's the point, the thread is dead. Start a new one if need be. Again WHO CARES.
Blimey. Why are some people so hell-bent on proving themselves to be morons? I already explained it to you. I suggest you calm down, have some reading lessons, re-read my post and then maybe you'll be able to figure it out.
I'm still having serious upload speed problems; download speeds are down also, but I have excess capacity for downloads so I don' notice it as much. Upload speeds though are under 100k; anybody have any solutions here? I took my MacBook Pro into the Apple store today, and they recommended replacing the AirPort card...
Ok, so here are the troubleshooting steps I've taken (Baseline system: MacBook Pro, Core Duo 2 ghz, 2 GB RAM, OS 10.5.2):
1. Created a test account - problem still exists
2. Booted into Windows XP via bootcamp - problem does not exist
3. Booted to safe mode, run daily/weekly/monthly scripts, reset PRAM - problem still exists
My assumption from this is that it is not specific to my user profile, and is specific to OS X, and is not a problem with my AirPort card
4. Connected via ethernet directly to my AEBS - problem does not exist
5. Connected via Wifi from my work computer (Dell Latitude D620) - problem does not exist
6. Connected via Wifi from my old PowerMac G4 Cube - problem does not exist
This tells me that it is not a problem with the AEBS or wireless LAN configuration, and it doesn't occur on OS 10.4
7. Completed an archive and install of OS X 10.5 (from the DVD) - problem does not exist
8. Ran software update; the following updates were installed - problem still exists
AirPort utility 5.3.1
Remote Desktop Client 3.2.1
iLife support 8.2
QuickTime 7.4.1
Front Row Update 2.1.2
Mac OS X Combined update 10.5.2
iTunes 7.6.1
This tells me the issue is localized to one of these updates, most likely the 10.5.2 update.
I'm still having serious upload speed problems; download speeds are down also, but I have excess capacity for downloads so I don' notice it as much. Upload speeds though are under 100k; anybody have any solutions here?
You could try this. Whilst it says it fixes slow SMB download, it has also been reported to fix a variety of other link-speed issues. It's worth a shot.
You could try this. Whilst it says it fixes slow SMB download, it has also been reported to fix a variety of other link-speed issues. It's worth a shot.
Thanks, I'll give it a try. I wish Apple would acknowledge that there are people experiencing these issues though.
Thanks, I'll give it a try. I wish Apple would acknowledge that there are people experiencing these issues though.
Mike
If that doesn't help, try also rebooting every machine in Safe Mode (shift down), then restarting from the login menu, holding down Apple-Option-P-R (PRAM) for two chimes, then letting it reboot normally.
The first reboot will take a long time but this is normal. Sorted my problem out (and my Time Machine one!)
I've tried the safe mode boo/followed by a PRAM reset - no luck there. I think it's really tied to the 10.5.2 update or the Airport update. When I did an Archive and Install from the Leopard retail disk, it worked fine. As soon as software update ran though, I started having the same issue.
Comments
I knew a few people were having a cry but as far as I knew it was a small minority so I never expected Apple to change it!
People round here always underestimate how many people a vocal minority represents.
I think it was the right decision to make if it had to be one way or the other because the transparency negatively affected usability.
As ever though, a simple choice would have been good. I would be surprised if there wasn't a way to turn transparency back on but with Apple you never know.
I think it was the right decision to make if it had to be one way or the other because the transparency negatively affected usability.
The irritating thing is that technically, having a variable amount of transparency would be very easy to implement. Apple could then have a slider in System preferences to allow the user to set the transparency level to whatever they please.
As you allude to, it might be possible to set the transparency by playing with a plist file somewhere.
What do you mean by 300-more MB? The update was 341MB as it is.
BTW, I reinstalled iSync and now it works fine. Still don't know what the problem was...
Please, tell me somebody how to reinstall iSync so it would work....? I just do not know how it is done. I can not live without it
Anyone??? Please....
You can try to extract it from the system software disk(s) using Pacifist.
Thanks for the hint! It did work (I got it up to 2MB/s in one direction), but I'm so lazy I'll probably just end up waiting for the official fix in 10.5.3...
Yep that worked - thanks to mikep123 for posting the link!
It worked when I applied the patch to both machines - otherwise yes it only worked in one direction.
This is a follow up to Bug ID# 5741969. After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 5565883. The original bug number being used to track this duplicate issue can be found in the State column, in this format: Duplicate/OrigBug#.
If you have any additional questions related to this bug or wish to check on status of the original issue, please update this bug report or send an email to <devbugs@apple.com>, referencing your Bug ID# 5741969.
Thank you for submitting this bug report. We truly appreciate your assistance in helping us discover and isolate bugs.
Best Regards,
Allison Vanderby
Apple Developer Connection
Worldwide Developer Relations
Just a quick update, in case anyone finds this page while searching for info on the PDF copy bug. I received this email after following Mr. H's suggestion: (pretty cool that they reply to developer bug reports individually!)
This is a follow up to Bug ID# 5741969. After further investigation it has been determined that this is a known issue, which is currently being investigated by engineering. This issue has been filed in our bug database under the original Bug ID# 5565883. The original bug number being used to track this duplicate issue can be found in the State column, in this format: Duplicate/OrigBug#.
If you have any additional questions related to this bug or wish to check on status of the original issue, please update this bug report or send an email to <devbugs@apple.com>, referencing your Bug ID# 5741969.
Thank you for submitting this bug report. We truly appreciate your assistance in helping us discover and isolate bugs.
Best Regards,
Allison Vanderby
Apple Developer Connection
Worldwide Developer Relations
What was the point, this thread is old already. Who cares.
What was the point, this thread is old already. Who cares.
Wow! Thanks for that!
The point is stated quite clearly by meelash: "in case anyone finds this page while searching for info on the PDF copy bug".
Google and other web search-engines have "bots" which continually scan and index these pages. There are millions of OS X users around the world and it is quite possible that some of them who may suffer from this bug would search for info on it and come across this page.
Others of us just like to keep up-to-date with this kind of info, so we know what are bugs and what is user-error or malfunction. Even if we're not affected directly, it helps to assist others with trouble-shooting.
Wow! Thanks for that!
The point is stated quite clearly by meelash: "in case anyone finds this page while searching for info on the PDF copy bug".
Google and other web search-engines have "bots" which continually scan and index these pages. There are millions of OS X users around the world and it is quite possible that some of them who may suffer from this bug would search for info on it and come across this page.
Others of us just like to keep up-to-date with this kind of info, so we know what are bugs and what is user-error or malfunction. Even if we're not affected directly, it helps to assist others with trouble-shooting.
What's the point, the thread is dead. Start a new one if need be. Again WHO CARES.
What's the point, the thread is dead. Start a new one if need be. Again WHO CARES.
You must, or you wouldn't be so violent about it.
BTW, thanks Mr. H. It is always helpful to finish a 'problem' thread with a solution.
What's the point, the thread is dead. Start a new one if need be. Again WHO CARES.
Blimey. Why are some people so hell-bent on proving themselves to be morons? I already explained it to you. I suggest you calm down, have some reading lessons, re-read my post and then maybe you'll be able to figure it out.
Ok, so here are the troubleshooting steps I've taken (Baseline system: MacBook Pro, Core Duo 2 ghz, 2 GB RAM, OS 10.5.2):
1. Created a test account - problem still exists
2. Booted into Windows XP via bootcamp - problem does not exist
3. Booted to safe mode, run daily/weekly/monthly scripts, reset PRAM - problem still exists
My assumption from this is that it is not specific to my user profile, and is specific to OS X, and is not a problem with my AirPort card
4. Connected via ethernet directly to my AEBS - problem does not exist
5. Connected via Wifi from my work computer (Dell Latitude D620) - problem does not exist
6. Connected via Wifi from my old PowerMac G4 Cube - problem does not exist
This tells me that it is not a problem with the AEBS or wireless LAN configuration, and it doesn't occur on OS 10.4
7. Completed an archive and install of OS X 10.5 (from the DVD) - problem does not exist
8. Ran software update; the following updates were installed - problem still exists
AirPort utility 5.3.1
Remote Desktop Client 3.2.1
iLife support 8.2
QuickTime 7.4.1
Front Row Update 2.1.2
Mac OS X Combined update 10.5.2
iTunes 7.6.1
This tells me the issue is localized to one of these updates, most likely the 10.5.2 update.
I'm still having serious upload speed problems; download speeds are down also, but I have excess capacity for downloads so I don' notice it as much. Upload speeds though are under 100k; anybody have any solutions here?
You could try this. Whilst it says it fixes slow SMB download, it has also been reported to fix a variety of other link-speed issues. It's worth a shot.
You could try this. Whilst it says it fixes slow SMB download, it has also been reported to fix a variety of other link-speed issues. It's worth a shot.
Thanks, I'll give it a try. I wish Apple would acknowledge that there are people experiencing these issues though.
Mike
Thanks, I'll give it a try. I wish Apple would acknowledge that there are people experiencing these issues though.
Mike
If that doesn't help, try also rebooting every machine in Safe Mode (shift down), then restarting from the login menu, holding down Apple-Option-P-R (PRAM) for two chimes, then letting it reboot normally.
The first reboot will take a long time but this is normal. Sorted my problem out (and my Time Machine one!)
Mike