Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

iTunes2.0.1 released Apps
Apple has now re-released iTunes2 for OS X, in the form of a new iTunes 2.0.1, available on the iTunes2 download page. For those of you who might have grabbed the original installer, delete it now. It had a serious error with the installer script that could wipe your hard drive in certain circumstances.

The short version of what Apple appears to have changed in this new installer? Any reference that used to look like this
rm -rf $2Applications/iTunes.app 2< /dev/null
now looks like this
rm -rf "$2Applications/iTunes.app" 2< /dev/null
The addition of the quotation marks takes care of any issues regarding drives with spaces in their filenames. In addition, the file lengths on "iTunes.bom" and "iTunes.pax.gz" have both changed, indicating that there were additional changes made behind the scenes. I haven't bothered top expand and compare the two .pax archives; at this point, suffice it to say that Apple made a bad mistake, realized it, and acted quickly (for a large corporation) to fix the problem. This, of course, is little solace for those who were affected.

A detailed explanation of the problem with the earlier installer script is available if you read the rest of this article...

Here's what I was theorizing earlier today...

If you downloaded the iTunes2 installer and have not yet installed it, I would highly recommend that you do not install it! Apple has pulled the installer due to a bug in the script. Thanks to a tip in an email about the cause (spaces in volume names), I went digging into the package installer and think I found the source of the problem. The following code is in a file called 'preflight' inside the iTunes.pkg installer (in Contents/Resources):
# if iTunes application currently exists, delete it
if [ -e $2Applications/iTunes.app ] ; then
rm -rf $2Applications/iTunes.app 2< /dev/null
fi
So what's the problem? If your volumes have spaces and are named similarly (let's say "Disk", "Disk 1", and "Disk 2"), then this bug could bite you. The '$2' variable that's passed in contains the path to your selected iTunes installation destination. In our example, let's assume it was headed for "Disk 1". So '$2' should contain /Volumes/Disk\ 1 (notice the backslash for the space). However, if it instead contained /Volumes/Disk 1, then the "rm -rf" command would execute TWICE. It would look like this:
rm -rf /Volumes/Disk 1/Applications/iTunes.app 2< /dev/null
One of the commands (the second half, 'rm -rf 1/Applications/iTunes.app') would probably not do anything, since the path is invalid. The second command, though, could be brutal. 'rm -rf /Volumes/Disk' would delete the entire volume 'Disk' used in this example.

I can't see how the "$2" variable is built, so this is all conjecture based on the evidence and looking at the "preflight" file. Obviously, there's an issue with the installer, since Apple has now pulled it ... but if you grabbed it already, I would highly recommend you do not use it, even if you don't appear to meet the criteria listed above. Just wait for a new installer from Apple, and keep your data safe!

UPDATE: Now that I have the new installer, it's quite easy to see what changed. The 'preflight' script now looks like this:
# if iTunes application currently exists, delete it
if [ -e "$2Applications/iTunes.app" ] ; then
rm -rf "$2Applications/iTunes.app" 2< /dev/null
fi
The quotation marks take care of the issues with space in drive names, and there were also some apparent changes to a few of the files in the iTunes bundle.
    •    
  • Currently 0.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (0 votes cast)
 
[4,464 views]  

iTunes2.0.1 released | 30 comments | Create New Account
Click here to return to the 'iTunes2.0.1 released' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Arrrg...! Login hang!
Authored by: junehao on Nov 03, '01 04:36:32AM

After installed iTunes2, reboot, and login to my account, and got a HANG. The login process seems being waiting for something. The menu extras already show up and functional. Only the login progress bar keep running... No Apple menu, no dock, no Finder, no everything, except the menu extras.

After 10 minutes I gave up and rebooted the machine. Then I got the same HANG when logging in. Now if I reboot into OS 9, I still don't know the problem... wait a second... Since I have the menu extras, and there's an item in each extra menu to open its own preference, which means, the System Preferences app! Yes! I got my System Preferences running! And when I checked the login item, I found a new item "iTunesHelper" was there and set to "Hide". I suspected it was the problem. So I removed it and logout by selecting the Apple menu (yes, now I also got the Apple menu) -> Log Out... and log back in. Voila! Finally I got my desktop and Finder back.

