10.5.6 and iRiver Music Manager Crashes My Mac

[martinvanderhof]

I have an iRiver IFP-995 flash player with the accompanying Music Manager software. I have a January (2008) Mac Pro.

I updated from 10.5.5 to 10.5.6 yesterday. Since doing so, every time I connect my iRiver via USB, my mac crashes with a message telling me to restart the computer. I can connect the iRiver fine, but it crashes when the software is open and I turn the iRiver player on so the software can read the player.

Has anyone else experienced this problem, or can anyone offer some troubleshooting suggestions?

Thanks, everyone.

 

[jaimev]

I have the exact same problem. For me, it happens when I connect my iRiver ifp-899 to a iMac (iSight) G5. Started happening immediately after upgrading to 10.5.6. At first I thought it was a munged Software Update, so I ran the Combo Updater, but same result.

I submitted a bug report and the contents of a kernel panic log file [*] to Apple (via http://developer.apple.com/bugreporter/bugrptform.html). Who knows if that'll do any good.

I've read about the open source ifp library (http://ifp-driver.sourceforge.net/) but have no idea whether it's been ported to OS X, and if so, how to use it to move files to my iRiver mp3 player.


[*]
Mon Dec 15 23:00:29 2008


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000008 PC=0x000000004C515FE4
Latest crash info for cpu 0:
Exception state (sv=0x4dff8a00)
PC=0x4C515FE4; MSR=0x00009030; DAR=0x00000008; DSISR=0x40000000; LR=0x4C515EBC; R1=0x4C926A60; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x4C515EBC 0x4C52C3E8 0x4C52C36C 0x0037D820 0x4C52B01C 0x0037AC9C
0x00094798 0x0002C200 0x00024CFC 0x000B364C 0x00000000
backtrace terminated - frame not mapped or invalid: 0xBFFFE510

Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBFamily(3.2.7)@0x4c503000->0x4c538fff
Proceeding back via exception chain:
Exception state (sv=0x4dff8a00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x56f9d280)
PC=0x90115158; MSR=0x0000F030; DAR=0xE00B3000; DSISR=0x42000000; LR=0x9011C080; R1=0xBFFFE510; XCP=0x00000030 (0xC00 - System call)

BSD process name corresponding to current thread: iRiver Music Man

Mac OS version:
9G55

Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:39:01 PST 2008; root:xnu-1228.9.59~1/RELEASE_PPC
System model name: PowerMac12,1
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x0009BCF0 0x0009C694 0x00029EA0 0x000AFA90 0x000B32F8
Proceeding back via exception chain:
Exception state (sv=0x4dff8a00)
PC=0x4C515FE4; MSR=0x00009030; DAR=0x00000008; DSISR=0x40000000; LR=0x4C515EBC; R1=0x4C926A60; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x4C515EBC 0x4C52C3E8 0x4C52C36C 0x0037D820 0x4C52B01C 0x0037AC9C
0x00094798 0x0002C200 0x00024CFC 0x000B364C 0x00000000
backtrace terminated - frame not mapped or invalid: 0xBFFFE510

Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBFamily(3.2.7)@0x4c503000->0x4c538fff
Exception state (sv=0x56f9d280)
PC=0x90115158; MSR=0x0000F030; DAR=0xE00B3000; DSISR=0x42000000; LR=0x9011C080; R1=0xBFFFE510; XCP=0x00000030 (0xC00 - System call)

BSD process name corresponding to current thread: iRiver Music Man

 

[idarrin]

Same thing for me. You guys are not alone. iRiver IFP 780.

 

[aendaman]

same for me...

Same for me (iRiver IFP-995, iRiverMusicManager v1.1.3).
Has anyone reported this to iRiver? I mean, their devices are great but the support is really lame. They still only have the v1.1.3 version of the software available (still only PPC, even after two years of Intel Macs... Hello ).
Should i TimeMachine back to 10.5.5 now? I am using the iRiver on a regular basis to record analog stuff...

I mailed to iRiver support. Their first answer was just laughable:

"Please do not try to connect any Iriver device to a macbook. the iriver product line was not made compatible for macs o/s."

I replied mentioning the fact that they themselves provide a Mac OS X version of the MusicManager software...

"The reply from my supervisor is that iriver is currently not selling any product that are mac compatible and old products do not currently have updates."

If thats the final say, goodbye iRiver, Hello any-funky-line-in-recording-device-as-fancy-and-handy-as-my-ifp-995-but-probably-not-invented-yet.

 

[redgatormc]

And the beat goes on... (or not so much...)

MacBook Pro + 10.5.6 + iRiver 1.18 + iFP-890T = toxic
aka "Great Grey Screen of Death"

I didn't even know there was a "Great Grey Screen of Death".

However, I think I might just get rid of the Mac rather than my beloved iFP-890T. The iRiver device has made many a travel mile shorter, and many a traffic jam more tolerable, whereas the Mac (versus Win-doahs) has just been different stupid s**t... I'd rather have stupid s**t that might actually be fixed one day...

Two-handed mouse? Who thought THAT was a good idea?

But thank you for the postings, guys...

 

[redgatormc]

Resolution...

Solution... and now I may be stuck with the stupid Mac...

Go to the www.iriver.com site and download the "MSC" firmware. This makes the device act like any other USB storage device (Sony Camera, Cruzer, etc.)

The iriver site has a flash dialog, which is slow and stupid, so be patient:

[Support][Downloads]<enter "ifp-800" in the empty box>[GO][IFP-800 Series Firmware V1.95(MCS Version)]<select your particular country firmware download>

Since the Mac is WACKED, you will have to find a willing Windows box, install ye ol Music Manager, and install the firmware from there. Once done, the iRiver device works like a USB storage device.

Further firmware upgrades (probably not for me with my crufty old device) would involve downloading a new firmware load as a file, then executing that as a firmware upgrade (no manager involved).

The downloads are 3-4X slower than the Music Manager, but the Music Manager was never a bit hit with me (frequently crashed under Windows, always crashed on exit). The USB function looks to work just fine.

And voice recording creates *.MP3 files rather than *.REC files (which, it appears in a simple experiment, are EXACTLY THE SAME THING).

So we all happy. Throw away the Music Manager and come over to reality...