toggle

AAPL Stock: 439.66 ( -3.27 )

http://www.macnn.com/articles/02/10/08/apple.kb/

Apple KB roundup: 10.2 issues; iSync tip

updated 07:00 pm EDT, Tue October 8, 2002

 
", 0, 0);


Recent Apple advisories and tips: Computers running Mac OS 9 or X can stop responding if put into sleep while an iPod is connected; the Mac OS X 10.2 Finder may become unresponsive for 30 to 90 seconds if the Inspector version of the Info window is used to change a file name; in order to sync with a Palm OS device, users of iSync 1.0 must first configure conduit settings in HotSync Manager; automatic notification of software updates may be turned off after upgrading Mac OS X 10.1 to version 10.2; a kernel panic may occur under OS X 10.2 if a file whose filename ends with "#02" -- or any other hexadecimal number -- is copied via any Apple file service (Finder, etc.).


by MacNN Staff

Post tools:

TAGS :

 troubleshooting
toggle

Comments

  1. MacNN.com Reader

    Fresh-Faced Recruit

    Joined: Jul 2001

    0

    Hex Number XFer

    I've have this happen to me. I had a file named #02 (for number 2), and in froze both machines when I transfered it. Glad Apple is aware of it.

  1. MacNN.com Reader

    Fresh-Faced Recruit

    Joined: Jul 2001

    0

    odd

    That's kind of a wacky bug, isn't it?

  1. MacNN.com Reader

    Fresh-Faced Recruit

    Joined: Jul 2001

    0

    Not in Finder...

    It's on any server - ASIP, Mac OS X Server, File Sharing, etc.

  1. Rosyna

    Forum Regular

    Joined: Aug 2001

    0

    Loverly

    Considering the Mac OS is the most likely software to create files this way. The #number format is used to mangle names when the program doesn't support a long file name. Let's say, for example, a user using the most recent AIM client (which supports long file names) sends a file named something like "My file name is far too long for it to fit within 31 characters" to someone using the previous release of AIM client that doesn't. They'll get something like "My File name is far too#DEADBEEF" due to name mangling. So apple is saying that if you move that file to another drive (which copies) you are going to kernel panic. How romantic.

  1. MacNN.com Reader

    Fresh-Faced Recruit

    Joined: Jul 2001

    0

    hexadecimal kernel panic

    Yes, I had this happen to me, too!! I back up my iBook's entire HD to my PowerMac, then burn a CD of that just to be extra sure, every month or two. The last time I did this was just before switching to Jaguar. Saturday, I spent all day long wondering what the &*&@#** was going on that I couldn't simply transfer my HD as I had always done before, via Ethernet. The error message I got was something like, "File with name already exists." What an insane message! I thought, "This always worked before. Why now?" Eventually I just changed the name of about a dozen files and my "problem" was solved. Sort of. Only it wasn't really MY problem, if you ask me. I have to say I really don't like an OS telling me how to format my file names or how long to make them, either. This is a real irritant!

  1. Rosyna

    Forum Regular

    Joined: Aug 2001

    0

    You think that's weird

    Stuff a long file name with Drop Stuff 6.5 (the one that doesn't support it), then change the name of the file you stuffed. unstuff the archive making sure the file will end in the same location as the original. You'll get a duplicate file error! (if you unstuff to a different location, it should take the name of what you renamed the original to.

  1. MacNN.com Reader

    Fresh-Faced Recruit

    Joined: Jul 2001

    0

    How?

    I'm no software developer so this could be a naive question, but how is it that they let the iPod and the Finder copy bug get past them? I can see that all the testing in the world won't catch certain bugs but surely they would have made sure that an iPod was connected to a Mac when it was put to sleep in the course of every day usage, or that they did finder copies in various ways? They seem to be very obvious bugs to have hanging around. The name mangling thing has always irritated me - I have no idea what the workaround could be but there must be something better than seeing a load of weird characters half way through the file name. Since the change in the way the Mac Identifies files and their creators has changed I have had so many more issues with file naming - For me it has been a definate step backward. I used to laugh at PC users having to tell their computer which program to open a file with, but now I'm getting it too. Anyway - Drifting slightly off topic here..............

  1. MacNN.com Reader

    Fresh-Faced Recruit

    Joined: Jul 2001

    0

    VST

    hi there, exactly the same thing happens with VST FW pocket disks.

  1. MacNN.com Reader

    Fresh-Faced Recruit

    Joined: Jul 2001

    0

    IrDa?

    Any word on Synching through the infrared port?

  1. MacNN.com Reader

    Fresh-Faced Recruit

    Joined: Jul 2001

    0

    Kudos to Apple

    for documenting these bugs. Previously, many quirks were undocumented and therefore it was difficult to track down the source of the problem.

    This documentation not only "takes responsibility" for these issues, but indicates Apple engineers are working on fixes.

    Great work and a tremendously valuable service for Apple customers.

Login Here

Not a member of the MacNN forums? Register now for free.

 
close
Photo
toggle

Network Headlines

toggle

Most Popular

MacNN Sponsor

Recent Reviews

MaxUpgrades MaxConnect for 2006-2008 Mac Pro

Nobody outside of Cupertino's privileged bunch knows the future of the Mac Pro line for sure. Despite Apple's reluctance to tell us wh ...

Brother HL-3170CDW LED Printer

We've mentioned before that we are far from a paperless society. For now, at least, there are tasks that require a piece of paper for ...

HTC One

It is hard to overstate just how critically important the HTC One is to the Taiwanese company’s fortunes. Despite its alarming decline ...

toggle

Most Commented