I checked iTunes2 and found out where the iTunesHelper is:

/Applications/iTunes.app/Contents/Resources/iTunesHelper

It is also a software bundle. When I open the package, I saw this file:

iTunesHelper.app/iTunesHelper

This file not only resides in the same level of the folder "Contents", also links to the actual executable iTunesHelper.app/Contents/MacOS/iTunesHelper. Weird, isn't it?

Anybody got idea of what iTunesHelper is for? I only know it's a background only app.



[ Reply to This | # ]
Arrrg...! Login hang!
Authored by: Paul Burney on Nov 03, '01 11:08:38PM

Actually, I had this problem twice last week and I don't think it was related to iTunes. I did the same thing you did, hard restart at first and then the problem still occurred on the next login.

After login stalled, I was able to open system prefs, then use the force quit keys to bring up the finder from which I could get to the terminal and then kill the loginwindow process. I mentioned it on the apple discussion boards, but no one responded.

My problem seemed to work itself out after a while, I guess. Hopefully it doesn't happen to you again.



[ Reply to This | # ]
Arrrg...! Login hang!
Authored by: SeanAhern on Nov 04, '01 06:24:05AM

I had *exactly* the same experience.

At first, I thought the installation of iTunes 2.0.0 killed me, since I have partitions, and there are spaces in my partition names. Luckily, the partition that has OS X on it is just called "X", so this wasn't actually the case.

But I would get this annoying hang. Thing is, if I logged in as "root", the hang didn't happen. I tried killing processes with "kill -9", and they wouldn't kill. I tried doing a "sudo reboot" and nada. This was a weird one.

Once I removed the ITunesHelper from the login window (dunno why I looked there), things seem back to normal.

Wacky! I am expecting an iTunes 2.0.2 shortly...



[ Reply to This | # ]
Readme
Authored by: vonleigh on Nov 03, '01 06:19:18AM

Make sure to read the readme. It says something to the effects that one must delete iTunes before installing iTunes 2. Also, to get rid of the dock icon before opening the newly installed app.

Installed and had no problems. The buttons on the bottom are redesigned (they look like metal instead of reflective colored plastic). Also the full screen Visuals seem to work smoother on my G4. Wish i had an ipod ;)


Vonleigh



[ Reply to This | # ]
Readme
Authored by: origjohn on Nov 03, '01 04:16:32PM

I downloaded Itunes2 early this morning. The only problem was that the file i downloaded had an ext of .pl and would only open as a text file. After a few tries, I changed the ext from .pl to .dmg
The file then worked, and mounted a disk image with itunes2 filder inside. Opening the folder was the itunes2.pkg. I clicked this, and after asking where to install itunes2, it installed and then optimized without problems. I didnot delete itunes1 first, and the install appeared to delete the old itunes and install the new verson without a problem. The new version works great, I made an audio CD and it was very fast as it did not convert the mp3 files first, it appears to do it on the fly. The equalizer works great too. So the problems mentioned are not affecting everyone. I did this on my powerbook g3/500 firewire. I have not tried it on my G3 blue/white 400 as of yet.



[ Reply to This | # ]
And iTunes IS Scriptable!
Authored by: DougAdams on Nov 03, '01 09:25:11AM

Create a folder called "Scripts" in the iTunes folder in OS 9 or in OS X in the Users > username > Library > iTunes folder folder. You can then run compiled and application scripts from iTunes' Scripts Menu. Then, visit my site for free scripts and info:

http://www.malcolmadams.com/itunes/



[ Reply to This | # ]
scripting with streamripper?
Authored by: joon on Nov 04, '01 01:20:01PM
any chance of you making a script to rip a playing stream with stream ripper? Streamripper uses the terminal and I know the terminal is scriptable. I have some scripting knowledge but I'm a little behind when it comes to scripting in X. It would be great if you could just access the script from the script menu and rip any stream. Who needs Napster? ;) stream ripper at sourceforge thanks! joon

[ Reply to This | # ]
scripting with streamripper?
Authored by: sabi on Nov 04, '01 02:51:45PM
If you don't need/can't use the song-splitting ability of streamripper, you might want to try archiver.pl written by Jamie Zawinski instead - it's what I use most of the time. It just records a stream, no relaying, no cutting into pieces, but it uses zero CPU compared to streamripper (which uses close to 100% CPU on a G4/533 for me).

Your best bet is to find some osax or something that lets you run shell commands from AppleScript. My recording script actually calls one or the other based on whether I request relaying:

     if [[ -z $@ ]] {
       mkdir $rptmp
       $HOME/src/archiver.pl --verbose $rpurl $rptmp $rpsecs || exit
       mv $rptmp/*/*.mp3 $rpd/$fn
       rm $rptmp/*/*.time
       rmdir $rptmp/*
     } else {
       streamripper $rpurl -r -s -d $rpd -l $rpsecs || exit
       mv $rptmp/* $rpd/$fn
     }


[ Reply to This | # ]
scripting with streamripper?
Authored by: joon on Nov 04, '01 11:43:57PM

Close to 100% on a 533 G4? That sounds too high. I get < 40% on a Titanium G4 500. Just today I had streamripper rip and relay while iTunes2 was playing that relay and this was with IE 5 running, Photoshop and Dreamweaver in classic for my web work -and yes, I was working as usual going back and forth, those apps weren't just sitting there. I know I was really pushing it but I had very little problems. Only if that Altivec kicked in more often it would be less of an issue.

Wow! archiver.pl can do that as a perl script? Doesn't it need extra libraries to call on. I have to try it out. Thanks for the link.

And any chance of you commenting on that script? It looks nothing like Applescript. I'm lost.. I have a lot to learn.

thanks alot Sabi!



[ Reply to This | # ]
ive got it worst~!!
Authored by: dewme5 on Nov 03, '01 11:42:45AM

alright.. so I didn't read the readme... really.. i meant to. So, becuase of that, I didn't know that I was supposed to get rid of itunes first. But the installer went on just fine. until it got to the last part. where it "optimizes machine for performance" or something like that. well it just hung there. So, after a long wait, i force quit the installer. I tried to go to my drive where I had the readme.... all my files are gone! I have 3 drives. one is a 42gb in 3 partitions (which contains osx, and on another partition, my downloaded files.... where I was installing itunes from) Another 42gb drive (both are maxtors) which is for music, and big applications (mostly os9 stuff) and a third which is the apple 10gb drive that came with the computer. that is my os9 drive.
on the first drive, I lost most every file in my third partition. but, in it's place are two files. "desktop DB and Deskop DF" I don't remember them there before, but I could be wrong. I'm sure there is other stuff missing off of that drive, in different partitions.
on the second drive, I am missing about 12gb of music another 10gb of files and programs, but some are still there.. I haven't checked everything, but for instance, my "music" folder is still there, but inside of it is ALL messed up. lots of missing stuff.
on the third drive, sort of the same thing Lots and Lots of missing stuff. I have a system folder (for os9) but the only thing in it, is my extension folder.)

This happened last night before bed. so I tossed and turned alot! I did attempt one reboot. The startup screen was a gray back ground wiht a happy mac. but didn't do anything else. I shut off and went to sleep. This morning, the same thing. gray screen with happy mac. I put in the 10.1 upgrade disc, and then used the disk utility off of there. There was a problem with my osx partition, so I repaired it, everything looked fine after that. so i rebooted, was greeted by a gray screen with a happy mac for a few seconds, and then right into osx.1 But, nothing was fixed. I am avoiding doing as much as possible on my computer. I'm not running anyting but sherlock, ie5, and the finder. I know it's something that can be repaired if I don't mess anything up. How do i fix those first couple of sectors on a hard drive.

I have at my disposal, a firewire case and an iMac. So i can pull my drives out, hook them up thru the firewire, and work off of that other mac. it has techtool 3 on it. But that's the only thing i can think of. PLEASE HELP



[ Reply to This | # ]
found the problem
Authored by: dewme5 on Nov 03, '01 02:43:50PM

Itunes2 + multiple partitions = screwed up computer. there are lots of complaints at
http://discussions.info.apple.com/webx?50@@.efb9834/0

there is also more information at www.macintouch.com

seems apple did a bad thing.



[ Reply to This | # ]
os x version not available.
Authored by: charlietuna on Nov 03, '01 03:08:08PM

the os x version isn't on the apple web site. it says that the os x version will be available later.



[ Reply to This | # ]
It worked for me on OSX1.1
Authored by: origjohn on Nov 03, '01 04:20:46PM

Readme
Authored by: origjohn on Sat, Nov 3 at 04:16PM
On OSX1.1 I downloaded Itunes2 early this morning. The only problem was that the file i downloaded had an ext of .pl and would only open as a text file. After a few tries, I changed the ext from .pl to .dmg
The file then worked, and mounted a disk image with itunes2 filder inside. Opening the folder was the itunes2.pkg. I clicked this, and after asking where to install itunes2, it installed and then optimized without problems. I didnot delete itunes1 first, and the install appeared to delete the old itunes and install the new verson without a problem. The new version works great, I made an audio CD and it was very fast as it did not convert the mp3 files first, it appears to do it on the fly. The equalizer works great too. So the problems mentioned are not affecting everyone. I did this on my powerbook g3/500 firewire. I have not tried it on my G3 blue/white 400 as of yet.



[ Reply to This | # ]
Shell scripts checking for old iTunes files
Authored by: ashill on Nov 03, '01 04:21:02PM
In the same Resources folder of the iTunes installer package, the file VolumeCheck checks for and deletes the receipt from the previous install of iTunes:
#!/bin/sh

# if current iTunes pkg exists, delete it b/c of Installer bug
if [ -e $1Library/Receipts/iTunes.pkg ] ; then
	rm -rf $1Library/Receipts/iTunes.pkg 2> /dev/null
fi

# return do nothing status to Installer
exit 0
I'm not sure what that first comment in the script means. Presumably, there's some bug in the installer that prevents updating an old version succesfuly; therefore, they just delete the remnants of the old version. As you noted, Rob, the bug in the shell script is the one that deletes every file on the hard drive; I wonder what the bug in the Installer itself is.
By the way, $1 and $2 (and $n, where n is an integer) are not normal shell variables. I'm not very experienced with shell scripts, but, as I understand it, $1 refers to the first argument on the command line call, $2 to the second, etc. Therefore, if someone could find the script in there that executes the preflight script, we should be able to figure out the problem more preciesly. -Alex Hill

[ Reply to This | # ]
install problems
Authored by: dewme5 on Nov 03, '01 04:21:40PM

I did not delete my previous version of itunes. but I have read cases of people that did, and did not delete itunes.. both have had problems
I do have multiple partitions, bob <osx drive>, bob.2, bob 3, A Big Boy, and Macintosh HD <os9.2 volume>

Bob is what i installed to, and is also the X partion. every other partiton got screwed up.



[ Reply to This | # ]
install problems
Authored by: ashill on Nov 03, '01 04:36:13PM

Even if someone did delete iTunes, the bug would still bite him if he didn't delete the iTunes package receipt; see my comment "Shell scripts checking for old iTunes files."

I myself had no problems, although I deleted only the application itself. I have two partitions: one named "Hard Disk" and one (invisible) named "swap". I'm not sure, but I think my external disk (named "Firewire Disk") was also mounted. I guess I was lucky because none of my partitions' names are the same before the first space.

-Alex Hill



[ Reply to This | # ]
Trying to replicate...
Authored by: robg on Nov 03, '01 04:59:54PM

I've been trying to figure out exactly what happened, but I'm having no luck. I created a "mytestdir" directory (to duplicate "Volumes) and then made "test", "test 1" and "test 2" directories inside. I then tried to execute what I thought the "rm -rf" command would look like ("rm -rf mytestdir/test 1/iTunes.pkg 2> /dev/null"). This did, indeed, delete the "test" directory, but "test 1" and "test 2" were fine. I'm not sure how this managed to delete multiple volumes...unless Apple had a wildcard symbol after the "Disk" word?

On the MacWorld boards, though, one of the people that got zapped had very different volume names (but they did have spaces), so there's more going on than just similar names...

-rob.



[ Reply to This | # ]
Have I been incredibly lucky?
Authored by: ebow on Nov 03, '01 05:53:40PM

[KNOCK ON WOOD]

My iMac's hard drive is partitioned into 6 volumes. Two of these, "Mac OS X" and "Mac OS 9" have spaces in their names. I installed to the volume "Mac OS X" and have experienced no ill effects.

I downloaded and installed iTunes 2 at around 1:30 this afternoon (3 Nov). I didn't look around too much for user feedback and first impressions, which I usually make a point of doing. I didn't read the ReadMe, so I didn't know to delete iTunes 1.1. I did however stuff it just in case I wanted to go back. The installation went rapidly, but the cleanup took a bit of time, so I walked away. When I came back, my system had already restarted, and iTunes 2 had replaced 1.1 in the Dock. It was only *after* all of this that I read these horror stories. Now I'm a bit nervous about restarting my computer, but I guess if I'm okay at this point, I'll be okay in general. I certainly hope so!



[ Reply to This | # ]
iTunes 2.0.1 out; shell scripts unchanged
Authored by: ashill on Nov 04, '01 12:22:16AM

Apple has released the (presumably) fixed version. The preflight and VolumeCheck shell scripts that actually did the erasing are unmodified, so the calls to them were presumably fixed so as to not contain spaces in the pathnames.

-Alex Hill



[ Reply to This | # ]
Slight changes...
Authored by: robg on Nov 04, '01 12:29:08AM

Actually, they added double-quotes to every script file ... so the $2 is unchanged from the prior release, which means this was just a space-in-filenames problem, apparently.

I'm still confused, though, as to how people could have lost non-similarly-named volumes if this is true. It shouldn't have done anything to "XYZ" if the other partitions were "ABC", "ABC 1" and "ABC 2". Yet several people have reported losing all the partitions. Odd.

-rob.



[ Reply to This | # ]
iTunes 2.0.1 out; shell scripts unchanged
Authored by: ashill on Nov 04, '01 12:31:07AM

Whoops; I missed the quotation marks. ;)

This whole debacle will sure make me be doubly careful that I'm not typing
sudo rm -rf / path/to/file
next time I try to delete something. It also makes you realize what a wonderful invention the trash can was when Apple first introduced it; I wish all installers moved old files to the trash rather than deleting them. It would have made this whole thing much less serious.

-Alex Hill



[ Reply to This | # ]
Easy fix (unverified)
Authored by: enkidu on Nov 04, '01 12:30:52AM
I can't be sure since I didn't have a chance to download the iTunes2 upgrade but by looking at the shell script code, I think that changing the line:
rm -rf $2/Applications/iTunes.app 2< /dev/null
to:
rm -rf "$2/Applications/iTunes.app" 2< /dev/null
should eliminate the danger of mis-tokenizing the rm -rf line.
As a part-time 'nix hacker (Linux, SunOS, OSF and now OSX), I find the use of spaces in directory/file names a "bad thing" and something that should be avoided, particularly in volume names since many basic system scripts don't properly quote their arguments. Because of the way that sh works, spaces in names just doesn't work unless you're totally anal about quoting everything. This rule also helps reduce confusion (for example doing an ls in a directory with three files named "Enkidu Pictures", "Pictures" and "Enkidu"). This is also why I don't run shell scripts in my wife's user area.
$1 and $2 are the shell variables and represent the first and second arguments to a script.

[ Reply to This | # ]
Yup...
Authored by: robg on Nov 04, '01 12:38:45AM

That's what Apple changed ... by the way, what does the "2 > /dev/null" part do? I know "> /dev/null" is redirect to null, but what's the "2" for?

-rob.



[ Reply to This | # ]
Yup...
Authored by: Brad Puett on Nov 04, '01 02:04:54AM

That's what Apple changed ... by the way, what does the "2 > /dev/null" part do? I know "> /dev/null" is redirect to null, but what's the "2" for?

-rob.




" 2> " refers to Standard Error, just as " > " refers to Standard Output. So the statement " 2> /dev/null " means that any "leftover" error messages will be "trashed" (i.e. discarded, thrown away).

Hope that was clear!


[ Reply to This | # ]
2 /dev/null
Authored by: reverie on Nov 04, '01 02:07:01AM

2> /dev/null
will consolidate the standard output (stdout) and diagnostic output (stderr) of the preceding command and then send it to /dev/null (i.e., a black hole). Basically, it's making sure the script stays quiet. It's a feature of sh, the Bourne shell, and you can read more about it if you 'man sh'.



[ Reply to This | # ]
And so the deMacification continues...
Authored by: name99 on Nov 05, '01 02:44:30AM

Am I the only one who is horrified, not just by the fact that these bugs occur, but by the response to them?
Here we have Apple screwing up BIG TIME, and the general public response in this forum is basically "Tough---you shouldn't have used spaces in any item on your file system".

Once upon a time Apple and the Mac was about computers adapting to human habits. Now that the UNIX crowd are firmly in charge of Apple, not only are they shoving stupidities like file-name extensions down our throats, or file-case-sensitivity on UFS, but they are now slowly working on making the user , in self censorship, ensure that every file name they use meets UNIX standards.

What happened to
C:>ONGRATLN.W95 ?
When people trying out Win XP say that it looks better than MacOS X and is easier to use (something I have seen in more than one place, including in the press) it is time for Apple to think seriously about what they are doing.
And it does not help the process when the UNIX heads on the net act as apologists for Apple's user hostility, on the grounds that "well we should all learn the UNIX way of doing things anyway".



[ Reply to This | # ]
And so the deMacification continues...
Authored by: ashill on Nov 05, '01 10:46:39AM

Apple made a major mistake. It was completely their fault, which they publicly acknowledged very quickly. They released a fix very quickly.

This is in no way an apology for an egregious and one might even say negligent mistake on their part, but bugs do happen in programs, particularly in installers. Bugs like this can happen in OS 9 installers; the difference is that we can read the shell scripts for this particular OS X installer and figure out exactly what went wrong. I personally find it interesting to investigate the cause of the bug, but I do not believe that it is the end user's responsibility to know what bit them.

I use spaces in my volume names and in my file names. It is rare that Mac OS X causes problems because of spaces in file names; when it does, it's a bug that needs to be corrected, and has been corrected promptly by Apple.

If you do stuff in a shell on a regular basis, it can be a pain to have files with spaces in them. Therefore, I try to avoid using spaces in files that I regularly access from the terminal. However, if you don't use the terminal (much), there should be no need to worry about spaces, and usually, there is no need to worry about spaces.

I don't speak for this forum, but I am sympathetic to anyone who was bitten by this bug, and I am impressed by Apple's response (although I am not impressed by their testing prior to release). I wish I could be helpful, rather than simply understand what went wrong, but I can't.

Regarding file-case sensitivity on UFS: HFS+ is the default file system, and it behaves exactly like OS 9 with regards to file-case sensitivity: it is case-preserving, but not case-sensitive. File name extensions are not a Unix concept, they're a dumb Windows concept that Apple is sorely mistaken in adopting (IMHO).

No one is saying that we should all learn the Unix way. I am learning the Unix way because I think it's fun, and because I use Solaris (Sun's version of Unix) boxes in the astronomy lab in which I work. It is Apple's publicly stated position that any problem in OS X that requires Unix knowledge to fix is an unresolved bug; for the most part, they have lived up to that promise (including with this iTunes debacle; it could just have well have been a bug in compiled code, as far as Apple's fix is concerned). Sometimes, those of us with Unix knowledge can fix a problem before Apple releases a fix, but that doesn't mean that Apple is forcing users to learn the Unix way; non-Unix-saavy users will have to wait as long (and no longer) than they did for a fix for a similar problem in OS 9.

-Alex Hill



[ Reply to This | # ]
And so the deMacification continues...
Authored by: Brad Puett on Nov 05, '01 01:56:13PM

The main problem I have with this whole "mistake" is that, for at least some of us, it' not fixed!! if I try to install iTunes 2.01 now, as soon as it reboots fromthe installation, I'm left with the "smiley mac face" starign at me from the screen, NO cursor at all, and a freeze that lasts until I force a hardware reset, and then force a PRAM reset, just to get back into 9.2.1!! I'm sorry, but this unacceptable!!

Especially since I'm getting a LOT more errors (roughly 10x) in my log files, plus 2 kernel panics (of which I have never had before this "installation"), which I can never get out of unless I force a hardware reset!!

In order to recover from the "installation", I had to:
a) Hardware reset (i.e. "paperclip")
b) PRAM reset (in order to allow me to boot into 9.2.1)
c) Delete everythig related to "iTune" on the "X" partition ...
d) Reinstall 10.1, using the 10.1 update CD
e) Boot (finally!) into 10.1, go to System Preferences, go to Login, and delete off the iTuneHelper program that was still selected (even though it didn't exist!)

Here's just 2 examples of the messages I'm now still getting:


Nov 5 12:34:02 localhost kextd[41]: loading module: com.apple.iokit.IOHIDFamily.
Nov 5 12:34:03 localhost kextd[41]: loading module: com.apple.iokit.IOUSBHIDDriver.
Nov 5 12:34:04 localhost mach_kernel: USB: 3669.929: [0x16F7600] USB Generic Mouse @ 4 (0x14130000)


Nov 5 12:39:15 localhost mach_kernel: USB: 3980.904: AppleUSBHub[0x16B7A00]::stop - trying command sleep (0/1).
Nov 5 12:39:15 localhost mach_kernel: USB: 3980.960: [0x16F7600] USB Generic Hub @ 3 (0x14100000)
Nov 5 12:39:15 localhost kextd[41]: loading module: com.apple.iokit.IOHIDFamily.
Nov 5 12:39:15 localhost kextd[41]: loading module: com.apple.iokit.IOUSBHIDDriver.
Nov 5 12:39:16 localhost mach_kernel: USB: 3982.276: [0x206CC00] USB Generic Mouse @ 5 (0x14130000)
Nov 5 12:39:16 localhost mach_kernel: USB: 3982.277: [0x16D1000] USB Generic Keyboard @ 4 (0x14110000)
Nov 5 12:39:25 localhost mach_kernel: USB: 3990.751: AppleUSBHub[0x16B7A00]::CheckForDeadHub - calling commandWakeup
Nov 5 12:39:25 localhost mach_kernel: USB: 3990.752: AppleUSBHub[0x16B7A00]::stop - returned from command sleep (0,0)!!


I realize that more than a few people lost data, but what has me temporarily upset is that I've been given the impression by the major Mac Sites that the iTunes 2.01 package *fixed* all the problems, and Apple is no longer working on a solution! It's not fixed for some of us!!

(Sorry, but it's been a *very* frustrating weekend ...)




[ Reply to This | # ]
Installer log file
Authored by: ashill on Nov 04, '01 11:20:26AM
This may be beating a dead horse at this point, but I discovered an iTunes installer log in /Library/Receipts. (I do not have an iTunes installer receipt-- is that true for everyone after the iTunes 2 install?) Note that this is a receipt from the install of iTunes 2, not 2.0.1; I did not install 2.0.1. The relevant lines: Target Selection Selected volume "Hard Disk" Mounted at: / My theory is that the output of the "Mounted at:" line is the $2 argument that we haven't been able to see. Therefore, anyone who's other disks were erased must have installed to a partition mounted at "/Volumes/Disk name with a space". Does anyone have this log file after an install erased other partitions? If so, what does "Mounted at:" say? -Alex Hill

[ Reply to This | # ]
2.02 released...
Authored by: robg on Nov 16, '01 10:15:06AM
No word on what's changed. I checked the installer package, and they still have the correct quotes in place :-). www.apple.com/itunes -rob.

[ Reply to This | # ]