![]() It’s a nice idea, but in reality, there are numerous areas where Setup Assistant simply doesn’t-and probably can’t-save you from additional work. The promise implicit in Setup Assistant’s migration is that you won’t have to reconfigure everything and can just get back to work. What I do notice is that all the flakiness I was experiencing has disappeared-it’s nice to be able to restart without it being a production (see “ Six Lessons Learned from Dealing with an iMac’s Dead SSD,” 27 April 2020).ĭuring the setup of the new iMac, I had no issues migrating all my data from the Samsung T5 SSD that I had been using to boot the old iMac, but I was somewhat surprised at how much additional work was necessary afterward. The new machine is great, although I have to admit that I don’t notice much of a performance improvement over the old one, despite it having a much beefier CPU. Several weeks ago, I upgraded from a 2014 27-inch iMac with Retina display to Apple’s new 2020 version of the same model (see “ 27-inch iMac Receives Significant Update, Other iMacs Get a Nod,” 4 August 2020). Moving to a New Mac: What’s Left to Do After Migration? #1664: Real system requirements for OS 2023, beware Siri creating alarms instead of timers.#1665: Important OS security updates, abusive Web notifications, solve myopia with an iPhone, Self Service Repair.#1666: Air quality websites and apps, The Password Game.#1667: OS Rapid Security Responses, 1Password and 2FA, using Siri to request music.#1668: Updated Rapid Security Responses, OS public betas, screen saver bug fixed, “Red Team Blues” book review.If this is a widespread problem, folk should let me know, and I'll do a 2.6.1 release ASAP. The workaround is to remove the custom icon before you add it to DragThing, by selecting the icon in the Get Info window, and choosing 'Clear' from the edit menu, or pasting on another one under 8.1. Unfortunately, DragThing doesn't fail gracefully when it can't find the right data, hence the -1000 error. If you want a custom icon that works under both 8.1 and 8.5, you need to build it by hand, or use something like the IconFactory's IconDropper: The problem comes because the 8.5 and later Finders only add an 'icns' resource when you paste on a custom icon, not the separate "icl8" style data. Update: James Thomson (author of DragThing) replies: "This is likely related to a known problem DragThing has under 8.1 - if you have a 32-bit custom icon pasted on an item, and none of the 'old style' custom icon data there, DragThing will get a "-1000" error when it tries to read the icon, since the 32-bit icons don't work under 8.1. ![]() And if 8.1 users make it a DragThing palette item, they will crash and corrupt their preferences when they try and use it. ![]() But if you pasted it on after you upgraded to 8.6, then 8.1 users will just get a generic shared icon. That is, if you pasted the custom icon onto the folder while you were in an earlier version of the OS, then 8.1 users will still see it. This seems to be related to the way 8.6 creates folder icons, because I've noticed that all 8.1 machines get generic server icons when they log onto shared folders created in 8.6. ![]() Eric Taylor found that when he tried to use DragThing to log onto a shared folder on an 8.6 machine with a custom icon on the folder, it caused a crash. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |